Outdoor Mobile Robot Positioning: GNSS Receivers for AMRs
Outdoor mobile robot positioning needs a multi-constellation, multi-frequency RTK GNSS receiver — not a consumer GPS module. A Septentrio mosaic-X5-based receiver outputs roughly 1 cm RTK accuracy, sub-degree dual-antenna heading, up to 60 dB of AIM+ interference rejection and up to 100 Hz updates: enough for path following, auto-docking and geofencing in urban or industrial RF environments. What follows is how to size those specs to your platform.
Talk to a GNSS engineer about your robot platform
Tell us your accuracy target, correction source (NTRIP, local base, radio) and interface — we will recommend a module or receiver box and send a quote.
What accuracy does an outdoor AMR or service robot actually need?
| Robot task | Accuracy you need | What enables it |
|---|---|---|
| Waypoint navigation, patrol routing, area coverage | 1–3 m | Single-frequency GNSS is usually enough |
| Yard logistics path following, geofencing, fleet coordination | 10–30 cm | RTK position; no heading sensor required |
| Auto-docking, charging contacts, pallet or row alignment | <5 cm position plus heading | RTK with dual-antenna heading |
| Inspection tagging, survey-grade mapping, as-built capture | <2 cm absolute, repeatable | RTK with a fixed local base or network RTK |
Why standard GPS fails on outdoor robots
- Multipath. Glass facades, containers and vehicles reflect satellite signals, so position jumps metres exactly where yards and streets narrow.
- RF interference. LTE/Wi-Fi front ends, motor drives and video downlinks raise the noise floor until the receiver loses lock. Deliberate jamming is the extreme version.
- Magnetic heading drift. Robots are full of steel and current-carrying cable; a magnetometer heading reference needs constant re-calibration and still drifts near structures.
- Latency and rate. At 2 m/s a 5 Hz output leaves 40 cm between fixes. High-dynamics platforms also need a timestamped pulse-per-second (PPS) reference to align IMU and odometry.
All four are addressed at receiver level. AIM+ interference mitigation filters the RF band before it corrupts tracking, while multi-frequency reception (L1/L2/L5 + E1/E5a/E5b + B1I/B2I/B3 on mosaic-X5) resolves ionospheric delay and improves multipath rejection.
Correction links: network RTK, local base or radio
- Network RTK (NTRIP over LTE/Wi-Fi). Simplest for delivery and service robots; convergence typically under 10 seconds. Needs cellular coverage and a subscription.
- Local base station. Highest repeatability, independent of mobile networks — the standard choice for controlled industrial sites, mines and farms.
- Radio modem. For sites with no usable IP link; adds hardware at both ends.
Wire the correction source and receiver into the same clock domain. A PPS output lets the fusion layer timestamp GNSS, wheel odometry and IMU samples consistently — that is what keeps trajectories stable through turns.
Heading: dual-antenna GNSS beats a magnetometer
A dual-antenna receiver computes true heading from the phase difference between two antennas on a known baseline: no calibration, no declination, no steel or motor interference. With suitable baseline spacing you get sub-degree heading plus pitch and roll, which docking, row following and slope work depend on — without adding a gyro. Two constraints: clear sky view with a proper antenna ground plane, and a baseline long enough for your heading target. Engineering that spacing early is cheaper than retrofitting the chassis.
Spec table: module vs board vs receiver box
| Option | Positioning | Anti-jamming | Heading | Best for |
|---|---|---|---|---|
| u-blox ZED-F9P-class module | cm-level RTK, L1/L2 | No dedicated mitigation array | No native dual-antenna heading | Clean-sky prototypes, hobby-grade AMRs |
| Eview HB51 dual-antenna RTK heading board | cm-level RTK, Septentrio-based | AIM+ interference mitigation | Dual-antenna true heading | Robots where heading is the blocker |
| Eview HB52H / HB52 ultralight module | Sub-cm RTK, mosaic-G5 | AIM+ interference mitigation | Heading, pitch and roll | Small delivery robots, legged robots, battery-limited platforms |
| Eview GNSS receiver box (mosaic-X5) | 0.6 cm + 0.5 ppm H; 1.0 cm + 1.0 ppm V (RTK) | AIM+ up to 60 dB suppression | Dual-antenna support | Yard AGVs and industrial platforms needing IP67, CAN and Ethernet |
Specifications follow Eview/Septentrio published data for the named configurations — confirm the option set on your quote, because AIM+ licensing, interface and enclosure choices change the part number. Integrate a board or OEM module where you have your own enclosure; use a rugged receiver box where you would rather not design one.
Integration checklist before you order
- Interfaces: Ethernet, RS232, USB and CAN bus cover most robot controllers.
- Output rate: up to 100 Hz for high dynamics; anything above 5 Hz also improves fusion quality.
- Protocols: NMEA 0183 for bring-up, binary SBF for raw measurements, RTCM 3.x in and out for corrections.
- Timing: PPS / TimeReference for sensor timestamp alignment.
- Mounting: antenna ground plane, baseline length for heading, cable routing away from motor phase leads.
- Lead time: plan 4–6 weeks on standard OEM module orders.
FAQ: outdoor mobile robot positioning
What GNSS accuracy do outdoor mobile robots need?
Metre-level is enough for waypoint routing. Path following and geofencing need 10–30 cm. Precision tasks such as docking, row following and pallet alignment need better than 5 cm position plus heading. Eview RTK modules deliver sub-centimetre RTK accuracy with convergence typically under 10 seconds.
Is RTK necessary, or is PPP enough?
PPP gives decimetre-level accuracy with wide-area coverage and no base station, which can be acceptable for routing. RTK is the right choice for centimetre repeatability, fast convergence, or operation without a satellite correction stream. Many mosaic-family receivers support both.
Can GNSS replace SLAM on an outdoor robot?
No — they solve different problems. SLAM gives local consistency and obstacle awareness; GNSS gives global position, which stops long-range drift and allows absolute waypoint commands. The standard architecture is GNSS for the global frame plus lidar or vision SLAM for local mapping.
How do robots keep positioning under RF interference?
Interference has to be handled before it reaches the tracking loops. AIM+ monitors the spectrum and suppresses interfering signals — up to 60 dB on Eview receiver hardware — keeping RTK fixes stable near radio towers, power lines and heavy machinery instead of dropping to a dead-reckoning failsafe.
What is the fastest way to integrate GNSS into ROS 2?
Choose a receiver with documented ROS 2 driver support publishing NavSatFix, TwistWithCovarianceStamped and TimeReference topics, so data drops straight into Nav2 and standard fusion packages. Eview GNSS modules ship with ROS 2 integration guidance, and both NMEA and binary SBF output are available for custom drivers.
Next step: size the receiver to your robot
Send us your robot type, accuracy target, correction source and controller interface. We will reply with a specific module or receiver box recommendation, antenna and baseline guidance, and a quote. Browse the GNSS for robotics and autonomous robots range or contact Eview GNSS directly.
