> 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/dji-d-rtk-3.md). # DJI D-RTK 3 / D-RTK 2 with Network RTK Corrections Run the DJI D-RTK 3 or D-RTK 2 alongside RTKdata NTRIP corrections. Custom Network RTK in DJI Pilot 2, port 2101, mountpoint AUTO, one source at a time. The **DJI D-RTK 3** and the older **D-RTK 2** are DJI's own mobile base stations. They set up over your site, compute their own position, and send corrections to the aircraft over the DJI radio link. RTKdata takes the other route: corrections arrive over the internet as an NTRIP stream, so no base has to be carried, levelled, or re-initialised. Two questions come up in almost every support case on this topic: 1. Can a D-RTK be run against a third-party NTRIP caster instead of acting as its own base? 2. What happens if the local base and the network stream are both active? {% hint style="warning" %} A DJI aircraft processes **one correction source at a time**: either the local D-RTK base over the radio link, or a network caster over NTRIP. The two cannot be blended, and running both does not add stability. Choose one per flight. {% endhint %} ## Requirements * **Aircraft:** a DJI aircraft with an RTK module. Documented in solved cases: Matrice 4 Enterprise, Matrice 300 / 350 RTK, Mavic 3E / 3T / 3M, Inspire 3, Agras T50 * **Base hardware (optional):** DJI D-RTK 3, D-RTK 3 AG, or D-RTK 2. Not required for the NTRIP workflow * **Controller and app:** DJI Enterprise controller running **DJI Pilot 2**, or the Agras controller running the **DJI Agras app** * **Internet:** Wi-Fi hotspot, 4G dongle, or built-in SIM on the controller. The aircraft itself does not connect to the internet * **Firmware:** aircraft, controller, and base module on the latest version * **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 %} ### Pick the correction path **Path A, aircraft over NTRIP (recommended).** The aircraft pulls corrections straight from RTKdata through the controller. The D-RTK base stays packed away and switched off. This is the path the steps below describe. **Path B, base as a relay.** A D-RTK 3 placed with a clear sky view can take NTRIP corrections and pass them to the aircraft over the radio link. It only helps in specific situations (see [When a local base, when Network RTK](#when-a-local-base-when-network-rtk)), it needs RTKdata feeding it, and the exact menu wording differs between app and firmware versions. If you go this route, configure the NTRIP fields listed below on whichever device holds the NTRIP client, and verify Fix on the aircraft before flying. {% endstep %} {% step %} ### Power on outdoors and wait for satellite lock Power on the aircraft outdoors under open sky and let it acquire satellites before touching the RTK settings. RTK will not initialise without a GNSS position, because the caster needs a valid GGA position to route corrections. Sixty seconds powered on outdoors is a reasonable minimum. If a D-RTK base is part of your setup, it needs the same clear sky view. {% endstep %} {% step %} ### Give the controller internet Connect the controller to a hotspot, dongle, or SIM. Confirm it works by loading a webpage in the controller's browser. If that fails, the hotspot dropped and nothing else matters. {% endstep %} {% step %} ### Open RTK settings * **DJI Pilot 2:** tap the **three-dot menu (...)** in camera view, open **RTK**, and toggle RTK on * **DJI Agras app:** open **Operation View** and tap the **RTK settings** {% endstep %} {% step %} ### Switch off the D-RTK search first On Agras aircraft, disable the **"D-RTK 2 Search"** toggle **before** entering anything else. With the toggle on, the aircraft keeps scanning for a DJI base in the background and that scanning fights the network connection. The failure pattern reported from the field: it works at first, gets flakier, then stops entirely across battery swaps. {% hint style="danger" %} Do **not** select **"D-RTK 2 Mobile Station"** when you are using an NTRIP service. The aircraft then waits for a DJI base that is not there. It will sit on a full satellite count and never reach Fix, or take an initial fix and then silently drop corrections. This is a common misconfiguration, and it fails quietly rather than with an error. {% endhint %} {% endstep %} {% step %} ### Select Custom Network RTK Under the RTK service type, select **Custom Network RTK**. That selection is what tells the app to open an NTRIP stream and to exchange GGA positions with the caster. {% 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 the website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended), alternatives `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 the website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended), alternatives `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 the website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended), alternatives `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} Use `AUTO` unless your project requires a specific reference frame, and note that mountpoint names are case sensitive, so they must be **ALL CAPS**. A local CRS name typed into the mountpoint field gets you **no corrections**. The port is **2101**, not 2102 and not 2103. The NTRIP username starts with `rtk` and is not the same as your website account password. {% endhint %} {% endstep %} {% step %} ### Connect and verify Fix Tap **Connect** and watch the RTK status: | Status | Colour | Meaning | | ---------------------- | ------ | ----------------------------------------------------------------- | | **SINGLE** | Red | No corrections arriving at all | | **FLOAT / Converging** | Yellow | Corrections arriving, position not yet locked to centimetre level | | **FIX** | Green | Centimetre-level accuracy active | Expect Float within 30 to 90 seconds and Fix shortly after under open sky. If the status screen shows a **correction age** of a few seconds, corrections are flowing. If it shows nothing or `---`, they are not getting through despite a Connected label. Confirm a green Fix on the ground before every launch, including after each battery swap. {% endstep %} {% endstepper %} ## One correction source at a time This is the behaviour behind most of the failures on this page. * **No blending.** The aircraft accepts corrections either from the local base over the radio link or from the network over NTRIP. There is no mode that combines them, and running both does not improve stability. * **Wrong source selected, silent failure.** With "D-RTK 2 Mobile Station" selected while an NTRIP service is in use, the aircraft holds satellites and never reaches Fix, because it is waiting for a DJI base that is not broadcasting. * **Background scanning conflicts.** The Agras "D-RTK 2 Search" toggle keeps hunting for a DJI base while Network RTK is running. The connection degrades over a session rather than failing outright. * **One credential set, one live connection.** Session logs from one account showed a rover and a drone connected on the same credentials kicking each other off every 5 to 6 seconds, so neither held a session long enough to fix. Once one device dropped out, the other held 100% Fix rate for the rest of the session. For two devices at once, add a second data stream. ## When a local base, when Network RTK **Network RTK (RTKdata over NTRIP) fits when:** * You are within roughly 30 to 50 km of a reference station. Baselines around 12 to 15 km delivered a first Fix in normal convergence time in several cases, and 80 km was still workable but slower to converge * You want the same reference frame on every visit. One operator saw up to 15 feet of shift between visits because a local base re-averaged its position after each battery change. A fixed network station removes that drift * Setup time matters. One customer's summary after switching: "Certainly much faster than my RTK base station" * You fly several sites a day and do not want to carry, mount, and re-initialise a base **A local D-RTK base earns its place when:** * You work in a genuine coverage gap. In one rural case the nearest stations were far enough out that Fix was hard to hold across the whole work area, while the same configuration reached 100% Fix rate elsewhere * Mobile data at the site is unreliable, since NTRIP needs a live link on the controller for the whole flight * The NTRIP connection is challenged for other reasons and a local radio link is more dependable that day **Combining the two the way that actually works:** use RTKdata to establish the precise position of your base first, with a rover connected to the network. You then have an accurately positioned local base you can run over the radio link on sites where the NTRIP link is not dependable. This is a sequence, not simultaneous operation. {% hint style="info" %} Working in a coverage gap regularly? Hosting a station is often the better fix. See [Host a Base Station](/support/host-a-base-station.md). {% endhint %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights. If your deliverable needs heights above mean sea level, apply a geoid model in your processing software. See [Understanding Heights](/get-started/understanding-heights.md). {% endhint %} ## Troubleshooting The Problem column quotes the wording used in real support cases. | Problem | Cause | Fix | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "29 satellites, no fix. Any ideas? Nothing else is using the licence." (AU, 04/2026) | RTK service type set to D-RTK 2 Mobile Station, so the aircraft waits for a DJI base that is not broadcasting | In RTK settings switch to **Custom Network RTK**, then enter host, port `2101`, mountpoint `AUTO`, and the dashboard credentials | | "controller was showing up to 29 RTK but would not give me a green light to start using it" (US, 04/2026) | "D-RTK 2 Search" enabled in the DJI Agras app | Disable **D-RTK 2 Search** first, then confirm Custom Network RTK is selected. Green Fix followed within 30 to 60 seconds outdoors | | "I didn't have AUTO in all caps. I did that and it turned green with only 23RTK." (US, 04/2026) | Mountpoint typed in lower case | Type `AUTO` in ALL CAPS, no spaces | | "On the controller it just says converging. I let it run for about five minutes but just says converging." (US, 07/2026) | Port entered as `2102`, plus restricted sky view in valley terrain | Correct the port to `2101`. Check the correction age field, move to the most open spot available, disconnect, wait 30 seconds, reconnect | | "Ok. When I change the port to 2101. It won't save." (US, 07/2026) | The controller refuses to save an edited profile when another field fails validation | Delete the NTRIP profile completely and create a new one, entering server, then port, then mountpoint, then credentials in that order | | "For some reason I'm not able to change the password in controller." (US, 07/2026) | Cached credentials in the app, and in that case the website account password had been changed instead of the RTK credential | Disconnect, clear the password field before typing, or delete and recreate the profile. Take the password from **RTK Credentials** in the dashboard, not the website account | | "I am getting an authentication error on the T8." (Caribbean, 06/2026) | No active service period on the account, so the credentials authorise nothing. Not a device or mountpoint issue | Confirm the subscription is active in the dashboard, then reconnect with the unchanged settings | | "Primarily before takeoff I had a good fix. But then on take off I lost RTK as I climb up 20 m. Getting the following message (Sudden RTK position data change)" (UK, 05/2026) | Multipath in a dense urban canyon. The apparent position jump on ascent trips a DJI safety warning and RTK is dropped | Hold Fix on the ground for 2 to 3 minutes before takeoff, move the launch point 20 to 30 m away from building faces, ascend slowly. The slower ascent kept the Fix on the customer's second attempt | | Rover and drone "were both connected simultaneously using the same credentials. The two devices were kicking each other off every 5 to 6 seconds." (AU, 03/2026) | One credential set carries one live connection | Run one device at a time, or add a second data stream in the dashboard | | "once I take up the drone to change batteries, I lose RTK connection" (Caribbean, 05/2026) | A battery swap resets the RTK module and the session starts over | Normal behaviour. Wait for satellite lock, reconnect, allow 30 to 60 seconds for Fix. Budget 60 to 90 seconds per swap | | Status reads Connected, but correction age shows nothing or `---` | Corrections are not actually arriving despite the connection label | Recheck host, port, and mountpoint. Disconnect, wait 30 seconds, reconnect to force a fresh session | | Connection fails only on one mobile network | Some carriers block DNS resolution on non-standard ports | Enter the regional IP address instead of the hostname, port `2101` | ## Tips * **Sequence matters.** Outdoors, satellite lock, then connect NTRIP. Connecting first sends a position of 0,0 and the caster cannot route corrections to that. * **Satellite count is not Fix.** Cases in this case archive repeatedly show 25 to 35 satellites with no Fix. High satellite counts rule out sky view, not configuration. * **Check the RTK screen, not just the badge.** Correction age and the Connected label together tell you whether the problem is the link or the environment. * **After firmware updates**, reopen RTK settings and confirm the service type is still Custom Network RTK. * **Distance still matters.** Convergence takes longer and Fix is less stable as the baseline grows. Check the [Coverage Map](https://rtkdata.com/coverage/) before committing to a site. ## Related Guides * [DJI Pilot 2 RTK Setup](/integration-hub/ntrip-clients-and-field-software/dji-pilot-pilot-2.md): the app-level NTRIP walkthrough that applies to every DJI Pilot 2 aircraft * [DJI Agras T70P / T100](/integration-hub/drones-and-uavs/dji-agras-t70p-t100.md): the current Agras generation on the D-RTK 3 AG module, same Custom Network RTK flow * [DJI Agras T50 / T40 / T25](/integration-hub/drones-and-uavs/dji-agras-t50-t40-t25.md): the previous Agras generation, including the D-RTK 2 Search toggle you have to switch off * [DJI RTK Troubleshooting](/support/dji-rtk-troubleshooting.md): what to do when the status stays on Converging or drops mid-mission * [Host a Base Station](/support/host-a-base-station.md): the option to close a coverage gap instead of carrying a base ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Surveying](https://rtkdata.com/surveying/) * [Agriculture](https://rtkdata.com/agriculture/) --- # 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/dji-d-rtk-3.md?ask=&goal= ``` `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.