What is Easiest Way To Install Dump1090-Mutability

[mgunther]

@obj

I’ve been slack on the packaging/release front because it’s a lot of effort to sort out for not much reward; doing user support is really not my idea of fun.
There’s plenty of development going on, you just have to build it yourself.

I was able to build and install the latest version myself by doing the following:

Edit 2nd Jan 2016: Member jprochazka has created a set of setup scripts that automate many essential decoder and feeder installations, including dump1090-mutability. More details here: ADS-B Feeder Project Setup Scripts

**Edit 2nd Jan 2016: ** On Orange Pi’s there are additional steps that need to be taken first. Thanks to abcd567 for working this out!

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ca-certificates
sudo apt-get install git
sudo apt-get install build-essential
sudo apt-get install cron

Edit 2nd Aug 2015: On a brand-new Pi (with Wheezy Raspbian) where nothing else is installed yet you will need to get some libraries for the dongle first. If you already have a version of dump1090 running successfully, then you don’t need to install them. Also, Jessie Raspbian seems to include these libraries and you probably don’t have to install them again.

~ $ wget https://github.com/mutability/librtlsdr/releases/download/v0.5.4_git-1/librtlsdr0_0.5.4.git-1_armhf.deb
~ $ wget https://github.com/mutability/librtlsdr/releases/download/v0.5.4_git-1/librtlsdr-dev_0.5.4.git-1_armhf.deb
~ $ sudo dpkg -i librtlsdr0_0.5.4.git-1_armhf.deb
~ $ sudo dpkg -i librtlsdr-dev_0.5.4.git-1_armhf.deb

Install git software if not already present on the system:

pi@raspberrypi ~ $ sudo apt-get install git-core

Make a git directory in your home directory and change into it:

pi@raspberrypi ~ $ mkdir git
pi@raspberrypi ~ $ cd git

Clone the repository to the pi:

pi@raspberrypi ~/git $ git clone https://github.com/mutability/dump1090.git

Install some more required packages:

pi@raspberrypi ~/git $ sudo apt-get install librtlsdr-dev libusb-1.0-0-dev pkg-config debhelper

Build the package from the cloned source on the pi. Need to be in the correct directory (dump1090):

pi@raspberrypi ~/git $ cd dump1090
pi@raspberrypi ~/git/dump1090 $ dpkg-buildpackage -b

The above will take a few minutes and if all goes to plan, should produce a package file:
~/git/dump1090-mutability_1.15~dev_armhf.deb (or whatever the latest version is)

Install the new dump1090-mutability package:

pi@raspberrypi ~/git/dump1090 $ cd ..
pi@raspberrypi ~/git $ sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

Edit 25th December 2015.
It is recommended to disable the in-built web server of dump1090 and run a “proper” web server instead.

Reconfigure dump1090-mutability and enter “0” for the html port number (this disables the in-built web server):

pi@raspberrypi ~ $ sudo dpkg-reconfigure dump1090-mutability

Install lighttpd webserver and make dump1090 available:

pi@raspberrypi ~ $ sudo apt-get install lighttpd
pi@raspberrypi ~ $ sudo lighty-enable-mod dump1090
pi@raspberrypi ~ $ sudo /etc/init.d/lighttpd force-reload

