FlightAware Discussions

Having trouble getting dump978 & dongle running

I hove both dongles on my Raspberry pi. I have serialized both. The blue pro stick 1090 is 00001090 and the orange UAT 978 stick is 00000978. DUMP1090-fa is running just fine. But DUMP978-fa seems to be have an issue. Any help would be appreciated.

pi@piaware:~ $ rtl_test -t
Found 2 device(s):
0: Realtek, RTL2832U, SN: 00001090
1: Realtek, RTL2832U, SN: 00000978

Using device 0: Generic RTL2832U
usb_claim_interface error -6
Failed to open rtlsdr device #0.
pi@piaware:~ pi@piaware:~ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset:
Active: active (running) since Sun 2019-10-27 22:44:18 UTC; 2min 7s ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 413 (piaware)
CGroup: /system.slice/piaware.service
├─413 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusf
├─622 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --n
└─831 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localho

Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): fa-mlat-client 0.2.10 st
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Using UDP transport to 7
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Listening for Beast-form
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Listening for Extended B
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Input connected to local
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Input format changed to
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Beast-format results con
Oct 27 22:45:55 piaware sudo[1454]: piaware : TTY=unknown ; PWD=/ ; USER=root ;
Oct 27 22:45:55 piaware sudo[1454]: pam_unix(sudo:session): session opened for u
Oct 27 22:45:55 piaware piaware[413]: no ADS-B data program seen listening on po
lines 1-20/20 (END)…skipping…
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-10-27 22:44:18 UTC; 2min 7s ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 413 (piaware)
CGroup: /system.slice/piaware.service
├─413 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─622 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.024 --lon -84.179
└─831 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --resul

Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): fa-mlat-client 0.2.10 starting up
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Using UDP transport to 70.42.6.191 port 7304
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Listening for Beast-format results connection on port 30105
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Listening for Extended Basestation-format results connection on port 30106
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Input connected to localhost:30005
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Input format changed to BEAST, 12MHz clock
Oct 27 22:45:12 piaware piaware[413]: mlat-client(831): Beast-format results connection with ::1:30104: connection established
Oct 27 22:45:55 piaware sudo[1454]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Oct 27 22:45:55 piaware sudo[1454]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 27 22:45:55 piaware piaware[413]: no ADS-B data program seen listening on port 30978 for 90 seconds, next check in 60s

[1]+ Stopped sudo systemctl status piaware
pi@piaware:~ $ sudo systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2019-10-27 22:44:18 UTC; 2min 49s ago
Docs: https://flightaware.com/adsb/piaware/
Main PID: 410 (dump1090-fa)
CGroup: /system.slice/dump1090-fa.service
└─410 /usr/bin/dump1090-fa --net-bo-port 30005 --fix --device-index 00001090 --gain -10 --ppm 0 --max-range 360 --net --net-heartbeat 60 --net-ro-s

Oct 27 22:44:18 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Oct 27 22:44:19 piaware dump1090-fa[410]: Sun Oct 27 22:44:19 2019 UTC dump1090-fa 3.7.2 starting up.
Oct 27 22:44:19 piaware dump1090-fa[410]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001090)
Oct 27 22:44:19 piaware dump1090-fa[410]: Found Rafael Micro R820T tuner
Oct 27 22:44:20 piaware dump1090-fa[410]: rtlsdr: enabling tuner AGC

