Was my blue receiver just fried?

[ExCalbr]

We just had a very strong storm blow through. I have two receivers. The one that had been out of service for a while was just starting to ramp up again. I was watching the stats steadily improve. Then the storm hit, and activity dropped to zero. Investigating, I determined that the power supply was fried, so I replaced it with another, and the RPi zero starts up just fine. My local connection shows a map but no aircraft and Skyaware unknown version. Is the receiver fried? Or maybe I need to just re-image the SD card? If I do the latter, how can I continue with the same site ID: 24859.

Here’s what I can see of the logs (storm started around 18:30 local):

Refresh Log

[2025-05-28 17:05 CDT] 1694592 msgs recv’d from dump1090-fa (2644 in last 5m); 1694592 msgs sent to FlightAware
[2025-05-28 17:10 CDT] 1697141 msgs recv’d from dump1090-fa (2549 in last 5m); 1697141 msgs sent to FlightAware
[2025-05-28 17:12 CDT] mlat-client(3202): Server: 0.0 kB/s from server 0.0kB/s TCP to server 2.6kB/s UDP to server
[2025-05-28 17:12 CDT] mlat-client(3202): Results: 11.7 positions/minute
[2025-05-28 17:12 CDT] mlat-client(3202): Server status: synchronized with 409 nearby receivers
[2025-05-28 17:12 CDT] mlat-client(3202): Receiver status: connected
[2025-05-28 17:12 CDT] mlat-client(3202): Receiver: 586.0 msg/s received 276.3 msg/s processed (47%)
[2025-05-28 17:12 CDT] mlat-client(3202): Aircraft: 13 of 19 Mode S, 58 of 90 ADS-B used
[2025-05-28 17:15 CDT] 1699746 msgs recv’d from dump1090-fa (2605 in last 5m); 1699746 msgs sent to FlightAware
[2025-05-28 17:20 CDT] 1702304 msgs recv’d from dump1090-fa (2558 in last 5m); 1702304 msgs sent to FlightAware
[2025-05-28 17:25 CDT] 1705008 msgs recv’d from dump1090-fa (2704 in last 5m); 1705008 msgs sent to FlightAware
[2025-05-28 17:27 CDT] mlat-client(3202): Receiver status: connected
[2025-05-28 17:27 CDT] mlat-client(3202): Results: 16.4 positions/minute
[2025-05-28 17:27 CDT] mlat-client(3202): Server status: synchronized with 407 nearby receivers
[2025-05-28 17:27 CDT] mlat-client(3202): Aircraft: 10 of 19 Mode S, 60 of 79 ADS-B used
[2025-05-28 17:27 CDT] mlat-client(3202): Server: 0.0 kB/s from server 0.0kB/s TCP to server 2.8kB/s UDP to server
[2025-05-28 17:27 CDT] mlat-client(3202): Receiver: 567.3 msg/s received 267.9 msg/s processed (47%)
[2025-05-28 17:30 CDT] 1707786 msgs recv’d from dump1090-fa (2778 in last 5m); 1707786 msgs sent to FlightAware
[2025-05-28 17:35 CDT] 1710445 msgs recv’d from dump1090-fa (2659 in last 5m); 1710445 msgs sent to FlightAware
[2025-05-28 17:40 CDT] 1712948 msgs recv’d from dump1090-fa (2503 in last 5m); 1712948 msgs sent to FlightAware
[2025-05-28 17:42 CDT] mlat-client(3202): Receiver status: connected
[2025-05-28 17:42 CDT] mlat-client(3202): Server: 0.0 kB/s from server 0.0kB/s TCP to server 2.8kB/s UDP to server
[2025-05-28 17:42 CDT] mlat-client(3202): Receiver: 544.7 msg/s received 262.6 msg/s processed (48%)
[2025-05-28 17:42 CDT] mlat-client(3202): Aircraft: 8 of 17 Mode S, 60 of 90 ADS-B used
[2025-05-28 17:42 CDT] mlat-client(3202): Server status: synchronized with 436 nearby receivers
[2025-05-28 17:42 CDT] mlat-client(3202): Results: 13.8 positions/minute
[2025-05-28 17:45 CDT] 1715240 msgs recv’d from dump1090-fa (2292 in last 5m); 1715240 msgs sent to FlightAware
[2025-05-28 17:50 CDT] 1717289 msgs recv’d from dump1090-fa (2049 in last 5m); 1717289 msgs sent to FlightAware
[2025-05-28 17:55 CDT] 1719174 msgs recv’d from dump1090-fa (1885 in last 5m); 1719174 msgs sent to FlightAware
[2025-05-28 17:57 CDT] mlat-client(3202): Receiver status: connected
[2025-05-28 17:57 CDT] mlat-client(3202): Aircraft: 9 of 15 Mode S, 51 of 85 ADS-B used
[2025-05-28 17:57 CDT] mlat-client(3202): Server: 0.0 kB/s from server 0.0kB/s TCP to server 2.7kB/s UDP to server
[2025-05-28 17:57 CDT] mlat-client(3202): Receiver: 539.2 msg/s received 253.9 msg/s processed (47%)
[2025-05-28 17:57 CDT] mlat-client(3202): Server status: synchronized with 487 nearby receivers
[2025-05-28 17:57 CDT] mlat-client(3202): Results: 15.4 positions/minute
[2025-05-28 18:00 CDT] 1721396 msgs recv’d from dump1090-fa (2222 in last 5m); 1721396 msgs sent to FlightAware
[2025-05-28 18:05 CDT] 1723330 msgs recv’d from dump1090-fa (1934 in last 5m); 1723330 msgs sent to FlightAware
[2025-05-28 18:10 CDT] 1725392 msgs recv’d from dump1090-fa (2062 in last 5m); 1725392 msgs sent to FlightAware
[2025-05-28 18:12 CDT] mlat-client(3202): Results: 16.5 positions/minute
[2025-05-28 18:12 CDT] mlat-client(3202): Server status: synchronized with 405 nearby receivers
[2025-05-28 18:12 CDT] mlat-client(3202): Aircraft: 7 of 11 Mode S, 50 of 77 ADS-B used
[2025-05-28 18:12 CDT] mlat-client(3202): Server: 0.0 kB/s from server 0.0kB/s TCP to server 2.7kB/s UDP to server
[2025-05-28 18:12 CDT] mlat-client(3202): Receiver: 553.1 msg/s received 254.9 msg/s processed (46%)
[2025-05-28 18:12 CDT] mlat-client(3202): Receiver status: connected
[2025-05-28 18:15 CDT] 1727444 msgs recv’d from dump1090-fa (2052 in last 5m); 1727444 msgs sent to FlightAware
[2025-05-28 18:20 CDT] 1729577 msgs recv’d from dump1090-fa (2133 in last 5m); 1729577 msgs sent to FlightAware
[2025-05-28 18:25 CDT] 1731865 msgs recv’d from dump1090-fa (2288 in last 5m); 1731865 msgs sent to FlightAware
[2025-05-28 18:27 CDT] mlat-client(3202): Server: 0.1 kB/s from server 0.0kB/s TCP to server 2.7kB/s UDP to server
[2025-05-28 18:27 CDT] mlat-client(3202): Receiver status: connected
[2025-05-28 18:27 CDT] mlat-client(3202): Aircraft: 5 of 9 Mode S, 62 of 81 ADS-B used
[2025-05-28 18:27 CDT] mlat-client(3202): Receiver: 542.2 msg/s received 253.3 msg/s processed (47%)
[2025-05-28 18:27 CDT] mlat-client(3202): Server status: synchronized with 461 nearby receivers
[2025-05-28 18:27 CDT] mlat-client(3202): Results: 22.0 positions/minute
[2025-05-28 18:30 CDT] 1734053 msgs recv’d from dump1090-fa (2188 in last 5m); 1734053 msgs sent to FlightAware
[2025-05-28 18:35 CDT] logged in to FlightAware as user ExCalbr
[2025-05-28 18:35 CDT] multilateration data requested
[2025-05-28 18:35 CDT] my feeder ID is fc8e7018-5f0d-4180-43ca-0a8d9a6597d0
[2025-05-28 18:35 CDT] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 206.253.80.198:12659:1793188260
[2025-05-28 18:35 CDT] site statistics URL: https://flightaware.com/adsb/stats/user/ExCalbr#stats-24859
[2025-05-28 18:35 CDT] mlat-client(32221): Listening for Extended Basestation-format results connection on port 30106
[2025-05-28 18:35 CDT] mlat-client(32221): fa-mlat-client 0.2.13 starting up
[2025-05-28 18:35 CDT] mlat-client(32221): Input connected to localhost:30005
[2025-05-28 18:35 CDT] mlat-client(32221): Using UDP transport to 206.253.80.198 port 12659
[2025-05-28 18:35 CDT] mlat-client(32221): Route MTU changed to 1500
[2025-05-28 18:35 CDT] mlat-client(32221): Listening for Beast-format results connection on port 30105
[2025-05-28 18:35 CDT] mlat-client(32221): Input format changed to BEAST, 12MHz clock
[2025-05-28 18:35 CDT] mlat-client(32221): Beast-format results connection with ::1:30104: connection established
[2025-05-28 18:40 CDT] 1738245 msgs recv’d from dump1090-fa (2046 in last 5m); 1738002 msgs sent to FlightAware
[2025-05-28 18:45 CDT] 1740339 msgs recv’d from dump1090-fa (2094 in last 5m); 1740096 msgs sent to FlightAware
[2025-05-28 18:46 CDT] site statistics URL: https://flightaware.com/adsb/stats/user/ExCalbr#stats-24859
[2025-05-28 18:46 CDT] logged in to FlightAware as user ExCalbr
[2025-05-28 18:46 CDT] multilateration data requested
[2025-05-28 18:46 CDT] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 206.253.80.201:11035:1326048038
[2025-05-28 18:46 CDT] my feeder ID is fc8e7018-5f0d-4180-43ca-0a8d9a6597d0
[2025-05-28 18:46 CDT] mlat-client(1649): fa-mlat-client 0.2.13 starting up
[2025-05-28 18:46 CDT] mlat-client(1649): Listening for Beast-format results connection on port 30105
[2025-05-28 18:46 CDT] mlat-client(1649): Using UDP transport to 206.253.80.201 port 11035
[2025-05-28 18:46 CDT] mlat-client(1649): Input format changed to BEAST, 12MHz clock
[2025-05-28 18:46 CDT] mlat-client(1649): Route MTU changed to 1500
[2025-05-28 18:46 CDT] mlat-client(1649): Input connected to localhost:30005
[2025-05-28 18:46 CDT] mlat-client(1649): Listening for Extended Basestation-format results connection on port 30106
[2025-05-28 18:46 CDT] mlat-client(1649): Beast-format results connection with ::1:30104: connection established
[2025-05-28 18:50 CDT] 1742152 msgs recv’d from dump1090-fa (1813 in last 5m); 1741873 msgs sent to FlightAware
[2025-05-28 18:55 CDT] 1743963 msgs recv’d from dump1090-fa (1811 in last 5m); 1743684 msgs sent to FlightAware
[2025-05-28 19:45 CDT] multilateration data requested
[2025-05-28 19:45 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:45 CDT] site statistics URL: https://flightaware.com/adsb/stats/user/ExCalbr#stats-24859
[2025-05-28 19:45 CDT] adept reported location: 30.35743, -97.72322, 782ft AMSL
[2025-05-28 19:45 CDT] my feeder ID is fc8e7018-5f0d-4180-43ca-0a8d9a6597d0
[2025-05-28 19:45 CDT] logged in to FlightAware as user ExCalbr
[2025-05-28 19:45 CDT] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2025-05-28 19:45 CDT] no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
[2025-05-28 19:46 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:46 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:46 CDT] multilateration data requested
[2025-05-28 19:46 CDT] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2025-05-28 19:46 CDT] 0 msgs recv’d from dump1090 (0 in last 89m); 0 msgs sent to FlightAware
[2025-05-28 19:47 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:47 CDT] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2025-05-28 19:48 CDT] piaware (process 430) is exiting…
[2025-05-28 19:48 CDT] update request complete
[2025-05-28 19:48 CDT] multilateration data no longer required, disabling mlat client
[2025-05-28 19:48 CDT] performing manual update, action: restart_piaware
[2025-05-28 19:48 CDT] restarting piaware. hopefully i’ll be right back…
[2025-05-28 19:48 CDT] manual update (user-initiated via their flightaware control page) requested by adept server
[2025-05-28 19:48 CDT] piaware (process 430) is shutting down because it received a shutdown signal (SIGTERM) from the system…
[2025-05-28 19:48 CDT] attempting to restart piaware using ‘systemctl --no-block try-restart piaware.service < /dev/null’…
[2025-05-28 19:48 CDT] no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
[2025-05-28 19:48 CDT] logged in to FlightAware as user ExCalbr
[2025-05-28 19:48 CDT] my feeder ID is fc8e7018-5f0d-4180-43ca-0a8d9a6597d0
[2025-05-28 19:48 CDT] multilateration data requested
[2025-05-28 19:48 CDT] adept reported location: 30.35743, -97.72322, 782ft AMSL
[2025-05-28 19:48 CDT] site statistics URL: https://flightaware.com/adsb/stats/user/ExCalbr#stats-24859
[2025-05-28 19:48 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:48 CDT] UAT support disabled by local configuration setting: uat-receiver-type
[2025-05-28 19:48 CDT] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2025-05-28 19:48 CDT] performing manual update, action: restart_dump1090
[2025-05-28 19:48 CDT] attempting to restart dump1090..
[2025-05-28 19:48 CDT] update request complete
[2025-05-28 19:48 CDT] dump1090 restart appears to have been successful
[2025-05-28 19:48 CDT] attempting to restart dump1090-fa using ‘systemctl --no-block try-restart dump1090-fa.service < /dev/null’…
[2025-05-28 19:48 CDT] manual update (user-initiated via their flightaware control page) requested by adept server
[2025-05-28 19:49 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:49 CDT] no ADS-B data program seen listening on port 30005 for 64 seconds, next check in 60s
[2025-05-28 19:50 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:50 CDT] no ADS-B data program seen listening on port 30005 for 124 seconds, next check in 60s
[2025-05-28 19:51 CDT] site statistics URL: https://flightaware.com/adsb/stats/user/ExCalbr#stats-24859
[2025-05-28 19:51 CDT] multilateration data requested
[2025-05-28 19:51 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:51 CDT] adept reported location: 30.35743, -97.72322, 782ft AMSL
[2025-05-28 19:51 CDT] my feeder ID is fc8e7018-5f0d-4180-43ca-0a8d9a6597d0
[2025-05-28 19:51 CDT] logged in to FlightAware as user ExCalbr
[2025-05-28 19:52 CDT] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2025-05-28 19:52 CDT] no ADS-B data program seen listening on port 30005 for 63 seconds, next check in 60s
[2025-05-28 19:52 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:52 CDT] multilateration data requested
[2025-05-28 19:52 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:52 CDT] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2025-05-28 19:53 CDT] 0 msgs recv’d from dump1090 (0 in last 95m); 0 msgs sent to FlightAware
[2025-05-28 19:53 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:53 CDT] no ADS-B data program seen listening on port 30005 for 70 seconds, next check in 60s
[2025-05-28 19:54 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:54 CDT] no ADS-B data program seen listening on port 30005 for 130 seconds, next check in 60s
[2025-05-28 19:55 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:55 CDT] site statistics URL: https://flightaware.com/adsb/stats/user/ExCalbr#stats-24859
[2025-05-28 19:55 CDT] my feeder ID is fc8e7018-5f0d-4180-43ca-0a8d9a6597d0
[2025-05-28 19:55 CDT] multilateration data requested
[2025-05-28 19:55 CDT] logged in to FlightAware as user ExCalbr
[2025-05-28 19:55 CDT] adept reported location: 30.35743, -97.72322, 782ft AMSL
[2025-05-28 19:55 CDT] 0 msgs recv’d from dump1090; 0 msgs sent to FlightAware
[2025-05-28 19:56 CDT] no ADS-B data program seen listening on port 30005 for 64 seconds, next check in 60s
[2025-05-28 19:56 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:56 CDT] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2025-05-28 19:57 CDT] 0 msgs recv’d from dump1090 (0 in last 99m); 0 msgs sent to FlightAware
[2025-05-28 19:57 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:57 CDT] no ADS-B data program seen listening on port 30005 for 71 seconds, next check in 60s
[2025-05-28 19:58 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:58 CDT] no ADS-B data program seen listening on port 30005 for 131 seconds, next check in 60s
[2025-05-28 19:59 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 19:59 CDT] no ADS-B data program seen listening on port 30005 for 191 seconds, next check in 60s
[2025-05-28 20:00 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 20:00 CDT] no ADS-B data program seen listening on port 30005 for 251 seconds, next check in 60s
[2025-05-28 20:01 CDT] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2025-05-28 20:01 CDT] no ADS-B data program seen listening on port 30005 for 311 seconds, next check in 60s
[2025-05-28 20:02 CDT] 0 msgs recv’d from dump1090 (0 in last 5m); 0 msgs sent to FlightAware

