Thanks, Tim!
I tried to install gr-eventstream with the last GR version and had problems
with cmake. I only had success after using the same cmake parameters I used
building GR.
Nevertheless, I made a drop-in replacement of my block with ES Source and I
was unable to mimic the previous behavior.
You may want to look at gr-eventstream source block, this is exactly what
it is intended to do, precisely timed if desired
On Mon, Nov 30, 2015, 2:38 PM Francisco Albani
wrote:
> Hi to all.
>
> (this email subject may be inaccurate)
>
> I need a block with the
Today I finally wrote the first working version.
I will be very grateful if you take a look and tell me if you find anything
wrong.
Highlighted code: http://pastebin.com/4fKmHgfE
Thanks and bye!
Raw code:
import numpy
import pmt
from gnuradio import gr
class AsyncMsgSourceC(gr.sync_block):
I'm a bit curious as to why you'd need a forecast that returns 0 --
basically, there's no input stream, so I'm not quite sure forecast
return values make a difference.
Like Tom, I see a bit of a problem with this:
1. from a stream perspective, this is a simple source. Sources should
block
On Mon, Nov 30, 2015 at 2:37 PM, Francisco Albani <
francisco.alb...@gmail.com> wrote:
> Hi to all.
>
> (this email subject may be inaccurate)
>
> I need a block with the following characteristics:
>
> * Input port for messages.
> * Output port for complex/float/byte/etc. stream.
> * Forecast
Hi to all.
(this email subject may be inaccurate)
I need a block with the following characteristics:
* Input port for messages.
* Output port for complex/float/byte/etc. stream.
* Forecast always answers 0.
* Work function first check the message queue. If there are no messages,
emits zeros; if