Re: [Discuss-gnuradio] Integration of python's time.time() and work() calls

2015-05-29 Thread Marcus Müller
Hi Anil, On 05/29/2015 04:29 AM, Anil Kumar Yerrapragada wrote: > >>Or is there a way to make sure that the in-buffer gets updated > multiple times within the same work call? > > Will placing the work function inside a while 1 do the trick? Never do that. Your job as GR user is to write the work()

[Discuss-gnuradio] can't install gnuradio 3.7.7.1 and newest UHD

2015-05-29 Thread Nemanja Savic
Hi all, I am stil using gnuradio 3.6.5.1 and yesterday I wanted to install newest version of both gnuradio and UHD driver. I wanted to install them on some different path and to preserve working environment until I am sure that newcomers work. First I downloaded and built UHD. I followed instruct

[Discuss-gnuradio] What if noutput_itmes is too short?

2015-05-29 Thread Jeon
I am trying to remove `preamble` and `start frame delimiter` from a frame and only the payload will be passed to the next block. While in debugging, `ninput_items` is 7742, and `noutput_items` is 4096, for instance. An offset where the frame starts is 790. Simple calculation gives me that 7742 -

Re: [Discuss-gnuradio] What if noutput_itmes is too short?

2015-05-29 Thread Jeon
After posting the previous thread, I've searched APIs from GNU Radio doxygen. Several candidates have been found. 1. [`produce()`]( http://gnuradio.org/doc/doxygen/classgr_1_1block.html#aa5581727d057bdd8113f8b2a3fc5bd66 ) 2. [`set_min_noutput_items()`]( http://gnuradio.org/doc/doxygen/classgr_1_1

Re: [Discuss-gnuradio] What if noutput_itmes is too short?

2015-05-29 Thread Marcus Müller
Hi Jeon, On 05/29/2015 01:46 PM, Jeon wrote: > I am trying to remove `preamble` and `start frame delimiter` from a > frame and only the payload will be passed to the next block. > > While in debugging, `ninput_items` is 7742, and `noutput_items` is > 4096, for instance. An offset where the frame

Re: [Discuss-gnuradio] GRC Reacting Slowly

2015-05-29 Thread Andreas Ladanyi
Hi Murray, thats an interesting fact. My project has a lot (i didnt count them) of blocks. I have the same delay problem on my PC and on my embedded device. On the embedded device its slower than on my pc :-) If i use only a few blocks than the delay is short. So i think your theory and su

Re: [Discuss-gnuradio] SDRA, Programme complete

2015-05-29 Thread Iluta V
Thank you very much, Markus, for your update on SDRA programme. I look forward to coming! Hopefully you would know how to get to Friedrichshafen. Would it be better to fly to Liechtenstein or Switzerland (Zurich) if there is reliable transport or still to Munich (though it looks 3x further away th

Re: [Discuss-gnuradio] GRC Reacting Slowly

2015-05-29 Thread Koslowski, Sebastian (CEL)
Hey, so, I timed the flowgrah update steps rewrite, validate, create labels, create shapes and it turns out most time is actually spent in validate. However, for some reason the validate step currently performs the evaluation of the params and this is also where it spends almost all of its time. S

Re: [Discuss-gnuradio] SDRA, Programme complete

2015-05-29 Thread Marcus Müller
Hi Iluta, over German Railroad (Deutsche Bahn)'s website www.bahn.de you can plan and book train tickets from both München and Zürich Flughafen (==airport); just checked, takes about two hours and 30 € to get from Zurich airport to Friedrichshafen Stadt. If you get a connection including a transpo

Re: [Discuss-gnuradio] SDRA, Programme complete

2015-05-29 Thread Iluta V
Dear Marcus, Thanks a lot! Switzerland and Zurich airport with a travel over the lake sound excellent! Good reminder to stay away from Frankfurt. Actually I've been to all Frankfurt airports (FRA, ZFR, HHN), and depending on purpose of travel all of these airports are very good! google.com/flight

Re: [Discuss-gnuradio] What if noutput_itmes is too short?

2015-05-29 Thread Jeon
Thank you for your reply, Marcus. Now I'm getting a little bit more. As I understand, if I consume(0, n), where n is less than ninput_items, then only n samples at the front of input_items[] are consumed and unconsumed part remains. And then, at the next call of general_work(), incoming samples a

[Discuss-gnuradio] Diagnosing the cause of D's

2015-05-29 Thread Richard Bell
Hi all, I need some help determining the cause of D's being displayed from my N210 device. I know it means GNU Radio is not consuming the samples from my laptops Ethernet socket buffer fast enough, causing the USRP to overflow it. What I would like to do now, is learn how to monitor performance s

Re: [Discuss-gnuradio] Diagnosing the cause of D's

2015-05-29 Thread Johnathan Corgan
On Fri, May 29, 2015 at 9:07 AM, Richard Bell wrote: > What I would like to do now, is learn how to monitor performance such that > I can figure out which part of my receiver is the bottleneck, so I can > focus on optimizations there. I can't lower the sample rate anymore, > because I'm already

[Discuss-gnuradio] Wire format: using 8-bit (sc8) vs using 16-bit (sc16) resolution to gnu radio

2015-05-29 Thread Nick Kara
Hi, i am using usrp N200 and i set to gnu radio the wire format as either 16-bit -> sc16 or 8-bit ->sc8 and host format fc32(complex float) when i use a) sc16 the power in the window where i see the spectrum is at -110 dB or -100 dB, without transmitter sending data (so i see only noise) b) sc8 the

