hi,
A couple of months ago i set up an RS2 as a permanent base station on the roof of a building. It has access to a wifi network with good signal, however, it’s sporadically losing its connection to the wifi network which means we lose corrections via NTRIP. Sometimes it will stay connected for a few days, sometimes connection is lost within 24 h. The RS2 is not turning off, just losing connection to the wifi. It’s possible there is an issue with the Access Point its connecting to, but I’d like to rule out any issues with the RS2. Rebooting the RS2 restores the connection.
The firmware is 31.8 (latest available), it’s connected to a 12v power supply via Ext cable and set to turn on/off with the power supply. The power supply stays on.
Is there anything in a log file that might indicate why the wifi connection is lost? e.g. could it tell me if its a specific time of the day that the connection is lost?
How do i access log file?
You’ll probably find more/better info in the WiFi AP logs. Do you have a single AP or more than one with the same network SSID, and are there other 2.4GHz WiFi networks in the area?
If there are other 2.4GHz networks in the area it may be that the AP is changing band to try get less collision/intereference with the other nets, and the RS2 isn’t always following it.
thanks. I’ve asked our IT dept. to look at the AP logs or send them to me, and check the channel settings or logs of changes to channels.
There are lots of APs broadcasting the same SSID, but i think there’s only one that is visible to the RS2, certainly only one that is close enough to provide a good signal.
Does anyone know whether this is signs of an issue with connection to the wifi network?
Blockquote
May 15 09:52:33 Reach NetworkManager[591]: [1715766753.2837] device[77e04291b4d185f3] (wlan0): wifi-scan: scanning requested but not allowed at this time
May 15 09:52:33 Reach NetworkManager[591]: [1715766753.2839] device[77e04291b4d185f3] (wlan0): wifi-scan: scheduled in 120 seconds (interval now 120 seconds)
May 15 09:54:33 Reach NetworkManager[591]: [1715766873.2844] device[77e04291b4d185f3] (wlan0): wifi-scan: scanning requested but not allowed at this time
May 15 09:54:33 Reach NetworkManager[591]: [1715766873.2846] device[77e04291b4d185f3] (wlan0): wifi-scan: scheduled in 120 seconds (interval now 120 seconds)
May 15 09:56:33 Reach NetworkManager[591]: [1715766993.2844] device[77e04291b4d185f3] (wlan0): wifi-scan: scanning requested but not allowed at this time
May 15 09:56:33 Reach NetworkManager[591]: [1715766993.2846] device[77e04291b4d185f3] (wlan0): wifi-scan: scheduled in 120 seconds (interval now 120 seconds)
May 15 09:58:33 Reach NetworkManager[591]: [1715767113.2842] device[77e04291b4d185f3] (wlan0): wifi-scan: scanning requested but not allowed at this time
May 15 09:58:33 Reach NetworkManager[591]: [1715767113.2845] device[77e04291b4d185f3] (wlan0): wifi-scan: scheduled in 120 seconds (interval now 120 seconds)
May 15 10:00:33 Reach NetworkManager[591]: [1715767233.2851] device[77e04291b4d185f3] (wlan0): wifi-scan: scanning requested but not allowed at this time
May 15 10:00:33 Reach NetworkManager[591]: [1715767233.2854] device[77e04291b4d185f3] (wlan0): wifi-scan: scheduled in 120 seconds (interval now 120 seconds)
May 15 10:01:02 Reach NetworkManager[591]: [1715767262.0996] device[77e04291b4d185f3] (wlan0): wifi-scan: scanning requested
May 15 10:01:02 Reach NetworkManager[591]: [1715767262.0999] device[77e04291b4d185f3] (wlan0): wifi-scan: no SSIDs to probe scan
May 15 10:01:02 Reach NetworkManager[591]: [1715767262.1013] device[77e04291b4d185f3] (wlan0): wifi-scan: scheduled in 120 seconds (interval now 120 seconds)
May 15 10:01:02 Reach NetworkManager[591]: [1715767262.1130] device[77e04291b4d185f3] (wlan0): wifi-scan: scanning-state: scanning
May 15 10:01:02 Reach NetworkManager[591]: [1715767262.9490] device[77e04291b4d185f3] (wlan0): wifi-scan: scanning-state: idle
May 15 10:01:03 Reach NetworkManager[591]: [1715767263.0681] device[77e04291b4d185f3] (wlan0): wifi-scan: scan-done callback: successful
if it’s got band steering running, see if they can disable it and see if that helps.
try changing the AP broadcast power for the 2.4G channels - I think the RS2 is on the edge of switching to another AP (or loosing connection). Tweaking the output power on the AP might persuade the RS2 to ignore other weaker signals and stay put. It could even be that a neighbouring AP needs it’s broadcast power turning down slightly in order to persuade the RS2 not to try & hop over.
I’ve asked our IT dept to look at the settings on the AP.
One thing occurred to me though. Why does the RS2 not automatically reconnect to the wifi network after losing its connection? Is it normal behaviour for it to ignore a wifi signal it can see and has credentials for?
The signal is definitely still there as after a reboot it finds it immediately, and while its connected it shows two or three bars.
It might be because the AP is negotiating with/trying to pass it over to another AP and neither AP ‘wins’. That’s why your IT dept might need to look at the power settings on the AP’s.
Is the RS set to only access one network too, or are there multiple networks available to it - that might also explain why it’s not rejoining if it can join another SSID/Network.
To investigate the issue, could you please send us the Full System Report? As it contains sensitive information, you can email it to us at support@emlid.com.
Also, I agree with @ElectroNick. Please make sure that the Wi-Fi is using the 2.4 GHz band. Reach doesn’t support the 5Ghz band.
Also, would it be possible to test it with another Wi-Fi network and check the connection? This is to rule out that it’s not this specific network that causes the disconnection. Thanks!
I want to inform you that we have been in contact with @ecw via email. The developers have checked the full system report. The Reach RS2 is working fine, and the issue is likely with the network (network configuration or being too far away from the RS2).
If anyone has the same issue, please feel free to create a new thread or email us at support@emlid.com. Thanks!
An update from me. Firstly, thank you to the Emlid support team for helping so quickly here and via email.
We haven’t been able to test the RS2 on a different AP, but we have set up a dedicated SSID on that AP which is only being used by the RS2. So far, that seems to have worked.
When our IT dept looked at the logs of connected devices on the network, they noticed that the RS2 was occasionally jumping onto another AP even though it had poor signal. Perhaps that was the cause of the loss of connection?
Now its got its own dedicated SSID to connect to hopefully it won’t jump onto another AP anymore.
When our IT dept looked at the logs of connected devices on the network, they noticed that the RS2 was occasionally jumping onto another AP even though it had a poor signal. Perhaps that was the cause of the loss of connection?
Based on the Full System Report, Reach was trying to connect to this network, but it seemed too far from the AP, and sometimes Reach couldn’t find this network, so it disconnected. When it happened, Reach started to look for the network.
Also, sometimes, it took too long to authenticate in the network, and the timeout was received.
If you encounter the same issue again, please feel free to email us at support@emlid.com. Thanks!
