Choosing an RTK GNSS module for a UGV: single vs dual antenna heading
Updated 2026-11-17 · YUANZHI ROBOTICS engineering team
For most outdoor UGVs that already carry a LiDAR and run SLAM or map-based localization, a single-antenna RTK module such as the u-blox ZED-F9P or Unicore UM980 is enough: RTK fixes the position, and heading comes from motion and the rest of the localization stack. Choose a dual-antenna heading receiver such as the Unicore UM982 (or a NovAtel OEM7720 / PwrPak7D at the high end) when the robot must know its heading while standing still or turning on the spot, when it runs GNSS-led waypoint navigation, or when the magnetometer is unreliable near steel and motors. This guide explains how we make that call and what it changes on the vehicle.

What RTK solves, and what it does not
RTK gives centimetre-level position when the receiver has a fixed solution and a stream of corrections from a base station or an NTRIP service. It does not, on its own, tell the robot which way it is facing. A single antenna can only infer heading from its own track over the ground, which works while the vehicle drives forward and fails when it is parked, reversing, or rotating in place on skid-steer wheels or tracks.
That is the whole decision in one question: do you need heading at zero speed? If yes, you need two antennas, an INS with good heading observability, or another heading source such as LiDAR map matching.
Receivers we work with
The table lists the GNSS receivers in our payload catalog. Dimensions, mass and power are taken from the manufacturers' published data; a dash means we do not quote a figure.
| Receiver | Type | Heading from GNSS | Size (mm) | Mass | Power |
|---|---|---|---|---|---|
| u-blox ZED-F9P | RTK module | Single antenna; two modules can run as moving base and rover | 22 × 17 × 2.4 | 1.8 g | 0.2 W |
| Unicore UM980 | RTK module | Single antenna | 22 × 17 × 2.6 | 1.88 g | 0.48 W |
| Unicore UM982 | Dual-antenna RTK module | Yes, built in | 21 × 16 × 2.6 | 1.82 g | 0.6 W |
| ComNav K823 | Positioning board with IMU | Check configuration | 40 × 30 × 3.2 | — | 1.6 W |
| Xsens MTi-680G | RTK GNSS/INS | Single antenna, heading from INS fusion | 56.5 × 40.9 × 36.75 | 98 g | 1.0 W |
| NovAtel OEM7720 | Dual-antenna OEM board | Yes, built in | 71 × 46 × 7.5 | 29 g | — |
| NovAtel PwrPak7D | Enclosed dual-antenna receiver | Yes, built in | 147 × 125 × 55 | 500 g | — |
The receiver itself is rarely the weight or power problem on a UGV. The antennas, cables, the correction link and the mounting structure are what take space on the deck.
When a single antenna is the right choice
- The robot already has a good localization stack. If a LiDAR such as a Livox Mid-360 and wheel odometry are fused in a SLAM or map-based localizer, RTK anchors the map to world coordinates and stops drift on long open routes. Heading comes from the scan matcher.
- Routes are mostly forward driving. Crop rows, perimeter roads and pipeline corridors give enough motion for track-based heading between stops.
- Deck space is tight. One antenna is easier to place with a clear sky view than two antennas separated by a useful baseline.
When you need dual-antenna heading
- GNSS-led navigation. Waypoint following in fields or yards with few LiDAR features needs heading before the robot moves, otherwise the first metres of every leg are a guess.
- Turning on the spot. Skid-steer and tracked bases such as the AgileX Bunker or Clearpath Husky rotate in place often, and track-based heading is undefined during those turns.
- Magnetic disturbance. Steel structures, drive motors and battery currents make magnetometer heading unreliable on most UGV decks.
- Georeferenced sensing. When a PTZ, thermal camera or LiDAR has to tag what it sees with world coordinates, heading error turns directly into position error at range.

Antenna choice and placement
For dual-antenna heading, a longer and stiffer baseline between the two antennas gives better heading. On our own payload designs we keep the two antennas at least 30 cm apart, above the highest nearby obstruction, on the same rigid structure so the baseline does not flex. In our catalog the Harxon HX-CH7609A small helix (43.6 mm diameter, 40.8 mm tall, 30.5 g) and the full-band HX-CHX600A helix (40 mm diameter, 82.6 mm tall, 45 g) suit vehicle decks; the HX-CSX601A survey antenna (173.4 mm diameter, 500 g) is better suited to a base station or a large vehicle such as a Clearpath Warthog.
Other placement rules we follow: keep LTE/5G and video radio antennas away from the GNSS antennas, keep LiDARs from shadowing the sky view, and route coaxial cables away from motor drivers. Antenna mounting and cable routing matter as much as the receiver choice.
Corrections and integration
- Correction source. NTRIP over the vehicle's cellular link is simplest where coverage exists; a local base station with a radio link is the fallback for remote sites. Decide what the robot does when corrections drop and the solution falls from fixed to float.
- Time and frames. Feed the receiver's PPS and time to the compute module so GNSS, LiDAR and camera timestamps agree, and publish the antenna lever arms correctly in the robot's TF tree.
- ROS 2. Publish NavSatFix and heading, then fuse them with odometry and IMU, for example with robot_localization or a factor-graph localizer. Test the fallback behaviour, not only the happy path.

Our default recommendation
For a LiDAR-equipped inspection or patrol UGV, start with a single-antenna UM980 or ZED-F9P and let the LiDAR localizer provide heading. Move to a UM982 dual-antenna setup when the mission is GNSS-led, the base turns on the spot often, or you need heading before the first metre of motion. Reserve NovAtel-class receivers for projects that already specify them or rely on their ecosystem. For choosing the vehicle itself, see best UGV for outdoor security patrol and our Husky A200 payload guide.
We design and integrate GNSS/RTK payloads on UGVs, robot dogs and drones: antenna mounts, correction links, time sync and ROS 2 fusion. Sketch a set in the payload configurator, see the Clearpath Husky A200, AgileX Bunker and AgileX Hunter 2.0 platform pages, or read about our UGV payload and robot autonomy services.
FAQ
Do I need a dual-antenna GNSS receiver on my UGV?
Only if the robot needs heading while stopped or rotating in place, runs GNSS-led navigation, or must georeference sensor data accurately. If a LiDAR localizer already provides heading, a single-antenna RTK module is usually enough.
ZED-F9P or UM982 for a robot?
The ZED-F9P is a single-antenna RTK module; two can be paired as moving base and rover for heading. The UM982 has dual-antenna heading built into one module. Pick the UM982 when heading at zero speed is a requirement.
How far apart should the two GNSS antennas be on a UGV?
A longer, rigid baseline gives better heading. On our own payload designs we keep them at least 30 cm apart on the same rigid structure, with a clear sky view.
Where do RTK corrections come from on a mobile robot?
Usually from an NTRIP service over the robot's 4G/5G link, or from a local base station over a radio link at remote sites. Plan the robot's behaviour for when corrections drop.
Can YUANZHI ROBOTICS integrate RTK GNSS on a Husky, Bunker or Hunter?
Yes. We design antenna mounts, correction links, time sync and ROS 2 fusion for UGV payloads. Send your platform and route through the payload configurator.