Reach Firmware 26 Update: Legacy RTCM3 Messages and NMEA Output Settings

We are excited to release the Reach Firmware 26 update. From today, the release is available for all devices. We’ve enhanced stability, improved the user interface, and implemented some of the long-awaited features!

Legacy RTCM3 support to work with other RTK receivers

This update allows connecting Reach RS2 as a base station with traditional third-party receivers and agricultural equipment. You now have this option with RTCM3 legacy messages 1004, 1008, 1012, 1033 for multi-band devices.

RTCM3 legacy messages in a Base mode in ReachView 3

To set up various RTCM messages, go to the “Base mode” in the ReachView 3 app, choose your type of legacy messages and the required rate.

NMEA output configuration: talker ID and messages set

With this release, we have also added configurable NMEA position output in Reach Panel. You can choose a Talker ID and the desired set of NMEA messages.

To access Reach Panel from the ReachView 3 app, go to the “Receivers” screen, tap the receiver’s name and choose “Reach Panel”. The app will navigate you to the Reach Panel.

Access to Reach Panel from ReachView 3

In the Reach Panel, open the “Position Output” tab, select the NMEA format, and then set up a Talker ID, the required messages, and their frequency. Keep in mind that the NMEA output rate should be equal to or lower than the RTK Settings rate.

NMEA output configuration in Reach Panel

Specifying the talker ID and the message parameters helps you connect Reach rovers to various GIS apps, software for GPR, and agriculture machinery guidance. This means that you can freely use Reach with software and hardware requiring a specific NMEA output.

To better match the current RTCM3 message configuration, the LoRa air data rate for RS2 is automatically updated with this release. If you have custom settings for the LoRa air data rate, please check them after the update. To avoid different LoRa air data rates for the base and rover, we recommend updating all your devices.

Seamless compatibility with PPP services and more

Another functional improvement is the additional fields in RINEX files for Reach RS2. Now, RINEX logs contain “Antenna” and “Receiver” header fields so that you can import the raw files into PPP services without any changes.

We have also added configurable RINEX logging in ReachView 3, which allows you to filter out some satellite systems (e.g., record GPS only while in GNSS all systems are enabled), log RINEX at a lower rate than the GNSS rate, and enter the antenna height.

One more handy feature is logging autostart. It lets you log in automatically after rebooting or turning on the device.

Raw data settings

What’s more, this release uses the new naming and versioning schemes to differentiate it from the ReachView 3 app. Previously, we used to call firmware updates ReachView v2.24, ReachView v2.25, etc. From now on, stable firmware updates will be called Reach Firmware 26, Reach Firmware 27, etc. Forthcoming features will be available in Beta versions (previously known as “dev”) called Reach Firmware 26 Beta 1, Reach Firmware 26 Beta 2, etc.

Check out the complete list of fixes and improvements:


  • Improve LoRa stability on RS/RS+ and for the external LoRa module
  • Reduce charge current in case of overheat on Reach RS2
  • Enable the searching LED indication even in the night mode
  • Send to NTRIP caster meta-information when running a Correction Output as an NTRIP Server
  • Change default RINEX logs name with device name and updated extensions for RINEX logs to conform standards RINEX < 3.02
  • Improve RTK performance in case of changing the correction input source on multi-band receivers (Reach M2, Reach RS2)
  • Send position output even before SINGLE status
  • Improve Wi-Fi stability when the receiver is turned on
  • New Updater interface
  • Remove output power slider for LoRa at Correction Input tab
  • Support 4800 baud rate for serial output on RS/RS+/RS2 devices
  • New Full System Report name
    • Full System Report filenames now have different names to help you distinguish one from another. The pattern is as follows: <Reach Name>_<Device type>_<Date>
  • Add new About block with S/N of the device on the Settings Tab
  • All log files generated on the receivers from Logging tab follow the same naming pattern: <Reach_Name>-<Log_Type>*<Log_Date>*<…>.<Log_Extension>
  • Update LoRa frequency constraints for Philippines
  • Various stability improvements

The interface of the logging tab has been significantly updated:

