> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/qgroundcontrol.md).

# QGroundControl NTRIP Setup: PX4 Drone RTK

**QGroundControl (QGC)** is the ground control station for PX4-based drones. Its built-in NTRIP client streams RTK corrections from a caster like RTKdata.com to the vehicle, so any PX4 aircraft with an RTK-capable GNSS receiver can reach centimeter-level accuracy. One setup covers every PX4 vehicle.

## Requirements

* **QGroundControl** (current version) on the ground station
* PX4 vehicle with an **RTK-capable GNSS receiver**
* Telemetry link between QGC and the vehicle
* Internet on the ground station
* Active RTKdata.com account with RTK credentials

{% hint style="info" %}
Don't have an RTKdata.com account yet? [Start 30-day Free Trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) or [View Pricing](https://rtkdata.com/pricing/)
{% endhint %}

## Step-by-step setup

{% stepper %}
{% step %}

### Open the NTRIP / RTK settings

In QGroundControl, open **Application Settings → NTRIP / RTK**.
{% endstep %}

{% step %}

### Enter your RTKdata caster details

Fill in the fields using your region's host:

{% tabs %}
{% tab title="North America" %}

* **Host address:** `rtk.rtkdata.com` (IP fallback `13.56.117.10`)
* **Server port:** `2101`
* **Username / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`)
* **Mount Point:** `AUTO` (ALL CAPS) — or use **Browse** to pick from the source table
* **Use TLS encryption:** **off**
* **RTCM Message Filter:** leave empty (forward all)
  {% endtab %}

{% tab title="Europe" %}

* **Host address:** `eu.rtkdata.com` (IP fallback `3.73.41.96`)
* **Server port:** `2101`
* **Username / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`)
* **Mount Point:** `AUTO` (ALL CAPS) — or use **Browse** to pick from the source table
* **Use TLS encryption:** **off**
* **RTCM Message Filter:** leave empty (forward all)
  {% endtab %}

{% tab title="Australia" %}

* **Host address:** `aus.rtkdata.com` (IP fallback `54.206.56.130`)
* **Server port:** `2101`
* **Username / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`)
* **Mount Point:** `AUTO` (ALL CAPS) — or use **Browse** to pick from the source table
* **Use TLS encryption:** **off**
* **RTCM Message Filter:** leave empty (forward all)
  {% endtab %}
  {% endtabs %}

Alternative mountpoints for a specific datum: `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`.
{% endstep %}

{% step %}

### Connect and verify RTK Fix

QGC connects to the caster and forwards RTCM corrections to the vehicle. Watch the GPS status progress **3D Fix → RTK Float → RTK Fixed**.

{% hint style="danger" %}
**RTKdata needs your position (GGA).** The caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections — it is **not** a VRS service and sends nothing without a position. QGC must forward the vehicle's position to the caster. If you connect but stay on **Float** with no Fix, the position/GGA is not reaching the caster — see Troubleshooting and [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md).
{% endhint %}
{% endstep %}
{% endstepper %}

## Vertical reference (heights)

{% hint style="info" %}
RTKdata delivers **ellipsoidal heights** (WGS 84 ellipsoid). Apply a geoid model in your processing if you need orthometric heights.
{% endhint %}

## Troubleshooting

| Problem                      | Cause                                          | Fix                                                                                         |
| ---------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Connects but stays on Float  | Vehicle position (GGA) not reaching the caster | Ensure the vehicle has a 3D fix so QGC can report position; update QGC to a current version |
| Connection fails immediately | TLS enabled                                    | Turn **Use TLS encryption** off — RTKdata uses a plain caster on `2101`                     |
| Authentication fails         | Wrong credentials                              | Re-enter username/password from the dashboard (username starts with `rtk`)                  |
| Mount point empty in Browse  | Source table not loaded                        | Re-open the settings to refresh, then select `AUTO`                                         |

## Tips

* **One page, every PX4 vehicle.**
* **Leave the RTCM Message Filter empty** so all correction messages are forwarded.
* **TLS off, port `2101`, mountpoint `AUTO` in ALL CAPS.**

## Related Industry Solutions

* [Drones](https://rtkdata.com/drones/)
* [Robotics](https://rtkdata.com/robotics/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/qgroundcontrol.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.