[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] How to implement a Packet Sink Block as simple as
Re: [Discuss-gnuradio] How to implement a Packet Sink Block as simple as possible
Mon, 21 May 2012 12:31:59 -0700
Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
> I wonder whether there is a simpler way - without the need of a
> state-machine, queue and watcher thread. The only thing I practically
> need is to map the demodulated bits into frames (of variable length).
> I don't think a full blown packet stack should be necessary or a queue
> data structure.
> I'd be happy if someone had a fix or a workaround. I'm not sure
> whether there is a simpler solution though.
You may want to take a look at my GrExtras project. See readme for more
This gives you the ability to write blocks in python like any other
gnuradio block with a work function and all. Its probably a better way
to get access to streams in gnuradio rather than these hacky message
queues and python threads. Its using the schedulers own threads to call
into your implementation.
Also, it implements a message passing framework on top of the existing
stream tags interface. Again, no hack-around, its using the schedulers
own threads to call into your implementation.
I want to give this project a wiki page with a coding guide and a formal
announcement. In the meantime, take a look at some of the blocks in the
project as an example. I think the work in this project address some of
your issues from a framework perspective. Obviously, you still probably
have blocks to implement that are not part of GR.
or I'm just peddling my own crap :-)