LimeSDR - strange behaviour

SatNOGS Software
1

Hi all!

I have already used LimeSDR with the V2.1.2 without any problems. After setting up a new station, with the Lime, there are unexpected problems, I never experienced before.

The observation seems to run sucessfull, but the observation is marked black, “failed” and the audio and the waterfall only last a few seconds.

No problems at all with the sdr-stick on the same station. I only change device and antenna in the environment.

Any ideas appreciated!

stefan/oe6isp

The log:

initrigs4_dummy: _init called
rig_init: rig_model=Hamlib NET rigctl
rig_init: rx_range_list1 is empty, using rx_range_list2
rig_init: rig does not have tx_range!!
netrigctl_init version 20230106.0
[INFO] Make connection: ‘LimeSDR-USB [USB 3.0] 90726074D061D’
[INFO] Reference clock 30.72 MHz
[INFO] Device name: LimeSDR-USB
[INFO] Reference: 30.72 MHz
[INFO] LMS7002M register cache: Disabled
[INFO] RX LPF configured
[INFO] Rx calibration finished
netrigctl_close: done
netrigctl_close: done
INFO satnogsclient.radio.grsat Stopped gr_satellites
INFO satnogsclient.observer.observer Observation 14332434 finished.
INFO satnogsclient.scheduler.tasks Upload of waterfall image for observation 14332434 successful.
INFO satnogsclient.scheduler.tasks Upload of audio recording for observation 14332434 successful.

image
image550×762 97 KB

2

UPDATE: I found at least a work-around - the problem seems to be related to the USB3.x ports of the AMD X370 mainboard - hardware or drivers. Plugging the LimeSDR to a USB2-port solves the problem for now. As the sample-rate is very low, this is not a restriction for this application.

Stefan/OE6ISP

2 Likes
3

Do you have an external power supply for the lime or just the usb? I see some issues the myriad forum regarding usb3 ports (e.g. LimeSDR fails to stream over USB 3.0 leading to a single-shot receive spectrum and USB Transfer Error state - #2 by andrewback - LimeSDR - MyriadRF Discourse).

Is this issue related to this?

4

The Lime has externel power and there are no problems running on win11 for example, whch lets e speculate it’s a combination of specific hardware and debian-drivers. I can also exclude another reason, the unstable USB3-link of the Lime, which can be worked around by using short cable and a USB3-hub close to the board.

No, I cannot see a relation to the other issue.

Stefan/OE6ISP