I’ve tried the two tones example, and it doesn’t work. By that I mean it seems the Python script it generates runs, then just returns without an error message or anything which makes sense to me.
Output:
LimeSuite Sink (TX) info
##################
Connecting to device
##################
Devices found: 1
##################
Device list:
Nr.:|0|device:|LimeSDR-USB, media=USB 3.0, module=STREAM, addr=1d50:6108,
serial=0009060B00123456
##################
Device number 0 from the list is used.
Estimated reference clock 30.7197 MHz
Reference clock 30.720 MHz
CGEN: Freq=80 MHz, VCO=2.56 GHz, INT=82, FRAC=349525, DIV_OUTCH_CGEN=15
M=156, N=3, Fvco=1040.000 MHz
16: 55 AD 2A
16: AB 5A 55
phase: min 31.2; max 197.3; selected 114.2)
M=156, N=3, Fvco=1040.000 MHz
M=156, N=3, Fvco=1040.000 MHz
16: C6 DC 37
16: AA 58 75
16: AA 5A D5
phase: min 15.6; max 171.3; selected 93.5)
M=156, N=3, Fvco=1040.000 MHz
##################
INFO: device_handler::enable_channels(): SISO CH0 set for device number 0.
INFO: device_handler::set_samp_rate(): CGEN: Freq=32 MHz, VCO=2.432 GHz, INT=78,
FRAC=174762,
DIV_OUTCH_CGEN=37
set sampling rate: 0.25 MS/s.
INFO: device_handler::set_rf_freq(): RF frequency set [TX]: 60 MHz.
INFO: device_handler::set_analog_filter():
>>> Done
I also tried the quick test, and don’t see anything for the RX test example. I also don’t have an o-scope, but have an Ettus USRP B200 tuned to the same frequency I’m trying to use for transmitting (920 MHz) with gnuradio.
Why are the controls and text labels on the LimeSuite so cryptic? I barely know what any of that gibberish means.
“Cryptic” messages are there because you are using debug build of LimeSuite. I assume you are using the newest version of gr-limesdr. Have you tried running two tones after upgrading LimeSuite?
I’m sure I wasn’t using a debug build of LimeSuite, since I don’t think there would be debug builds in the repository. I have not tried again to see if “two tones” works, but I did rebuild gr-limesdr once I upgraded LimeSuite. I still get the errors in the LimeQuickTest though.