No ADS-B data program seen listening

FlightAware ADS-B Flight Tracking
1

Good Morning,

This morning when I check my RPi feeder I am getting the following error: “no ADS-B data program seen listening on port 30005 for 276 seconds, next check in 60”. I have restarted the RPi multiple times and still getting the same error.

Any ideas how to resolve this please?

2

If I issue a status command I get this:

sudo piaware-status
PiAware master process (piaware) is running with pid 545.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 22334.
Local ADS-B receiver (dump1090-fa) is running with pid 23523.

dump1090-fa (pid 23523) is listening for ES connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is connected to FlightAware.

dump1090 is NOT producing data on localhost:30005.

3

Also checked the dongle:

$ sudo rtl_test
Found 1 device(s):
0: Realtek, RTL2832U, SN: 00001000

Using device 0: Generic RTL2832U
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.

Info: This tool will continuously read from the device, and report if
samples get lost. If you observe no further output, everything is fine.

Reading samples in async mode…
Allocating 15 zero-copy buffers
lost at least 16 bytes

4

And from the command sudo systemctl status dump1090-fa I get the following output:

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 Sat 2025-09-27 11:21:07 UTC; 10s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 25154 (dump1090-fa)
Tasks: 3 (limit: 2058)
CPU: 385ms
CGroup: /system.slice/dump1090-fa.service
└─25154 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --device-index 0 --gain 60 --adaptive-range --fix --lat 52.75746 --l>

Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_demod_write_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_demod_read_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_demod_write_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_demod_read_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_write_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_write_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: adaptive: using 50% duty cycle
Sep 27 11:21:07 piaware dump1090-fa[25154]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 9.0dB (step 1)
Sep 27 11:21:07 piaware dump1090-fa[25154]: adaptive: enabled dynamic range control, target dynamic range 30.0dB
Sep 27 11:21:07 piaware dump1090-fa[25154]: Allocating 4 zero-copy buffers
lines 1-20/20 (END)…skipping…
● 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 Sat 2025-09-27 11:21:07 UTC; 10s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 25154 (dump1090-fa)
Tasks: 3 (limit: 2058)
CPU: 385ms
CGroup: /system.slice/dump1090-fa.service
└─25154 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --device-index 0 --gain 60 --adaptive-range --fix --lat 52.75746 --lon -2.55661 --max-range 360 --net-ro-port 30002 →

Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_demod_write_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_demod_read_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_demod_write_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_demod_read_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_write_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: rtlsdr_write_reg failed with -1
Sep 27 11:21:07 piaware dump1090-fa[25154]: adaptive: using 50% duty cycle
Sep 27 11:21:07 piaware dump1090-fa[25154]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 9.0dB (step 1)
Sep 27 11:21:07 piaware dump1090-fa[25154]: adaptive: enabled dynamic range control, target dynamic range 30.0dB
Sep 27 11:21:07 piaware dump1090-fa[25154]: Allocating 4 zero-copy buffers

5

Your dongle or RPi’s usb port has some issue.

Unplug the dongle, leave it unplugged for 5 minutest cool down, then replug it firmly inusb port of Pi and reboot Pi. Ater fewminutes check status of dump1090-fa

`sudo systemctl status dump1090-f

Note: if you are using a usb cable to connect dongle to RPi remove it and plug the dongle directly in usb port of RPi.

If above does not remedy the situation, your donge is on the way to die. Purchase anoter dongle.

1 Like
6

Is this your online station or are you setting up a new receiver?
(your online station seems to be working fine)

7

I may have the same or similar problem. … on the way out.

She’s been a good ship, though.

8

“Sep 24 20:49:43 piaware systemd[l]: piaware.service: Watchdog timeout (limit 2min)!”"

“Sep 24 20:49:43 piaware systemd[l]: piaware.service: Killing process 1593 (piaware) with signal SIGABRT.”

We did have a solid storm with rainfall and nobody was flying. For a very rare once-in-a-while my one (!) node didn’t see any a/c at all.

9

Thanks to everyone who took the time to reply. I removed the USB extender from the FlightAware stick and plugged it directly in and I was back in action. Replaced the USB extender and all is now good

Thanks

2 Likes