What are the things that you do with -mutability that you have trouble doing with -fa?
What is the difference between the two, apart from the webpage it displays (if that is one of the differences???)
Nothing really, it is only a matter of getting habituated to one software or the other.
Whatever I can do with dump1090-mutability, I can do with dump1090-fa (package install), and the procedure is only slightly different (i.e. instead of editing file
/etc/default/dump1090-fa is to be edited
In piaware SD card image, the piaware-config controls most parameters of dump1090-fa, and file /etc/default/dump1090-fa is over-written by generator script at every reboot, so basically in piaware SD card image it is the generator script which need to be edited.
The worst case is the dump1090-mutability ver 1.14 installed by the built-in script of Flightradar24’s fr24feed.
The ver 1.14 is installed by fr24feed if it senses abscence of a decoder. This is generally ok as long as someone does not try to install dump1090-mutability v 1.15~dev or dump1090-fa. Such attempt results in disaster. Another bad point is that fr24feeder takes over ownership of dump1090-mut ver 1.14, blocks its auto start at boot, and ver 1.14 is started by fr24feeder.
The nightmare happens when in an installation with dump1090-mutability ver 1.15~dev or dump1090-fa, the fr24feeder setting are chosen “receiver=dvbt”. The fr24feeder’s script installs dump1090-mutability v1.14 over ver 1.15 or fa, creating a real mess.
Indeed. The working setup is to feed FA24 ModeS Beast (TCP) from localhost:30005.
True, but to the inexperienced/first time users, the option “receiver=dvbt” look very natural and logical and they choose it, save setting and restart fr24feed. The moment fr24 restarts with this setting, it runs the installation script for ver 1.14, and that does it.
Same with me, my RasPis R2 & R3 have dump1090-mutability ver 1.15~dev and my (mobile) RasPi Zero has dump1090-fa.
At first I did’nt like the new face of dump1090-fa, but now it’s OK for me and I configured it similar to ‘my’ dump1090-mutability ver 1.15~dev :
I ‘pimped’ both with additional buttons for “RPi-Monitor” and “statistics” (collectd); see red marker in screenshots.
Klick on button then opens a new tab in my browser.
It was by coincidence,
first I installed fr24feed with dump1090-mutability
Then few month later I joined flightaware but didn’t installed dump1090-fa
And now because I don’t want to use google maps what is used in the “dump1090-mutability view” regarding to policy change about the API key, I wanted to use Skyview, with openstreetmaps.
If I started in the beginning with flightaware it would have been dump1090-fa.
I founf this community about tracking planes by coincidence and started with the whole process in february
and it’s now after months I come more to an understanding of the complete thing.
Those who install Flightradar24 feeder BEFORE installing Flightaware Piaware feeder, end up with dump1090-mutability ver 1.14 .
If they use Flightradar24’s Pi24 image, dump1090-mutability ver 1.14 is pre-installed in it.
If they use Raspbian image with package install of FR24 feeder (by their bash script), and on startup the FR24FEED does not find any dump1090 listening on ports 30002/30005, it sets “receiver = dvbt”, which triggers following script which installs dump1090-mutability ver 1.14
cat /usr/lib/fr24/install_dump1090.sh #!/bin/bash # Stop on first error set -e LOGFILE=/var/log/fr24feed_install_dump1090.log exec > >(tee -a $LOGFILE) exec 2>&1 if grep -q "^receiver.*dvbt" /etc/fr24feed.ini && [ ! -e /usr/lib/fr24/dump1090 ] ; then echo "dump1090 is not found, downloading dump1090-mutability..." # to skip any questions from APT export DEBIAN_FRONTEND=noninteractive echo 'dump1090-mutability dump1090-mutability/auto-start boolean false' | debconf-set-selections -v apt-get update -y apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install librtlsdr0 libusb-1.0-0 dirmngr lighttpd wget -y # Download and install dump1090-mutability wget -O /tmp/dump1090-mutability_1.14_armhf.deb https://github.com/mutability/dump1090/releases/download/v1.14/dump1090-mutability_1.14_armhf.deb dpkg -i /tmp/dump1090-mutability_1.14_armhf.deb rm -f /tmp/dump1090-mutability_1.14_armhf.deb ln -s /usr/bin/dump1090-mutability /usr/lib/fr24/dump1090 lighty-enable-mod dump1090 || true service lighttpd force-reload || true systemctl enable lighttpd || true systemctl start lighttpd || true echo "dump1090-mutability is installed. You can always override it in /etc/fr24feed.ini with any other supported driver." echo "Web server (aircraft map) at http://YOUR_DEVICE_IP/dump1090 is enabled by default." fi
Indeed I found out the hard way.
I bought the raspberry pi and installed the raspian.
Then installed fr24feed.
It seemed a nice project and it is, but I’m new to this and raspberry Pi (I know a little from unix from a far past) but the dvbt thingy and blocking it drove me nuts, now I have it working with fr24feed and piaware,
Dispaly of Flightaware feedback MLAT planes
Mutability versions 1.15~dev default settings enable display of FlightAware MLAT planes.
Mutability versions 1.14 installed by FR24FEEDER, starts displayin FlightAware MLAT planes when in file
/etc/fr24feed.ini I added following line
procargs="--net --net-bi-port 30104"
The difference in display by ver1.14 and 1,15 is in labelling.
In ver 1.15~dev mlat planes are shown as MLAT, but in version 1.14 both are shown as ADS-B.
Please see screenshots below.
dump1090-mutability ver 1.14 with SkyView GUI
dump1090-mutability ver 1.15~dev with SkyView GUI
Please do not do this, mlat is fed to a separate port specifically to avoid problems with dump1090 versions that are not mlat aware. dump1090-mutability 1.14 is not mlat aware.
Thanks for advise. This will guide readers in right direction of using either dump1090-fa or dump1090-mutability ver 1.15~dev, if they want Flightaware mlat.
What I posted above was just an experiment with FR24 installed dump1090-mutability 1.14.
I normally do NOT use mutability v 1.14.
I use dump1090-fa and dump1090-mutability ver 1.15~dev
In fact 2 years ago I have created two threads in FlightRadar24 forum to encourage FR24 users to use right versions which are mlat-feed-back ready.
2016-05-14: Manual install of dump1090-mutability ver 1.15~dev
2016-09-22: Automated install of of dump1090-fa / dump1090-mutability ver 1.15~dev using J Prochazka’s script.
When I read those threads your advice is to start from scratch
Is it a good scenario when I prepare this on an other Raspberry Pi and then put the SD card in the Pi I use for my tracking ?
So use the manual scenario until step 10 and then do the next steps on the pi I use for tracking ?
(I have RTC cards on my both pi’s so that is a step I have to look into also to do the configuration)
Yes, it will be ok if you prepare install on one Pi, then use the mocroSD card on another Pi, provided both Pi’s are identical i.e. same model (for example both are 3B+ or both are 3B etc).
If Pi’s are of different models, the swap may work ok, or may totally fail, or may run, but with problems. Try your luck.
ok, thanks ,I keep you informed
Lot of users are complaining about google map displaying water mark.
It is very strange that although I do NOT use any Google Key, the Google map on my following installs does not show any water mark or pop-up “Are you owner of this site?” (at least not yet, expecting it any time in future)
- An old version of dump1090-mutability ver 1.15~dev which has Google map.
- Planefider ver 4.1.1
Please see these screenshots taken about 10 minutes ago.
I think Google grandfathered some installs (for a while?) based on domain or IP.
I lost it once I opened the port to the outside world. Once that was done, there was no turning back. I use a different map now.
Thanks for cautioning.
I am lucky that I last used ddns.net/noip.com more than one years ago.
Will not open port-forwarding again as long as my Google map works ok.
I still use an older version of Mut to keep using Google maps. Does FA have a Google map option? I have a key for the installs. I would be happy to switch if FA can use Google Maps.