# Autel EVO II RTK

Connect the **Autel EVO II Pro RTK V3** to RTKdata.com's NTRIP correction service for centimeter-level positioning. This guide also applies to the **EVO II Enterprise RTK (640T)** thermal variant.

{% hint style="danger" %}
Autel consumer drones such as the **EVO Nano**, **EVO Lite**, and non-RTK EVO II models do **NOT** have an RTK module. This guide applies only to the EVO II Pro RTK V3 and EVO II Enterprise RTK (640T).
{% endhint %}

## Requirements

* **Aircraft:** Autel EVO II Pro RTK V3 (or EVO II Enterprise RTK 640T) with built-in RTK module
* **Controller:** Autel Smart Controller V3
* **Software:** Autel Explorer app — installed and updated to the latest version
* **Firmware:** Aircraft and controller firmware updated to the latest version
* **Internet:** Wi-Fi hotspot from your phone or mobile data connection on the controller
* **RTKdata account:** Active subscription with NTRIP 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 %}

#### Power on and connect to the internet

Power on the EVO II Pro RTK V3 and the Autel Smart Controller V3. Wait for them to link, then connect the controller to the internet via Wi-Fi hotspot or mobile data.
{% endstep %}

{% step %}

#### Open Autel Explorer

Launch the **Autel Explorer** app on the Smart Controller V3 and enter the camera/flight view.
{% endstep %}

{% step %}

#### Open RTK settings

* Tap **Settings** (gear icon)
* Navigate to the **RTK** section
* Toggle **RTK** to **ON**
  {% endstep %}

{% step %}

#### Select Custom NTRIP

Select **Custom NTRIP** as the RTK correction source.
{% endstep %}

{% step %}

#### Enter NTRIP connection settings

Select your region and enter the corresponding server details:

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

* **Host (domain):** `rtk.rtkdata.com`
* **Host (IP fallback):** `13.56.117.10`
* **Port:** `2101`
* **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login)
* **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`
  {% endtab %}

{% tab title="Europe" %}

* **Host (domain):** `eu.rtkdata.com`
* **Host (IP fallback):** `3.73.41.96`
* **Port:** `2101`
* **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login)
* **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`
  {% endtab %}

{% tab title="Australia" %}

* **Host (domain):** `aus.rtkdata.com`
* **Host (IP fallback):** `54.206.56.130`
* **Port:** `2101`
* **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login)
* **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`
  {% endtab %}
  {% endtabs %}

{% hint style="warning" %}
Only these four mountpoints are valid. Typing local CRS names as mountpoints will result in **no corrections**. Always use **ALL CAPS**.
{% endhint %}
{% endstep %}

{% step %}

#### Connect and verify

* Tap **Connect** to save and apply the settings
* Place the drone **outdoors** in an open area with clear sky view — the RTK module needs a GNSS satellite fix before it can communicate with the NTRIP server
* Monitor the RTK status indicator in Autel Explorer:

| Status     | Meaning                                                                 |
| ---------- | ----------------------------------------------------------------------- |
| **SINGLE** | Basic GPS fix acquired. No corrections applied yet.                     |
| **FLOAT**  | Correction data is being received and processed. Accuracy is improving. |
| **FIX**    | Centimeter-level accuracy is active. Standard deviation below 2 cm.     |

Convergence from SINGLE to FIX typically takes **30–90 seconds** in open sky conditions.
{% endstep %}
{% endstepper %}

## Vertical reference (heights)

{% hint style="info" %}
RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights (height above mean sea level). If your workflow requires orthometric heights, apply a geoid model in your post-processing software.
{% endhint %}

## Troubleshooting

| Problem                     | Cause                                    | Fix                                                                                                                            |
| --------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| No corrections received     | Drone is indoors or has no satellite fix | Move outdoors to open sky. The drone must acquire satellites before sending GGA data to the NTRIP server.                      |
| No corrections received     | No internet on controller                | Verify connectivity by opening a browser on the Smart Controller V3.                                                           |
| No corrections received     | Wrong credentials                        | Re-enter username and password from your RTKdata dashboard. Credentials are case-sensitive and the username starts with `rtk`. |
| RTK stays on FLOAT          | Obstructed sky view                      | Move away from buildings, trees, and power lines.                                                                              |
| RTK stays on FLOAT          | Too far from base station                | Verify your RTKdata subscription is active and you are within 50 km of a base station.                                         |
| Connection drops mid-flight | Weak internet connection                 | Use a stable hotspot or ensure strong cellular signal on the controller.                                                       |

## Tips

* **Firmware matters.** Always update the aircraft and Smart Controller V3 to the latest firmware before troubleshooting connectivity issues.
* **EVO II Enterprise RTK (640T)** uses the same NTRIP setup flow — the thermal camera variant follows identical RTK configuration steps.
* **For mapping missions**, enable persistent RTK in the mission settings so the drone maintains corrections throughout the entire flight.
* **Battery swaps:** After swapping batteries, allow 30–60 seconds for RTK to re-converge to FIX. Best accuracy is achieved within 30 km of the nearest reference station.
* **Consumer Autel drones are not supported.** The EVO Nano, EVO Lite, and standard EVO II series do not have RTK hardware.