Trying to get a SDRplay RSP to work and have been getting kicked off of FA MLAT as I keep getting the “Server status: clock unstable” error on PiAware using the SDRplay dump1090-mut with an API in it for the RSP. Other than that it seems to be about the same results as a RTL-SDR that’s running next to it on a splitter. According to a post I saw in which OJ said that it is caused by dropped samples on the USB bus as it shows up as the intervals between messages from the receiver being way off compared to the same messages being received by other receivers.
I’ve been talking with one of the programmers at SDRplay and he doesn’t seem to see any problems on his end and I have tried the following based on other similar discussions here on FA.
- Tried 3 different USB cables between Pi and RSP’s
- Tried both a RSP1 and a RSP1A
- Made sure the settings were for lowest bandwidth i.e --bwMode 0 (for 1.536), --normal (Ignore settings and set up RSP for ZeroIF 2MHz Demod), No oversample or any other bandwidth user.
- Disconnected Ethernet cable from Shared USB\Ethernet port and connected to WiFi with Pi close to WiFi.
- Connected both Ethernet cable and WiFi.
- Connected with just WiFi.
- Tried all 4 usb ports
- Tried other known good power supplies
As the command line string item --dev-sdrplay is the only thing that tells it to work with a RSP I have also tried it with a RTL-SDR on it without that switch and it works fine with no errors.
During the night when traffic falls below 175-200 msg/sec (30-40 planes) it will connect to the MLAT server and works fine.
One more item is MLAT seems to be working ok when connected to ADSBexchange and only occasionally I will see a sync error on their mlat matrix and then it goes away.
Are there any routines that can be run on the Pi to tell if it is indeed losing samples on the usb bus?