FlightAware Discussions

MLAT not syncing

Hi there,

last week I set up a second feeder. It is built on a Raspi 3 (PiAware is 3.7.2), with the flightaware pro stick, flightaware bandpass filter and the FlightAware 1090MHz ADS-B N-Type Antenne 5.5dBi. It is connected via WLAN and checked in. But MLAT is not working. On the webinterface it says either the raspi is running out of cpu or the location is wrong. Location is varified and enterned manually.

Her is the log:

[2019-11-11 07:39 CET] 241791 msgs recv’d from dump1090-fa (752 in last 5m); 241629 msgs sent to FlightAware
[2019-11-11 07:49 CET] 243338 msgs recv’d from dump1090-fa (757 in last 5m); 243176 msgs sent to FlightAware
[2019-11-11 07:50 CET] mlat-client(947): Server status: clock unstable
[2019-11-11 07:50 CET] mlat-client(947): Aircraft: 7 of 11 Mode S, 31 of 33 ADS-B used
[2019-11-11 08:04 CET] 245729 msgs recv’d from dump1090-fa (741 in last 5m); 245567 msgs sent to FlightAware
[2019-11-11 08:05 CET] mlat-client(947): Receiver status: connected
[2019-11-11 08:05 CET] mlat-client(947): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server
[2019-11-11 08:05 CET] mlat-client(947): Server status: clock unstable
[2019-11-11 08:05 CET] mlat-client(947): Receiver: 242.0 msg/s received 49.9 msg/s processed (21%)
[2019-11-11 08:05 CET] mlat-client(947): Aircraft: 15 of 18 Mode S, 21 of 23 ADS-B used
[2019-11-11 08:09 CET] 246443 msgs recv’d from dump1090-fa (714 in last 5m); 246281 msgs sent to FlightAware
[2019-11-11 08:14 CET] 247187 msgs recv’d from dump1090-fa (744 in last 5m); 247025 msgs sent to FlightAware
[2019-11-11 08:20 CET] mlat-client(947): Aircraft: 11 of 19 Mode S, 28 of 33 ADS-B used
[2019-11-11 08:20 CET] mlat-client(947): Receiver: 254.3 msg/s received 42.9 msg/s processed (17%)
[2019-11-11 08:20 CET] mlat-client(947): Server status: clock unstable
[2019-11-11 08:20 CET] mlat-client(947): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server
[2019-11-11 08:24 CET] 248889 msgs recv’d from dump1090-fa (938 in last 5m); 248727 msgs sent to FlightAware
[2019-11-11 08:29 CET] 249798 msgs recv’d from dump1090-fa (909 in last 5m); 249636 msgs sent to FlightAware
[2019-11-11 08:34 CET] 250523 msgs recv’d from dump1090-fa (725 in last 5m); 250361 msgs sent to FlightAware
[2019-11-11 08:35 CET] mlat-client(947): Server status: clock unstable
[2019-11-11 08:35 CET] mlat-client(947): Receiver status: connected
[2019-11-11 08:35 CET] mlat-client(947): Aircraft: 17 of 23 Mode S, 11 of 13 ADS-B used
[2019-11-11 08:39 CET] 251084 msgs recv’d from dump1090-fa (561 in last 5m); 250922 msgs sent to FlightAware
[2019-11-11 08:44 CET] 251516 msgs recv’d from dump1090-fa (432 in last 5m); 251354 msgs sent to FlightAware
[2019-11-11 08:50 CET] mlat-client(947): Server status: clock unstable
[2019-11-11 08:50 CET] mlat-client(947): Aircraft: 9 of 16 Mode S, 14 of 16 ADS-B used
[2019-11-11 08:50 CET] mlat-client(947): Receiver status: connected
[2019-11-11 08:50 CET] mlat-client(947): Receiver: 149.2 msg/s received 30.2 msg/s processed (20%)
[2019-11-11 08:50 CET] mlat-client(947): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.3kB/s UDP to server
[2019-11-11 08:54 CET] 252576 msgs recv’d from dump1090-fa (600 in last 5m); 252414 msgs sent to FlightAware
[2019-11-11 08:59 CET] 253218 msgs recv’d from dump1090-fa (642 in last 5m); 253056 msgs sent to FlightAware
[2019-11-11 09:04 CET] 253899 msgs recv’d from dump1090-fa (681 in last 5m); 253737 msgs sent to FlightAware
[2019-11-11 09:05 CET] mlat-client(947): Receiver status: connected
[2019-11-11 09:05 CET] mlat-client(947): Receiver: 206.5 msg/s received 39.4 msg/s processed (19%)
[2019-11-11 09:14 CET] 255268 msgs recv’d from dump1090-fa (685 in last 5m); 255106 msgs sent to FlightAware
[2019-11-11 09:19 CET] 255938 msgs recv’d from dump1090-fa (670 in last 5m); 255776 msgs sent to FlightAware
[2019-11-11 09:20 CET] mlat-client(947): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server
[2019-11-11 09:20 CET] mlat-client(947): Receiver status: connected
[2019-11-11 09:20 CET] mlat-client(947): Receiver: 226.3 msg/s received 39.0 msg/s processed (17%)
[2019-11-11 09:24 CET] 256620 msgs recv’d from dump1090-fa (682 in last 5m); 256458 msgs sent to FlightAware
[2019-11-11 09:29 CET] 257730 msgs recv’d from dump1090-fa (1110 in last 5m); 257568 msgs sent to FlightAware
[2019-11-11 09:34 CET] 258807 msgs recv’d from dump1090-fa (1077 in last 5m); 258645 msgs sent to FlightAware
[2019-11-11 09:35 CET] mlat-client(947): Receiver status: connected
[2019-11-11 09:35 CET] mlat-client(947): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.5kB/s UDP to server
[2019-11-11 09:35 CET] mlat-client(947): Aircraft: 14 of 22 Mode S, 33 of 39 ADS-B used
[2019-11-11 09:39 CET] 259679 msgs recv’d from dump1090-fa (872 in last 5m); 259517 msgs sent to FlightAware
[2019-11-11 09:44 CET] 260547 msgs recv’d from dump1090-fa (868 in last 5m); 260385 msgs sent to FlightAware
[2019-11-11 09:49 CET] 261304 msgs recv’d from dump1090-fa (757 in last 5m); 261142 msgs sent to FlightAware
[2019-11-11 09:50 CET] mlat-client(947): Receiver status: connected
[2019-11-11 09:50 CET] mlat-client(947): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server
[2019-11-11 09:50 CET] mlat-client(947): Aircraft: 10 of 14 Mode S, 24 of 28 ADS-B used
[2019-11-11 09:54 CET] 262094 msgs recv’d from dump1090-fa (790 in last 5m); 261932 msgs sent to FlightAware
[2019-11-11 10:05 CET] mlat-client(947): Receiver status: connected
[2019-11-11 10:05 CET] mlat-client(947): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server
[2019-11-11 10:05 CET] mlat-client(947): Receiver: 248.3 msg/s received 45.5 msg/s processed (18%)
[2019-11-11 10:05 CET] mlat-client(947): Aircraft: 14 of 26 Mode S, 25 of 29 ADS-B used
[2019-11-11 10:09 CET] 264492 msgs recv’d from dump1090-fa (880 in last 5m); 264330 msgs sent to FlightAware
[2019-11-11 10:17 CET] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.191:6627:2133589898
[2019-11-11 10:17 CET] my feeder ID is 451fc646-771a-4b54-88a6-b959eff8f194
[2019-11-11 10:17 CET] site statistics URL: https://flightaware.com/adsb/stats/user/highchain#stats-114456
[2019-11-11 10:17 CET] multilateration data requested
[2019-11-11 10:17 CET] mlat-client(20034): Listening for Beast-format results connection on port 30105
[2019-11-11 10:17 CET] mlat-client(20034): Using UDP transport to 70.42.6.191 port 6627
[2019-11-11 10:17 CET] mlat-client(20034): Input format changed to BEAST, 12MHz clock
[2019-11-11 10:17 CET] mlat-client(20034): Listening for Extended Basestation-format results connection on port 30106
[2019-11-11 10:17 CET] mlat-client(20034): Beast-format results connection with ::1:30104: connection established
[2019-11-11 10:24 CET] 267052 msgs recv’d from dump1090-fa (815 in last 5m); 266700 msgs sent to FlightAware
[2019-11-11 10:29 CET] 267787 msgs recv’d from dump1090-fa (735 in last 5m); 267435 msgs sent to FlightAware
[2019-11-11 10:32 CET] mlat-client(20034): Aircraft: 13 of 18 Mode S, 20 of 21 ADS-B used
[2019-11-11 10:32 CET] mlat-client(20034): Receiver: 271.3 msg/s received 55.8 msg/s processed (21%)
[2019-11-11 10:32 CET] mlat-client(20034): Receiver status: connected
[2019-11-11 10:32 CET] mlat-client(20034): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.5kB/s UDP to server
[2019-11-11 10:34 CET] 268441 msgs recv’d from dump1090-fa (654 in last 5m); 268089 msgs sent to FlightAware

Do you guys have any idea?

Thanks,

Marcus

Check the location again against the coordinates you find using this: https://www.mapcoordinates.net/en

The coordinates need to be accurate to 4 decimals, so this precision: 1.2345

Otherwise it might be that the power supply is having problems.
Which Raspberry Pi are you using for this setup?

Check for undervoltage please:

sudo dmesg --ctime | grep voltage

Hi I’m using a Raspi 3. Undervoltage I will check when back home. Check the location and corrected it. Let’s see now.

Thanks,
Marcus

SOLVED!

Ajusting the GPS-data solved it.

Many thanks!