Reach Firmware 29 update is rolling out today for Reach RS2, Reach RS+, and Reach M2/M+ devices. This latest update delivers enhanced RINEX logging and NTRIP protocols support, as well as general stability improvements for the overall user experience with Reach.
With the new update, we have added point markers into RINEX logs in ReachView 3. Now, if you collect points with RINEX logging enabled, the app records the collection events’ start and end times directly into the RINEX log for further post-processing in third-party PPK software. We have also included the approximate position in RINEX start/stop events. These improvements will help you seamlessly use the raw data from Reach for post-processing in your PPK software.
In RINEX NAV logs, we have added leap seconds output. What’s more, we have enhanced the RINEX logs’ compatibility for the OPUS preset.
One more improvement comes in the RINEX logging settings. You can now select SBAS (Satellite-based Augmentation System) in the satellite systems, which gives you additional data.
SBAS selection in logging settings
For NTRIP users, the latest update supports encrypted protocols over TLS/SSL required by some NTRIP casters. This means all AUSCORS mount points are now fully available in the ReachView 3 app.
AUSCORS mount points in ReachView 3
Furthermore, we have added support for the NTRIP V2.0 protocol. This feature allows connecting Reach receivers to Autel RTK drones using the NTRIP Local option in ReachView 3.
As usual, the new firmware version improves the overall stability and simplifies the user experience with Reach devices. Among other things, we have delivered the following improvements:
- Changed device naming restriction: the underscore character
_is forbidden to follow the standards of the correct device’s hostname in the network. If your devices’ names have underscores, they will be automatically renamed to the title without underscores (e.g., RS2_Base → RS2Base).
- Added the 14 Hz rate selector for the NMEA position output on single-band receivers.
- Improved battery charge estimation on Reach RS2.
- Increased stability when working over external LoRa on Reach M2.
Here is the complete list of changes we’ve implemented in this release.
- SBAS selection added to the RINEX logging settings
- Point markers added to the RINEX log when collecting data with ReachView 3
- Approximate position added to RINEX Events
- Leap seconds output added in RINEX NAV logs
- RINEX logs quality improved for the OPUS preset
- NTRIP V2.0 added to the NTRIP local caster option
- Encrypted protocols over TLS/SSL supported for some NTRIP casters
- Restriction added for device naming: the underscore character
- 14 Hz rate selector for the NMEA position output added on single-band receivers
- Battery charge estimation improved on Reach RS2
- Stability improved when working over an external LoRa module on Reach M2
- Epoch seconds overflow in RINEX
- NMEA timestamps for midnight
- Cases of the raw log being suddenly restarted
- Issues with unavailable log files
- Raw data debug setting for logging
- Stop recording logs if rolling logs is disabled and no space is left
- Solution logs file extension being always LLH
- Cases of the LoRa frequency settings not applied due to regulatory restrictions
- Getting NTRIP mount points for some casters
- Issues when it’s impossible to update base mode RTCM3 settings with NTRIP selected as base mode output
- Cases of the receiver stucking in loading
- Cases when devices with the same names are not visible in ReachView 3
- Representation of the current GSM modem mode for Reach RS2 receivers
- Alignment of the Base corrections label on the Logging tab
- Hint placement about RINEX header for Reach RS2 in the raw log settings
- Faded Updates section on repeatedly opened Updates panel
- Wrong Bluetooth device name representation
- Typo in the name of the sdun column in *.POS file