I'm sending 3 feeds to ADSBexchange and the latest one is Dunnsville-SDRplay which I've been trying to get a SDRplay RSP1 & 1A working. Over at "the other place" FlightAware I keep on getting "Server status: clock unstable" and it kicks me off the MLAT. In one of the discussions I saw where OJ stated "this 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." BUT so far on here I'm not getting kicked off MLAT here and the times I've looked at the mlat matrix I've only seen the sync error come up once or twice and then just go away. Is there any history that is obtainable that I could get to see if ADSBexchange is seeing any problem with this feed. I've been working with one of the programmers at SDRplay to resolve the possible Mirics chip driver issue but so far we don't see anything that would be causing it and I'd really like to see the SDRplay RSP work well. Note: I have been doing a lot of restarts at certain times testing different strings etc. so all the restart handshaking to get connections up is me. Thx
Well, ADSBx will just drop your data if your clocks are off. So the issue likely exists with the data you are feeding here as well. You can check how far you are off by looking at the feeder name in the sync matrix.
Thx, James. True, but it seems the threshold is higher here and as stated on the original post I have been watching the sync matrix data as well. Unfortunately the sync data page times out on a regular basis and needs to be refreshed so it's not a very stable tool at this point. What has been interesting as this is a fork of OJ's mutability it will also run a rtl-sdr and that is not having any issues whatsoever which points me toward issues with the Mitics API that replaces the RTL API. I have it tied into my main antenna today and we'll see how it does @ 900-1000 msg/sec. I usually see issues starting out above 200 msg/sec.