[ExCalbr]

Here’s the storm that just blew past. Looks like another one is coming.

[ExCalbr]

I found a similar post and followed instructions. Looks like the dongle is fried.

pi@piaware:~ $ sudo apt install stl-sdr

Reading package lists… Done

Building dependency tree… Done

Reading state information… Done

E: Unable to locate package stl-sdr

pi@piaware:~ $ sudo systemctl stop piaware dump1090-fa dump978-fa

pi@piaware:~ $ rtl_test -t

No supported devices found.

[ExCalbr]

On a whim I decided to swap the two mini USB ports (traded the power supply for the dongle connection. Now it’s working.

[ExCalbr]

Well, I had one good day. Then on Friday, although I was getting messages, the levels were low. See graphs for both my feeders here.

[ExCalbr]

I bought another blue feeder, and it seems to have made no difference. Yet there is a clear change on the day of the hailstorm. I disconnected everything, cleaned the connections at the RPi end, then reconnected, making sure everything was firm. It didn’t seem to make a difference. The other option is the antenna end. I’m using a FA antenna. It has a larger connector than at the RPi end. I had to climb up to the roof to inspect it. It seems firm. I was going to unscrew it and screw it back in, but I didn’t bring any tools with me up to the roof, and I was unable to unscrew it by hand. I wonder if something got jarred loose inside the antenna housing. Is there a diagram of what it’s like inside? The first image shows the messages received from May 13 until today. May 29 is when the storm hit. The second image shows a similar graph from my other feeder. The 250+ miles count has also dropped from a few dozen on average to zero.

[ExCalbr]

Never mind about the inside of the antenna. I found pictures on the forum.

[dongerrard204]

Are all of your outside coax connections well weatherproofed?

[ExCalbr]

The one at the base of the antenna (9 year-old antenna btw) is just what comes with the Flightaware antenna. It has a large screw-in housing that seems to protect the inner real connector. I’ve assumed this design was intended to be weatherproof. I added nothing extra on that end. The other end, by the RPi is sheltered, but still outside. Should I be doing something else at the antenna end? Edit: what I stated is false. The cable is one I bought last year.

[ExCalbr]

Doing a search I see it’s recommended to seal the connection with self-amalgamating tape or something. I have not done that. Perhaps I’ll bring the antenna down, take the connection apart, clean thoroughly and tape it up when I next have some time. If any storm could introduce water infiltration it was that one. We got and inch and a half of rain in 10 minutes. There was a microburst right over my location.

[abcd567]

For Beginners - Howto Connect FlightAware Antenna, Filter and Pro Stick - Connectors and Cables Required

Please scroll-up to see previous post for arrangement of Antenna, Connectors, Cable, Filter and ProStick. How-to Protect Outdoor Connectors and Cable From Ingress of Moisture (Due to Rain & Snow) and Resulting Short circuit, Corrosion, and Drop in Performance. The simplest way to protect your connectors and cable from ingress of moisture is to wrap self-amalgamating / self-fusing / self-bonding tape over the connectors. Please do NOT use ordinary electrical PVC tape as it wont protect properl…

[ExCalbr]

I just opened the FlightAware antenna using a pipe cutter to cut the fiberglass tube open, since there didn’t seem to be a way to otherwise take it apart. The interior of the antenna has several sections of wire connected by something, which I can’t see because they are covered with foam. Those pieces of foam were sopping wet. I didn’t think it was possible for moisture to get into the interior, but it obviously did.

[abcd567]

Flightaware 1090 MHz Antenna internal view

 

[ExCalbr]

[ExCalbr]

I put the antenna in my car to dry. Then I removed the foam and installed it on my inside feeder, that has been using my homemade spider antenna. It’s back to performing better than my spider antenna. Since it’ll be used indoors now, I’m not going to bother putting the fiberglass cover back on.

[wiedehopf]

@ExCalbr

not going to bother putting the fiberglass cover back on.

Materials around the antenna can influence its tuning.
So there can be a performance impact when not restoring it.
But it’s probably not much for this design.