Enable Mlat on Mutability 1.15 / EB_Version
- Thread starter Hardy2018
- Start date
ab cd
Senior Member
Both the dump1090-mutability and dump1090-fa are by default enabled to receive mlat-results on port 30104.
However the mlat calculations are NOT made locally on the Pi running dump1090. This is done on servers of sites like Planefinder, Flightaware, Adsbexchange, Flightradar24, and Radarbox24.
However not all these sites return mlat-results to your Pi. The situation is as follows:
- Plandfinder neither use RPi feeders for mlat calculation, nor feed backs any mlat results to RPi feeders. Currently they use only Plane Finder Radar and Radarcape receivers for mlat calculations.
- Flightradar24 and Radarbox24 use RPi feeders for mlat, but do NOT feed back results to your RPi.
- Flightaware and Adsbexchange use RPi fedders for mlat and DO feedback mlat-results to your RPi to port 30104 of dump1090(mutability EB Ver or fa) which display these mlat plane on their maps.
If you want to see mlat planes on dump1090-mutability EB VER, simply install piaware data feeder and Adsbexchange datafeeder, and that is all. Your dump1090-mutability EB Ver will automatically start displaying mlat planes whose results are fed back by these two site.
However the mlat calculations are NOT made locally on the Pi running dump1090. This is done on servers of sites like Planefinder, Flightaware, Adsbexchange, Flightradar24, and Radarbox24.
However not all these sites return mlat-results to your Pi. The situation is as follows:
- Plandfinder neither use RPi feeders for mlat calculation, nor feed backs any mlat results to RPi feeders. Currently they use only Plane Finder Radar and Radarcape receivers for mlat calculations.
- Flightradar24 and Radarbox24 use RPi feeders for mlat, but do NOT feed back results to your RPi.
- Flightaware and Adsbexchange use RPi fedders for mlat and DO feedback mlat-results to your RPi to port 30104 of dump1090(mutability EB Ver or fa) which display these mlat plane on their maps.
If you want to see mlat planes on dump1090-mutability EB VER, simply install piaware data feeder and Adsbexchange datafeeder, and that is all. Your dump1090-mutability EB Ver will automatically start displaying mlat planes whose results are fed back by these two site.
Last edited:
Hello ab cd,
thank you very much for the detailed explanation.
I was wondering who made mlat display on Dump1090 available.
(Now i know, It's FlightAware after an update, but I don't know when this happened)
My old ADSB-Pi is feeding since 2018:
- FlightAware
- Flightradar-24
- Planefinder
- Planeplotter
- AirNav Radarbox
Now I want to upgrade to a new RPI-4 Buster installation and add also Adsbexchange.
On my new RPI-4 (Buster) Adsbexchange, works perfect.
Now my question:
is there a possibility to define which feeder shows Mlat-Planes on the Dump1090 Map ?
are there any negative influence if all the Feeders are installed on the new RPI-4 ?
Best regards
Hardy
thank you very much for the detailed explanation.
I was wondering who made mlat display on Dump1090 available.
(Now i know, It's FlightAware after an update, but I don't know when this happened)
My old ADSB-Pi is feeding since 2018:
- FlightAware
- Flightradar-24
- Planefinder
- Planeplotter
- AirNav Radarbox
Now I want to upgrade to a new RPI-4 Buster installation and add also Adsbexchange.
On my new RPI-4 (Buster) Adsbexchange, works perfect.
Now my question:
is there a possibility to define which feeder shows Mlat-Planes on the Dump1090 Map ?
are there any negative influence if all the Feeders are installed on the new RPI-4 ?
Best regards
Hardy
ab cd
Senior Member
"is there a possibility to define which feeder shows Mlat-Planes on the Dump1090 Map ?"
No. On dump1090 (EB_VER or Flightaware Version) there is no feeder-wise segregation of mlat planes.
"are there any negative influence if all the Feeders are installed on the new RPI-4 ?"
No, there are no negative influence if you configure them normally.
NOTE FOR PLANEPLOTTER
In Dec 2019, I found that the planeplotter RPI feeder had a bug. It starts using 100% CPU if dump1090 (EB_VER/mutability or fa ver) is restarted, either automatically or manually.
I have posted a solution for it in Flightaware forums
Declaration of bug:
discussions.flightaware.com
Solution:
discussions.flightaware.com
I am not sure if Planeplotter software developers have removed the bug or it is still there.
You can check using command "top", check CPU % of Planeplotter, then issue command to restart dump1090, and check again the CPU usage of Planeplotter. If it does not jump to above 90%, then the bug has been removed by Planeplotter RPi feeder Developers.
No. On dump1090 (EB_VER or Flightaware Version) there is no feeder-wise segregation of mlat planes.
"are there any negative influence if all the Feeders are installed on the new RPI-4 ?"
No, there are no negative influence if you configure them normally.
NOTE FOR PLANEPLOTTER
In Dec 2019, I found that the planeplotter RPI feeder had a bug. It starts using 100% CPU if dump1090 (EB_VER/mutability or fa ver) is restarted, either automatically or manually.
I have posted a solution for it in Flightaware forums
Declaration of bug:
How-to Feed Plane Plotter Site directly from Raspberry Pi
CONCLUSION: Restart of dump1090 (fa or mutab) causes CPU usage of ppup1090 to jump from 0.7% to 98%, and stay there till ppup1090 is restarted (see details below). This also results in ppup1090 stops feeding data to planeplotter server. @Aerovision1 : Do you have a cron job to reset gain every...
discussions.flightaware.com
Solution:
How-to Feed Plane Plotter Site directly from Raspberry Pi
@Aerovision1 Thanks to @wiedehopf. Adding only one line (PartOf=…) to file ppup1090.service was enough. I tested it. Every time the dump1090 is started, ppup1090 also get started automatically, and CPU usage stays at below 1% Service file of ppup1090, if using dump1090-fa sudo nano...
discussions.flightaware.com
I am not sure if Planeplotter software developers have removed the bug or it is still there.
You can check using command "top", check CPU % of Planeplotter, then issue command to restart dump1090, and check again the CPU usage of Planeplotter. If it does not jump to above 90%, then the bug has been removed by Planeplotter RPi feeder Developers.
The "Problem" is not Fixed, i get 98% CPU-Load.
After Reboot back to Normal.
Next i will implement from https://discussions.flightaware.com...tter-site-directly-from-raspberry-pi/37538/27
An alternate (and better) method to start ppup1090 at boot is to create ppup1090.service file and enable it, so that ppup1090 is started by systemd instead of rc.local.
ab cd
Senior Member
That is not enough. To fix 98% cpu load bug, you will need to add line given below in ppup1090.service file:
PartOf=dump1090-mutability.service
Please see this post:
https://discussions.flightaware.com...tter-site-directly-from-raspberry-pi/37538/73
