We released PiAware v2.0.7 today, 29 June 2015. If you have auto-update enabled, you can check your stats page to see if you’ve got the release, if not, it will be later today. If you do manual updates, please visit: flightaware.com/adsb/piaware/upgrade
v2.0.7
Decoding bugfix introduced in v2.0.6
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
.
Change connection buffering to avoid triggering Nagle’s algorithm all the time.
v2.0.5
Improve package version reporting.
Improve mlat client logging; propagage client messages back to FlightAware so they appear in the ADS-B stats page log window.
Be more selective about what dump1090 init.d script we pick when trying to restart it.
Use invoke-rc.d to invoke init.d scripts, so we don’t try to start a service that is disabled in the current runlevel.
Use cxfreeze to package the included copy of fa-mlat-client, which should improve portability between Raspbian versions.
Try to use the packaged mlat client if present; fall back to anything on $PATH if it’s not present.
Are there separate deb packages for arm6 and arm7? I ran the update on a Pi 2 and got these errors. Is there anything I should do? Piaware is running after the update.
(Reading database ... 82379 files and directories currently installed.)
Preparing to replace piaware 2.0-7 (using piaware_2.0-7_armhf.deb) ...
Unpacking replacement piaware ...
Setting up piaware (2.0-7) ...
ldconfig: Can't link /usr/lib/arm-linux-gnueabihf/libeatrie.s/.1 to libdatrie.so.1.1.0
ldconfig: /usr/lib/arm-linux-gnueabihf/ is not a symbolic link
ldconfig: Can't link /usr/lib/lmbspandsp/so.2 to libspandsp.so.2.0.0
Processing triggers for man-db ...
Edit: Yes, that’s correct “Preparing to replace piaware 2.0-7 (using piaware_2.0-7_armhf.deb) …”. I ran the update a second time after doing ‘sudo apt-get install -fy’ to see if it would fix the errors, but it didn’t.
There is only one set of binaries, built for arm6 so they should run fine on both the Pi 1 and Pi 2.
The libraries it’s complaining about are completely unrelated to piaware as far as I can tell. I think there is a latent error somewhere else on your system. ldconfig does a system-wide rebuild of the linker cache, so if you have a problem elsewhere then it’ll reappear every time any package runs ldconfig, even if it’s an unrelated package.
(try “sudo ldconfig”, it’ll probably provoke the same error)
[2015-06-29 16:17 PDT] 1680771 msgs recv’d from dump1090 (332 in last 5m); 1675054 msgs sent to FlightAware
[2015-06-29 16:22 PDT] 1681183 msgs recv’d from dump1090 (412 in last 5m); 1675466 msgs sent to FlightAware
[2015-06-29 16:26 PDT] auto update (flightaware-initiated) requested by adept server
[2015-06-29 16:26 PDT] autoUpdate is not set in adept config, looking further…
[2015-06-29 16:26 PDT] autoUpdate in /etc/piaware is enabled, allowing update
[2015-06-29 16:26 PDT] performing auto update, action: piaware
[2015-06-29 16:26 PDT] got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
[2015-06-29 16:26 PDT] considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
[2015-06-29 16:26 PDT] fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 16:26 PDT] got status timeout trying to fetch flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 16:26 PDT] update request complete
[2015-06-29 16:27 PDT] 1681583 msgs recv’d from dump1090 (400 in last 5m); 1675866 msgs sent to FlightAware
[2015-06-29 16:32 PDT] 1681915 msgs recv’d from dump1090 (332 in last 5m); 1676198 msgs sent to FlightAware
[2015-06-29 16:37 PDT] 1682170 msgs recv’d from dump1090 (255 in last 5m); 1676453 msgs sent to FlightAware
[2015-06-29 16:42 PDT] 1682372 msgs recv’d from dump1090 (202 in last 5m); 1676655 msgs sent to FlightAware
[2015-06-29 16:47 PDT] 1682607 msgs recv’d from dump1090 (235 in last 5m); 1676890 msgs sent to FlightAware
[2015-06-29 16:52 PDT] 1682839 msgs recv’d from dump1090 (232 in last 5m); 1677122 msgs sent to FlightAware
[2015-06-29 16:56 PDT] auto update (flightaware-initiated) requested by adept server
[2015-06-29 16:56 PDT] autoUpdate is not set in adept config, looking further…
[2015-06-29 16:56 PDT] autoUpdate in /etc/piaware is enabled, allowing update
[2015-06-29 16:56 PDT] performing auto update, action: piaware
[2015-06-29 16:56 PDT] got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
[2015-06-29 16:56 PDT] considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
[2015-06-29 16:56 PDT] fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 16:56 PDT] got status timeout trying to fetch flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 16:56 PDT] update request complete
[2015-06-29 16:57 PDT] 1683073 msgs recv’d from dump1090 (234 in last 5m); 1677356 msgs sent to FlightAware
[2015-06-29 17:02 PDT] 1683278 msgs recv’d from dump1090 (205 in last 5m); 1677561 msgs sent to FlightAware
[2015-06-29 17:07 PDT] 1683458 msgs recv’d from dump1090 (180 in last 5m); 1677741 msgs sent to FlightAware
[2015-06-29 17:12 PDT] 1683669 msgs recv’d from dump1090 (211 in last 5m); 1677952 msgs sent to FlightAware
[2015-06-29 17:17 PDT] 1683855 msgs recv’d from dump1090 (186 in last 5m); 1678138 msgs sent to FlightAware
[2015-06-29 17:22 PDT] 1683989 msgs recv’d from dump1090 (134 in last 5m); 1678272 msgs sent to FlightAware
[2015-06-29 17:27 PDT] auto update (flightaware-initiated) requested by adept server
[2015-06-29 17:27 PDT] autoUpdate is not set in adept config, looking further…
[2015-06-29 17:27 PDT] autoUpdate in /etc/piaware is enabled, allowing update
[2015-06-29 17:27 PDT] performing auto update, action: piaware
[2015-06-29 17:27 PDT] got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
[2015-06-29 17:27 PDT] considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
[2015-06-29 17:27 PDT] fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 17:27 PDT] got status timeout trying to fetch flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 17:27 PDT] update request complete
[2015-06-29 17:27 PDT] 1684159 msgs recv’d from dump1090 (170 in last 5m); 1678442 msgs sent to FlightAware
[2015-06-29 17:32 PDT] 1684376 msgs recv’d from dump1090 (217 in last 5m); 1678659 msgs sent to FlightAware
[2015-06-29 17:37 PDT] 1684580 msgs recv’d from dump1090 (204 in last 5m); 1678863 msgs sent to FlightAware
[2015-06-29 17:42 PDT] 1684801 msgs recv’d from dump1090 (221 in last 5m); 1679084 msgs sent to FlightAware
[2015-06-29 17:47 PDT] 1685055 msgs recv’d from dump1090 (254 in last 5m); 1679338 msgs sent to FlightAware
[2015-06-29 17:52 PDT] 1685284 msgs recv’d from dump1090 (229 in last 5m); 1679567 msgs sent to FlightAware
[2015-06-29 17:57 PDT] auto update (flightaware-initiated) requested by adept server
[2015-06-29 17:57 PDT] autoUpdate is not set in adept config, looking further…
[2015-06-29 17:57 PDT] autoUpdate in /etc/piaware is enabled, allowing update
[2015-06-29 17:57 PDT] performing auto update, action: piaware
[2015-06-29 17:57 PDT] got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
[2015-06-29 17:57 PDT] considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
[2015-06-29 17:57 PDT] fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 17:57 PDT] got status timeout trying to fetch flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 17:57 PDT] update request complete
[2015-06-29 17:57 PDT] 1685480 msgs recv’d from dump1090 (196 in last 5m); 1679763 msgs sent to FlightAware
[2015-06-29 18:02 PDT] 1685756 msgs recv’d from dump1090 (276 in last 5m); 1680039 msgs sent to FlightAware
[2015-06-29 18:07 PDT] 1686038 msgs recv’d from dump1090 (282 in last 5m); 1680321 msgs sent to FlightAware
[2015-06-29 18:12 PDT] 1686243 msgs recv’d from dump1090 (205 in last 5m); 1680526 msgs sent to FlightAware
[2015-06-29 18:17 PDT] 1686407 msgs recv’d from dump1090 (164 in last 5m); 1680690 msgs sent to FlightAware
[2015-06-29 18:22 PDT] 1686565 msgs recv’d from dump1090 (158 in last 5m); 1680848 msgs sent to FlightAware
[2015-06-29 18:27 PDT] 1686770 msgs recv’d from dump1090 (205 in last 5m); 1681053 msgs sent to FlightAware
[2015-06-29 18:28 PDT] auto update (flightaware-initiated) requested by adept server
[2015-06-29 18:28 PDT] autoUpdate is not set in adept config, looking further…
[2015-06-29 18:28 PDT] autoUpdate in /etc/piaware is enabled, allowing update
[2015-06-29 18:28 PDT] performing auto update, action: piaware
[2015-06-29 18:28 PDT] got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
[2015-06-29 18:28 PDT] considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
[2015-06-29 18:28 PDT] fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 18:28 PDT] got status timeout trying to fetch flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 18:28 PDT] update request complete
[2015-06-29 18:32 PDT] 1686984 msgs recv’d from dump1090 (214 in last 5m); 1681267 msgs sent to FlightAware
[2015-06-29 18:37 PDT] 1687148 msgs recv’d from dump1090 (164 in last 5m); 1681431 msgs sent to FlightAware
[2015-06-29 18:42 PDT] 1687277 msgs recv’d from dump1090 (129 in last 5m); 1681560 msgs sent to FlightAware
[2015-06-29 18:47 PDT] 1687431 msgs recv’d from dump1090 (154 in last 5m); 1681714 msgs sent to FlightAware
[2015-06-29 18:52 PDT] 1687599 msgs recv’d from dump1090 (168 in last 5m); 1681882 msgs sent to FlightAware
[2015-06-29 18:57 PDT] 1687738 msgs recv’d from dump1090 (139 in last 5m); 1682021 msgs sent to FlightAware
[2015-06-29 18:58 PDT] auto update (flightaware-initiated) requested by adept server
[2015-06-29 18:58 PDT] autoUpdate is not set in adept config, looking further…
[2015-06-29 18:58 PDT] autoUpdate in /etc/piaware is enabled, allowing update
[2015-06-29 18:58 PDT] performing auto update, action: piaware
[2015-06-29 18:58 PDT] got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
[2015-06-29 18:58 PDT] considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
[2015-06-29 18:58 PDT] fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 18:58 PDT] got status timeout trying to fetch flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 18:58 PDT] update request complete
[2015-06-29 19:02 PDT] 1687887 msgs recv’d from dump1090 (149 in last 5m); 1682170 msgs sent to FlightAware
[2015-06-29 19:07 PDT] 1688061 msgs recv’d from dump1090 (174 in last 5m); 1682344 msgs sent to FlightAware
[2015-06-29 19:12 PDT] 1688345 msgs recv’d from dump1090 (284 in last 5m); 1682628 msgs sent to FlightAware
[2015-06-29 19:14 PDT] manual update (user-initiated via their flightaware control page) requested by adept server
[2015-06-29 19:14 PDT] manualUpdate is not set in adept config, looking further…
[2015-06-29 19:14 PDT] manualUpdate in /etc/piaware is enabled, allowing update
[2015-06-29 19:14 PDT] performing manual update, action: piaware
[2015-06-29 19:14 PDT] got status ok trying to fetch flightaware.com/adsb/piaware/files/latest
[2015-06-29 19:14 PDT] considering upgrading piaware from flightaware.com/adsb/piaware/fi … rmhf.deb….
[2015-06-29 19:14 PDT] fetching latest piaware version from flightaware.com/adsb/piaware/fi … _armhf.deb
[2015-06-29 19:14 PDT] got status timeout trying to fetch flightaware.com/adsb/piaware/fi … _armhf.deb
I see there was a change from using dump1090 to using faup1090 and to expect a decrease in flights…My question is should I be seeing this much of a difference? Monday is version 2.0.4, Tuesday/Wednesday is 2.0.7. Range has also decreased significantly. http://i.imgur.com/E5P787v.png
(a) you are actually using faup1090 (the piaware version upgrade does not change that, yet). If you are not using faup1090, then the changes don’t affect you;
(b) if you have customized how you run dump1090 at all, check that your changes were not disturbed by the upgrade and you are still running dump1090 in the way that you think;
(c) that your antenna hasn’t fallen down or something (that was the explanation the last time someone reported this !)
I wouldn’t generally expect large changes in aircraft count. You may lose some range density (i.e fewer hits at the edge of your range) because you’re reporting fewer stale positions out there.
edit: also, you only have a couple of days of history on that site and the time-based history shows the traffic is very spiky, it’s hard to conclude much there…
I never changed if I was using faup1090 or dump1090, but piaware-status shows faup1090 not running and dump1090 is running. Does that need to be changed? and if so, how would I force faup1090 to run?
The only thing I have actually changed with how piaware runs is that I installed the flightradar24 feeder application so that I can also feed to flightfeeder.
I checked the antenna yesterday for any issue but I didn’t find anything wrong. Ill check it again today and maybe try putting up a different one to see what happens.
I have this antenna installed right under the flight path for arrivals to San Francisco Airport and adjacent to departures for San Jose Airport. I should be getting a good aircraft count on this installation.
piaware 2.1-1 and a companion release of FlightAware’s version of dump1090 (1.2-1) are available for manual update now.
This update adds support for returning multilateration positions for use / display locally.
It also changes piaware’s behaviour so that faup1090 is always used for message interpretation, even if something is providing data on port 10001, so that a predictable set of translation rules are used.
You can use the “upgrade and restart Piaware” and “upgrade and restart dump1090” manual commands in turn from the ADS-B stats page to do this update if you have allowed manual updates; or you can upgrade by hand using the new packages listed here: flightaware.com/adsb/piaware/install. Auto updates will follow at some point.
Please reboot your piaware system either before or after upgrading. It’s possible that you have multiple, untracked, copies of old piaware versions still running that won’t be stopped automatically by the upgrade; these will interfere with correct operation. Rebooting will sort that out. (And hopefully that bug is fixed for the future)
The returned multilateration results are sent as artificial position messages to localhost port 30004, which should work without changes with a default dump1090 configuration. The results will be forwarded on to anything else connected to dump1090 too.
The updated dump1090 version knows how to display mlat positions differently to regular ones, but there’s otherwise no major changes there; you don’t have to upgrade dump1090 to get the positions, it’s just a display thing. dump1090-mutability (github master) also knows how to display them differently.
You can disable the result forwarding if it interferes with your setup via “piaware-config -mlatResults 0”
piaware changelog:
- Always use the version of faup1090 packaged with piaware to do message
translation from the raw form provided by dump1090 et al; don't rely on
the translation rules provided by anything listening on port 10001.
Pass the receiver location specified via the FlightAware website to
faup1090 so that it is available for position decoding.
Update fa-mlat-client to support display of multilateration results
returned from the FlightAware servers. The default configuration will
convert these results to synthetic Beast-format messages and pass them
to the local dump1090 on port 30004 for display on the local map.
This may be disabled by “piaware-config -mlatResults 0”.
Report CPU load in periodic health messages.
Preserve the timestamp that faup1090 provides in aircraft updates; this
may be some time in the past if the report used older data. Separately
report the time that the report was forwarded to FlightAware. This helps
the FlightAware servers put the right time information on reports that
have slightly stale (up to 30s old) data.
Tweaks to piaware’s self-restart to hopefully be more robust and avoid
leaving duplicate piaware processes around.
dump1090 changelog:
- Identify incoming multilateration results from fa-mlat-client and
color those aircraft differently in the side table.
Disable the FATSV port by default. piaware 2.1 uses its own copy
of faup1090 to do FATSV translation.
Static link librtlsdr and don’t ship a separate copy. This makes this
dump1090 package play more nicely with other packages that want to
provide librtlsdr.
Sorry if I missed something. Are you now developing Piaware? Is Piaware dump1090 now dump1090-mutability? Just wondering why you are making this announcement. Thanks.
There’s a bunch of background here: ads-b-flight-tracking-f21/mlat-on-pi-t20106.html
Nothing really changed; you still can’t do mlat on a Pi with a dongle (at least, not very well) by using the system clock. But you can avoid using the system clock by using ADS-B-equipped aircraft as reference beacons, and that works pretty well.
If you’re feeding VRS from dump1090 then VRS will get a copy of the positions that are fed back to dump1090, nothing special needed. The only thing is you won’t easily be able to distinguish them from non-mlat positions.
If you want a separate feed, fa-mlat-client will do that, but there’s currently no way to configure piaware to start fa-mlat-client with a different config. If you really want this you can edit /usr/lib/piaware/mlat.tcl and change how fa-mlat-client is invoked in the start_mlat_client proc. You’ll probably want to pass something like “–results basestation,connect,vrshost:12345”. This will eventually be configurable somewhere easier, it just didn’t make it into this release. If you do that you probably want to remove the beast-mode connection to dump1090 too so you only get one copy of the positions. Finally, if you use a recent VRS (possibly only in the preview releases) there is a multilateration feed option that is useful to tell VRS that it’s going to get only positions from the feed and it should merge those with other data from other feeds.
(I’ve had a report that the basestation feed when fed from FA doesn’t work with VRS, so there may be a bug to resolve in there too. The beast-format feed might work)
