Hi
I am using the ezcap RTL2838U USB dongle along with gnuradio 3.6.0 and
the svn latest version of Multimode.py on Debian Linux 6.0.2. I have
installed the HEAD git branches of rtl-sdr, gr-osmosdr and libosmocore
successfully. I have taken care of all pre-requisites needed as well
as in the build-gnuradio script.
However when I try to run multimode.py as root I get the following
error:
root# ./multimode.py
linux; GNU C++ version 4.4.5; Boost_104200;
UHD_003.004.000-325-g7e296167
Using Volk machine: ssse3_64
Traceback (most recent call last):
File “./multimode.py”, line 1089, in
tb = multimode(ahw=options.ahw, freq=options.freq,
ppm=options.ppm, vol=options.vol, ftune=options.ftune,
xftune=options.xftune, srate=options.srate, upclo=options.upclo,
devinfo=options.devinfo, agc=options.agc, arate=options.arate,
upce=options.upce, mthresh=options.mthresh, dmode=options.dmode,
offs=options.offs, flist=options.flist, dfifo=options.dfifo,
mbw=options.mbw, deemph=options.deemph)
File “./multimode.py”, line 340, in init
self.wxgui_waterfallsink2_0.set_callback(wxgui_waterfallsink2_0_callback)
File
“/usr/local/lib/python2.6/dist-packages/gnuradio/gr/hier_block2.py”,
line 50, in getattr
return getattr(self._hb, name)
AttributeError: ‘gr_hier_block2_sptr’ object has no attribute
‘set_callback’
Please advise how to fix this error.
I have tried using gnuradio-companion on the multimode.grc file and I
got this error after I generated a new multimode.py file:
./multimode.py
linux; GNU C++ version 4.4.5; Boost_104200;
UHD_003.004.000-325-g7e296167
Using Volk machine: ssse3_64
gr-osmosdr supported device types: file fcd rtl rtl_tcp uhd
Using device #0: ezcap USB 2.0 DVB-T/DAB/FM dongle
Found Elonics E4000 tuner
Exact sample rate is: 1000000.026491 Hz
gr_fir_ccc: using SSE
gr_fir_fff: using SSE
The program ‘python’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadWindow (invalid Window parameter)’.
(Details: serial 617 error_code 3 request_code 137 minor_code 4)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
More details about my device:
rtl_test -t
Found 1 device(s):
0: ezcap USB 2.0 DVB-T/DAB/FM dongle
Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle
Found Elonics E4000 tuner
Supported gain values (18): -1.0 1.5 4.0 6.5 9.0 11.5 14.0 16.5 19.0
21.5 24.0 29.0 34.0 42.0 43.0 45.0 47.0 49.0
Benchmarking E4000 PLL…
[E4K] PLL not locked for 51000000 Hz!
[E4K] PLL not locked for 2179000000 Hz!
[E4K] PLL not locked for 1090000000 Hz!
[E4K] PLL not locked for 1250000000 Hz!
E4K range: 52 to 2178 MHz
E4K L-band gap: 1090 to 1250 MHz
Any help will be appreciated!
Thanks.
–Vikas