> 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/drones-and-uavs/autel-evo-max-4t-4n.md).

# Autel EVO Max 4T / 4N RTK Setup: Custom NTRIP

Connect Autel's current enterprise drones — the **EVO Max 4T**, **EVO Max 4N**, and **Autel Alpha** — to RTKdata.com's NTRIP correction service for centimeter-level positioning.

{% hint style="danger" %}
The **EVO Max 4T / 4N** require the **optional Autel EVO Max RTK Module**. A base EVO Max without the module has **no RTK** and cannot use RTKdata. The **Autel Alpha** has RTK built in (no module needed). For the older **EVO II Pro RTK V3 / EVO II Enterprise (640T)**, see the separate [Autel EVO II RTK](/integration-hub/drones-and-uavs/autel-evo-ii-rtk.md) guide.
{% endhint %}

{% hint style="warning" %}
The EVO Max series and Alpha are controlled by the **Autel Enterprise App** on the **Smart Controller V3** — not the **Autel Explorer** app used by the older EVO II line. Menu names below refer to the Autel Enterprise App.
{% endhint %}

## Requirements

* **Aircraft:** EVO Max 4T or 4N with the **EVO Max RTK Module** installed — or **Autel Alpha** (built-in RTK)
* **Controller:** Autel **Smart Controller V3**
* **Software:** **Autel Enterprise App**, updated to the latest version
* **Firmware:** Aircraft, RTK module (if applicable), and controller firmware updated to the latest version — version mismatches commonly break RTK
* **Internet:** Wi-Fi hotspot tethered to the controller (the controller relays the correction stream)
* **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 %}

### Install the RTK module (EVO Max only)

On the **EVO Max 4T / 4N**, install the **EVO Max RTK Module**. On the **Autel Alpha**, RTK is built in — skip this step. Update aircraft, module, and Smart Controller V3 firmware to the latest version.
{% endstep %}

{% step %}

### Connect the controller to the internet

Tether the Smart Controller V3 to a phone Wi-Fi hotspot (or other internet source). The controller, not the aircraft, carries the NTRIP stream.
{% endstep %}

{% step %}

### Enable RTK

In the **Autel Enterprise App**, open **Settings (gear icon) → RTK** and turn the **RTK Aircraft Feature** **ON**.
{% endstep %}

{% step %}

### Select Custom (not Network RTK)

Choose **Custom** (Custom Network RTK) as the correction source.

{% hint style="warning" %}
Do **not** select **"Network RTK."** That is a legacy option Autel does not operate and it will not connect to a third-party caster. All third-party casters, including RTKdata, use **Custom**.
{% endhint %}
{% 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 %}

Enter the mountpoint **`AUTO`** manually (in ALL CAPS) rather than relying on a station list — RTKdata's `AUTO` is keyed to your position, not a fixed station.

{% hint style="danger" %}
**GGA must be sent.** The RTKdata caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections. Without GGA, the drone connects but receives no corrections and stays on Float. RTKdata is single-baseline and location-keyed — it is **not** a VRS service. The aircraft must have a satellite fix (be outdoors) so it can report position. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md).
{% endhint %}
{% endstep %}

{% step %}

### Connect and verify Fix

* Save/apply the settings to connect.
* Place the drone **outdoors** in an open area so the RTK system acquires satellites.
* Watch the RTK status in the live view:

| Status     | Meaning                                                  |
| ---------- | -------------------------------------------------------- |
| **SINGLE** | Basic GNSS fix. No corrections applied yet.              |
| **FLOAT**  | Corrections received and processing. Accuracy improving. |
| **FIX**    | Centimeter-level accuracy active (\~1–2 cm).             |

Convergence typically takes 30–90 seconds in open sky.
{% endstep %}
{% endstepper %}

## Vertical reference (heights)

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

## Troubleshooting

| Problem                         | Cause                                              | Fix                                                                                                |
| ------------------------------- | -------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Won't connect to caster         | "Network RTK" selected instead of **Custom**       | Switch the correction source to **Custom**                                                         |
| No RTK option at all            | EVO Max RTK Module not installed/detected          | Install the module (EVO Max) and confirm firmware is current; Alpha has built-in RTK               |
| No corrections / stuck on Float | Drone indoors or no satellite fix → no GGA sent    | Move outdoors to open sky so the aircraft acquires satellites and reports position                 |
| No corrections                  | No internet on the controller                      | Verify the Smart Controller V3 hotspot tether                                                      |
| Authentication fails            | Wrong credentials                                  | Re-enter username/password from the RTKdata dashboard (case-sensitive, username starts with `rtk`) |
| RTK keeps dropping              | Firmware mismatch (aircraft / module / controller) | Update all three to the latest firmware                                                            |

## Tips

* **EVO Max needs the RTK module; Alpha has RTK built in.** First check which hardware you have.
* **Always pick "Custom"** for RTKdata — "Network RTK" is a non-functional legacy option.
* **Enter `AUTO` manually** in ALL CAPS as the mountpoint.
* **Firmware first.** Mismatched aircraft/module/controller firmware is the most common RTK failure on this platform.
* **Different app from EVO II.** EVO Max/Alpha use the Autel Enterprise App; the EVO II line uses Autel Explorer — don't reuse those screenshots.

## Related Industry Solutions

* [Drones](https://rtkdata.com/drones/)
* [Surveying](https://rtkdata.com/surveying/)
* [Construction](https://rtkdata.com/construction/)


---

# 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/drones-and-uavs/autel-evo-max-4t-4n.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.