Everything appears fine with my feeder and I feed multiple different services but I cannot get MLAT to go green on my FlightAware page: davewill2010 ADS-B Feeder Statistics - FlightAware
Any idea on how I can get this fixed?
Thanks in advance
How accurate is your site location?
I believe it is spot on but if you can suggest how I can check and adjust I would be very interested to hear any suggestions.
Go to the paddle wheel and select “edit location”
Drag the map / pointer somewhere close to your actual location
OK I have dragged the pointer to the exact location of the antenna and will see if that helps.
Many Thanks for your help
I made the change about 25 minutes ago and it went green temporarily but then went back to red.
If I click on “View Anomaly” it shows this: Site 43072
- 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.
What does the piaware log tell you ?
If you get the RTC Clock unstable message then the issue is that the timing is not accurate enough for piaware.
Since the Pi doesn’t have a RTC module this is not something you can easily fix as far as I know, I’ve experimented with RTC modules for a Pi but it never was capable to get rid of the incidental red MLAT box.
I take it for granted now since it usually pops up when there is very little traffic around in my setups.
The “Clock Unstable” message is basically never about the actual system time, it’s about the SDR oscillator.
I’m not even aware that there is a “RTC Clock unstable” message, i don’t think there is.
1 Like
I’m referring to
[2026-08-27 15:53 CEST] mlat-client(2458694): Server status: clock unstable
There’s no mention of the RTC clock indeed but that has always been my assumption since the server sees the clock as unstable but that could be the SDR as well indeed.
Not sure i’ve corrected you specificially on this exact error but it sure feels like it 
Pointing at the system time for that error is … a red herring.
It can be a wrong position or data getting lost between SDR and decoder (on USB).
The reason for data getting lost can be multiple things, bad SDR or not enough voltage making it to the SDR (extension / power supply / pi board)
1 Like
Actually you’re pointing out that the logic I’m using isn’t as straightforward as I was thinking. So no offense taken in your reply, I’m still learning everyday from others on these boards.