Moved receiver 90 miles, now not feeding

FlightAware ADS-B Flight Tracking
1

Hi All:

I moved my PiZero2W / receiver / coax and antenna to a new location. The only change that I made was the network SSID and key. I can ssh into the device no problem. FA shows that I have three green buttons, but it’s not feeding any data to FA.

I can see this in the log and it essentially repeats over and over:

[2024-12-17 20:42 CST] dump1090 start appears to have been successful
[2024-12-17 20:42 CST] attempting to start dump1090..
[2024-12-17 20:42 CST] no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it...
[2024-12-17 20:42 CST] attempting to start dump1090-fa using 'systemctl --no-block restart dump1090-fa.service < /dev/null'...
[2024-12-17 20:43 CST] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2024-12-17 20:43 CST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2024-12-17 20:44 CST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2024-12-17 20:44 CST] no ADS-B data program is serving on port 30005, not starting multilateration client yet

I have rebooted and also tried the “Upgrade and restart PiAware” to no avail. All of the exact same hardware was working fine in the other location yesterday.

Any ideas?

Best Regards,
Steve - Houston, TX

2

(1) What is output of following command?

sudo systemctl status dump1090-fa

(2) Did you set new location’s latitude and longitude in following page?

https://www.flightaware.com/adsb/stats/user/

 

3

Thanks for the reply, abcd. Should have mentioned in the OP that the other change I made was the Rx location. Re-checked it and looks correct.

Looks like dump1090-fa is experiencing some kind of failure, exiting and restarting continually.

Could I be having some kind of port forwarding problem?

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 p>
     Active: activating (auto-restart) (Result: exit-code) since Wed 2024-12-18>
       Docs: https://flightaware.com/adsb/piaware/
    Process: 24165 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-j>
   Main PID: 24165 (code=exited, status=1/FAILURE)
        CPU: 46ms
lines 1-7/7 (END)...skipping...
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
     Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2024-12-18 15:18:35 UTC; 17s ago
       Docs: https://flightaware.com/adsb/piaware/
    Process: 24165 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, stat>
   Main PID: 24165 (code=exited, status=1/FAILURE)
        CPU: 46ms
~
lines 1-7/7 (END)...skipping...
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
     Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2024-12-18 15:18:35 UTC; 17s ago
       Docs: https://flightaware.com/adsb/piaware/
    Process: 24165 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json /run/dump1090-fa (code=exited, status=1/FAILURE)
   Main PID: 24165 (code=exited, status=1/FAILURE)
        CPU: 46ms

Best Regards,
Steve - Houston, TX

1 Like
4

No, the SDR isn’t working most likely.

Properly looking at the log instead of the status will be more useful:

sudo journalctl -u dump1090-fa -e -n50
1 Like
5

OK, here is the result of the command:

Hmm, rtlsdr: no supported devices found. Already swapped the cable, I’ll crack the dongle open…

pi@piaware:~ $ sudo journalctl -u dump1090-fa -e -n50
Dec 18 16:44:37 piaware systemd[1]: dump1090-fa.service: Main process exited, c>
Dec 18 16:44:37 piaware systemd[1]: dump1090-fa.service: Failed with result 'ex>
Dec 18 16:45:07 piaware systemd[1]: dump1090-fa.service: Scheduled restart job,>
Dec 18 16:45:07 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAwar>
Dec 18 16:45:07 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAwar>
Dec 18 16:45:07 piaware dump1090-fa[25978]: Wed Dec 18 16:45:07 2024 UTC  dump1>
Dec 18 16:45:07 piaware dump1090-fa[25978]: rtlsdr: no supported devices found.
Dec 18 16:45:07 piaware systemd[1]: dump1090-fa.service: Main process exited, c>
Dec 18 16:45:07 piaware systemd[1]: dump1090-fa.service: Failed with result 'ex>
Dec 18 16:45:37 piaware systemd[1]: dump1090-fa.service: Scheduled restart job,>
Dec 18 16:45:37 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAwar>
Dec 18 16:45:38 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAwar>
Dec 18 16:45:38 piaware dump1090-fa[25984]: Wed Dec 18 16:45:38 2024 UTC  dump1>
Dec 18 16:45:38 piaware dump1090-fa[25984]: rtlsdr: no supported devices found.
Dec 18 16:45:38 piaware systemd[1]: dump1090-fa.service: Main process exited, c>
Dec 18 16:45:38 piaware systemd[1]: dump1090-fa.service: Failed with result 'ex>
Dec 18 16:46:08 piaware systemd[1]: dump1090-fa.service: Scheduled restart job,>
Dec 18 16:46:08 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAwar>
Dec 18 16:46:08 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAwar>
Dec 18 16:46:08 piaware dump1090-fa[26053]: Wed Dec 18 16:46:08 2024 UTC  dump1>
Dec 18 16:46:08 piaware dump1090-fa[26053]: rtlsdr: no supported devices found.
Dec 18 16:46:08 piaware systemd[1]: dump1090-fa.service: Main process exited, c>
Dec 18 16:46:08 piaware systemd[1]: dump1090-fa.service: Failed with result 'ex>
lines 29-51/51 (END)
Dec 18 16:44:37 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Dec 18 16:44:37 piaware systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Dec 18 16:45:07 piaware systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 2309.
Dec 18 16:45:07 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Dec 18 16:45:07 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Dec 18 16:45:07 piaware dump1090-fa[25978]: Wed Dec 18 16:45:07 2024 UTC  dump1090-fa 8.2 starting up.
Dec 18 16:45:07 piaware dump1090-fa[25978]: rtlsdr: no supported devices found.
Dec 18 16:45:07 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Dec 18 16:45:07 piaware systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Dec 18 16:45:37 piaware systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 2310.
Dec 18 16:45:37 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Dec 18 16:45:38 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Dec 18 16:45:38 piaware dump1090-fa[25984]: Wed Dec 18 16:45:38 2024 UTC  dump1090-fa 8.2 starting up.
Dec 18 16:45:38 piaware dump1090-fa[25984]: rtlsdr: no supported devices found.
Dec 18 16:45:38 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Dec 18 16:45:38 piaware systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
Dec 18 16:46:08 piaware systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 2311.
Dec 18 16:46:08 piaware systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
Dec 18 16:46:08 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Dec 18 16:46:08 piaware dump1090-fa[26053]: Wed Dec 18 16:46:08 2024 UTC  dump1090-fa 8.2 starting up.
Dec 18 16:46:08 piaware dump1090-fa[26053]: rtlsdr: no supported devices found.
Dec 18 16:46:08 piaware systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
Dec 18 16:46:08 piaware systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.

Thanks,
Steve - Houston, TX

1 Like
6

Back in business. Thanks everyone for the help. As it turns out, BOTH electrolytic capacitors on the blue Flightaware stick were measuring <1uF on a C meter, out of circuit. Stated values are 220uF@10V for both caps. The cap on the left looked slightly puffed out on the top of the can and its bung seal was pushed out some.

IMG_9126
IMG_91261920×1440 129 KB

Soldered two replacement caps in and all good!

Best Regards,
Steve - Houston, TX

7 Likes
7

Good work!
Not many of us here prepared to work down to component level.
I’ve got a few failed SDR’s, but have to admit, it hadn’t occurred to me it’d be the reg caps. Linear regs don’t punish the caps like SMPS’s do.
I’ll see if they can be resurrected.

1 Like