[Hamlib-developer] Re: Network Interface

[Matt E. <ma...@et...>]

I lost the original reply, so quoting may be difficult...


>Geeez, I can't believe it. Couple of months ago, when I saw gnuradio
> poping up on gnu.org, I thought, these guys will need a User Interface,
> and Hamlib would fit very well with their approach.

Great minds think alike :)

> All you need to do for gnuradio, is to create a new backend (let's call
> it "gnuradio"), and provide set_freq/get_freq, set_mode/get_mode methods
> and so on. In the set_freq method for example, just call the appropriate
> function of gnuradio and link the backend plugin against your library.

Maybe I can write a backend to send commands over IP.

> I guess gnuradio is a little more complex to run, like you need to have the
> control over a main loop to do the DSP stuff. But this can be worked out.
> Practically, you may end up with running gnuradio from rpc.rigd,
> to make it persistant and simplify threads, but the gnuradio *backend*
> won't have to know about RPC.

Like you say, gnuradio can't be a normal backend.  It needs to control its own
main loop.  I'll take a look at the WinRadio backend, maybe there are some ideas
there.

> Sorry I won't be able to play with gnuradio because I don't have a computer
> with PCI slots (laptop), but I'll give a look at the source code anyway
> so we can speak the same language, and help you writting the gnuradio backend.

A common misconception.  GNURadio works with many different ADC and DAC devices.
 Some of us are using those $1200 PCI cards, but this would never take off at
that price.  You can do a lot of interesting stuff with any old sound card which
is supported under linux (ALSA or OSS).  You can also just input from and output
to files.  No hardware necessary at all.

> It's going to be fun!

Yes it is.

Matt
N2MJI