FlightAware Discussions

Airspy_adsb and the PiAware 5.0 update

Just a note of caution for Airspy feeders who run the Debian Package Add-on and who have not upgraded yet - based on my own dumb mistake…

If you do the upgrade via apt upgrade, do not answer Y when asked about Configuration file ‘/etc/default/dump1090-fa’:

Preparing to unpack .../09-dump1090-fa_5.0_armhf.deb ...
Unpacking dump1090-fa (5.0) over (4.0) ...
Preparing to unpack .../10-piaware_5.0_armhf.deb ...
Unpacking piaware (5.0) over (4.0) ...
Preparing to unpack .../11-piaware-repository_5.0_all.deb ...
Unpacking piaware-repository (5.0) over (4.0) ...
Setting up chromium-codecs-ffmpeg-extra (88.0.4324.187-rpt1) ...
Setting up piaware-repository (5.0) ...
Setting up python3-pygments (2.3.1+dfsg-1+deb10u1) ...
Setting up dump1090-fa (5.0) ...

Configuration file '/etc/default/dump1090-fa'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** dump1090-fa (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/default/dump1090-fa ...

Configuration file '/etc/lighttpd/conf-available/89-dump1090-fa.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** 89-dump1090-fa.conf (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/lighttpd/conf-available/89-dump1090-fa.conf ...
The user `dump1090' is already a member of `plugdev'.
Enabling lighttpd skyaware module..
Enabling skyaware: ok
Run "service lighttpd force-reload" to enable changes
Restarting lighttpd..

This overwrites the airspy_adsb specific changes to the dump1090-fa config file and puts your feeder off the air.

It took me a while to work out what I had done. If you end up in this position, you need to edit /etc/default/dump1090-fa to restore the airspy_adsb settings and restart dump1090-fa.

sudo nano /etc/default/dump1090-fa
sudo systemctl restart dump1090-fa

This is what my file looks like post edit:

# dump1090-fa configuration
# This is sourced by /usr/share/dump1090-fa/start-dump1090-fa as a
# shellscript fragment.

# If you are using a PiAware sdcard image, this config file is regenerated
# on boot based on the contents of piaware-config.txt; any changes made to this
# file will be lost.

# dump1090-fa won't automatically start unless ENABLED=yes
ENABLED=yes

RECEIVER_OPTIONS="--net-only"
DECODER_OPTIONS="--max-range 360 --fix"
NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1300 --net-ro-interval 0.2 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005
JSON_OPTIONS="--json-location-accuracy 1"

# Use a machine-specific wisdom file if it exists
if [ -f /etc/dump1090-fa/wisdom.local ]
then
  RECEIVER_OPTIONS="${RECEIVER_OPTIONS} --wisdom /etc/dump1090-fa/wisdom.local"
fi

I’m not sure how the Wisdom File section of the config file is necessary for an airspy_adsb setup, but my feeder seems to be working with it in the file.

2 Likes

You should be able to rerun airspy-conf if you used that before. GitHub - wiedehopf/airspy-conf

But as mentioned you’d then need to reapply your configuration options for the airspy as it goes back to defaults.

The wisdom file shouldn’t really matter because dump1090-fa doesn’t have to do any demodulation thus it won’t use much CPU which is what the wisdom file can help reduce.

3 Likes

Thank you for the warning.

I updated an AirSpy system by building the package from Github and restarted lighttpd.

That worked and SkyAware shows 5.0 but the stats page still shows 4.0.

Any thoughts?

Which page exactly do you mean?
Screenshot?

Statistics


SkyAware

I don’t know why, my airspy installation just stopped working after upgrading to 5.0.
I have checked the above file… nothing is wrong in that file.
I have re-run the tar1090 update, still the same.

It’ll stay red until you update to piaware 5.0 apparently.
Seems like a bug previously old versions weren’t marked as red.

That’s not very specific.
If you were asked if you would like to overwrite the /etc/default/dump1090-fa configuration and said yes then rerun airspy-conf …

Check the log for dump1090-fa and airspy_adsb
Debug commands · wiedehopf/adsb-wiki Wiki · GitHub

May not be relevant, but did you follow @eric1tran’s advice to also update via your stats page?

That webpage update doesn’t really work on my Ubuntu with Intel CPU.

Lighttpd:
sorin@ubuntu:~ sudo journalctl --no-pager -u lighttpd [sudo] password for sorin: -- Logs begin at Sat 2021-02-20 04:06:44 EST, end at Mon 2021-03-15 10:31:31 EDT. -- Feb 20 07:41:49 openhabian systemd[1]: Stopping Lighttpd Daemon... Feb 20 07:41:49 openhabian systemd[1]: lighttpd.service: Succeeded. Feb 20 07:41:49 openhabian systemd[1]: Stopped Lighttpd Daemon. Feb 20 07:41:49 openhabian systemd[1]: Starting Lighttpd Daemon... Feb 20 07:41:50 openhabian systemd[1]: Started Lighttpd Daemon. Feb 23 15:09:47 openhabian systemd[1]: Stopping Lighttpd Daemon... Feb 23 15:09:47 openhabian systemd[1]: lighttpd.service: Succeeded. Feb 23 15:09:47 openhabian systemd[1]: Stopped Lighttpd Daemon. Feb 23 15:09:47 openhabian systemd[1]: Starting Lighttpd Daemon... Feb 23 15:09:47 openhabian systemd[1]: Started Lighttpd Daemon. Mar 03 11:50:40 openhabian systemd[1]: Stopping Lighttpd Daemon... Mar 03 11:50:40 openhabian systemd[1]: lighttpd.service: Succeeded. Mar 03 11:50:40 openhabian systemd[1]: Stopped Lighttpd Daemon. Mar 03 11:50:40 openhabian systemd[1]: Starting Lighttpd Daemon... Mar 03 11:50:40 openhabian systemd[1]: Started Lighttpd Daemon. Mar 12 22:01:14 ubuntu systemd[1]: Stopping Lighttpd Daemon... Mar 12 22:01:15 ubuntu systemd[1]: lighttpd.service: Succeeded. Mar 12 22:01:15 ubuntu systemd[1]: Stopped Lighttpd Daemon. -- Reboot -- Mar 12 22:04:46 ubuntu systemd[1]: Starting Lighttpd Daemon... Mar 12 22:04:46 ubuntu systemd[1]: Started Lighttpd Daemon. Mar 12 22:17:25 ubuntu systemd[1]: Stopping Lighttpd Daemon... Mar 12 22:17:25 ubuntu systemd[1]: lighttpd.service: Succeeded. Mar 12 22:17:25 ubuntu systemd[1]: Stopped Lighttpd Daemon. Mar 12 22:17:25 ubuntu systemd[1]: Starting Lighttpd Daemon... Mar 12 22:17:25 ubuntu systemd[1]: Started Lighttpd Daemon. Mar 14 18:55:57 ubuntu systemd[1]: Stopping Lighttpd Daemon... Mar 14 18:55:57 ubuntu systemd[1]: lighttpd.service: Succeeded. Mar 14 18:55:57 ubuntu systemd[1]: Stopped Lighttpd Daemon. Mar 14 18:55:57 ubuntu systemd[1]: Starting Lighttpd Daemon... Mar 14 18:55:57 ubuntu systemd[1]: Started Lighttpd Daemon. sorin@ubuntu:~ ls /etc/lighttpd/conf-enabled
07-mod_setenv.conf 88-graphs1090.conf 95-tar1090-otherport.conf
47-stat-cache.conf 88-tar1090.conf 99-unconfigured.conf
88-dump1090-fa-statcache.conf 89-dump1090-fa.conf
sorin@ubuntu:~$ grep mod_setenv /etc/lighttpd/ -rnT
/etc/lighttpd/conf-available/89-dump1090-fa.conf: 42: #server.modules += ( “mod_setenv” )
/etc/lighttpd/conf-available/07-mod_setenv.conf: 1: server.modules += ( “mod_setenv” )
/etc/lighttpd/conf-available/05-setenv.conf: 3: #server.modules += ( “mod_setenv” )

For 1090fa:
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: Mon Mar 15 09:59:52 2021 EDT Caught SIGTERM, shutting down…
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: Statistics: Mon Mar 15 08:54:52 2021 EDT - Mon Mar 15 09:59:52 2021 EDT
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: Local receiver:
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 samples processed
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 samples dropped
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 Mode A/C messages received
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 Mode-S message preambles received
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 with bad message format or invalid CRC
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 with unrecognized ICAO address
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 accepted with correct CRC
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 messages with signal power above -3dBFS
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: Messages from network clients:
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 Mode A/C messages received
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 Mode S messages received
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 with bad message format or invalid CRC
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 with unrecognized ICAO address
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 accepted with correct CRC
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 total usable messages
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 surface position messages received
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 airborne position messages received
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 global CPR attempts with valid positions
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 global CPR attempts with bad data
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 global CPR attempts that failed the range check
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 global CPR attempts that failed the speed check
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 global CPR attempts with insufficient data
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 local CPR attempts with valid positions
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 aircraft-relative positions
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 receiver-relative positions
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 local CPR attempts that did not produce useful positions
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 local CPR attempts that failed the range check
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 local CPR attempts that failed the speed check
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 CPR messages that look like transponder failures filtered
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 non-ES altitude messages from ES-equipped aircraft ignored
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 unique aircraft tracks
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 aircraft tracks where only one message was seen
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 aircraft tracks which were not marked reliable
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: CPU load: 0.1%
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 ms for demodulation
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 0 ms for reading from USB
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 3263 ms for network input and background tasks
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: Range histogram:
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)…
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu systemd[1]: dump1090-fa.service: Succeeded.
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ████████████████████████████████████████████████████████████████████████████
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]:
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ----------------------------------------------------------------------------
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: 013 048 083 118 154 189 224 259 294 329 364 399 434 469 504 540 575 610 645 km
Mar 15 09:59:52 ubuntu dump1090-fa[2072885]: Mon Mar 15 09:59:52 2021 EDT Normal exit.
Mar 15 09:59:52 ubuntu systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Mar 15 09:59:52 ubuntu systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Mar 15 09:59:52 ubuntu dump1090-fa[2111580]: Mon Mar 15 09:59:52 2021 EDT dump1090-fa 4.0 starting up.
Mar 15 09:59:52 ubuntu dump1090-fa[2111580]: Net-only mode, no SDR device or file open.

