> 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-matrice-400.md). # DJI Matrice 400 RTK Setup: Pilot 2 NTRIP & Zenmuse L3 Connect the DJI Matrice 400 to RTKdata NTRIP in DJI Pilot 2: Custom Network RTK, port 2101, AUTO, internet on the RC Plus 2 and the Zenmuse L3 RTB check. To set up RTK on the **DJI Matrice 400** with RTKdata NTRIP corrections, open **Camera View** in DJI Pilot 2 on the remote controller, tap **•••** and then the RTK icon, turn on **RTK Positioning** in the **Precise Positioning Setting** panel and select **Custom Network RTK** under **Select RTK Service Type**. In the profile, enter the RTKdata host for your region in **NTRIP Address** (`rtk.rtkdata.com` for North America, `eu.rtkdata.com` for Europe or `aus.rtkdata.com` for Australia), `2101` in **Port**, the username and password from *RTK Credentials* in **Account** and **Password**, and `AUTO` in **Mount Point**, then tap **Save**, restart the aircraft on the ground and wait until the status table shows **FIX**. The remote controller needs internet from a DJI Cellular Dongle 2 with a nano-SIM card or from Wi-Fi, because the remote controller connects to the RTKdata caster, not the aircraft. The path, the internet requirement and the **FIX** check follow the DJI Matrice 400 User Manual v2.0 (section 4.9, Aircraft RTK) and the DJI video *DJI Matrice 400 | First Use*, which shows the **Precise Positioning Setting** panel on the M400. The profile field names (**Name**, **NTRIP Address**, **Port**, **Account**, **Password**, **Mount Point**, **Edit**) are the ones DJI Pilot 2 shows on a DJI RC Plus 2 with a Matrice 4E, and a third-party guide shows the same fields for the Mavic 3 Enterprise series. DJI describes Custom Network RTK in the same words in the Matrice 400 and Matrice 4 manuals, but the field names on the M400 can differ slightly. This page names no aircraft, remote controller or DJI Pilot 2 versions: update the aircraft, the remote controller, DJI Pilot 2 and the Zenmuse L3 together to the current releases. {% hint style="warning" %} **Choose Custom Network RTK, not Network RTK.** In the **Select RTK Service Type** list, **Network RTK** sits directly above **Custom Network RTK**. According to the DJI Zenmuse L3 Operational White Paper, **Network RTK** is the M400's built-in China Mobile service. Your RTKdata account goes into **Custom Network RTK**. {% endhint %} These are the values you enter. The field names in bold are the DJI Pilot 2 profile fields as shown on the Matrice 4E. Choose the server closest to your work area; all three servers share the same base station network, see [NTRIP Server Settings](/get-started/network.md). {% tabs %} {% tab title="North America" %} * **Host (domain)** in **NTRIP Address**: `rtk.rtkdata.com` * **Host (IP fallback):** `13.56.117.10`, only if the hostname does not connect * **Port:** `2101` * **Username / Password** in **Account** and **Password**: From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login * **Mountpoint (ALL CAPS)** in **Mount Point**: `AUTO` (recommended), or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` {% endtab %} {% tab title="Europe" %} * **Host (domain)** in **NTRIP Address**: `eu.rtkdata.com` * **Host (IP fallback):** `3.73.41.96`, only if the hostname does not connect * **Port:** `2101` * **Username / Password** in **Account** and **Password**: From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login * **Mountpoint (ALL CAPS)** in **Mount Point**: `AUTO` (recommended), or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` {% endtab %} {% tab title="Australia" %} * **Host (domain)** in **NTRIP Address**: `aus.rtkdata.com` * **Host (IP fallback):** `54.206.56.130`, only if the hostname does not connect * **Port:** `2101` * **Username / Password** in **Account** and **Password**: From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login * **Mountpoint (ALL CAPS)** in **Mount Point**: `AUTO` (recommended), or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` {% endtab %} {% endtabs %} | Field | Value | | -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **RTK Positioning** | On | | **Select RTK Service Type** | **Custom Network RTK**. Not **Network RTK**, not **D-RTK Base Station**, not **NONE** | | **Name** | Your own profile for RTKdata, not a saved profile of another correction service | | **NTRIP Address**, North America | `rtk.rtkdata.com`, IP fallback `13.56.117.10` | | **NTRIP Address**, Europe | `eu.rtkdata.com`, IP fallback `3.73.41.96` | | **NTRIP Address**, Australia | `aus.rtkdata.com`, IP fallback `54.206.56.130` | | **Port** | `2101` | | **Account** | Username from *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). It starts with `rtk` and is not your website login | | **Password** | Password from *RTK Credentials*, not your website password. It is case sensitive | | **Mount Point** | `AUTO` in capitals (recommended), or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` | | **Maintain Positioning Accuracy Mode** | Check whether it is on. If it is, check the RTK status after any loss of the control link or the internet, see *What does Maintain Positioning Accuracy Mode do?* below | * Enter only the hostname in **NTRIP Address**, without `:2101`. The port has its own field. * Mountpoint names are case sensitive: `AUTO` in capitals. A local coordinate system name in **Mount Point** returns no corrections. * One set of credentials allows one connection at a time. A ground rover, a base or a second aircraft running at the same time needs its own data stream, see [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices). * The `AUTO` mountpoint chooses the reference station from the position the aircraft reports as NMEA GGA. The DJI Pilot 2 profile seen on the Matrice 4E has no GGA field, and DJI documents no GGA setting for the M400, so connect only once the aircraft has a satellite position, see [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). ## Requirements * **Aircraft:** DJI Matrice 400 with its built-in RTK module * **Remote controller:** DJI RC Plus 2 Enterprise, listed as DJI RC Plus 2 Enterprise Enhanced on the M400 spec page * **Software:** DJI Pilot 2 on the remote controller, updated to the current version * **Firmware:** aircraft, remote controller, DJI Pilot 2 and, if you fly it, the Zenmuse L3 updated together. The Zenmuse L3 release notes say that otherwise "usage will be affected" * **Internet on the remote controller:** a DJI Cellular Dongle 2 with a nano-SIM card mounted on the remote controller, or a Wi-Fi connection such as a phone hotspot. The M400 manual: "Keep the remote controller powered on and connected to the internet when using this function." * **SIM card for the dongle:** without PIN code, not from a virtual mobile network operator, and not an IoT SIM card. The M400 manual warns that an IoT SIM card seriously compromises the video transmission quality * **RTKdata account:** active RTK credentials (username starts with `rtk`), one data stream per device that is connected at the same time * **RTKdata coverage** at your site: check the [coverage map](/get-started/coverage-map.md) before you go out * **For the Zenmuse L3:** DJI Terra 5.3.0 or later for the point cloud reconstruction {% 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 %} ## How do you set up Custom Network RTK on the DJI Matrice 400 in DJI Pilot 2? Give the remote controller internet, wait outside until the aircraft has a satellite position, open **Camera View** > **•••** > RTK icon in DJI Pilot 2, turn on **RTK Positioning**, select **Custom Network RTK**, enter the RTKdata profile, tap **Save**, restart the aircraft on the ground and wait for **FIX**. {% stepper %} {% step %} ### Give the remote controller internet Mount the DJI Cellular Dongle 2 with a nano-SIM card on the remote controller, or connect the remote controller to Wi-Fi or a phone hotspot. Keep the remote controller switched on and online for as long as you use Custom Network RTK. {% endstep %} {% step %} ### Power on, link and wait for a satellite position 1. Power on the aircraft and the remote controller. The M400 manual: "Make sure that the remote controller is connected to the aircraft and the internet." 2. Take the aircraft outside under open sky and let it find its satellite position before Custom Network RTK connects. {% hint style="warning" %} **Position first, then connect.** `AUTO` picks the reference station from the aircraft's position. If Custom Network RTK connects before the aircraft has a satellite position, the caster cannot assign a station and no corrections arrive. In that case, reconnect once the aircraft has its position. {% endhint %} {% endstep %} {% step %} ### Open Precise Positioning Setting In DJI Pilot 2, open **Camera View**, tap **•••** at the top right and select the RTK icon in the toolbar on the right. The panel **Precise Positioning Setting** opens. {% endstep %} {% step %} ### Turn on RTK Positioning Turn on **RTK Positioning**. The note under the switch says: "When RTK is enabled after aircraft takes off, make sure aircraft is hovering until RTK is fixed." Below it is the switch **Maintain Positioning Accuracy Mode**, see *What does Maintain Positioning Accuracy Mode do?* below. {% endstep %} {% step %} ### Select Custom Network RTK Under **Select RTK Service Type**, select **Custom Network RTK**. The list also shows **NONE**, **D-RTK Base Station** and **Network RTK**. {% hint style="warning" %} **Network RTK is not RTKdata.** **Network RTK** sits directly above **Custom Network RTK**. The DJI Zenmuse L3 Operational White Paper describes it as the M400's built-in China Mobile "Network RTK". Always select **Custom Network RTK** for RTKdata. {% endhint %} {% hint style="warning" %} **Do not select D-RTK Base Station.** This service type waits for corrections from DJI base station hardware. With RTKdata, the aircraft then receives no corrections and does not reach **FIX**. {% endhint %} {% endstep %} {% step %} ### Enter the RTKdata profile Fill in the profile with the values from the tabs above: 1. **Name**: your own profile for RTKdata. To change a saved profile, tap **Edit**. 2. **NTRIP Address**: the host for your region, for example `eu.rtkdata.com` 3. **Port**: `2101` 4. **Account** and **Password**: from *RTK Credentials* 5. **Mount Point**: `AUTO` 6. Tap **Save**. These field names are the ones DJI Pilot 2 shows on the Matrice 4E; on the M400 they can differ slightly. **Save** is named in the M400 manual. {% endstep %} {% step %} ### Restart the aircraft on the ground {% hint style="warning" %} After you switch the service type, the panel shows **Restart aircraft after switching RTK services**. Once the profile is saved, power the aircraft off and on again while it is on the ground, before takeoff. Then open **Precise Positioning Setting** again and check that **Custom Network RTK** and your RTKdata profile are still selected. {% endhint %} {% endstep %} {% step %} ### Wait for FIX Stay under open sky and wait until the status table in **Precise Positioning Setting** shows **FIX** for the aircraft's positioning. How to read the status is described in *How do you know RTKdata corrections are really arriving on the M400?* below. {% endstep %} {% endstepper %} ## How does the Matrice 400 get internet for RTK corrections? The Matrice 400 gets RTKdata corrections through its remote controller: DJI Pilot 2 on the DJI RC Plus 2 Enterprise connects to the RTKdata caster over a DJI Cellular Dongle 2 with a nano-SIM card or over Wi-Fi, and passes the corrections to the aircraft over the control link. | Internet source | For Custom Network RTK | Notes | | ---------------------------------------------------------------------------- | ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DJI Cellular Dongle 2 with a nano-SIM card, mounted on the remote controller | Yes, named in the M400 manual | SIM without PIN code, not from a virtual mobile network operator, not an IoT SIM card | | Wi-Fi on the remote controller, for example a phone hotspot | Yes, named in the M400 manual | The remote controller has to stay online for the whole flight | | DJI Cellular Dongle 2 mounted on the aircraft | Not documented as a source for Custom Network RTK | The M400 manual describes it for **Enhanced Transmission**. For Custom Network RTK, DJI names only the remote controller, and DJI's M400 support FAQ says that the network RTK services are bound to the remote controller | * If the SIM card has a PIN code, remove it in a smartphone first. The M400 manual says that the dongle otherwise fails to connect to the internet. * The M400 manual also says that a SIM card from a virtual mobile network operator "may lead to an inability to connect to the Internet". * On long flights, the corrections depend on the mobile network at the remote controller and on the link to the aircraft. The Zenmuse L3 manual advises setting up your own RTK base station for post-processing "When the mobile network or remote controller video transmission signal is weak". {% hint style="warning" %} **Dual control: set up RTK on remote controller A.** The M400 manual: "The pilot of remote controller B cannot adjust settings for network RTK or custom network RTK." Enter the RTKdata profile on remote controller A. DJI does not say which controller needs the internet in this mode; since remote controller A holds the RTK settings, give remote controller A the internet connection as well. {% endhint %} {% hint style="danger" %} **Restart only on the ground.** The M400 manual: "In a 4G-only transmission scenario, restarting the remote controller or DJI Pilot 2 will result in failsafe RTH." Every restart on this page, of the aircraft, the remote controller or DJI Pilot 2, and every time you turn RTK off and on, is meant for the ground before takeoff. {% endhint %} ## Which RTK service type do you choose on the M400: Network RTK, Custom Network RTK or D-RTK Base Station? Choose **Custom Network RTK** on the M400 for RTKdata: it is the service type for your own NTRIP account, while **Network RTK** is DJI's built-in China Mobile service and **D-RTK Base Station** expects a DJI base station. | **Select RTK Service Type** option | What it is | For RTKdata | | ---------------------------------- | ------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | **NONE** | No RTK service selected | Do not use | | **D-RTK Base Station** | Corrections from DJI base station hardware | Do not use with RTKdata. For a DJI base, see [DJI D-RTK 3 / D-RTK 2](/integration-hub/drones-and-uavs/dji-d-rtk-3.md) | | **Network RTK** | The M400's built-in China Mobile service, according to the DJI Zenmuse L3 Operational White Paper | Do not use | | **Custom Network RTK** | Your own NTRIP account with address, port, account, password and mount point | **Select this** | After a switch of the service type, save the profile and restart the aircraft on the ground, as the panel note **Restart aircraft after switching RTK services** says. Choose the service type before takeoff. ## How do you know RTKdata corrections are really arriving on the M400? RTKdata corrections are arriving on the M400 when the status table in **Precise Positioning Setting** shows **FIX** for the aircraft's positioning and the RTK icon turns white; the line **Receiving RTK signal. Ensure network connection is stable** is not proof on its own. | Where | What to look for | Meaning | | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | RTK icon in the GNSS positioning status of DJI Pilot 2 | Gray | The RTK service is not enabled (M400 manual) | | RTK icon in the GNSS positioning status of DJI Pilot 2 | White | The RTK data is converged (M400 manual) | | Status table, **Aircraft** column, **Positioning:** | **FIX** | The M400 manual: the aircraft "has obtained and used differential data from Network RTK" | | **Aircraft RTK Status:** | **Connected** | Label seen on the Matrice 4E. Not proof of a fix on its own | | Status table, **Custom Network RTK** column | **Latitude:**, **Longitude:**, **Ellipsoidal Height** and the satellite count | Position and satellites of the reference station that sends the corrections (labels seen on the Matrice 4E) | | Panel line **Receiving RTK signal. Ensure network connection is stable** | Shown | Not tied to a working connection: DJI's M400 video shows it with **Network RTK** selected, a Matrice 4E video with **Custom Network RTK** | * With `AUTO`, the **Custom Network RTK** column most likely shows the RTKdata station assigned to your position. You can use it to check the distance between the station and your site. * In photo metadata, the M400 manual lists the field `RtkFlag`: `50` is a fixed solution, `32` to `49` a floating solution and `16` single point positioning. The manual does not say which payloads write it. ### What does Maintain Positioning Accuracy Mode do? **Maintain Positioning Accuracy Mode** keeps the RTK status for up to 10 minutes after an RTK module communication error, with decreasing accuracy. The text in the panel: "In case of an RTK module communication error, the aircraft will automatically maintain the current RTK status with gradually decreasing accuracy. The aircraft will exit RTK if the connection is not re-established within 10 minutes." * Check whether the switch is on in **Precise Positioning Setting**. * After any loss of the control link or the internet, open **Precise Positioning Setting** and check the status table before you continue mapping. * For Zenmuse L3 flights, also check the **RTB** status in the task quality report after the flight. {% hint style="info" %} **Correction format.** RTKdata streams RTCM 3.2 with MSM4 messages (1074, 1084, 1094, 1114, 1124, 1134) and 1005. DJI publishes no list of correction input formats for the M400, and the DJI Pilot 2 profile seen on the Matrice 4E has no format field. {% endhint %} ## How does the Zenmuse L3 use RTK on the Matrice 400? The Zenmuse L3 uses the RTK solution of the Matrice 400 and has no NTRIP settings of its own: set up Custom Network RTK with your RTKdata account on the aircraft as above, check for **FIX** before you record, and the L3 stores the base station stream as a `.RTB` file for processing in DJI Terra 5.3.0 or later. ### Before and after an L3 flight 1. Before you record, check in **Camera View** > **•••** > RTK icon that the RTK status is **FIX**. The Zenmuse L3 manual makes this part of the preparation. 2. When the mobile network or the remote controller video transmission signal is weak, set up your own RTK base station as well; the L3 manual recommends it for post-processing. A third-party base station must support at least three GNSS systems. 3. After the flight, open the task quality report with **View Now** and check **RTK**, **IMU** (the POS status) and **RTB**. 4. Wait at least 60 seconds after recording before you power off or remove the memory card. The L3 manual: "Wait at least 60 seconds to avoid reduced accuracy or data corruption." 5. Copy the DCIM folder to your computer, keep a backup and check that the `.RTB` file exists and is not 0 KB. The L3 manual describes the RTB file as "Base station RTCM data". If it is missing or empty, network RTK was unstable or off during the flight, and the DJI white paper says the reconstruction "is likely to fail". 6. Process the data in DJI Terra 5.3.0 or later. When Terra calculates the POS from the recorded data, it uses the `.RTB` file as the base station file, and the DJI white paper requires network RTK that is "stable and fixed throughout the entire flight path". ### If the RTB file is not usable: Local PPK * In DJI Terra, create a task with **New Task** > **LiDAR Point Cloud**, import the L3 data, select **Local PPK** and import your own base station data with **Add Base Station File**. The L3 manual lists D-RTK 3 `.DAT` files, OEM4 and OEM6, RINEX v2.1x and v3.0x, and RTCM v3.0 to v3.3 with MSM3 to MSM7. * The base station has to be less than 15 km from the aircraft. The L3 manual: "Otherwise, the calculation may fail." * Back up the DCIM folder before you test PPK: DJI Terra replaces the network RTK base station file during the PPK calculation. * RTKdata does not offer base station observation files as a self-service download (for a specific need, contact [support](/support/support.md)), so Local PPK normally uses your own base station. * The DJI white paper points to cloud PPK when the RTB file is abnormal, but the DJI Terra release notes list cloud PPK processing "for Chinese mainland only". Elsewhere, use Local PPK with your own base station or fly the mission again. ### Other payloads on the M400 * Do not use the L3 dedicated mounting bracket for other payloads. The L3 known issue list: "Abnormalities occur when using the L3 dedicated mounting bracket to install H30 series, P1, or L2." Use the original M400 aircraft bracket for these payloads, and update them first by SD card, as the M400 release notes describe. * This page covers DJI payloads. For a third-party LiDAR payload, follow the scanner's own RTKdata guide in [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md). ## Which coordinate system should you use with AUTO for M400 and Zenmuse L3 data? Use the regional datum that the RTKdata `AUTO` mountpoint delivers at your position, for example NAD83(2011) in the USA or ETRS89 in Europe, and declare it in the DJI Terra project, because DJI Terra outputs WGS84 by default. * `AUTO` delivers your region's datum, chosen from the aircraft's GGA position: for example NAD83(2011), epoch 2010.0, in the USA; NAD83(CSRS)v7, epoch 2010.0, in Canada; ETRS89 (realization ETRF2000), epoch 2010.0, in Europe; and GDA2020, epoch 2020.0, in Australia. For regions not listed, `AUTO` falls back to WGS84(G2139) at the mid-year epoch. The datum for every region is listed in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md). * `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver ITRF2020 and ITRF2014 at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) at the mid-year epoch. * Set the ground control points, the aircraft output and the DJI Terra project to the same system **before** you process, see [Matching the Frame in Your Processing Software](/get-started/coordinate-systems-and-datums.md#matching-the-frame-in-your-processing-software). * DJI does not document which datum Terra assumes for the base station coordinates in the `.RTB` file. Check the first project against ground control. * Heights are ellipsoidal. Apply a geoid model in your processing software if you need orthometric heights, see [Understanding Heights](/get-started/understanding-heights.md). * A consistent offset of 50 cm to 1 m against ground control usually means a datum mismatch, see [Why Your Coordinates May Be Offset](/get-started/coordinate-systems-and-datums.md#why-your-coordinates-may-be-offset). ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | No **FIX**, **Network RTK** is selected | **Network RTK** is the M400's built-in China Mobile service, not your NTRIP account | Select **Custom Network RTK**, enter the RTKdata profile, tap **Save** and restart the aircraft on the ground | | No corrections, **D-RTK Base Station** is selected | The aircraft waits for DJI base station hardware | Switch to **Custom Network RTK**, save the RTKdata profile and restart the aircraft on the ground | | **Custom Network RTK** selected, still no corrections | Service type switched without restarting the aircraft (**Restart aircraft after switching RTK services**) | Power the aircraft off and on while it is on the ground, then check the status table | | RTK settings cannot be changed in dual control | Setup attempted on remote controller B, which "cannot adjust settings for network RTK or custom network RTK" | Set up Custom Network RTK on remote controller A and give it the internet connection | | Profile correct, but no connection | Remote controller offline: SIM with PIN code, SIM from a virtual mobile network operator, dongle only on the aircraft, or Wi-Fi lost | Remove the PIN in a smartphone, use a SIM from a mobile network operator, mount the dongle on the remote controller or use Wi-Fi, and keep the remote controller online | | Login works, but no corrections, right after power on or indoors | Connected before the aircraft had a satellite position, so `AUTO` cannot assign a station | Go outside, wait for the satellite position, then reconnect | | Login rejected or no corrections | Website login used instead of the RTK credentials, or mountpoint typed in lowercase | Use the username (starts with `rtk`) and password from *RTK Credentials* and `AUTO` in capitals | | Corrections drop every few seconds | Another device, such as a ground rover or a base, uses the same credentials at the same time | One device per data stream, or add a second data stream, see [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices) | | Hostname entered, internet works, no connection | The mobile carrier blocks DNS resolution on non-standard ports, or the hostname does not connect | Enter the IP fallback for your region, see *If the hostname does not connect* below | | **Receiving RTK signal. Ensure network connection is stable** shown, no **FIX** | The line appears regardless of a working connection | Check the status table, the service type, the profile and the internet on the remote controller | | Mapping continues after a link loss, accuracy drops | **Maintain Positioning Accuracy Mode** keeps the RTK status for up to 10 minutes with decreasing accuracy | Check the status table after the loss, check the L3 task quality report and fly the affected segments again | | `.RTB` file missing or 0 KB after a Zenmuse L3 flight | Network RTK unstable or off during the flight | Use Local PPK with your own base station less than 15 km away, or fly again. Next time, check **FIX** before recording and the **RTB** status after the flight | | Point cloud or orthophoto offset against ground control | Datum mismatch: `AUTO` delivers the regional datum, DJI Terra outputs WGS84 by default | Set ground control, aircraft output and the Terra project to the same system | | Abnormal behaviour with H30, P1 or L2 after flying the L3 | L3 dedicated mounting bracket used for another payload | Use the original M400 aircraft bracket | ### If the hostname does not connect The M400 manual describes the NTRIP host stored in the photo metadata as "IP address or domain name of Network RTK". Keep the hostname for your region whenever it connects. Use the IP fallback only if the connection fails with the hostname although internet, credentials and mountpoint are right: enter the IP for your region in **NTRIP Address** and keep port, credentials and mountpoint. | Region | Hostname (preferred) | IP fallback for **NTRIP Address** | **Port** | **Mount Point** | | ------------- | -------------------- | --------------------------------- | -------- | --------------- | | North America | `rtk.rtkdata.com` | `13.56.117.10` | `2101` | `AUTO` | | Europe | `eu.rtkdata.com` | `3.73.41.96` | `2101` | `AUTO` | | Australia | `aus.rtkdata.com` | `54.206.56.130` | `2101` | `AUTO` | For connection problems that are not specific to DJI, see [Common Connection Issues](/support/common-connection-issues.md). ## Tips * **FIX on the ground, then launch.** The panel note says: "When RTK is enabled after aircraft takes off, make sure aircraft is hovering until RTK is fixed." * **Choose the service type before takeoff.** A switch needs a restart of the aircraft, and restarts belong on the ground. * **Update everything together.** Aircraft, remote controller, DJI Pilot 2 and Zenmuse L3 on compatible releases, and DJI Terra 5.3.0 or later for L3 data. * **Back up before PPK.** Keep a copy of the DCIM folder, because Terra replaces the network RTK base station file during the PPK calculation. * **Plan a base for long flights.** On long corridor or long range missions, record your own base station data for Local PPK in case the mobile network or the link to the aircraft weakens. ## Frequently asked questions ### Does the Zenmuse L3 need its own NTRIP login on the Matrice 400? No. The Zenmuse L3 has no NTRIP settings of its own and uses the RTK solution of the Matrice 400, so the RTKdata profile goes into **Custom Network RTK** in DJI Pilot 2 on the remote controller. Check for **FIX** before you record; the L3 then stores the base station stream as a `.RTB` file. ### Why does the M400 show Receiving RTK signal but no FIX? Because **Receiving RTK signal. Ensure network connection is stable** is not proof that corrections arrive: DJI's M400 video shows the line with **Network RTK** selected. Check that **Custom Network RTK** is selected and the aircraft was restarted after the switch, that the remote controller is online, that the aircraft had a satellite position before connecting, and that the RTKdata credentials from *RTK Credentials* and `AUTO` are right. Corrections arrive when the status table shows **FIX**. ### Which correction format does RTKdata send to the Matrice 400? RTKdata sends RTCM 3.2 with MSM4 messages (1074, 1084, 1094, 1114, 1124, 1134) and 1005. DJI publishes no list of correction input formats for the M400, and the DJI Pilot 2 profile seen on the Matrice 4E has no format field to set. ### Can I use the same RTKdata login on the M400 and a ground rover at the same time? No. One set of RTKdata credentials allows one connection at a time; if a rover and the M400 use the same login at the same time, the sessions disconnect each other. Add a second data stream for the second device, see [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices). ### What if the .RTB file is missing or 0 KB after a Zenmuse L3 flight? Then network RTK was unstable or off during the flight, and DJI says the reconstruction is likely to fail. The DJI Terra release notes list cloud PPK "for Chinese mainland only", so elsewhere the way out is Local PPK in DJI Terra with your own base station data, less than 15 km from the site, or a new flight; RTKdata does not provide base station files for download. Next time, check **FIX** before recording, wait 60 seconds after recording and check the **RTB** status in the task quality report. ## Quick reference 1. Internet on the remote controller: DJI Cellular Dongle 2 with a nano-SIM card (no PIN, no virtual operator, no IoT SIM) or Wi-Fi. In dual control, use remote controller A. 2. Power on, link, go outside and wait for the aircraft's satellite position. 3. DJI Pilot 2: **Camera View** > **•••** > RTK icon > **Precise Positioning Setting**, turn on **RTK Positioning**. 4. **Select RTK Service Type**: **Custom Network RTK** (not **Network RTK**, not **D-RTK Base Station**). 5. **NTRIP Address** `rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com` (IP fallback `13.56.117.10`, `3.73.41.96` or `54.206.56.130`), **Port** `2101`, **Account** and **Password** from *RTK Credentials*, **Mount Point** `AUTO`, **Save**, then restart the aircraft on the ground. 6. Wait for **FIX** in the status table and a white RTK icon. 7. Zenmuse L3: **FIX** before recording, 60 seconds after recording, `.RTB` present and not 0 KB, DJI Terra 5.3.0 or later, datum declared in the Terra project. ## Related Guides * [NTRIP Server Settings](/get-started/network.md): the regional hosts, IP fallbacks, port and mountpoints in one reference * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why the caster needs your position before it sends corrections * [DJI Pilot 2 RTK Setup](/integration-hub/ntrip-clients-and-field-software/dji-pilot-pilot-2.md): general DJI Pilot 2 notes on GNSS lock and GGA; its menu path is written for the M300, M350 and Mavic 3E, on the M400 use the path on this page * [DJI Matrice 4 Enterprise RTK](/integration-hub/drones-and-uavs/dji-matrice-4-enterprise-rtk.md): RTKdata setup for the Matrice 4E and 4T in DJI Pilot 2 * [DJI Matrice 300 / 350 RTK and M30T](/integration-hub/drones-and-uavs/dji-matrice-300-350-m30t.md): RTKdata setup for the Matrice 300 RTK, Matrice 350 RTK and M30T * [DJI D-RTK 3 / D-RTK 2](/integration-hub/drones-and-uavs/dji-d-rtk-3.md): when to use a DJI base station and when network RTK, one correction source at a time * [DJI RTK Troubleshooting](/support/dji-rtk-troubleshooting.md): the decision tree for DJI drones that do not reach FIX * [Common Connection Issues](/support/common-connection-issues.md): what to check when corrections do not arrive * [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which datum `AUTO` and its variants deliver in each region * [Understanding Heights](/get-started/understanding-heights.md): ellipsoidal and orthometric heights, and how to apply a geoid * [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices): where to find your RTK credentials and how many devices can connect at once * [Coverage Map](/get-started/coverage-map.md): check the station coverage at your site before you fly * [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md): RTKdata guides for SLAM scanners and LiDAR payloads * [Georeferencing SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): datum and height rules for georeferenced point clouds * [Drones & UAVs](/integration-hub/drones-and-uavs.md): all drone platforms with an RTKdata setup guide ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) * [Utilities](https://rtkdata.com/utilities/) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-matrice-400.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.