Drone GPS and RTK Guide: GNSS, Dual-Band, Compass and CAN
The GPS module is the autopilot's link to the outside world: position hold, return to home and every automatic mission depend on it. Choosing one comes down to how accurate you need to be, which autopilot and firmware you run, and where on the airframe it will sit.
GPS, GNSS and satellite constellations
GPS is the American satellite system; GNSS is the general term for all of them. Alongside GPS there are GLONASS (Russia), Galileo (Europe) and BeiDou (China), plus regional systems such as Japan's QZSS and India's NavIC, and SBAS services that broadcast corrections. A receiver that tracks several constellations at once sees more satellites, gets a fix faster and holds accuracy better near buildings, hills and trees.
In u-blox terms, the older M8 generation tracks up to three constellations at once, while M9 and M10 receivers can track up to four. A good single-band module typically gives a position within one to a few metres, which is plenty for position hold and return to home.
Single-band or dual-band (L1/L5)
Classic receivers use only the L1 band. Dual-band receivers add a second band, L5 or L2, which lets them remove most of the error the ionosphere adds and reject signals reflected off buildings far better. The result is steadier accuracy in difficult places and, in RTK receivers, a much faster fix. Today most of the L5-band work is done by Galileo E5a and BeiDou B2a, since GPS L5 is still officially pre-operational.
The common u-blox families, from basic to precise:
- M8 (for example M8N): single-band, the long-time standard, a few metres of accuracy
- M9 and M10: single-band, more constellations at once and better interference handling; M10 is common on INAV and FPV builds
- F10 (for example MAX-F10S): dual-band L1/L5 for metre-level accuracy in difficult environments, but not RTK
- M8P: single-band with RTK, about 2.5 cm with corrections (used in the Here3 and Here3+)
- F9P: dual-band RTK, about 1 cm plus 1 ppm, with fast convergence and moving-baseline support. The original ZED-F9P uses L1/L2; L1/L5 versions such as the NEO-F9P (used in the Here4) also exist
What RTK is and when you need it
RTK (Real-Time Kinematic) takes the receiver from metres to centimetres. A base station at a known position measures the satellite errors and sends RTCM corrections to the aircraft, which uses them to solve its position from the carrier phase of the signal. The status first shows RTK float, while corrections are in use but precision is not yet full, and then RTK fixed.
Corrections can come from your own base station, which surveys its position in and passes corrections through Mission Planner or QGroundControl over the telemetry link, or from an NTRIP service over the internet, fed by a network of permanent reference stations. With NTRIP, stay reasonably close to the station: the error grows by roughly a centimetre for every 10 km of distance.
You need RTK for mapping and surveying, precision landing on a pad, crop rows, close-range inspection and rovers that follow exact paths. Most FPV, long-range and general photo flights do not. Keep in mind that a base which surveyed itself in for a few minutes gives centimetre accuracy relative to the base, not on the map; for absolute accuracy, the base must sit on a precisely known point.
The compass is still the weak point
Most GPS modules include a magnetometer, and that is usually the reason a drone toilet-bowls or drifts in position hold. Current in the battery leads, the distribution board and the ESC wiring creates magnetic fields, and their strength falls off sharply with distance. That is why the GPS goes on a mast, up and away from the power wiring.
Keep power leads short and twisted together, calibrate the compass away from cars and metal structures, and make sure the module's orientation matches the setting (usually an arrow pointing forward). On many multirotors the internal compass in the autopilot sees too much interference and is disabled, leaving the one in the GPS unit. In ArduPilot, CompassMot measures how much the motors disturb the compass.
DroneCAN or serial
A serial GPS connects with a UART for position and, usually, I2C for the compass. It is simple, cheap and works with Betaflight, INAV, ArduPilot and PX4. Betaflight and most INAV builds use serial GPS.
A DroneCAN GPS has its own processor and sends processed data over the CAN bus. Several devices share one bus, the differential signal is more robust over longer cables, the compass, LED, buzzer and safety switch can share the same cable, and the module's firmware can be updated through the autopilot. It needs a CAN-capable autopilot and firmware support, which in practice means ArduPilot or PX4.
Here3, Here3+ and Here4
CubePilot's Here units are DroneCAN GNSS modules designed around the Cube. The Here3 combines a u-blox M8P with an STM32F302 processor and a combined IMU and compass. The Here3+ keeps the M8P but moves to a faster STM32H757 processor and an RM3100 compass. Both reach about 2.5 cm with RTK corrections. The Here4 moves to a dual-band NEO-F9P (L1/L5), about 1 cm plus 1 ppm with RTK and updates of up to 20 Hz.
For RTK you also need a base: either your own, such as the Here+ Base, or an NTRIP service. Match the base to the aircraft receiver: a dual-band receiver needs dual-band corrections to deliver its full advantage.
GPS for yaw (moving baseline)
Two RTK receivers on the same aircraft can measure the direction between their antennas and give the autopilot a heading with no compass at all. That helps near steel structures and power lines, and on heavy aircraft with high currents where the compass struggles. ArduPilot supports this with pairs of F9P receivers, including two DroneCAN units such as a pair of Here4, as well as some dual-antenna single units. M8P-based receivers do not support it.
The antennas must be at least 30 cm apart, both need a clear view of the sky, and their exact positions relative to the centre of gravity have to be entered in the parameters. A compass can stay on as a fallback.
Common mistakes
- Mounting the GPS flat on the frame next to the video transmitter or under a carbon plate. Carbon blocks signals, and 1.2–1.3 GHz video sits right next to the GNSS bands
- Testing RTK indoors or between buildings and expecting a fixed solution
- Arming before the GPS has a solid fix and enough satellites, instead of waiting for the pre-arm checks to pass
- Calibrating the compass next to a car or metal table, or with the module's orientation set wrong
- Expecting absolute map accuracy from a base that only surveyed itself in for a few minutes
- Relying on GNSS alone. Jamming and spoofing have been widely reported in Israel, so set sensible failsafes and know how to fly in a mode that does not need GPS



