My Pi Keeps loosing Wifi Connection?

FlightAware ADS-B Flight Tracking
1

Can anyone tell me why my RP keeps getting kicked off my Wi-Fi. Signal is strong enough. I am unplugging the power and restarting it once a day at least. When I unplug it and plug it back in it reconnects fine and will stay on for hours.

[2022-11-28 16:12 PST] mlat-client(2623): Receiver status: connected
[2022-11-28 16:12 PST] mlat-client(2623): Server status: synchronized with 354 nearby receivers
[2022-11-28 16:12 PST] mlat-client(2623): Receiver: 68.5 msg/s received 34.3 msg/s processed (50%)
[2022-11-28 16:14 PST] 89106 msgs recv’d from dump1090-fa (991 in last 5m); 89106 msgs sent to FlightAware
[2022-11-28 16:19 PST] 89924 msgs recv’d from dump1090-fa (818 in last 5m); 89924 msgs sent to FlightAware
[2022-11-28 16:26 PST] mlat-client(2623): Route MTU changed to 1500
[2022-11-28 16:27 PST] mlat-client(2623): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server
[2022-11-28 16:27 PST] mlat-client(2623): Server status: synchronized with 312 nearby receivers
[2022-11-28 16:27 PST] mlat-client(2623): Aircraft: 9 of 14 Mode S, 18 of 19 ADS-B used
[2022-11-28 16:29 PST] 91642 msgs recv’d from dump1090-fa (912 in last 5m); 91642 msgs sent to FlightAware
[2022-11-28 16:34 PST] 92697 msgs recv’d from dump1090-fa (1055 in last 5m); 92697 msgs sent to FlightAware
[2022-11-28 16:39 PST] 94026 msgs recv’d from dump1090-fa (1329 in last 5m); 94026 msgs sent to FlightAware
[2022-11-28 16:42 PST] mlat-client(2623): Server status: synchronized with 373 nearby receivers
[2022-11-28 16:42 PST] mlat-client(2623): Receiver status: connected
[2022-11-28 16:42 PST] mlat-client(2623): Results: 4.4 positions/minute
[2022-11-28 16:42 PST] mlat-client(2623): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.5kB/s UDP to server
[2022-11-28 16:42 PST] mlat-client(2623): Receiver: 90.2 msg/s received 46.0 msg/s processed (51%)
[2022-11-28 16:49 PST] 95352 msgs recv’d from dump1090-fa (533 in last 5m); 95352 msgs sent to FlightAware
[2022-11-28 16:54 PST] 95625 msgs recv’d from dump1090-fa (273 in last 5m); 95625 msgs sent to FlightAware
[2022-11-28 16:57 PST] mlat-client(2623): Receiver: 39.9 msg/s received 18.7 msg/s processed (47%)
[2022-11-28 16:57 PST] mlat-client(2623): Results: 0.2 positions/minute
[2022-11-28 16:57 PST] mlat-client(2623): Receiver status: connected
[2022-11-28 16:57 PST] mlat-client(2623): Server status: synchronized with 367 nearby receivers
[2022-11-28 16:57 PST] mlat-client(2623): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.3kB/s UDP to server
[2022-11-28 17:09 PST] 96795 msgs recv’d from dump1090-fa (466 in last 5m); 96795 msgs sent to FlightAware
[2022-11-28 17:12 PST] mlat-client(2623): Results: 5.3 positions/minute
[2022-11-28 17:12 PST] mlat-client(2623): Receiver: 46.1 msg/s received 25.8 msg/s processed (56%)
[2022-11-28 17:12 PST] mlat-client(2623): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.3kB/s UDP to server
[2022-11-28 17:14 PST] 97252 msgs recv’d from dump1090-fa (457 in last 5m); 97252 msgs sent to FlightAware
[2022-11-28 17:16 PST] mlat-client(2623): Route MTU changed to 1476

2

The single most common failure point is the PSU.
Try a different USB charger and see if that helps.

1 Like
3

Even with the CanaKit 3.5A Raspberry Pi 4 Power Supply? It’s only going down once a day.

4

Not seen any complaints of those, but it’s such an easy thing to eliminate.

5

Will do. Thank you and I’ll get an OEM charger.

6

Command to check dc voltage

sudo dmesg --ctime | grep voltage

If above command gives no output, then dc voltage is ok.

 

7

If you are using 5 Ghz wifi, try gearing down to 2.4 Ghz to see if that brings a more stable connection. If you’re already using 2.4 Ghz, you could select another channel in your router as there could be interference or overloading on the channel currently in use.

8

I am using 2.4 thanks

9

I battled this same situation for months and never could find a solution for the WiFi dropping - except for switching to Ethernet connection. Once I did that no more connectivity issues.

10

It’s been stable today. I’m waiting to see what happens.

11

Is there any kind of diagnostic check I can run on this Pi?

12

Bought my own router and got rid of the comcast crap. Changed to Channel 1 on the 2.4ghz Wifi. We will see how this works out.

13

I will be interested how you make out. At the time I was using Spectrum supplied router. A few weeks ago I bought my own equipment. But I have not tried going back to WiFi to see if it would work. I really don’t need to now but I am curious to know if the router is/was the problem.

14

I haven’t been on this forum in many months. The last 2 days was the first I have posted in those many months. Today my FA went down. Coincidence? When I first set up FA several years ago 2 computers that were on line got trashed. Today a computer that was on line got trashed at the same time my FA went down. Coincidence?

15

I hope it wasn’t my bad luck lol

16

Well I have gone about 36 hours and have not been kicked off of WIFI. I have come to the consensus that running my feed on a Comcast provided rental gateway is not a good idea. You have very little control due to comcast locking it up. I bought my own Netgear Wifi Gateway yesterday and and now running on 2.4GHZ on Channel 1. Comcast had me on Channel 11 and you cannot change channels on their provided Gateway. I am running most of my home devices on the 5ghz band and running the Pi and a couple smart outlets and that’s it. I have come to the consensus if your going to run Wifi you might want to run it on your own personally owned Gateway and stay away from your Internet provided unit and have little to no control. I think now I am running my Pi on a cleaner channel and being in an apartment complex there might be several people using these ISP provided units and all on the same Channel 11?? I will report back if it gets kicked offline again…but so far so good.

17

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