Understanding Message Types in RTK: RTCM, CMR, and Why It All Matters 

A thumbnail for an article on message types in RTK.

In the world of precision positioning, Real-Time Kinematic (RTK) technology has become indispensable for professionals in surveying, agriculture, construction, and geospatial fields. RTK offers centimeter-level accuracy by using correction data transmitted from a base station to a rover. But for this system to work, both sides must speak the same “language.” This is where message types—like RTCM and CMR—come into play.

In this article, we’ll break down what these message types are, how they work, why they matter, and why it’s essential to keep up with the latest standards if you want reliable, accurate, and future-proof RTK performance.

YouTube video

What Are RTK Message Types?

A Quick History of RTK Message Types

Comparing RTCM and CMR

Why Do RTK Message Types Matter?

Why You Should Use the Latest RTCM Version

Practical Advice for Survey Businesses

Final Thoughts

FAQs

What Are RTK Message Types?

Think of RTK message types like file formats or spoken languages. If one device speaks English and the other only understands French, communication breaks down. In RTK, this “language” is the format in which correction data is transmitted from the base station to the rover.

RTK correction messages carry data such as satellite positions, pseudorange measurements, phase observations, and satellite health status. These are critical to enable the rover to refine its own satellite data and achieve centimeter-level positioning.

The format or protocol in which this correction data is packaged is referred to as a message type. If the base and rover support different message types, they won’t be able to interpret each other’s signals.

Sokkia GRx2 and the Hemisphere S631 can work together even though they are different manufacturers and of different eras.
As long as two units have a common message type they will be able to communicate. The Hemisphere S631 and Sokkia GRX2 are able to communicate with a common RTCM message type, despite an almost 10 year difference between the two units. 

A Quick History of RTK Message Types

The Early Days: Proprietary Protocols

When GPS technology became commercially viable in the 1980s and early 1990s, manufacturers like Trimble, Leica, and John Deere each created their own proprietary message formats. This was great for internal product ecosystems but terrible for interoperability. If your rover was made by one company, it wouldn’t work with a base station from another, or work as a rover with a different base station.This fragmentation limited flexibility and increased costs, forcing businesses to stay within a single brand’s ecosystem.

Timeline of constellation and message type release.
As more GNSS constellations have come online message types have had to be updated to include the relevant information. Many of the Trimble message types are updated over time, with CMR+ gaining the ability to transmit GLONASS corrections later into its life. 

Trimble’s CMR: The First Semi-Universal Format

In the 1990s, Trimble introduced CMR (Compact Measurement Record), which helped pave the way for better cross-compatibility. Due to the limitations of early radios for RTK equipment, a more compact and efficient message type was required. CMR was specifically designed to better package RTK corrections from the base to include more information than was previously possible.  This allowed RTK to really take a step forward in widespread use, with the more efficient message type able to transmit over limited-bandwidth connections like UHF radios or early cellular networks.

CMR allowed some interoperability within the Trimble ecosystem and even across brands in limited scenarios, but it was still controlled by a single company and lacked full transparency or open standardization.

RTCM: The Push for a Universal Standard

To address the fragmentation problem, the Radio Technical Commission for Maritime Services (RTCM) developed an open and standardized message format. The working group behind these formats, published its first GPS correction message specification in the 1980s. Over time, this format evolved to support more constellations, higher accuracy, and more flexibility.

Today, RTCM is the de facto standard for RTK correction messages and is widely supported across GNSS receivers from different manufacturers. It provides the interoperability that the industry desperately needed.

Rene from Bench Mark GNSS Equipment with a base and rover of Radian IS RTK equipment.
When first starting out Bench-Mark set out with the Sokkia Radian series of receivers. Due to the limited performance, RTCM was not initially a great option and required a proprietary message type to work properly. 

Comparing RTCM and CMR

Let’s break down the key differences between these two message formats.

FeatureRTCM MessageCMR Message
OwnershipOpen standard (RTCM)Proprietary (Trimble)
CompatibilityIndustry Standard Older Versions like CMR and CMR+ are widely available. The latest CMRx is only available on Trimble receivers. 
Constellation SupportAll Constellations and All Signals. CMR: GPS Only
CMR+: GPS and GLONASS
CMRx: All Constellations and All Signals. 

CMR and CMR+

Trimble’s CMR initially only supported the GPS constellation. It was after all the first GNSS system made available commercially, you can learn more about the history of GPS here: GPS In Surveying – From Weapon of War to Everyday Tool. As Glonass became commercially available, CMR was upgraded to CMR+, adding Glonass support. However, after the release of CMR+, Trimble has not continued providing the message type to other manufacturers. As a consequence, the full signal, full constellation CMRx is not available for use for anyone outside of the Trimble ecosystem. 

RTCM Versions

Over the years RTCM has continued to evolve as constellations and signals have been:

  • RTCM 1.x: Published as the first standard in 1985, but never widely adopted by industry.  
  • RTCM 2.x: First message that was used in RTK work, initially supporting GPS but upgraded to support GLONASS. Introduced in 1990, with CMR being developed to solve many of the problems with this message in work with RTK equipment.
  • RTCM 3.x: Introduced in 2004 to be more compact and work better with RTK equipment, it has been continually upgraded, adding support for Galileo and BeiDou in the newest versions. It is the recommended message type for most applications and hardware.

Why Do RTK Message Types Matter?

Interoperability

The biggest benefit of using an open standard like RTCM is interoperability. Whether you use a Trimble base station and a Leica rover—or mix in Emlid, Topcon, or other brands—RTCM allows them to work together, as long as they support the same RTCM version and message types.

