My Raspberry PiAware was working flawlessly for over 200 days until I accidentally broke the pin connector from the antenna to the USB dongle while moving my indoor antenna higher.
Offline since August 4th awaiting a new USB Dongle and that finally arrived yesterday.
I plugged it in and I’m now still receiving the “No ADS-B data program is serving port 30005” log message after it says that “dump1090 start appears to have been successful”
I have rebooted the Pi, I have rebooted and checked my internet router, I’ve gone back and forth from wifi to hard line and still wont feed data.
My pi checks in with the site but no data upload.
I removed the micro SD card wiped it and completely reloaded Dump 1090. I even did a reset on the Pi and it just wont upload data.
Why would it work so well for so long and then suddenly give me such grief after being offline awaiting the new USB dongle?
I am not a programmer by any means but any advice would be appreciated.
Have you tried “10.0.0.1:8080” (replace 10.0.0.1 with the network ip address to the Pi) to see if it displays any aircraft?
You should get something like this (no ac in the air here, as it is 1am), though with a list of aircraft and some ac icons on the map (if they have ADSB and if there’s enough stations for MLAT in your area). http://www.crowingstudios.com/images/Dump1090tn.png
I wiped the sd card and reinstalled the software and still getting this…
[2015-08-14 20:17 EDT] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2015-08-14 20:18 EDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2015-08-14 20:18 EDT] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2015-08-14 20:19 EDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2015-08-14 20:19 EDT] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s
[2015-08-14 20:20 EDT] 0 msgs recv’d from the ADS-B data program (0 in last 5m); 0 msgs sent to FlightAware
[2015-08-14 20:20 EDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2015-08-14 20:20 EDT] no ADS-B data program seen listening on port 30005 for 370 seconds, trying to start it…
[2015-08-14 20:20 EDT] attempting to start fadump1090.sh using ‘invoke-rc.d fadump1090.sh start’…
[2015-08-14 20:20 EDT] dump1090 start appears to have been successful
[2015-08-14 20:41 EDT] 0 msgs recv’d from (not currently connected to an adsb source); 0 msgs sent to FlightAware
[2015-08-14 20:41 EDT] no ADS-B data program is serving on port 30005, next check in 60s
[2015-08-14 20:41 EDT] no new messages received in 19618331 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart dump1090, possibly restart faup1090 and definitely reconnect, just in case…
[2015-08-14 20:41 EDT] attempting to restart dump1090 using ‘/etc/init.d/fadump1090.sh restart’…
[2015-08-14 20:41 EDT] dump1090 restart appears to have been successful
[2015-08-14 20:41 EDT] stop_faup1090: no need to stop faup1090, it’s not running
[2015-08-14 20:41 EDT] close_faup1090_socket called with no socket argument and no faup1090 global socket
[2015-08-14 20:41 EDT] will attempt to connect to faup1090 in 60s…
[2015-08-14 20:42 EDT] 0 msgs recv’d from (not currently connected to an adsb source) (0 in last 1m); 0 msgs sent to FlightAware
[2015-08-14 20:42 EDT] no ADS-B data program is serving on port 30005, next check in 60s
[2015-08-14 20:43 EDT] no ADS-B data program is serving on port 30005, next check in 60s
[2015-08-14 20:44 EDT] no ADS-B data program is serving on port 30005, next check in 60s
4th line from the bottom does this indicate that the brand new usb dongle isn’t doing its job?
