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

DJI Matrice 300 / 350 RTK & M30T: Pilot 2 NTRIP

Connect DJI Matrice 300 RTK, Matrice 350 RTK and M30T to RTKdata NTRIP in DJI Pilot 2: Custom Network RTK, port 2101, AUTO mountpoint, fix troubleshooting.

The Matrice 300 RTK, Matrice 350 RTK and M30T are flown from DJI Pilot 2 on a DJI Enterprise controller. The NTRIP client sits inside Pilot 2, so the aircraft itself never connects to the internet: the controller does, and it passes corrections down the control link.

The Matrice 4 series uses the same NTRIP fields but a different Pilot 2 build and a different settings layout. If you fly an M4E or M4T, use the Matrice 4 Enterprise RTK guide instead.

Requirements

  • Aircraft: Matrice 300 RTK, Matrice 350 RTK or M30T with the built-in RTK module

  • Controller: DJI RC Plus, or the Smart Controller shipped with your aircraft

  • Software: DJI Pilot 2, updated to the current version

  • Firmware: Aircraft and controller on current firmware. Older firmware had problems initialising Network RTK

  • Internet: Phone hotspot, USB 4G dongle, or the controller's own data connection. The drone does not connect to the internet itself

  • RTKdata account: Active subscription with NTRIP credentials, one data stream per device that is connected at the same time

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

Step-by-step setup

1

Power on and link

Power on the aircraft and the controller and wait for the link to establish.

2

Connect the controller to the internet

Connect the controller to a phone hotspot, a USB 4G dongle, or its own data connection. Verify it works by loading a page in the controller's browser. If the browser cannot load anything, RTK will not connect either.

3

Go outdoors and wait for satellite lock

Take the aircraft outside into open sky and let it acquire satellites before you touch the RTK settings. RTK does not initialise indoors or without a GNSS lock. Leave the aircraft powered on and stationary for at least 60 seconds.

4

Open RTK settings

  • Tap the three-dot menu (...) in the camera view

  • Open the RTK section

On some app versions the RTK panel sits under a different settings tab. The fields below are the same either way.

5

Select Custom Network RTK

Set the RTK service type to Custom Network RTK.

Do not select D-RTK 2 Mobile Station. That mode waits for DJI's own base station hardware. With an NTRIP service it fails silently: the aircraft keeps tracking satellites and never reaches a fix. It is a common mistake, and it produces no error message.

6

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

  • 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

  • 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

Use AUTO unless your project requires a specific reference frame, and enter the mountpoint in ALL CAPS, since the name is case sensitive. A local CRS name in that field gets you no corrections. The username and password come from the RTK Credentials section of your dashboard, not from your website login. The NTRIP username starts with rtk.

7

Connect and verify

Tap Connect and watch the RTK status indicator:

Status
Colour
Meaning

SINGLE

Red

No corrections are arriving at all.

FLOAT

Yellow

Corrections are arriving, accuracy is still converging.

FIX

Green

Centimeter-level accuracy is active.

Under open sky, FIX is typically reached in 30 to 90 seconds.

Wait for a green FIX on the ground before you start a mapping mission, not just FLOAT. Images captured on FLOAT are geotagged at decimeter level, and mixing fixed and float images across a site produces exactly the kind of variance that shows up later against your ground control.

Two devices on one set of credentials

This is the most frequent cause of unexplained dropouts on these aircraft, and it looks nothing like a credential problem in the field.

Each data stream allows one active connection. If a rover, a base, or a second aircraft is connected with the same username at the same time, the two sessions knock each other off. In one reported case the session log showed a ground rover and an M300 connected simultaneously, disconnecting each other every few seconds. Neither device held a session long enough to fix. As soon as one dropped out, the aircraft held a stable connection and a 100% fix rate for the rest of the session.

What to do:

  • Run one device per data stream. Check that a rover, base, or second controller is not still connected in the background.

  • When flying with network RTK, a local base station does not need to be connected at all. RTKdata streams corrections straight to the aircraft.

  • If you genuinely need a rover and a drone online at the same time, add a second data stream from your account dashboard. Each stream comes with its own set of credentials.

DJI Terra: the base position in the processing report

DJI Terra reads the base station coordinates embedded in the RTCM stream and displays that physical location. It therefore always shows a real station somewhere, never a virtual point next to your site. A station that looks far away in the report is not evidence that corrections were poor.

The AUTO mountpoint routes on the position your aircraft reports in its GGA message. "Nearest" is not purely straight-line distance: station health, stream quality and availability at that moment are part of the selection, so the anchor station shown in Terra is not always the closest station on the map.