dump1090-mutability web interface will now be available here: ](http://)/dump1090/

Whenever OBJ makes updates to the source, the process to update dump1090-mutability will be the following:

Update the local repository:

pi@raspberrypi ~/git/dump1090 $ git pull

Build and install same as previously:

pi@raspberrypi ~/git/dump1090 $ dpkg-buildpackage -b
pi@raspberrypi ~/git/dump1090 $ cd ..
pi@raspberrypi ~/git $ sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

(replacing the version number as required)

I hope that my notes are accurate. I did not try an uninstall yet, so don’t know how that would be done.

[tjowen]

@mgunther

@obj

I’ve been slack on the packaging/release front because it’s a lot of effort to sort out for not much reward; doing user support is really not my idea of fun.
There’s plenty of development going on, you just have to build it yourself.

I was able to build and install the latest version myself by doing the following:

Install git software if not already present on the system:

pi@raspberrypi ~ $ sudo apt-get install git-core

Make a git directory in your home directory and change into it:

pi@raspberrypi ~ $ mkdir git
pi@raspberrypi ~ $ cd git

Clone the repository to the pi:

pi@raspberrypi ~/git $ git clone https://github.com/mutability/dump1090.git

Install some more required packages:

pi@raspberrypi ~/git $ sudo apt-get install librtlsdr-dev libusb-1.0-0-dev pkg-config debhelper

Build the package from the cloned source on the pi. Need to be in the correct directory (dump1090):

pi@raspberrypi ~/git $ cd dump1090
pi@raspberrypi ~/git/dump1090 $ dpkg-buildpackage –b

The above will take a few minutes and if all goes to plan, should produce a package file:
~/git/dump1090-mutability_1.15~dev_armhf.deb (or whatever the latest version is)

Install the new dump1090-mutability package:

pi@raspberrypi ~/git $ sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

I’m now running version v1.15~dev

Whenever OBJ makes updates to the source, I think the process will be the following:

Update the local repository:

pi@raspberrypi ~/git/dump1090 $ git pull

Build and install same as previously:

pi@raspberrypi ~/git/dump1090 $ dpkg-buildpackage –b
pi@raspberrypi ~/git $ sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

(replacing the version number as required)

I hope that my notes are accurate. I did not try an uninstall yet, so don’t know how that would be done.

Thank you mgunther, your instructions worked perfectly for me.
…Tom

[obj]

@tjowen

When stepping through the Dump1090-mutability reconfigure remember the following unless this no longer applies to the new piaware…
…Tom

Important: You must configure NET_BIND_ADDRESS=“”, or equivalently enter a blank answer to the “Interface address to bind to?” configuration question, to avoid a bug in piaware that will make piaware think that there is no dump1090 running.

This is fixed in current piaware so you no longer need that workaround.

[obj]

@mgunther

I did not try an uninstall yet, so don’t know how that would be done.

“apt-get remove dump1090-mutability” will do the trick.

Your notes look good to me - that’s basically how I do my builds while developing.

[tjowen]

@obj

@tjowen

When stepping through the Dump1090-mutability reconfigure remember the following unless this no longer applies to the new piaware…
…Tom

Important: You must configure NET_BIND_ADDRESS=“”, or equivalently enter a blank answer to the “Interface address to bind to?” configuration question, to avoid a bug in piaware that will make piaware think that there is no dump1090 running.

This is fixed in current piaware so you no longer need that workaround.

Thank you for confirming the fix is in…

[obj]

@Adraenyse

Can I get some clarification:

v2.0.6
Use faup1090 from dump1090-mutability. As dump1090-mutability makes many decoding decisions differently to the previous version of faup1090, and there are additional changes to the rules for when positions are emitted, you may see decreases in the number of positions recorded by FlightAware, but data will be more accurate.

If you’re running 2.0-7, aren’t you already using dump1090-mutability?

piaware 2.0-7 includes a version of faup1090 which uses the same Mode S decoding logic that dump1090-mutability uses.

faup1090 is purely a message translator, it takes raw demodulated mode S messages from dump1090 or other software, interprets those messages, and converts those messages to the form that piaware wants (which is a summary of aircraft state per aircraft with periodic updates). It doesn’t have the RF frontend, demodulator, web interface, etc that dump1090 has.

Previously, faup1090 was built on top of dump1090_mr - the change here is to build it on top of dump1090-mutability to pick up a bunch of decoding improvements/bugfixes.

[obj]

It’s on the cards but I don’t have a concrete timeline.

[MikeConnors]

@tjowen

@mgunther

@obj

I’ve been slack on the packaging/release front because it’s a lot of effort to sort out for not much reward; doing user support is really not my idea of fun.
There’s plenty of development going on, you just have to build it yourself.

I was able to build and install the latest version myself by doing the following:

Install git software if not already present on the system:

pi@raspberrypi ~ $ sudo apt-get install git-core

Make a git directory in your home directory and change into it:

pi@raspberrypi ~ $ mkdir git
pi@raspberrypi ~ $ cd git

Clone the repository to the pi:

pi@raspberrypi ~/git $ git clone https://github.com/mutability/dump1090.git

Install some more required packages:

pi@raspberrypi ~/git $ sudo apt-get install librtlsdr-dev libusb-1.0-0-dev pkg-config debhelper

Build the package from the cloned source on the pi. Need to be in the correct directory (dump1090):

pi@raspberrypi ~/git $ cd dump1090
pi@raspberrypi ~/git/dump1090 $ dpkg-buildpackage –b

The above will take a few minutes and if all goes to plan, should produce a package file:
~/git/dump1090-mutability_1.15~dev_armhf.deb (or whatever the latest version is)

Install the new dump1090-mutability package:

pi@raspberrypi ~/git $ sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

I’m now running version v1.15~dev

Whenever OBJ makes updates to the source, I think the process will be the following:

Update the local repository:

pi@raspberrypi ~/git/dump1090 $ git pull

Build and install same as previously:

pi@raspberrypi ~/git/dump1090 $ dpkg-buildpackage –b
pi@raspberrypi ~/git $ sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

(replacing the version number as required)

I hope that my notes are accurate. I did not try an uninstall yet, so don’t know how that would be done.

Thank you mgunther, your instructions worked perfectly for me.
…Tom

post177419.html#p177419

All goes well until I try and build the .deb package. I get the following:

pi@na5ss-3 ~/git/dump1090 $dpkg-buildpackage –b
dpkg-buildpackage: unknown option or argument –b

Usage: dpkg-buildpackage …]

