[Discuss-gnuradio] Timer-Chronometer

2017-09-27 Thread Ali
Hi to all, I have a USRP and I am writing the outputs via file sink. I want to see how much time has passed since the begining so that I can stop recording at any time I want. In other words, I want a chronometer in my GRC. It doesn't have to show miliseconds, it is enough to see seconds. What is

Re: [Discuss-gnuradio] Matplotlib and GNU Radio: Dynamic plot

2017-09-27 Thread Ali
Hi to all, For those who are interested in, the approach in the following link seems to be useful. I tried for my case, and it is working fine. http://recolog.blogspot.com.tr/2015/08/processing-data-out-of-gnuradio.html Thanks, Ali 2017-09-21 20:04 GMT+03:00 Marcus Müller : > Interesting! > >

Re: [Discuss-gnuradio] Sample rate block in GNU radio

2017-09-27 Thread abhilash b
Hello all, I am new to GNU radio and I have one basic query. Suppose I am having 10 samples and I set sample rate at 20MHz with repeat option ON (assuming my hardware supports this bandwidth). Is that means my samples first gets repeated 20M samples and gets transmitted at once? -- -Regards Ab

Re: [Discuss-gnuradio] Custom OFDM Carrier Allocator block

2017-09-27 Thread Michael Dickens
HI Alice - When you edited the XML file, did you change the "key", "category", "import", or "make" parts? For example, if I were to make a copy of "ofdm_sync_sc_cfb" into an OOT called "FOO", then I'd need to do the following for it to not be a duplicate of the original: {{{ FOO_ofdm_sync_sc_cfb

Re: [Discuss-gnuradio] [USRP-users] Audio Control loop testing

2017-09-27 Thread Benny Alexandar
>>Could you maybe elaborate how you're planning to solve all a),b),c) instead >>of asking for new feedback? For a) & b) will use the sound card clock and using micro seconds timer. And for c) run the decoded PCM through a FIFO buffer this is a local buffer which is not part of gnu-radio connec

[Discuss-gnuradio] GR-SQL Now Directly Supports HackRF/RTL Recordings

2017-09-27 Thread GhostOp14
Hi everyone, I added two new capabilities to the GR-SQL module, both based on command-line recordings directly from a HackRF using hackrf_transfer -r or with rtl_sdr. HackRF produces signed 8-bit samples and rtl_sdr produces unsigned 8-bit samples which need to be converted before using directly

Re: [Discuss-gnuradio] Specify taps for 'FFT_Filter' using function call to 'GLFSR Source'

2017-09-27 Thread Marcus Müller
Hi Cinaed, interestingly, period() gives me 0b(degree ones) all the time, so I'm not sure we don't see a bug there. Best regards, Marcus On 09/27/2017 12:01 AM, Cinaed Simson wrote: > Try > > from gnuradio import digital as digital > src=digital.glfsr_source_f(13,False,0x100D,0xA5A5) >

Re: [Discuss-gnuradio] [USRP-users] Audio Control loop testing

2017-09-27 Thread Marcus Müller
And as also said earlier, I don't believe very much that it will work that easily, since the CPU clock is a) worse than the typical SDR and sound card clocks, b) has different resolutions, c) and needs to still be sufficiently interpolatable for the jittery, variable-workload-length that GNU Radio

Re: [Discuss-gnuradio] Specify taps for 'FFT_Filter' using function call to 'GLFSR Source'

2017-09-27 Thread Cinaed Simson
Try from gnuradio import digital as digital src=digital.glfsr_source_f(13,False,0x100D,0xA5A5) src.period() src has type Unfortunately, I don't know enough to be able to convert to an array of floats need for filter taps. -- Cinaed On 09/26/2017 05:45 PM, Chad Spooner wrote: > All:

Re: [Discuss-gnuradio] Specify taps for 'FFT_Filter' using function call to 'GLFSR Source'

2017-09-27 Thread Marcus Müller
Hi Chad! So, yeah, it seems we forgot to wrap the raw C++ GLFSR with SWIG, so that it's not directly available in Python-land. So, this[1] fixes that. You'd use it like this: * have an import Block, "from gnuradio import digital" * Have a variable with id "taps_gen" (or so), value "digital.glfsr