We found a Bug in the Emlid Reach modules (2017 generation). The Emlid Reach modules do not work properly when RF connection is used to achieve RTK. This is, the Emlid Reach modules works properly doing RTK via WiFi but when serial (UART) RF modules are used, the input corrections are not received (on any of the transmission rate options).
However, we were able to make it work by doing a hack using the Realview3 App (as shown in the video: https://youtu.be/oXcV-mvmgtU).
The hack consists of the following steps:
In the Emlid Reach base module:
Select the transmission rate 115200 bauds on Base mode for the corrections.
In the Emlid Reach rover module:
Activate base mode and select the transmission rate 115200 bauds on Base mode for the corrections.
Disable the input corrections
Activate the input corrections
Disable Base mode.
The hack works only with the transmission rate 115200 bauds. If for some reason it doesn’t, the rover module must be restarted and redo the hack rover steps again.
The issue must be related to the firmware code related to base mode. We are using the latest firmware.
We tested this behaviour with RF modules: a pair of HC-12 and a pair of HKPilot ht03.
We thoroughly tested the last Reach Module firmware to ensure all the functionality, including Correction input and output, works smoothly. I don’t remember any similar reports from the 28.4 firmware as well. Just to check I got it right, do your receivers work on 28.4?
To clarify, somehow firmware does not work properly using RF connectivity. We don’t understand why we were able to make it work (not directly only with the mentioned hack) in transmission rate 115200 bauds and not any other?
Btw, when we are listening from a PC through a serial terminal. connected at transmission rate 115200 bauds, and the start the Emlid Reach module, we are able see a prompt terminal for login to the Emlid Reach. Could it this be related with the issue somehow?
We don’t understand why we were able to make it work (not directly only with the mentioned hack) in transmission rate 115200 bauds and not any other?
The baud rate depends on the particular radio configuration. It seems that it’s 115200 for your radios.
Btw, when we are listening from a PC through a serial terminal. connected at transmission rate 115200 bauds, and the start the Emlid Reach module, we are able see a prompt terminal for login to the Emlid Reach. Could it this be related with the issue somehow?
This output is not related to the radio connection. So, it doesn’t say much about what could go wrong in this setup.
From what we see in our tests and other users’ experience, the correction input and output work smoothly on the 28.4 firmware. It’s the last version for Edison-based devices, and it was tested thoroughly. But radios and their configurations differ. So, the issue is likely related to the particular radio. We can hardly say what exactly can be wrong from the side of a 3rd-party device, but you can check if these radios work in other setups or try other radios with your Reach devices. It should help localize the issue.
The other option is that the issue lies on the receivers’ side. The old Reach Modules have no protection, so with time, something could go wrong with the units’ hardware. In turn, it could lead to issues with correction output or input on the specific receivers. If it’s the case, it’s hard to determine the root remotely without examining the units. Still, you can connect the receivers to Wi-Fi and work via the Emlid NTRIP Caster as a workaround.
