Home › Technology › RTK
Technology

RTK GNSS Receiver for Centimetre Positioning

An RTK GNSS receiver uses corrections from a base station to reach centimetre accuracy: 0.6 cm + 0.5 ppm horizontal and 1 cm + 1 ppm vertical, with about 7 s initialisation. Eview delivers it in the HB6, HB10, HB50 and HBEV11 rovers and the HB62 base, powered by Septentrio modules.

Ask a quote See RTK receivers
0.6 cm + 0.5 ppm
Horizontal RTK
1 cm + 1 ppm
Vertical RTK
~7 s
RTK initialisation
100 Hz
Output (HB10, HB6)
How it works

How RTK reaches centimetre accuracy

Base and rover
A base station at a known point measures the same satellites as the rover and sends corrections. The HB62 is a rugged base with NTRIP and Ethernet. See base receivers.
Carrier-phase measurements
RTK uses the phase of the GNSS carrier wave, not just the code. Once the whole-cycle ambiguities are resolved, the position is accurate to the centimetre.
Corrections over RTCM
Corrections arrive as RTCM v3 from your own base, a CORS network or an NTRIP caster, over radio, 4G or Ethernet. See NTRIP and RTCM.
Multi-frequency, multi-constellation
More signals across GPS, Galileo, BeiDou, GLONASS and QZSS help ambiguities resolve quickly and keep the fix in harder sky. See multi-constellation GNSS.
Fix that holds
AIM+ removes interference, APME+ reduces multipath, LOCK+ keeps tracking under vibration and IONO+ handles scintillation. See AIM+ anti-jamming.
Fast output
Control loops need fresh positions. HB10, HB6 and HB56 output up to 100 Hz and mosaic-G5 products up to 20 Hz. See 100 Hz GNSS.
Comparison

GNSS positioning methods compared

MethodCorrectionsTypical accuracyNotes
StandaloneNoneMetre-levelSingle receiver, no external data
SBASSatellite-based augmentation (e.g. EGNOS, WAAS)Sub-metre to metre-levelFree, broadcast by geostationary satellites
DGNSSCode corrections from a base or networkSub-metreUses code, not carrier phase
Galileo HAS (PPP)Free PPP corrections on Galileo E6-B or internetUnder 25 cm horizontal (initial service)Full service targets about 20 cm H and 40 cm V (95%); no local base needed
RTK floatBase or network, RTCM v3Decimetre-levelAmbiguities not yet resolved
RTK fixedBase or network, RTCM v30.6 cm + 0.5 ppm H, 1 cm + 1 ppm VAbout 7 s initialisation; centimetre-level

RTK figures are Septentrio module specifications; HAS figures are from EUSPA. Galileo HAS is supported on mosaic-G5 products such as the HBEV11.

Recommended products

Eview RTK receivers and base stations

ProductBest forKey specs
HB62 baseYour own RTK base stationmosaic-X5, NTRIP, Ethernet, 64 GB logging, IP67, 9–36 V
HB6Lightweight RTK rovermosaic-X5, 100 Hz, 45 g, USB-C, microSD, 4.5–12 V
HB10RTK with heading and fast outputAsteRx-m3 Pro+, dual antenna, 0.15° at 1 m, 100 Hz, <10 ms latency
HB6 ProRTK and attitude in 45 gmosaic-H, heading 0.15° / pitch or roll 0.25° at 1 m, RTK + attitude up to 20 Hz
HB50Low-power RTKmosaic-G5 P3, 59 × 44 × 12 mm, 50 g, 0.44 W, 20 Hz
HB52 / HB52HUltralight RTKmosaic-G5, 48 × 35 × 12.6 mm, USB-C, microSD
HBEV11 smart antennaBase or rover in one unitmosaic-G5, receiver and antenna, one M12 cable, Galileo HAS

All products are quote-based. For a complete datasheet, email sales@gnss-solutions.com. Browse all box receivers and smart antennas.

Use cases

Where RTK is used

Drone mapping
Centimetre geotags and precise landing. See UAV and drone GNSS.
Survey and GIS
Base and rover surveying, stakeout and GIS capture. See survey and GIS.
Precision agriculture
Auto-steer and repeatable passes across the field. See precision agriculture.
Construction and mining
Machine control and site positioning. See construction and mining.
Robotics and mowers
Centimetre paths for outdoor robots and lawn mowers. See robotics GNSS.
Deformation monitoring
Continuous RTK on bridges, dams and slopes. See deformation monitoring.
Integration

How to set up RTK

Pick a correction source
Use your own HB62 base, a CORS network or an NTRIP caster. Keep the baseline short, as error grows by 0.5 ppm horizontally (5 mm per 10 km).
Log raw data too
Output RTK in real time and log raw SBF to SD for RINEX post-processing at the same time. See RTK vs PPK.
Connect to your system
NMEA and SBF out over UART, USB or Ethernet; ArduPilot and PX4 over UART. See our ArduPilot guide.
FAQ

RTK GNSS: frequently asked questions

What is RTK?

RTK (Real-Time Kinematic) is a GNSS method that uses carrier-phase measurements and corrections from a nearby base station to give centimetre positions in real time. The base and rover see the same satellites, so shared errors cancel out once the carrier-phase ambiguities are resolved.

How accurate is RTK?

Eview receivers, powered by Septentrio modules, are specified at 0.6 cm + 0.5 ppm horizontal and 1 cm + 1 ppm vertical in RTK fixed mode. The ppm term grows with distance to the base, so 10 km adds 5 mm horizontally. See real-world RTK data.

What is the difference between RTK float and RTK fixed?

In RTK float the receiver uses corrections but has not yet resolved the whole-cycle carrier ambiguities, so accuracy is decimetre-level. In RTK fixed the ambiguities are resolved and accuracy reaches the centimetre-level specification. Most applications wait for a fixed solution.

Can I use RTK without my own base?

Yes. Network RTK delivers RTCM v3 corrections from a CORS network or NTRIP caster over the internet, so you only need a rover with a data link. Running your own HB62 base gives you control of the baseline and availability where no network exists.

How long does RTK take to fix, and how does it compare with PPP?

RTK initialisation takes about 7 s with Septentrio modules. Galileo HAS PPP needs no local base, but it is decimetre-level: under 25 cm horizontal at initial service, and it takes longer to converge. RTK is still needed for centimetre work.

Related reading

Get centimetre positioning for your project

Tell us your platform, correction source and output rate, and we will recommend a rover and base.

Ask a quote