Gnuradio-companion & hamlib bodging

GNU Radio
1

Hi,

In gnuradio-companion, I’m tring to control my KX3 transceiver using
hamlib’s rigctl utility.

I’ve bodged a call to:
float(pexpect.run(“rigctl -m 229 -r /dev/ttyUSB0 -s 38400 f”))
in a variable block’s value, and then used that to set the wxgui
waterfall sink’s baseband frequency, which works but i’m trying to
figure out 2 more things.

  1. Can i do something similar to set the KX3’s vfo frequency? a similar
    command to rigctl can be used if i can bodge the call into Freq Set
    Varname somehow.

  2. Somehow i need to accommodate physical knobulation of the VFO on the
    radio, and keep the waterfall scale in sinc with the radio, i.e. by
    polling the same command i’ve used above. Is there any chance i can do
    that via similar bodging in gnuradio-companion, or, am I actually going
    to have to write actually write some code?

Cheers,

Darren, G0HWW

2

Never mind. I’ve bodged it directly in the generated python.

Darren

3

Hi again,

I’ve got my gnuradio ‘pan-adapter’ for my KX3 transceiver pretty much
working now: g0hww.blog: Gnuradio, hamlib and the KX3

but there seems to be a memory leak occurring when I call

self.wxgui_waterfallsink2_0.set_baseband_freq(self.rig_freq)

to update the waterfall’s baseband centre frequency with the result of
polling the transceiver (using pexpect with hamlib’s rigctl).

To be clear, the leak only occurs when set_baseband_freq() is called. if
that line is commented out, there is no leak.

Is this a known issue?

Cheers,

Darren

4

On Sun, Oct 28, 2012 at 5:36 PM, Darren L. [email protected]
wrote:

polling the transceiver (using pexpect with hamlib’s rigctl).

To be clear, the leak only occurs when set_baseband_freq() is called. if
that line is commented out, there is no leak.

Is this a known issue?

Cheers,

Darren

Hi Darren,

Great you got things working for you!

The wx stuff is all done in Python, so I’m surprised to hear of a
memory leak there. Can you confirm how big a leak it is?

Tom