FlightAware Discussions

PiAware orange. PROBLEM with the Mode S Reciver, Help!

Guys help me out here!! I’m dying trying to make this device run again whit no success… of course I’m a beginer. I don’t know why it sudenly stops the radio c, probably is a bug in the code or the device is defective

Here is the log, and some picts


Screenshot_2019-11-08%20ramseyCatalan%20ADS-B%20Feeder%20Statistics%20%E2%9C%88%20FlightAware
Screenshot_2019-11-08%20FlightFeeder%20SkyAware%20-%200%200

This is the log:

[2019-11-08 06:25 PST] Receiver location changed, restarting dump1090 and skyaware978
[2019-11-08 06:25 PST] attempting to restart skyaware978…
[2019-11-08 06:25 PST] site statistics URL: https://flightaware.com/adsb/stats/user/ramseyCatalan#stats-112814
[2019-11-08 06:25 PST] multilateration data requested
[2019-11-08 06:25 PST] attempting to restart skyaware978 using ‘systemctl --no-block try-restart skyaware978.service < /dev/null’…
[2019-11-08 06:25 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:25 PST] dump1090 restart appears to have been successful
[2019-11-08 06:25 PST] logged in to FlightAware as user ramseyCatalan
[2019-11-08 06:25 PST] no ADS-B data program seen listening on port 30005 for 4 seconds, next check in 60s
[2019-11-08 06:27 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:27 PST] multilateration data requested
[2019-11-08 06:27 PST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2019-11-08 06:28 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:28 PST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2019-11-08 06:29 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:29 PST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2019-11-08 06:30 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:30 PST] no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
[2019-11-08 06:31 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:31 PST] no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
[2019-11-08 06:31 PST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2019-11-08 06:32 PST] logged in to FlightAware as user ramseyCatalan
[2019-11-08 06:32 PST] site statistics URL: https://flightaware.com/adsb/stats/user/ramseyCatalan#stats-112814
[2019-11-08 06:32 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:32 PST] multilateration data requested
[2019-11-08 06:33 PST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2019-11-08 06:33 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:34 PST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2019-11-08 06:34 PST] multilateration data no longer required, disabling mlat client
[2019-11-08 06:34 PST] multilateration data requested
[2019-11-08 06:34 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:35 PST] attempting to restart skyaware978…
[2019-11-08 06:35 PST] skyaware978 restart appears to have been successful
[2019-11-08 06:35 PST] attempting to restart dump1090…
[2019-11-08 06:35 PST] multilateration data requested
[2019-11-08 06:35 PST] Receiver location changed, restarting dump1090 and skyaware978
[2019-11-08 06:35 PST] site statistics URL: https://flightaware.com/adsb/stats/user/ramseyCatalan#stats-112814
[2019-11-08 06:35 PST] attempting to restart dump1090-fa using ‘systemctl --no-block try-restart dump1090-fa.service < /dev/null’…
[2019-11-08 06:35 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:35 PST] logged in to FlightAware as user ramseyCatalan
[2019-11-08 06:35 PST] dump1090 restart appears to have been successful
[2019-11-08 06:35 PST] attempting to restart skyaware978 using ‘systemctl --no-block try-restart skyaware978.service < /dev/null’…
[2019-11-08 06:35 PST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2019-11-08 06:36 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:36 PST] no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
[2019-11-08 06:36 PST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2019-11-08 06:37 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:37 PST] no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
[2019-11-08 06:38 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:38 PST] dump1090 start appears to have been successful
[2019-11-08 06:38 PST] no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it…
[2019-11-08 06:38 PST] attempting to start dump1090…
[2019-11-08 06:38 PST] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2019-11-08 06:38 PST] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2019-11-08 06:39 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:39 PST] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2019-11-08 06:39 PST] multilateration data no longer required, disabling mlat client
[2019-11-08 06:39 PST] multilateration data requested
[2019-11-08 06:39 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:40 PST] Receiver location changed, restarting dump1090 and skyaware978
[2019-11-08 06:40 PST] attempting to restart skyaware978…
[2019-11-08 06:40 PST] site statistics URL: https://flightaware.com/adsb/stats/user/ramseyCatalan#stats-112814
[2019-11-08 06:40 PST] multilateration data requested
[2019-11-08 06:40 PST] attempting to restart dump1090-fa using ‘systemctl --no-block try-restart dump1090-fa.service < /dev/null’…
[2019-11-08 06:40 PST] skyaware978 restart appears to have been successful
[2019-11-08 06:40 PST] dump1090 restart appears to have been successful
[2019-11-08 06:40 PST] logged in to FlightAware as user ramseyCatalan
[2019-11-08 06:40 PST] attempting to restart dump1090…
[2019-11-08 06:40 PST] attempting to restart skyaware978 using ‘systemctl --no-block try-restart skyaware978.service < /dev/null’…
[2019-11-08 06:40 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:41 PST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2019-11-08 06:41 PST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2019-11-08 06:41 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:42 PST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2019-11-08 06:43 PST] no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
[2019-11-08 06:43 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:44 PST] no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it…
[2019-11-08 06:44 PST] attempting to start dump1090…
[2019-11-08 06:44 PST] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2019-11-08 06:44 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:46 PST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2019-11-08 06:46 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:47 PST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2019-11-08 06:47 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:48 PST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2019-11-08 06:48 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:49 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:50 PST] no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it…
[2019-11-08 06:50 PST] attempting to start dump1090-fa using ‘systemctl --no-block restart dump1090-fa.service < /dev/null’…
[2019-11-08 06:50 PST] dump1090 start appears to have been successful
[2019-11-08 06:50 PST] attempting to start dump1090…
[2019-11-08 06:50 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:51 PST] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware
[2019-11-08 06:51 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:52 PST] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2019-11-08 06:53 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:53 PST] no ADS-B data program seen listening on port 30005 for 190 seconds, next check in 60s
[2019-11-08 06:54 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:54 PST] no ADS-B data program seen listening on port 30005 for 250 seconds, next check in 60s
[2019-11-08 06:55 PST] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2019-11-08 06:55 PST] no ADS-B data program seen listening on port 30005 for 310 seconds, next check in 60s

I’m just guessing on this last photos:

Contact adsbsupport@flightaware.com

They will help help you with FlightFeeder issues.

I checked my orange FA-dongle and the components missing in your receiver are also missing in mine so I wouldn’t worry about that.
I guess the USB connector has been soldered manually so it seems normal so find some residual solder flux on the pcb between the usb-pins and the electrolytic capacitor TC3.

Then is a software problem… thank you… hopefully some one here can help.

Best regards

Most people here built their own receiver, buying hardware and using the piaware software image or installing it as a add-on on a standard linux image.

Your FA FlightFeeder uses a custom software and the hardware still belongs to FA, so you will still have to wait for them to help you.

And even thought the things you noted on the pcb are not unusual, the hardware could still be defective.

I have an Orange FlightFeeder and at some point the USB cable between the receiver and the Pi failed. Also the receiver wasn’t in that good of a shape - compared with another stand-alone FA receiver that I had bought for my personal Pi.
I have arranged the troubleshooting with FA people and they sent the replacement parts.
I would strongly suggest to get in touch with the FA support via email.

2 Likes

I posted something which didn’t fit to this thread.
Therefore i deleted it. The comment then is flagged and removed automatically. That’s the normal behavior of FA discussion board

This post was flagged by the community and is temporarily hidden.