Why do you use dump1090-mutability?

[paulg1953]

Thanks, it was the direct feed from an Rpi I was referring to

[SoNic67]

@abcd567

However feeding PlanePlotter Site is possible without installing PP software on Windows.

Why would you do that?

[abcd567]

@SoNic67

Why would you do that?

Same reason as for feeding all other sites.

[zymucicp]

+1 dump1090-mutability in the case of use with OpenWrt/LEDE and with different linux distribution as ArchLinux.

[zymucicp]

@obj, as already mentioned in this thread the OpenWRT/LEDE build of dump1090 actually uses this as source.

The problem of switching to dump1090-fa is that the db folder is generally too big (>12Mb) for most of the router’s flash memory. Could be there any solution, as for example manually using a reduced version of the db?

[obj]

Sure, it should run fine without the DB, you can probably just omit the whole db directory. Or there are scripts under tools/ that let you regenerate the DB with whatever data you want (I don’t know how you’d pick what to include though)

[thespeedycab]

Hi abcde567
Thanks for your contributions. I provide data to FR24 and FA. Out of the reasons you list numbers 1, 2 and 4 apply to me.
The steps you are providing for uninstall of dump1090-mutalibility and install of dump1090-fa, will that continue to provide data to FR24 as well as FA ? Can I safely do this will maintaining FR24 feed (http://192.168.86.251:8754/index.html)?
thx

[abcd567]

@thespeedycab

First you have to tell us what is your software:

Pi24 image + installed FA feeder
OR
Raspbian image + installed FR24 and FA feeders
OR
Something else

[thespeedycab]

@abcd567
Aha. Good point, if not a critical one.
I have RPI with Raspian image and dump1090-mutability v1.15 installed. Then I added the FR24 feeder and the FA feeder.

[abcd567]

@thespeedycab

The steps you are providing for uninstall of dump1090-mutalibility and install of dump1090-fa, will that continue to provide data to FR24 as well as FA ? Can I safely do this will maintaining FR24 feed

Yes, the method to replace dump1090-mutability by dump1090-fa is safe and wont break the feeds to FR24 and FA.

However when the method was posted, the current version for dump1090-fa was 3.6.2, while now it is 3.6.3. I am therefore repeating the method with latest version number 3.6.3 below:

1 - Uninstall dump1090-mutability

1.1 - Purge installed dump1090-mutability

sudo dpkg --purge dump1090-mutability

1.2 - The dpkg --purge command removes all files and configuration of dump1090-mutability, making system clean. However it fails to remove one folder (/usr/share/dump1090-mutability) because the folder is not empty. This is not a problem. Manually remove it by command below.

sudo rm -rf /usr/share/dump1090-mutability

.

2 - Install dump1090-fa

wget http://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_3.6.3_all.deb

sudo dpkg -i piaware-repository_3.6.3_all.deb

sudo apt-get update

sudo apt-get install dump1090-fa

sudo reboot

.

[Randstad]

Does changing to dump1090-fa break statistics of The ADS-B Receiver Project?

[abcd567]

I have tested this method long ago. Dont remember well about adsb-receiver project stats, but if I recall correctly, in one of configuration files of collectd, I had to change dump1090 to dump1090-fa.

EDIT: found it

ADS-B Receiver Project Setup Scripts

Change " URL “http://localhost/dump1090” " to " URL “http://localhost/**dump1090-fa**” " in /etc/collectd/collectd.conf. Restart the service collectd. Look at your graphs or make ls -lsa /var/lib/collectd/rrd/localhost/dump1090-localhost. Just tried it, because I’ve seen that the /data/stats.json still exist at the 3.0.3 image and this is where collectd gets the data. It’s working here… HTH

[abcd567]

@Randstad

Thanks to @GeorgLichtblau for finding this in August 2016

Open file collectd.conf for editing

sudo nano /etc/collectd/collectd.conf

Press ctrl+w and type
module dump1090

Press Enter key, the cursor will jump to line:

    <Module dump1090>
            <Instance localhost>
                    URL "http://localhost/dump1090"
            </Instance>
    </Module>

Add -fa after dump1090 as shown below

    <Module dump1090>
            <Instance localhost>
                    URL "http://localhost/dump1090-fa"
            </Instance>
    </Module>

Save the file, exit and restart collectd module

sudo service collectd restart

[Randstad]

@abcd567
Great, thanks! Will give it a try

[Me109]

Familiarity for me.

My receiver setup was running unchanged for a couple of years; Piaware 3.5.3, and dump1090-mutability in --net-only fed by Airspy. Piaware and dump1090 were on a Pi 2, and Airspy a Pi3. Last week I finally spent time moving everything to the Pi3. Not being involved for awhile I forgot many of the nuances. I went through several different builds: apt-get Piaware and dump1090-fa, Piaware SD, ADSBexchange scripts, then ADSB-receiver scripts.

Ultimately what worked for me was the familiarity with dump1090-mutability…in the little time I wanted to spend on this project it wasn’t clear to me how to tweak dump1090-fa in the same manner as dump1090-mutability (eg simply edit the config file or run thru sudo dpkg dump1090-reconfigure). That’s not to say it isn’t there, I just didn’t/don’t want to invest the time right now to figure it out…it all works and I’m satisfied.

[thespeedycab]

At the FR24 forum you wrote a nice detailed install instructions for set up of the dump1090-mutability v1.15-dev. I am looking for something like that here, but can’t find it.
Is it just as simple as described on: https://flightaware.com/adsb/piaware/install ?
And then add the FR24 flightfeeder ?
Apologies for my ignorance or if I overlooked it

[wiedehopf]

You can configure FR24 as described in the thread over at FR24 or here Bake a Pi

The installation of dump1090-fa and piaware you can just do as described on the install page you linked.

You will need to either deactivate or remove dump1090-mutability.
sudo apt-get remove dump1090-mutability
You might also need to run:

sudo lighty-disable-mod dump1090

Those two only apply if you had dump1090-mutability installed before.
If FR24 is already installed and configured to get data on port 30005 there is no need to change anything.

[thespeedycab]

@wiedehopf Great. Thanks! As always

[abcd567]

The sad demise of an old faithful…

github > mutability > dump1090 > branch master - 5 days ago:

https://github.com/mutability/dump1090/blob/master/README.md

Old dump1090-mutability fork

dump1090-mutability is no longer maintained; please don’t use it for new installs.

For new installs and ongoing development, try dump1090-fa, which is available at GitHub - flightaware/dump1090: Dump1090 is a simple Mode S decoder for RTLSDR devices

The historical master branch is available in the unmaintained branch.

[abcd567]

Russians are still keen to use dump1090-mutability, and strangely prefer ver 1.14 over 1.15~dev or dump1090-fa.

Below is the translation (from Russian to English) of an interesting discussion on this topic dated yesterday:

Member Madlzz’spost:

installed 1.14 - and there google maps dev. And where to google api key?

.
My Reply to Madlzz:

Why v 1.14? It has an outdated decoder, is not able to handle Flightaware feedback and requires a Google Key.

Install version 1.15 ~ dev. It has an advanced decoder, supports mlat and does not require Google Key, as it uses OpenStreet Map.

.

Reply to my post by Senior Member ffa1978 :

“It has an outdated decoder, is not able to handle Flightaware feedback and requires a Google Key.”

you know, if you didn’t make a comparison, it’s better to keep silent. We did it. And not only me, with normalized dividers and the same receivers. For all its obsolescence, there is a better decoder than in 1.15. Due to a more simplified validation check, the reception is better. Yes more messages are broken , but they are filtered out by a mixer or vrs. Well, the version from fa is just rubbish. Aggressive mode is off, a hard validation check - all this can of course be corrected in the source (the same agressive), but even with editing it is worse than everyone. By the way, the last 1.14 the same thing went with agre off with the mode in the code in the source code (more precisely, the condition is applied that the recovered messages do not go to the network with the key Modes.net_verbatim = 1, it was corrected apparently for the sake of fa.

Here is this wonderful edit to dump1090.c made in 2018. It is strongly recommended to remove Modes. Net_Verbatim

} else if (! strcmp (argv [j], "- aggressive")) {

#ifdef ALLOW_AGGRESSIVE
Modes.nfix_crc = MODES_MAX_BITERRORS;
Modes.net_verbatim = 1;
#else
fprintf (stderr,  "warning: --aggressive not supported in this build, option ignored. \ n");
#endif
@@ -1034.6 +1034.7 @@ int main (int argc, char ** argv) {

.

+++
“It has an advanced decoder, supports mlat and does not require Google Key”

I only agree with the latter. The decoder is worse, MLAT is perfectly supported by version 1.14 as well.

+++
“unable to handle Flightaware feedback”

port 30104 is also open there. No need to say if you do not know

+++
“First uninstall version 1.14”

we have no problems in Russia with Google keys except the Crimea. We don’t need to delete anything

+++

“It has an advanced decoder”

doesn’t have