# RTK GPS [Real Time Kinematic (RTK)](https://en.wikipedia.org/wiki/Real_Time_Kinematic) GNSS/GPS systems provide centimeter-level accuracy, allowing PX4 to be used in applications like precision surveying (where pinpoint accuracy is essential). This feature requires *QGroundControl* running on a laptop/PC and a vehicle with a WiFi or Telemetry radio link to the ground station laptop. :::note Some RTK GPS setups can provide yaw/heading information, as an alternative to the compass: * [RTK GPS Heading with Dual u-blox F9P](/px4-user-guide/drone_parts/peripherals/rtk_gps/u-blox_f9p_heading.md). * GPS directly output yaw (see table below). ::: ## Supported RTK Devices PX4 supports the [u-blox M8P](https://www.u-blox.com/en/product/neo-m8p), [u-blox F9P](https://www.u-blox.com/en/product/zed-f9p-module) and the [Trimble MB-Two](https://www.trimble.com/Precision-GNSS/MB-Two-Board.aspx) GPS, and products that incorporate them. The RTK compatible devices below that are expected to work with PX4 (it omits discontined devices). The table indicates devices that also output yaw, and that can provide yaw when two on-vehicle units are used. It also highlights devices that connect via the CAN bus, and those which support PPK (Post-Processing Kinematic). | GPS | Yaw Output | [Dual F9P GPS Heading](/px4-user-guide/drone_parts/peripherals/rtk_gps/u-blox_f9p_heading.md) | [DroneCAN](/px4-user-guide/drone_parts/peripherals/dronecan.md) | PPK | | ----------------------------------------------------------------------------------------------------------------- | :--------: | :-------------------------------------------------------------------------------------------: | :-------------------------------------------------------------: | :-: | | [ARK RTK GPS](/px4-user-guide/drone_parts/peripherals/rtk_gps/ark_rtk_gps.md) | | ✓ | ✓ | | | [CUAV C-RTK GPS](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_cuav_c-rtk.md) | | | | | | [CUAV C-RTK2](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_cuav_c-rtk2.md) | | | | ✓ | | [CUAV C-RTK 9Ps GPS](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_cuav_c-rtk-9ps.md) | | ✓ | | | | [Femtones MINI2 Receiver](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_fem_mini2.md) | | | | | | [Freefly RTK GPS](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_freefly.md) (F9P) | | | | | | [CubePilot Here3](https://www.cubepilot.org/#/here/here3) | | | ✓ | | | [Holybro H-RTK F9P Helical or Base](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_holybro_h-rtk-f9p.md) | | ✓ | | | | [Holybro DroneCAN H-RTK F9P Helical](https://holybro.com/products/dronecan-h-rtk-f9p-helical) | | ✓ | ✓ | | | [Holybro H-RTK F9P Rover Lite](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_holybro_h-rtk-f9p.md) | | | | | | [Holybro DroneCAN H-RTK F9P Rover](https://holybro.com/products/dronecan-h-rtk-f9p-rover) | | | ✓ | | | [Holybro H-RTK M8P GNSS](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_holybro_h-rtk-m8p.md) | | | | | | [Holybro H-RTK UM982 GPS](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_holybro_unicore_um982.md) | ✓ | | | | | [LOCOSYS Hawk R1](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_locosys_r1.md) | | | | | | [LOCOSYS Hawk R2](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_locosys_r2.md) | ✓ | | | | | [Septentrio AsteRx-RIB](/px4-user-guide/drone_parts/peripherals/rtk_gps/septentrio_asterx-rib.md) | ✓ | Septentrio dual antenna heading | | ✓ | | [Septentrio mosaic-go](/px4-user-guide/drone_parts/peripherals/rtk_gps/septentrio_mosaic-go.md) | ✓ | Septentrio dual antenna heading | | ✓ | | [SparkFun GPS-RTK2 Board - ZED-F9P](https://www.sparkfun.com/products/15136) | | ✓ | | | | [SIRIUS RTK GNSS ROVER (F9P)](https://store-drotek.com/911-sirius-rtk-gnss-rover-f9p.html) | | ✓ | | | | [mRo u-blox ZED-F9 RTK L1/L2 GPS](https://store.mrobotics.io/product-p/m10020d.htm) | | ✓ | | | | [Trimble MB-Two](/px4-user-guide/drone_parts/peripherals/rtk_gps/rtk_gps_trimble_mb_two.md) | ✓ | | | | :::note Some RTK modules can only be used in a particular role (base or rover), while others can be used interchangeably. ::: ## Positioning Setup/Configuration RTK positioning requires a *pair* of [RTK GPS devices](#supported-rtk-devices): a "base" for the ground station and a "rover" for the vehicle. In addition you will need: * A *laptop/PC* with QGroundControl (QGroundControl for Android/iOS do not support RTK) * A vehicle with a WiFi or Telemetry radio link to the laptop. :::note *QGroundControl* with a base module can theoretically enable RTK GPS for multiple vehicles/rover modules. At time of writing this use case has not been tested. ::: ### Hardware Setup #### Rover RTK Module (Vehicle) The connection method and cables/connectors required depends on the selected RTK module (and on the [flight controller](/px4-user-guide/drone_parts/flight_controller.md)). Most are connected via the flight controller's GPS port, in the same way as any other GPS module. Some are connected to the [CAN](/px4-user-guide/drone_parts/peripherals/can.md) bus (i.e. using [DroneCAN](/px4-user-guide/drone_parts/peripherals/dronecan.md)). See [documentation for the selected device](#supported-rtk-devices) and [DroneCAN](/px4-user-guide/drone_parts/peripherals/dronecan.md) for more information on wiring and configuration. #### Base RTK Module (Ground) Connect the base module to *QGroundControl* via USB. The base module must not be moved while it is being used. :::tip Choose a position where the base module won't need to be moved, has a clear view of the sky, and is well separated from any buildings. Often it is helpful to elevate the base GPS, by using a tripod or mounting it on a roof. ::: #### Telemetry Radio/WiFi The vehicle and ground control laptop must be connected via [wifi or a radio telemetry link](/px4-user-guide/drone_parts/peripherals/telemetry.md). The link *must* use the MAVLink 2 protocol as it makes more efficient use of the channel. This should be set by default, but if not, follow the [MAVLink2 configuration instructions](#mavlink2) below. ### RTK Connection Process The RTK GPS connection is essentially plug and play: 1. Start *QGroundControl* and attach the base RTK GPS via USB to the ground station. The device is recognized automatically. 2. Start the vehicle and make sure it is connected to *QGroundControl*. :::tip *QGroundControl* displays an RTK GPS status icon in the top icon bar while an RTK GPS device is connected (in addition to the normal GPS status icon). The icon is red while RTK is being set up, and then changes to white once RTK GPS is active. You can click the icon to see the current state and RTK accuracy. ::: 3. *QGroundControl* then starts the RTK setup process (known as "Survey-In"). Survey-In is a startup procedure to get an accurate position estimate of the base station. The process typically takes several minutes (it ends after reaching the minimum time and accuracy specified in the [RTK settings](#rtk-gps-settings)). You can track the progress by clicking the RTK GPS status icon. ![survey-in](/files/2hVIm4TnXjTgJcBFnBLT) 4. Once Survey-in completes: * The RTK GPS icon changes to white and *QGroundControl* starts to stream position data to the vehicle: ![RTK streaming](/files/qkBYUo0PVA7IaSmjyCFt) * Vehicle GPS switches to RTK mode. The new mode is displayed in the *normal* GPS status icon (`3D RTK GPS Lock`): ![RTK GPS Status](/files/vhr2h5uzyvgt4S6AkByv) ### Optional PX4 Configuration The following settings may need to be changed (using *QGroundControl*). #### RTK GPS settings The RTK GPS settings are specified in the *QGroundControl* [General Settings](https://docs.qgroundcontrol.com/master/en/SettingsView/General.html#rtk_gps) (**SettingsView > General Settings > RTK GPS**). ![RTK GPS Setup](/files/3i98dwMxuCsWCTHhjSNu) These settings define the minimum duration and minimum accuracy for completing the RTK GPS setup process (known as "Survey-In). :::tip You can save and reuse a base position in order to save time: perform Survey-In once, select *Use Specified Base Position* and press **Save Current Base Position** to copy in the values for the last survey. The values will then persist across QGC reboots until they are changed. ::: #### MAVLink2 The MAVLink2 protocol must be used because it makes more efficient use of lower-bandwidth channels. This should be enabled by default on recent builds. To ensure MAVLink2 is used: * Update the telemetry module firmware to the latest version (see [QGroundControl > Setup > Firmware](https://docs.qgroundcontrol.com/master/en/SetupView/Firmware.html)). * Set [MAV\_PROTO\_VER](/px4-user-guide/advanced_config/parameter_reference.md#MAV_PROTO_VER) to 2 (see [QGroundControl Setup > Parameters](https://docs.qgroundcontrol.com/master/en/SetupView/Parameters.html)) #### Tuning You may also need to tune some parameters as the default parameters are tuned assuming a GPS accuracy in the order of meters, not centimeters. For example, you can decrease [EKF2\_GPS\_V\_NOISE](/px4-user-guide/advanced_config/parameter_reference.md#EKF2_GPS_V_NOISE) and [EKF2\_GPS\_P\_NOISE](/px4-user-guide/advanced_config/parameter_reference.md#EKF2_GPS_P_NOISE) to 0.2. #### Dual Receivers A second GPS receiver can be used as a backup (either RTK or non RTK). See the [EKF2 GPS Configuration](/px4-user-guide/advanced_config/tuning_the_ecl_ekf.md#gps) section. ### Vehicle Setup Example The airframe build topic [DJI Flamewheel 450 with distance sensor and RTK GPS](/px4-user-guide/airframes/frames_multicopter/dji_flamewheel_450.md) describes an airframe setup with the Here+ RTK GPS and a Pixhawk 3 Pro. ## Further Information * [RTK-GPS (PX4-Integration)](/px4-user-guide/development/hardware/rtk_gps.md): Developer information about integrating RTK-GPS support into PX4. * [Real Time Kinematic](https://en.wikipedia.org/wiki/Real_Time_Kinematic) (Wikipedia) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://px4.gitbook.io/px4-user-guide/drone_parts/peripherals/rtk_gps.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.