Options:
-F (default) normal full build (binaries and sources).
-b binary-only, do not build source.
-B binary-only, no arch-indep files.
-A binary-only, only arch-indep files.
-S source only, no binary files.
-nc do not clean source tree (implies -b).
-tc clean source tree when finished.
-D (default) check build dependencies and conflicts.
-d do not check build dependencies and conflicts.
-R rules file to execute (default is debian/rules).
-T call debian/rules with the proper environment.
–as-root ensure -T calls the target with root rights.
-j] specify jobs to run simultaneously (passed to ).
-r
command to gain root privileges (default is fakeroot).
-p
command to sign .dsc and/or .changes files (default is gpg).
-k the key to use for signing.
-ap add pause before starting signature process.
-us unsigned source package.
-uc unsigned .changes file.
–admindir=
change the administrative directory.
-?, --help show this help message.
–version show the version.

Options passed to dpkg-architecture:
-a Debian architecture we build for.
-t set GNU system type.

Options passed to dpkg-genchanges:
-si (default) source includes orig if new upstream.
-sa uploaded source always includes orig.
-sd uploaded source is diff and .dsc only.
-v changes since version .
-m maintainer for package is .
-e maintainer for release is .
-C changes are described in .
–changes-option=
pass option to dpkg-genchanges.

Options passed to dpkg-source:
-sn force Debian native source format.
-s[sAkurKUR] see dpkg-source for explanation.
-z compression level to use for source.
-Z compression to use for source (gz|xz|bzip2|lzma).
-i] ignore diffs of files matching regex.
-I] filter out files when building tarballs.
–source-option=
pass option to dpkg-source.

Any suggestions?

Thanks, Mike

[mighty3507]

All goes well until I try and build the .deb package. I get the following:

pi@na5ss-3 ~/git/dump1090 $dpkg-buildpackage –b
dpkg-buildpackage: unknown option or argument –b

Usage: dpkg-buildpackage …]

Any suggestions?

Thanks, Mike

Did you cut and past the command? I ran into the same problem when cutting and pasting. I manually typed the command and it ran without any issues.

–Steve

[beckerm13]

