For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

Connect the Autel EVO Max 4T, 4N, and Alpha to RTKdata NTRIP corrections. Enable RTK, choose Custom Network RTK, and enter host, port, and AUTO mountpoint for centimeter RTK.

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.

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

Don't have an RTKdata.com account yet? 👉 Start 30-day Free Trial or View Pricing

Step-by-step setup

1

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.

2

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.

3

Enable RTK

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

4

Select Custom (not Network RTK)

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

5

Enter NTRIP connection settings

Select your region and enter the corresponding server details:

  • 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

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.

6

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.

Vertical reference (heights)

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.

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.

Last updated

Was this helpful?