GNSS RTK Receiver Compatibility: Can Different Brands Work Together?

Can a GNSS RTK base station from one brand work with a rover from another? Can an existing field controller operate a new GNSS receiver?

These are important questions for surveying companies and equipment distributors managing mixed-brand GNSS systems.

Different brands can often exchange RTK correction data through standard formats. However, correction compatibility, instrument control and software compatibility are separate issues.

Before purchasing equipment from different manufacturers, it is important to understand exactly what needs to work together.

Quick Answer: Can Different GNSS RTK Brands Work Together?

Yes, many GNSS RTK receivers from different brands can work together when they support compatible correction formats and communication methods.

RTCM correction messages are widely used for cross-brand base-rover operation.

However, RTCM support alone does not guarantee a successful RTK fixed solution. The exact message types, satellite signals, firmware, communication settings and positioning configuration must also be compatible.

A field controller that can receive corrections for one receiver may not be able to configure another manufacturer's receiver.

1. Base and Rover Compatibility: Start With RTCM

A GNSS RTK base station sends correction information to a rover.

When the base and rover come from different manufacturers, a standardized correction format is usually the most practical starting point.

RTCM 3.x is widely supported by professional GNSS receivers.

Modern RTCM Multiple Signal Messages (MSM) can represent observations from satellite constellations such as GPS, GLONASS, Galileo and BeiDou.

However, buyers should check more than the RTCM version number.

For example, a rover may support RTCM 3.x but not every MSM message type produced by the base.

Before purchasing, confirm:

• RTCM version supported by both receivers

• Correction message types available from the base

• Message types accepted by the rover

• GNSS constellations and signals supported by both systems

• Firmware requirements and known compatibility limitations

For a mixed-brand fleet, request written confirmation or a practical test using the exact receiver models.

2. NTRIP Compatibility Is Not the Same as RTCM Compatibility

NTRIP is a method for transporting GNSS correction data over the internet.

RTCM describes correction data formats, while NTRIP provides a way to distribute those streams.

A rover may successfully connect to an NTRIP caster but still fail to obtain a fixed RTK solution if the correction stream is unsuitable.

When using a CORS or network RTK service, verify:

1. Caster address and port

2. Username and password requirements

3. Mountpoint selection

4. Correction stream format and message types

5. Whether the service requires the rover's approximate position through NMEA GGA messages

6. Network connectivity and data delivery

For more background, read our guide What Is CORS in GNSS Surveying?.

3. Radio Compatibility: Matching Frequency Is Not Enough

When using a local base station and radio corrections, surveyors sometimes assume that two receivers will communicate if their radios operate on the same frequency.

This is not always true.

The radios may also need compatible:

• Channel spacing

• Modulation and over-the-air protocols

• Data transmission rates

• Error correction and framing settings

• Correction data format

For example, two receivers may both support UHF radio operation but use incompatible transmission protocols.

In that situation, the rover may receive no usable correction stream.

Check the exact radio configuration of both devices and comply with local radio licensing and frequency regulations.

For a comparison of correction delivery methods, see RTK Radio vs NTRIP.

4. Field Controller and Software Compatibility

Correction compatibility does not mean that a field controller can operate every GNSS receiver.

A controller typically uses field software and manufacturer-specific drivers or communication interfaces to configure receiver settings.

For example, a controller may connect to a GNSS receiver through Bluetooth but lack the software support required to:

• Configure base or rover operation

• Select correction input

• Start and stop surveys

• Manage antenna settings

• Record observations and perform stakeout

This distinction is particularly important for equipment distributors who plan to supply receivers and controllers from different brands.

Browse our Survey Data Collectors to compare available field controller options.

5. A Fixed Solution Does Not Prove Coordinate Compatibility

Suppose a rover successfully receives corrections from a different-brand base station and reports RTK FIX.

Does that mean the coordinates are correct?

Not necessarily.

A fixed solution indicates that the receiver has resolved the relevant carrier-phase ambiguities according to its positioning model. It does not independently verify the coordinate reference system or base station position.

Potential problems include:

• Incorrect base station coordinates

• Different coordinate reference systems

• Wrong datum transformation parameters

• Incorrect localization or site calibration

• Confusion between ellipsoidal and orthometric heights

• Incorrect antenna height settings

For example, two rover systems may both show FIX while producing different local grid coordinates because they use different site transformations.

Before starting production work, measure known control points and confirm that the results meet project tolerances.

Read RTK Fixed but Wrong Coordinates for a more detailed explanation.

Cross-Brand GNSS RTK Compatibility Checklist

A supplier should be able to explain which combinations have been tested and which still require verification.

Practical Example: Adding a New Rover to an Existing Fleet

Consider a surveying contractor using several GNSS RTK receivers from Brand A.

The contractor wants to purchase additional rovers from Brand B without replacing the existing base station.

Before ordering, the team should first confirm that the Brand A base can transmit an RTCM correction stream supported by the proposed Brand B rover.

Next, it should test the selected correction delivery method, whether UHF radio or NTRIP.

The team should then verify that its field software can configure the new receiver and handle the required coordinate system.

Finally, both receiver types should measure the same known control points to check agreement within the project's tolerances.

This is an illustrative procurement workflow, not a documented test of particular brands or models.

Questions to Ask Your GNSS Equipment Supplier

When comparing mixed-brand GNSS systems, send the supplier the following information:

• Existing base station brand and exact model

• Proposed rover model

• Current RTCM output settings

• Radio or NTRIP correction method

• Field controller and software version

• Country of operation and required coordinate system

Ask whether the proposed configuration has been tested and what limitations may apply.

A useful supplier response should identify the required settings and compatibility conditions rather than simply claiming that all GNSS receivers work together.

Final Thoughts

Different GNSS RTK brands can often operate together, but successful integration depends on more than a shared correction format.

RTCM message support, correction delivery, field software and coordinate configuration must all be checked separately.

For surveying companies and distributors, testing the complete system before placing a large order is usually the safest approach.

RTKSurvey.com is a multi-brand surveying equipment supplier offering GNSS Receivers and related field accessories.

If you are planning a mixed-brand GNSS RTK system, contact our team with your existing equipment models and intended application to discuss suitable options.