I am a new feeder and I believe I have my MLAT working correctly as I can see my feeder name in the matrix as well as the graphic. After taking over an unused receiver in the custom feeds section, I was able to see my own plane traffic. I do not see any MLAT tracks when looking at my custom receiver, they either all say "no" or just empty. Does this mean that I am not receiving a back-feed? How can I double check this to make sure I am configured properly? Thanks for the help,
The mlat results should only appear on your local map from dump1090. But that's just the mlat results you take part in. Those won't appear on your custom VRS feed. MLAT aircraft will only be on the main global VRS, not the custom feeds.
That's the idea I had as well but I was checking out a few custom feeds and they had MLAT results stating "yes", so I wasn't sure.
That would need to be configured so your MLAT results appear there. (normal custom feed setup) You can check if mlat-client is connected here: https://adsbexchange.com/myip/ Or you can check your sync matrix: https://www.adsbexchange.com/active-feeds/ Note that MLAT isn't quite as stable and sometimes you won't get a connection. That's normal it should connect eventually. (UK MLAT is the exception i believe it's overloaded a bit so might not get a connection)
Default configuration of mlat-client Code: ... --results beast,connect,127.0.0.1:30104 ... and dump1090 Code: ... --net-bi-port 30004,30104 ... It means that mlat-client is pushing results to dump1090 using port 30104 (aircrafts visible on local dump1090 map). To make results available to VRS or any other software add at the end of mlat-client script (before done) Code: --results,beast,listen,31003 where 'beast' is data format and 31003 is port number.
I was taking a look at /etc/default/mlat-client and found the line for results and It only had "basestation,listen,31003". I went ahead and added 'beast' in there as well and rebooted. Not sure if that is the correct way to go about it but I will see if it fixed the issue. Thanks for the help.
The adsb exchange script doesn't use that configuration file. MLAT results going to dump1090 will not be forwarded to adsb exchange or other feed services. This is very much on purpose otherwise feed services would not know which aircraft are ADS-B and which are MLAT. If there are custom feeds that have MLAT, then it's James doing some configuration server side. You'll have to go through the forms for custom feeds most likely. But that can take time and James is busy enough as it is. I'd suggest looking at the global adsb exchange map for MLAT. Or if you want to see your local mlat you can look at the local /dump1090-fa map on your pi. Note that if you have flightaware mlat going as well that results of both will be shown.
Check your /home/pi/adsb-exchange/adsbexchange-mlat_maint.sh it should look like (lat, lon, alt, user - your data) Code: #!/bin/sh while true do sleep 30 /usr/bin/mlat-client --input-type dump1090 --input-connect localhost:30005 --lat your.lat --lon your.lon --alt youralt --user yourusername --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,localhost:30104 done This is only place you need to edit.
You won't see MLAT on the custom feed. Only your local map. FlightAware, FR24 etc all will sue ADSBx if we forward mlat.
That makes sense to me but I had checked around on different custom feeds and MLAT seemed to be working on a couple. For example, on global custom 2 there is a feed named "Koko" that currently has some MLAT tracks. That is why I thought was possible.