u-blox positions ZED-F9P as a multi-band RTK module capable of centimeter-level accuracy in seconds. A survey drone still earns that performance only when correction delivery, antenna installation, time synchronization, RF cleanliness, coordinate frames, and failure handling are engineered as one navigation chain.
Side-by-side design view
| Integration layer | Design decision | Flight validation |
|---|---|---|
| GNSS bands | Match module variant and antenna | Constellation and band tracking under motion |
| Corrections | RTCM or supported service path | Latency, dropouts and reconvergence |
| Antenna | Ground plane, LNA, cable and placement | All attitudes and payload configurations |
| Time | Timepulse and timestamp architecture | Camera or lidar event alignment |
| Estimator | Quality gates and coordinate frames | Fixed, float and standalone transitions |
Choose the correction architecture first
ZED-F9P supports multi-band RTK and standard correction workflows. Decide whether the aircraft receives corrections from a local base, a network service, or another vehicle before selecting the telemetry link and writing the navigation interface.
Correction age and transport latency are part of the accuracy budget. Log them beside fix type, satellite count, dilution metrics, carrier solution status, and estimator innovations so field problems can be diagnosed rather than guessed.
Antenna installation determines usable performance
Place the GNSS antenna above carbon fiber, batteries, video transmitters, high-current wiring, switching inductors, and digital clocks. Provide the ground plane and RF conditions required by the selected antenna rather than copying a module-only reference layout.
Survey drones often carry cameras, gimbals, or lidar that change the electromagnetic and mechanical environment. Test every production payload configuration and measure the antenna-to-sensor lever arm in the same body coordinate frame used by the estimator.
Time and coordinate integrity
Centimeter position is not enough when an image is captured at the wrong instant. Use timepulse and event timestamps to align GNSS, camera shutter, IMU, and logging. Document all delays and confirm that firmware updates do not silently shift them.
Define datum, projection, antenna reference point, body frame, sensor frame, and output convention. Many apparent GNSS errors are actually frame, sign, or lever-arm mistakes that a fixed solution cannot detect.
Degraded modes and procurement
Test entry into RTK fixed, operation in float, correction loss, RF interference, base-coordinate errors, spoofing or jamming indicators, reboot, and reconvergence. The aircraft needs an explicit rule for continuing, pausing, returning, or landing in each quality state.
Quote the complete ZED-F9P suffix. Confirm band combination, firmware compatibility, package, temperature range, antenna BOM, correction-service support, and the production test method before approving alternatives.
Related UAV chip pages
Need a BOM review or quotation?
Send the exact part numbers, package, quantity, target application, and required date. We will reply with availability for review—without presenting unverified stock claims.
Submit a UAV chip RFQFrequently asked questions
Does ZED-F9P always provide centimeter accuracy?
No. It requires suitable signals, antenna installation, valid corrections, convergence, and a correctly configured navigation chain.
Can RTK replace the IMU?
No. GNSS and IMU solve complementary timing and dynamics problems and are normally fused.
Which ZED-F9P suffix should be ordered?
The exact suffix must match the required bands, firmware, grade, package, and approved antenna and correction architecture.
Official technical references
Specifications must be confirmed in the latest manufacturer datasheet for the exact orderable suffix.