Logging settings are moved from the Settings tab under the gear on the Logging tab


  • Fix rare issues with time synchronization
  • Fix some errors with cellular connectivity on Reach RS2
  • Update behavior of the bottom connector
    • Add a deadband 10s to shutdown on wall unplug feature
    • Device can turn on via the external 9-pin bottom connector even if the battery is discharged
  • Optimize charging algorithm on RS2
  • Fix reversed camera trigger polarity for Reach Module/M+/M2
  • Reduce the rate of NMEA GGA that is sent to the VRS
  • Fix rare case of sudden RTK Setting reset to the default values
  • Fix false SBAS cycle slips during RTCM3 1107 to RINEX conversion (single-band devices)
  • Incorrect status of stream on Correction input and Position output tabs
  • Some cases when RS2 can stuck in loading
  • Display of outdated base satellites data when the connection with Correction Input source is lost
  • The output of null LLH/XYZ/ENU solutions, now only NMEA and ERB solutions are output before SINGLE status
  • Missing GLONASS carrier phase information in RINEX logs collected from a base
  • Compressing big log files (over 2GB)
  • Fix rare cases with position output from two sources
  • Fix an issue that in rare circumstances would lead RS+/RS2 to a reboot instead of it being shut down
  • Fix rare issues with RINEX log disappearing
  • Fix disappearing RTCM3 messages counter when corrections are coming
  • Fix PDOP display for SINGLE solutions on single-band devices
  • Do not show the baseline when no solution
  • Misleading checkbox select in the Privacy Policy agreement modal on opening the privacy policy link

Great news, can’t wait to install this on my units. I have a special request for the RINEX settings. I love that you added the antenna height option, but I would like to have an option to specify the antenna I use with my M2. It’s obviously automatic with the RS2, but not with the M2 since I can attach any antenna.

Thank you


I second that request! Having a field in the app to enter the antenna code would be welcome.


Hi there,

We’ll note your request. Thanks for that!

Thank you so much for Talker Codes selection, and NMEA selection. No outside conversion needed anymore just the M2 and a ttl / 232 converter very easy to setup.

Taking it for a spin on the Tractor Harrowing tomorrow very excited, spring is here again.


Spring has sprung here. Some farmers have started “early” planting. I think we are 1 to 2 weeks out before everyone starts planting.

Farm drainage work is in full swing before the planting begins so I am BUSY. I haven’t had a chance to test the 2nd Beta release. I want to test the talker as well.

After updating to Firmware 26, using ReachView 3, anyone else having Bluetooth connection issues with a Trimble Nomad 6G handheld data collector? Worked fine before the update.

In ReachView, the MAC address shows, and shows a very quick connect during pairing… and the Nomad says it connected during so… but after that, the Nomad will not connect again.

Works fine with my (2) Surface PCS and a desktop workstation.

Could be very well something of my own, but figured I’d ask just in case as I have exhausted every option that I have control over.

EDIT: after some more searching, found this:

I did not have BT enabled in the Position Output. I had mistaken disabled it.

It now connects while in FieldGenius9. But for some odd reason, in the Windows 6.1 OS on the handheld, it shows BT is disconnected, yet its connected during FieldGenius use. Seems it used to state connected either way before. At least it’s staying connected now… took forever to figure out.

NMEA and Talker code selection is working great :grinning: :smile: :grin: :blush:
The Trimble Ez Guide 150 has never steered better, threw out the WAAS antenna this morning!

But iPhone hot spot gremlins are back :cry:

The M2 was very militant about making its own hot spot no matter what, and would not lock onto the iPhone’s hot spot by itself.

I had to log onto the M2’s hots pot with my iPhone, then transfer to my Friends iPhone Hotspot.

Is there a way to have a software switch to make the Reach prefer a external wifi hotspot, vs starting its own immediately by adding a substantial delay. This would make it easier to latch onto an external wifi hot spot, while still making it able to start its own hot spot much later for recovery without having to re flash it?


What is this NMEA Talker ID (GN GP?) and Messages “simply” please?

“GP” talker code signifies the message was generated by a gps receiver

“GN” signifies it was a GNSS receiver

Then there are multiple sentence structures that contain different measured data. Like “gga” or “vtg” there are many of these sentences that contain different data.

Velocity and direction of a gps unit would start with “gpvtg” in ascii.

NMEA was developed for maritime use of all instruments on a ship sharing data over the same data bus.

GPS uses only a small amount of the sentence structures laid out in the NMEA communication standard.

Most older and some newer commercial equipment uses the GP code

Modern equipment may use the GN code


Please can you send me the link for reach firmware 26 update I only have the image of it.
I’m using RS+.

1 Like

Hi, i have updated my to Reach RS2 units to firmware 26, but when i tried to Measured height in Raw data settings, it does not allow to put height like 1.34, just whole numbers like 1. Anyone experienced the same issue?

Try “,” (without quotes) instead of “.” (without quotes).

It does not allow me, i am using samsung s10, nut i am going to try with windows now.

Try with Google Keyboard.

1 Like

And another issue, i have troubles finding Reach RS2 as bluetooth with a windows mobile device, and carlson surv ce, even thought i have checked on ReachView that bluetooth is on and discoverable.

Sorry, after a couple of restarts of both devices, finally windows mobile found reach rs2’s bluetooth.

Past posts, I think had something to do with region settings in the phone itself? Been awhile.

I think agrimgalina had a post on this a couple years back?

2 posts were split to a new topic: Reach Module RINEX header

The solution is to download a Gboard google keyboard, thanks to @polina.buriak