Autel EVO RTK Base Station and NTRIP Setup Guide

Feeding corrections to Autel EVO II RTK and EVO Max 4T: custom NTRIP in the Autel Enterprise app, base station options beyond the network, and an offline workflow for sites without coverage.

Autel’s place in the RTK mapping fleet

Autel’s RTK aircraft — the EVO II RTK series and the EVO Max 4T — earned their niche as capable non-DJI options: mechanical-shutter mapping payloads on the EVO II RTK V2/V3, strong sensing on the Max, and — decisive for many government and enterprise buyers — procurement eligibility where DJI is restricted. Their RTK stack is standards-based: an onboard multi-band receiver consuming RTCM corrections configured as an NTRIP client in the Autel Enterprise app, which means the entire base-station conversation from the wider industry applies unchanged.

Correction options in the Autel Enterprise app

The app’s RTK settings offer the familiar menu: network RTK via custom NTRIP (host, port, mountpoint, username, password — the same five fields as everyone), and vendor base pairings where supported. Practical notes gathered from the field: mountpoints are case-sensitive here as everywhere; the controller supplies the data path for NTRIP, so its connectivity — SIM, Wi-Fi, or hotspot — is part of the link budget; and confirm the RTK status page shows FIX with steady correction age before arming, because Autel’s status vocabulary (FIX/FLOAT) behaves exactly as the industry’s (the universal triage).

Base options: the same three doors

Network RTK: works wherever coverage and subscriptions reach — with the standard caveats on baselines, per-rover fees, and coverage edges. A survey receiver as base: an Emlid Reach or similar serving RTCM over NTRIP feeds an EVO as readily as any rover, base-coordinates question included. A self-converging PPP base: computes its own ~1.5 cm ITRF2020 position in about three minutes from L-Band satellite corrections and serves the EVO over NTRIP — or, for internet-free sites, over transports that bridge to the controller — with no CORS dependency at all (the architecture). For the procurement contexts where Autel aircraft often fly — remote infrastructure, cross-border programs, agencies wary of external dependencies — the self-contained base is a natural pairing.

An offline recipe for coverage-free sites

Where the site has no cellular: place and converge the base; enable its Wi-Fi hotspot / local NTRIP caster; join the Autel smart controller to that Wi-Fi; enter the local caster’s host (the base’s own address), port, and mountpoint in custom NTRIP; confirm FIX. The correction path never touches the internet — base to controller over local Wi-Fi, controller to aircraft over Autel’s link — and mission range is governed by the aircraft link as normal. Keep the base logging RINEX throughout as PPK insurance; EVO raw logs plus base RINEX post-process in standard tools when a leg needs rescuing (the backup workflow).

Mixed-fleet reality: Autel beside everything else

Most Autel aircraft fly in mixed environments — beside DJI airframes, survey rovers, and machine control. The RTCM broadcast makes this a non-event: one base, one mountpoint (or radio channel), every consumer on one absolute datum, so an EVO Max inspection dataset overlays the Matrice mapping block and the rover’s checkpoints without ceremony (why the format guarantees it). Program managers who anchor the fleet this way report the practical benefit less as accuracy than as arithmetic: cross-aircraft comparisons stop needing a registration step.

Verification, because vendor mix invites doubt

When aircraft brands mix, accuracy scepticism rises — answer it with the standing two-checkpoint habit: shoot two independent points with a rover on the same correction stream after each mission, compare against the deliverable, file the residuals. Expect the EVO platforms to sit in the same 2–5 cm photogrammetric band as their peers when fed centimetre corrections. The checkpoints certify the whole chain — base coordinates, NTRIP path, Autel geotags, processing — in one number pair, which ends brand-flavoured accuracy debates before they start (the checkpoint discipline).

Program notes for 2026

Firmware cadence on Autel’s enterprise line is active — pin versions per project and test RTK behaviour after updates rather than mid-job. Batteries and payload availability are healthier than legacy-DJI spares markets but plan lead times for fleets. And the aircraft-agnostic lesson stands: invest the accuracy budget in the correction source, not the airframe badge — the base outlives every aircraft it feeds, and its absolute datum is what keeps a multi-brand program’s data coherent across the years.

Procurement contexts: why the pairing suits restricted fleets

A large share of Autel's enterprise deployments exist because procurement rules restrict alternatives — public-safety agencies, defense-adjacent contractors, critical-infrastructure operators. Those same contexts usually carry data-sovereignty and independence requirements that make the correction architecture a compliance topic: per-rover reliance on a commercial network is a third-party dependency; a self-contained base whose corrections arrive by satellite and never transit external servers is an easy line in a security review. The offline recipe above is thus not merely a remote-site trick for these fleets — it is the default posture, with NTRIP over agency networks as the convenience layer where policy allows.

One-line takeaway

Autel's RTK aircraft speak the same NTRIP-and-RTCM language as everyone else — give them an absolute, self-contained correction source and they slot into mixed fleets, restricted procurements, and coverage-free sites without a single proprietary dependency.

Field notes from mixed Autel/DJI operations

Crews flying both ecosystems off one base report the differences are cosmetic: menu paths and status vocabulary vary, the five NTRIP fields do not. Two Autel-specific habits worth adopting: verify RTK status after any Enterprise-app update before a billable mission (behaviour has shifted across versions), and when the smart controller shares a hotspot with other site devices, give the base's caster a static address so the NTRIP host field never chases DHCP. Beyond that, the universal rules govern — FIX before arming, correction age 1–2 s, two checkpoints after — and the aircraft badge stops mattering to the deliverable.

Further reading

The transport trade-offs behind the offline recipe — radio, NTRIP, and link paths — are compared in choosing a correction path; the universal base-coordinates question is settled in setting up without a known point.

One-line takeaway

Five NTRIP fields connect an EVO to any RTCM 3.x source — pair it with a self-contained absolute base and the platform's procurement independence extends all the way down to the correction layer.

Further reading (workflow neighbours)

The verification arithmetic behind the two-checkpoint habit is worked through in the GCP guide, and the frame bookkeeping for mixed-brand deliverables lives in ITRF2020 explained.

Frequently asked questions

Does the Autel EVO II RTK support custom NTRIP?

Yes — the Autel Enterprise app exposes standard NTRIP client fields (host, port, mountpoint, credentials) that accept any RTCM 3.x source, including a self-converging base.

Can an EVO fly RTK with no internet at the site?

Yes — join the controller to the base’s local Wi-Fi and point custom NTRIP at the base’s own caster. The whole correction path stays offline.

Does PPK work on Autel RTK aircraft?

Yes — the RTK models log raw observations; pair with base RINEX in standard post-processing tools for corrected geotags after the flight.

Can one base serve Autel and DJI aircraft together?

Yes — RTCM over NTRIP or radio is a broadcast; both ecosystems consume it simultaneously and land on the same absolute datum.

What accuracy should I expect?

With centimetre corrections and FIX discipline, the usual photogrammetric 2–5 cm horizontal band — verified with two checkpoints per mission like any other aircraft.