Closed sgofferj closed 3 years ago
Hi @sgofferj,
Unfortunately there isn't any way supported by the mlat-client to increase the logging verbosity:
usage: mlat-client [-h]
[--input-type {auto,dump1090,beast,radarcape_12mhz,radarcape_gps,radarcape,sbs,avrmlat}]
--input-connect INPUT_CONNECT [--results RESULTS]
[--no-anon-results] [--no-modeac-results] --lat LAT --lon
LON --alt ALT [--privacy] --user USER [--server SERVER]
[--no-udp] [--log-timestamps]
However, from what I can gather there are no problems with your software configuration.
I've had a chat to the ADSBExchange devs regarding this, and the problem with your MLAT appears to be the amount of positions you're feeding in. MLAT won't sync if there are no positions being fed. While chatting to the devs, we saw a plane pop up and immediately your mlat-client started syncing:
Your feed:
Positions from your area:
Your MLAT results (from just that one plane):
As you can see, there is a lot of aircraft activity in your area, but you were only picking up that one flight.
Accordingly, you may wish to consider:
Improving the quality of your feed will result in much better and more stable MLAT synchronisation.
Will do! Thanks for your help and your work!
You're very welcome.
I'm running your containers so far successfully as a stack with readsb-protobuf, adsb-exchange and tar1090. The only thing that doesn't seem to work is MLAT. the status page shows me all green but my station doesn't seem to sync with any peers: https://adsbx.org/sync/feeder.html?5A&ADSB_VLK
The console output doesn't seem to show any errors. Here's an example:
I couldn't find any documentation for the mlat client or any debugging options. Could you please advise how to enable additional debugging output or where to start debugging?