For the last few days my site - 92827 - has lost MLAT synchronization for extended periods then re-synchonizes. Is this a backend issue or something broken at mine? Typically synced with 454 nearby receivers. The log shows nothing obvious.
1 Like
If it was fine before, SDR might be dying.
1 Like
My MLAT comes and goes regularly during high traffic volume times of day. The log states that MLAT is no longer needed, and the system reverts to a “Beast” mode. Doesn’t appear to be anything broken but the system is reacting to the usefulness of MLAT at a particular time. After a while, the system restarts the MLAT protocol and it’s up and running again. It never complains about being able to establish the MLAT location. With your 454 nearby receivers it appears you are in a fairly active environment also.
1 Like
MLAT transition from log:
multilateration data no longer required, disabling mlat client
[2024-12-19 12:35 EST] mlat-client(28651): Exiting on connection loss
[2024-12-19 12:35 EST] fa-mlat-client exited normally
[2024-12-19 12:37 EST] multilateration data requested
[2024-12-19 12:37 EST] mlat-client(29124): Listening for Extended Basestation-format results connection on port 30106
[2024-12-19 12:37 EST] 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 2620:13d:c004:11::193:14961:2814579537
[2024-12-19 12:37 EST] mlat-client(29124): Input format changed to BEAST, 12MHz clock
[2024-12-19 12:37 EST] mlat-client(29124): Input connected to localhost:30005
[2024-12-19 12:37 EST] mlat-client(29124): Using UDP transport to 2620:13d:c004:11::193 port 14961
[2024-12-19 12:37 EST] mlat-client(29124): Route MTU changed to 1500
[2024-12-19 12:37 EST] mlat-client(29124): Listening for Beast-format results connection on port 30105
[2024-12-19 12:37 EST] mlat-client(29124): fa-mlat-client 0.2.12 starting up
[2024-12-19 12:37 EST] mlat-client(29124): Beast-format results connection with ::1:30104: connection established
1 Like
Craig, your explanation is exactly what I’ve been seeing in the log. And yes, wieddehopf, the original problem was caused by a failing SDR which has been replaced replaced. The traffic here in SoCal is very high.
Thanks for the definitive explanation.
1 Like