@mighty3507

All goes well until I try and build the .deb package. I get the following:

pi@na5ss-3 ~/git/dump1090 $dpkg-buildpackage –b
dpkg-buildpackage: unknown option or argument –b

Usage: dpkg-buildpackage …]

Any suggestions?

Thanks, Mike

Did you cut and past the command? I ran into the same problem when cutting and pasting. I manually typed the command and it ran without any issues.

–Steve

I had the same issue. I deleted the dash from the -b and typed my own dash and the problem went away.

Marty

[wnypoker]

@ki7ab

@tjowen

post177419.html#p177419

All goes well until I try and build the .deb package. I get the following:

pi@na5ss-3 ~/git/dump1090 $dpkg-buildpackage –b
dpkg-buildpackage: unknown option or argument –b

Usage: dpkg-buildpackage …]

Options:
-F (default) normal full build (binaries and sources).
-b binary-only, do not build source.
-B binary-only, no arch-indep files.
-A binary-only, only arch-indep files.
-S source only, no binary files.
-nc do not clean source tree (implies -b).
-tc clean source tree when finished.
-D (default) check build dependencies and conflicts.
-d do not check build dependencies and conflicts.
-R rules file to execute (default is debian/rules).
-T call debian/rules with the proper environment.
–as-root ensure -T calls the target with root rights.
-j] specify jobs to run simultaneously (passed to ).
-r
command to gain root privileges (default is fakeroot).
-p
command to sign .dsc and/or .changes files (default is gpg).
-k the key to use for signing.
-ap add pause before starting signature process.
-us unsigned source package.
-uc unsigned .changes file.
–admindir=
change the administrative directory.
-?, --help show this help message.
–version show the version.

Options passed to dpkg-architecture:
-a Debian architecture we build for.
-t set GNU system type.

Options passed to dpkg-genchanges:
-si (default) source includes orig if new upstream.
-sa uploaded source always includes orig.
-sd uploaded source is diff and .dsc only.
-v changes since version .
-m maintainer for package is .
-e maintainer for release is .
-C changes are described in .
–changes-option=
pass option to dpkg-genchanges.

Options passed to dpkg-source:
-sn force Debian native source format.
-s[sAkurKUR] see dpkg-source for explanation.
-z compression level to use for source.
-Z compression to use for source (gz|xz|bzip2|lzma).
-i] ignore diffs of files matching regex.
-I] filter out files when building tarballs.
–source-option=
pass option to dpkg-source.

Any suggestions?

Thanks, Mike

The same thing happened to me. I just used dpkg-buildpackage without the -b option and it worked.

[MikeConnors]

@beckerm13

@mighty3507

All goes well until I try and build the .deb package. I get the following:

pi@na5ss-3 ~/git/dump1090 $dpkg-buildpackage –b
dpkg-buildpackage: unknown option or argument –b

Usage: dpkg-buildpackage …]

Any suggestions?

Thanks, Mike

Did you cut and past the command? I ran into the same problem when cutting and pasting. I manually typed the
command and it ran without any issues.

–Steve

I had the same issue. I deleted the dash from the -b and typed my own dash and the problem went away.

Marty

Yes, I cut and paste. I’ll give it a try.

Thanks!

Mike

[mgunther]

@beckerm13

@mighty3507

Did you cut and past the command? I ran into the same problem when cutting and pasting. I manually typed the command and it ran without any issues.

–Steve

I had the same issue. I deleted the dash from the -b and typed my own dash and the problem went away.

Marty

Yes, quite possibly MS Word playing tricks here. I edited the original post and put in a correct dash for the -b part.

[Frazpo]

@mgunther

@obj

I’ve been slack on the packaging/release front because it’s a lot of effort to sort out for not much reward; doing user support is really not my idea of fun.
There’s plenty of development going on, you just have to build it yourself.

I was able to build and install the latest version myself by doing the following:

Install git software if not already present on the system:

pi@raspberrypi ~ $ sudo apt-get install git-core

