FlightAware Discussions

1090 and 978 setup issue

I’ve been using single sdr and 1090 setup for a while and trying to configure second dongle for 978. got them both serialized, but after reboot it hangs up as shown below, and I lose cursor control over putty.

Using pi 4 with two orange dongles and combined 1090+978 filter.

how to I get past this hurdle?

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 Wed 2021-02-03 21:17:14 UTC; 55min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 555 (piaware)
Tasks: 4 (limit: 2065)
CGroup: /system.slice/piaware.service
├─555 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusf
├─682 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --n
└─724 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localho

Feb 03 22:11:52 piaware sudo[715]: pam_unix(sudo:session): session closed for us
Feb 03 22:11:52 piaware piaware[555]: Starting multilateration client: /usr/lib/
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): fa-mlat-client 0.2.11 st
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Using UDP transport to 7
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Listening for Beast-form
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Listening for Extended B
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Route MTU changed to 150
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Input connected to local
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Input format changed to
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Beast-format results con
lines 1-21/21 (END)…skipping…
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-02-03 21:17:14 UTC; 55min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 555 (piaware)
Tasks: 4 (limit: 2065)
CGroup: /system.slice/piaware.service
├─555 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─682 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 34.28
└─724 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --resu

Feb 03 22:11:52 piaware sudo[715]: pam_unix(sudo:session): session closed for user root
Feb 03 22:11:52 piaware piaware[555]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --inpu
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): fa-mlat-client 0.2.11 starting up
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Using UDP transport to 70.42.6.232 port 9948
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Listening for Beast-format results connection on port 30105
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Listening for Extended Basestation-format results connection
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Route MTU changed to 1500
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Input connected to localhost:30005
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Input format changed to BEAST, 12MHz clock
Feb 03 22:11:53 piaware piaware[555]: mlat-client(724): Beast-format results connection with ::1:30104: connection es
~
~
~
~
~
lines 1-21/21 (END)

You mean you need to press Q to exit the systemctl status?

Anyhow piaware log isn’t gonna help you, check the logs for dump1090-fa and dump978-fa:
Debug commands · wiedehopf/adsb-wiki Wiki · GitHub

while my 1090 is working fine, 978 does not. there are differences between the 1090 status report and 978 indicating 978 does not start. below is the status report. how can I fix this?

