Troubleshooting

The fastest fixes for “connected but no corrections,” “no GGA,” datum/unit offsets, DJI Terra baseline warnings, and more.

Troubleshooting - Get to RTK: FIX Fast

When RTK won’t settle, 90% of cases fall into a few patterns. Work through the checks below in order. They’re distilled from recent tickets and logs and should get you to FIX quickly.

1) “Waiting for base” / No corrections flowing

Symptoms

  • Your client logs in “Successful” but shows 0 GGA and no station distance; no RTCM arrives.

  • DJI controller connects but never switches to RTK: FIX.

Root cause The caster isn’t receiving your NMEA‑GGA (your approximate position), so it can’t localize you to a nearby base.

Fix — do all of the following

  1. Go outdoors with open sky and make sure the rover has a standalone GNSS position before connecting. Many apps won’t emit GGA indoors.

  2. Send GGA to the caster (ON).

    • Lefebure (Android): Pair Bluetooth to your GNSS, set Receiver Connection to that Bluetooth device, enable Send GGA to NTRIP Caster on connect and every 5–10 s.

    • DJI Pilot 2 (M3E): Use Custom Network RTK, then tap Start Transmitting outdoors. Pilot 2 pushes GGA automatically once the aircraft has a fix; there’s no separate GGA toggle.

  3. Use the right mountpoint (ALL CAPS): AUTO (or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014). Any other text will return no data.

Confirm it worked: In your client or in logs you should see GGA lines (e.g., $GNGGA... ,4,...) and a non‑zero station distance. That indicates the caster localized you and corrections are active.

2) Logs show “Successful” but the receiver stays standalone/float

Symptoms

  • GGA is sent, you see a base and distance, but solution quality stays 1 (autonomous) and RTK Fix Rate = 0%.

Root cause The rover is not parsing the incoming correction format (most often it’s set to CMR/CMR+ instead of RTCM3).

Fix

  • In your rover/app, set Correction format = RTCM3 (Trimble: RTCM3Net/RTCM RTK). Reconnect and verify the solution flips to RTK: FIX.

3) “Invalid password” / can’t log in

Symptoms

  • Caster returns Invalid password immediately after connect.

Fix

  • Copy your credentials from the RTKdata.com dashboard; beware of hidden spaces or device “smart quotes.” Try once more. (Many recent failures were just a mistyped password.)

4) Steady ~4 ft horizontal offset (two networks / old control)

Symptoms

  • Results are consistently off by ~4 ft, not random scatter.

Root causes & fixes

  • Feet unit mismatch in your collector (US survey foot vs. international foot) in State Plane → switch to US survey foot variant of the zone used to set the control; re‑occupy.

  • Datum/epoch mismatch between networks (e.g., one stream in NAD83(2011), the other in ITRF/WGS84) → pick the matching mountpoint (e.g., AUTO regional frame vs. AUTO_WGS84) and ensure the project CRS matches the control.

5) DJI Terra: “Baseline exceeds limit by 15 km”

What it really means Terra’s warning is often about post‑processing base selection (PPK) rather than your live RTK session. We’ve seen clean RTK FIX at 0.7–21 km baselines in the logs while Terra later picked a distant CORS for PPK and flagged a limit.

Rule of thumb Horizontal accuracy degrades ~1 cm per 10 km of baseline; even at ~35 km, RTK fixes are achievable in good sky, with small accuracy penalties.

Fix

  • Reprocess in Terra using the same base that served your flight or upload the corresponding RINEX from our network rather than letting Terra auto‑pick a far base.

6) “We’re outside your coverage” (edge regions)

You can still test: expect float ~20–30 cm (often good enough for many UAS tasks) and confirm on your sites with the free trial, which ends automatically.

7) Mountpoints — only these four (case‑sensitive)

Use exactly one of:

AUTO
AUTO_WGS84
AUTO_ITRF2020
AUTO_ITRF2014

Anything else will stream nothing. AUTO chooses the correct regional frame (e.g., NAD83(2011) in the US, ETRS89 in Europe, GDA2020 in Australia). Heights are ellipsoidal; apply your local geoid in GIS/photogrammetry for orthometric elevations.

8) One‑minute health check (enter exactly)

Regional hostnames + IP fallback (Port 2101):

North America  Host: rtk.rtkdata.com   (IP: 13.56.117.10)
Europe         Host: eu.rtkdata.com    (IP: 3.73.41.96)
Australia      Host: aus.rtkdata.com   (IP: 54.206.56.130)
Port           2101
Mountpoint     AUTO   (ALL CAPS)
GGA to caster  ON
User/Pass      Your RTKdata credentials

Still stuck? Email [email protected] with a GGA line and a screenshot of your NTRIP settings.

PreviousDJI Pilot / Pilot 2NextSupport

Last updated