Make a git directory in your home directory and change into it:

pi@raspberrypi ~ $ mkdir git
pi@raspberrypi ~ $ cd git

Clone the repository to the pi:

pi@raspberrypi ~/git $ git clone https://github.com/mutability/dump1090.git

Install some more required packages:

pi@raspberrypi ~/git $ sudo apt-get install librtlsdr-dev libusb-1.0-0-dev pkg-config debhelper

Build the package from the cloned source on the pi. Need to be in the correct directory (dump1090):

pi@raspberrypi ~/git $ cd dump1090
pi@raspberrypi ~/git/dump1090 $ dpkg-buildpackage -b

The above will take a few minutes and if all goes to plan, should produce a package file:
~/git/dump1090-mutability_1.15~dev_armhf.deb (or whatever the latest version is)

Install the new dump1090-mutability package:

pi@raspberrypi ~/git $ sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

I’m now running version v1.15~dev

Whenever OBJ makes updates to the source, I think the process will be the following:

Update the local repository:

pi@raspberrypi ~/git/dump1090 $ git pull

Build and install same as previously:

pi@raspberrypi ~/git/dump1090 $ dpkg-buildpackage -b
pi@raspberrypi ~/git $ sudo dpkg -i dump1090-mutability_1.15~dev_armhf.deb

(replacing the version number as required)

I hope that my notes are accurate. I did not try an uninstall yet, so don’t know how that would be done.

I upgraded however I have no data getting to the web interface. It appears I am feeding to FA and shows running ok.
I have the interface but it shows “unknown version” now and the ajax error stating dump1090 not running.
Ideas. novice here.

[mgunther]

How did you answer the configuration questions? Did you disable the internal dump1090 web server? What address do you type into your browser for the dump1090 web page?

[Frazpo]

@mgunther

How did you answer the configuration questions? Did you disable the internal dump1090 web server? What address do you type into your browser for the dump1090 web page?

I went ahead and reverted to the piaware sd card load. Going to start fresh on another card with a mutability version.

To answer your question I entered nothing on the internal web server option. Should I have entered a port? I dont remember doing that in previous loads.

[mgunther]

Well it depends what you want to do: you can use the internal dump1090 web server and you need to specify a port during configuration. However, it is recommended to install a separate web server and disable the internal dump1090 web server (i.e. specify port 0).

See the first post here for a suggested web server install:
ads-b-flight-tracking-f21/raspbian-ubuntu-packages-for-dump1090-mutability-available-t19619.html?hilit=dump1090%20mutability

[Frazpo]

@mgunther

Well it depends what you want to do: you can use the internal dump1090 web server and you need to specify a port during configuration. However, it is recommended to install a separate web server and disable the internal dump1090 web server (i.e. specify port 0).

See the first post here for a suggested web server install:
ads-b-flight-tracking-f21/raspbian-ubuntu-packages-for-dump1090-mutability-available-t19619.html?hilit=dump1090%20mutability

I was confused about this in the beginning when installing mutability the first time. I was using the interface on the Pi itself <ip/dump1090>
It ended up at the gmap.html address.

So is the stock piaware dump1090 as good as dump1090-mutability? I had read where it was basicially the same now.
If not is it possible to install mutability on top of the piaware sd image?

[mgunther]

Yes I believe that some improvements that originated in the mutability version have now been incorporated into stock FA version. The FA version will now also show MLAT positions.
So if perhaps you are not that familiar with Linux, don’t care under which user account dump1090 runs or where it writes it’s log files to and don’t always need the latest (unsupported) development versions of everything, then stock FA dump1090 would be a better fit for you.

[LCOVA76]

What is actually the benefit of installing dump1090 mutability over installing the latest PiAware??

I’m going to install and configure a new Rpi and havent decided which way to go…
Do the step by step (Fresh Raspbian + Mutability + Flightaware, Flightradar and Planefnder clients)
or install the latest Piaware software and after that install the FR24 and PF clients…

What are the pros of installing mutability??