Data Completeness and Accuracy

The message format determines what data gets transmitted. Older formats may omit information about additional GNSS constellations, limiting accuracy. For example, if you’re only receiving corrections containing GPS data, your accuracy and fix time, especially in difficult conditions, are significantly worse than if you’re using corrections containing GPS + GLONASS + Galileo + BeiDou.

Newer RTCM versions allow richer, more complete satellite data to be transmitted with fewer errors, even over constrained bandwidth.

Bandwidth Efficiency

Bandwidth is often limited in the field—especially when using radio links or older cellular connections. Modern RTCM messages are structured to reduce data size without sacrificing information. This efficiency translates into more stable connections and faster rover initialization.

CMR, while compact in its time, can’t match the efficiency and extensibility of RTCM 3.x and beyond. 

Future-Proofing

GNSS technology is evolving. New signals and constellations are coming online (like L5, Galileo E5, BeiDou B2a). You want your equipment and communication protocols to support them as they’re adopted. RTCM is actively maintained and updated by a standards body, who ensures that the signals give the best performance in all environments. With Trimble locking the latest CMR versions to their hardware, you are constrained to using Trimble software. 

A surveyor using the Hemisphere S631 in the woods.
New units like the Hemisphere S631 are capable of achieving repeatable and accurate solutions even in high multi-path environments. By leveraging all of the available signals on the newest RTCM corrections, it is able to do this. 

Why You Should Use the Latest RTCM Version

If you’re setting up an RTK system today, the latest RTCM version (currently RTCM 3.x or RTCM MSM) should be your go-to. Here’s why:

1. Supports All Major GNSS Constellations

RTCM 3.3 includes full support for:

This multi-constellation support drastically improves availability, redundancy, and positioning accuracy—especially in tough environments like urban canyons or under canopy.

2. Faster Initialization Times

More satellite data means the rover can resolve ambiguities and get a “fix” more quickly. For many professionals, time is money. A rover that fixes in seconds instead of minutes can transform productivity. Message type isn’t everything, but having access to the latest available signals gives your receiver the best chance of obtaining a fixed solution. 

YouTube video

3. Standardized, Extensible, and Open

RTCM is an open format, maintained by a global standards body. That means better support, more widespread adoption, and faster updates when new satellite capabilities are released. Contrast that with CMR, which is proprietary and updated at the pace of one company’s internal roadmap.

Practical Advice for Survey Businesses

If you’re running a survey business today, here’s what you need to keep in mind:

  • Use RTCM 3.3 if possible. It’s the most flexible and complete.
  • Ensure base and rover match in version and message support. A mismatch means no fix. Most modern 7thgeneration receivers have the ability to Auto-Detect the correction format.
  • Avoid locking yourself into proprietary formats like CMR unless there’s a compelling reason (e.g., legacy infrastructure).
  • Keep firmware updated. Manufacturers regularly improve RTCM handling and support.

Final Thoughts

RTK message types are more than technical details—they’re the backbone of accurate, efficient GNSS positioning. CMR played an important historical role, but today, RTCM is the standard that drives the modern industry.

If you’re serious about performance, compatibility, and future-proofing your gear, RTCM 3.3 is the way forward.

Make sure your base, rover, and software all speak the same “language”—and speak the latest dialect.

FAQs

What are RTK message types and why do they matter?

RTK message types are the formats used to transmit correction data from a base station to a rover in RTK GPS systems. They matter because both devices must use the same format to communicate effectively and achieve centimeter-level positioning accuracy.

What’s the difference between RTCM and CMR?

RTCM is an open, standardized format supported across most GNSS brands. CMR, developed by Trimble, is a proprietary format. RTCM supports all major satellite constellations and is widely compatible, while the newest CMR message types are limited to Trimble systems.

Why should I use the latest version of RTCM?

The latest version, RTCM 3 MSM, supports all global satellite constellations and signals. It allows faster initialization, better accuracy, and is more efficient in bandwidth use. It’s also future-proof and regularly updated by a global standards body.

Can I mix old RTK receivers with new ones? 

Yes, but only if they support a common message type like RTCM or CMR. By using an older receiver as either the base or rover you are limiting the effectiveness of the complete system. However, in open sky or areas without many obstacles you will still be able to survey effectively.  

What if my base doesn’t support the latest RTCM 3 message type?

If your base does not support the latest RTCM message type you may want to instead use CMR+ if available, and if not RTCM 2. Older receivers will likely perform better when using CMR+.    

What’s the best practice for setting up an RTK system today?

Use RTCM 3.3 whenever possible. Make sure your base and rover support the same message types and versions. Avoid proprietary formats unless required, and keep firmware up to date to ensure compatibility and performance.

Bench Mark Equipment & Supplies is your team to trust with all your surveying equipment. We have been providing high-quality surveying equipment to land surveyors, engineers, construction, airborne and resource professionals since 2002. This helps establish ourselves as the go-to team in Calgary, Canada, and the USA. Plus, we provide a wide selection of equipment, including global navigation satellite systems, RTK GPS equipment, GNSS receivers, and more. We strive to provide the highest level of customer care and service for everyone. To speak to one of our team today, call us at +1 (888) 286-3204 or email us at [email protected]

About the Author

Réal is your go to man for answers on technology, and what equipment is the best fit for your company. With a degree from Trinity Western University, Réal has the knowledge and experience to quickly understand your needs and find the best solution for you.​

In this article