FlightAware shows RED on MLAT Feeder Status


#1

Just did the latest upgrade (which I realize may not have been the latest). Current piaware stats:

$ uname -a
Linux piaware 4.14.66-v7+ #1137 SMP Fri Aug 24 16:36:53 BST 2018 armv7l GNU/Linux

$ dpkg -l piaware
ii  piaware        3.6.2        armhf        Open Aviation Data Exchange Proto

Has anyone seen a recent solution to get MLAT stats working again? This was working up until this upgrade.


#3

I spoke too soon. It is NOT fixed. MLAT still shows Red on FA.com.

Any thoughts?


#4

Go to your feeder page on FA, hit the white gear icon on the upper right below the map. Scroll in the log box at the bottom and see what mlat-client messages say.


#5

Here’s what I’ve got. Seems like it’s clean.

[2018-08-28 15:28 CDT] mlat-client(1391): fa-mlat-client 0.2.10 starting up
[2018-08-28 15:28 CDT] mlat-client(1391): Using UDP transport to 70.42.6.197 port 8860
[2018-08-28 15:28 CDT] mlat-client(1391): Listening for Beast-format results connection on port 30105
[2018-08-28 15:28 CDT] mlat-client(1391): Listening for Extended Basestation-format results connection on port 30106
[2018-08-28 15:28 CDT] mlat-client(1391): Input connected to localhost:30005
[2018-08-28 15:28 CDT] mlat-client(1391): Input format changed to BEAST, 12MHz clock
[2018-08-28 15:28 CDT] mlat-client(1391): Beast-format results connection with ::1:30104: connection established

#6

Looks like you just restarted, or this is the very top pf the log. Let things run for 5 or 10 minutes then look near the bottom for:

[2018-08-28 13:49 PDT] mlat-client(594): Receiver status: connected
[2018-08-28 13:49 PDT] mlat-client(594): Server status: synchronized with 324 nearby receivers

#7

Unstable clock. Check you have the correct position set; check your power and USB connections.


#8

Few more things. Still showing red. Here’s a couple more items from the log file pulled right off the device (note these are UTC, not CDT)

Aug 28 20:43:24 piaware piaware[1367]: mlat-client(1391): Receiver status: connected
Aug 28 20:43:24 piaware piaware[1367]: mlat-client(1391): Server status:   clock unstable
Aug 28 20:43:24 piaware piaware[1367]: mlat-client(1391): Receiver:  645.6 msg/s received      185.8 msg/s processed (29%)
Aug 28 20:43:24 piaware piaware[1367]: mlat-client(1391): Server:      0.1 kB/s from server    0.0kB/s TCP to server     2.1kB/s UDP to server
Aug 28 20:43:24 piaware piaware[1367]: mlat-client(1391): Results:  43.7 positions/minute
Aug 28 20:43:24 piaware piaware[1367]: mlat-client(1391): Aircraft: 62 of 113 Mode S, 50 of 75 ADS-B used
Aug 28 20:58:25 piaware piaware[1367]: mlat-client(1391): Receiver status: connected
Aug 28 20:58:25 piaware piaware[1367]: mlat-client(1391): Server status:   clock unstable
Aug 28 20:58:25 piaware piaware[1367]: mlat-client(1391): Receiver:  581.9 msg/s received      171.7 msg/s processed (30%)
Aug 28 20:58:25 piaware piaware[1367]: mlat-client(1391): Server:      0.0 kB/s from server    0.0kB/s TCP to server     2.0kB/s UDP to server
Aug 28 20:58:25 piaware piaware[1367]: mlat-client(1391): Aircraft: 52 of 95 Mode S, 53 of 74 ADS-B used

I’m going to double check the connections right now.


#9

Also, the position is correctly set on FA.com. Is there another location in a config file somewhere that I need to post it?

All connections look solid. Just started happening once I upgraded to 3.6.2.


#10

OK it’s temporarily back to green. Let’s see if it holds.