dump978-fa.service - dump978 ADS-B UAT receiver
Loaded: loaded (/lib/systemd/system/dump978-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-02-04 10:05:25 UTC; 2h 14min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 5497 (dump978-fa)
Tasks: 4 (limit: 2065)
CGroup: /system.slice/dump978-fa.service
└─5497 /usr/bin/dump978-fa --raw-port 30978 --json-port 30979 --sdr driver=rtlsdr,serial=0000

Feb 04 10:05:25 piaware dump978-fa[5497]: usb_claim_interface error -6
Feb 04 10:05:25 piaware dump978-fa[5497]: Found Rafael Micro R820T tuner
Feb 04 10:05:25 piaware dump978-fa[5497]: Found Rafael Micro R820T tuner
Feb 04 10:05:26 piaware dump978-fa[5497]: Exact sample rate is: 2083333.135571 Hz
Feb 04 10:05:26 piaware dump978-fa[5497]: [R82XX] PLL not locked!
Feb 04 10:05:26 piaware dump978-fa[5497]: SoapySDR: using maximum manual gain 49.6 dB
Feb 04 10:05:26 piaware dump978-fa[5497]: SoapySDR: using stream setting buffsize=262144
Feb 04 10:05:26 piaware dump978-fa[5497]: Allocating 15 zero-copy buffers
Feb 04 10:05:54 piaware dump978-fa[5497]: [::]:30978: accepted a connection from [::1]:35784
Feb 04 10:05:55 piaware dump978-fa[5497]: [::]:30978: accepted a connection from [::1]:35786
~
~

here are the journal entries. is that what you meant by log?

BTW, Q doesn’t exit the mode, I have to start a new putty session oddly.

pi@piaware:~ $ sudo journalctl -eu dump978-fa
Feb 04 08:16:00 piaware dump978-fa[4611]: Allocating 15 zero-copy buffers
Feb 04 08:16:04 piaware dump978-fa[4611]: [::]:30978: accepted a connection from [::1]:35746
Feb 04 08:16:29 piaware dump978-fa[4611]: [::]:30978: accepted a connection from [::1]:35748
Feb 04 10:04:54 piaware systemd[1]: dump978-fa.service: Main process exited, code=killed, status=11/SEGV
Feb 04 10:04:54 piaware systemd[1]: dump978-fa.service: Failed with result ‘signal’.
Feb 04 10:05:24 piaware systemd[1]: dump978-fa.service: Service RestartSec=30s expired, scheduling restart.
Feb 04 10:05:24 piaware systemd[1]: dump978-fa.service: Scheduled restart job, restart counter is at 1.
Feb 04 10:05:24 piaware systemd[1]: Stopped dump978 ADS-B UAT receiver.
Feb 04 10:05:25 piaware systemd[1]: Started dump978 ADS-B UAT receiver.
Feb 04 10:05:25 piaware dump978-fa[5497]: raw-port: listening for connections on 0.0.0.0:30978
Feb 04 10:05:25 piaware dump978-fa[5497]: raw-port: listening for connections on [::]:30978
Feb 04 10:05:25 piaware dump978-fa[5497]: json-port: listening for connections on 0.0.0.0:30979
Feb 04 10:05:25 piaware dump978-fa[5497]: json-port: listening for connections on [::]:30979
Feb 04 10:05:25 piaware dump978-fa[5497]: usb_claim_interface error -6
Feb 04 10:05:25 piaware dump978-fa[5497]: Found Rafael Micro R820T tuner
Feb 04 10:05:25 piaware dump978-fa[5497]: Found Rafael Micro R820T tuner
Feb 04 10:05:26 piaware dump978-fa[5497]: Exact sample rate is: 2083333.135571 Hz
Feb 04 10:05:26 piaware dump978-fa[5497]: [R82XX] PLL not locked!
Feb 04 10:05:26 piaware dump978-fa[5497]: SoapySDR: using maximum manual gain 49.6 dB
Feb 04 10:05:26 piaware dump978-fa[5497]: SoapySDR: using stream setting buffsize=262144
Feb 04 10:05:26 piaware dump978-fa[5497]: Allocating 15 zero-copy buffers
Feb 04 10:05:54 piaware dump978-fa[5497]: [::]:30978: accepted a connection from [::1]:35784
Feb 04 10:05:55 piaware dump978-fa[5497]: [::]:30978: accepted a connection from [::1]:35786

and from 1090
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 Wed 2021-02-03 23:00:48 UTC; 13h ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 558 (dump1090-fa)
Tasks: 3 (limit: 2065)
CGroup: /system.slice/dump1090-fa.service
└─558 /usr/bin/dump1090-fa --device-index 00001090 --gain -10 --ppm 0 --max-range 360 --fix -

Feb 03 23:00:48 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Feb 03 23:00:48 piaware dump1090-fa[558]: Wed Feb 3 23:00:48 2021 UTC dump1090-fa 4.0 starting up.
Feb 03 23:00:49 piaware dump1090-fa[558]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U,
Feb 03 23:00:49 piaware dump1090-fa[558]: Found Rafael Micro R820T tuner
Feb 03 23:00:49 piaware dump1090-fa[558]: rtlsdr: enabling tuner AGC
Feb 03 23:00:49 piaware dump1090-fa[558]: Allocating 4 zero-copy buffers
~

Well, that’s not good.

What is your hardware (edit: ok, I see Pi 4) and software (sdcard image etc)?

Check your power.

I’m also not clear exactly what the failure you’re seeing is. What’s not working, specifically?

yeah, I saw that as well. my read since an error return said ‘signal’ that the input signal might simply be too low. on the 978 display I see zero hits. since I just got it hooked up late in the day yesterday, thought I’d give it a day to see if anything comes up today.

regarding hardware, I am using a 1090 antenna with combined 1090/978 filter, splitter, two orange dongles serialized to Pi4. My thought was that there should be some 978 signal there even if attenuated due to the 1090 tuning, but have no way to verify. elsewhere in the log it said it was at max gain. I have a combo 978/1090 antenna on order from ADSBexchange.com (via amazon) which should show up next week.

There’s a difference between the processes not starting/staying running and antenna/signal issues. The dual-SDR configuration should be OK, even if no signal is coming in. If you look at the web page at your Pi’s IP address, the 978 section may be red/yellow/green (red = processes not running, yellow = no planes seen on 978, green = traffic seen).

I’m running 4.0, so this might be slightly different than your set-up, but these are the processes running (and may point you in a direction either with missing processes or arguments to running ones):

Blockquote
476 ? Ssl 11:04 /usr/bin/skyaware978 --connect localhost:30978 --reconnect-interval 30 --history-count 120 --history-interval 30 --lat 44.18251 --lon -92.40722 --json-dir /run/skyaware978
483 ? S<sl 4654:52 /usr/bin/dump1090-fa --device-index 00001090 --gain -10 --ppm 0 --max-range 360 --fix --net --net-heartbeat 60 --net-ro-size 1300 --net-ro-interval 0.2 --net-http-port 0 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bo-port 30005 --net-bi-port 30004,30104 --json-location-accuracy 2 --lat 44.18251 --lon -92.40722 --write-json /run/dump1090-fa --quiet
485 ? Ssl 153:17 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
500 tty1 Ssl+ 15:31 /usr/bin/tclsh8.6 /usr/lib/piaware-support/piaware-console-status
674 ? Ss 20:59 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
757 ? S 61:52 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 44.183 --lon -92.407
9282 ? S 119:39 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:16328:3055985181
15186 ? S<sl 36:38 /usr/bin/dump978-fa --raw-port 30978 --json-port 30979 --sdr-gain 25 --sdr driver=rtlsdr,serial=00000978
15238 ? Sl 0:01 /usr/lib/piaware/helpers/faup978 --connect localhost:30978

not shift Q, just q if you will.

I meant the log format i linked when i asked for it.

Anyhow … what you posted is that 978 is working and crashing every now and then (which isn’t good but not something that necessarily should prevent you from receiving something).

Now it’s unknown how well you’ll receive 978 and it’s unknown when the first 978 aircraft are gonna be in your coverage zone.
Note that zone will be much less due to 978 aircraft typically flying at 4000 to 10000 ft.

Agree we don’t know about the traffic situation at all. My antenna is on top of the roof so that should help some. Was just hoping to see something to confirm operation, just give me a blip. Lol

I wonder if there is some built in timeout if it doesn’t see traffic for a time, if it tries to restart?

Just got a hit, so am more confident now that I didn’t mess up the install, -16 RSSI

But not sure what is the sweet spot on signal strength for the sdr. From the 1090 side, I have seen some at -17 for RSSI but that is the smallest

1 Like

You should probably check your 1090 range for low flying planes to get an idea.
I’d recommend this: https://github.com/wiedehopf/tar1090#tar1090ptracks