First post, brand new stock PiAware setup that’s been running for 12 hours and I’m seeing the following error message:
Anomaly report for PiAware feeder with a MAC address of xxx:
This feeder is not being used for multilateration because its timing information appears to be unreliable. This can be caused by the site location being incorrect, or because your Pi is running out of free CPU.
I’m seeing this in the logs:
[2015-10-10 10:18 PDT] mlat(2398): Receiver status: connected
[2015-10-10 10:18 PDT] mlat(2398): Server status: clock unstable
[2015-10-10 10:18 PDT] mlat(2398): Receiver: 10.7 msg/s received 0.2kB/s from receiver
[2015-10-10 10:18 PDT] mlat(2398): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2015-10-10 10:18 PDT] mlat(2398): Results: 21.3 positions/minute
[2015-10-10 10:18 PDT] mlat(2398): Aircraft: 4 of 4 Mode S, 1 of 1 ADS-B used
Site location should be fine, CPU usage is low, and Mlat was working earlier. What’s causing this issue and how do I debug?
Same on my side - I’ve changed recently from PI B+ to PI 2 and to my surprise today I received anomalies notification. It started showing when receiver has picked up more than 300 msgs/s. Any idea on that?
Don’t know if it is pertinent, but I had similar clock error notifications from Planeplotter recently. I did not check the RPi logs at the time. The cause appeared to be a significant DOS attack at the time. Thruput degradation was enough to be remarked on by XYL/DW
Unsupported receivers
The FlightRadar24 radarcape-based receiver. This produces a deliberately crippled timestamp in its output, making it useless for multilateration. If you have one of these, you should ask FR24 to fix this.