The Reach Firmware 33 introduces new features and improvements to refine Reach RS3 compatibility over UHF and allows you to stream corrections from your Reach base using two output channels at the same time. This update is available for Reach RS3, RS2/RS2+, RS+, M2, and M+ devices.
Reworked UHF compatibility for Reach RS3
This release improves the Reach RS3’s compatibility with third-party base stations via UHF radio, helping you maintain consistent RTK performance in the field. The corrections reception system has been reworked to provide greater stability when receiving corrections via the TRIMTALK 450S* protocol. This helps to reduce interruptions and maintain a reliable connection in challenging environments.
Dual-channel corrections output for Reach bases
The new firmware adds the ability to send base corrections from Reach receivers via two channels simultaneously. This gives you greater flexibility in complex or dynamic field setups. For example, you can broadcast corrections over both LoRa and NTRIP simultaneously to support a drone flight while collecting GCPs on the ground. The dual-channel output also allows you to simply switch between channels when your rover moves out of range or loses network access.
To enable a second base corrections output, go to the Settings menu in Emlid Flow and select the desired output channel.
With NTRIP, Serial, and TCP server, you can also use a single channel to output two correction streams. When using the same correction channel, be sure to configure two simultaneous outputs carefully to avoid conflicts:
| Channel | Using the same channel for dual output |
|---|---|
| LoRa | No |
| NTRIP | Make sure to use different credentials. |
| Serial | Make sure to use different ports. |
| TCP client/server | Make sure to use different ports. |
| Local NTRIP | No |
| Bluetooth | No. You also can’t use it if the receiver is already streaming its position. |
Learn more in our documentation.
Other improvements
- Updated GNSS chip firmware for multi-band devices to improve the quality of the position calculation. As a result, the 10 Hz RTK update rate is now available only when the BeiDou system is disabled.
- Improved Bluetooth connection management. Reach receivers now support only one active Bluetooth connection at a time, either Bluetooth Classic or BLE.
- Enhanced mobile connection configuration to speed up the connection.
- Improved Reach antenna registry to enhance compatibility when using Reach as a rover with third-party bases.
- Added signal strength indicators in Reach Panel: for LoRa on Reach RS2/RS2+ and for both LoRa and UHF on Reach RS3.
- Updated LoRa radio settings to comply with Japan’s local regulations.
What’s fixed
- Raw debug logging option. Now, when enabled, the UBX debug log is recorded regardless of the other logging settings.
- Tilt compensation stability for Reach RS3 devices.
- Cases where only the LLH log was recorded.
- Cases where it was impossible to connect to Reach RS+.
- Cases where Reach is not visible in the Emlid Flow scanner.
- Rollback from beta to stable version.
- Display device type in the RINEX log header.
Update your Reach Firmware and share your feedback—we’d love to hear how it works for you!
*TRIMTALK is a trademark of Trimble Inc.