New Reach Firmware 30 improves Reach compatibility with other receivers and software

Hi Arnaud,

Thanks for your patience.

I’ve checked the settings and if you select any type of Authentication except Not provided, you need to enter the necessary credentials. These fields cannot be left blank. We haven’t changed this mechanism so it works the same way on the previous firmware.

Does your network carrier require PAP authentication with no username and password? Does the mobile data work if you select Authentication typeNot provided and enter the APN?

The APN config is automatically set ( via SIM ).

Also when crossing border the device is very slow to switch network, it’s a real pain. The roaming should be quick.

There is an issue after this update. The network, blue LED is not blinking while connected to Wi-Fi. It is switched off. Turning on hot-spot turns the LED on (solid) and then switching back to Wi-Fi makes the LED blinking. Then after reboot, the problem appears again.

Hi, after upgrading from beta, reappear old bug with wi-fi disable option.
Sometimes after disabling wi-fi and power cycle reach m+, wi-fi starts as wanted but at www there is still enable wi-fi switch, and it’s impossible to disable wi-fi again without next power restart.


I try to update from 30 beta 3 to the stable 30, it does all the procedure, but after rebooting the firmware is still beta 3.

Hello everyone!

Today we’ve released a new Reach Firmware 30.1.


  • Fixed some cases when the base didn’t emit corrections after booting the device
  • Returned the IBGE logging preset for single-band devices
  • Fixed some cases when LoRa didn’t receive corrections after booting the device
  • Fixed missing UBX logs when raw data debug is enabled
  • Fixed indication for the network LED on the Reach RS+ devices

Hi Arnaud,

Does it work if you use only APN settings without choosing a particular authentication type?

This can happen because the cell towers aren’t distributed close to the particular location. Some cell tower transmitters are set to low power on purpose. It can induce some delays in finding the available network connection during the location change.

Hi Łukasz,

Thanks for reporting!

There indeed was a bug that affected the blue LED behavior. But we’ve just released the fix for it in Reach Firmware 30.1. Please update your device to this version to check whether it helps.

1 Like

Hi @rccam,

Do you mean the Turn Wi-Fi off to save the battery power functionality? It disables Wi-Fi only for the current session and enables Wi-Fi back after the next reboot. If you mean something else, can you please elaborate a bit more on the issue? It’ll help me to find a solution for you.

Hi Kostas,

Thanks for reporting!

Is it possible for you to try updating the device via another Wi-Fi network to check whether it changes anything? If this doesn’t help, please send the Full system report from the device to I’ll check what went wrong here.

Don’t know, I only use auto.

My phone and other devices change faster much faster.

Yes, when I write wi-fi disable option - I mean “Turn Wi-Fi off to save the battery power functionality” As I write wi-fi starts normally as wanted on every boot.
But there is problem with missing switch/options to disable wi-fi and etc. For clarification: there is situation when after reboot reach wi-fi is working as hot-spot but there is only enable wifi switch/option at www (and that switch doesn’t do anything). So I’m unable to switch off reach hotspot, or connect to another external wi-fi. That’s old bug, that been previosly cleared but now reappears.

edit: I checked on 30.1 fw and same that on 30.0
Also if reach is connected to external wi-fi and I use disable wi-fi option, after first reach power restart and wi-fi auto reconnect there is same bug and only visible option at is enable wi-fi.

Hi @rccam,

Could you probably elaborate on it a bit further by providing some screenshots or a screencast for illustration? You may share it with me by sending it to I’ll take your email and we’ll check with the devs on what’s not working fine.

We are having an issue with our RS2’s (6 total) not showing any connection or data in the Status overview window and also the Corrections portion. The RS2 still beeps like it is fixed or lost fixed. But there is no data stream for satellites or NTRIP. There was no issue last week when using the RS2’s, but today this has came up.

Ok so after a few hours of panic and headache, I have figured out that it is only the Bluetooth that is affected for us. If I switch to WiFi I can get corrections and satellite data.

Added info:
I have now flashed one of my units with 30.1 and it seems to function fine. It is odd to me that 4 out of or 6 units I could test had the same issue, all Bluetooth. Also did this update change the need to connect via setting in an iPhone? the units do not show up in my setting WiFi or Bluetooth, but show up in the Emlid Flow app.

Do they also work well over Bluetooth? Which version did you have before?

I think that this is just because all your devices are on the same Wi-Fi network.

1 Like

Yes they work over Bluetooth, which is the main thing we use. I upgraded all 6 units to 30.1 on March 7, 2023.

Update: I have just flashed a second unit that is now working fine with Bluetooth and WiFi.


There is some screenshot’s. I also send e-mail with video record
Apparently on fourth screenshot there is unproper Enable Wi-fi option, that also does nothing.
Instead like in screenshot fourth available options should be like in first screenshot after every reboot.

Between these I do proper reboot/power restart

1 Like

Thank you! I also received the videos, which were very helpful! I was able to reproduce the same behavior. I’ll look into it with the developers and get back to you with updates.

Did we loose the ability to check the rover/base location on the OSM map through the browser interface at for example?
It was quite convenient to do a quick check on rovers connected to machines remotely.

1 Like