To judge the actual quality of a dataset, look at the data rather than the station name:

  • Inspect the MRK file next to your images. The RTK status flag per image is 50 for RTK fixed and 34 for float.

  • Compare the RMS values in Terra's processing report against any ground control you measured.

Vertical reference (heights)

RTK corrections deliver ellipsoidal heights (height above the WGS 84 ellipsoid), not orthometric heights (height above mean sea level). If your workflow requires orthometric heights, apply a geoid model in your post-processing software.

Troubleshooting

Problem
Cause
Fix

"For some reason I cannot get a fix from the M300 RTK at all. 29 satellites, no fix." Status indicator red.

A red indicator means no corrections are arriving. Either the service type is still D-RTK 2 Mobile Station, or the NTRIP session was never established. Satellite count is unrelated to this.

Three-dot menu in camera view, RTK settings: confirm Custom Network RTK, host, port 2101, mountpoint AUTO, and RTK credentials from the dashboard. Then toggle RTK off, wait 10 seconds, toggle it on again to force a fresh session.

"It was dropping the VRS connection all the time until we turned off wifi on the base so it could no longer get a fix."

Two devices on the same credentials. The session log showed a ground rover and the M300 connected at the same time, kicking each other off every few seconds.

One device per data stream. Disconnect the base or rover, or add a second data stream in the dashboard. With network RTK the local base does not need to be online.

"Worked for a while, now having trouble again. 27 satellites, still converging."

Satellite count does not decide the fix. Corrections must arrive and the receiver must resolve carrier phase ambiguities. Long baseline, partial sky obstruction or a stale session all prevent that.

Disconnect and reconnect the NTRIP session to force a fresh one. Check the distance to the nearest station: 30 to 40 km is comfortable, beyond roughly 50 km a stable fix becomes unreliable.

"I've got 50 satellites connected this morning and still getting up to 5 minute loss of signal. Sometimes only 10 seconds."

Brief interruptions on the controller's internet link. Satellite internet in particular hands over between satellites, and the Pilot 2 NTRIP client does not always re-establish the session by itself.

In the field: disconnect and reconnect in the RTK panel, which usually restores fix within 60 seconds. Longer term: update Pilot 2 and aircraft firmware, later versions improved NTRIP session recovery.

"Fail to Enable Network RTK"

Older aircraft and Pilot 2 firmware had problems initialising Network RTK.

Update aircraft and controller firmware and Pilot 2. Then toggle RTK off, wait 5 seconds, on again. If it persists, restart Pilot 2 completely.

Custom Network RTK is selected, but the server entry stays on a disconnected state and no corrections arrive.

Wrong credentials (website login instead of RTK credentials), wrong port, or a mobile carrier that blocks DNS resolution on non-standard ports.

Re-enter the RTK credentials from the dashboard, the username starts with rtk. Confirm port 2101. If DNS is the problem, enter the regional IP fallback from the tabs above instead of the hostname.

"DJI Terra places the base position of the RTK data from the M300 [...] 76 km away from the site, when there is a CORS station [...] only 35 km away."

Terra displays the physical station whose coordinates are embedded in the RTCM stream. Station selection follows your GGA position plus station health and availability, not straight-line distance alone.

Not a fault condition. Validate the dataset instead: check the MRK status flags (50 fixed, 34 float) and the RMS values in Terra's report against your ground control.

"I am processing only with RS2 base log PPK, not with RTK. Haven't been able to hold a fix long enough on the M300 to use RTK reliably."

Repeated session dropouts at a long baseline, in this case combined with the credential conflict above.

Work through the causes above first. If the fix still does not hold, PPK is a legitimate fallback: fly on GNSS, log raw data, and process against a public CORS station. Note that RTKdata does not provide downloadable base logs.

Tips

  • Fix on the ground, then launch. Skipping the FIX check is the most common source of inaccurate survey data on these aircraft.

  • Battery swap resets the RTK module. After every swap, allow 30 to 90 seconds on the ground for re-convergence before continuing the mission.

  • Keep firmware current. Both the Network RTK initialisation and the NTRIP session recovery were improved in later Pilot 2 and aircraft firmware versions.

  • Credentials persist. Pilot 2 remembers the last Custom Network RTK configuration, so you enter it once per controller.

  • With DroneDeploy: M300, M350 and Phantom 4 RTK are planned and flown in the DJI app, and that is where the RTKdata NTRIP credentials go. DroneDeploy processes the imagery afterwards, so the two do not compete.

  • Baseline distance matters. Corrections are interpolated across several reference stations, but beyond roughly 50 km convergence takes longer and the fix is less stable.

Related Guides

Related Industry Solutions

PreviousDJI Dock 3 / Matrice 4D
NextDJI D-RTK 3 / D-RTK 2

Last updated

Was this helpful?