Lighttpd and dump1090-fa look fine.

I didn’t see the log for airspy_adsb.

What is the exact issue you have?

‘’’
Mar 12 22:04:40 ubuntu systemd[1]: Started Airspy ADS-B receiver.
Mar 12 22:04:40 ubuntu airspy_adsb[745]: airspy_adsb v1.85
Mar 12 22:04:40 ubuntu airspy_adsb[745]: Listening for beast clients on port 47787
Mar 12 22:04:40 ubuntu airspy_adsb[745]: Acquired Airspy device with serial 26A464DC28232193
Mar 12 22:04:40 ubuntu airspy_adsb[745]: Decoding started at 20 MSPS
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 491520 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 196608 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 196608 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
Mar 12 22:04:40 ubuntu airspy_adsb[745]: /!\ Lost 98304 samples /!
‘’’

Doesn’t seem like it’s pushing data to dump1090-fa.

You are missing a message like this:

Mar 15 16:13:01 pi airspy_adsb[29969]: Push client connected to localhost:30004 (beast)

Not sure how you were getting data to dump1090-fa previously or what you were using instead of dump1090-fa …

You can either fix the config /etc/default/airspy_adsb so it looks like this.

#network settings
NET= -l 47787:beast -c localhost:30004:beast

Or you can rerun GitHub - wiedehopf/airspy-conf and recustomize the configuration.

1 Like

That was it, I was missing that! Thanks!