Device Playbook

Device‑specific notes for rovers and drones, including RTCM3 requirements and GGA output.

Device Playbook - GNSS & Drones Setup (RTK via NTRIP)


How RTK works on devices (quick)

  1. Your receiver opens an NTRIP connection to RTKdata.com (either built‑in client on the device or via a companion app/bridge).

  2. The receiver (or app) sends your approximate position (NMEA GGA) so the caster can localize you.

  3. RTKdata.com streams RTCM corrections (regional frame if you use AUTO).

  4. The receiver converges: Autonomous → RTK Float → RTK FIX (centimeter‑level).


Enter RTKdata.com connection settings (regional hostnames + IP fallback)

Use the nearest regional hostname where possible. If your device only accepts numbers or DNS is blocked, use the numeric IP. Keep ALL CAPS where noted.

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 website login)

  • Mountpoint (ALL CAPS): AUTO (recommended) — or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

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 website login)

  • Mountpoint (ALL CAPS): AUTO (recommended) — or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

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 website login)

  • Mountpoint (ALL CAPS): AUTO (recommended) — or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014


Common device workflows

A) Receiver has a built‑in NTRIP client (simplest)

  1. Network: bring the receiver online (Wi‑Fi, Ethernet, LTE/hotspot).

  2. NTRIP client: open the NTRIP/corrections menu on the device UI or web UI.

  3. Enter settings: regional host (or IP), Port 2101, username/password, mountpoint (ALL CAPS).

  4. GGA: enable Send NMEA GGA (often automatic in built‑in clients).

  5. Connect: confirm incoming RTCM and watch status go to RTK FIX.

B) Receiver uses a companion app / bridge (PC or mobile)

Typical examples: u‑center (Windows), Septentrio DataLink, SW Maps, EOS Tools Pro.

  1. Physical link: connect the receiver via USB/Serial/Bluetooth.

  2. App NTRIP profile: in the app, create an NTRIP connection with regional host/IP, Port 2101, credentials, mountpoint.

  3. GGA path:

    • Ensure the receiver outputs NMEA GGA @ 1 s on the same interface the app listens to (e.g., USB1/COM, or Bluetooth).

    • Many apps have a “Send NMEA GGA to caster” toggle — set it to ON.

  4. Bridge: start the connection; the app forwards GGA to RTKdata.com and streams RTCM back to the receiver.

  5. Verify: in the app or device UI, confirm RTK FIX.


Hardware best practices (faster, more reliable FIX)

  • Open sky: clear view of the sky; avoid trees/buildings to reduce multipath.

  • Baseline: shorter distance to the nearest reference generally yields faster, tighter FIX.

  • Antenna & mounting: use the recommended antenna for your receiver; set pole/antenna height correctly in your app/project.

  • Firmware: keep the receiver on a current, stable firmware version.

  • Power & cables: ensure solid power and quality data cables (USB/serial) to avoid intermittent drops.

  • Vertical reference: RTK heights are ellipsoidal; apply a geoid in GIS/photogrammetry (or on-rover if supported) for orthometric elevations.


Quick FIX check (field)

  1. Move outdoors; wait for satellites and a base to be selected.

  2. Confirm NTRIP connected and incoming RTCM.

  3. Status should progress to RTK FIX; note satellites and baseline distance.

  4. Log a test point and verify repeatability.

If you’re stuck on FLOAT, re‑check: regional host/IP, Port 2101, credentials, mountpoint = AUTO, GGA ON, and open sky.



Need a different device? Open a request with your model and firmware version, and we’ll add a guide.

Last updated