Writing a Stand Alone Program Using GNURadio Blocks/Components
Müller, Marcus (CEL)
mueller at kit.edu
Tue Mar 5 07:27:38 UTC 2019
as much as I like this mailing list, I think discussions on how to
write GNU Radio blocks are best off on the GNU Radio mailing list.
GNU Radio has tutorials on how to write your own blocks, both for
blocks written in Python (simplicity) and in C++ (speed/system
programming); you can find them on .
How you communicate with your "app" depends on what that is – is it a
separate process continously running, can it be a thread in another
process, or could one understand it as library?
Generally, GNU Radio was (is) meant to be used as library that you can
use from within your program; you'd just call the right GNU Radio
functions from within your program to set up the flow graph, and then
tell GNU Radio to spawn of the processes to run that flow graph, and
then can interact with the signal processing / get the data it
produces. (GQRX is an example of such a programm.)
Whether that is easier for you than running a GNU Radio flow graph as a
separate process interchanging data with your app is hard to tell.
 discuss-gnuradio at gnu.org, sign up on
On Mon, 2019-03-04 at 22:05 -0600, P C wrote:
> I never heard about "zmq block or socket to pass" I will look into
> those methods.
> Something tells me I should go the route to write my own block but I
> don't know where to start.
> Would you have a link?
> Note, I don't want a block of samples to go to my app, what I want is
> each time the FIR filter spits out a sample I want to process it with
> my app.
> On 3/4/2019 4:38 PM, samuel verdon wrote:
> > Hello,
> > You can use a zmq block or socket to pass your data to your app or
> > if you want you can write your own block that pass your data to
> > your app via a callback method.
> > Sam
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6582 bytes
Desc: not available
More information about the osmocom-sdr