Reach RS+ Version Update 2.21.1

I decided to update my system from 2.15.5 to 2.21.1 today. I have done updates for versions previously and have not had any issues. Today, my rover’s STAT light never turned green indicating a successful update and my app never restarted. It had the screen that tells me that the version software is updating. After 3 hours of continuous wifi connection with no results to say that the version has successfully updated, I decided to try to reboot the rover myself. Now, I am stuck. My rover will only power on (only orange PWR light on). No NET or STAT lights. I have no connection with my phone app. What happened?? Can anyone direct me how to get this rover running again on the latest or previous version??

Matt

Reflash unit. https://docs.emlid.com/reachrs/common/reachview/firmware-reflashing/

1 Like

Hi Matt,

Did the reflashing help to resolve the issue?

I try to reflashing buy not successful. I try to do many time

After that i try to update flashing tool but can not success too

Now problem with startup it can not work just blink LED

Have you also tried the firmware update mode on the unit?

2 Likes

yes, How to fix it?

Hi @Huot_Samnang,

May I ask you to share the flasher logs? To access flasher logs, you can follow these steps:

  1. Press Win + R
  2. The Run window should appear
  3. Paste this string into the Run window: AppData\Local\Emlid\Reach Firmware Flash Tool\logs

It should open the folder with flasher logs. Please zip them and post here.

1 Like

I can not find where i can post file

22:14:45: default: info: Runtime environment:
os: “winnt”
os_version: “10.0.18362”
prod_type: “windows”
prod_version: “10”
qt_version: 5.12.3
qt_build: “i386-little_endian-ilp32”
app_name: “Reach Firmware Flash Tool”
app_version: “v1.1.1-reach”
app_logs_path: “C:/Users/Huot Samnang/AppData/Local/Emlid/Reach Firmware Flash Tool”
app_settings_path: “\HKEY_CURRENT_USER\Software\Emlid\Reach Firmware Flash Tool”
app_executable: “C:/Program Files (x86)/Reach Firmware Flash Tool/Reach Firmware Flash Tool.exe”
app_library_paths: (“C:/Program Files (x86)/Reach Firmware Flash Tool”)
app_args: (“C:\Program Files (x86)\Reach Firmware Flash Tool\Reach Firmware Flash Tool.exe”)
22:17:34: FlashingManager: info: “Starting new FlashingManager with [device: ReachRSplus; action: Flashing and Testing; image: C:/Users/Huot Samnang/AppData/Local/Temp/Reach Firmware Flash Tool/reach-plus-v2.16.0/reach-plus-v2.16.0.img]”
22:17:34: FlashingResultValidator: warn: “Couldn’t find flashing_result.json”
22:17:34: servicemanager: info: “Service DeviceWatcher is starting…”
22:17:35: servicemanager: info: “Service DeviceWatcher is running…”
22:17:35: servicemanager: info: Service: “DeviceWatcher” has started. Channel: “localhost:55675” Executable: “C:/Program Files (x86)/Reach Firmware Flash Tool/watch_controller.exe”
22:17:35: DeviceWatcherClient: info: " [Channel localhost:55675; State: Starting] " | “”
22:17:36: DeviceWatcherClient: info: " [Channel localhost:55675; State: Running] " | “”
22:17:37: DeviceWatcherClient: info: Requesting device watching…
22:17:37: DeviceWatcherClient: warn: " [Channel localhost:55675; State: Errored] " | “Device watcher crashed” | “GRPC error - Received RST_STREAM with error code 2”
22:22:53: servicemanager: info: “Service DeviceWatcher unexpectedly crashed”

22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Watch controller logging activated
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Cli arguments: Namespace(listen=‘localhost:55675’, logconfig=‘C:\Program Files (x86)\Reach Firmware Flash Tool/logconf.json’, logfile=‘C:/Users/Huot Samnang/AppData/Local/Emlid/Reach Firmware Flash Tool/logs/01.11.2019_22-14-45/watch_controller.log’, parent=1760)
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Unknown cli arguments: []
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Construct WatchController
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Start grpc server
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Create process representer for parent(1760)
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Wait for terminating_event or parents’ death…
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - gRPC Start() called
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Creating watcher…
22:17:35 - services_factory.py - IP:localhost:55675 - Port:not set - INFO - OneShotNeutisWatcher created
22:17:35 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Starting server…
22:17:35 - grpc_service.py - IP:localhost:55675 - Port:not set - INFO - Check (‘127.0.0.1’, 50357) socket
22:17:35 - grpc_service.py - IP:localhost:55675 - Port:not set - INFO - Socket was picked
22:17:35 - grpc_service.py - IP:localhost:55675 - Port:not set - INFO - New channel state: ChannelConnectivity.IDLE
22:17:35 - grpc_service.py - IP:localhost:55675 - Port:not set - INFO - New channel state: ChannelConnectivity.READY
22:17:36 - grpc_service.py - IP:localhost:55675 - Port:not set - INFO - udp socket was closed
22:17:36 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Server has been started
22:17:36 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Work mode: flash
22:17:36 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Initialize Watcher
22:17:36 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Watcher has been initialized
22:17:36 - grpc_service.py - IP:localhost:55675 - Port:not set - INFO - New channel state: ChannelConnectivity.IDLE
22:17:37 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - The number of plugged devices has been changed to 0
22:17:37 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - gRPC Watch() called
22:17:37 - watch_controller.py - IP:localhost:55675 - Port:not set - INFO - Begin watching
22:17:39 - watch_controller.py - IP:localhost:55675 - Port:not set - ERROR - Catched RpcError: <_Rendezvous of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = “Connect Failed”
debug_error_string = “{“created”:”@1572621459.115000000",“description”:“Failed to create subchannel”,“file”:“src/core/ext/filters/client_channel/client_channel.cc”,“file_line”:2608,“referenced_errors”:[{“created”:"@1572621459.115000000",“description”:“Pick Cancelled”,“file”:“src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc”,“file_line”:234,“referenced_errors”:[{“created”:"@1572621459.114000000",“description”:“Connect Failed”,“file”:“src/core/ext/filters/client_channel/subchannel.cc”,“file_line”:663,“grpc_status”:14,“referenced_errors”:[{“created”:"@1572621459.114000000",“description”:“OS Error”,“file”:“src/core/lib/iomgr/tcp_client_windows.cc”,“file_line”:106,“os_error”:“No connection could be made because the target machine actively refused it.\r\n”,“syscall”:“ConnectEx”,“wsa_error”:10061}]}]}]}"

@Huot_Samnang
Try to download a file “1.1.3reach.7z” manually
https://files.emlid.com/flash-tools/repo/public/win/reach/full/1.1.3reach.7z
and put it to “Reach Firmware Flash Tool” Directory
Located at:
C:/Users/Huot Samnang/AppData/Local/Emlid/
and reflash.

Thank still problem. Now i found that because of USB. Some USB can not work properly with Emlid USB. I don’t know why, because i can reflash Emlid with my old PC but i can not reflash with my new PC

Happy for you thanks for the info.

1 Like

Hi @Huot_Samnang,

Do I understand correctly that you managed to reflash the unit? Did it solve the issue with the rover?

Yes sure I try to reflash the unit because my Emlid Reach RS+ have problem after i update to version 2.21. Now i already reflash to stable version 2.18.1