Re: [Discuss-gnuradio] usrp_spectrum_sense.py raw iq samples

2017-01-04 Thread Mallesham Dasari
Hi Julian, Thank you so much again. I am able to collect the raw IQ samples using USRP source and File sink with gnuradio-companion. But, I am confused why you said that I will run into additional problems. On Wed, Jan 4, 2017 at 12:22 PM, Mallesham Dasari wrote: > Hi Julian, > > Thank you so m

Re: [Discuss-gnuradio] Tune Requests

2017-01-04 Thread mleech
http://files.ettus.com/manual/structuhd_1_1tune__request__t.html Should help On 2017-01-04 12:37, Sean Horton wrote: > I have my flowgraph set up so that parameters such as rx and tx frequencies > can be changed while running, and it's being sent two frequencies to listen > to, freq1 and fre

[Discuss-gnuradio] Tune Requests

2017-01-04 Thread Sean Horton
I have my flowgraph set up so that parameters such as rx and tx frequencies can be changed while running, and it's being sent two frequencies to listen to, freq1 and freq2, and the idea is that if there are two frequencies, to set the frequency to (freq1 + freq2) / 2, but the fft shows that one of

Re: [Discuss-gnuradio] usrp_spectrum_sense.py raw iq samples

2017-01-04 Thread Mallesham Dasari
Hi Julian, Thank you so much for the response. By whole WiFi band, I mean from 2.401G to 2.473G, which is complete WiFi band. Is it possible to sweep entire band by using the approach you mentioned? I thought using gnuradio-companion, we can scan only one or few channels depending on the sample ra

Re: [Discuss-gnuradio] How to "kill flowgraph" with a custom block

2017-01-04 Thread David Kersh
Ah! Thank you so much Marcus! I've managed to transplant this correction into my bigger flow graph and now everything works as intended. >You're using a hard-coded port of 58 in your server. That probably means you're running GNU Radio as root (because classically, normal users can't bind to socke

Re: [Discuss-gnuradio] How to "kill flowgraph" with a custom block

2017-01-04 Thread Marcus Müller
Well, don't have that buffer in the first place, then. Instead, write a block with no stream in- and no stream outputs, and have it emit a "stop" message to the "system" message port of any existing block within your flow graph, e.g. the vector sink. The QT Gui should die by itself once you use an

Re: [Discuss-gnuradio] How to "kill flowgraph" with a custom block

2017-01-04 Thread Marcus Müller
Dear David, using your gr-research OOT, I was able to notice the following: It shuts down just fine! A few notes: * You're using the Qt GUI build mode, which gives you a GUI window. That GUI thread then lingers. As soon as you change your build mode to "No GUI"/"Run To Completion" in the option

Re: [Discuss-gnuradio] reg:GNUradio build - gr-trellis module

2017-01-04 Thread Bastian Bloessl
Hi, glad it worked. Maybe it's good enough the have it archived on the mailing list. I guess, if at all, people will find it through Google. Best, Bastian Am 04.01.2017 um 12:18 schrieb Oleg Kokorin: hello Bastian it works. thanks a lot. do you think it maybe worth to add to the compilation

Re: [Discuss-gnuradio] reg:GNUradio build - gr-trellis module

2017-01-04 Thread Oleg Kokorin
hello Bastian it works. thanks a lot. do you think it maybe worth to add to the compilation wiki somewhere? thanks Oleg   Sent: Tuesday, January 03, 2017 at 7:22 PM From: "Bastian Bloessl" To: "Oleg Kokorin" , discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] reg:GNUradio build - gr-trelli

Re: [Discuss-gnuradio] How to "kill flowgraph" with a custom block

2017-01-04 Thread Marcus Müller
Hi David, did you write these blocks "free-standing" or generated them from with in an OOT with gr_modtool? Really, I want to locally reproduce your problem, but I'm not overly eager to first manually fiddle your xml files into my system, place the python files in a directory where python looks f

Re: [Discuss-gnuradio] How to "kill flowgraph" with a custom block

2017-01-04 Thread Marcus Müller
Can you really share your whole Out-Of-Tree module including an example .grc or python flow graph? Best regards, Marcus On 04.01.2017 10:53, David Kersh wrote: > Hi Marcus, > > The 'stop' comparison definitely triggers as the appropriate text is > printed to the GRC console. > > I think you're

Re: [Discuss-gnuradio] [Bulk] Re: How to "kill flowgraph" with a custom block

2017-01-04 Thread davidk
Dear Gisle, thank you for the reply. I'm pretty sure my UDP server code works as intended since it's mainly cherry picked from https://wiki.python.org/moin/UdpCommunication and some other code I have worked on, independent from GNURadio. I think maybe the fact my UDPBroadcast block has had its in

Re: [Discuss-gnuradio] How to "kill flowgraph" with a custom block

2017-01-04 Thread davidk
///Not sure if I replied correctly/// Hi Marcus, The 'stop' comparison definitely triggers as the appropriate text is printed to the GRC console. I think you're right about my UDP broadcaster. I want it to be one of those types of blocks similar to the two default blocks in a flowgraph: Options

Re: [Discuss-gnuradio] usrp_spectrum_sense.py raw iq samples

2017-01-04 Thread Julian Arnold
Hi Mallesham, the easiest way would probably be to create your own simple flowgraph using GRC like so: |-| |-| | USRP Source | --> | File Sink | |-| |-| However, remember tha