[Discuss-gnuradio] Peak_Detector2 stalls simulation

2015-01-02 Thread Ludwig Stephan (CR/AEH4)
Hello and Season's Greetings, I am experiencing a problem with the blocks::peak_detector2 block. The simulation stalls after some time. My conjecture is that this is due to the kind the block handles its output in work(), but I am not sure, since I am not that deep into the scheduler. I am

Re: [Discuss-gnuradio] Question on threshold mathematics in correlate_and_sync block

2015-01-02 Thread Andy Walls
On Wed, 2014-12-31 at 15:48 -0500, Andy Walls wrote: On Wed, 2014-12-31 at 14:00 -0500, Andy Walls wrote: Hi. Can someone give me a brief clue about the threshold testing in the correlate_and_sync block? I found my answer in this post:

Re: [Discuss-gnuradio] Question on threshold mathematics in correlate_and_sync block

2015-01-02 Thread Tom Rondeau
On Fri, Jan 2, 2015 at 8:57 AM, Andy Walls a...@silverblocksystems.net wrote: On Wed, 2014-12-31 at 15:48 -0500, Andy Walls wrote: On Wed, 2014-12-31 at 14:00 -0500, Andy Walls wrote: Hi. Can someone give me a brief clue about the threshold testing in the correlate_and_sync block?

Re: [Discuss-gnuradio] Question on threshold mathematics in correlate_and_sync block

2015-01-02 Thread Nick Foster
Hi Tom, Andy, Thanks for the reports and details. I can definitely see the problem with the situation you're describing. We obviously weren't considering that case when we designed the block. We were really expecting any preamble/access code that we were using would have good

Re: [Discuss-gnuradio] Question on threshold mathematics in correlate_and_sync block

2015-01-02 Thread Andy Walls
On Fri, 2015-01-02 at 09:56 -0800, Nick Foster wrote: There is another problem which prevents proper correlation: the end of work coming mid-burst. See the attached End of work mid-corr.png which shows an end of work tag with the value of

[Discuss-gnuradio] Peak_Detector2 stalls simulation

2015-01-02 Thread Achilleas Anastasopoulos
Stephan, We have worked with this block and realized it has a bug (not just an inefficient functionality). This is easy to see if you consider what happens when the first time work is called, the threshold is passed, a peak is found in item i and so d_peak_ind is set to i, but there are less

Re: [Discuss-gnuradio] Getting time each time power squelch is on

2015-01-02 Thread Dan CaJacob
Hi Luis, I am pretty certain there is a block in mainline GR to do this with tagging. Burst tagger maybe? The tags define the burst boundaries and a timestamp is recorded as well. On Jan 2, 2015 5:46 PM, Luis Colunga lccolung...@gmail.com wrote: Hello, I have a Python handcoded block in

[Discuss-gnuradio] Getting time each time power squelch is on

2015-01-02 Thread Luis Colunga
Hello, I have a Python handcoded block in which I want every time that power squelch is triggered, grab the actual time and then use that filename to write a wav file with a decoded stream. What would be a good approach? I tried using variables but I see they don't update at runtime and I am not

[Discuss-gnuradio] optional port in grc block

2015-01-02 Thread Achilleas Anastasopoulos
Hi all, I would like to have grc block with a bool option Debug. Once this is set to True, then I would like to have an additional output port. How do I do that? I already added this part in the xml file: param nameDebug/name keydebug/key