Hi all, The AdsbExchange installation script used in adsbreceiver image uses MLAT-client 0.2.9 and seems that it does not work/sync correctly. So, if you use adsbreceiver image, and you have installed the adsbexchange feeder with the built in script you should remove it and install it again manually to get the MLAT-client 0.2.6 Code: sudo service mlat-client stop sudo apt-get remove mlat-client sudo apt-get purge mlat-client cd adsb-receiver/build/ sudo rm -rf adsbexchange sudo apt-get install git sudo git clone https://github.com/jprochazka/adsb-exchange.git cd adsb-exchange sudo chmod +x setup.sh sudo ./setup.sh sudo reboot Cheers
Thanks. Someone should advise Joe that this is th case. I believe the newer versions of MLAT-client are written specifically for the FlightAware MLAT Server implementation, not the open source one. Dan
Hello, I read that there would be a problem with mlat-client 0.2.9 but it works for me... Sorry, I could give more details but that is considered has spam.
please send me a email with your intallation details to marcoses11 at gmail dot com also tell me please the geograpic area where you have the stuff.
I did not receive your info. Could you say if you see your statation synced whith another stations in the MLAT Syncronization Matrix?
I sent the mail successfully yesterday and I did'nt receive any reject. The address is correct with "at" and "dot" replaced of course! Anyway, my station is in France and it is displayed in the "Western Europe/West Africa" region (beduzar). It shows successful calculations for my station. I see me in the "Coverage Graphics" and in the "MLAT Synchronisation Matrix" where I am synced with several stations even accross the Channel. Please check if "marcoses11 at gmail dot com" is OK and I try to send my details again.
Yes, my fault, for some reason It was in the spam folder. The difference in your setup is that you are not using ADSBRECEIVER image. You are using Raspbian Jessie with the PA and ADSBExchange feeders and MLAT clients. The ADSBReciver image (www.adsbreceiver.net) is a different project that uses "Dump1090 Mutability", and for some reason makes mlat-client versions newer than 0.2.6 to have sync problems. In fact it takes control of mlat-client in some way disabling it : Code: [email protected]:~ $ sudo systemctl -l status mlat-client ● mlat-client.service - LSB: Multilateration client Loaded: loaded (/etc/init.d/mlat-client) Active: active (exited) since Sun 2017-10-29 18:39:12 CET; 2h 22min ago Process: 505 ExecStart=/etc/init.d/mlat-client start (code=exited, status=0/SUCCESS) Oct 29 18:39:12 raspberrypi mlat-client[505]: Not starting mlat-client daemon, disabled via /etc/default/mlat-client ... (warning). Oct 29 18:39:12 raspberrypi systemd[1]: Started LSB: Multilateration client.
Okay. So, the problem is not actually mlat-client 0.2.9. With my configuration, I have no reason to switch back to an older version of mlat-client. Thank you very much for your explanations.
You are welcome. I did an error in my previous post, its edited now, I wrote "mlat mutability" but I mean "dump1090-mutability"
Hi all, jprochazka Reverted mlat-client version back to 0.2.6 by default. https://github.com/jprochazka/adsb-receiver/commit/e2ff3c9a7de913851b16c63234ad8878be5e45f4 Code: # mlat-client MLAT_CLIENT_VERSION="0.2.6" MLAT_CLIENT_TAG="v0.2.6" Admins please close the Thread. Cheers