[2]+ Stopped sudo systemctl status dump1090-fa
pi@piaware:~ $ sudo systemctl status dump978-fa
● dump978-fa.service - dump978 ADS-B UAT receiver
Loaded: loaded (/lib/systemd/system/dump978-fa.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun 2019-10-27 22:47:30 UTC; 359ms ago
Docs: https://flightaware.com/adsb/piaware/
Process: 1561 ExecStart=/usr/share/dump978-fa/start-dump978-fa (code=exited, status=1/FAILURE)
Main PID: 1561 (code=exited, status=1/FAILURE)

Oct 27 22:47:30 piaware systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 27 22:47:30 piaware systemd[1]: dump978-fa.service: Unit entered failed state.
Oct 27 22:47:30 piaware systemd[1]: dump978-fa.service: Failed with result ‘exit-code’.

What’s the output for:

sudo piaware-config

Also let’s check the proper log:

sudo journalctl --no-pager -u dump978-fa

pi@piaware:~ $ piaware-config
warning: /boot/piaware-config.txt:1: unrecognized option C
allow-auto-updates yes # value set at /boot/piaware-config.txt:69
allow-manual-updates yes # value set at /boot/piaware-config.txt:73
allow-mlat yes # value set at /boot/piaware-config.txt:77
allow-modeac yes # value set at /boot/piaware-config.txt:81
image-type piaware # value set at /usr/share/piaware-support/piaware-image-config.txt:5
manage-config yes # value set at /usr/share/piaware-support/piaware-image-config.txt:4
rtlsdr-device-index 00001090 # value set at /boot/piaware-config.txt:101
rtlsdr-gain max # value set at /boot/piaware-config.txt:62
uat-receiver-host 192.168.1.20 # value set at /boot/piaware-config.txt:100
uat-receiver-type sdr # value set at /boot/piaware-config.txt:99
uat-sdr-device driver=rtlsdr,serial=00000978 # value set at /boot/piaware-config.txt:102
wired-address 192.168.1.20 # value set at /boot/piaware-config.txt:86
wired-broadcast 192.168.1.255 # value set at /boot/piaware-config.txt:88
wired-gateway 192.168.1.1 # value set at /boot/piaware-config.txt:89
wired-netmask 255.255.255.0 # value set at /boot/piaware-config.txt:87
wired-network yes # value set at /boot/piaware-config.txt:27
wired-type static # value set at /boot/piaware-config.txt:28
wireless-address 192.168.1.25 # value set at /boot/piaware-config.txt:94
wireless-broadcast 192.168.1.255 # value set at /boot/piaware-config.txt:96
wireless-country US # value set at /boot/piaware-config.txt:98
wireless-gateway 192.168.1.1 # value set at /boot/piaware-config.txt:97
wireless-netmask 255.255.255.0 # value set at /boot/piaware-config.txt:95
wireless-network no # value set at /boot/piaware-config.txt:90
wireless-password # value set at /boot/piaware-config.txt:92
wireless-ssid xxxxxxxxxxxxxx # value set at /boot/piaware-config.txt:91
wireless-type dhcp # value set at /boot/piaware-config.txt:93

pi@piaware:~ $ sudo journalctl --no-pager -u dump978-fa
– Logs begin at Mon 2019-10-28 11:34:48 UTC, end at Mon 2019-10-28 11:48:59 UTC. –
Oct 28 11:34:56 piaware systemd[1]: Started dump978 ADS-B UAT receiver.
Oct 28 11:34:57 piaware dump978-fa[415]: raw-port: listening for connections on 0.0.0.0:30978
Oct 28 11:34:57 piaware dump978-fa[415]: raw-port: listening for connections on [::]:30978
Oct 28 11:34:57 piaware dump978-fa[415]: json-port: listening for connections on 0.0.0.0:30979
Oct 28 11:34:57 piaware dump978-fa[415]: json-port: listening for connections on [::]:30979
Oct 28 11:34:57 piaware dump978-fa[415]: usb_claim_interface error -6
Oct 28 11:34:57 piaware dump978-fa[415]: Found Rafael Micro R820T tuner
Oct 28 11:34:58 piaware dump978-fa[415]: Found Rafael Micro R820T tuner
Oct 28 11:34:58 piaware dump978-fa[415]: Exact sample rate is: 2083333.135571 Hz
Oct 28 11:34:58 piaware dump978-fa[415]: [R82XX] PLL not locked!
Oct 28 11:34:58 piaware dump978-fa[415]: SoapySDR: using maximum manual gain 49.6 dB
Oct 28 11:34:58 piaware dump978-fa[415]: SoapySDR: using stream setting buffsize=262144
Oct 28 11:34:58 piaware dump978-fa[415]: [::]:30978: accepted a connection from [::1]:39122
Oct 28 11:35:00 piaware dump978-fa[415]: [::]:30978: accepted a connection from [::1]:39126
Oct 28 11:36:17 piaware dump978-fa[415]: Message source reports error: TIMEOUT
Oct 28 11:36:17 piaware systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
Oct 28 11:36:17 piaware systemd[1]: dump978-fa.service: Unit entered failed state.
Oct 28 11:36:17 piaware systemd[1]: dump978-fa.service: Failed with result ‘exit-code’.
Oct 28 11:36:48 piaware systemd[1]: dump978-fa.service: Service hold-off time over, scheduling restart.
Oct 28 11:36:48 piaware systemd[1]: Stopped dump978 ADS-B UAT receiver.
Oct 28 11:36:48 piaware systemd[1]: Started dump978 ADS-B UAT receiver.
Oct 28 11:36:48 piaware dump978-fa[1382]: raw-port: listening for connections on 0.0.0.0:30978
Oct 28 11:36:48 piaware dump978-fa[1382]: raw-port: listening for connections on [::]:30978
Oct 28 11:36:48 piaware dump978-fa[1382]: json-port: listening for connections on 0.0.0.0:30979
Oct 28 11:36:48 piaware dump978-fa[1382]: json-port: listening for connections on [::]:30979
Oct 28 11:36:48 piaware dump978-fa[1382]: usb_claim_interface error -6
Oct 28 11:36:48 piaware dump978-fa[1382]: Found Rafael Micro R820T tuner
Oct 28 11:36:49 piaware dump978-fa[1382]: Found Rafael Micro R820T tuner
Oct 28 11:36:49 piaware dump978-fa[1382]: Exact sample rate is: 2083333.135571 Hz
Oct 28 11:36:49 piaware dump978-fa[1382]: [R82XX] PLL not locked!
Oct 28 11:36:49 piaware dump978-fa[1382]: SoapySDR: using maximum manual gain 49.6 dB
Oct 28 11:36:49 piaware dump978-fa[1382]: SoapySDR: using stream setting buffsize=262144
Oct 28 11:37:17 piaware dump978-fa[1382]: [::]:30978: accepted a connection from [::1]:39140
Oct 28 11:37:19 piaware dump978-fa[1382]: [::]:30978: accepted a connection from [::1]:39142

This means the dongle somehow stopped delivering data.
But dump978-fa was restarted and worked fine for 12 minutes which is the time you printed the log.

Let’s check if you voltage issues with this command:

sudo dmesg --ctime | grep voltage

Is the dongle connected directly to the RPi or are you using an extension?
If you are using an extension, try another.

No response from the voltage command

pi@piaware:~ pi@piaware:~ sudo dmesg --ctime | grep voltage
pi@piaware:~ pi@piaware:~
pi@piaware:~ sudo dmesg --ctime | grep voltage pi@piaware:~

Yea, might be a little flaky. I’ll swap it out when I get home. I may be able to get by without it.

I am getting some data now.