This morning i seen in my system (Debian 10), that a new version of Dump1090, the 3.8.0 is ready to be installed on my Pi4 !
I have installed it, and all run as normal for the moment !
I have seen in the changelog that now we can use the 2 bits corrected messages, that’s great, but how do that, where to put the --net-verbatim option ?
I do not understand if i need to use too the --fix option too ?
If you are using a package install, then options can be specified in /etc/default/dump1090-fa
To enable 2-bit correction (do you really want this?) include --fix --fix in the options.
By default these 2-bit-corrected messages will not be emitted to any network clients. If you do want to pass them on, then either the client should enable verbatim mode on that connection (this requires changes to the client) or you can pass the --net-verbatim option to turn on verbatim mode for all connections. In verbatim mode, the original uncorrected message is sent to the network - the downstream client is then responsible for applying error correction if desired. So either way, there’s probably some work needed in other software if you want it to handle these messages.
piaware and faup1090 in 3.8.0 are verbatim-mode-aware, so you don’t need to do anything special there - but note that they make a deliberate decision not to use 2-bit corrected messages.
but for buster 10/piaware it didnt (pi main)
[2020-01-03 10:07 GMT] performing manual update, action: piaware
[2020-01-03 10:07 GMT] *** running command ‘/usr/lib/piaware/helpers/run-apt-get update’ and logging output
[2020-01-03 10:07 GMT] manual update (user-initiated via their flightaware control page) requested by adept server
[2020-01-03 10:07 GMT] skipping action piaware
[2020-01-03 10:07 GMT] run-apt-get(22306): Automatic updates not available for OS raspbian:10 (Raspbian GNU/Linux 10 (buster))
[2020-01-03 10:07 GMT] child process 22306 exited with status EXIT 1
[2020-01-03 10:09 GMT] 409070 msgs recv’d from dump1090-fa (4502 in last 5m); 407835 msgs sent to FlightAware
piaware 3.7.2 doesn’t know how to auto-upgrade on buster (note that 3.7.2 on buster isn’t officially supported…), and if you installed the stretch version then a command-line upgrade will upgrade to the 3.8.0~bpo9 stretch version, not the 3.8.0 buster version. You’ll probably want to rerun the package install instructions to pick up the buster repository package (but wait a few days first - the website is not updated for that yet)
edit: try this (instructions are specifically for Buster, don’t do this on Stretch)