Open darethehair opened 5 days ago
https://github.com/ADSBexchange/feedclient
Edit: sorry, i read over it to fast and just see u already had a working MLAT sharing config. However leaving it here as the part 'Disable / Enable adsbexchange MLAT-results in your main decoder interface' could be the tweek u need, or set u on the right path.
https://github.com/ADSBexchange/feedclient
Edit: sorry, i read over it to fast and just see u already had a working MLAT sharing config. However leaving it here as the part 'Disable / Enable adsbexchange MLAT-results in your main decoder interface' could be the tweek u need, or set u on the right path.
Yes, MLAT is configured and the ADS-B Feeder Status page tells me that MLAT is 'connected' and 'feed OK' -- but I never see any MLAT flights in the tracking display. I am not sure what 'enable/disable' you are referring to, but I did try to run the 'axupdate.sh' script in hopes that it might be there -- and it eventually failed with compile errors (!) on 'readsb'. As for MLAT, it told me the following:
Installing mlat-client to virtual environment
34
36
38
40
46
48
50
60
70
https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-Lite:-ADS-B-receiver
You gotta check the MLAT sync. For example the mlat-client log will tell you more.
Not sure if this will help illustrate my situation, but my MLAT connections are working fine:
Most aircraft have ADS-B transponders.
That sync pattern suggests limited range as well, that doesn't help either.
For MLAT results you need 4 receivers to receive the ModeS aircraft to get an MLAT position. So sufficiently overlapping coverage might only exist for aircraft > 30k ft and in a limited area.
You can always try other MLAT networks (and sending data to other aggregators also helps :)) If you're on a pi3/4/5 i'd recommend this for easy setup: https://adsb.im/
Or if you'd rather set things up yourself: https://sdr-enthusiasts.gitbook.io/ads-b/
Makes it simple to send data to multiple sites.
The active display page for tracking flights appears to have a code/color reserved for 'MLAT' tracking, but I never see any showing up -- despite having a working MLAT-sharing configuration. Have I forgotten to do something?
In previous alternate tar0190 setups that I have run over the years, it seems to me that my range with MLAT activated was further than I am now getting, so I am curious if I need to tweek something.