No ADS-B data program seen listening on port 30005 error


I recently (two days ago) started using the Flightaware 1090MHz PiAware ADS-B Kit. Initially everything we working well (over 1000 flights tracked per day) and then the Pi started reporting the errors:

[2022-08-13 16:55 EDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2022-08-13 16:55 EDT] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2022-08-13 16:56 EDT] no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s

This continues on and on.

Unplugging and plugging in the Pi does not correct. Restarting the Pi does not correct. Restarting Piaware and/or dump1090 does not correct. Unplugging the ADS-B stick does not correct.

Would anyone have an inkling what to do next?


Did you enable 978 by chance?
Or install fr24 or rbfeeder?

pgrep -fa dump

Otherwise … SDR might be dead.

It’s the install that the Flightaware installation instructions direct. There is no other feeds going out from the Pi.

Did you enable 978 by chance? - No. I wouldn’t know how to.
Or install fr24 or rbfeeder? - Strictly using Flightaware, nothing else.

Assuming the SDR is dead, can I use any SDR or do I have to use the Flightaware Prostick (the blue one is what I have)?

Yes you can use any RTL2832U+R820T SDR, but first check your SDR which you suspect has failed.

(1) Install sdr checking software

sudo apt install rtl-sdr  

(2) Stop dump1090-fa dump978-fa and piaware to free the SDR

sudo systemctl stop piaware dump1090-fa dump978-fa   

(3) Test the SDR by giving following command:

rtl_test -t

If your Dongle is OK,
Properly connected to Pi,
you will see this output

Found 1 device(s):
 0: Realtek, RTL2832UFA, 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 
Sampling at 2048000 S/s. 
No E4000 tuner found, aborting.


Took a bit to check what you suggested as I didn’t have a screen or keyboard connected to the Pi.

As such I needed to get a micro to usb hub to connect the keyboard and a HDMI cable.

Installed the HDMI cable and the status screen on the Pi showed no receiver connected.

Removing the original micro to usb cable and then connecting the hub caused the Pi to reboot and when it came back up the SDR stick was recognized and the Pi started sending data.

At this point it likely is the cable causing the issue, though I can’t see an obvious problem with the pins or connectors. I’ll let things be as they are with the new cable and if it fails again I’ll run the test on the Pi as suggested and see what that says and post more information here.

Thanks to all that helped, really appreciated!

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.