Hello All,
I was hoping someone could help shed some light on why my LimeSDR becomes unfindable after use in GNURadio or osmocom’s command line tests. The command line test has been easier to get reproducible results. After calling osmocom_fft -s 8e6 -a “driver=lime,device=0”
I do get the spectral plot, but changing the sampling rate results in an error [Error] BEGIN DATA READING LIBUSB_ERROR_NO_DEVICE
. Attempting to run commands SoapySDRUtil –find or LimeUtil –find then continue to return no results, even after disconnecting and reconnecting the SDR to the computer. A restart of the computer solves the problem, so that has me thinking that a driver must be silently crashing on the computer.
I can reproduce the problem by starting at a sampling rate of 8MSPS and increasing to 10MSPS, or by starting at 10MSPS, decreasing to 8MSPS and then increasing again to 10MSPS.
I’m running Ubuntu 17.10 and I followed the instillation procedures for on the Lime Suite Quickstart Tutorial and then installed gr-osmosdr using sudo apt-get install gr-osmosdr
. I had gnu radio installed prior.
I’m still fairly new to this hardware so any help on further troubleshooting or solutions would be greatly appreciated. Thank you.