FlightAware is proud to announce the launch of PiAware 3.8.0! This version provides support for the Raspberry Pi 4.
Major release highlights:
Buster support; sdcard image is now based on Buster; Pi 4 support.
Changes to handling of noisy data; additional messages are required before aircraft are considered to be reliably tracked. This will affect site statistics (notably “Other” aircraft counts) for some sites.
Wheezy is EOL and packages are no longer built for it. Please reimage with Buster.
New Buster sdcard images now configure the network using the upstream style of having dhcpcd control everything. Existing sdcard images are unaffected.
USB removable media is no longer automounted.
The “flightaware-user” and “flightaware-password” configuration options are no longer used; please use the normal site-claiming mechanisms to associate sites with a FlightAware account.
The usual bugfixes and small feature additions
FAQ: (I’ll add to this as things come up)
“I installed the PiAware 3.7.2 packages on Raspbian Buster, how do I upgrade to 3.8.0?”
You will need to manually install the Buster piaware-repository package to ensure that you get the Buster packages:
What is the output of last command? (post only the first 3 lines of output)
cd piaware_builder
git pull
git log
Before git pull, I got
$ cd piaware_builder
$ git log
commit f6ab1594567cf3cf1ed3252278a6cd1f0084702a (HEAD -> dev, origin/dev)
Author: Oliver Jowett <oliver@mutability.co.uk>
Date: Thu Nov 28 13:41:46 2019 +0800
Add a rule for building on Ubuntu disco per report on the forums
commit 1eab80a8fc7b41bfd2911adb5707621e7a13e274
Merge: 8539fb0 b58f98f
Author: Oliver Jowett oliver@mutability.co.uk
Date: Mon Dec 30 12:29:34 2019 +0800
Merge branch 'dev' into staging
commit b58f98f05b8706dc673c6dea0cc8b915d15bb7d1
Author: Oliver Jowett oliver@mutability.co.uk
Date: Mon Dec 30 12:26:28 2019 +0800
sensible-build.sh restructuring:
remove the ubuntu-specific overrides in favor of using overrides from the underlying debian version
remove some duplication
:
If you want we can discuss this on the Linux x86 thread, so we don’t pollute this?
In 3.8.0, if a static IP address is configured in /boot/piaware-config.txt, e.g. “wired-type static” or “wireless-type static”, you will encounter a typo that causes the static network configuration to fail.
Fix: edit line 99 of /usr/lib/piaware-support/generate-network-config from
lappend dhcpcd “static ip_address=[[$config get ${net}-address]”
to
lappend dhcpcd “static ip_address=[$config get ${net}-address]”
The single-message thing is a likely consequence of some changes to how dump1090 decides which messages to accept early on in the lifetime of an aircraft track. I didn’t see that effect here, but your environment is probably very different to mine. Do you see any change in effective range, or in “real aircraft” (with position) counts?
no issues with the range, it’s the same i had before. Also the number of aircraft with position did not change significantly.
The only thing which has been increased together with the “single message tracks” is the number of messages and positions/sec (RHS) which went up by approx 10-15%.
This is how it looked yesterday after the upgrade (ignore the short period before, there the gain was set to “-10”)