Re: [Discuss-gnuradio] Wire format: using 8-bit (sc8) vs using 16-bit (sc16) resolution to gnu radio

2015-05-29 Thread Martin Braun
On 29.05.2015 12:53, Nick Kara wrote: > Hi, i am using usrp N200 and i set to gnu radio the wire format as > either 16-bit -> sc16 > or 8-bit ->sc8 and host format fc32(complex float) when i use > a) sc16 the power in the window where i see the spectrum is at -110 dB > or -100 dB, without transmitt

Re: [Discuss-gnuradio] What if noutput_itmes is too short?

2015-05-29 Thread Marcus Müller
Hi Jeon, On 05/29/2015 05:25 PM, Jeon wrote: > As I understand, if I consume(0, n), where n is less than > ninput_items, then only n samples at the front of input_items[] are > consumed and unconsumed part remains. And then, at the next call of > general_work(), incoming samples are appended at th

Re: [Discuss-gnuradio] Diagnosing the cause of D's

2015-05-29 Thread Marcus Müller
Hi Richard, 320kS is not the minimal rate; if I'm not mistaken it's 100MHz/512. Ds are relatively serious, and I've rarely seen them: The typical "your system is too slow" results in "O"verflows; typically, you see "D" if UHD starts wondering where the sample packet n disappeared to, after receiv

Re: [Discuss-gnuradio] Diagnosing the cause of D's

2015-05-29 Thread Marcus D. Leech
On 05/29/2015 02:13 PM, Marcus Müller wrote: Hi Richard, 320kS is not the minimal rate; if I'm not mistaken it's 100MHz/512. Ds are relatively serious, and I've rarely seen them: The typical "your system is too slow" results in "O"verflows; typically, you see "D" if UHD starts wondering where

Re: [Discuss-gnuradio] Integration of python's time.time() and work() calls

2015-05-29 Thread Anil Kumar Yerrapragada
Hi Marcus, Thanks for the explanation, it is very clear. But is there a way to keep track of time elapsed across *consecutive* work calls? Like I said in the first post in this thread, if I have a sliding window based energy detect. Samples keep coming in, but at some point I will have to say, r

Re: [Discuss-gnuradio] Integration of python's time.time() and work() calls

2015-05-29 Thread Marcus Müller
Hi Anil, On 05/29/2015 09:07 PM, Anil Kumar Yerrapragada wrote: > Hi Marcus, > > Thanks for the explanation, it is very clear. > > But is there a way to keep track of time elapsed across *consecutive* > work calls? well, you have the nitems_read() method, which, assuming you have a constant samp

[Discuss-gnuradio] Problem with volk and fftw memory alignment

2015-05-29 Thread djch-gnuradio
I've been trying out the (bleeding edge) corr_est() code and the test_corr_est.grc sometimes segvs. Not repeatable, won't crash under gdb :-) From a core file, it's crashing loading the first element of aVector in volk_32fc_x2_multiply_32fc_a_avx instruction is vmovaps (%eax),%ymm1where eax

Re: [Discuss-gnuradio] How to start and stop recording without exiting the flowgraph

2015-05-29 Thread Murray Thomson
Hi, I tried to follow Carl's suggestion to record a wav file but it didn't work for me. The first time I change the check box the wav file sink will stop working forever. File sinks works fine. Will Martin's suggestion work for wav files or does anyone have another suggestion to record wav files o

Re: [Discuss-gnuradio] Integration of python's time.time() and work() calls

2015-05-29 Thread Anil Kumar Yerrapragada
Hi Marcus, Thank you for your patient replies. Last question. >>Your block is asked "I'd like to ask you to produce 512 items. How much input do you need?". >>If your block then says "I need 400 items", This means that for the block to output 512 items it needs 400 items in the input. >>no matt

Re: [Discuss-gnuradio] What if noutput_itmes is too short?

2015-05-29 Thread Sylvain Munaut
Hi, > As I understand, if I consume(0, n), where n is less than ninput_items, then > only n samples at the front of input_items[] are consumed and unconsumed > part remains. And then, at the next call of general_work(), incoming samples > are appended at the end of input_item[]. Is this right? > >