I have one of the older RS2 models (ie. it does not do 4G) and I am attempting to update to 32.2 from the 31.6 firmware. I connect to my hotspot, it downloads, it does the whole flashing light bit, and when I reconnect and check the version…it still says 31.6 as the current version. I would like to test out the new Beta (ie. for the dual transmit), but am unable to. I have connected to my second phone as the hotspot to avoid the issues some people have getting their internet from the same device running Flow. I typically do the following:
-start up a personal hotspot on my iPhone 14
-connect my Pixel 7 to that hotspot
-create a hotspot on my Pixel 7
-connect my RS2 to the Pixel 7 hotspot
-open Flow and connect to the RS2 via Bluetooth
-send NTRIP corrections via Bluetooth
This has always given me the best compatibility when using Flow.
Side note–when using SurvPC, the set up is similar (ie. the RS2 connects to my Pixel 7 hotspot, the DC has its own sim, I connect to the RS2 via Bluetooth with a NMEA profile, and the DC passes NTRIP corrections to the RS2 using its own internet).
iPhone 14 hotspot, Flow on Pixel 7, laptop to Reach Panel
-told it to update via the Reach Panel; downloaded the update, said it was updating, took quite long and I got worried it was borked, opened a new windows, reconnected, and downloaded the logs. Link to logs from this time period available here: Survey
Upon reconnecting via Bluetooth, the update had not worked or it will say “Couldn’t load current settings.” Could not connect via IP. Note that Bluetooth LED on RS2 was not lit up. I could make it flash when clicking on the Receiver.
Pixel 7 hotspot, Flow on iPhone 14, laptop to Reach Panel
-told it to update to the Beta as it seemed to allow that option if I clicked it on.
Could connect via Bluetooth. LED now lights up. Would say “Couldn’t load current settings” when clicking Settings. Would often get a “502 Bad Gateway” when trying to connect to the Reach Panel. Could not get it to flash when clicking on the Receiver. Could only connect via Bluetooth (ie. not via IP).
Power cycled.
Can now see Bluetooth and IP Receivers.
Bluetooth was extremely fussy. Most of the connection problems seem to be less frequent if I used IP connection only. This is somewhat funny to be as I used to use the RS2 with a Carlson Surveyor+ over Bluetooth and Windows Mobile is not exactly the most forgiving when it comes to Bluetooth or Wifi in my experience. I could connect to both the Geodnet and Can-net RTN’s and get fix. I was pretty happy with this.
Set up my M2 in my Mettatec case. Turned off the RS2. My goal has always been to use this as a Lora/PPK base for drone mapping. Updated to 28 something using the Flow app. Rebooted. It asked to update to the new Beta. Double-checked the forum and it said it was supported. Updated. Now, in Flow, I can see the RS2 but keep getting the “Couldn’t load current settings” message. Boot time is around 5 minutes.
In short, I now have the following issues:
The base (ie. M2) does not appear in Flow. I cannot connect via IP or Bluetooth to it. When scanning Bluetooth on my IPhone or Pixel, it does not appear. I can sometimes see its Wifi when I power cycle it, but it asks for a password that I do not seem to know.
I can see the rover (ie. RS2) in Flow. I cannot connect to it via IP. I can connect to it via Bluetooth, but I cannot change any of the settings. Hotspot off of Pixel 7 does not have a password as I am trying to minimize factors affecting the setup. It still takes about 5 minutes to boot up.
Any ideas? Is there a way to do a full factory reset of both? I was really hoping to get things set up with a base that transmit UHF and caster, but at this point I would just be happy with a base/rover setup that did one or the other. Right now, they are “dead in the water.”
Did you try updating both units (M2 connected to antenna) outside or at least through nearby window within wifi range??? You may have to REFLASH manually via USB cable and PC.
Correct. Both were updated on a pole outside with clear rural sky. M2 was connected to the antenna in the Mettatec base station kit. I always, at least, have them by the window when they are turned on. The M2 LED shows green when I currently attempt to connect.
The RS2 was always a bit fiddly for me, but most survey equipment seems to have certain “quirks.” It worked fine as a network rover; I was just trying to come up with a solution for implementing our drone work and Emlid’s stuff seems perfect for it.
I have not tried yet, but can try to produce the logs if it will help Emlid diagnose.
Thanks for the detailed breakdown of your steps. It really helped, as it seems like you’ve tried every possible setup, and surely the units shouldn’t behave this way.
Afterward, try reflashing your Reach receivers. This updates/rolls back your devices to the latest stable version, 32.2. Just a heads up—this resets your device to its original state and erases all saved logs. We have a step-by-step guide you can check out.
I can sometimes see its Wifi when I power cycle it, but it asks for a password that I do not seem to know.
This means the M2 is in hotspot mode, indicated by a static blue LED light.
You can connect to it by entering the default password, which is emlidreach.
