[prev in list] [next in list] [prev in thread] [next in thread]
List: gnuradio-discuss
Subject: Re: help for a sdr-based sound-art installation
From: Stefano Zorzanello <stefanozorzanello () gmail ! com>
Date: 2021-02-14 7:10:05
Message-ID: 64716f0b-2242-4ac9-8630-f030201b9ebc () gmail ! com
[Download RAW message or body]
Yes, just hackRF One plugged into the RPI...
===
Sent from my mind, some fingers and electronics helped.
Il giorno 13 feb 2021, 23:13, alle ore 23:13, Fabian Schwartau <fabian@opencode.eu> ha scritto:
>You are welcome :)
>I can't actually explain why it is working with the hackrf argument. If
>you have only one sdr connected, it should work without it.
>Anyway, I'm glad it works now.
>
>Am 13. Februar 2021 22:54:32 MEZ schrieb Stefano Zorzanello
><stefanozorzanello@gmail.com>:
>>please apologize, I didn't realize to have replied just to you.
>>
>>about hackrf recognition, this is the terminal report:
>>
>>- - - -
>>
>>$ hackrf_info
>>Found HackRF board 0:
>>USB descriptor string: 0000000000000000088869dc3326571b
>>Board ID Number: 2 (HackRF One)
>>Firmware Version: 2017.02.1
>>Part ID Number: 0xa000cb3c 0x005d4f64
>>Serial Number: 0x00000000 0x00000000 0x088869dc 0x3326571b
>>
>>- - - -
>>
>>in GRC after an initial alert window
>>"The xterm executable '' is missing.
>>You can change this setting in your gnuradio.conf, in section [grc],
>>'xterm_executable'.
>>(This message is shown only once)"
>>
>>I have change the permissions of grc.conf to set the file like this:
>>
>>xterm_executable = /usr/bin/xterm
>>
>>after this change the alert hasn't appeared anymore.
>>
>>*And finally adding "hackrf" in the device argument in osmocom source
>>did
>>the trick! *
>>
>>So I thank you very much, you could not believe but I spent a couple
>of
>>week about this silly thing, beating my head on the wall (with the
>risk
>>to
>>break at least one of the two)
>>
>>So it's quite likely that I'll be back with other newbie issues... but
>>in
>>the meantime I thank you very much for your support,
>>all best
>>Stefano
>>
>>
>>
>>Il giorno sab 13 feb 2021 alle ore 20:47 Fabian Schwartau <
>>fabian@opencode.eu> ha scritto:
>>
>>> Hi Stefano,
>>>
>>> we should stay on the mailing list, so everyone can follow and
>>contribute.
>>> Are you sure there are not other messages? Because those below are
>no
>>> error messages, just a warning and a bit of information, nothing to
>>> really worry about.
>>> One common problem (which I did not have) is missing permission on
>>the
>>> hackrf. But then you should get an error message telling that he was
>>not
>>> able to access the hackrf. Can you send the complete output of the
>>> program? Also try running it with sudo to check if it is a
>permission
>>> issue.
>>> Do you have multiple SDRs (you said something about an rtl-sdr?)
>>> attached to the Pi? Try adding "hackrf" (without the quotes) to the
>>> device arguments in the osmocom source.
>>> Also try hackrf_info in a terminal to see if the hackrf is detected
>>> properly. You can also try osmocom_siggen or osmocom_spectrum_sense
>>and
>>> see if you can access the hackrf.
>>> What if you replace the osmocom source with a random source (also
>add
>>a
>>> throttle block to limit cpu usage)? Does it work?
>>> Just to make sure: You are running a graphical environment and
>>starting
>>> the script from there, not an ssh connection?
>>>
>>> Best regards,
>>> Fabian
>>>
>>> Am 13.02.21 um 19:25 schrieb Stefano Zorzanello:
>>> > Hi Fabian, thank you very much for your reply.
>>> >
>>> > I'm using RPI 3b, with Debian 9.13.
>>> > I have just installed gnuradio-companion 3.7.10 again following
>the
>>> > terminal commands you wrote me
>>> >
>>> > $ sudo apt install gnuradio gr-osmosdr hackrf
>>> >
>>> > the software installation went fine but as I run the flowgraph I
>>get no
>>> > window displaying any signal, and the same error message
>>> >
>>> > - - -
>>> > Warning: failed to XInitThreads()
>>> > linux; GNU C++ version 6.2.0 20161010; Boost_106100;
>>> > UHD_003.009.005-0-unknown
>>> >
>>> > gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10
>>> > built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri
>hackrf
>>> > bladerf rfspace airspy soapy redpitaya
>>> >
>>> > - - -
>>> > any other idea to make it working?
>>> > thanks again,
>>> > best regards
>>> >
>>> > Stefano
>>> >
>>> > Il giorno sab 13 feb 2021 alle ore 17:26 Fabian Schwartau
>>> > <fabian@opencode.eu <mailto:fabian@opencode.eu>> ha scritto:
>>> >
>>> > Hi Stefano,
>>> >
>>> > don't worry asking such questions here on the list. That's its
>>> purpose I
>>> > guess ;)
>>> > First of all: I was able to run both of your flowgraphs on my
>>PC
>>> with a
>>> > HackRF One, so the problem lies somewhere else.
>>> > A small google search reavealed no perfect solution, but it
>>indicated
>>> > that something may be wrong with your installation. Like
>>gnuradio was
>>> > build against a certain library version but you are using a
>>> > different one.
>>> > How did you install gnuradio on the Pi? What Pi is it exactly?
>>An
>>> > original Pi 1 (A/B)? You may have trouble feeding 10 Msps
>>though that
>>> > old hardware. But it should start anyway.
>>> > What OS are you using? Which version?
>>> > I would recommend installing gnuradio from the distro
>>repositories
>>> using
>>> > apt. If you did so, a very simple solution may be to try a
>>different
>>> > distribution (or version), like Raspi OS (Raspbian), Ubuntu,
>>Arch,
>>> ...
>>> > there are many for the Pi. This will likely be a straight
>>forward
>>> > workaround for your problem.
>>> > Nevertheless, I just tried it on one of my Pi 3 with a fairly
>>clean
>>> and
>>> > up-to-date Raspi OS. I installed the following stuff:
>>> > $ sudo apt install gnuradio gr-osmosdr hackrf
>>> > And both of your flow graphs worked like a charm with that.
>>> >
>>> > If you have any further questions, feel free to ask them :)
>>> >
>>> > Hope I could help,
>>> > Fabian
>>> >
>>> >
>>> > Am 13.02.21 um 15:04 schrieb Stefano Zorzanello:
>>> > > Dear list members,
>>> > >
>>> > > I'm sorry to bother you with the classic newbie stuff, but
>>I'm
>>> stuck -
>>> > > since some days (the solutions found on the web didn't work
>>for
>>> > me) - to
>>> > > this point:
>>> > >
>>> > > - gnuradio-companion RaspberryPi 3b + hackRF one with a very
>>simple
>>> > > blocks flow doesn't display any signal window;
>>> > > and the error message I get is the following one:
>>> > >
>>> > > - - - -
>>> > >
>>> > > Warning: failed toXInitThreads()linux; GNU C++version 6.2.0
>>> 20161010;
>>> > > Boost_106100; UHD_003.009.005-0-unknowngr-osmosdr
>>0.1.4(0.1.4)
>>> > gnuradio
>>> > > 3.7.10built-in sourcetypes: file osmosdr fcd rtl rtl_tcp uhd
>>miri
>>> > hackrf
>>> > > bladerf rfspaceairspy soapy redpitaya *** Error
>>> in`/usr/bin/python':
>>> > > corrupted double-linked list: 0x01a81c08 ***
>>> > >
>>> > > - - - -
>>> > >
>>> > > I'm trying to follow some very nice youtube tutorial
>(Ossman,
>>> Hackaday
>>> > > etc. ) but I cannot proceed if I can't neither make grc
>>working
>>> with a
>>> > > simple sketch.
>>> > >
>>> > > Any help is greatly appreciated.
>>> > >
>>> > > More, if you have any suggestion or advice, here it follows
>a
>>> general
>>> > > description of the process I want to develop for my
>sound-art
>>/ sdr
>>> > > based installation.
>>> > >
>>> > > The set up should be as follows:
>>> > >
>>> > > - a small robot(flor hover type) moves randomly in a
>>restricted
>>> area
>>> > > (few sq meters)of a big room.
>>> > > On this device, an RPI("A") + [DVB-T+DAB+FM] usb dongle,
>>> > > battery-powered, is mounted to detect some RF activity in
>>some rf
>>> > range.
>>> > > Some values should be extracted (intensity over time of a
>>> particular
>>> > > freq // and intensity of shifting detected frequencies). The
>>> movements
>>> > > of the robot in the room should cause different detected
>>values.
>>> > >
>>> > > - these values should be shared or sent in real-time to an
>>external
>>> > > software (PureData) that sends these values via OSC to
>>another
>>> > RPI("B"),
>>> > > which is steady, that will use the incoming values as a
>>control
>>> signal
>>> > > for some audio DSP-treatments (sampling and granulation).
>The
>>raw
>>> > audio
>>> > > material for dsp audio treatments will be just RF noise.-
>The
>>audio
>>> > > treatments will be played inside the room via loudspeakers.
>>> > >
>>> > > - through a microphone and dsp, the live audio stream will
>be
>>> analyzed
>>> > > in PureData (intensity and spectrum-centroid) in real-time
>by
>>the
>>> > steady
>>> > > RPI. The values extracted from the audio-domain should be
>>sent to
>>> > > GNURADIO-COMPANION to transmit some signals via HackRF one
>in
>>the
>>> very
>>> > > same frequency range which is detected by RPI("A").
>>> > >
>>> > > - the idea is to build a close circuit of information
>>generation,
>>> > which
>>> > > should be modulated over time and ever-changing, due to the
>>> conversion
>>> > > of values between the domains radio/audio, and to the
>>implication
>>> > of the
>>> > > room acoustic response analyzed and encoded to interfere in
>>the
>>> > > radiowaves domain.
>>> > >
>>> > > The suggestion of this idea comes from the works of Agostino
>>Di
>>> Scipio
>>> > > "Audible Ecosystemics" (2000-2005) which develop very deeply
>>> feedback
>>> > > network processes based in the pure audio/acoustic domain.
>My
>>> > purpose is
>>> > > to try to do something similar in a cross-domain set
>>(Radio/Audio
>>> > > through Sonification and Dsp treatments)
>>> > > thank you very much for your kind attention and help,
>>> > >
>>> > > best
>>> > >
>>> > > Stefano Zorzanello
>>> > >
>>> >
>>> >
>>>
>>>
>>>
[Attachment #3 (text/html)]
<html><head></head><body style="zoom: 0%;"><div dir="auto">Yes, just hackRF One \
plugged into the RPI...<br><br></div> <div dir="auto"><!-- tmjah_g_1299s -->===<!-- \
tmjah_g_1299e --><br></div> <div dir="auto"><!-- tmjah_g_1299s -->Sent from my mind, \
some fingers and electronics helped.<!-- tmjah_g_1299e --></div> <div \
class="gmail_quote" >Il giorno 13 feb 2021, alle ore 23:13, Fabian Schwartau <<a \
href="mailto:fabian@opencode.eu" target="_blank">fabian@opencode.eu</a>> ha \
scritto:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; \
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> You are welcome :)
<br>I can't actually explain why it is working with the hackrf argument. If you have \
only one sdr connected, it should work without it. <br>Anyway, I'm glad it works now.
<br>
<br>
<div class="gmail_quote">
Am 13. Februar 2021 22:54:32 MEZ schrieb Stefano Zorzanello \
<stefanozorzanello@gmail.com>: <blockquote class="gmail_quote" style="margin: \
0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> \
<div dir="ltr"> <div dir="ltr">
<div dir="ltr">
<div dir="ltr">
please apologize, I didn't realize to have replied just to you.
</div>
<div dir="ltr">
<br>
</div>
<div>
about hackrf recognition, this is the terminal report:
</div>
<div>
<br>
</div>
<div>
- - - -
</div>
<div>
<br>
</div>
<div>
$ hackrf_info
<br>Found HackRF board 0:
<br>USB descriptor string: 0000000000000000088869dc3326571b
<br>Board ID Number: 2 (HackRF One)
<br>Firmware Version: 2017.02.1
<br>Part ID Number: 0xa000cb3c 0x005d4f64
<br>Serial Number: 0x00000000 0x00000000 0x088869dc 0x3326571b
<br>
</div>
<div>
<br>
</div>
<div>
- - - -
</div>
<div dir="ltr">
<br>
</div>
<div>
in GRC after an initial alert window
</div>
<div>
"The xterm executable '' is missing.
<br>You can change this setting in your gnuradio.conf, in section [grc], \
'xterm_executable'. <br>(This message is shown only once)"
<br>
</div>
<div dir="ltr">
<br>
</div>
<div dir="ltr">
I have change the permissions of grc.conf to set the file like this:
<br>
</div>
<div dir="ltr">
<br>
</div>
<div dir="ltr">
<div>
xterm_executable = /usr/bin/xterm
<br>
</div>
<div>
<br>
</div>
<div>
after this change the alert hasn't appeared anymore.
</div>
<div>
<b><br></b>
</div>
<div>
<b>And finally adding "hackrf" in the device argument in osmocom source did \
the trick! </b> </div>
<div>
<br>
</div>
<div>
So I thank you very much, you could not believe but I spent a couple of week \
about this silly thing, beating my head on the wall (with the risk to break at least \
one of the two) </div>
<div>
<br>
</div>
<div>
So it's quite likely that I'll be back with other newbie issues... but in the \
meantime I thank you very much for your support, </div>
<div>
all best
</div>
<div>
Stefano
</div>
<div></div>
<div>
<br>
</div>
<div>
<br>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
Il giorno sab 13 feb 2021 alle ore 20:47 Fabian Schwartau <
<a href="mailto:fabian@opencode.eu" target="_blank">fabian@opencode.eu</a>> ha \
scritto: <br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"> Hi Stefano,
<br>
<br> we should stay on the mailing list, so everyone can follow and contribute.
<br> Are you sure there are not other messages? Because those below are no
<br> error messages, just a warning and a bit of information, nothing to
<br> really worry about.
<br> One common problem (which I did not have) is missing permission on the
<br> hackrf. But then you should get an error message telling that he was not
<br> able to access the hackrf. Can you send the complete output of the
<br> program? Also try running it with sudo to check if it is a permission issue.
<br> Do you have multiple SDRs (you said something about an rtl-sdr?)
<br> attached to the Pi? Try adding "hackrf" (without the quotes) to the
<br> device arguments in the osmocom source.
<br> Also try hackrf_info in a terminal to see if the hackrf is detected
<br> properly. You can also try osmocom_siggen or osmocom_spectrum_sense and
<br> see if you can access the hackrf.
<br> What if you replace the osmocom source with a random source (also add a
<br> throttle block to limit cpu usage)? Does it work?
<br> Just to make sure: You are running a graphical environment and starting
<br> the script from there, not an ssh connection?
<br>
<br> Best regards,
<br> Fabian
<br>
<br> Am 13.02.21 um 19:25 schrieb Stefano Zorzanello:
<br> > Hi Fabian, thank you very much for your reply.
<br> >
<br> > I'm using RPI 3b, with Debian 9.13.
<br> > I have just installed gnuradio-companion 3.7.10 again following the
<br> > terminal commands you wrote me
<br> >
<br> > $ sudo apt install gnuradio gr-osmosdr hackrf
<br> >
<br> > the software installation went fine but as I run the flowgraph I get no
<br> > window displaying any signal, and the same error message
<br> >
<br> > - - -
<br> > Warning: failed to XInitThreads()
<br> > linux; GNU C++ version 6.2.0 20161010; Boost_106100;
<br> > UHD_003.009.005-0-unknown
<br> >
<br> > gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10
<br> > built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf
<br> > bladerf rfspace airspy soapy redpitaya
<br> >
<br> > - - -
<br> > any other idea to make it working?
<br> > thanks again,
<br> > best regards
<br> >
<br> > Stefano
<br> >
<br> > Il giorno sab 13 feb 2021 alle ore 17:26 Fabian Schwartau
<br> > <
<a href="mailto:fabian@opencode.eu" target="_blank">fabian@opencode.eu</a> \
<mailto: <a href="mailto:fabian@opencode.eu" \
target="_blank">fabian@opencode.eu</a>>> ha scritto: <br> >
<br> > Hi Stefano,
<br> >
<br> > don't worry asking such questions here on the list. \
That's its purpose I <br> > guess ;)
<br> > First of all: I was able to run both of your \
flowgraphs on my PC with a <br> > HackRF One, so the problem \
lies somewhere else. <br> > A small google search reavealed no \
perfect solution, but it indicated <br> > that something may \
be wrong with your installation. Like gnuradio was <br> > \
build against a certain library version but you are using a <br> > \
different one. <br> > How did you install \
gnuradio on the Pi? What Pi is it exactly? An <br> > original \
Pi 1 (A/B)? You may have trouble feeding 10 Msps though that <br> > \
old hardware. But it should start anyway. <br> > What OS \
are you using? Which version? <br> > I would recommend \
installing gnuradio from the distro repositories using <br> > \
apt. If you did so, a very simple solution may be to try a different <br> \
> distribution (or version), like Raspi OS (Raspbian), Ubuntu, \
Arch, ... <br> > there are many for the Pi. This will likely \
be a straight forward <br> > workaround for your problem.
<br> > Nevertheless, I just tried it on one of my Pi 3 with \
a fairly clean and <br> > up-to-date Raspi OS. I installed the \
following stuff: <br> > $ sudo apt install gnuradio gr-osmosdr \
hackrf <br> > And both of your flow graphs worked like a charm \
with that. <br> >
<br> > If you have any further questions, feel free to ask \
them :) <br> >
<br> > Hope I could help,
<br> > Fabian
<br> >
<br> >
<br> > Am 13.02.21 um 15:04 schrieb Stefano Zorzanello:
<br> > > Dear list members,
<br> > >
<br> > > I'm sorry to bother you with the classic newbie \
stuff, but I'm stuck - <br> > > since some days (the \
solutions found on the web didn't work for <br> > me) - to
<br> > > this point:
<br> > >
<br> > > - gnuradio-companion RaspberryPi 3b + hackRF \
one with a very simple <br> > > blocks flow doesn't display \
any signal window; <br> > > and the error message I get is \
the following one: <br> > >
<br> > > - - - -
<br> > >
<br> > > Warning: failed toXInitThreads()linux; GNU \
C++version 6.2.0 20161010; <br> > > Boost_106100; \
UHD_003.009.005-0-unknowngr-osmosdr 0.1.4(0.1.4) <br> > \
gnuradio <br> > > 3.7.10built-in sourcetypes: file \
osmosdr fcd rtl rtl_tcp uhd miri <br> > hackrf
<br> > > bladerf rfspaceairspy soapy redpitaya *** Error \
in`/usr/bin/python': <br> > > corrupted double-linked list: \
0x01a81c08 *** <br> > >
<br> > > - - - -
<br> > >
<br> > > I'm trying to follow some very nice youtube \
tutorial (Ossman, Hackaday <br> > > etc. ) but I cannot \
proceed if I can't neither make grc working with a <br> > > \
simple sketch. <br> > >
<br> > > Any help is greatly appreciated.
<br> > >
<br> > > More, if you have any suggestion or advice, \
here it follows a general <br> > > description of the \
process I want to develop for my sound-art / sdr <br> > > \
based installation. <br> > >
<br> > > The set up should be as follows:
<br> > >
<br> > > - a small robot(flor hover type) moves randomly \
in a restricted area <br> > > (few sq meters)of a big room.
<br> > > On this device, an RPI("A") + [DVB-T+DAB+FM] \
usb dongle, <br> > > battery-powered, is mounted to detect \
some RF activity in some rf <br> > range.
<br> > > Some values should be extracted (intensity over \
time of a particular <br> > > freq // and intensity of \
shifting detected frequencies). The movements <br> > > of \
the robot in the room should cause different detected values. <br> > \
> <br> > > - these values should be shared or sent \
in real-time to an external <br> > > software (PureData) \
that sends these values via OSC to another <br> > RPI("B"),
<br> > > which is steady, that will use the incoming \
values as a control signal <br> > > for some audio \
DSP-treatments (sampling and granulation). The raw <br> > \
audio <br> > > material for dsp audio treatments will \
be just RF noise.- The audio <br> > > treatments will be \
played inside the room via loudspeakers. <br> > >
<br> > > - through a microphone and dsp, the live audio \
stream will be analyzed <br> > > in PureData (intensity and \
spectrum-centroid) in real-time by the <br> > steady
<br> > > RPI. The values extracted from the audio-domain \
should be sent to <br> > > GNURADIO-COMPANION to transmit \
some signals via HackRF one in the very <br> > > same \
frequency range which is detected by RPI("A"). <br> > >
<br> > > - the idea is to build a close circuit of \
information generation, <br> > which
<br> > > should be modulated over time and \
ever-changing, due to the conversion <br> > > of values \
between the domains radio/audio, and to the implication <br> > \
of the <br> > > room acoustic response analyzed and \
encoded to interfere in the <br> > > radiowaves domain.
<br> > >
<br> > > The suggestion of this idea comes from the \
works of Agostino Di Scipio <br> > > "Audible Ecosystemics" \
(2000-2005) which develop very deeply feedback <br> > > \
network processes based in the pure audio/acoustic domain. My <br> > \
purpose is <br> > > to try to do something similar in \
a cross-domain set (Radio/Audio <br> > > through \
Sonification and Dsp treatments) <br> > > thank you very \
much for your kind attention and help, <br> > >
<br> > > best
<br> > >
<br> > > Stefano Zorzanello
<br> > >
<br> >
<br> >
<br>
<br>
<br>
</blockquote>
</div>
</blockquote>
</div></blockquote></div></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic