# Disconnection/Data Feed Not Working

**URL:** <https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207>\
**Category:** ADS-B Flight Tracking\
**Created:** [September 2, 2017, 2:05am UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207 "2017-09-02T02:05:24Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![jleglen](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jleglen/32/439_2.png) [@jleglen](https://discussions.flightaware.com/u/jleglen)\
**Post date:** [September 2, 2017, 2:05am UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/1 "2017-09-02T02:05:25Z")

</div>

Over the past week, I have experienced loss of data on the Skyview page. The Feeder shows that it is checking in, but I am getting no data. Wi-fi connection is strong. The setup has been running flawlessly for 7 weeks, and just this past week the problem has come up. Any ideas?

Thanks

Log File:

[2017-09-01 19:06 EDT] 108 msgs recv’d from dump1090-fa (0 in last 5m); 108 msgs sent to FlightAware  
[2017-09-01 19:07 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 19:07 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 19:07 EDT] mlat-client(813): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)  
[2017-09-01 19:07 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 19:07 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 19:11 EDT] 108 msgs recv’d from dump1090-fa (0 in last 5m); 108 msgs sent to FlightAware  
[2017-09-01 19:16 EDT] 108 msgs recv’d from dump1090-fa (0 in last 5m); 108 msgs sent to FlightAware  
[2017-09-01 19:21 EDT] 108 msgs recv’d from dump1090-fa (0 in last 5m); 108 msgs sent to FlightAware  
[2017-09-01 19:22 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 19:22 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 19:22 EDT] mlat-client(813): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)  
[2017-09-01 19:22 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 19:22 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 19:26 EDT] 108 msgs recv’d from dump1090-fa (0 in last 5m); 108 msgs sent to FlightAware  
[2017-09-01 19:31 EDT] 108 msgs recv’d from dump1090-fa (0 in last 5m); 108 msgs sent to FlightAware  
[2017-09-01 19:36 EDT] 108 msgs recv’d from dump1090-fa (0 in last 5m); 108 msgs sent to FlightAware  
[2017-09-01 19:37 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 19:37 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 19:37 EDT] mlat-client(813): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)  
[2017-09-01 19:37 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 19:37 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 19:40 EDT] no new messages received in 3685 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart everything, just in case…  
[2017-09-01 19:40 EDT] faup1090 exited with SIG SIGHUP  
[2017-09-01 19:40 EDT] attempting to restart dump1090…  
[2017-09-01 19:40 EDT] attempting to restart dump1090-fa using ‘systemctl --no-block try-restart dump1090-fa.service \< /dev/null’…  
[2017-09-01 19:40 EDT] dump1090 restart appears to have been successful  
[2017-09-01 19:41 EDT] ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good  
[2017-09-01 19:41 EDT] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 32.907 --lon -79.801  
[2017-09-01 19:41 EDT] Started faup1090 (pid 2227) to connect to dump1090-fa  
[2017-09-01 19:41 EDT] 108 msgs recv’d from dump1090-fa (0 in last 5m); 108 msgs sent to FlightAware  
[2017-09-01 19:42 EDT] mlat-client(813): Lost connection to localhost:30005  
[2017-09-01 19:42 EDT] mlat-client(813): Reconnecting in 30.0 seconds  
[2017-09-01 19:42 EDT] mlat-client(813): Beast-format results connection with 127.0.0.1:30104: connection lost  
[2017-09-01 19:42 EDT] lost connection to dump1090-fa via faup1090  
[2017-09-01 19:42 EDT] faup1090 exited normally  
[2017-09-01 19:42 EDT] reconnecting to dump1090-fa  
[2017-09-01 19:42 EDT] ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good  
[2017-09-01 19:42 EDT] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 32.907 --lon -79.801  
[2017-09-01 19:42 EDT] Started faup1090 (pid 2269) to connect to dump1090-fa  
[2017-09-01 19:42 EDT] mlat-client(813): Input connected to localhost:30005  
[2017-09-01 19:42 EDT] mlat-client(813): Input format changed to BEAST, 12MHz clock  
[2017-09-01 19:42 EDT] mlat-client(813): Beast-format results connection with 127.0.0.1:30104: connection established  
[2017-09-01 19:46 EDT] 314 msgs recv’d from dump1090-fa (206 in last 5m); 314 msgs sent to FlightAware  
[2017-09-01 19:51 EDT] 538 msgs recv’d from dump1090-fa (224 in last 5m); 538 msgs sent to FlightAware  
[2017-09-01 19:52 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 19:52 EDT] mlat-client(813): Server status: clock unstable  
[2017-09-01 19:52 EDT] mlat-client(813): Receiver: 26.3 msg/s received 14.0 msg/s processed (53%)  
[2017-09-01 19:52 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server  
[2017-09-01 19:52 EDT] mlat-client(813): Results: 2.3 positions/minute  
[2017-09-01 19:52 EDT] mlat-client(813): Aircraft: 11 of 14 Mode S, 5 of 10 ADS-B used  
[2017-09-01 19:56 EDT] 694 msgs recv’d from dump1090-fa (156 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:01 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:06 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:07 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 20:07 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 20:07 EDT] mlat-client(813): Receiver: 4.5 msg/s received 2.5 msg/s processed (56%)  
[2017-09-01 20:07 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 20:07 EDT] mlat-client(813): Results: 1.2 positions/minute  
[2017-09-01 20:07 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 20:11 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:16 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:21 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:22 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 20:22 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 20:22 EDT] mlat-client(813): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)  
[2017-09-01 20:22 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 20:22 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 20:26 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:31 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:36 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:37 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 20:37 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 20:37 EDT] mlat-client(813): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)  
[2017-09-01 20:37 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 20:37 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 20:41 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:46 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:51 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:52 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 20:52 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 20:52 EDT] mlat-client(813): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)  
[2017-09-01 20:52 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 20:52 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 20:55 EDT] no new messages received in 3703 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart everything, just in case…  
[2017-09-01 20:55 EDT] faup1090 exited with SIG SIGHUP  
[2017-09-01 20:55 EDT] attempting to restart dump1090…  
[2017-09-01 20:55 EDT] attempting to restart dump1090-fa using ‘systemctl --no-block try-restart dump1090-fa.service \< /dev/null’…  
[2017-09-01 20:55 EDT] dump1090 restart appears to have been successful  
[2017-09-01 20:56 EDT] ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good  
[2017-09-01 20:56 EDT] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 32.907 --lon -79.801  
[2017-09-01 20:56 EDT] Started faup1090 (pid 2990) to connect to dump1090-fa  
[2017-09-01 20:56 EDT] 694 msgs recv’d from dump1090-fa (0 in last 5m); 694 msgs sent to FlightAware  
[2017-09-01 20:57 EDT] mlat-client(813): Lost connection to localhost:30005  
[2017-09-01 20:57 EDT] mlat-client(813): Reconnecting in 30.0 seconds  
[2017-09-01 20:57 EDT] mlat-client(813): Beast-format results connection with 127.0.0.1:30104: connection lost  
[2017-09-01 20:57 EDT] lost connection to dump1090-fa via faup1090  
[2017-09-01 20:57 EDT] faup1090 exited normally  
[2017-09-01 20:57 EDT] reconnecting to dump1090-fa  
[2017-09-01 20:57 EDT] ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good  
[2017-09-01 20:57 EDT] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 32.907 --lon -79.801  
[2017-09-01 20:57 EDT] Started faup1090 (pid 3028) to connect to dump1090-fa  
[2017-09-01 20:57 EDT] mlat-client(813): Input connected to localhost:30005  
[2017-09-01 20:57 EDT] mlat-client(813): Input format changed to BEAST, 12MHz clock  
[2017-09-01 20:57 EDT] mlat-client(813): Beast-format results connection with 127.0.0.1:30104: connection established  
[2017-09-01 21:01 EDT] 986 msgs recv’d from dump1090-fa (292 in last 5m); 986 msgs sent to FlightAware  
[2017-09-01 21:06 EDT] 1298 msgs recv’d from dump1090-fa (312 in last 5m); 1298 msgs sent to FlightAware  
[2017-09-01 21:07 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 21:07 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 21:07 EDT] mlat-client(813): Receiver: 43.4 msg/s received 19.7 msg/s processed (45%)  
[2017-09-01 21:07 EDT] mlat-client(813): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.3kB/s UDP to server  
[2017-09-01 21:07 EDT] mlat-client(813): Results: 29.2 positions/minute  
[2017-09-01 21:07 EDT] mlat-client(813): Aircraft: 11 of 17 Mode S, 6 of 7 ADS-B used  
[2017-09-01 21:11 EDT] 1388 msgs recv’d from dump1090-fa (90 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:16 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:21 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:22 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 21:22 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 21:22 EDT] mlat-client(813): Receiver: 0.9 msg/s received 0.4 msg/s processed (44%)  
[2017-09-01 21:22 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 21:22 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 21:26 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:31 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:36 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:37 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 21:37 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 21:37 EDT] mlat-client(813): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)  
[2017-09-01 21:37 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 21:37 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 21:41 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:46 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:51 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 21:52 EDT] mlat-client(813): Receiver status: connected  
[2017-09-01 21:52 EDT] mlat-client(813): Server status: not synchronized with any nearby receivers  
[2017-09-01 21:52 EDT] mlat-client(813): Receiver: 0.0 msg/s received 0.0 msg/s processed (0%)  
[2017-09-01 21:52 EDT] mlat-client(813): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server  
[2017-09-01 21:52 EDT] mlat-client(813): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
[2017-09-01 21:56 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware  
[2017-09-01 22:01 EDT] 1388 msgs recv’d from dump1090-fa (0 in last 5m); 1388 msgs sent to FlightAware

---

<div class="post-metadata">

**Author:** ![jonhawkes2030](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jonhawkes2030/32/113977_2.png) [@jonhawkes2030](https://discussions.flightaware.com/u/jonhawkes2030)\
**Post date:** [September 2, 2017, 2:22am UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/2 "2017-09-02T02:22:09Z")

</div>

Check the antenna connection.  
Loose connectors or water in them.

---

<div class="post-metadata">

**Author:** ![jleglen](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jleglen/32/439_2.png) [@jleglen](https://discussions.flightaware.com/u/jleglen)\
**Post date:** [September 2, 2017, 2:29am UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/3 "2017-09-02T02:29:29Z")

</div>

Forgot to mention - that was one of the first things I checked. I’m using the [Flight Aware Antenna](https://www.amazon.com/1090MHz-ADS-B-Antenna-66cm-26in/dp/B00WZL6WPO), which has been great. Connection to the dongle and antenna are good.

---

<div class="post-metadata">

**Author:** ![jonhawkes2030](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jonhawkes2030/32/113977_2.png) [@jonhawkes2030](https://discussions.flightaware.com/u/jonhawkes2030)\
**Post date:** [September 2, 2017, 2:42am UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/4 "2017-09-02T02:42:42Z")

</div>

Is the N connector on the coax a 50 per 75Ohm version?  
The 75 Ohm version has a smaller pin and can make intermittent contact with the antenna.

---

<div class="post-metadata">

**Author:** ![jleglen](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jleglen/32/439_2.png) [@jleglen](https://discussions.flightaware.com/u/jleglen)\
**Post date:** [September 2, 2017, 3:11am UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/5 "2017-09-02T03:11:16Z")

</div>

It’s 50. I also am into ham radio and I have a bunch of it.

---

<div class="post-metadata">

**Author:** ![jonhawkes2030](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jonhawkes2030/32/113977_2.png) [@jonhawkes2030](https://discussions.flightaware.com/u/jonhawkes2030)\
**Post date:** [September 2, 2017, 3:41am UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/6 "2017-09-02T03:41:56Z")

</div>

Ham too.  
Maybe a problem with the dongle or USB connection or cable.

There was a recent post about a Ham wiping out his ads-b receiver with his transmitter. The outage looks to be too long for that.

---

<div class="post-metadata">

**Author:** ![jleglen](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jleglen/32/439_2.png) [@jleglen](https://discussions.flightaware.com/u/jleglen)\
**Post date:** [September 2, 2017, 11:20pm UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/7 "2017-09-02T23:20:41Z")

</div>

I may have found the source of the problem. A bad USB port in the Raspberry Pi. So far, so good - no drops. Fingers crossed.

---

<div class="post-metadata">

**Author:** ![jonhawkes2030](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jonhawkes2030/32/113977_2.png) [@jonhawkes2030](https://discussions.flightaware.com/u/jonhawkes2030)\
**Post date:** [September 2, 2017, 11:44pm UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/8 "2017-09-02T23:44:48Z")

</div>

I use decent USB 3.0 pigtails with ferrite chokes just to be sure(and to have enough room for multiple dongles).

Good luck.

Jon

---

<div class="post-metadata">

**Author:** ![jleglen](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jleglen/32/439_2.png) [@jleglen](https://discussions.flightaware.com/u/jleglen)\
**Post date:** [September 2, 2017, 11:57pm UTC](https://discussions.flightaware.com/t/disconnection-data-feed-not-working/25207/9 "2017-09-02T23:57:14Z")

</div>

Thanks for your help. I’m going to order pigtails now.