# NTRIP RTK Setup Guides Connect your GNSS rover, drone, or app to RTKdata.com for centimeter-level RTK via NTRIP. Regional hosts, IP fallbacks, simple mountpoints, and a free 30-day trial. Connect your GNSS rover, drone, or app to RTKdata.com for sub-2 cm RTK via NTRIP. Regional hosts, IP fallbacks, and four simple mountpoints. Free 30-day trial. ![RTKdata Logo](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2FcYvjtTEPqfWQ8DXdquYR%2FLogo%20png.png?alt=media\&token=f56e5830-7d35-4450-9838-de9d57eaa33b) ## RTKdata.com - RTK Corrections Setup, NTRIP Hosts & Mountpoints ## Welcome to RTKdata.com Docs Get from signup to **RTK: FIX** in minutes. These docs show you how to connect your rover or app to **RTKdata.com**, verify accuracy, and stay productive in the field. **Quick Start** · **Network & Mountpoints** · **Integration Hub** · **Start Free Trial** *** ### What is RTKdata.com? **RTKdata.com** provides **network RTK corrections** for GNSS/GPS receivers via the standard **NTRIP** protocol. Use your existing hardware and field apps to stream **real‑time RTCM** corrections and achieve **centimeter‑level** positioning. **Who uses RTKdata.com?** Survey & GIS teams · UAV mapping & photogrammetry · Construction & utilities · Agriculture · Research *** ### How it works (60‑second overview) 1. Your app or rover opens an **NTRIP** connection to RTKdata.com. 2. It sends its **approximate position (NMEA GGA)** so the service can localize you. 3. RTKdata.com streams **RTCM** corrections matched to your region/frame. 4. Your receiver converges: **Autonomous → RTK Float → RTK FIX**. *** ### Why RTKdata.com? * **Fast, precise**: real‑time RTK with typical **centimeter‑level** accuracy in open sky. * **Works with your tools**: standard **NTRIP**; compatible with popular apps and receivers. * **Simple setup**: one page of parameters for all devices; clear device/app guides. * **Global reach**: regional endpoints and a live coverage view to plan field work. * **Enterprise ready**: guidance for deployment, security/connectivity, and monitoring. *** ### Start here * [**Quick Start**](https://docs.rtkdata.com/get-started/quick-start) - four steps from account to **RTK: FIX**. * [**Network**](https://docs.rtkdata.com/get-started/network) - (Hosts/IPs & Mountpoints) * [**Integration Hub**](https://docs.rtkdata.com/integration-hub) - step‑by‑step setup for **Apps** and **Devices** * [**Coverage**](https://docs.rtkdata.com/get-started/coverage-map) - check availability by region and run an outdoor FIX test. Need credentials? [**Start 30‑day Free Trial**](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) - auto‑ends, no surprises. *** ### Concepts you'll see referenced * **NTRIP & GGA** - why the rover must send **NMEA GGA** to get the right corrections. * **Baseline & time‑to‑FIX** - distance to the nearest reference affects convergence. * **Mountpoints** - use **`AUTO`** for regional frames; fixed global frames available if required. * **Vertical reference** - RTK heights are **ellipsoidal**; apply a **geoid** in GIS/photogrammetry (or on the rover if supported) for **orthometric** elevations. Read more in [**NTRIP & GGA essentials**](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). *** ### Troubleshooting & support * **No corrections / stuck on FLOAT?** Start at [**Troubleshooting**](https://docs.rtkdata.com/support/troubleshooting-and-faq) * **Still blocked?** Open a ticket and include screenshots + app/device details # RTK Quick Start Guide: Get RTK FIX in 5 Minutes Set up RTK corrections in 5 minutes. Create your account, get NTRIP credentials, enter connection settings, and verify RTK FIX. Free 30-day trial included Get from signup to **RTK FIX** in four steps. Total time: about 5 minutes. *** ## Step 1: Create Your Account Sign up at [rtkdata.com](https://rtkdata.com/try-rtk-corrections-free-for-30-days/). Every new account includes a **free 30-day trial** with full access to the correction service. No credit card required, and the trial ends automatically -- no surprise charges. ## Step 2: Get Your NTRIP Credentials 1. Log in at [rtkdata.com/my-account](https://rtkdata.com/my-account/). 2. Go to the **RTK Credentials** tab. 3. Copy your **Username** (starts with `rtk`) and **Password**. > **Important:** These are separate from your website login. Your email and website password will **not** work in your GNSS device. See [Account & Credentials](/get-started/account-and-credentials) for details. ## Step 3: Enter Connection Settings Open the NTRIP settings on your receiver, drone, or field app, and enter these values: | Setting | Value | | -------------- | --------------------------------------------------------------------------------------------- | | **Host** | `eu.rtkdata.com` (Europe) / `rtk.rtkdata.com` (North America) / `aus.rtkdata.com` (Australia) | | **Port** | `2101` | | **Mountpoint** | `AUTO` (ALL CAPS, case-sensitive) | | **Username** | Your NTRIP username from the dashboard | | **Password** | Your NTRIP password from the dashboard | Also make sure **Send NMEA GGA** (or "Send receiver position") is turned **ON**. Without this, the caster cannot determine your location and will not send corrections. > Need step-by-step instructions for a specific device? See our [device-specific guides](/integration-hub/ntrip-clients-and-field-software) for Emlid, DJI, u-blox, Septentrio, SW Maps, and more. ## Step 4: Go Outside and Verify Take your device outdoors to a location with clear sky visibility. Wait for the status to progress through these stages: 1. **SINGLE** -- the receiver is tracking satellites but has no corrections yet. 2. **FLOAT** -- corrections are arriving and the receiver is converging. 3. **FIX** -- centimeter-level accuracy achieved. Convergence typically takes **5 to 20 seconds** under open sky. If FIX does not appear within 90 seconds, see the checklist below. *** ## If You Are Stuck on FLOAT 1. Verify your mountpoint is `AUTO` in ALL CAPS. 2. Confirm GGA output is enabled (send NMEA position to the caster). 3. Check your internet connection -- 4G/LTE is recommended over 3G. 4. Move away from tall buildings, trees, or metal structures. 5. Disconnect and reconnect the NTRIP client. 6. Confirm you are within [coverage](https://rtkdata.com/coverage/) of a reference station. For persistent issues, see [Troubleshooting & FAQ](/support/troubleshooting-and-faq). *** ## Key Notes * **Heights** are delivered as **ellipsoidal** values (not orthometric / mean sea level). Apply a geoid model in your GIS software or rover if you need elevation above sea level. See [Understanding Heights](/get-started/understanding-heights). * **One connection at a time** per data stream. Running two devices on the same credentials simultaneously will cause disconnects. Add a second data stream from your account dashboard if needed. * **Regional server choice** matters: pick the server closest to your work area. See [Network & Mountpoints](/get-started/network) for full details. # NTRIP Server Settings: Hosts, Port, Mountpoints RTKdata NTRIP connection reference: regional hostnames, IP fallbacks, port 2101, the AUTO mountpoint and how GGA selects your nearest base station. RTKdata operates a global RTK corrections network with **20,000+ reference stations** and **99.99% uptime** at the NTRIP endpoints. Under open-sky conditions, most users achieve RTK FIX in **5 to 20 seconds**. *** ## Connection Basics All devices connect using the **NTRIP** (or NTRIPv2) protocol on **port 2101**. Your network must allow **outbound TCP on port 2101**. Firewalls, VPNs, and some mobile carriers can block this port -- see [Troubleshooting](/support/troubleshooting-and-faq) if you have connection issues. You need NTRIP credentials from the [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website email and password. See [Account & Credentials](/get-started/account-and-credentials). *** ## Regional Servers Choose the server closest to your work area. All three servers share the same global base station network; the difference is routing latency. | Region | Hostname (preferred) | IP Fallback | Port | | ----------------- | -------------------- | --------------- | ------ | | **Europe** | `eu.rtkdata.com` | `3.73.41.96` | `2101` | | **North America** | `rtk.rtkdata.com` | `13.56.117.10` | `2101` | | **Australia** | `aus.rtkdata.com` | `54.206.56.130` | `2101` | **When to use the IP fallback:** Some older Android controllers, tablets, and embedded systems cannot resolve DNS hostnames. If your device fails to connect using the hostname, enter the IP address instead. *** ## Mountpoints RTKdata provides four mountpoints. Names are **case-sensitive** and must be entered in **ALL CAPS**. Use **`AUTO`** unless your project specifically requires a global reference frame. | Mountpoint | Description | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | **`AUTO`** | **Recommended.** Delivers corrections in your region's local datum (e.g., NAD83 in the US, ETRS89 in Europe, GDA2020 in Australia). | | **`AUTO_ITRF2020`** | ITRF2020 at epoch 2015.0 | | **`AUTO_ITRF2014`** | ITRF2014 at current epoch | | **`AUTO_WGS84`** | WGS84(G2139) at mid-year epoch | For the full list of regional datums delivered by `AUTO` per country, see [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums). ### How AUTO Selects a Base Station When your device connects and sends its approximate position (via NMEA GGA), the RTKdata caster identifies the nearest reference station and begins streaming corrections from it. If you move across a coverage area, the system can hand off to a closer station automatically. This is why **GGA output must be enabled** -- without your position, the caster cannot assign a base station and you will receive no data. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials) for details. *** ## Heights All corrections are delivered with **ellipsoidal heights**. If you need orthometric (mean sea level) elevations, apply a geoid model in your rover software or during post-processing. See [Understanding Heights](/get-started/understanding-heights) for guidance. *** ## Quick Reference ``` Host: eu.rtkdata.com / rtk.rtkdata.com / aus.rtkdata.com Port: 2101 Mountpoint: AUTO Username: (from RTKdata dashboard, starts with "rtk") Password: (from RTKdata dashboard) GGA: ON (required) ``` # Coverage Map: How to Check RTK Coverage Before Field Work Learn how to read the RTK coverage map, understand 2 cm and 2-10 cm accuracy zones, and verify your area before deployment. 20,000+ stations, 140+ countries. {% hint style="success" %} **Check coverage in your area before heading to the field:**\ [Open Live Coverage Map](https://rtkdata.com/coverage/) {% endhint %} RTKdata.com operates **20,000+ active reference stations worldwide** across **140+ countries and 4,600+ cities**, delivering centimeter-level positioning accuracy. *** ## How to Read the Map The coverage map shows two zones: * **2 cm zone** — RTK FIX reliable, survey-grade accuracy * **2–10 cm zone** — RTK FIX achievable, good for mapping and agriculture If your work area is inside a colored zone, RTKdata will work for you. If you're outside or near the edge, [start a free trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) and test on-site — some areas have coverage beyond what the map shows. *** ## Before Field Deployment 1. **Check the map** — verify your project area has coverage: [rtkdata.com/coverage](https://rtkdata.com/coverage/) 2. **Test on-site** — run a quick outdoor FIX test before committing to a full survey day 3. **Note on heights** — elevation values are **ellipsoidal by default**. Apply a geoid model if you need orthometric (sea level) heights. See [Understanding Heights](/get-started/understanding-heights). *** ## Mountpoint Recommendation Use the `AUTO` mountpoint — it automatically applies the correct regional datum: | Region | Datum applied by AUTO | | ------------- | --------------------- | | United States | NAD83(2011) | | Europe | ETRS89 / ETRF2000 | | Australia | GDA2020 | | New Zealand | NZGD2000 | For global applications, use `AUTO_WGS84` or `AUTO_ITRF2020`. See [Network & Mountpoints](/get-started/network) for details. *** ## No Coverage in Your Area? * **Try it anyway** — the free trial lets you test. Coverage may extend beyond the map. * **Host a base station** — RTKdata provides free hardware in exchange for 1 year of free service. See [Host a Base Station](/support/host-a-base-station). * **Check back regularly** — the network is constantly expanding with new stations. {% hint style="info" %} [Start your 30-day Free Trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) — no credit card required, auto-ends. {% endhint %} # RTK Ellipsoidal vs Orthometric Heights Explained RTKdata delivers ellipsoidal heights: learn why your elevation may be off by 10-50 m and how to apply a geoid model in Emlid, DJI, Trimble, and QGIS RTKdata delivers **ellipsoidal heights** (height above the mathematical WGS84 ellipsoid). If your elevation readings are off by 10–50+ meters compared to known benchmarks, this page explains why — and how to fix it. *** ## The Short Version > **RTKdata gives you height above the ellipsoid. Your benchmark, topographic map, or "sea level" reference uses height above the geoid. The difference between these two surfaces can be 10–50+ meters depending on your location.** This is NOT an error. It's two different measurement systems. You need to apply a **geoid model** to convert. *** ## What Are Ellipsoidal and Orthometric Heights? ### Ellipsoidal Height (what RTKdata delivers) Height measured from the **WGS84 ellipsoid** — a smooth mathematical surface that approximates Earth's shape. This is what GPS/GNSS receivers calculate directly. ### Orthometric Height (what most people expect) Height measured from the **geoid** — an irregular surface that follows mean sea level. This is what topographic maps, benchmarks, construction plans, and most real-world applications use. ### The Geoid Separation The difference between the ellipsoid and the geoid is called **geoid separation** (or geoid undulation). It varies by location: | Region | Typical Geoid Separation | Direction | | --------------------- | ------------------------ | ------------------------------ | | United States (CONUS) | 15–35 m | Ellipsoid is ABOVE geoid | | Europe | 35–55 m | Ellipsoid is ABOVE geoid | | Australia | 15–30 m | Ellipsoid is ABOVE geoid | | South America | -10 to +30 m | Varies | | Southeast Asia | -20 to +10 m | Often ellipsoid is BELOW geoid | **Example:** In Denver, Colorado, the geoid separation is approximately **-18 meters**. If your RTK receiver shows an ellipsoidal height of 1,625 m, the orthometric (MSL) height is approximately 1,625 - (-18) = 1,643 m. If you compare the raw ellipsoidal height to a benchmark that uses MSL, you'll see a \~18 m offset. *** ## "My Elevation Is Off by X Meters" — Quick Diagnostic | Offset Size | Likely Cause | Solution | | ---------------------- | ---------------------------------------------------- | ------------------------------------ | | 10–55 m (or 30–180 ft) | Geoid separation not applied | Apply a geoid model (see below) | | 0.5–2 m | Datum mismatch (e.g., WGS84 vs local vertical datum) | Check datum settings | | 0.05–0.5 m | Different geoid model version or epoch | Use the correct regional geoid model | | < 0.05 m | Normal RTK vertical accuracy | This is expected performance | > **If your elevation is off by roughly 30–180 feet (10–55 meters), it's almost certainly a geoid issue — NOT a problem with RTKdata.** *** ## Regional Geoid Separation Examples These are approximate values to help you recognize a geoid issue: | Location | Approximate Geoid Separation | | --------------------- | ---------------------------- | | New York City, USA | -32 m | | Denver, Colorado, USA | -18 m | | Los Angeles, USA | -33 m | | London, UK | +47 m | | Berlin, Germany | +40 m | | Sydney, Australia | +22 m | | Perth, Australia | -28 m | | Sao Paulo, Brazil | -7 m | | Dubai, UAE | -27 m | *** ## How to Apply a Geoid Model ### In Emlid Flow 1. Open your project settings 2. Go to **Coordinate system** 3. Select your local vertical datum (which includes a geoid model) 4. Heights will automatically be converted to orthometric ### In DJI Terra 1. DJI Terra outputs ellipsoidal heights by default 2. In **Output Coordinate System**, select a system that includes a vertical datum 3. Or apply the geoid correction in post-processing (QGIS, Global Mapper, etc.) ### In Trimble Access 1. Go to **Jobs** > **Properties** > **Coord sys** 2. Select your local coordinate system (which includes a geoid file) 3. If needed, download the geoid file from Trimble's data manager 4. Heights will display as orthometric once the geoid is active ### In Pix4D 1. Go to **Processing Options** > **Output Coordinate System** 2. Select a coordinate system with a vertical component (e.g., "NAD83 + NAVD88 height") 3. Or set a specific geoid model under vertical datum settings ### In QGIS (Post-Processing) 1. Load your data 2. Go to **Layer** > **Export** > **Save Features As** 3. Set the CRS to include a vertical datum (e.g., EPSG:6360 for NAD83(2011) + NAVD88) 4. QGIS will apply the geoid transformation during export ### In SingularPad 1. Go to **Project Settings** > **Coordinate System** 2. Select your local vertical datum 3. Ensure the geoid file for your region is loaded *** ## Common Geoid Models by Region | Region | Geoid Model | Covers | | ----------------- | ------------------------- | --------------------------------------------------- | | United States | **GEOID18** (or GEOID12B) | NAVD88 vertical datum | | Europe | **EGM2008** | Global, widely supported | | United Kingdom | **OSGM15** | Ordnance Survey datum (ODN) | | Australia | **AUSGeoid2020** | AHD (Australian Height Datum) | | Canada | **CGG2013a** (or HTv2.0) | CGVD2013 vertical datum | | New Zealand | **NZGeoid2016** | NZVD2016 vertical datum | | Global (fallback) | **EGM96** or **EGM2008** | Works everywhere, less precise than regional models | *** ## Real-World Examples from Support These cases were all resolved by applying the correct geoid model: * **Emlid RS3 user (Ojai, California):** RTKdata showed 122 ft, expected 240 ft. Difference of 118 ft = geoid separation in Southern California. Applying GEOID18 resolved the offset. * **SingularXYZ user (Denver, CO):** \~65 ft (20 m) offset — exactly the geoid separation for Denver. * **SingularPad user (Vancouver, Canada):** 20–40 cm elevation offset in CAD stakeout — no geoid model applied in SingularPad. *** ## Key Takeaway | What you want | What to do | | ----------------------------------------- | ------------------------------------------------------- | | Elevation matching sea level / benchmarks | Apply a geoid model in your software | | Raw ellipsoidal height for processing | Use RTKdata output directly (no conversion needed) | | Compare to survey control points | Ensure both use the same vertical datum and geoid model | **RTKdata delivers correct ellipsoidal heights. If your elevation seems wrong, apply a geoid model before concluding there's an accuracy issue.** # RTK Coordinate Systems & Datums Explained Which regional datum each RTKdata mountpoint delivers, and how to resolve datum mismatches, ellipsoidal vs orthometric heights and survey feet settings. RTKdata corrections are available in multiple geodetic reference frames. The mountpoint you choose determines the coordinate system of the corrections streamed to your device. *** ## Mountpoints RTKdata provides four mountpoints. Names are **case-sensitive** and must be entered in **ALL CAPS**. | # | Mountpoint | Details | | - | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | **`AUTO`** | Regional Geodetic Coordinate System (RGCS) — automatically delivers corrections in your region's local datum. **Recommended for most workflows.** | | 2 | **`AUTO_ITRF2020`** | ITRF2020 Geodetic Coordinate System at epoch 2015.0 | | 3 | **`AUTO_ITRF2014`** | ITRF2014 Geodetic Coordinate System with current epoch | | 4 | **`AUTO_WGS84`** | WGS84(G2139) in the middle of the current year (e.g., 2025.5 for year 2025, 2024.5 for year 2024) | > **Recommendation:** Use `AUTO` unless your project specifically requires a global reference frame. AUTO eliminates the most common source of coordinate shifts by delivering corrections in your regional datum. *** ## Regional Geodetic Coordinate System (RGCS) When you connect with the `AUTO` mountpoint, RTKdata automatically selects the correct regional geodetic coordinate system based on your location. The table below shows exactly which datum and epoch is delivered per region. | # | Geodetic Coordinate System Name | Epoch # | Effective Regions | | -- | ------------------------------------------ | ------------- | -------------------- | | 1 | **NAD83(2011)** | 2010.0 | USA | | 2 | **NAD83(PA11)** | 2010.0 | USA Hawaii | | 3 | **NAD83(MA11)** | 2010.0 | Guam | | 4 | **NAD83(CSRS)v7** | 2010.0 | Canada | | 5 | **ETRS89(ETRF2010)(2010.0)** | 2010.0 | Europe | | 6 | **GDA2020(2020.0)** | 2020.0 | Australia | | 7 | **NZGD2000(2000.0)** | 2000.0 | New Zealand | | 8 | **TUREF(2005.0)=ITRF96(2005.0)** | 2005.0 | Turkey | | 9 | **ITRF2008(2005.0)=ITRF2008(2005.0)** | 2005.0 | India | | 10 | **ITRF2008(2011.811)** | 2011.811 | Egypt | | 11 | **NGD2012(2012.0)=ITRF2008(2012.0)** | 2012.0 | Nigeria | | 12 | **PGD2020=ITRF2014(2020.044)** | 2020.044 | Philippines | | 13 | **ITRF2014(2010)** | 2010.0 | Mexico | | 14 | **ITRF2014** | current epoch | Kenya | | 15 | **CGCS2000(2000.0)=ITRF97(2000.0)2** | 2000.0 | China | | 16 | **JGD2011(2011.3945)=ITRF2008(2011.3945)** | 2011.3945 | Japan | | 17 | **IGRS2013(2012.0)=ITRF2008(2012.0)** | 2012.0 | Indonesia | | 18 | **ITRF1991(1994.0)** | 1994.0 | South Africa | | 19 | **WGS84(G730)(1994.0)** | 1994.0 | Sri Lanka | | 20 | **ITRF2020(2025.0)** | 2025.0 | Taiwan | | 21 | **ITRF2014(2010)** | 2010.0 | Thailand | | 22 | **KGD2002(2002.0)=ITRF2000(2002.0)** | 2002.0 | South Korea | | 23 | **MGRF2020(2020.0)=ITRF2020(2020.0)** | 2020.0 | Malaysia | | 24 | **MTRF2000(2004.0)=ITRF2000(2004.0)** | 2004.0 | United Arab Emirates | | 25 | **SIRGAS2000(2000.4)=ITRF2000(2000.4)** | 2000.4 | South America | | 26 | **GGD=ITRF2008(2011.353)** | 2011.353 | Georgia | | 27 | **WGS84(G2139)(20xx.5)1** | 20xx.5 | Other regions | > **Note:** For regions not listed above, `AUTO` falls back to WGS84(G2139) at the mid-year epoch. *** ## Why Your Coordinates May Be Offset If you see a consistent **50 cm – 1 m offset** compared to local survey control, this is almost certainly a **datum mismatch**, not an accuracy problem. The earth's tectonic plates move. Global frames like ITRF2014 track current plate positions, while regional datums (NAD83, ETRS89, GDA2020) were fixed at a specific point in time. The difference grows every year, which is why mixing two reference frames shows up as a steady, predictable offset. **The Fix:** 1. **Use `AUTO`.** It delivers corrections in your regional datum, eliminating the shift in most cases. 2. **Software transformation:** If you must use a global mountpoint (`AUTO_ITRF2020`, `AUTO_WGS84`), set your rover/drone software to transform from WGS84/ITRF to your local system. *** ## Vertical Reference: Ellipsoidal vs. Orthometric Heights RTKdata provides **ellipsoidal heights** (height above the WGS84 ellipsoid). These are NOT the same as: * Mean Sea Level (MSL) * Orthometric height * Local vertical datum To convert to orthometric heights, apply a **geoid model** in your software: * **EGM96 / EGM2008** — global geoid models * **OSGM15** — UK geoid model * **GEOID18** — US geoid model * **AUSGeoid2020** — Australian geoid model Most surveying software and GIS applications can apply geoid corrections automatically when the correct vertical datum is selected. See [Understanding Heights](/get-started/understanding-heights) for a detailed guide. *** ## US Survey Feet vs. International Feet If you see a steady **\~4 ft / 1.2 m offset** in the United States, check your controller's unit settings. The difference between US Survey Feet and International Feet causes a noticeable shift at scale. **Fix:** Set your controller/software project to use the correct foot definition for your state. # Account & NTRIP Credentials Guide Learn how RTKdata accounts work, where to find your NTRIP credentials, and how to manage data streams. Covers website login vs. NTRIP credentials and free trial This page explains how RTKdata accounts work, how to find your NTRIP credentials, and answers common account questions. *** ## Website Login vs. NTRIP Credentials RTKdata uses **two separate sets of credentials**: | | Website Login | NTRIP Credentials | | ------------------- | --------------------------------------------------------- | ----------------------------------------------------------------------- | | **Purpose** | Access your dashboard, manage subscription | Connect your GNSS device to the RTK service | | **Where to use** | [rtkdata.com/my-account](https://rtkdata.com/my-account/) | Your GNSS receiver, drone, or NTRIP client app | | **Username format** | Your email address | Starts with `rtk` (e.g., `rtkabc123`) | | **Where to find** | You set this at registration | [RTK Credentials page](https://rtkdata.com/my-account/rtk-credentials/) | > **#1 support issue:** Using your website email/password in the NTRIP client. This will always fail. Use the dedicated NTRIP credentials from your dashboard. *** ## How to Find Your NTRIP Credentials 1. Log in at [rtkdata.com/my-account](https://rtkdata.com/my-account/) 2. Go to **RTK Credentials** tab 3. Copy your **Username** and **Password** 4. Enter these in your device's NTRIP settings **Tips:** * Copy carefully — avoid trailing spaces * Credentials are case-sensitive * If in doubt, re-type manually instead of copy/paste *** ## Sharing Credentials Across Devices Each subscription includes **one concurrent data stream** (one device connected at a time). | Scenario | Allowed? | | ------------------------------------------------------------- | ----------------------------------------------------------- | | Use the same credentials on different devices (one at a time) | Yes | | Share credentials among team members (one at a time) | Yes, but we recommend separate data streams for reliability | | Multiple drones flying simultaneously | Requires one data stream per drone | ### What happens when two devices connect at the same time? If a second device connects while another is already active on the same data stream, the **currently connected device gets disconnected** and the new device takes over. This can cause unexpected RTK loss in the field. **Solution:** Purchase additional data streams — you can add monthly or annual subscriptions at any time from your [account dashboard](https://rtkdata.com/my-account/). For enterprise fleets, [book a meeting](https://sales.rtkdata.com/#use) to discuss volume options. *** ## Multiple Data Streams Your account login stays the same — you can add or remove data streams as needed: * Purchase additional monthly or annual data streams from your [account dashboard](https://rtkdata.com/my-account/) * Check the **Connections** count in your dashboard — it shows how many concurrent streams your account supports * Each data stream supports one simultaneous device connection * You can scale up or down at any time *** ## Free Trial | Detail | Info | | -------------------- | ---------------------------------- | | Duration | 30 days | | Features | Full access, same as paid plans | | Auto-renewal | No — trial ends automatically | | Credit card required | No | | Limit | One trial per user/device | | Credentials | Available immediately after signup | Start your trial at [rtkdata.com/try-rtk-corrections-free-for-30-days](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) *** ## Changing Your NTRIP Username Your NTRIP username is auto-generated and tied to your subscription. If you need to change it, contact support at . *** ## Cannot Log In | Problem | Solution | | --------------------------------- | ------------------------------------------ | | Forgot password | Use the password reset on the login page | | "Password required" loop | Clear browser cache and cookies, try again | | Account locked | Contact | | Never received confirmation email | Check spam folder, or contact support | *** ## Subscription Management You can manage your subscription from your [account dashboard](https://rtkdata.com/my-account/): * **Pause** your subscription (keeps credentials active, stops billing) * **Cancel** anytime — no lock-in * **Switch plans** (monthly ↔ annual ↔ 5-year) * **View payment history** and download invoices # RTK Accuracy Explained: 2 cm Survey-Grade Understand realistic RTKdata accuracy: 2 cm survey-grade near a base station, what sky view, internet latency and distance do to your FIX. RTK accuracy depends primarily on your distance to the nearest base station. This page sets realistic expectations so you can plan your fieldwork accordingly. *** ## What to Expect RTKdata delivers centimeter-level accuracy when you're within coverage. Check the [Coverage Map](https://rtkdata.com/coverage/) to verify your area before heading to the field. Performance depends on distance to the nearest base station, sky view, and internet stability. *** ## Understanding the Coverage Map The [RTKdata Coverage Map](https://rtkdata.com/coverage/) uses two color zones: * **2 cm zone:** RTK FIX reliable, survey-grade accuracy * **2–10 cm zone:** RTK FIX achievable, good for mapping and agriculture * **Outside colored areas:** No nearby base station — accuracy depends on distance to nearest station > **Always check the coverage map BEFORE going to the field.** Knowing your expected accuracy in advance prevents frustration and wasted time. *** ## What Affects Accuracy Beyond Distance ### Sky View / GNSS Environment * **Best:** Open field, no obstructions above 15 degrees elevation * **Good:** Rural area with scattered trees * **Challenging:** Near buildings, under partial tree canopy * **Poor:** Urban canyons, dense forest, near large metal structures Multipath interference (signals bouncing off buildings or metal) is the #1 accuracy killer after distance. ### Internet Connection RTK requires real-time corrections. High latency degrades accuracy: * **< 1 second latency:** Full RTK performance * **1–3 seconds latency:** Slightly degraded, may see more FLOAT * **> 3 seconds latency:** Corrections become stale, accuracy drops significantly Use a stable 4G/5G connection. Avoid public Wi-Fi or VPNs. ### Atmospheric Conditions * **Ionospheric activity** (solar storms) can degrade RTK, especially at longer baselines * **Tropospheric conditions** (heavy rain, extreme temperature inversions) have minor effects * These are rarely the primary cause of issues — check distance and sky view first *** ## "I'm in the 2–10 cm Zone — What Does That Mean?" If the coverage map shows you're in the **2–10 cm zone**: * **RTK FIX** is achievable but may take longer to converge * Horizontal positions will typically be within **2–10 cm** of true position * Vertical accuracy will be **1.5–2x worse** than horizontal * This is **sufficient for:** drone mapping, photogrammetry (with GCPs), agriculture guidance, general construction layout * This is **NOT sufficient for:** survey-grade control points, precise boundary surveys, or measurements requiring < 2 cm *** ## When to Consider a Local Base Station If you regularly work in an area without nearby RTKdata coverage, hosting a local base station may be the best solution: * **RTKdata provides the hardware** (compact GNSS station, size of a large water bottle) * **You provide:** a location with clear sky view, power (1.5W USB-C), and Wi-Fi (2.4 GHz) * **Benefit:** 1 year of free RTK service * **Calibration:** 12–24 hours automatic after installation See [Host a Base Station](/support/host-a-base-station) for full details and requirements. *** ## Improving Your Results ### Quick Wins 1. **Move to open area** — Even 20 meters away from a building can make a difference 2. **Wait longer** — Give RTK 60–90 seconds to converge. Don't rush. 3. **Check your mountpoint** — Use `AUTO` (ALL CAPS). Wrong mountpoint = no corrections. 4. **Use the nearest regional server** — EU server for Europe, AUS for Australia/Oceania 5. **Stable internet** — 4G hotspot beats weak Wi-Fi every time ### For Best Possible Accuracy 1. Work within 15 km of a base station 2. Use a survey-grade or high-quality mapping receiver 3. Ensure clear sky view (15 degrees elevation minimum) 4. Use a stable 4G/5G internet connection 5. Wait for RTK FIX and verify it's stable before collecting points 6. Apply the correct geoid model for orthometric heights (see [Understanding Heights](/get-started/understanding-heights)) # Pricing FAQ: Plans, Billing & Trial RTKdata pricing answers: monthly, annual and 5-year plans, USD billing, why one license is one connection, cancellation and the 30-day free trial. Answers to the most common questions about RTKdata pricing, payments, and plans. *** ## Plans & Pricing | Plan | Price | Best for | | ---------- | -------------------- | ----------------------- | | Monthly | $40/month | Short projects, testing | | Annual | $400/year (save 17%) | Regular use | | 5-Year | $1,920 (save 60%) | Long-term operations | | Enterprise | Custom | Fleets, large teams | All prices are per license (one concurrent data stream). *** ## Frequently Asked Questions ### Is pricing in USD? Yes. All RTKdata prices are listed in **US Dollars (USD)**. Your bank or payment provider handles currency conversion at checkout if you're paying in another currency (GBP, EUR, AUD, etc.). ### Can I pay in GBP / EUR / AUD? Payments are processed in USD. Your credit card company or bank will convert at the current exchange rate. The exact amount in your local currency depends on your bank's rate and any foreign transaction fees. ### Do you offer education discounts? Contact us at to discuss educational or academic pricing. ### Can I run multiple drones / devices on one subscription? Each subscription gives you **one set of NTRIP credentials** (username + password) that supports **one active connection at a time**. * **One device at a time?** Yes — enter the same credentials in each device and use them one after another. Only one can be connected at any moment. * **Two devices connected at the same time?** The device that connects **last takes over** — the first device gets **disconnected** and loses RTK immediately. This is the most common cause of unexpected RTK drops in the field. * **Need more simultaneous connections?** Purchase additional data streams (monthly or annual) from your [account dashboard](https://rtkdata.com/my-account/). Each additional stream gives you a separate set of credentials. * **Fleet operations?** [Book a meeting](https://sales.rtkdata.com/#use) to discuss enterprise volume options. ### Can multiple people share one subscription? Yes, but only **one person can be connected at a time**. If a colleague connects with the same credentials while you're working, **your connection gets dropped**. For teams working simultaneously, add one data stream per person from your [account dashboard](https://rtkdata.com/my-account/). ### What happens when my free trial ends? The trial ends automatically after 30 days. There is **no auto-renewal** and no credit card is required. Your credentials simply stop working. To continue, purchase a subscription. ### How do I cancel? Go to [My Account](https://rtkdata.com/my-account/) → Subscription → Cancel. Cancellation is immediate, no lock-in, no penalties. ### I accidentally bought the wrong plan / too many subscriptions Contact — we'll sort it out. ### Will my dashboard update immediately after payment? It may take a few minutes for your dashboard to reflect a new payment. If it hasn't updated after 15 minutes, contact support with your order confirmation email. ### Do you charge VAT/tax? Taxes (including VAT) may apply depending on your location and will be shown at checkout or on your invoice. *** ## Coverage Outside the Map If your location is outside the [Coverage Map](https://rtkdata.com/coverage/): 1. **Try it anyway** — the free trial lets you test. Some areas have coverage beyond what's shown on the map. 2. **Request a local base station** — RTKdata can sometimes provide a local reference station at no additional cost. Contact us at . 3. **Check back regularly** — the network is constantly expanding with new stations. *** ## Enterprise & Fleets For organizations with multiple receivers, drones, or large field teams: * Volume discounts available * Dedicated account management * Custom SLAs Contact or [book a meeting](https://sales.rtkdata.com/#use). # Integration Hub: RTK Setup Guides Step-by-step RTKdata setup guides for DJI and Autel drones, Emlid, Trimble, Leica and u-blox rovers, NTRIP field software and agriculture auto-steer. Connect your GNSS rover, drone, or field software to RTKdata.com. Select your device or app below for a step-by-step setup guide. *** ## Drones & UAVs | Device | App | Guide | | -------------------------------------------------------------------------------------------------------------------------------- | -------------- | ----------------------------------- | | [DJI Mavic 3 Enterprise RTK (3E / 3T / 3M)](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-mavic-3-enterprise-rtk) | DJI Pilot 2 | Mapping & inspection drone | | [DJI Matrice 4 Enterprise RTK](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-matrice-4-enterprise-rtk) | DJI Pilot 2 | Newest enterprise drone (2025) | | [DJI Agras T50 / T40 / T25](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-agras-t50-t40-t25) | DJI Agras App | Agricultural spraying drones | | [DJI Phantom 4 RTK (P4R)](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-phantom-4-rtk) | GS RTK App | Legacy survey drone | | [Autel EVO II Pro RTK V3](https://docs.rtkdata.com/integration-hub/drones-and-uavs/autel-evo-ii-rtk) | Autel Explorer | DJI alternative, enterprise mapping | *** ## GNSS Rovers & Receivers | Device | Companion App | Guide | | ------------------------------------------------------------------------------------------------------------------------ | --------------------------- | ---------------------------------------------------- | | [Emlid Reach RS3](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/emlid-reach-rs3) | Emlid Flow | Newest Emlid multi-band rover with tilt compensation | | [Emlid Reach RS2+](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/emlid-reach-rs2+) | Emlid Flow | Popular mid-range survey rover | | [Emlid Reach RX / RX2](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/emlid-reach-rx-rx2) | Emlid Flow | Compact rover for GIS & mapping | | [Trimble R12i / R10 / R750](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/trimble-r12i) | Trimble Access | Professional survey receivers | | [Trimble Receivers (General)](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/trimble-receivers) | Trimble Access / Earthworks | VRS vs Single Base setup guide | | [Leica GS18 / GS16 / GS07](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/leica-gs18) | Leica Captivate | Professional survey receivers | | [ArduSimple simpleRTK2B / 3B](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/ardusimple-simplertk2b) | SW Maps / u-center | Popular low-cost u-blox F9P board | | [SparkFun RTK Facet](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/sparkfun-rtk-facet) | SW Maps / WiFi Portal | u-blox F9P based receiver | | [Septentrio mosaic-X5](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/septentrio-mosaic-x5) | Web UI / RxTools | Professional multi-frequency module | | [Bad Elf Flex](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/bad-elf-flex) | Bad Elf GPS App | Professional GNSS receiver | | [Bad Elf Flex Mini](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/bad-elf-flex-mini) | Bad Elf GPS App | Compact GNSS receiver | | [EOS Arrow Gold](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/eos-arrow-gold) | EOS Tools Pro | GIS-grade GNSS receiver | *** ## NTRIP Clients & Field Software | Software | Platform | Guide | | ------------------------------------------------------------------------------------------------------------------------ | ----------------- | ---------------------------------------- | | [SW Maps](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/sw-maps) | Android | Best free NTRIP client for testing & GIS | | [Emlid Flow](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/emlid-flow) | iOS / Android | Companion app for Emlid receivers | | [DJI Pilot / Pilot 2](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/dji-pilot-pilot-2) | DJI Controllers | Flight app for DJI Enterprise drones | | [Lefebure NTRIP Client](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/lefebure-ntrip-client) | Android | Most popular standalone NTRIP client | | [u-center (u-blox F9)](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/u-center-u-blox-f9) | Windows | Configuration tool for u-blox F9P chips | | [Septentrio RxTools](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/septentrio-rxtools) | Windows | Suite for Septentrio receivers | | [EOS Tools Pro](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/eos-tools-pro) | iOS / Android | Companion app for EOS Arrow receivers | | [Carlson SurvPC / SurvCE](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/carlson-survpc) | Windows | Professional surveying software | | [MicroSurvey FieldGenius](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/fieldgenius) | Windows / Android | Professional surveying software | | [QField / QGIS](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/qfield) | Android / iOS | Open-source mobile GIS | *** ## Agriculture | System | Guide | | ------------------------------------------------------------------------------- | --------------------------------------------------- | | [RTKdata for Agriculture](https://docs.rtkdata.com/integration-hub/agriculture) | Compatibility list, setup tips for all ag equipment | | [AgOpenGPS](https://docs.rtkdata.com/integration-hub/agriculture/agopengps) | Open-source auto-steer with u-blox F9P | *** ## Key Resources * [NTRIP & GGA Essentials](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials) — How NTRIP works and why GGA matters * [Quick Start](https://docs.rtkdata.com/get-started/quick-start) — From signup to RTK FIX in 4 steps * [Troubleshooting & FAQ](https://docs.rtkdata.com/support/troubleshooting-and-faq) — Common problems and fixes * [DJI RTK Troubleshooting](https://docs.rtkdata.com/support/dji-rtk-troubleshooting) — "Converging" issues, battery swap, distance {% hint style="info" %} **Don't see your device?** Most GNSS receivers with an NTRIP menu work with RTKdata. Use the [Quick Start](https://docs.rtkdata.com/get-started/quick-start) settings and contact if you need help. {% endhint %} # NTRIP Clients & Field Software: RTK Setup Guides Connect any NTRIP client or field software to RTKdata. Guides for SW Maps, Lefebure, Emlid Flow, FieldGenius, Carlson SurvPC, and more. Free 30-day trial ## How it Works Understanding the data flow helps you troubleshoot connections in seconds. 1. **Connect:** Your app connects to the RTKdata Caster (Server) via Internet. 2. **Locate:** The app sends your approximate position via **NMEA GGA** message. 3. **Stream:** The Caster calculates corrections for that specific location and streams them back (RTCM). 4. **Fix:** Your Rover calculates the exact position: `Autonomous` → `Float` → `FIX` (✅). *** ## Universal Connection Settings Enter these details into your application (e.g., SW Maps, Lefebure, FieldGenius). > Select your Region: Click the tabs below to find the fastest server for your location. ### North America * **Host (domain):** `rtk.rtkdata.com` * **Host (IP fallback):** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/) (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 [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/) (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 [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/) (not website login) * **Mountpoint (ALL CAPS):** `AUTO` *(recommended)* — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` > **Mountpoints are Case Sensitive.** You must type `AUTO` in ALL CAPS. *** ## Popular App Guides Select your software to view the specific step-by-step configuration. ### Free & GIS Apps (Android/iOS) * [SW Maps](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/sw-maps) - *Best free tool for testing & GIS.* * [Emlid Flow](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/emlid-flow) - *Standard for Reach RS2/RS3.* * [Lefebure NTRIP Client](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/lefebure-ntrip-client) - *Classic NTRIP injector.* * [GNSS Master](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/gnss-master) - *Best NTRIP relay & mock location app (Android).* * [MapIt GIS](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/mapit-gis) - *Android GIS with built-in NTRIP & RTK processing.* ### Professional Surveying Software * [MicroSurvey FieldGenius](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/fieldgenius) - *Windows & Android.* * [Carlson SurvPC / SurvCE](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/carlson-survpc) - *The surveyor's standard.* * [QField / QGIS](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/qfield) - *Open Source Mobile GIS.* * [HYPACK](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/hypack) - *Marine / hydrographic survey (Windows).* ### Hardware Tools * [u‑center (u‑blox F9)](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/u-center-u-blox-f9) - *For chip configuration (F9P).* * [Septentrio RxTools](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/septentrio-rxtools) - *Deep dive analysis.* > **Don't see your app?** Use the Universal Settings above. # NTRIP & GGA Explained: AUTO Mountpoint How NTRIP and NMEA GGA work with RTKdata. The caster reads your GGA position to pick the nearest base station via the AUTO mountpoint, not a VRS. Port 2101. This page explains how the NTRIP protocol works, why your device must send GGA messages, and how the AUTO mountpoint routes corrections to you. *** ## What Is NTRIP? NTRIP (Networked Transport of RTCM via Internet Protocol) is the standard protocol for delivering RTK correction data over the internet. It uses a three-part architecture: * **NTRIP Server** -- a reference (base) station that generates correction data and sends it to the caster. * **NTRIP Caster** -- a central server that receives corrections from many base stations and distributes them to connected clients. RTKdata operates the caster at `eu.rtkdata.com`, `rtk.rtkdata.com`, and `aus.rtkdata.com`. * **NTRIP Client** -- your rover, drone, or field app. It connects to the caster, authenticates, and receives the correction stream. The client connects to the caster over TCP on **port 2101**, provides a username, password, and mountpoint name, and then receives a continuous stream of RTCM3 correction messages. *** ## What Is GGA and Why Does the Caster Need It? **GGA** (Global Positioning System Fix Data) is an NMEA sentence that contains your receiver's approximate position, fix quality, number of satellites, and altitude. It looks like this: ``` $GPGGA,123519,4807.038,N,01131.000,E,1,08,0.9,545.4,M,47.0,M,,*47 ``` When your device connects to the RTKdata caster and requests the `AUTO` mountpoint, the caster needs to know **where you are** so it can: 1. **Select the nearest base station** and stream corrections from it. 2. Optimize the corrections for your specific location (reducing baseline distance and improving accuracy). If the caster never receives a GGA message from your device, it has no way to determine which base station to use. The result: **your session connects successfully, but no correction data is delivered.** This is the single most common cause of "connected but no corrections" issues. *** ## What Happens When GGA Is Not Sent When a device connects without sending GGA: 1. The caster authenticates the client -- login succeeds. 2. The caster waits for the client's position to assign a base station. 3. No position arrives. The caster continues waiting. 4. The client sees 0 kB/s throughput and no corrections. This appears in RTKdata session logs as a **0 GGA session**. If you see "connected but no data" or "waiting for base", the first thing to check is whether GGA output is enabled. *** ## How to Enable GGA The setting name varies by app, but the concept is the same: your device must send its approximate position back to the caster. | App / Device | Setting Location | | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | | [Emlid Flow](/integration-hub/ntrip-clients-and-field-software/emlid-flow) | Correction input > NTRIP > **Send receiver position (NMEA)** = ON | | [SW Maps](/integration-hub/ntrip-clients-and-field-software/sw-maps) | NTRIP settings > **Send NMEA GGA to caster** = ON | | [u-center (u-blox)](/integration-hub/ntrip-clients-and-field-software/u-center-u-blox-f9) | Receiver > NTRIP Client (uses current position automatically; ensure receiver has a valid fix) | | [Septentrio RxTools](/integration-hub/ntrip-clients-and-field-software/septentrio-rxtools) | RxControl > Output Settings > NMEA > **GGA @ 1 s**; DataLink forwards it | | [EOS Tools Pro](/integration-hub/ntrip-clients-and-field-software/eos-tools-pro) | NTRIP/Differential > **Send NMEA GGA to caster** = ON | | [DJI Pilot / Pilot 2](/integration-hub/ntrip-clients-and-field-software/dji-pilot-pilot-2) | Automatic once the drone has a satellite fix. Must be outdoors. | *** ## GGA Rate Recommendation Set GGA output to **1 Hz (once per second)** where your app allows you to configure the interval. This gives the caster an up-to-date position so it can optimize corrections as you move. Some apps default to 5 or 10 seconds, which works but is less responsive if you are covering large distances quickly. A 1 Hz rate uses negligible bandwidth (about 70 bytes per message). *** ## How the AUTO Mountpoint Works When you connect to mountpoint `AUTO`: 1. Your device sends a GGA message with its approximate position. 2. The caster looks up the nearest reference station from its network of 20,000+ stations. 3. The caster begins streaming RTCM3 corrections from that station. 4. As you move and send updated GGA messages, the caster can switch to a closer station if one becomes available. This means `AUTO` is a dynamic, location-aware mountpoint. It removes the need to know which specific base station to connect to. For most workflows, `AUTO` is the recommended choice. The other mountpoints (`AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`) work the same way but deliver corrections in a specific reference frame instead of the regional datum. See [Network & Mountpoints](/get-started/network) for details on when to use each. *** ## RTKdata Connection Settings | Setting | Value | | -------------- | --------------------------------------------------------------------------------------------- | | **Host** | `eu.rtkdata.com` / `rtk.rtkdata.com` / `aus.rtkdata.com` | | **Port** | `2101` | | **Mountpoint** | `AUTO` (ALL CAPS, case-sensitive) | | **Username** | From [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/) (starts with `rtk`) | | **Password** | From RTKdata Dashboard | | **Send GGA** | **ON** (required) | *** ## Heights RTKdata delivers **ellipsoidal heights** in all reference frames. If you need orthometric (mean sea level) elevations, apply a geoid model in your rover software or during post-processing. See [Understanding Heights](/get-started/understanding-heights). ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) * [Agriculture](https://rtkdata.com/agriculture/) # SW Maps NTRIP Setup: Connect to RTK Corrections Guide to connecting SW Maps to RTKdata via NTRIP on Android. Stream centimeter-level RTK corrections to any Bluetooth GNSS receiver. Free 30-day trial SW Maps is a free Android GIS and mapping application that doubles as one of the best NTRIP clients available on mobile. It connects to external Bluetooth GNSS receivers such as the SparkFun RTK Facet, ArduSimple simpleRTK2B, and any u-blox ZED-F9P-based board. SW Maps streams RTK corrections from an NTRIP caster like RTKdata.com directly to your receiver, delivering centimeter-level accuracy for survey-grade field data collection. **Download:** [Google Play Store](https://play.google.com/store/apps/details?id=np.com.softwel.swmaps) (free) ## Requirements * Android phone or tablet with internet access (mobile data or Wi-Fi hotspot) * Bluetooth-capable GNSS receiver (SparkFun RTK Facet, ArduSimple, u-blox F9P board, etc.) * GNSS antenna with clear sky view (survey pole or tripod recommended) * Active RTKdata.com account with username and password {% 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 %} #### Connect your Bluetooth GNSS receiver 1. Power on your GNSS receiver and enable Bluetooth on your Android phone. 2. Open SW Maps and tap the **Bluetooth** icon in the top toolbar (or go to **Menu → Bluetooth GNSS**). 3. Tap **Scan** to discover nearby devices. Select your receiver from the list. 4. Set the **Instrument Model** to match your hardware (e.g., "Generic RTK Receiver" or your specific model). 5. Set the **Instrument Height** to your pole or tripod height. 6. Tap **Connect**. The status bar should begin showing coordinates from the external receiver. {% hint style="warning" %} **Phone GPS vs. External Receiver:** After connecting, verify that coordinates come from your external receiver, not the phone's internal GPS. Phone GPS accuracy is typically 5–15 m. Your external receiver should show 1–3 m accuracy before corrections. If the accuracy indicator shows 10+ m, the app is still using the phone's internal GPS. Reconnect via Bluetooth GNSS and confirm the source has switched. {% endhint %} {% endstep %} {% step %} #### Open the NTRIP client 1. Tap the **Menu** icon (three horizontal lines) in the top-left corner. 2. Tap **NTRIP Client**. 3. Tap **Add New Profile** (or the **+** button). 4. Enter a profile name (e.g., "RTKdata EU" or "RTKdata NA"). {% endstep %} {% step %} #### Enter RTKdata.com connection settings Fill in the following fields: * **Send NMEA GGA to Caster:** **Enabled (ON)** {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} The **Send NMEA GGA to Caster** toggle must be **ON**. RTKdata.com uses your GGA position to generate corrections from the nearest Virtual Reference Station. Without GGA, the caster cannot compute corrections and you will remain stuck on FLOAT indefinitely. {% endhint %} {% endstep %} {% step %} #### Connect and verify RTK FIX 1. Tap **Connect** to start the NTRIP correction stream. 2. Watch the status bar at the top as the solution progresses: **Autonomous → DGPS → Float → FIX**. 3. Once you see **RTK FIX**, you have centimeter-level accuracy. This typically takes 10–60 seconds under clear sky. **How to verify RTK is working:** * **Solution type** in the status bar reads **FIX** (not Float or Autonomous). * **Horizontal accuracy** drops to **0.01–0.02 m** (1–2 cm). * **Age of corrections** stays below 5 seconds (visible in the NMEA data stream). * The NTRIP icon in the toolbar shows an active connection (no red X). {% endstep %} {% endstepper %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------- | ------------------------------- | ----------------------------------------------------------------------- | | Position shows phone GPS (10+ m accuracy) | External receiver not connected | Go to **Bluetooth GNSS**, reconnect receiver, verify coordinates change | | NTRIP connects but stays on FLOAT | GGA not sent to server | Enable **Send NMEA GGA to Caster** in the NTRIP profile | | "Connection refused" or timeout | Wrong host/port or no internet | Double-check hostname spelling and port `2101` | | Mountpoint error or "No data" | Mountpoint not uppercase | Enter `AUTO` in ALL CAPS, not `auto` or `Auto` | | Corrections received but accuracy poor | Obstructed sky view | Move to open sky; avoid trees, buildings, overhead cover | | Receiver pairs but no position data | Wrong protocol | Ensure NMEA output is enabled on the receiver over Bluetooth | ## Tips for best results * **Always confirm your position source.** SW Maps defaults to phone GPS if no Bluetooth device is connected. Double-check before collecting data. * **Save your NTRIP profile.** The profile persists between sessions so you only configure credentials once. * **Export data** in GeoJSON, KML, CSV, or Shapefile format directly from the app. * **Check satellite count.** Tap the satellite icon to see tracking status. You need at least 10–12 satellites for reliable FIX. * **If FIX drops repeatedly**, check receiver firmware and ensure the antenna has a proper ground plane. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Environmental Monitoring](https://rtkdata.com/environmental-monitoring/) * [Utilities](https://rtkdata.com/utilities/) # Emlid Flow NTRIP Setup: Reach RTK Corrections Configure Emlid Flow NTRIP for Reach RS2+, RS3 and RX receivers with RTKdata. Add host, port 2101, AUTO mountpoint and Global CS for centimeter RTK fix. Emlid Flow is the official companion app for Emlid GNSS receivers, including the Reach RS2+, Reach RS3, Reach RX, and Reach RX2. Available on both iOS and Android, it handles receiver configuration, NTRIP correction input, data collection, and project management. When paired with an RTKdata.com subscription, Emlid Flow streams real-time corrections to your receiver for centimeter-level RTK positioning. **Download:** [App Store (iOS)](https://apps.apple.com/app/emlid-flow/id1463967138) | [Google Play (Android)](https://play.google.com/store/apps/details?id=com.emlid.flow) ## Requirements * Emlid receiver (Reach RS2+, RS3, RX, or RX2) with clear sky view * Smartphone or tablet running Emlid Flow (iOS 14+ or Android 7+) * Internet access on your phone (mobile data or Wi-Fi) * Active RTKdata.com account with username and password {% 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 %} ### Power on and connect the receiver 1. Turn on your Emlid receiver and wait for the LED to indicate it is ready (blinking blue on RS2+/RS3). 2. Open Emlid Flow on your phone. 3. The app will detect your receiver via Bluetooth or Wi-Fi. Tap on your device name to connect. 4. Wait for the receiver to acquire satellites. The status bar will display the number of satellites tracked. {% endstep %} {% step %} ### Open correction input settings 1. In the main Emlid Flow interface, tap the **Correction input** tab (satellite dish icon on the bottom bar). 2. Select **NTRIP** as the correction source. {% endstep %} {% step %} ### Create a new NTRIP profile 1. Tap the **+** button or **Add new** to create a new profile. 2. Give the profile a name (e.g., "RTKdata Europe"). {% endstep %} {% step %} ### Enter RTKdata.com connection settings Fill in the following fields: * **Send receiver position (NMEA):** **ON** {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} **Global CS vs. Local CS:** When the app asks you to confirm the coordinate system during NTRIP setup, select **Global CS** (not a local coordinate system). The `AUTO` mountpoint handles regional corrections automatically. Apply your local datum or projection only in the survey project settings, never in the NTRIP connection configuration. Mixing this up is the most common source of coordinate errors with Emlid receivers. {% endhint %} {% endstep %} {% step %} ### Connect and wait for FIX 1. Tap **Apply** or **Save** to store the profile. 2. Tap the toggle or **Connect** button to start streaming corrections. 3. Watch the solution status in the top bar: **Single → Float → FIX**. 4. Once you see **FIX**, your receiver is operating at centimeter-level accuracy. **How to verify RTK is working:** * **Solution status** in the status bar displays **FIX** (green indicator). * **Horizontal precision** shows values of **0.014 m** or similar (1–2 cm). * **Correction age** remains below 5 seconds (visible in status details). * **Correction input** tab shows data actively streaming (byte counter increasing). {% endstep %} {% endstepper %} {% hint style="warning" %} **LoRa Conflict Warning:** If you also use an Emlid base station with LoRa radio, you must disable LoRa correction input before enabling NTRIP. Running both simultaneously causes correction conflicts and unpredictable position jumps. Use one correction source at a time. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------- | --------------------------------------- | --------------------------------------------------------------------------------- | | "Confirm login" popup repeats | Wrong credentials or unreachable server | Verify username/password; check hostname spelling | | Connected but stuck on FLOAT | GGA not sent or poor sky | Ensure **Send receiver position (NMEA)** is ON; move to open sky | | "Mountpoint not found" | Mountpoint not uppercase | Enter `AUTO` in ALL CAPS | | Coordinate system conflict | Local CS selected during NTRIP setup | Choose **Global CS** for the NTRIP connection; apply local CS in project settings | | Receiver not appearing in app | Bluetooth/Wi-Fi not active | Toggle Bluetooth/Wi-Fi off and on; restart the receiver | | Accuracy stays at meter level | Too few satellites | Wait 30–60 seconds; ensure unobstructed 360-degree sky view | ## Tips for Emlid Flow * **Global CS for NTRIP, local CS for projects.** This distinction is critical and the most common mistake. * **Keep firmware current.** Update via Emlid Flow for improved RTK convergence and multi-constellation support. * **Built-in survey tools.** Emlid Flow includes point collection, stakeout, and CSV/DXF export without needing a separate GIS app. * **Profile switching.** Create one NTRIP profile per region for quick switching between work areas. * **Check correction latency.** If correction age exceeds 10 seconds, switch between Wi-Fi and mobile data. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # DJI Pilot 2 RTK Setup: Connect NTRIP Corrections Set up RTKdata NTRIP on DJI Pilot 2 for M350, M300 and Mavic 3E RTK drones. Pick Custom Network RTK, port 2101, AUTO mountpoint for centimeter mapping. DJI Pilot 2 is DJI's official flight control application for Enterprise-grade drones, including the Matrice 350 RTK, Matrice 300 RTK, Mavic 3 Enterprise RTK, and Matrice 4 series. It runs exclusively on DJI Enterprise controllers (RC Pro Enterprise, RC Plus) and includes a built-in NTRIP client for receiving RTK corrections from services like RTKdata.com, enabling centimeter-level positioning for precision mapping, surveying, and inspection flights. **Platform:** Pre-installed on DJI Enterprise controllers. Not available on consumer controllers or public app stores. ## Requirements * DJI Enterprise drone with RTK capability (M350 RTK, M300 RTK, Mavic 3E RTK, M4 series) * DJI Enterprise controller (RC Pro Enterprise or RC Plus) with internet access * Internet connection on the controller (Wi-Fi, mobile hotspot, or built-in 4G dongle) * Active RTKdata.com account with username and password * Open sky conditions at the takeoff location {% 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 %} ### Power on and link aircraft 1. Power on the controller and the aircraft. 2. Wait for the aircraft and controller to link (status bar shows "Connected"). 3. Ensure the controller has internet access. If using a mobile hotspot, connect via **Settings → Wi-Fi** on the controller. {% endstep %} {% step %} ### Open RTK settings 1. On the DJI Pilot 2 main screen, tap the **three-dot menu (...)** or the **gear icon** to open settings. 2. Navigate to **Safety → RTK** (on some firmware versions: **Settings → RTK**). 3. Toggle the **RTK switch** to **ON**. {% endstep %} {% step %} ### Select Custom Network RTK 1. Under **RTK Service Type**, you will see options including "D-RTK 2 Mobile Station" and "Custom Network RTK". 2. Select **Custom Network RTK**. {% hint style="warning" %} **Do NOT select "D-RTK 2 Mobile Station."** That option is exclusively for DJI's own D-RTK 2 base station hardware. Selecting it when using an NTRIP service like RTKdata.com will fail silently — the drone will appear to accept the settings but will never receive corrections. This is the single most common configuration mistake with DJI Enterprise drones. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com connection settings Tap **Custom Network RTK** to open the configuration fields: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} RTKdata.com uses port **2101**. Some DJI tutorials and third-party NTRIP services reference port 2103. Using the wrong port will result in a silent connection failure. Always use **2101** for RTKdata.com. {% endhint %} {% endstep %} {% step %} ### Wait for GNSS fix, then connect 1. Before tapping **Connect**, wait until the aircraft status shows a valid GNSS position (satellite count and position indicators are active in the status bar). 2. Tap **Connect** to start the NTRIP stream. 3. The RTK status will progress: **No Corrections → Single → Float → FIX**. {% hint style="warning" %} If you connect NTRIP before the aircraft has a GNSS fix, the GGA message sent to the server will contain coordinates of 0,0. The caster cannot generate corrections without a valid position. If this happens, disconnect, wait for a GNSS fix, then reconnect. {% endhint %} **How to verify RTK is working:** * **RTK status** in the top status bar shows **FIX** (green "RTK" indicator). * **Positioning accuracy** drops to **1–2 cm** horizontal in the RTK panel. * **Satellite count** shows 15+ satellites being tracked. * During mapping missions, the flight log records RTK FIX status for each photo capture. {% endstep %} {% endstepper %} ## Troubleshooting | Problem | Cause | Fix | | -------------------------------------------------- | ------------------------------ | ---------------------------------------------------------- | | "D-RTK 2" selected instead of "Custom Network RTK" | Wrong RTK source type | Switch to **Custom Network RTK** under RTK Service Type | | Port set to 2103 | Confused with other services | RTKdata.com uses port **2101** exclusively | | Connected but stuck on FLOAT | No GNSS fix when NTRIP started | Disconnect, wait for satellite lock, reconnect | | "Connection failed" or timeout | No internet or wrong hostname | Verify controller internet access; check hostname and port | | Mountpoint not found | Lowercase or misspelled | Enter `AUTO` in ALL CAPS | | RTK FIX drops during flight | Weak internet on controller | Use a dedicated mobile hotspot with strong signal | ## Tips for DJI Pilot 2 * **Always wait for GNSS lock before connecting NTRIP.** This is the single most common issue with DJI RTK setups. * **Check RTK status per photo.** After mapping flights, review EXIF data to confirm every image has RTK FIX. * **Pre-flight checklist:** Controller online → Aircraft linked → GNSS fix confirmed → NTRIP connected → FIX achieved → Start mission. * **Terrain Follow missions** benefit especially from RTK, as altitude reference becomes much more precise. * **DJI Pilot 2 remembers settings.** The last Custom Network RTK configuration persists, so you enter credentials only once per controller. * **Keep firmware current.** DJI occasionally patches RTK-related bugs in firmware updates for both aircraft and controller. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Surveying](https://rtkdata.com/surveying/) # u-center NTRIP Setup: u-blox ZED-F9P RTK Configure the u-center NTRIP client for u-blox ZED-F9P boards with RTKdata. Set COM port, baud rate, host, port 2101 and AUTO mountpoint to verify RTK fix. u-center is a free Windows desktop application from u-blox for configuring, testing, and monitoring u-blox GNSS receivers. It is the primary tool for working with u-blox ZED-F9P chips found in popular RTK boards such as the SparkFun RTK Facet, SparkFun RTK Express, ArduSimple simpleRTK2B, and standalone ZED-F9P evaluation kits. u-center includes a built-in NTRIP client that streams corrections from RTKdata.com directly to the receiver over USB, making it ideal for bench testing, firmware configuration, and verifying RTK performance. **Download:** [u-blox u-center](https://www.u-blox.com/en/product/u-center) (Windows, free) {% hint style="info" %} **u-center v1 vs. u-center 2:** This guide covers the classic u-center (v1), which remains the most widely deployed version. u-center 2 has a redesigned interface — the NTRIP client is located under **Receiver → Correction Services → NTRIP** instead of **Receiver → NTRIP Client**. All field values remain the same. {% endhint %} ## Requirements * u-blox ZED-F9P receiver board or device (SparkFun, ArduSimple, etc.) * Multi-band GNSS antenna connected to the receiver * USB cable connecting the receiver to your Windows PC * Windows PC with u-center installed and internet access * Active RTKdata.com account with username and password {% 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 %} ### Connect the receiver via USB 1. Connect your u-blox F9P board to your PC via USB. 2. Launch u-center. 3. In the toolbar, click the **COM port dropdown** (top-left) and select the correct COM port. If unsure, check **Windows Device Manager → Ports (COM & LPT)** for the u-blox device. 4. Set the **baud rate** to match your receiver's configuration. Click the baud rate dropdown next to the COM port selector. * **Common baud rates:** 38400 (SparkFun default), 115200 (ArduSimple default), 9600 (u-blox factory default) 5. Click the **Connect** button (plug icon) or press **Ctrl+F9**. 6. The bottom status bar should begin showing satellite data, confirming the connection is active. {% hint style="warning" %} **Baud Rate Troubleshooting:** If the status bar shows no data or garbage characters, the baud rate is wrong. Try 38400, 115200, then 9600 until you see valid NMEA sentences in the **Text Console** (**View → Text Console**). The correct baud rate will immediately produce readable position data. {% endhint %} {% endstep %} {% step %} ### Verify satellite reception 1. Open **View → Docking Windows → Satellite Level** to see the satellite sky plot. 2. Confirm bars appear for GPS, Galileo, BeiDou, and/or GLONASS. 3. The **Fix Mode** indicator in the status bar should show at least **3D Fix** before proceeding. {% endstep %} {% step %} ### Open the NTRIP client 1. Go to **Receiver → NTRIP Client...** in the menu bar. 2. The NTRIP Client dialog will open. {% endstep %} {% step %} ### Enter RTKdata.com connection settings Fill in the NTRIP Client fields: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% endstep %} {% step %} ### Start the NTRIP stream 1. Click **OK** or **Connect** to start the connection. 2. A green NTRIP icon will appear in the toolbar when the connection is active. 3. Monitor the **Fix Mode** in the bottom status bar: **3D → DGNSS → FLOAT → FIX**. 4. Convergence to RTK FIX typically takes 15–60 seconds with good sky conditions. **How to verify RTK is working:** * **Fix Mode** in the status bar displays **RTK FIX** (GGA fix quality = 4). * **Accuracy estimates** in the Navigation window (**View → Docking Windows → Navigation**) show horizontal accuracy of **0.01–0.02 m**. * The **NTRIP icon** in the toolbar stays green with no red indicators. * In the **Text Console** (**View → Text Console**), GGA messages show fix quality = 4 (RTK FIX) or 5 (Float). {% endstep %} {% endstepper %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------------- | ---------------------------------- | --------------------------------------------------------------- | | No data after connecting COM port | Wrong baud rate | Try 38400, 115200, or 9600 | | "Connection failed" in NTRIP Client | Wrong hostname/port or no internet | Verify hostname, confirm port `2101`, check internet | | NTRIP connects but stays on FLOAT | No initial 3D fix (GGA = 0,0) | Wait for 3D fix before starting NTRIP | | Mountpoint error | Lowercase or misspelled | Enter `AUTO` in ALL CAPS | | "Timeout" errors | Firewall blocking port 2101 | Add u-center to firewall exceptions; allow outbound TCP on 2101 | | Corrections received but no RTK improvement | Antenna indoors or obstructed | Move antenna to clear 360-degree sky view | ## Tips for u-center * **u-center is a configuration and testing tool, not a field tool.** Use it to verify your F9P board works with RTKdata.com before deploying with a mobile app like SW Maps. * **Save configuration to flash.** After confirming RTK works, go to **View → Configuration View → CFG** and send "Save current configuration." This stores settings in non-volatile memory. * **Monitor RTCM data.** The **Packet Console** (**View → Packet Console**) shows raw UBX and NMEA messages, including incoming RTCM3 correction data. * **GGA output rate.** Ensure the receiver outputs GGA at 1 Hz. Check via **View → Configuration View → MSG**. * **Multi-receiver setups.** u-center supports multiple simultaneous COM port connections for testing several F9P boards at once. ## Related Industry Solutions * [Robotics](https://rtkdata.com/robotics/) * [Transportation](https://rtkdata.com/transportation/) # Septentrio RxTools NTRIP Setup: DataLink & Web UI Stream RTKdata NTRIP corrections to Septentrio mosaic and AsteRx receivers using RxTools DataLink or the web interface. Port 2101, AUTO mountpoint, GGA at 1 Hz. RxTools is a desktop software suite from Septentrio for configuring and monitoring Septentrio GNSS receivers such as the mosaic-X5, mosaic-H, AsteRx-m3, and AsteRx SB series. The suite includes two key applications: **RxControl** for real-time receiver monitoring and configuration, and **DataLink** for serial and network data routing. To stream NTRIP corrections from RTKdata.com to a Septentrio receiver, you use DataLink as the NTRIP client to bridge correction data to the receiver. Alternatively, the receiver's built-in web interface offers a simpler path for users who prefer browser-based configuration. **Download:** [Septentrio RxTools](https://www.septentrio.com/en/products/software/rxtools) (Windows, free) ## Requirements * Septentrio GNSS receiver (mosaic-X5, mosaic-H, AsteRx series, etc.) * Multi-band GNSS antenna with clear sky view * USB or serial cable connecting the receiver to your Windows PC * Windows PC with RxTools installed and internet access * Active RTKdata.com account with username and password {% 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 (DataLink method) {% stepper %} {% step %} ### Connect the receiver with RxControl 1. Connect your Septentrio receiver to the PC via USB or serial cable. 2. Launch **RxControl** from the RxTools suite. 3. Go to **File → New Connection** and select USB or the appropriate COM port. 4. Click **Connect**. RxControl will display receiver status, satellite tracking, and position data. 5. Verify that the receiver is tracking satellites and has at least a standalone position fix. {% endstep %} {% step %} ### Configure NMEA GGA output Before setting up DataLink, ensure the receiver outputs GGA messages so the NTRIP caster can determine your approximate position. 1. In RxControl, go to **Navigation → Advanced Output Settings**. 2. Under **NMEA Output**, enable **GGA** on the connection port (USB1 or COM1) at a **1-second interval**. 3. Apply the settings. {% hint style="warning" %} **Why GGA matters:** RTKdata.com uses the `AUTO` mountpoint to generate a Virtual Reference Station based on your position. Without GGA output, the caster cannot determine your location and will not send appropriate corrections. This is the most common reason for NTRIP connections that appear active but produce no RTK improvement. {% endhint %} {% endstep %} {% step %} ### Launch DataLink and create connections 1. Launch **DataLink** from the RxTools suite (or from RxControl via **Tools → DataLink**). 2. You need to create two connections and bridge them: **Connection 1 — Serial Port (to the receiver):** 1. Click **New Connection → Serial Port**. 2. Select the COM port or USB port connected to your Septentrio receiver. 3. Set the baud rate to **115200** (default for most Septentrio receivers). 4. Click **OK**. **Connection 2 — NTRIP Client (to RTKdata.com):** 1. Click **New Connection → NTRIP Client**. 2. Fill in the connection fields: * **Send NMEA GGA:** **Enabled** {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% endstep %} {% step %} ### Bridge the two connections 1. In DataLink, select both connections. 2. Click **Link** or drag one connection onto the other to create a bidirectional bridge. 3. The bridge routes GGA from the receiver to the NTRIP caster, and RTCM corrections from the caster to the receiver. 4. Data flow indicators should show bytes moving in both directions. {% endstep %} {% step %} ### Monitor RTK convergence in RxControl 1. Switch back to RxControl. 2. Open the **Position** window and the **PVT Status** panel. 3. Watch the solution type progress: **Standalone → DGPS → RTK Float → RTK FIX**. 4. Once **RTK FIX** appears, centimeter-level accuracy is achieved. **How to verify RTK is working:** * **PVT Mode** in RxControl shows **RTK Fixed** (solution type 4). * **Horizontal accuracy** drops to **0.01–0.02 m**. * **Correction age** stays below 5 seconds. * DataLink shows active bidirectional data flow (byte counters incrementing). * Satellite Tracking view shows differential corrections applied (satellites marked with "D"). {% endstep %} {% endstepper %} ## Alternative: Web interface method Septentrio receivers include a built-in web interface that can configure NTRIP directly, bypassing DataLink entirely. 1. Connect the receiver via USB and open a browser to `http://192.168.3.1` (default IP). 2. Navigate to **Communication → NTRIP Client**. 3. Enter the same RTKdata.com connection settings from the tabs above. 4. Enable the NTRIP client and monitor status from the web dashboard. {% hint style="info" %} The web interface method is simpler and recommended for field deployments where you do not want to run desktop software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------ | -------------------------- | ----------------------------------------------------------------------------- | | DataLink NTRIP connection fails | Wrong hostname or port | Verify hostname; confirm port is `2101` | | Connected but no corrections applied | Bridge not configured | Ensure serial and NTRIP connections are linked bidirectionally in DataLink | | Stuck on FLOAT | GGA not sent to caster | Enable GGA output at 1 Hz on the receiver port; check DataLink GGA forwarding | | "Mountpoint not found" | Lowercase or wrong name | Enter `AUTO` in ALL CAPS | | COM port busy or unavailable | Another app using the port | Close other serial tools; use separate ports for RxControl and DataLink | | Position jumps erratically | Multipath interference | Move antenna away from reflective surfaces; use a ground plane | ## Tips for Septentrio RxTools * **DataLink is a routing tool.** It passes data between caster and receiver without processing corrections. * **RxControl diagnostics.** Use built-in sky plots, position scatter plots, and C/N0 views to diagnose signal quality. * **Keep firmware current.** Septentrio firmware updates improve NTRIP handling and RTK convergence time. * **Advanced mountpoints.** For specific reference frames, use `AUTO_ITRF2020` or `AUTO_ITRF2014` instead of `AUTO`. * **Concurrent logging.** RxControl can log raw SBF data while receiving corrections for post-processing QC. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Robotics](https://rtkdata.com/robotics/) * [Transportation](https://rtkdata.com/transportation/) # EOS Tools Pro NTRIP Setup: Arrow GNSS RTK Stream RTKdata NTRIP corrections to EOS Arrow Gold and Arrow 200 via EOS Tools Pro. Set port 2101, AUTO mountpoint and Android mock location for GIS RTK. EOS Tools Pro is the official companion app for EOS Positioning Systems' Arrow series GNSS receivers, including the Arrow Gold, Arrow Gold+, Arrow 100, and Arrow 200. Available on iOS and Android, it manages Bluetooth connectivity, NTRIP correction streaming, position monitoring, and receiver diagnostics. When paired with RTKdata.com, EOS Tools Pro delivers centimeter-level RTK corrections to your Arrow receiver for high-accuracy GIS data collection, surveying, and asset management. **Download:** [App Store (iOS)](https://apps.apple.com/app/eos-tools-pro/id1436038498) | [Google Play (Android)](https://play.google.com/store/apps/details?id=com.eos.toolspro) ## Requirements * EOS Arrow receiver (Arrow Gold, Arrow Gold+, Arrow 100, or Arrow 200) with antenna * Smartphone or tablet running EOS Tools Pro (iOS or Android) * Bluetooth enabled on your phone * Internet access (mobile data or Wi-Fi) * Survey pole or tripod with clear sky view * Active RTKdata.com account with username and password {% 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 %} ### Pair and connect the Arrow receiver via Bluetooth 1. Turn on your EOS Arrow receiver. The LED indicators will flash as it initializes. 2. Open EOS Tools Pro on your phone. 3. Tap the **Bluetooth** icon or go to **Settings → Bluetooth Connection**. 4. The app will scan for nearby Arrow devices. Tap your receiver name to pair and connect. 5. Once connected, EOS Tools Pro displays satellite tracking and a position. Wait for at least a **3D fix** before configuring NTRIP. {% hint style="info" %} **Bluetooth Pairing Tip:** If your Arrow receiver does not appear in the scan list, ensure it is in pairing mode (check the LED pattern in your Arrow user manual). On Android, you may need to pair the device in your phone's system Bluetooth settings first, then connect from within EOS Tools Pro. {% endhint %} {% endstep %} {% step %} ### Open the correction source menu 1. In EOS Tools Pro, tap the **Settings** gear icon. 2. Navigate to **Correction Source** (labeled **Differential/NTRIP** in some versions). 3. Select **NTRIP** as the correction type. {% endstep %} {% step %} ### Create a new NTRIP profile 1. Tap **Add New Profile** or the **+** button. 2. Enter a profile name (e.g., "RTKdata Europe" or "RTKdata NA"). {% endstep %} {% step %} ### Enter RTKdata.com connection settings Fill in the NTRIP fields: * **Send NMEA GGA to Caster:** **ON** {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% endstep %} {% step %} ### Connect and wait for RTK FIX 1. Tap **Save** to store the profile, then tap **Connect**. 2. EOS Tools Pro establishes the NTRIP connection and begins streaming corrections to the Arrow receiver. 3. Monitor the solution status: **Autonomous → Float → FIX**. 4. Once **FIX** appears, you have centimeter-level positioning. **How to verify RTK is working:** * **Solution indicator** shows **RTK FIX** (green badge or "Fixed" label). * **Horizontal accuracy** displays **0.01–0.02 m** (1–2 cm). * **NTRIP status** shows active connection with bytes being received. * **Satellite panel** shows corrections applied to tracked satellites. * **Correction age** remains under 5 seconds. {% endstep %} {% endstepper %} ## Mock location for third-party GIS apps EOS Arrow receivers can feed RTK-corrected positions to other Android apps (Esri Field Maps, QGIS, Mapit GIS, etc.) using Android's mock location feature. This allows EOS Tools Pro to handle NTRIP corrections in the background while your GIS app receives the corrected position. **To enable mock location on Android:** 1. Go to **Android Settings → Developer Options** (enable Developer Options first if needed). 2. Set **Mock Location App** to **EOS Tools Pro**. 3. Open EOS Tools Pro, connect to the Arrow receiver, and start NTRIP corrections. 4. Open your GIS app — it will now receive the RTK-corrected position from the Arrow receiver instead of the phone's internal GPS. {% hint style="info" %} On iOS, mock location is handled automatically through the Bluetooth connection. No additional configuration is needed. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------- | ----------------------------------------- | ------------------------------------------------------------------- | | Arrow not found in Bluetooth scan | Bluetooth disabled or not in pairing mode | Enable Bluetooth; confirm Arrow is powered and in pairing mode | | "Authentication failed" | Wrong username or password | Verify credentials; username starts with `rtk` | | Connected but stuck on FLOAT | GGA not sent to caster | Enable **Send NMEA GGA to Caster** in NTRIP settings | | Mountpoint error | Not uppercase | Enter `AUTO` in ALL CAPS | | Accuracy stays at meter level | Poor sky or low satellite count | Move to open sky with 360-degree view | | App crashes during connection | Outdated app version | Update EOS Tools Pro from App Store or Google Play | | RTK drops frequently | Unstable internet | Switch between Wi-Fi and mobile data; ensure strong cellular signal | ## Tips for EOS Tools Pro * **Antenna height matters.** Set the correct pole height before collecting data. The app applies antenna offset for the specific Arrow model automatically. * **Battery management.** Arrow receivers consume more power during RTK. Carry a spare battery or power bank for long sessions. * **Profile persistence.** NTRIP profiles are saved in the app. Configure once per region. * **Firmware updates.** EOS releases Arrow firmware updates that improve RTK performance. Check for updates via EOS Tools Pro. * **Coordinate output.** EOS Tools Pro supports multiple coordinate formats. Ensure your GIS project's CRS matches the output format. * **RTKdata.com heights are ellipsoidal.** If you need orthometric heights (mean sea level), apply a geoid model in your GIS software or configure the Arrow's geoid settings. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Utilities](https://rtkdata.com/utilities/) # Lefebure NTRIP Client: Android RTK Corrections Setup Connect Lefebure NTRIP Client to RTKdata on Android. Stream RTK corrections to any Bluetooth GNSS receiver with centimeter-level accuracy. Free 30-day trial Lefebure NTRIP Client is the most popular standalone NTRIP client for Android. It connects to any Bluetooth GNSS receiver — including SparkFun RTK Facet, ArduSimple simpleRTK2B, Emlid Reach, and any u-blox ZED-F9P-based board — and streams RTK corrections from an NTRIP caster like RTKdata.com directly to your receiver. The app also supports Android mock locations, allowing other apps on your phone to use the centimeter-level corrected position. **Download:** [Google Play Store](https://play.google.com/store/apps/details?id=com.lefebure.ntripclient) (free) ## Requirements * **Android phone or tablet** with Bluetooth and internet access (cellular data or Wi-Fi) * **Bluetooth-capable GNSS receiver** (SparkFun RTK, ArduSimple, or any receiver outputting NMEA over Bluetooth) * **GNSS antenna** with clear sky view * **RTKdata.com account** with active RTK credentials (username starting with `rtk`) {% 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 %} #### Install and open the app 1. Install **Lefebure NTRIP Client** from the Google Play Store. 2. Launch the app. You will see the main screen with connection status and data stream panels. 3. Grant all requested permissions (Bluetooth, Location). {% endstep %} {% step %} #### Pair your Bluetooth GNSS receiver 1. Power on your GNSS receiver and ensure Bluetooth is enabled on it. 2. On your Android phone, go to **Settings > Bluetooth** and pair with your receiver (e.g., "RTK\_GNSS", "RTK Facet-XXXX", or "SparkFun RTK"). 3. Return to Lefebure. Tap the **gear icon** (Settings) in the top-right corner. 4. Under **Receiver Connection**, tap **Bluetooth Device** and select your paired receiver from the list. 5. Set **Baud Rate** to match your receiver (typically **115200** or **38400**). {% endstep %} {% step %} #### Configure the NTRIP profile In Settings, scroll to the **NTRIP** section and enter the following: {% tabs %} {% tab title="North America" %} * **Caster Host:** `rtk.rtkdata.com` * **Caster IP (fallback):** `13.56.117.10` * **Caster 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` {% endtab %} {% tab title="Europe" %} * **Caster Host:** `eu.rtkdata.com` * **Caster IP (fallback):** `3.73.41.96` * **Caster 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` {% endtab %} {% tab title="Australia" %} * **Caster Host:** `aus.rtkdata.com` * **Caster IP (fallback):** `54.206.56.130` * **Caster 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` {% endtab %} {% endtabs %} {% hint style="danger" %} **"Send NMEA to Server" must be ON.** This is the number one issue users encounter. Without sending NMEA GGA to the caster, RTKdata.com cannot determine your position and cannot generate Virtual Reference Station corrections. You will see "0 GGA sessions" on your RTKdata dashboard and corrections will never arrive. {% endhint %} {% endstep %} {% step %} #### Enable GGA output 1. Still in Settings, find **Send NMEA to Server** (sometimes labeled "Send NMEA GGA to Caster"). 2. Set this to **ON / Enabled**. 3. Set the **GGA send interval** to **5 seconds** (default is fine). 4. Confirm by checking that the data stream panel shows outgoing GGA sentences after connecting. {% endstep %} {% step %} #### Set up mock locations (optional) To make other Android apps (e.g., Google Maps, field collection apps) use the RTK-corrected position: 1. On your phone, go to **Settings > About Phone** and tap **Build Number** 7 times to enable Developer Options. 2. Go to **Settings > Developer Options > Select mock location app**. 3. Choose **Lefebure NTRIP Client** from the list. 4. Return to Lefebure. In Settings, enable **Mock Location Provider**. {% hint style="info" %} With mock locations enabled, every app on your phone will use the centimeter-level position from your external receiver instead of the phone's internal GPS. {% endhint %} {% endstep %} {% step %} #### Connect and verify RTK Fix 1. Return to the main screen and tap **Connect** (the play button). 2. The app will connect to your Bluetooth receiver and to the RTKdata NTRIP caster simultaneously. 3. Monitor the status display: * **NMEA stream:** You should see GGA, GSA, and GSV sentences flowing. * **RTCM stream:** Incoming correction data bytes should increment steadily. * **Fix type** progresses: **GPS Fix > DGPS > Float > Fix**. 4. Once **Fix** is shown, accuracy is at centimeter level. Typical convergence is 30-90 seconds. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). If your project requires orthometric heights, apply a geoid model in your GIS or surveying software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | 0 GGA sessions on RTKdata dashboard | "Send NMEA to Server" is OFF | Enable **Send NMEA to Server** in Lefebure settings. This is required for VRS corrections. | | "Server TCP Error" | Incorrect host, port, or no internet | Verify hostname spelling, port `2101`, and that your phone has an active data connection. Try the IP fallback address. | | Connection drops repeatedly | Weak cellular signal or app sleeping | Disable battery optimization for Lefebure in Android settings. Keep the app in the foreground. | | Bluetooth pairs but no NMEA data | Wrong baud rate or receiver not outputting NMEA | Match the baud rate in Lefebure to the receiver's Bluetooth baud rate (typically 115200). | | Stuck on Float, never reaches Fix | GGA not being sent or poor sky view | Confirm GGA is enabled. Move to open sky. Check satellite count (need 10+ satellites). | | Mountpoint error | Lowercase or misspelled mountpoint | Type `AUTO` in ALL CAPS. Do not attempt to browse the source table. | ## Tips and tricks * **"Send NMEA to Server" is non-negotiable.** Verify this setting every time you troubleshoot. It is the single most common cause of failed connections. * **Lefebure works with virtually any Bluetooth GNSS receiver** — SparkFun RTK, ArduSimple, Emlid, Bad Elf, EOS Arrow, and generic u-blox boards. * **Use the data stream panel** to confirm both outgoing GGA and incoming RTCM. If GGA lines are flowing but RTCM bytes stay at zero, the caster is not responding — check your credentials. * **Mock locations are powerful.** Once configured, apps like DroneDeploy, ArcGIS Field Maps, and Collector can use RTK-corrected positions natively. * **For persistent connection issues**, try switching from hostname to the direct IP address for your region. Some mobile networks have DNS resolution delays. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Agriculture](https://rtkdata.com/agriculture/) # Carlson SurvPC / SurvCE NTRIP RTK Setup Connect Carlson SurvPC or SurvCE to RTKdata NTRIP corrections. Configure your GPS rover, NTRIP host, port 2101 and AUTO mountpoint for centimeter RTK fix. Carlson SurvPC and SurvCE are popular third-party survey data collection software packages widely used across North America and worldwide. SurvPC runs on Windows tablets and laptops, while SurvCE runs on Windows CE and Windows Mobile handhelds. Both include a built-in NTRIP client and support most major GNSS receiver brands, making them an excellent choice for connecting to RTKdata.com RTK corrections in the field. **Download:** [Carlson SurvPC / SurvCE](https://www.carlsonsw.com/products/field-data-collection/) (commercial license required) ## Requirements * Windows tablet, laptop, or Windows CE/Mobile data collector running SurvPC or SurvCE * Compatible GNSS receiver (Carlson, Hemisphere, Topcon, Trimble, Leica, or generic NMEA) * Internet access on the field device (cellular data, Wi-Fi, or phone hotspot) * GNSS antenna with clear sky view (survey pole or tripod recommended) * Active RTKdata.com account with RTK credentials (username starting with `rtk`) {% 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 %} ### Configure GPS rover equipment 1. Open SurvPC/SurvCE and create or open a job. 2. Go to **Equip > GPS Rover**. 3. Select the correct **GPS Brand/Model** from the dropdown that matches your receiver hardware (e.g., "Carlson BRx7", "Hemisphere", "Generic NMEA"). 4. Set the **COM Port** and **Baud Rate** to match your receiver connection (Bluetooth serial, USB, or cable). 5. Set the **Antenna Height** and select the correct measurement method (bottom of antenna, phase center, etc.). 6. Tap **OK** to save the equipment profile. {% hint style="warning" %} **Selecting the wrong GPS brand or model** is the most common configuration mistake. SurvPC/SurvCE sends specific initialization commands based on the selected model. An incorrect selection can prevent the receiver from outputting corrections properly or cause communication failures. {% endhint %} {% endstep %} {% step %} ### Set up the internet connection 1. From the GPS Rover screen (or go to **Equip > GPS Rover > Internet**), select the **Internet** tab. 2. Choose your connection type: * **Direct IP** — recommended for most setups using Wi-Fi or a tethered phone hotspot. * **Cellular Modem** — if your data collector has a built-in modem. * **Bluetooth Phone** — to dial through a paired smartphone (legacy method). 3. For **Direct IP**, ensure your device is already connected to the internet via Wi-Fi or USB tethering before proceeding. {% hint style="info" %} **Phone hotspot tip:** Connect your data collector to your smartphone's Wi-Fi hotspot before opening SurvPC. Select **Direct IP** as the connection type — this is the simplest and most reliable method. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings 1. In the Internet tab, select **NTRIP** as the correction delivery method. 2. Fill in the connection fields: {% tabs %} {% tab title="North America" %} * **Caster Address:** `rtk.rtkdata.com` * **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` {% endtab %} {% tab title="Europe" %} * **Caster Address:** `eu.rtkdata.com` * **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` {% endtab %} {% tab title="Australia" %} * **Caster Address:** `aus.rtkdata.com` * **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` {% endtab %} {% endtabs %} 3. Ensure **Send GGA to Caster** is enabled. RTKdata.com requires your GGA position to generate Virtual Reference Station corrections. {% endstep %} {% step %} ### Connect and begin surveying 1. Tap **Connect** (the green arrow or connect button) to start receiving corrections. 2. Monitor the solution status in the SurvPC/SurvCE skyplot or status bar: * **Autonomous** — no corrections yet * **DGPS / Float** — corrections arriving, solution converging * **Fixed** — centimeter-level accuracy achieved 3. Convergence to Fix typically takes 15–60 seconds with clear sky view. 4. Begin your survey using **Store Points**, **Stakeout**, or **Topo Survey** routines. {% hint style="info" %} SurvPC displays horizontal and vertical precision estimates on the store-point screen. Always verify the solution is **Fixed** and precision is below your project tolerance before storing control points. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). SurvPC/SurvCE can apply a geoid model to convert to orthometric heights. Configure this under **Job > Coordinate System > Geoid** and select the appropriate model for your region (e.g., GEOID18 for the US). {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------ | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | Receiver not communicating | Wrong GPS brand/model or COM port | Re-select the exact manufacturer and model in **Equip > GPS Rover**. Verify the COM port matches the Bluetooth or USB connection. | | "Unable to connect to caster" | No internet or wrong host/port | Confirm the device has internet access first. Double-check hostname and port `2101`. Try the IP fallback. | | Stuck on Float, never reaches Fix | GGA not being sent | Verify **Send GGA to Caster** is enabled. Without GGA, VRS corrections cannot be computed. | | Mountpoint error | Lowercase or misspelled mountpoint | Enter `AUTO` in ALL CAPS. Do not browse the source table — type it directly. | | Internet drops during survey | Phone hotspot going to sleep | Disable auto-sleep on the hotspot phone. Keep the hotspot app in the foreground or disable battery optimization. | | Corrections arrive but poor accuracy | Obstructed sky or wrong antenna height | Move to open sky, verify the antenna height entry, and check that the measurement method matches your setup. | ## Tips for best results * **Double-check your GPS brand/model selection** before troubleshooting anything else. This is the root cause of most SurvPC/SurvCE connection issues. * **Use Direct IP over a phone hotspot** for the most reliable internet connection. It is simpler than Bluetooth DUN or built-in modems. * **Save your NTRIP settings in a job template** so all new jobs inherit the correct RTKdata.com configuration automatically. * **Monitor satellite count** in the skyplot view. Aim for 12+ tracked satellites for fast and stable Fix convergence. * **For Windows CE devices**, ensure the device clock is set correctly. An incorrect system time can cause NTRIP authentication to fail. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # FieldGenius NTRIP Setup: Windows & Android RTK Connect MicroSurvey FieldGenius on Windows or Android to RTKdata NTRIP. Set the instrument profile, host, port 2101 and AUTO mountpoint for centimeter RTK fix. MicroSurvey FieldGenius is a professional survey field software developed by MicroSurvey (a Hexagon company). Available for both Windows and Android, it supports a wide range of GNSS receivers including Trimble, Leica, Topcon, and generic NMEA devices. Its built-in NTRIP client makes it straightforward to connect to RTKdata.com and receive real-time RTK corrections for centimeter-level positioning in the field. **Download:** [MicroSurvey FieldGenius](https://www.microsurvey.com/products/fieldgenius/) (commercial license required) ## Requirements * Windows tablet/laptop or Android device running FieldGenius * Compatible GNSS receiver (Trimble, Leica, Topcon, or any generic NMEA receiver) * Internet access on the field device (cellular data, Wi-Fi, or hotspot) * GNSS antenna with clear sky view (survey pole or tripod recommended) * Active RTKdata.com account with RTK credentials (username starting with `rtk`) {% 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 %} ### Configure your instrument profile 1. Open FieldGenius and create or open a project. 2. Go to **Survey > Instrument > Select Instrument**. 3. Choose the correct **manufacturer and model** that matches your GNSS receiver hardware. 4. If your receiver is not listed, select **Generic NMEA** as the instrument type. 5. Set the **communication port** (COM port) to match the connection to your receiver — Bluetooth serial port, USB, or internal. 6. Tap **Connect** to verify that FieldGenius communicates with the receiver. You should see satellite tracking and a standalone position. {% hint style="warning" %} **Instrument profile mismatch** is the most common setup error. If you select the wrong manufacturer or model, FieldGenius may fail to communicate with the receiver or send incorrect commands. Always verify the exact model in your receiver's documentation. {% endhint %} {% endstep %} {% step %} ### Set up the internet connection 1. Go to **Survey > Instrument > Internet Setup** (or **Configure Internet**). 2. Select your internet connection method: * **Internal modem** — if your data collector has a built-in cellular modem. * **Bluetooth DUN / Phone tether** — for connecting via a smartphone hotspot. * **Wi-Fi / Direct IP** — if connected to a Wi-Fi network. 3. Verify that the device has an active internet connection before proceeding. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings 1. In the Internet Setup screen, select **NTRIP** as the correction source type. 2. Fill in the following connection fields: {% tabs %} {% tab title="North America" %} * **Caster Address:** `rtk.rtkdata.com` * **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` {% endtab %} {% tab title="Europe" %} * **Caster Address:** `eu.rtkdata.com` * **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` {% endtab %} {% tab title="Australia" %} * **Caster Address:** `aus.rtkdata.com` * **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` {% endtab %} {% endtabs %} 3. Ensure **Send GGA Position** is enabled. RTKdata.com requires your approximate position (GGA) to compute Virtual Reference Station corrections. {% endstep %} {% step %} ### Connect and begin surveying 1. Tap **Connect** to start the NTRIP correction stream. 2. Monitor the solution status in the FieldGenius status bar as it progresses: **Autonomous > DGPS > Float > Fix**. 3. Once the status shows **RTK Fix**, you have centimeter-level accuracy. Convergence typically takes 15–60 seconds under open sky. 4. Begin your survey — use **Store Point**, **Stakeout**, or **Topo** as needed. {% hint style="info" %} FieldGenius displays the solution quality and number of satellites in the status bar. Verify **Fix** status before storing critical survey points. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). FieldGenius can apply a local geoid model to convert ellipsoidal heights to orthometric. Configure this under **Project > Coordinate System > Geoid Model**. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ---------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------ | | Receiver not responding | Wrong instrument profile or COM port | Re-check the manufacturer/model selection and verify the correct COM port under Instrument settings | | "Connection failed" on NTRIP | Incorrect host, port, or no internet | Double-check the hostname, port `2101`, and that your device has active internet. Try the IP fallback. | | Stuck on Float indefinitely | GGA not being sent to caster | Confirm **Send GGA Position** is enabled. Without GGA, VRS corrections cannot be generated. | | Mountpoint error | Lowercase or misspelled mountpoint | Enter `AUTO` in ALL CAPS. Do not use `auto` or `Auto`. | | COM port busy or unavailable | Another app is using the serial port | Close other apps that may be accessing the receiver's Bluetooth or USB serial connection. | | Poor accuracy even with Fix | Bad sky view or incorrect antenna height | Move to open sky, re-measure the antenna height, and ensure the pole is level. | ## Tips for best results * **Match the instrument profile exactly** to your receiver hardware. This is the single most important configuration step in FieldGenius. * **Test the internet connection** before configuring NTRIP. A failed hotspot or cellular connection is easier to diagnose separately. * **Save your NTRIP profile** within the project template so you do not need to re-enter credentials for each new project. * **Use the satellite tracking screen** to verify at least 10–12 satellites before expecting a reliable Fix. * **For Windows tablets**, ensure power management does not disable Bluetooth or Wi-Fi when the screen turns off. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # QField RTK Setup: Centimeter NTRIP Corrections Get centimeter RTK in QField for QGIS using RTKdata corrections. Feed positions via Lefebure mock location or a receiver NTRIP client, port 2101, AUTO mountpoint. QField is a free, open-source mobile GIS application for Android and iOS, designed as the field companion to QGIS desktop. It excels at offline-capable data collection and works seamlessly with QGIS projects. QField does **not** have a built-in NTRIP client, so RTK corrections must be provided externally — either through a companion NTRIP app (such as Lefebure NTRIP Client or SW Maps) that sets Android mock locations, or through a GNSS receiver with its own internal NTRIP client. Once corrected positions are available, QField reads them automatically. **Download:** [QField on Google Play](https://play.google.com/store/apps/details?id=ch.opengis.qfield) | [QField on App Store](https://apps.apple.com/app/qfield-for-qgis/id1531726814) (free) ## Requirements * Android or iOS device with internet access (cellular data or Wi-Fi) * Bluetooth-capable GNSS receiver (SparkFun RTK, ArduSimple, Emlid Reach, or any NMEA receiver) * An NTRIP source — one of the following: * **Lefebure NTRIP Client** or **SW Maps** installed on the same Android device (for mock location approach) * A GNSS receiver with built-in NTRIP client (e.g., Emlid Reach, SparkFun RTK Facet with Wi-Fi) * Active RTKdata.com account with RTK credentials (username starting with `rtk`) {% 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 %} ### Connect your Bluetooth GNSS receiver 1. Power on your GNSS receiver and enable Bluetooth. 2. On your phone, go to **Settings > Bluetooth** and pair with the receiver. 3. Verify the pairing is successful before continuing. {% hint style="warning" %} **QField does not manage Bluetooth GNSS connections directly.** The corrected position must be delivered to QField through Android mock locations or through the receiver's own NTRIP connection. The steps below explain both approaches. {% endhint %} {% endstep %} {% step %} ### Set up NTRIP corrections (Option A: Lefebure NTRIP Client) This is the recommended approach for most users. Lefebure handles the NTRIP connection and feeds the corrected position to QField via Android mock locations. 1. Install **Lefebure NTRIP Client** from the Google Play Store. 2. Open Lefebure and configure the Bluetooth receiver connection (see the [Lefebure setup guide](/integration-hub/ntrip-clients-and-field-software/lefebure-ntrip-client) for details). 3. Enter the RTKdata.com NTRIP settings: {% tabs %} {% tab title="North America" %} * **Caster Host:** `rtk.rtkdata.com` * **Caster IP (fallback):** `13.56.117.10` * **Caster 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` {% endtab %} {% tab title="Europe" %} * **Caster Host:** `eu.rtkdata.com` * **Caster IP (fallback):** `3.73.41.96` * **Caster 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` {% endtab %} {% tab title="Australia" %} * **Caster Host:** `aus.rtkdata.com` * **Caster IP (fallback):** `54.206.56.130` * **Caster 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` {% endtab %} {% endtabs %} 4. Enable **Send NMEA GGA to Server** — this is required for RTKdata.com VRS corrections. 5. Tap **Connect** in Lefebure. Wait for the solution to reach **RTK Fix**. {% endstep %} {% step %} ### Enable Android mock locations 1. On your phone, go to **Settings > About Phone** and tap **Build Number** 7 times to unlock Developer Options. 2. Go to **Settings > Developer Options > Select mock location app**. 3. Choose **Lefebure NTRIP Client** (or SW Maps, if using that instead). 4. Return to Lefebure and enable **Mock Location Provider** in its settings. 5. Verify mock locations are working: open Google Maps and confirm the blue dot shows centimeter-level accuracy matching Lefebure's reported position. {% hint style="info" %} With mock locations active, **every app** on your Android device — including QField — will automatically receive the RTK-corrected position from your external GNSS receiver. {% endhint %} {% endstep %} {% step %} ### Set up NTRIP corrections (Option B: Receiver with built-in NTRIP) If your receiver has a built-in NTRIP client (e.g., Emlid Reach via ReachView, SparkFun RTK Facet via Wi-Fi), you can configure RTKdata.com directly on the receiver: 1. Access your receiver's web interface or configuration app. 2. Enter the same RTKdata.com NTRIP settings shown in the tabs above. 3. The receiver handles corrections internally and outputs an already-corrected NMEA position over Bluetooth. 4. No mock location setup is needed — QField receives the corrected position directly from the Bluetooth connection. {% endstep %} {% step %} ### Open QField and collect data 1. Open QField and load your QGIS project. 2. QField will automatically use the device's location. With mock locations enabled (Option A) or a receiver outputting corrected positions (Option B), QField receives centimeter-level accuracy. 3. Tap the **crosshair** icon to center on your current position. 4. Verify accuracy: QField shows a position accuracy circle. With RTK Fix, this circle should be very small (1–2 cm). 5. Begin digitizing features, collecting points, or performing field inspections. {% hint style="info" %} **QGIS desktop post-processing:** You can also collect raw GNSS observations in the field and post-process them in QGIS using RTKdata.com RINEX data. This is useful for areas without cellular coverage. Contact RTKdata.com support for RINEX data availability. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). QField displays coordinates as received. If your project requires orthometric heights, apply a geoid model in your QGIS project settings before deploying to QField. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | QField shows phone GPS accuracy (5–15 m) | Mock locations not active or wrong app selected | Verify Developer Options > Mock location app is set to Lefebure. Confirm Lefebure's Mock Location Provider is enabled. | | Lefebure has Fix but QField still inaccurate | Mock location provider not enabled in Lefebure | Open Lefebure settings and toggle **Mock Location Provider** ON. | | NTRIP connects but stays on Float | GGA not being sent to caster | Enable **Send NMEA GGA to Server** in Lefebure. This is required for VRS corrections. | | Mountpoint error | Lowercase or misspelled mountpoint | Enter `AUTO` in ALL CAPS. | | QField cannot find project files | Project not synced to device | Transfer the QGIS project and all data layers to the device's QField folder via QFieldCloud or USB. | | Position jumps between phone GPS and receiver | Mock location toggling on/off | Ensure only one mock location provider is active. Disable the phone's internal location if needed. | ## Tips for best results * **Lefebure + QField is the most common RTK workflow** for open-source GIS users. Set up Lefebure first, confirm RTK Fix, then open QField. * **SW Maps is an alternative** to Lefebure for the mock location approach, and also works as a standalone data collection app. * **Prepare your QGIS project on desktop first.** Define layers, symbology, and forms in QGIS, then transfer to QField. This saves significant field time. * **For iOS users**, mock locations are not available. Use a receiver with a built-in NTRIP client (Option B) instead. * **Keep Lefebure running in the foreground** (or disable battery optimization) to prevent Android from killing the mock location provider during fieldwork. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Environmental Monitoring](https://rtkdata.com/environmental-monitoring/) * [Utilities](https://rtkdata.com/utilities/) # GNSS Master NTRIP Setup: Android Mock Location Use GNSS Master on Android to relay RTKdata NTRIP corrections to any app via mock location. Connect a u-blox F9P receiver, port 2101, AUTO mountpoint. GNSS Master is a free Android app developed by ArduSimple that acts as a universal bridge between an external GNSS receiver and any Android application. It connects to receivers via USB OTG, Bluetooth, BLE, or Wi-Fi/TCP, streams RTK corrections from an NTRIP caster like RTKdata.com, and provides the corrected position to other apps through Android mock locations. This makes it one of the most versatile NTRIP relay apps available — any Android app that uses location (Google Maps, ArcGIS Field Maps, DroneDeploy, etc.) can benefit from centimeter-level accuracy without needing its own NTRIP support. **Download:** [Google Play Store](https://play.google.com/store/apps/details?id=com.gnssmaster) (free) ## Key capabilities | Feature | Details | | -------------------------- | ------------------------------------------------------------------------------------- | | **Platform** | Android (phone or tablet) | | **Cost** | Free (PointPerfect corrections require a separate subscription from ArduSimple) | | **Receiver connection** | USB Serial (OTG), Bluetooth Classic, Bluetooth LE, Wi-Fi / TCP | | **NTRIP support** | Built-in NTRIP Client (V1 and V2) | | **Mock location relay** | Yes — broadcasts corrected position to all other Android apps | | **NTRIP Server mode** | Yes — can also function as an NTRIP server for base station setups | | **Receiver configuration** | Can change u-blox and Septentrio receiver settings (Rover, Base, custom config files) | ## Requirements * Android phone or tablet with USB OTG or Bluetooth * External GNSS receiver (ArduSimple simpleRTK2B, SparkFun RTK Facet, any u-blox F9P board, Septentrio, etc.) * Internet connection (cellular data or Wi-Fi) * Active RTKdata.com account with RTK 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 %} ### Connect your GNSS receiver 1. Connect your GNSS receiver to your Android device: * **USB OTG:** Plug the receiver into your phone/tablet using a USB OTG cable. Grant USB permission when prompted. * **Bluetooth:** Pair the receiver in Android Bluetooth settings first, then select it in the app. * **Wi-Fi/TCP:** Ensure both devices are on the same network. 2. Open **GNSS Master**. Access the navigation drawer by swiping from the left edge or tapping the GNSS Master icon in the top menu bar. 3. Go to the **Receiver** page and tap the **gear icon** next to **GNSS Receiver Connection**. 4. Select your connection type (USB Serial, Bluetooth, BLE, or TCP) and choose your device from the list. 5. Tap **Connect**. The status should change to **Connected** with data flowing. {% hint style="warning" %} For USB OTG connections, your Android device must support USB Host mode. Most modern Android phones and tablets do. If the receiver is not detected, try a different USB OTG cable — some charge-only cables do not support data. {% endhint %} {% endstep %} {% step %} ### Enable mock location output To relay the corrected position to other Android apps: 1. On your Android device, go to **Settings > About Phone** and tap **Build Number** 7 times to enable Developer Options. 2. Go to **Settings > Developer Options > Select mock location app** and choose **GNSS Master**. 3. In GNSS Master, check the **Mock Location** checkbox on the main screen. 4. Optionally, also check **Output to SW Maps** if you use SW Maps for data collection. {% hint style="info" %} With mock location enabled, every Android app on your device will use the RTK-corrected position from your external receiver instead of the phone's internal GPS. This includes Google Maps, any GIS app, and field data collection tools. {% endhint %} {% endstep %} {% step %} ### Configure the NTRIP correction source 1. Open the **Corrections** page by tapping **Correction Input** or navigating via the drawer. 2. In the **Mode** dropdown, select **NTRIP Client**. 3. Tap the **+** button next to **NTRIP Connections** to add a new profile. 4. In the NTRIP Client dialog, enter the following: {% tabs %} {% tab title="North America" %} * **NTRIP Address (Host):** `rtk.rtkdata.com` * **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` {% endtab %} {% tab title="Europe" %} * **NTRIP Address (Host):** `eu.rtkdata.com` * **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` {% endtab %} {% tab title="Australia" %} * **NTRIP Address (Host):** `aus.rtkdata.com` * **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` {% endtab %} {% endtabs %} 5. Check **Send NMEA GGA to Base Station**. This is required for RTKdata.com's VRS corrections. 6. Tap **Save**. {% hint style="danger" %} **"Send NMEA GGA to Base Station" must be checked.** Without GGA, RTKdata.com cannot determine your position and cannot generate Virtual Reference Station corrections. You will stay on FLOAT indefinitely. {% endhint %} {% endstep %} {% step %} ### Connect and verify RTK Fix 1. Select your saved NTRIP profile and tap **Connect**. 2. In the **Status** page, verify that both **GNSS Receiver Connection** and **Correction Input** show **Connected** with data flowing. 3. Monitor the solution status as it progresses: **Autonomous > Float > Fix**. 4. Once you see **RTK Fix**, the corrected position is being relayed to all apps via mock location. {% hint style="info" %} Convergence to Fix typically takes 15–60 seconds under clear sky. The NTRIP client stays connected even when the receiver temporarily disconnects, so corrections resume automatically when the receiver reconnects. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). If your workflow requires orthometric heights, apply a geoid model in your GIS or surveying software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------- | ------------------------------------ | ---------------------------------------------------------------------------------------- | | USB receiver not detected | USB OTG not supported or bad cable | Use a data-capable USB OTG cable. Check that your Android device supports USB Host mode. | | Bluetooth pairs but no data | Wrong receiver protocol or baud rate | Ensure the receiver outputs NMEA over Bluetooth. Check baud rate settings. | | NTRIP connects but stays on Float | GGA not sent to caster | Check **Send NMEA GGA to Base Station** in the NTRIP profile settings. | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS. Do not use `auto` or `Auto`. | | Mock location not working in other apps | Developer Options not configured | Verify GNSS Master is selected as the mock location provider in Developer Options. | | Corrections drop when screen turns off | Android battery optimization | Disable battery optimization for GNSS Master in Android settings. | ## Tips for best results * **GNSS Master is the best option for relaying RTK to any Android app.** If your field app does not have a built-in NTRIP client, use GNSS Master as the relay layer. * **You can browse the mountpoint source table** by tapping the button next to the mountpoint field. However, for RTKdata.com, simply type `AUTO` in ALL CAPS. * **Receiver configuration built in.** You can switch your u-blox F9P between Rover and Base mode directly from the app — no need for u-center on a desktop. * **Works alongside SW Maps.** Enable both Mock Location and "Output to SW Maps" for the best combination of NTRIP relay and GIS data collection. * **NTRIP V2 is supported** if your caster requires it. Select the version in the NTRIP connection dialog. RTKdata.com works with both V1 and V2. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Agriculture](https://rtkdata.com/agriculture/) # Mapit GIS NTRIP Setup: Android & iOS RTK Connect Mapit GIS on Android and iOS to RTKdata NTRIP corrections for centimeter RTK. Built-in NTRIP client, receiver setup, Send GGA, and on-device geoid heights. Mapit GIS is a GIS data collection and mapping app with a **built-in NTRIP client** for receiving real-time RTK corrections. NTRIP is integrated directly into the main app (**Settings → NTRIP Corrections**) — there is no separate companion app. Mapit connects to an external GNSS receiver, streams corrections from an NTRIP caster like RTKdata.com to that receiver, and lets you collect centimeter-level data in the field. **Download:** * [Mapit GIS — Android (3.2.8+)](https://play.google.com/store/apps/details?id=com.mapitgis.mapitgis) (Google Play — free tier available, Pro/Pro Plus subscriptions for advanced features) * [Mapit GIS — iOS (1.7+)](https://apps.apple.com/app/apple-store/id6757866571) (App Store) {% hint style="info" %} **NTRIP is now built in.** Earlier versions of this guide referenced a separate "Mapit GIS – NTRIP Client" companion app and an RTKLIB processing engine. That architecture no longer exists. Since the v3.0 rebuild, NTRIP corrections are part of the main Mapit GIS app. The receiver computes the RTK solution; Mapit forwards the RTCM corrections to it. {% endhint %} ## How it works Mapit GIS connects to your NTRIP caster, receives RTCM corrections, and forwards them to your connected GNSS receiver. **The receiver itself computes the RTK fix (Float → Fixed)** — Mapit does not do on-device RTK processing. This is the standard "NTRIP client + smart receiver" model used by most field software. ## Key capabilities | Feature | Details | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Platform** | Android and iOS (phone or tablet) | | **Cost** | Free tier available. NTRIP RTK corrections require a **Mapit Pro Plus** subscription. | | **Receiver connection (Android)** | Bluetooth Classic (SPP), Bluetooth LE (Nordic UART), USB serial, TCP/Wi-Fi | | **Receiver connection (iOS)** | Bluetooth LE and TCP/IP work without restriction. Classic-Bluetooth receivers require Apple MFi whitelisting (currently Eos Arrow and Juniper Geode/Spire). | | **NTRIP support** | Built-in NTRIP client — **NTRIP v1 and v2** | | **RTK processing** | Performed by the **receiver**. Mapit forwards RTCM corrections and reads the receiver's NMEA position. | | **GIS features** | Point/line/polygon collection, attribute forms | | **Export formats** | GeoJSON, KML, Shapefile, CSV, **DXF, GPX, GeoParquet**, plus direct publishing to **PostgreSQL/PostGIS** and **ArcGIS Online** | | **Heights** | Can apply a geoid model on-device (Pro Plus *Orthometric Height* feature, e.g. EGM2008 / OSGM15 / GEOID18) to output orthometric (MSL) heights directly | ## Requirements * Android (3.2.8+) or iOS (1.7+) phone or tablet running a current version of **Mapit GIS** * **Mapit Pro Plus** subscription (required for NTRIP RTK corrections) * A multi-frequency (L1/L2) RTK-capable GNSS receiver that accepts RTCM3 corrections (e.g., Eos Arrow, Juniper Geode/Spire, ArduSimple, SparkFun RTK, u-blox F9P board) * Internet connection (cellular data or Wi-Fi) * Active RTKdata.com account with RTK 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 %} ### Install Mapit GIS and subscribe to Pro Plus Install Mapit GIS (Android 3.2.8+ or iOS 1.7+) and subscribe to **Mapit Pro Plus**, which unlocks NTRIP RTK corrections. {% endstep %} {% step %} ### Connect your GNSS receiver Pair and connect your external GNSS receiver under **Settings → External GNSS**. Choose the connection type your receiver uses (Bluetooth / BLE / USB / TCP). {% hint style="warning" %} On **iOS**, classic-Bluetooth receivers require Apple MFi whitelisting (currently Eos Arrow and Juniper Geode/Spire). **BLE** and **TCP/IP** receivers connect without that restriction. On Android, pair Bluetooth receivers in the OS Bluetooth settings first. {% endhint %} {% endstep %} {% step %} ### Add an NTRIP configuration Go to **Settings → NTRIP Corrections → Add Configuration** and enter your RTKdata caster details for your region: {% tabs %} {% tab title="North America" %} * **Host:** `rtk.rtkdata.com` * **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` {% endtab %} {% tab title="Europe" %} * **Host:** `eu.rtkdata.com` * **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` {% endtab %} {% tab title="Australia" %} * **Host:** `aus.rtkdata.com` * **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` {% endtab %} {% endtabs %} {% endstep %} {% step %} ### Set the receiver target and keep Send GGA on 1. Set the **receiver target** (Bluetooth / BLE / TCP / USB) so corrections are forwarded to the right device. 2. Leave **Send GGA on** — this is required. {% hint style="danger" %} **Send GGA must stay enabled.** The RTKdata caster uses your GGA position to select the **nearest reference station** from its network and stream corrections from it. Without GGA, the caster authenticates you but never assigns a base station, and you stay stuck on Float. (RTKdata is a single-baseline network keyed to your position via GGA — it is **not** a VRS service.) {% endhint %} {% endstep %} {% step %} ### Connect and verify Fix 1. Tap **Connect**. 2. The NTRIP indicator on the map turns **green** once the receiver reaches Float/Fixed. 3. Wait for the receiver to report **RTK Fixed**. Convergence typically takes 15–60 seconds under open sky. {% endstep %} {% endstepper %} ## Vertical reference (heights) RTKdata delivers **ellipsoidal heights** (height above the WGS 84 ellipsoid). Unlike most field apps, Mapit GIS can convert these on-device: {% hint style="info" %} Mapit GIS Pro Plus includes an **Orthometric Height** feature that applies a geoid model (e.g. EGM2008, OSGM15, GEOID18) on-device to output orthometric (mean sea level) heights directly — you do **not** need post-processing just to convert from ellipsoidal to orthometric. See [Understanding Heights](/get-started/understanding-heights). {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ---------------------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | Stuck on Float indefinitely | GGA not being sent to the caster | Confirm **Send GGA** is enabled in the NTRIP configuration | | Connected but no corrections | Wrong host for your region, or blank port | Verify the regional host spelling and that the port is `2101` | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS | | Receiver not found (Android) | Device not paired in OS settings | Pair the receiver in Android Bluetooth settings first, then select it under Settings → External GNSS | | Classic-Bluetooth receiver won't connect (iOS) | Apple MFi restriction | Use a BLE or TCP/IP receiver, or one of the MFi-whitelisted models (Eos Arrow, Juniper Geode/Spire) | | Receiver reaches Fixed but heights look wrong | Expecting orthometric but receiving ellipsoidal | Enable the **Orthometric Height** geoid model (Pro Plus) or convert in post-processing | | NTRIP RTK options missing | Free tier, or app not updated | Subscribe to **Mapit Pro Plus** and update to the current app version | ## Tips for best results * **One app, NTRIP built in.** There is no separate companion app and no RTKLIB/"Positioning Mode" configuration. Everything lives under **Settings → NTRIP Corrections**. * **The receiver computes the fix.** Mapit forwards RTCM and reads NMEA — make sure your receiver is a true RTK receiver that accepts RTCM3 corrections. * **Send GGA is mandatory** for the `AUTO` mountpoint. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). * **Get orthometric heights on-device** with the Pro Plus geoid feature instead of post-processing. * **Export is flexible** — DXF, GPX, GeoParquet, GeoJSON, KML, Shapefile, and CSV, plus direct publishing to PostGIS and ArcGIS Online. ## Reference links (Mapit GIS) * NTRIP Client guide: [mapitgis.com/docs/external-gnss/ntrip-client](https://mapitgis.com/docs/external-gnss/ntrip-client) * Connecting a receiver: [mapitgis.com/docs/external-gnss/connecting-a-receiver](https://mapitgis.com/docs/external-gnss/connecting-a-receiver) * RTK and fix types: [mapitgis.com/docs/external-gnss/rtk-and-fix-types](https://mapitgis.com/docs/external-gnss/rtk-and-fix-types) * Geoid / orthometric heights: [mapitgis.com/docs/settings/geoid-models](https://mapitgis.com/docs/settings/geoid-models) * Mapit Pro Plus: [mapitgis.com/docs/subscriptions/mapit-pro-plus](https://mapitgis.com/docs/subscriptions/mapit-pro-plus) ## Related Industry Solutions * [Utilities](https://rtkdata.com/utilities/) * [Environmental Monitoring](https://rtkdata.com/environmental-monitoring/) # HYPACK NTRIP Setup: RTK for Hydrographic Survey Set up the HYPACK NTRIPOUT driver to feed RTKdata RTK corrections to your vessel GNSS receiver. Port 2101, AUTO mountpoint, GGA at 1 Hz for hydro survey. HYPACK is a professional hydrographic survey software suite developed by Xylem, used worldwide for planning, collecting, processing, and analyzing marine survey data. HYPACK includes a dedicated **NTRIP Output (NTRIPOUT)** driver that receives RTK corrections from an NTRIP caster like RTKdata.com and forwards them to the survey vessel's GNSS receiver over a network or serial connection, enabling centimeter-level positioning for bathymetric surveys, dredging operations, and marine construction. **Download / Purchase:** [HYPACK by Xylem](https://www.xylem.com/en-us/brand/hypack/) (commercial license required — contact Xylem for pricing; lease options available) ## Key capabilities | Feature | Details | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | **Platform** | Windows (desktop/laptop aboard survey vessel) | | **Cost** | Commercial license (contact Xylem for pricing). Lease options available with up to 85% of lease price applicable toward full purchase. | | **NTRIP support** | Built-in NTRIPOUT driver — dedicated NTRIP client that forwards corrections to GPS receiver | | **NTRIP version** | V1 and V2 (checkbox to advertise as NTRIP V2 client) | | **Correction delivery** | Network (TCP/IP) or shared serial port with GPS driver | | **Mock location relay** | Not applicable — HYPACK receives corrected positions from the GNSS receiver after corrections are applied | | **Typical use** | Bathymetric surveys, dredging guidance, marine construction positioning | ## Requirements * **Windows PC or tablet** running HYPACK (current version recommended) * **GNSS receiver** capable of accepting RTCM3 corrections (e.g., Trimble, Hemisphere, u-blox, SBG, or integrated units like CEE HydroSystems CEESCOPE) * **Internet connection** on the survey vessel (cellular modem, Wi-Fi, or satellite link) * **Network or serial connection** between the HYPACK PC and the GNSS receiver * **Active RTKdata.com account** with RTK 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 %} ### Add the NTRIP Output driver in HYPACK Hardware 1. Open HYPACK and go to **Preparation > Hardware** (or **Hardware Setup**). 2. In the Hardware configuration window, click on your survey vessel. 3. Under the **Devices** tab, click **Add Device**. 4. From the driver list, select **NTRIPOUT** (the NTRIP Output driver). * If you do not see NTRIPOUT in the list, click **Rescan Driver List** to refresh available drivers. 5. The NTRIPOUT driver will be added to your hardware configuration. {% hint style="info" %} The NTRIPOUT driver is a standalone driver dedicated to receiving NTRIP corrections and forwarding them to a GPS receiver. It replaces the older NTRIP tab that existed inside the GPS.DLL driver. {% endhint %} {% endstep %} {% step %} ### Configure the NTRIP connection settings 1. Double-click the **NTRIPOUT** driver to open its settings dialog. 2. Enter the NTRIP caster connection details: {% tabs %} {% tab title="North America" %} * **Caster Address / Host:** `rtk.rtkdata.com` * **IP Fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% tab title="Europe" %} * **Caster Address / Host:** `eu.rtkdata.com` * **IP Fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% tab title="Australia" %} * **Caster Address / Host:** `aus.rtkdata.com` * **IP Fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} 3. If available, check **"Advertise as NTRIP Ver. 2 Client"** to use the newer NTRIP V2 protocol (optional — RTKdata.com supports both V1 and V2). 4. Ensure the driver is configured to **send GGA at 1 Hz** — this is typically the default. RTKdata.com requires GGA to generate VRS corrections. {% hint style="danger" %} **GGA output must be enabled at 1 Hz.** Without GGA, RTKdata.com cannot determine your vessel's position and cannot compute corrections. The correction stream will not deliver usable data. {% endhint %} {% endstep %} {% step %} ### Configure the correction output to the GNSS receiver The NTRIPOUT driver receives RTCM3 corrections from the caster and must forward them to your GNSS receiver. Configure the output path based on your hardware setup: **Option A: Network (TCP/IP) — most common for modern setups** 1. In the NTRIPOUT driver settings, set the output connection to **Network Client TCP**. 2. Enter the GNSS receiver's IP address and the TCP port for corrections input. * Example for CEE HydroSystems CEESCOPE: IP `192.168.2.2`, Port `3001` * For other receivers, consult your receiver's documentation for the corrections input port. **Option B: Serial port — for receivers connected via RS-232** 1. The NTRIPOUT driver can share the same serial port as the GPS.DLL driver (the NTRIP.DLL shares the serial port with GPS.DLL). 2. Set the COM port and baud rate to match your GNSS receiver's serial connection. {% hint style="warning" %} **Start sequence matters.** For network connections, the GNSS receiver must be powered on and have acquired a position **before** starting the NTRIP driver. If the TCP socket cannot connect, the correction stream will not start. Suggested workflow: (1) Power on receiver, (2) Wait for satellite acquisition, (3) Start HYPACK survey with NTRIP driver. {% endhint %} {% endstep %} {% step %} ### Verify RTK Fix in HYPACK 1. Start a survey session in HYPACK. 2. The NTRIPOUT driver connects to RTKdata.com and begins receiving RTCM3 corrections. 3. Monitor the GPS device status in the HYPACK status bar or the **Survey** window: * The GPS quality indicator should progress from **Autonomous > DGPS > Float > Fix**. 4. Once **RTK Fix** is achieved, the corrected position is used for all survey data collection. {% hint style="info" %} Check the correction age in the GPS status display. It should remain below 5 seconds. If correction age climbs steadily, the NTRIP connection may be dropping — verify internet connectivity. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**. For hydrographic surveys, you typically need heights referenced to a chart datum or local vertical datum. Use HYPACK's **Tide** or **RTK Tide** module to apply tidal corrections, or convert ellipsoidal heights to your required vertical datum using a geoid model or local benchmark. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------------------ | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | NTRIPOUT driver not in device list | Driver DLL missing or not scanned | Click **Rescan Driver List** in Hardware setup. Ensure HYPACK installation is complete. | | TCP connection to receiver fails | Receiver not powered or wrong IP/port | Verify the receiver is on and has acquired a position. Check IP address and TCP port in receiver documentation. | | NTRIP connects but no corrections reach receiver | Output path misconfigured | Verify the TCP or serial output settings match the receiver's correction input port. | | Stuck on Float | GGA not being sent or baseline too long | Confirm GGA is sent at 1 Hz. Check RTKdata coverage for your survey area. | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS. | | Corrections drop during survey | Vessel cellular signal lost | Use a cellular modem with external antenna mounted high on the vessel. Consider a marine-grade 4G/LTE router. | | GPS quality oscillates between Fix and Float | Marginal sky view or multipath | Ensure the GNSS antenna is mounted with a clear 360-degree sky view above the vessel superstructure. Avoid mounting near radar or communication antennas. | ## Tips for best results * **Internet at sea is the biggest challenge.** Invest in a quality marine cellular modem with external antenna. For offshore work beyond cellular range, consider Starlink Maritime or Iridium-based solutions. * **The NTRIPOUT driver is separate from the GPS driver.** This is by design — NTRIPOUT handles the correction stream while GPS.DLL reads the corrected position from the receiver. They can share a serial port if needed. * **Data usage is minimal.** RTK corrections use approximately 5–10 kbit/s, which is negligible even on metered satellite connections. * **Test the full chain dockside** before going to the survey site. Verify NTRIP connection, correction delivery to the receiver, and RTK Fix — all while you still have reliable internet. * **HYPACK version matters.** The standalone NTRIPOUT driver replaced the older NTRIP functionality embedded in GPS.DLL. Ensure you are running a current version of HYPACK for the best NTRIP support. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Environmental Monitoring](https://rtkdata.com/environmental-monitoring/) # Mission Planner NTRIP Setup: ArduPilot RTK Send RTKdata NTRIP corrections to any ArduPilot drone with Mission Planner. RTK/GPS Inject setup, caster host, port 2101, AUTO mountpoint, GGA, and RTK Fixed verification. **Mission Planner** is the ground control station for ArduPilot-based drones and rovers. Its built-in NTRIP client streams RTK corrections from a caster like RTKdata.com to the vehicle over the telemetry link, so any ArduPilot aircraft with an RTK-capable GNSS (e.g. u-blox F9P) can reach centimeter-level accuracy. One setup covers every ArduPilot vehicle. ## Requirements * **Mission Planner** (current version) on a Windows ground station * ArduPilot vehicle with an **RTK-capable GNSS receiver** * Telemetry link between Mission Planner and the vehicle * Internet on the ground station * Active RTKdata.com account with RTK 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 %} ### Open the NTRIP / GPS Inject settings In Mission Planner, go to **SETUP → Optional Hardware → RTK/GPS Inject**. {% endstep %} {% step %} ### Select NTRIP From the connection-type dropdown, select **NTRIP**, then press **Connect**. A dialog appears asking for the caster details. {% endstep %} {% step %} ### Enter your RTKdata caster details Mission Planner accepts the caster as a single string in the format `user:pass@host:port/mountpoint`. Use your region's host and your RTKdata credentials: {% tabs %} {% tab title="North America" %} ``` rtkUSERNAME:PASSWORD@rtk.rtkdata.com:2101/AUTO ``` * IP fallback host: `13.56.117.10` {% endtab %} {% tab title="Europe" %} ``` rtkUSERNAME:PASSWORD@eu.rtkdata.com:2101/AUTO ``` * IP fallback host: `3.73.41.96` {% endtab %} {% tab title="Australia" %} ``` rtkUSERNAME:PASSWORD@aus.rtkdata.com:2101/AUTO ``` * IP fallback host: `54.206.56.130` {% endtab %} {% endtabs %} * Replace `rtkUSERNAME` / `PASSWORD` with your *RTK Credentials* from the dashboard (username starts with `rtk`). * Keep the mountpoint **`AUTO`** in ALL CAPS. Alternatives: `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`. {% endstep %} {% step %} ### Confirm GGA / position is sent When prompted, let Mission Planner send the **vehicle's current position** to the caster (GGA). A resend interval of about **1 second** is ideal. {% hint style="danger" %} **GGA must be sent.** RTKdata uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections. RTKdata is single-baseline and location-keyed — it is **not** a VRS service. If Mission Planner sends a fixed/zero position or none at all, you will not receive corrections. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% step %} ### Verify RTK Fix Watch the GPS status in Mission Planner (HUD / status bar). The fix type should progress **GPS → RTK Float → RTK Fixed**. Inject rate (bytes/s) should be non-zero once corrections flow. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTKdata delivers **ellipsoidal heights** (WGS 84 ellipsoid). Apply a geoid model in your processing if you need orthometric (mean sea level) heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------ | -------------------------------- | ------------------------------------------------------------------------- | | Connects but no inject / stays Float | GGA / position not being sent | Ensure Mission Planner sends the vehicle's current position to the caster | | Authentication fails | Wrong credentials | Re-check the `user:pass` part of the string (username starts with `rtk`) | | No corrections | Wrong host or mountpoint case | Verify the regional host and that the mountpoint is `AUTO` in ALL CAPS | | Connection refused on a secure port | Mission Planner NTRIP has no TLS | Use RTKdata's plain caster on port `2101` (no TLS needed) | ## Tips * **One page, every ArduPilot vehicle** — copters, planes, rovers all use this same NTRIP/GPS-Inject flow. * **Mountpoint `AUTO` in ALL CAPS.** * **Plain port `2101`** — no TLS required, which suits Mission Planner's NTRIP client. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Robotics](https://rtkdata.com/robotics/) * [Agriculture](https://rtkdata.com/agriculture/) # QGroundControl NTRIP Setup: PX4 Drone RTK Send RTKdata NTRIP corrections to any PX4 drone with QGroundControl. NTRIP/RTK settings, host address, server port 2101, AUTO mount point, and RTK Fixed verification. **QGroundControl (QGC)** is the ground control station for PX4-based drones. Its built-in NTRIP client streams RTK corrections from a caster like RTKdata.com to the vehicle, so any PX4 aircraft with an RTK-capable GNSS receiver can reach centimeter-level accuracy. One setup covers every PX4 vehicle. ## Requirements * **QGroundControl** (current version) on the ground station * PX4 vehicle with an **RTK-capable GNSS receiver** * Telemetry link between QGC and the vehicle * Internet on the ground station * Active RTKdata.com account with RTK 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 %} ### Open the NTRIP / RTK settings In QGroundControl, open **Application Settings → NTRIP / RTK**. {% endstep %} {% step %} ### Enter your RTKdata caster details Fill in the fields using your region's host: {% tabs %} {% tab title="North America" %} * **Host address:** `rtk.rtkdata.com` (IP fallback `13.56.117.10`) * **Server port:** `2101` * **Username / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`) * **Mount Point:** `AUTO` (ALL CAPS) — or use **Browse** to pick from the source table * **Use TLS encryption:** **off** * **RTCM Message Filter:** leave empty (forward all) {% endtab %} {% tab title="Europe" %} * **Host address:** `eu.rtkdata.com` (IP fallback `3.73.41.96`) * **Server port:** `2101` * **Username / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`) * **Mount Point:** `AUTO` (ALL CAPS) — or use **Browse** to pick from the source table * **Use TLS encryption:** **off** * **RTCM Message Filter:** leave empty (forward all) {% endtab %} {% tab title="Australia" %} * **Host address:** `aus.rtkdata.com` (IP fallback `54.206.56.130`) * **Server port:** `2101` * **Username / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`) * **Mount Point:** `AUTO` (ALL CAPS) — or use **Browse** to pick from the source table * **Use TLS encryption:** **off** * **RTCM Message Filter:** leave empty (forward all) {% endtab %} {% endtabs %} Alternative mountpoints for a specific datum: `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`. {% endstep %} {% step %} ### Connect and verify RTK Fix QGC connects to the caster and forwards RTCM corrections to the vehicle. Watch the GPS status progress **3D Fix → RTK Float → RTK Fixed**. {% hint style="danger" %} **RTKdata needs your position (GGA).** The caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections — it is **not** a VRS service and sends nothing without a position. QGC must forward the vehicle's position to the caster. If you connect but stay on **Float** with no Fix, the position/GGA is not reaching the caster — see Troubleshooting and [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTKdata delivers **ellipsoidal heights** (WGS 84 ellipsoid). Apply a geoid model in your processing if you need orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ---------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------- | | Connects but stays on Float | Vehicle position (GGA) not reaching the caster | Ensure the vehicle has a 3D fix so QGC can report position; update QGC to a current version | | Connection fails immediately | TLS enabled | Turn **Use TLS encryption** off — RTKdata uses a plain caster on `2101` | | Authentication fails | Wrong credentials | Re-enter username/password from the dashboard (username starts with `rtk`) | | Mount point empty in Browse | Source table not loaded | Re-open the settings to refresh, then select `AUTO` | ## Tips * **One page, every PX4 vehicle.** * **Leave the RTCM Message Filter empty** so all correction messages are forwarded. * **TLS off, port `2101`, mountpoint `AUTO` in ALL CAPS.** ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Robotics](https://rtkdata.com/robotics/) # MyUtiliGuard NTRIP Setup: RTK Utility Locating Connect MyUtiliGuard and the Subsite UtiliGuard 2 RTK to RTKdata NTRIP corrections. RTK login fields, Station mountpoint AUTO, and centimeter utility locating accuracy. **MyUtiliGuard** is the mobile companion app for the **Subsite Electronics UtiliGuard 2 RTK** utility locator (Subsite is part of The Charles Machine Works / Ditch Witch family). The app connects to the locator over Bluetooth, supplies RTK corrections from an NTRIP caster like RTKdata.com, and logs centimeter-grade utility points for GIS/damage-prevention workflows. The UtiliGuard 2 RTK reaches centimeter accuracy only when the app feeds it corrections — so you bring your own NTRIP service. **Download:** * [MyUtiliGuard — iOS](https://apps.apple.com/us/app/myutiliguard/id1438037402) (iOS 11.0+) * [MyUtiliGuard — Android](https://play.google.com/store/apps/details?id=com.subsite.utiliguard) ## Requirements * **Subsite UtiliGuard 2 RTK** locator (integrated survey-grade dual-band GNSS) * **MyUtiliGuard** app on iOS or Android, with location permission allowed * Internet on the phone (the phone relays corrections to the locator over Bluetooth) * Active RTKdata.com account with RTK 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 %} ### Enable Bluetooth on the locator and connect On the UtiliGuard 2 RTK: **press and hold → Configuration → Settings → Communications → Radio On/Off → On**. Then in MyUtiliGuard tap **Connect → select your UtiliGuard 2 → Ok**. {% endstep %} {% step %} ### Open the RTK login Tap the **action button → GPS RTK Login**. On first use, tap **Allow While Using App** for the location permission. {% hint style="warning" %} Leave **location permission enabled**. The app uses your position to tell the caster where you are (GGA). RTKdata is location-keyed — without your position it cannot send corrections. {% endhint %} {% endstep %} {% step %} ### Add a new RTK service Tap the **down arrow → action button → New RTK**, then fill in the form. Note that the mountpoint field is labeled **"Station."** {% tabs %} {% tab title="North America" %} * **Name:** `RTKdata NA` (any label you like) * **Host:** `rtk.rtkdata.com` * **Port:** `2101` * **Station (mountpoint, ALL CAPS):** `AUTO` * **User / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`) {% endtab %} {% tab title="Europe" %} * **Name:** `RTKdata EU` * **Host:** `eu.rtkdata.com` * **Port:** `2101` * **Station (mountpoint, ALL CAPS):** `AUTO` * **User / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`) {% endtab %} {% tab title="Australia" %} * **Name:** `RTKdata AUS` * **Host:** `aus.rtkdata.com` * **Port:** `2101` * **Station (mountpoint, ALL CAPS):** `AUTO` * **User / Password:** From *RTK Credentials* in the dashboard (username starts with `rtk`) {% endtab %} {% endtabs %} Alternatives for the **Station** field if you need a specific datum: `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` (all caps). {% hint style="danger" %} **"Station" is the NTRIP mountpoint** — enter `AUTO` in ALL CAPS. RTKdata uses your position (GGA) to select the **nearest reference station** and stream single-baseline RTCM3 corrections; it is **not** a VRS service. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% step %} ### Save and log in Tap **Save** (the app verifies the credentials), then **Login**. Confirm the **Bytes Rx Total** counter climbs — that means corrections are streaming. The locator's GNSS solution should move toward an RTK fix (accuracy to \~cm). You can then stow the phone and begin locating. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTKdata delivers **ellipsoidal heights** (height above the WGS 84 ellipsoid). MyUtiliGuard records the GNSS-reported height; treat logged elevations as ellipsoidal and convert to orthometric (MSL) in your GIS if needed. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------- | -------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | Authenticates but never reaches RTK fix | Position (GGA) not reaching the caster | Confirm **location permission** is granted; RTKdata needs your position | | "Bytes Rx Total" stays at 0 | Wrong host/Station or credentials | Verify the regional Host, that **Station** is `AUTO` in ALL CAPS, and the User/Password from the dashboard | | Can't find the mountpoint field | It's labeled **"Station"** | Enter `AUTO` in the **Station** field | | Locator not found | Bluetooth radio off on the locator | Enable the radio: hold → Configuration → Settings → Communications → Radio On/Off → On | | Login rejected | Wrong credentials | Re-enter User/Password from the RTKdata dashboard (username starts with `rtk`) | ## Tips * **"Station" = mountpoint = `AUTO`** (ALL CAPS). This is the field people miss most. * **Keep location permission on** — that's what lets the app send GGA so RTKdata can pick your nearest base. * **Watch "Bytes Rx Total"** to confirm corrections are flowing. * **Save multiple profiles** (e.g. one per region) and switch between them via the saved RTK list. ## Related Industry Solutions * [Utilities](https://rtkdata.com/utilities/) * [Construction](https://rtkdata.com/construction/) # GNSS Rover NTRIP Setup Guides: RTK Corrections Device-specific NTRIP setup guides for GNSS rovers and receivers on RTKdata. Find your host, port 2101, mountpoint AUTO, and RTK corrections settings. ## Device-Specific Setup Guides | Manufacturer | Device | Guide | | ------------ | ------------------- | ---------------------------------------------------------------------------------------------------------- | | Emlid | Reach RS2+ | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/emlid-reach-rs2+) | | Emlid | Reach RX / RX2 | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/emlid-reach-rx-rx2) | | Bad Elf | Flex | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/bad-elf-flex) | | Bad Elf | Flex Mini | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/bad-elf-flex-mini) | | SparkFun | RTK Facet | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/sparkfun-rtk-facet) | | Septentrio | Mosaic X5 | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/septentrio-mosaic-x5) | | EOS | Arrow Gold | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/eos-arrow-gold) | | GeoMax | Zenith60 / Zenith40 | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/geomax-zenith60-zenith40) | | Stonex | S980A / S900A | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/stonex-s980a-s900a) | | Tersus | Oscar / David | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/tersus-oscar-david) | | ComNav | T300 / K8 | [Setup Guide](https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/comnav-t300-k8) | *** ## Regional Connection Details | Region | Host | Port | | ----------------- | ----------------- | ------ | | **Europe** | `eu.rtkdata.com` | `2101` | | **North America** | `rtk.rtkdata.com` | `2101` | | **Australia** | `aus.rtkdata.com` | `2101` | **Mountpoint:** `AUTO` (recommended, ALL CAPS) *** ## Critical Configuration Requirements > **Do not use your website login!** Use the **NTRIP Username & Password** found in your [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/). ### Data Format * **Required:** RTCM 3.2 (or RTCM 3.X, Auto) * **Do NOT use:** CMR, CMR+, RTCM 2.3 ### GNSS/NMEA Output **NMEA GGA output must be enabled.** The server will not send any corrections without receiving your rover's position. *** ## Universal Setup (Trimble, Leica, Topcon, etc.) For devices not listed above, use the universal connection parameters: 1. **Host:** Select your regional server (see table above) 2. **Port:** `2101` 3. **Mountpoint:** `AUTO` 4. **Username/Password:** From your RTKdata Dashboard 5. **NMEA GGA:** Enable transmission to caster ### Trimble-Specific Configuration Trimble users must select **"Single Base (RTCM via NTRIP)"** rather than proprietary modes (iMAX, VRS, MAX, FKP). RTKdata operates through a network of many physical base stations assigned dynamically to rovers. *** ## Resources * [NTRIP Credentials](https://rtkdata.com/my-account/rtk-credentials/) * [Coverage Map](https://rtkdata.com/coverage/) * [Support](https://docs.rtkdata.com/support/support) # Emlid Reach RS3 RTK Setup: Emlid Flow NTRIP Set up the Emlid Reach RS3 with RTKdata NTRIP in Emlid Flow for centimeter RTK. Correction input, GGA, tilt compensation calibration, and Global CS guidance. The Emlid Reach RS3 is Emlid's newest multi-band RTK receiver (2024), built for professional surveying, construction, and GIS. It tracks GPS, GLONASS, Galileo, BeiDou, and QZSS on L1/L2/L5 frequencies. The RS3 features a built-in **IMU for tilt compensation**, faster convergence than the RS2+, and an updated antenna design. Like the RS2+, it is configured through the **Emlid Flow** app via Wi-Fi or Bluetooth. ## Requirements * **Emlid Reach RS3** powered on with a clear view of the sky * **Emlid Flow app** installed on your phone or tablet (iOS or Android) * **Internet connection** on your phone (cellular data or Wi-Fi) * **RTKdata.com account** with active RTK credentials (username starting with `rtk`) * **Survey pole** (recommended — required for tilt compensation calibration) {% 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 %} ### Power on and connect via Emlid Flow 1. Press and hold the power button on the RS3 for 3 seconds. The LED indicators will begin their startup sequence. 2. Open the **Emlid Flow** app on your phone. 3. Tap **+ Add new device** or select your RS3 from the device list. 4. Connect via **Wi-Fi** (the RS3 creates a hotspot named `reach:XX:XX`) or via **Bluetooth** if previously paired. 5. Once connected, the device dashboard displays satellite count, solution status, and battery level. {% hint style="info" %} **RS3 vs RS2+ connection:** The pairing process is identical to the RS2+. If you have used Emlid Flow with an RS2+, the interface will be familiar. The RS3 appears as a separate device in the device list. {% endhint %} {% endstep %} {% step %} ### Navigate to correction input 1. From the device dashboard in Emlid Flow, tap **Correction input** in the left-hand menu. 2. Toggle correction input to **Enabled** (if not already on). 3. Select **NTRIP** as the correction source. 4. Tap **Add new NTRIP profile** (or edit an existing one). {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the fields exactly as shown. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **Send receiver position to the correction service:** **Enabled** (sends NMEA GGA so RTKdata generates corrections for your exact location) Tap **Save** to store the profile. {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. Do not browse the source table — type the mountpoint manually. {% endhint %} {% endstep %} {% step %} ### Connect and wait for Fix 1. Tap **Connect** on the saved NTRIP profile. 2. The correction input status will show **Connected** with incoming data bytes. 3. Watch the solution status progress: **Single > Float > Fix**. 4. The RS3 achieves Fix faster than the RS2+ thanks to its updated antenna and receiver engine. Expect **Fix within 15-60 seconds** under clear sky. {% endstep %} {% step %} ### Handle the "Confirm Login" prompt The RS3 shares the same Emlid cloud sync behavior as the RS2+. You may see a popup in Emlid Flow that says **"Confirm login to resume data sync."** 1. Tap **Confirm** or **Dismiss** when the message appears. 2. If it keeps reappearing, sign into your Emlid account in Emlid Flow under **Settings > Account**. 3. This prompt does **not** affect your NTRIP connection. RTK corrections continue flowing while the popup is displayed. 4. If the popup causes a momentary NTRIP disconnect, tap **Reconnect** in the Correction input menu. {% hint style="warning" %} This is an Emlid cloud sync issue, not an RTKdata issue. It occurs when Emlid Flow needs to verify your Emlid account credentials for project synchronization. {% endhint %} {% endstep %} {% step %} ### Enable tilt compensation (RS3 exclusive) 1. With an active RTK Fix, mount the RS3 on a survey pole. 2. In Emlid Flow, navigate to **Settings > Tilt compensation**. 3. Enable tilt compensation and follow the on-screen calibration: walk in a figure-8 pattern while tilting the pole in multiple directions. 4. Once calibrated, the RS3 reports corrected positions even when the pole is tilted up to 30 degrees from vertical. 5. The status bar will show a tilt compensation indicator confirming the IMU is active. {% endstep %} {% endstepper %} ## Vertical reference (heights) and coordinate systems {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal** (WGS84), not orthometric (mean sea level). Use the **Global coordinate system** for your NTRIP connection. If your project requires a local datum or MSL heights, apply the transformation in post-processing or configure the local CS within Emlid Flow's project settings. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------ | | "Confirm login to resume data sync" | Emlid cloud sync prompt | Tap **Confirm** or dismiss. Sign into your Emlid account in Emlid Flow settings. | | Correction input shows "Disconnected" | Wrong credentials or no internet | Verify username/password from your RTK dashboard (not website login). Check phone internet. | | Stuck on Float, never reaches Fix | Poor sky visibility or antenna obstructed | Move to open sky. Ensure the RS3 is upright on a pole. Check that at least 12+ satellites are tracked. | | Mountpoint error | Lowercase or misspelled mountpoint | Type `AUTO` in ALL CAPS. Do not browse the source table. | | Tilt compensation not available | No RTK Fix or not calibrated | Achieve a stable RTK Fix first, then run the figure-8 calibration routine. | | Connection drops frequently | Weak cellular signal | Move to better coverage. The RS3 will auto-reconnect when signal returns. | ## Tips and tricks * **Use Wi-Fi for initial setup, Bluetooth for fieldwork.** Wi-Fi provides a faster setup experience, but Bluetooth keeps your phone's internet connection active for streaming corrections. * **Tilt compensation is a major advantage** of the RS3 over the RS2+. It eliminates the need to perfectly level the pole for every measurement, saving significant time in the field. * **Use Global CS for NTRIP, local datum in post-processing.** RTKdata corrections are computed in a global reference frame. Apply your local coordinate system and geoid model when exporting or processing survey data. * **Check "Age of corrections"** in the Emlid Flow dashboard. If it exceeds 5 seconds, your internet connection may be unstable. * **Enable raw data logging** under the Logging tab for PPK post-processing. This is your safety net if NTRIP connectivity is intermittent during a survey. * **Battery life with NTRIP and tilt compensation active** is approximately 11-14 hours. Monitor battery status in Emlid Flow and carry a USB-C power bank for extended sessions. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) * [Agriculture](https://rtkdata.com/agriculture/) # Emlid Reach RS2+ RTK Setup: Emlid Flow NTRIP Connect the Emlid Reach RS2+ to RTKdata NTRIP in Emlid Flow for centimeter RTK. Correction input setup, GGA, and the Confirm Login prompt fix. Free 30-day trial. ![Emlid Reach RS2+](https://emlid.com/wp-content/themes/emlid/img/reachrs2/rs2+/Reach_RS2+_store_2x.webp) The Emlid Reach RS2+ is a multi-band GNSS receiver designed for surveying, mapping, and construction layout. It tracks GPS, GLONASS, Galileo, BeiDou, and QZSS on L1/L2/L5 frequencies, delivering centimeter-level accuracy when connected to an RTK correction service. The RS2+ is self-contained with a built-in antenna, battery (up to 16 hours), and an integrated LoRa radio. It connects to your phone or tablet through the **Emlid Flow** app via Wi-Fi or Bluetooth. ## Requirements * **Emlid Reach RS2+** powered on with a clear view of the sky * **Emlid Flow app** installed on your phone or tablet (iOS or Android) * **Internet connection** on your phone (cellular data or Wi-Fi hotspot) * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** (optional but recommended for fieldwork) {% 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 %} ### Power on and connect 1. Press and hold the power button on the RS2+ for 3 seconds. The LEDs will begin cycling. 2. Open the **Emlid Flow** app on your phone. 3. Tap **+ Add new device** or select your RS2+ from the device list. 4. Connect via **Wi-Fi** (the RS2+ creates its own hotspot named `reach:XX:XX`) or via **Bluetooth** if previously paired. 5. Once connected, you will see the device dashboard with satellite count and solution status. {% endstep %} {% step %} ### Configure correction input 1. From the device dashboard, tap **Correction input** in the left menu. 2. Tap the toggle to enable correction input (if not already on). 3. Select **NTRIP** as the correction source. 4. Tap **Add new NTRIP profile** (or edit an existing one). {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the fields exactly as shown. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **Send receiver position to the correction service:** **Enabled** (this sends NMEA GGA to RTKdata so corrections are generated for your location) Tap **Save** to store the profile. {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} ### Connect and verify 1. Tap **Connect** on the saved NTRIP profile. 2. The status bar will show correction input as **Connected**. 3. Watch the solution status in the top bar progress: **Single** → **Float** → **Fix**. {% endstep %} {% step %} ### Handle the "Confirm Login" prompt (RS2+ specific) A common issue specific to the RS2+ is a popup in Emlid Flow that says **"Confirm login to resume data sync."** This message is unrelated to your NTRIP connection — it is an Emlid cloud account sync prompt. 1. When the message appears, tap **Confirm** or **Dismiss**. 2. If it keeps reappearing, sign into your Emlid account in Emlid Flow under **Settings → Account**. 3. This prompt does not affect RTK corrections. Your NTRIP connection will remain active even while the popup is displayed. 4. If the popup causes the NTRIP connection to drop, simply tap **Reconnect** in the Correction input menu. {% endstep %} {% endstepper %} ## What to expect * **LED behavior:** The power LED stays solid green. When receiving corrections, the status LED turns solid or blinking green depending on the solution type. * **Convergence time:** With good sky visibility and a nearby RTKdata base station, expect **Float** within 10–30 seconds and **Fix** within 30–90 seconds. * **Accuracy at Fix:** Horizontal accuracy of 1–2 cm, vertical accuracy of 2–3 cm. * **Dashboard display:** Emlid Flow shows satellite count, solution type (Single/Float/Fix), and age of corrections in real time. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). If your project requires MSL heights, apply a geoid model in your GIS software or use Emlid Flow's geoid settings. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------------- | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- | | "Confirm login to resume data sync" message | Emlid cloud sync prompt interfering | Tap **Confirm** or dismiss the dialog, then reconnect NTRIP. Sign into your Emlid account to prevent recurrence. | | Correction input shows "Disconnected" | Wrong credentials or no internet | Double-check username/password from your RTK dashboard (not your website login). Verify your phone has active internet. | | Stuck on Float, never reaches Fix | Poor sky visibility or antenna issue | Move to an open area away from buildings and tree canopy. Ensure the RS2+ is upright on a pole, not tilted. | | Mountpoint error or empty mountpoint list | Mountpoint typed in lowercase | Type `AUTO` in all capital letters. Do not browse the mountpoint list — type it manually. | | Connection drops repeatedly | Weak cellular signal | Switch to a different network or move to an area with better reception. The RS2+ will auto-reconnect when signal returns. | ## Tips and tricks * **Use Wi-Fi for initial setup, Bluetooth for fieldwork.** Wi-Fi gives a faster connection for configuration, but Bluetooth is more reliable in the field since your phone keeps its own internet connection. * **Enable position logging** in Emlid Flow before starting your survey so you have a backup record of all collected points. * **Check "Age of corrections"** on the dashboard. If it climbs above 5 seconds, your internet connection may be unstable. * **The RS2+ remembers your NTRIP profile.** After first setup, it will auto-connect on subsequent power-ups if you leave correction input enabled. * **For PPK fallback**, enable raw data logging under the Logging tab. If your NTRIP connection drops mid-survey, you can post-process the data later. * **Battery life with NTRIP active** is approximately 14–16 hours. The receiver will warn you at 10% battery in the app. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) * [Agriculture](https://rtkdata.com/agriculture/) # Emlid Reach RX / RX2 NTRIP Setup: RTK Corrections Step-by-step guide to connecting Emlid Reach RX and RX2 to RTKdata via NTRIP in Emlid Flow. Covers iOS and Android setup including mock location configuration The Emlid Reach RX and RX2 are compact, lightweight multi-band GNSS receivers built for GIS data collection and mapping. Unlike the RS2+ which has a built-in antenna, the RX series is a small receiver module that pairs with an external antenna or attaches to a survey pole. It connects to your phone or tablet **exclusively via Bluetooth**, and the phone handles the internet connection for NTRIP corrections. The RX tracks GPS, GLONASS, Galileo, and BeiDou. The RX2 adds QZSS and L5 support for faster convergence. ## Requirements * **Emlid Reach RX or RX2** with a compatible GNSS antenna * **Emlid Flow app** installed on your phone or tablet (iOS or Android) * **Internet connection** on your phone (cellular data) * **RTKdata.com account** with active RTK credentials * **Survey pole or mounting bracket** for the antenna * **Note for iOS users:** You need the MFi-certified revision of the RX/RX2 for iOS Bluetooth compatibility. Check your device packaging or Emlid support if unsure. {% 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 %} #### Power on and pair via Bluetooth 1. Press the power button on the RX/RX2. The LED will begin blinking. 2. Open the **Emlid Flow** app. 3. Tap **+ Add new device**. The app scans for nearby Emlid devices via Bluetooth. 4. Select your **Reach RX** or **Reach RX2** from the list. 5. If prompted, confirm the Bluetooth pairing on your phone. 6. Once connected, the device dashboard appears showing satellite tracking status. {% endstep %} {% step %} #### Configure correction input 1. Tap **Correction input** in the left-side menu. 2. Toggle correction input **On** if it is not already enabled. 3. Select **NTRIP** as the correction type. 4. Tap **Add new NTRIP profile**. {% endstep %} {% step %} #### Enter RTKdata.com NTRIP settings Fill in the fields. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **Send receiver position to the correction service:** **Enabled** Tap **Save**. {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} #### Connect and verify 1. Tap **Connect** on your saved profile. 2. The correction input status changes to **Connected**. 3. Monitor the solution: **Single** → **Float** → **Fix**. {% endstep %} {% step %} #### Set up mock location (Android) The RX/RX2 outputs corrected positions to your field app via mock location on Android. This makes every app on your phone use the centimeter-level position from the RX instead of the phone's built-in GPS. 1. On your Android phone, go to **Settings → About phone** and tap **Build number** 7 times to enable Developer Options. 2. Go to **Settings → Developer Options → Mock location app**. 3. Select **Emlid Flow** as the mock location provider. 4. Open your field app (ArcGIS Field Maps, Mergin Maps, QField, SW Maps, etc.). It will now receive the corrected RTK position automatically. **On iOS**, mock location is not available. Instead, select the RX/RX2 as an external Bluetooth GNSS source directly in your field app's location settings. {% endstep %} {% endstepper %} ## What to expect * **LED indicators:** Solid green = powered on and tracking. Blinking blue = Bluetooth connected. The LED does not directly indicate Fix status — check the app. * **Convergence time:** Typically 15–60 seconds to Float, then 30–90 seconds to Fix with good sky visibility. * **Accuracy at Fix:** 1–2 cm horizontal, 2–4 cm vertical. * **Battery life:** Approximately 8–10 hours (RX) or 10–12 hours (RX2) with Bluetooth and NTRIP active. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). If your project requires MSL heights, apply a geoid model in your GIS software or use Emlid Flow's geoid settings. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------------ | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | RX not appearing in Emlid Flow | Bluetooth not enabled or device out of range | Ensure Bluetooth is on. Keep the RX within 10 meters. Restart Bluetooth on your phone if needed. | | NTRIP connects but solution stays Single | GGA not being sent | Verify **Send receiver position** is toggled on in the NTRIP profile. | | Float but no Fix after several minutes | Obstructed sky or multipath | Move away from buildings, metal structures, and dense tree cover. | | Field app not receiving corrected position | Mock location not configured | On Android, enable Developer Options → Mock location app → Emlid Flow. On iOS, use the Bluetooth GNSS method in your field app. | | "Authentication failed" error | Wrong credentials | Use the username and password from your RTK dashboard, not your RTKdata.com website login. | ## Tips and tricks * **The RX2 converges faster than the RX** due to additional L5 tracking. If you frequently work in challenging environments, the RX2 is worth the upgrade. * **Bluetooth range is about 10 meters.** Keep your phone in a pocket or chest mount rather than leaving it in your vehicle. * **Antenna matters.** The RX/RX2 accuracy depends heavily on the external antenna quality. Use the Emlid-recommended survey antenna for best results. * **Save multiple NTRIP profiles** if you work across regions — one for EU, one for NA, etc. Switch between them with a single tap. * **Enable logging** for PPK backup. If corrections drop, you can post-process the raw data against RTKdata RINEX files. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) * [Agriculture](https://rtkdata.com/agriculture/) # Trimble R12i / R10 RTK Setup: Trimble Access Connect the Trimble R12i, R10, and R750 to RTKdata NTRIP in Trimble Access. Create a Single Base RTCM v3 style (not VRS), mountpoint AUTO, for centimeter RTK. The Trimble R12i, R10, and R750 are professional survey-grade GNSS receivers delivering centimeter-level accuracy for land surveying, construction, and geospatial applications. The R12i features Trimble ProPoint GNSS engine and tilt compensation for measurements without leveling the pole. These receivers are configured through **Trimble Access** software running on a TSC5, TSC7, or T7 controller connected via Bluetooth or Wi-Fi. ## Requirements * **Trimble R12i, R10, or R750** powered on with clear sky visibility * **Trimble Access** software on a TSC5, TSC7, or T7 controller * **Internet connection** on the controller (cellular modem, phone hotspot via Bluetooth, or Wi-Fi) * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with Trimble quick-release adapter {% 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 {% hint style="danger" %} RTKdata delivers **single-baseline RTCM corrections**, not VRS. You must create a **Single Base / RTCM** survey style. Do NOT select "Network RTK," "VRS," "iMAX," or "CMRx." Using the wrong style will cause the survey to hang at 90% during startup. {% endhint %} {% stepper %} {% step %} ### Create a new survey style 1. In Trimble Access, tap **Settings** (gear icon) → **Survey Styles**. 2. Tap **New** to create a fresh style. 3. Name it **RTKdata Single Base**. 4. Under **Positioning type**, select **RTK**. {% endstep %} {% step %} ### Configure rover correction source 1. Inside the new style, tap **Rover options**. 2. Set **Correction source** to **Internet connection**. 3. Set **Correction type** to **RTCM v3**. {% hint style="warning" %} Do NOT select VRS, iMAX, or CMRx as the correction type. RTKdata uses standard RTCM 3.x single-baseline corrections. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Tap **NTRIP settings** and fill in the fields. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} Type the mountpoint manually — do not browse the source table. {% endstep %} {% step %} ### Start the survey 1. Return to the main screen and tap **Survey** → **Start survey**. 2. Select the **RTKdata Single Base** style you just created. 3. Trimble Access will connect to the internet, then to RTKdata's NTRIP caster. 4. Wait for the solution to progress: **Autonomous** → **Float** → **Fix**. 5. Once at Fix, the controller displays accuracy estimates and you can begin collecting points. {% endstep %} {% endstepper %} ## R12i tilt compensation The R12i includes Trimble's ProPoint engine with IMU-based tilt compensation. Once connected to RTKdata with a Fix solution, tilt compensation initializes automatically. You do not need to level the pole — simply hold it near-vertical and the receiver compensates for up to 30 degrees of tilt. A tilt icon appears on the controller when tilt compensation is active. ## Trimble Catalyst DA2 The Trimble Catalyst DA2 antenna also works with RTKdata. It requires a **Catalyst Basic** subscription license (not the Free tier) to accept external NTRIP corrections. Configure it in the Trimble Catalyst app using the same NTRIP settings above. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Apply a geoid model in Trimble Access (Settings → Coordinate system → Vertical adjustment) if your project requires MSL heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | "Starting survey" stuck at 90% | VRS or Network RTK style selected | Delete the style and create a new one using **RTCM v3** correction type, not VRS/iMAX. | | "Mount point not found" | Wrong capitalization or typo | Type `AUTO` in ALL CAPS. Do not browse the mountpoint list. | | No internet connection | Controller not connected to network | Pair your phone via Bluetooth for internet sharing, or use the controller's built-in cellular modem. | | Float only, never reaches Fix | Obstructed sky or large baseline | Move to open sky. Check that RTKdata has base station coverage in your area via the [coverage map](https://rtkdata.com). | | Corrections disconnect mid-survey | Unstable cellular connection | Check signal strength. The receiver will auto-reconnect when the connection stabilizes. | ## Tips and tricks * **Always use RTCM v3** — this is the only correction type compatible with RTKdata's single-baseline architecture. * **Save the survey style** so your crew can reuse it across projects without reconfiguring each time. * **Check correction age** on the controller status bar. If it exceeds 5 seconds, your internet connection may be dropping. * **For the R750 machine receiver**, configure the same NTRIP settings through Trimble SitePulse or Trimble WorksOS instead of Trimble Access. * **Firmware updates** improve RTK performance. Keep your receiver and Trimble Access up to date via Trimble Installation Manager. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # Trimble Receivers NTRIP Setup: Single Base RTK Set up Trimble Access and Earthworks with RTKdata NTRIP corrections. RTKdata is not VRS: use a Single Base RTCM v3 style, mountpoint AUTO, to avoid the 90% hang. This guide covers setup for Trimble Access, Trimble Earthworks, and other Trimble controllers (TSC5, TSC7, T7, Tablet). Trimble receivers are fully compatible with RTKdata — but require specific settings because **RTKdata is NOT a VRS network**. *** ## Important: RTKdata is NOT VRS > **RTKdata delivers standard RTCM corrections via NTRIP from physical base stations. It does NOT provide Trimble-proprietary VRS/iMAX/CMRx streams.** If you select a "Network RTK" or "VRS" survey style in Trimble Access, the software will wait indefinitely for virtual reference station data that never arrives. This is the #1 cause of Trimble connection failures with RTKdata. *** ## Trimble Access Setup (Step-by-Step) ### Step 1: Create a New Survey Style 1. Open **Trimble Access** 2. Go to **Settings** > **Survey Styles** 3. Tap **New** (do NOT modify an existing VRS/Network RTK style) 4. Name it: `RTKdata Single Base` ### Step 2: Configure Correction Source 1. In the survey style, go to **Rover options** > **Correction source** 2. Select: **Internet connection** 3. Set correction type to: **RTCM v3** 4. Do **NOT** select "VRS", "iMAX", "Network RTK", or "CMRx" ### Step 3: NTRIP Settings | Setting | Value | | ------------------- | -------------------------------------------------------------------------------------- | | **Connection type** | NTRIP | | **Host** | `eu.rtkdata.com` (Europe) / `rtk.rtkdata.com` (Global) / `aus.rtkdata.com` (Australia) | | **Port** | `2101` | | **Mountpoint** | `AUTO` | | **Username** | Your NTRIP username (starts with `rtk`) | | **Password** | Your NTRIP password | ### Step 4: Start Survey 1. Go to **Survey** > **Start survey** 2. Select the `RTKdata Single Base` style you just created 3. Wait for satellite lock (6+ satellites) 4. Wait for RTK Fix — this should happen within 30–90 seconds *** ## Common Trimble Problems ### "Starting Survey" Stuck at \~90% **Cause:** You are using a Network RTK / VRS survey style. Trimble Access is waiting for VRS data that RTKdata does not provide. **Fix:** 1. Stop the survey 2. Create a new survey style as described above 3. Make sure the correction type is set to **RTCM v3** (NOT VRS/iMAX) 4. Restart the survey ### Empty Mountpoint List **Cause:** Some Trimble controllers (and Topcon MAGNET Field) cannot parse the RTKdata sourcetable correctly. **Fix:** Do NOT browse for mountpoints. Instead, manually type `AUTO` (ALL CAPS) in the mountpoint field. ### "No Corrections Received" Check these in order: 1. Is your survey style set to **RTCM v3** (not VRS/CMRx)? 2. Is the mountpoint `AUTO` in ALL CAPS? 3. Are you using your **NTRIP credentials** (not website login)? 4. Does the controller have internet access? ### Trimble DA2 / Catalyst Compatibility Trimble Catalyst with a **Free license** may block third-party NTRIP sources. You need at least a **Catalyst Basic** license to use external NTRIP correction services like RTKdata. If you're using Catalyst Free and cannot connect: * Upgrade your Catalyst license, OR * Use the Trimble DA2 with Trimble Access directly (not through Catalyst app) *** ## Trimble Earthworks (Machine Control) Trimble Earthworks handles NTRIP differently than Trimble Access and is generally easier to set up: 1. Go to **GNSS Configuration** > **Corrections** 2. Select **NTRIP** as the correction source 3. Enter the RTKdata server details (same as table above) 4. Mountpoint: `AUTO` 5. Enter your NTRIP credentials Earthworks typically connects without issues because it does not enforce VRS-specific protocols. *** ## Trimble Access vs. Earthworks — Key Differences | Feature | Trimble Access | Trimble Earthworks | | ------------------- | --------------------------------------------- | --------------------------- | | VRS enforcement | Yes — must explicitly select RTCM/Single Base | No — accepts standard NTRIP | | Survey style needed | Yes — create "Single Base" style | No — just configure NTRIP | | Common issue | Stuck at 90% | Rare connection issues | | Mountpoint browsing | Often fails — type manually | Usually works | *** ## Recommended Settings Summary | Setting | Value | | ----------------- | ----------------------------------------- | | Survey style type | Single Base / RTCM | | Correction format | RTCM v3 | | NTRIP version | v1 or v2 (both work) | | GGA sending | Automatic (enabled by default in Trimble) | | Mountpoint | `AUTO` (typed manually, ALL CAPS) | | Port | `2101` | *** ## Still Not Working? Before contacting support, gather: 1. Screenshot of your survey style settings (correction source section) 2. Screenshot of the NTRIP connection settings 3. Your Trimble controller model and software version 4. The exact error message or behavior Contact support at with this information. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # Leica GS18 & GS16 RTK Setup: NTRIP in Captivate Connect Leica GS18 T, GS16, and GS07 receivers to RTKdata NTRIP in Captivate. Bluetooth internet, RTK rover profile, mountpoint AUTO, GGA, and tilt setup. The Leica GS18 T, GS16, and GS07 are professional survey-grade GNSS receivers by Leica Geosystems (Hexagon). The GS18 T is the flagship model featuring calibration-free tilt compensation — measure without leveling the pole. These receivers are configured through **Leica Captivate** software running on a CS20 or CS35 controller. The GS07 can also be configured via the Leica Captivate app on a smartphone. ## Requirements * **Leica GS18 T, GS16, or GS07** powered on with clear sky visibility * **Leica Captivate** on a CS20 or CS35 controller (or Captivate app for GS07) * **Internet connection** via phone hotspot over Bluetooth, USB tethering, or controller SIM card * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with Leica adapter {% 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 %} ### Set up internet connection 1. On the CS20/CS35 controller, go to **Settings** → **Connections** → **Internet connections**. 2. Tap **New** to create a new internet profile. 3. Select **Bluetooth** (for phone hotspot) or **USB** (for USB tethering). 4. If using Bluetooth, pair your phone with the controller first under **Settings → Connections → Bluetooth**. 5. Enable your phone's mobile hotspot and confirm the controller shows "Internet connected." {% hint style="warning" %} The controller must have an active internet connection before RTK corrections will work. If you see "No internet," verify your phone's hotspot is active and Bluetooth is paired. {% endhint %} {% endstep %} {% step %} ### Create an RTK rover profile 1. Go to **Settings** → **RTK Rover** → **RTK Network profile**. 2. Tap **New** to create a new profile. 3. Name it **RTKdata**. 4. Set **Network type** to **Direct IP** or **NTRIP**. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the connection fields. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not browse the mountpoint table — Leica Captivate may time out or return an empty list if the source table is large. {% endhint %} {% endstep %} {% step %} ### Configure GGA position sending 1. In the RTK profile settings, ensure **Send GGA position** is set to **On** or **Automatic**. 2. This sends your approximate position to RTKdata so the correct base station corrections are generated for your location. {% endstep %} {% step %} ### Start the RTK survey 1. Tap **Survey** → **Start** from the main menu. 2. Select the **RTKdata** RTK profile you created. 3. Captivate connects to the internet, then to the NTRIP caster. 4. Watch the solution status in the status bar: **Navigated** → **Float** → **Fixed**. 5. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## GS18 T tilt compensation The GS18 T features calibration-free tilt compensation using an integrated IMU. Once RTK Fix is achieved, tilt compensation activates automatically — no initialization routine required. You can measure with the pole tilted up to 30 degrees. The controller displays a tilt icon and the compensated position in real time. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in Leica Captivate under **Settings → Coordinate system → Height mode** if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------ | | "No internet connection" | Phone hotspot not paired or inactive | Verify Bluetooth pairing between controller and phone. Restart the phone's hotspot. | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address is correct. | | Wrong network type selected | "Network RTK" instead of Direct IP/NTRIP | Edit the RTK profile and change the network type. RTKdata is a standard NTRIP caster. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | ## Tips and tricks * **Bluetooth internet is the most common setup** — pair your phone once and it auto-reconnects on future surveys. * **Save the RTK profile** so your entire crew can load it on their controllers without re-entering settings. * **GS07 users** can configure NTRIP directly in the Leica Captivate app on Android, using the same settings above. * **Check "Correction age"** on the Captivate status bar. Values above 5 seconds indicate an unstable internet link. * **For Leica iCON construction receivers**, the same NTRIP settings apply — configure them in iCON field software. * **Keep firmware updated** via Leica myWorld to benefit from the latest constellation support and RTK improvements. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # ArduSimple simpleRTK2B NTRIP Setup: F9P RTK Connect the ArduSimple simpleRTK2B / simpleRTK3B (u-blox ZED-F9P) to RTKdata NTRIP for centimeter RTK. Bluetooth phone or USB u-center setup with GGA. The ArduSimple simpleRTK2B is the most popular low-cost RTK board, built around the **u-blox ZED-F9P** multi-band GNSS module. It tracks GPS, GLONASS, Galileo, and BeiDou on L1/L2 frequencies and delivers centimeter-level accuracy with RTK corrections. The newer simpleRTK3B uses the u-blox ZED-F9R with built-in IMU for dead reckoning. Both boards are compatible with the ArduSimple RTK Handheld kit and the RTK Calibrated Surveyor kit. This guide covers two setup methods: Bluetooth to phone (fieldwork) and direct USB to PC (bench testing). ## Requirements * **ArduSimple simpleRTK2B** or **simpleRTK3B** board with GNSS antenna and clear sky view * **Method A:** Smartphone with Bluetooth and the Lefebure NTRIP Client or SW Maps app (Android) * **Method B:** Windows PC with USB cable and u-blox u-center installed * **RTKdata.com account** with active RTK credentials (username starting with `rtk`) * **ArduSimple Bluetooth module** (XBee socket) if using Method A {% 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 %} ## Method A: Bluetooth to Phone (Lefebure or SW Maps) This is the recommended method for field use. Your phone runs the NTRIP client and forwards RTCM corrections to the F9P over Bluetooth. {% stepper %} {% step %} ### Prepare the board 1. Insert the ArduSimple Bluetooth module into the **XBee socket** on the simpleRTK2B. 2. Connect your GNSS antenna to the board and place it with a clear sky view. 3. Power the board via USB or battery. The green power LED should be solid. 4. Confirm **UART2 is configured for RTCM input** at the correct baud rate. The default is **38400** for UART2. If you have changed it, use **115200** for best performance. {% hint style="warning" %} If UART2 is not configured to accept RTCM input, corrections from the phone will be ignored. In u-center, go to **UBX-CFG-PRT** and enable RTCM3 on UART2 input. {% endhint %} {% endstep %} {% step %} ### Pair Bluetooth on your phone 1. On your Android phone, go to **Settings > Bluetooth** and scan for devices. 2. Pair with the ArduSimple module (typically named **RTK\_GNSS** or **ArduSimple**). 3. Note the paired device name for the next step. {% endstep %} {% step %} ### Configure the NTRIP client app Open **Lefebure NTRIP Client** or **SW Maps** and create an NTRIP profile with these settings: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} * **Send NMEA GGA to Server:** **ON** (critical — without GGA, RTKdata cannot compute corrections) * **Receiver connection:** Select your paired ArduSimple Bluetooth device. {% endstep %} {% step %} ### Connect and verify RTK Fix 1. Tap **Connect** in the NTRIP client. The app streams RTCM corrections over Bluetooth to the F9P. 2. Monitor the solution status: **3D Fix > DGPS > Float > Fix**. 3. Once the board achieves **RTK Fix**, accuracy drops to **1-2 cm**. Convergence typically takes 30-90 seconds. 4. The **No RTK** LED on the simpleRTK2B should turn off when Fix is achieved. {% endstep %} {% endstepper %} *** ## Method B: USB to PC with u-center This method is ideal for bench testing, firmware updates, and initial board configuration. {% stepper %} {% step %} ### Connect the board to your PC 1. Plug the simpleRTK2B into your PC via USB. Windows should install the driver automatically (u-blox or FTDI). 2. Open **u-center** and select the correct COM port under **Receiver > Connection**. 3. Set the baud rate to **115200** (or **38400** if default). 4. Confirm you see satellite data in the satellite view panel. {% endstep %} {% step %} ### Enable the u-center NTRIP client 1. Go to **Receiver > NTRIP Client Settings**. 2. Enter the connection details for your region: {% tabs %} {% tab title="North America" %} * **Address:** `rtk.rtkdata.com` * **Port:** `2101` * **Username / Password:** Your RTK credentials * **Mountpoint:** `AUTO` {% endtab %} {% tab title="Europe" %} * **Address:** `eu.rtkdata.com` * **Port:** `2101` * **Username / Password:** Your RTK credentials * **Mountpoint:** `AUTO` {% endtab %} {% tab title="Australia" %} * **Address:** `aus.rtkdata.com` * **Port:** `2101` * **Username / Password:** Your RTK credentials * **Mountpoint:** `AUTO` {% endtab %} {% endtabs %} 3. Enable **Send GGA** and set the interval to **5 seconds**. 4. Click **OK** to connect. {% hint style="danger" %} If GGA is not being sent, you will see "0 GGA sessions" in the RTKdata dashboard and the caster will reject the connection. Always verify GGA is enabled. {% endhint %} {% endstep %} {% step %} ### Verify RTK Fix in u-center 1. Open the **Data View** panel (View > Data View). The **Fix Mode** field will show the current solution. 2. Watch the progression: **3D > DGNSS > Float > Fix**. 3. The horizontal accuracy estimate (hAcc) should drop below **0.02 m** at Fix. 4. The u-center map view will show your position converging to a stable point. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Apply a geoid model in your GIS or surveying software if MSL heights are required. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------- | -------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | No GGA sent (0 GGA sessions on dashboard) | GGA output disabled in app or u-center | Enable **Send NMEA GGA** in Lefebure / SW Maps, or enable **Send GGA** in u-center NTRIP settings. | | Wrong COM port in u-center | Multiple USB devices connected | Open Device Manager and confirm which COM port is assigned to the u-blox or FTDI device. | | UART2 not receiving corrections | RTCM input not enabled on UART2 | In u-center, navigate to **UBX-CFG-PRT > UART2** and enable RTCM3 under Protocol In. | | Mountpoint error | Typed in lowercase | Enter `AUTO` in ALL CAPS. Do not browse the mountpoint table. | | Bluetooth pairs but no data flows | Baud rate mismatch | Ensure the Bluetooth module and UART2 are both set to the same baud rate (38400 or 115200). | | Slow convergence or no Fix | Outdated firmware | Update the ZED-F9P firmware via u-center (**Tools > Firmware Update**). Use the latest HPG firmware from u-blox. | ## Tips and tricks * **Update your F9P firmware first.** Newer HPG firmware versions significantly improve Fix time and multi-constellation support. Download from the u-blox website. * **Method A is best for fieldwork** and pairs well with the ArduSimple RTK Handheld kit. Method B is best for initial configuration and bench testing. * **Set UART2 to 115200 baud** for faster RTCM throughput, especially when using multiple constellation corrections. * **The simpleRTK3B (F9R)** adds dead reckoning via its built-in IMU. The NTRIP setup is identical to the simpleRTK2B. * **For the RTK Calibrated Surveyor kit**, the board comes pre-configured with correct UART settings. Skip the UART2 configuration step. * **Log raw data** to the onboard microSD (if equipped) for PPK post-processing as a fallback when NTRIP connectivity is intermittent. ## Related Industry Solutions * [Robotics](https://rtkdata.com/robotics/) * [Drones](https://rtkdata.com/drones/) # Bad Elf Flex NTRIP Setup: Bad Elf GPS App RTK Set up the Bad Elf Flex GNSS receiver with RTKdata NTRIP corrections for centimeter RTK. OS-level Bluetooth pairing and Bad Elf GPS app NTRIP steps. The Bad Elf Flex is a professional-grade multi-frequency GNSS receiver designed for GIS data collection, asset mapping, and field survey. It tracks GPS, GLONASS, Galileo, and BeiDou on multiple frequencies and supports RTK corrections for centimeter-level accuracy. The Flex connects to your iOS or Android device via Bluetooth and is configured through the **Bad Elf GPS** app (called "Bad Elf GNSS" on some platforms). It features a rugged, weather-resistant housing and a built-in rechargeable battery. ## Requirements * **Bad Elf Flex** GNSS receiver, fully charged * **Bad Elf GPS app** (iOS) or **Bad Elf GNSS app** (Android) installed on your phone or tablet * **Internet connection** on your phone (cellular data recommended for field use) * **RTKdata.com account** with active RTK credentials (username and password from your RTK dashboard) * **Survey pole or bipod** with a 5/8"-11 thread mount (optional but recommended) * **Clear sky visibility** — avoid indoor testing {% 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 %} ### Power on and pair at OS level The Bad Elf Flex requires Bluetooth pairing at the operating system level **before** opening the app. This is different from some receivers that pair through the app directly. 1. Press and hold the power button on the Bad Elf Flex until the LED turns on. 2. The Flex enters Bluetooth pairing mode automatically on first boot. On subsequent boots, it reconnects to the last paired device. 3. **On your phone, open Settings → Bluetooth** and pair with the device named **Bad Elf Flex \[serial number]**. 4. Wait for the pairing to complete and show "Connected" in your phone's Bluetooth settings. 5. **Only after OS-level pairing is confirmed**, open the **Bad Elf GPS** app. The Flex should appear as connected in the app's device list. {% hint style="warning" %} If you skip the OS-level Bluetooth pairing and try to connect through the app first, the Flex will not be detected. Always pair in your phone's Bluetooth settings first. {% endhint %} {% endstep %} {% step %} ### Navigate to NTRIP settings 1. In the Bad Elf GPS app, tap on your **connected Flex device**. 2. Tap **Settings** (gear icon). 3. Scroll to **Corrections** or **RTK Corrections** section. 4. Tap **NTRIP** to open the NTRIP client configuration. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the fields. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **Send GGA:** **Enabled** Tap **Save** or **Done** to store the configuration. {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} ### Connect to NTRIP 1. Return to the main device screen. 2. Toggle the **NTRIP connection** to **On** (or tap **Connect**). 3. The app displays correction stream status — look for "Receiving corrections" or similar confirmation. {% endstep %} {% step %} ### Verify RTK Fix 1. Check the solution status indicator in the app. It will show the progression: **Autonomous** → **DGPS/Float** → **RTK Fix**. 2. Once you see **RTK Fix**, the receiver is delivering centimeter-level positions. {% endstep %} {% endstepper %} ## What to expect * **LED indicators:** Green = power on and tracking satellites. Blue blinking = Bluetooth connected. The app provides more detailed status than the LEDs. * **Convergence time:** 30–60 seconds to Float, 60–120 seconds to Fix under open sky. * **Accuracy at Fix:** 1–3 cm horizontal, 2–5 cm vertical. * **Battery life:** Approximately 8–10 hours with Bluetooth and NTRIP corrections active. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). If your project requires orthometric (MSL) heights, apply a geoid transformation in your GIS software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------- | | App does not see the Flex | Bluetooth not paired at OS level | Pair the Flex in your phone's **Bluetooth settings first**, then open the app. This is the most common issue. | | "Connection refused" or timeout | Wrong host or port | Verify the caster host spelling and that port is `2101`. Check for typos. | | "Authentication failed" | Incorrect credentials | Use the credentials from your RTKdata.com RTK dashboard, not your website login email/password. | | Corrections received but stuck on Float | Poor sky conditions or GGA not sent | Make sure **Send GGA** is enabled. Move to open sky away from buildings. | | Mountpoint not found | Lowercase or wrong mountpoint name | Type `AUTO` in all capital letters. Do not select from a list — type it manually. | | App crashes on iOS after update | App version incompatibility | Update both iOS and the Bad Elf GPS app to the latest versions. Restart your phone. | ## Tips and tricks * **Update firmware first.** Before heading to the field, check for firmware updates in the Bad Elf app. Newer firmware often improves RTK performance and connectivity stability. * **Always pair at the OS level before opening the app.** This is the number one support issue with the Flex on both iOS and Android. * **The Flex works with third-party apps too.** Apps like ArcGIS Field Maps, Collector, and other GIS tools can read the Flex's corrected position via Bluetooth GPS. * **Use the app's NMEA log feature** to record raw NMEA sentences for quality assurance or post-processing review. * **For best results, mount the Flex on a pole** at least 1 meter above ground to reduce multipath interference from the ground surface. * **If you work in multiple regions**, create separate NTRIP profiles for each RTKdata server (EU, NA, AUS) and switch as needed. * **Keep your phone within 5–10 meters** of the Flex to maintain a stable Bluetooth connection. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Utilities](https://rtkdata.com/utilities/) # Bad Elf Flex Mini RTK Setup: Bad Elf GPS App Connect the pocket-sized Bad Elf Flex Mini to RTKdata NTRIP for centimeter RTK. Bluetooth pairing, Bad Elf GPS app NTRIP profile, and GGA setup for fieldwork. The Bad Elf Flex Mini is a compact, pocket-sized multi-frequency GNSS receiver that delivers centimeter-level accuracy with RTK corrections. It shares the same core GNSS engine as the full-size Bad Elf Flex but in a significantly smaller and lighter form factor, making it ideal for GIS data collection, utility mapping, and fieldwork where portability matters. The Flex Mini connects to your phone via Bluetooth and is managed through the **Bad Elf GPS** app. ## Requirements * **Bad Elf Flex Mini** GNSS receiver, fully charged * **Bad Elf GPS app** (iOS) or **Bad Elf GNSS app** (Android) * **Internet connection** on your phone (cellular data recommended) * **RTKdata.com account** with active RTK credentials * **Clear sky visibility** for satellite tracking * **Optional:** Pole mount adapter or clip for attaching the Mini to a range pole or backpack {% 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 %} ## Flex Mini vs. Flex — Comparison | Feature | Bad Elf Flex | Bad Elf Flex Mini | | ---------------------- | ------------------------------- | ------------------------------- | | **Size** | Full-size, pole-mountable | Pocket-sized, clip-on | | **Built-in antenna** | Large survey-grade | Compact integrated antenna | | **Battery life** | 8–10 hours | 6–8 hours | | **Accuracy (RTK Fix)** | 1–3 cm | 1–4 cm | | **Weight** | \~340 g | \~150 g | | **Best for** | Survey, stakeout, boundary work | GIS, asset mapping, quick shots | | **Convergence speed** | Faster (larger antenna) | Slightly slower | | **Price** | Higher | Lower | The setup process is nearly identical to the Flex. The main difference is physical handling and slightly different convergence characteristics due to the smaller antenna. ## Step-by-step setup {% stepper %} {% step %} ### Power on and pair at OS level 1. Press and hold the power button on the Flex Mini until the LED activates. 2. On your phone, go to **Settings → Bluetooth** and pair with **Bad Elf Flex Mini \[serial number]**. 3. Wait for the OS to confirm the pairing before proceeding. 4. Open the **Bad Elf GPS** app. The Flex Mini should connect automatically. {% hint style="warning" %} Like the full-size Flex, the Mini requires OS-level Bluetooth pairing before the app will detect it. {% endhint %} {% endstep %} {% step %} ### Open NTRIP configuration 1. Tap your **connected Flex Mini** in the app. 2. Tap the **Settings** (gear icon). 3. Navigate to **Corrections** or **RTK Corrections**. 4. Tap **NTRIP** to configure the correction source. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the fields. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **Send GGA:** **Enabled** Tap **Save** or **Done**. {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} ### Connect and verify 1. Toggle the NTRIP connection **On**. 2. The app will show correction stream status. Look for "Receiving corrections" or a data rate indicator. 3. Monitor the solution: **Autonomous** → **Float** → **RTK Fix**. {% endstep %} {% endstepper %} ## What to expect * **LED indicators:** Solid green = tracking satellites. Blinking blue = Bluetooth active. Check the app for detailed solution status. * **Convergence time:** The Flex Mini's smaller antenna means convergence may take slightly longer than the full Flex. Expect 30–90 seconds to Float and 60–180 seconds to Fix. * **Accuracy at Fix:** 1–4 cm horizontal, 3–6 cm vertical. The compact antenna trades a small amount of precision for portability. * **Battery life:** 6–8 hours with Bluetooth and NTRIP active. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Apply a geoid model in your GIS software if orthometric elevations are required. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | -------------------------------- | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | Flex Mini not appearing in app | Bluetooth pairing incomplete | Pair in phone Bluetooth settings first, then open the Bad Elf app. | | "Authentication failed" | Wrong credentials | Use credentials from your RTKdata.com RTK dashboard. The username starts with `rtk`. | | Stuck on Float for extended time | Compact antenna needs better sky | The Mini is more sensitive to obstructions than the full Flex. Find a location with unobstructed sky in all directions. | | NTRIP disconnects frequently | Weak cellular signal | The Mini itself does not connect to the internet — your phone does. Move to better cell coverage or switch networks. | | Mountpoint error | Incorrect formatting | Type `AUTO` in all caps. Do not use lowercase. | | Inconsistent heights | Multipath from body/equipment | Hold the Mini above your head or mount on a short pole to separate it from reflective surfaces. | ## Tips and tricks * **Clip it high.** If you attach the Flex Mini to a backpack or vest, position it on the highest point (shoulder strap) for the best sky visibility. * **Update firmware before fieldwork.** Connect the Mini and check for updates in the Bad Elf app. * **The Mini works great for quick GIS shots** where you need sub-5 cm accuracy without deploying a full survey pole setup. * **For critical survey work, prefer the full-size Flex.** The larger antenna provides more robust Fix stability and faster re-acquisition after obstructions. * **Pair with GIS apps directly.** After the Bad Elf app establishes the NTRIP connection, apps like ArcGIS Field Maps, Mergin Maps, and QField can read the corrected position from the Flex Mini via Bluetooth. * **Carry a small power bank** if your fieldwork sessions exceed 6 hours. The Mini can charge while in use via its USB-C port. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Utilities](https://rtkdata.com/utilities/) # SparkFun RTK Facet Setup: SW Maps or WiFi NTRIP Connect the SparkFun RTK Facet (u-blox ZED-F9P) to RTKdata NTRIP for centimeter RTK. Two paths: Bluetooth with SW Maps or the built-in WiFi config portal. The SparkFun RTK Facet is a GNSS receiver built around the **u-blox ZED-F9P** module, designed for the maker, DIY, and professional surveying community. It tracks GPS, GLONASS, Galileo, and BeiDou on L1/L2 frequencies and delivers centimeter-level accuracy with RTK corrections. The Facet can be configured in two ways: through a Bluetooth-connected NTRIP client app (like SW Maps) on your phone, or through the device's built-in WiFi configuration portal. It features a rechargeable battery, microSD logging, and a standard 5/8"-11 survey pole thread. ## Requirements * **SparkFun RTK Facet** with clear sky visibility * **Smartphone or tablet** with internet connection * **One of the following for NTRIP:** * **Option A (recommended):** SW Maps app (Android) or Lefebure NTRIP Client (Android) connected via Bluetooth * **Option B:** WiFi configuration portal for built-in NTRIP client (no phone app needed — the Facet connects directly to WiFi and fetches corrections itself) * **RTKdata.com account** with active RTK credentials * **Survey pole** (optional, 5/8"-11 thread) {% 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 %} ## Setup Path A: Bluetooth + SW Maps (Android) {% stepper %} {% step %} ### Power on in Rover mode 1. Press the power button on the RTK Facet. The OLED display will show the SparkFun logo, then switch to the status screen. 2. Confirm the device is in **Rover** mode (shown on the display). If it shows "Base," short-press the mode button to switch. 3. The display shows satellite count and solution status. {% endstep %} {% step %} ### Pair via Bluetooth 1. On your Android phone, go to **Settings → Bluetooth** and pair with **RTK Facet-XXXX** (where XXXX is the device serial). 2. Open **SW Maps** (free on Google Play). 3. Tap the **Bluetooth GPS** icon (top bar) → **Select GPS Device** → choose **RTK Facet-XXXX**. 4. SW Maps will confirm "Connected to external GPS." {% endstep %} {% step %} ### Configure NTRIP in SW Maps 1. In SW Maps, tap the **menu** (three lines) → **NTRIP Connection**. 2. Tap **Add** or **Edit** to create a new NTRIP profile. 3. Enter the following settings. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **Send NMEA GGA:** **Enabled** {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. {% endhint %} 4. Tap **Connect**. 5. SW Maps will show "NTRIP Connected" and the solution type will progress toward **RTK Fix**. {% endstep %} {% endstepper %} *** ## Setup Path B: WiFi Configuration Portal This method lets the RTK Facet connect to corrections directly over WiFi, without needing a phone as a data relay. {% stepper %} {% step %} ### Enter WiFi config mode 1. With the Facet powered on, press and hold the mode button until the display shows **WiFi Config** or **AP Mode**. 2. The Facet creates a WiFi access point named **RTK Facet Setup**. {% endstep %} {% step %} ### Connect and open the portal 1. On your phone or laptop, connect to the **RTK Facet Setup** WiFi network. 2. Open a browser and navigate to ****. 3. The RTK Facet configuration portal loads. {% endstep %} {% step %} ### Configure NTRIP client 1. In the web portal, navigate to the **NTRIP Client** section. 2. Enable the NTRIP Client toggle. 3. Enter the settings. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **Transmit NMEA GGA:** **Enabled** {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. {% endhint %} 4. In the **WiFi Networks** section, add your home/office WiFi or phone hotspot credentials so the Facet can reach the internet. 5. Click **Save** and **Exit Config Mode**. 6. The Facet reboots and automatically connects to WiFi and then to the NTRIP caster. {% endstep %} {% endstepper %} ## What to expect * **OLED display:** Shows satellite count, solution type (3D/Float/Fix), horizontal accuracy estimate, and battery level. * **Convergence time:** 20–60 seconds to Float, 30–120 seconds to Fix. * **Accuracy at Fix:** 1.4 cm + 1 ppm horizontal (ZED-F9P specification). * **Battery life:** Approximately 10–14 hours depending on Bluetooth/WiFi usage. * **LED ring:** The Facet has colored LEDs that change based on solution status — check the SparkFun documentation for your firmware version's color scheme. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). If your project requires orthometric heights, apply a geoid model in your GIS software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | -------------------------------------------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | SW Maps cannot find the Facet | Not paired at OS level | Pair in Android Bluetooth settings first, then select in SW Maps. | | WiFi portal won't load at 192.168.4.1 | Not connected to Facet's AP | Verify your device is on the "RTK Facet Setup" WiFi network and not auto-switching to cellular. | | NTRIP connects but no Fix | GGA not being sent | Enable NMEA GGA transmission in either SW Maps or the WiFi portal settings. | | "Mount point does not exist" | Wrong capitalization | Type `AUTO` in all caps. | | Facet gets corrections over WiFi but loses connection outdoors | Out of WiFi range | Use your phone's mobile hotspot as the WiFi network. The Facet will connect to your phone's hotspot for internet access. | | Slow convergence or frequent Float drops | Firmware outdated | Update the Facet firmware via the SparkFun RTK firmware update tool. Newer ZED-F9P firmware significantly improves RTK performance. | ## Tips and tricks * **Path A (Bluetooth + SW Maps) is best for fieldwork** because your phone provides reliable mobile internet. Path B (WiFi) is better for static setups or when you want a phone-free solution using a local WiFi network. * **Update the ZED-F9P firmware** using u-blox u-center. SparkFun ships with a stable firmware, but u-blox regularly improves convergence times and constellation support. * **The microSD card logs raw data** by default. Use these logs for PPK post-processing if your NTRIP connection is intermittent. * **SW Maps is free and powerful.** It supports data collection, stakeout, area calculations, and KML/shapefile export — a full survey workflow at no cost. * **The Facet is open-source.** If you need custom behavior, the firmware is available on SparkFun's GitHub and can be modified with the Arduino IDE. * **For iOS users**, consider Lefebure NTRIP Client or similar apps, as SW Maps is Android-only. ## Related Industry Solutions * [Robotics](https://rtkdata.com/robotics/) * [Surveying](https://rtkdata.com/surveying/) # Septentrio mosaic-X5 NTRIP Setup: RTK Corrections Configure the Septentrio mosaic-X5 for RTK corrections via NTRIP using the web interface or RxTools DataLink. Step-by-step setup for advanced GNSS users. The Septentrio mosaic-X5 is a high-precision, multi-constellation, multi-frequency GNSS receiver module designed for professional and industrial applications. It tracks all current and planned GNSS constellations (GPS, GLONASS, Galileo, BeiDou, NavIC, QZSS, SBAS) across all available frequencies. The mosaic-X5 is aimed at system integrators, autonomous vehicles, precision agriculture, and advanced survey applications where reliability and accuracy are critical. It features a built-in web interface, NTRIP client, and **AIM+ interference mitigation** technology. This guide is intended for advanced users who are comfortable with receiver configuration via web interfaces or desktop software. ## Requirements * **Septentrio mosaic-X5** receiver module on an evaluation board or integrated into your system * **Multi-frequency GNSS antenna** connected to the receiver's antenna input * **USB cable** to connect the receiver to your computer * **Computer** with a web browser (Chrome, Firefox, Edge) or Septentrio **RxTools** software installed * **Internet connection** — either through the computer (using RxTools/DataLink) or via the receiver's Ethernet port (if available on your board) * **RTKdata.com account** with active RTK 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 %} ## Method 1: Web Interface (Recommended) The mosaic-X5 has a built-in web interface that is the simplest way to configure NTRIP. No software installation required. {% stepper %} {% step %} #### Connect and access the web interface 1. Connect the mosaic-X5 to your computer via USB. 2. The receiver appears as a network adapter. Open a browser and go to **** (default address). 3. The mosaic-X5 web interface dashboard loads, showing satellite tracking and position status. {% endstep %} {% step %} #### Configure the NTRIP client 1. In the web interface, navigate to **Communication → NTRIP Client**. 2. Click **New** to create a new NTRIP connection. 3. Fill in the settings. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **NMEA GGA:** **Enabled** / **Auto** {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. {% endhint %} 4. Click **OK** or **Apply**. {% endstep %} {% step %} #### Verify connection 1. The NTRIP Client status in the web interface changes to **Connected**. 2. Navigate to the **Position** page to monitor the solution type. 3. Watch for progression: **Autonomous** → **DGPS** → **RTK Float** → **RTK Fixed**. {% endstep %} {% endstepper %} *** ## Method 2: RxTools (RxControl + DataLink) Use this method if you cannot access the web interface or need more granular control over data routing. {% stepper %} {% step %} #### Launch RxControl 1. Install **RxTools** from Septentrio's support website. 2. Connect the mosaic-X5 via USB. 3. Open **RxControl** and connect to the receiver on the appropriate COM port. 4. Verify satellite tracking on the RxControl skyplot. {% endstep %} {% step %} #### Configure NTRIP via DataLink 1. Open **DataLink** (included in RxTools). 2. Create a **New Serial Connection** linked to the mosaic-X5 COM port. 3. Create a **New NTRIP Client Connection** with the settings for your region (same host, port, username, password, and mountpoint as shown in the tabs above). 4. **Link** the NTRIP connection to the serial connection (enable bidirectional data flow). 5. Click **Connect** on both connections. {% endstep %} {% step %} #### Enable NMEA GGA output 1. In RxControl, go to **Communication → Output → NMEA Output**. 2. Enable **GGA** output on the USB1 port at **1-second intervals**. 3. This ensures the receiver sends its position to RTKdata.com so corrections are calculated for your location. {% endstep %} {% step %} #### Verify 1. DataLink shows data flowing in both directions (corrections in, GGA out). 2. RxControl's position display shows solution progression toward **RTK Fixed**. {% endstep %} {% endstepper %} ## What to expect * **Web interface dashboard:** Real-time satellite skyplot, position quality, differential age, and NTRIP status. * **Convergence time:** The mosaic-X5 is extremely fast. Expect Float in 5–15 seconds and Fix in 15–45 seconds with good sky and antenna. * **Accuracy at Fix:** 0.6 cm + 0.5 ppm horizontal, 1 cm + 1 ppm vertical (receiver specification with quality antenna). * **AIM+ anti-jamming:** The mosaic-X5 actively mitigates RF interference, making it robust in environments near cellular towers or other RF sources. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal** by default. The mosaic-X5 can apply a geoid model internally — upload a geoid grid via the web interface under **Position → Geoid**. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------------------ | --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | Web interface not loading at 192.168.3.1 | USB driver not installed or IP conflict | Install the Septentrio USB driver. Check that your computer's network adapter for the mosaic shows the correct subnet. | | NTRIP Client shows "Authentication error" | Wrong credentials | Use credentials from your RTKdata.com RTK dashboard, not website login. | | No corrections received | GGA not enabled | Enable NMEA GGA output. Without GGA, RTKdata.com cannot determine your position to generate corrections. | | COM port conflict between RxControl and DataLink | Both tools trying to use the same port | Use separate COM ports: one for RxControl, one for DataLink. The mosaic-X5 exposes multiple virtual COM ports over USB. | | Position stuck on Float | Antenna quality or cable issue | Verify antenna connection. Use a survey-grade multi-frequency antenna, not a patch antenna. | | Corrections age climbing | Network latency | Use the RTKdata.com server closest to your location (EU, NA, or AUS). | ## Tips and tricks * **The web interface is the fastest setup path.** You can have NTRIP running in under 2 minutes without installing any software. * **Save your configuration** using the web interface's **Admin → Configuration → Save** so NTRIP auto-connects on power-up. * **The mosaic-X5 supports multiple correction streams** simultaneously. You can configure a backup NTRIP source for redundancy. * **Use the receiver's built-in Ethernet** (on evaluation boards that support it) for a cable-free internet connection, eliminating the need for a computer in the loop. * **For command-line users**, you can configure everything via serial commands. The command to add an NTRIP client is `snti,NTR1,...` — refer to the mosaic-X5 reference guide for full syntax. * **Enable SBF logging** on the microSD card for post-processing. Septentrio's SBF format retains full observation data at configurable rates. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Robotics](https://rtkdata.com/robotics/) * [Transportation](https://rtkdata.com/transportation/) # EOS Arrow Gold NTRIP Setup: EOS Tools Pro RTK Connect the EOS Arrow Gold to RTKdata NTRIP via EOS Tools Pro for centimeter RTK. Bluetooth pairing, GGA, Android mock location, and geoid height setup for GIS. The EOS Arrow Gold is a multi-frequency, multi-constellation GNSS receiver designed for GIS professionals who need sub-meter to centimeter-level accuracy. It tracks GPS, GLONASS, Galileo, and BeiDou on L1/L2/L5 frequencies and supports both RTK and Atlas (Trimble RTX) corrections. The Arrow Gold connects to your phone or tablet via Bluetooth and is managed through the **EOS Tools Pro** companion app. It is widely used in utilities, forestry, municipal GIS, and environmental field mapping. ## Requirements * **EOS Arrow Gold** receiver, fully charged * **EOS Tools Pro** app installed on your phone or tablet (available for iOS and Android) * **Internet connection** on your phone (cellular data for field use) * **RTKdata.com account** with active RTK credentials * **Bluetooth enabled** on your phone * **Survey pole or bipod** (optional, the Arrow Gold has a standard 5/8"-11 thread) * **Clear sky visibility** — take the receiver outside before testing {% 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 %} ### Power on the Arrow Gold 1. Press and hold the power button for 2 seconds. The LED indicators will light up. 2. **Green LED** = power on. **Blue LED blinking** = Bluetooth discoverable. 3. Wait about 30 seconds for the receiver to acquire satellites. {% endstep %} {% step %} ### Pair via Bluetooth 1. Open your phone's **Settings → Bluetooth**. 2. Find and pair with **Arrow Gold \[serial number]** in the device list. 3. Accept the pairing request if prompted. {% endstep %} {% step %} ### Connect in EOS Tools Pro 1. Open the **EOS Tools Pro** app. 2. The app should detect the Arrow Gold automatically. If not, tap **Select Receiver** and choose your Arrow Gold from the list. 3. Once connected, the app displays satellite count, PDOP, and current position accuracy. {% endstep %} {% step %} ### Configure NTRIP 1. In EOS Tools Pro, tap the **Menu** (hamburger icon or gear icon, depending on version). 2. Navigate to **RTK** or **Corrections** settings. 3. Select **NTRIP** as the correction source. 4. Tap **Add** or **Configure** to enter the NTRIP profile. 5. Enter the following settings. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Also configure: * **Send NMEA GGA:** **Enabled** {% hint style="warning" %} Only these four mountpoints are valid. Always use **ALL CAPS**. {% endhint %} 6. Tap **Save** and then **Connect**. {% endstep %} {% step %} ### Verify RTK Fix 1. Return to the main EOS Tools Pro screen. 2. The correction status indicator shows: **Autonomous** → **Float** → **RTK Fix**. 3. The accuracy display will drop from meter-level to centimeter-level once Fix is achieved. {% endstep %} {% step %} ### Set up mock location (Android) For Android users who want their GIS app to automatically receive the corrected position from the Arrow Gold: 1. Go to **Settings → About phone** and tap **Build number** 7 times to enable Developer Options. 2. Navigate to **Settings → Developer Options → Mock location app**. 3. Select **EOS Tools Pro** as the mock location provider. 4. Open your GIS app (ArcGIS Field Maps, QField, Mergin Maps, etc.). It will now use the Arrow Gold's RTK-corrected position as if it were the phone's built-in GPS. **On iOS**, mock location is not available. Instead, configure your GIS app to use the Arrow Gold as an external Bluetooth GNSS source in the app's location settings. {% endstep %} {% endstepper %} ## What to expect * **LED indicators on the Arrow Gold:** * Green solid = powered on * Blue blinking = Bluetooth active * Blue solid = Bluetooth connected * The receiver LEDs do not directly indicate RTK Fix — check EOS Tools Pro for solution status. * **Convergence time:** 20–60 seconds to Float, 30–120 seconds to Fix under open sky. * **Accuracy at Fix:** 1–2 cm horizontal, 2–4 cm vertical with a quality RTK correction source. * **Sub-meter mode:** Even without RTK Fix, the Arrow Gold with Atlas corrections can provide sub-meter accuracy as a fallback. * **Battery life:** Approximately 10–14 hours with Bluetooth and NTRIP corrections active. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal** by default. EOS Tools Pro can apply a geoid model (such as GEOID18 for the US) to display orthometric heights. Go to **Settings → Geoid** to configure this. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------- | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | Arrow Gold not appearing in EOS Tools Pro | Bluetooth not paired | Pair in your phone's Bluetooth settings first, then reconnect in the app. | | "NTRIP Connection Failed" | Incorrect host, port, or no internet | Double-check the caster address and port `2101`. Verify your phone has an active data connection. | | "Invalid credentials" or "Unauthorized" | Wrong username/password | Use the credentials from your RTKdata.com RTK dashboard. The username starts with `rtk` — do not use your website login. | | Corrections received but no Fix | GGA not enabled or poor sky | Ensure **Send NMEA GGA** is turned on. Move to open sky — the Arrow Gold needs visibility to at least 15–20 satellites for reliable Fix. | | Position jumps after losing Fix | Re-convergence after obstruction | This is normal. When you move back to open sky, the solution will re-converge within 30–60 seconds. | | Mountpoint rejected | Typed in lowercase | Enter `AUTO` in all capital letters. | | Mock location not working on Android | Developer Options not enabled or wrong app selected | Verify Developer Options are enabled and EOS Tools Pro is selected as the mock location provider. Restart your phone if needed. | ## Tips and tricks * **EOS Tools Pro shows real-time accuracy** in the status bar. Wait for the horizontal accuracy to drop below 3 cm before collecting critical points. * **Mock location on Android is the recommended workflow.** It lets every app on your phone use the Arrow Gold's corrected position without any special configuration per app. * **On iOS, use the "External GPS" setting** in apps like ArcGIS Field Maps, Collector, or Survey123 to read positions from the Arrow Gold via Bluetooth. * **Configure EOS Tools Pro to display the coordinate system** matching your project (UTM zone, state plane, etc.) for easier verification in the field. * **Keep firmware up to date.** EOS periodically releases firmware updates that improve RTK engine performance. Check the EOS website or contact your dealer. * **For long field sessions**, the Arrow Gold's 10+ hour battery is usually sufficient, but carry a USB power bank for backup. The receiver can operate while charging. * **Save your NTRIP profile.** EOS Tools Pro remembers the last used profile, so subsequent sessions connect automatically when you tap Connect. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Utilities](https://rtkdata.com/utilities/) # Topcon HiPer VR / HR RTK Setup: MAGNET Field Set up the Topcon HiPer VR and HiPer HR with RTKdata NTRIP in MAGNET Field. HiPer VR 4G modem or controller internet, mountpoint AUTO, GGA, and tilt setup. The Topcon HiPer VR and HiPer HR are professional survey-grade GNSS receivers by Topcon Positioning Systems. The HiPer VR is the flagship model with a built-in 4G modem, Universal Tracking technology, and a full GNSS antenna supporting all constellations. The HiPer HR is a lightweight, budget-friendly option that relies on a controller for internet connectivity (no internal modem). Both receivers are configured through **MAGNET Field** software running on an FC-6000, FC-5000, or FC-500 controller. ## Requirements * **Topcon HiPer VR or HiPer HR** powered on with clear sky visibility * **MAGNET Field** v7.0+ on an FC-6000, FC-5000, or FC-500 controller * **Internet connection** via the HiPer VR's internal 4G modem (SIM card) or the controller's cellular/Wi-Fi connection (required for HiPer HR) * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with Topcon adapter {% 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 %} ### Connect to the receiver 1. Power on your HiPer VR or HiPer HR and wait for satellite tracking to begin (LED indicators confirm satellite lock). 2. Open **MAGNET Field** on your FC-6000 or FC-5000 controller. 3. Go to **Configure** > **Survey Styles** and create a new style or edit an existing one. 4. Under **Instrument**, select your Topcon receiver model from the Bluetooth device list and pair if prompted. {% endstep %} {% step %} ### Configure the RTK rover correction source 1. In your survey style, navigate to **RTK** > **Rover**. 2. Set **Correction Source** to **Internet (NTRIP)**. 3. If using the **HiPer VR's internal modem**: select **Receiver Internet** and configure the APN for your mobile carrier if not already set. 4. If using the **controller's internet** (required for HiPer HR): select **Controller Internet** and ensure the controller has an active data connection via cellular or Wi-Fi hotspot. {% hint style="warning" %} The HiPer HR does **not** have an internal modem. You must use the controller's internet connection or tether the controller to a phone hotspot. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **Host / Caster Address:** `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` {% endtab %} {% tab title="Europe" %} * **Host / Caster Address:** `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` {% endtab %} {% tab title="Australia" %} * **Host / Caster Address:** `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` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not browse the mountpoint table — MAGNET Field may time out or return an incomplete list with large casters. {% endhint %} {% endstep %} {% step %} ### Verify GGA position sending 1. In the NTRIP settings, verify that **Send GGA** is set to **On** or **Automatic**. 2. MAGNET Field typically enables GGA by default, but confirm this has not been changed. {% hint style="danger" %} RTKdata requires GGA position data to select the nearest base station. Without GGA, the connection will succeed but no corrections will be delivered. {% endhint %} {% endstep %} {% step %} ### Start the RTK survey 1. Save the survey style and return to the main screen. 2. Tap **Survey** and select the style you just configured. 3. MAGNET Field will connect to the internet, then to the RTKdata NTRIP caster. 4. Watch the solution status: **Autonomous** > **Float** > **Fixed**. 5. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## HiPer VR tilt compensation The HiPer VR includes IMU-based tilt compensation. Once an RTK Fix is achieved, tilt compensation initializes after a brief walk calibration. You can then measure with the pole tilted without leveling. The FC controller displays a tilt icon and compensated position in real time. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in MAGNET Field under **Configure > Coordinate System > Vertical Adjustment** if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | No internet connection (HiPer VR) | SIM card not active or APN misconfigured | Verify the SIM card has data. Configure the correct APN for your carrier in MAGNET Field or the receiver's network settings. | | No internet connection (HiPer HR) | Controller has no data connection | The HiPer HR has no internal modem. Ensure the controller is connected to cellular data or a phone hotspot. | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address is correct. | | No corrections received | GGA sending disabled | Verify **Send GGA** is enabled in the NTRIP settings. RTKdata requires GGA to select the nearest base. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | | NTRIP v2.0 features not available | MAGNET Field version too old | Update to MAGNET Field v7.0 or later for full NTRIP v2.0 support. | ## Tips and tricks * **HiPer VR's built-in 4G modem** provides the most reliable connection — insert a SIM card and select Receiver Internet to avoid phone hotspot dependency. * **HiPer HR users** should pair the controller to a phone hotspot via Wi-Fi or Bluetooth for internet access. * **Save the survey style** so your entire crew can load it on their controllers without re-entering settings each day. * **Update to MAGNET Field v7.0+** for NTRIP v2.0 support, improved connection handling, and the latest constellation support. * **Check correction age** on the MAGNET Field status bar. Values above 5 seconds indicate an unstable internet link. * **Keep receiver firmware updated** via Topcon's Receiver Utility to benefit from the latest RTK engine improvements. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # Sokkia GCX3 / GRX3 RTK Setup: MAGNET Field Set up the Sokkia GCX3 and GRX3 with RTKdata NTRIP in MAGNET Field. Receiver or controller internet, mountpoint AUTO typed manually, GGA, and tilt setup. The Sokkia GCX3 and GRX3 are professional survey-grade GNSS receivers by Sokkia (a Topcon subsidiary). The GCX3 is the flagship model featuring a built-in 4G modem, IMU tilt compensation, and multi-constellation tracking. The GRX3 is a versatile receiver — some models include an internal modem while others rely on a controller for internet connectivity (check your specific model variant). Both receivers are configured through **MAGNET Field** (Sokkia edition) running on an SHC5000 or SHC500 controller. ## Requirements * **Sokkia GCX3 or GRX3** powered on with clear sky visibility * **MAGNET Field** (Sokkia edition) v7.0+ on an SHC5000, SHC500, or compatible controller * **Internet connection** via the receiver's internal 4G modem (SIM card) or the controller's cellular/Wi-Fi connection * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with Sokkia adapter {% 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 {% hint style="info" %} Sokkia is a Topcon subsidiary — MAGNET Field (Sokkia edition) follows the same workflow as the Topcon version. If you are familiar with Topcon HiPer receivers, the NTRIP configuration is identical. {% endhint %} {% stepper %} {% step %} ### Connect to the receiver 1. Power on your GCX3 or GRX3 and wait for satellite tracking to begin (LED indicators confirm satellite lock). 2. Open **MAGNET Field** on your SHC5000 or SHC500 controller. 3. Go to **Configure** > **Survey Styles** and create a new style or edit an existing one. 4. Under **Instrument**, select your Sokkia receiver from the Bluetooth device list and pair if prompted. {% endstep %} {% step %} ### Configure the RTK rover correction source 1. In your survey style, navigate to **RTK** > **Rover**. 2. Set **Correction Source** to **Internet (NTRIP)**. 3. If using the **GCX3's internal modem** (or GRX3 with modem): select **Receiver Internet** and configure the APN for your mobile carrier if not already set. 4. If using the **controller's internet**: select **Controller Internet** and ensure the controller has an active data connection via cellular or Wi-Fi hotspot. {% hint style="warning" %} Not all GRX3 models include an internal modem. If your GRX3 does not have a built-in modem, you must use the controller's internet connection. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **Host / Caster Address:** `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` {% endtab %} {% tab title="Europe" %} * **Host / Caster Address:** `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` {% endtab %} {% tab title="Australia" %} * **Host / Caster Address:** `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` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not browse the mountpoint table — MAGNET Field may time out or return an incomplete list with large casters. {% endhint %} {% endstep %} {% step %} ### Verify GGA position sending 1. In the NTRIP settings, verify that **Send GGA** is set to **On** or **Automatic**. 2. MAGNET Field typically enables GGA by default, but confirm this has not been changed. {% hint style="danger" %} RTKdata requires GGA position data to select the nearest base station. Without GGA, the connection will succeed but no corrections will be delivered. {% endhint %} {% endstep %} {% step %} ### Start the RTK survey 1. Save the survey style and return to the main screen. 2. Tap **Survey** and select the style you just configured. 3. MAGNET Field will connect to the internet, then to the RTKdata NTRIP caster. 4. Watch the solution status: **Autonomous** > **Float** > **Fixed**. 5. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## GCX3 tilt compensation The GCX3 features IMU-based tilt compensation. Once an RTK Fix is achieved, tilt compensation initializes after a brief walk calibration. You can then measure with the pole tilted without leveling. The controller displays a tilt icon and compensated position in real time. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in MAGNET Field under **Configure > Coordinate System > Vertical Adjustment** if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | No internet connection (receiver modem) | SIM card not active or APN misconfigured | Verify the SIM card has data. Configure the correct APN for your carrier in MAGNET Field or the receiver's network settings. | | No internet connection (controller) | Controller has no data connection | Ensure the controller is connected to cellular data or a phone hotspot. | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address is correct. | | No corrections received | GGA sending disabled | Verify **Send GGA** is enabled in the NTRIP settings. RTKdata requires GGA to select the nearest base. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | | NTRIP v2.0 features not available | MAGNET Field version too old | Update to MAGNET Field v7.0 or later for full NTRIP v2.0 support. | ## Tips and tricks * **GCX3's built-in 4G modem** provides the most reliable connection — insert a SIM card and select Receiver Internet to avoid phone hotspot dependency. * **The MAGNET Field workflow is identical to Topcon** — if your crew uses both Sokkia and Topcon receivers, the same survey styles and NTRIP settings apply. * **Save the survey style** so your entire crew can load it on their controllers without re-entering settings each day. * **Update to MAGNET Field v7.0+** for NTRIP v2.0 support, improved connection handling, and the latest constellation support. * **Check correction age** on the MAGNET Field status bar. Values above 5 seconds indicate an unstable internet link. * **Keep receiver firmware updated** via Sokkia's Receiver Utility to benefit from the latest RTK engine improvements. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # CHC i93 / i90 / X7 RTK Setup: LandStar 8 NTRIP Set up CHC i93, i90, i76, i73, and X7 receivers with RTKdata NTRIP in LandStar 8. Choose receiver or controller internet, enable GGA, and reach RTK Fix. The CHC i93, i90, i76, i73, and X7 are professional GNSS receivers by CHC Navigation (CHCNAV). The i93 and i90 are flagship models featuring built-in 4G modems, IMU tilt compensation, and multi-constellation tracking. The i76, i73, and X7 are mid-range receivers sharing the same NTRIP workflow. All receivers are configured through **LandStar 8** field software running on an Android controller or the CHC LT700/LT800 tablet. ## Requirements * **CHC i93, i90, i76, i73, or X7** powered on with clear sky visibility * **LandStar 8** v3.0+ on an Android controller or CHC LT700/LT800 tablet * **Internet connection** via the receiver's internal 4G modem (SIM card — i93/i90) or the controller's cellular/Wi-Fi connection * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with CHC adapter {% 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 %} ### Connect to the receiver 1. Power on your CHC receiver and wait for satellite tracking to begin (LED indicators confirm satellite lock). 2. Open **LandStar 8** on your Android controller. 3. Go to **Device** > **Connect** > **Device**. 4. Select your CHC receiver from the Bluetooth device list and tap **Connect**. 5. LandStar 8 will display the receiver model and current status once connected. {% endstep %} {% step %} ### Configure rover settings and datalink 1. In LandStar 8, go to **Device** > **Connect** > **Device** > **Rover Settings** (or navigate to the Rover configuration screen). 2. Set the **Work Mode** to **Rover**. 3. Under **Datalink**, select **NTRIP**. 4. Choose the internet source: * **Receiver Internal Network** — uses the receiver's built-in 4G modem (i93/i90 with SIM card inserted). Configure the APN for your carrier if prompted. * **Controller Network** — uses the Android controller's internet connection (phone hotspot or mobile data). {% hint style="danger" %} **"Receiver Internal Network" vs "Controller Network"** is the most common confusion point with CHC receivers. If your receiver does not have a SIM card or built-in modem (i76, i73, X7), you **must** select **Controller Network**. Selecting "Receiver Internal Network" on a receiver without a modem will fail silently. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **IP / Server Address:** `rtk.rtkdata.com` * **IP fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% tab title="Europe" %} * **IP / Server Address:** `eu.rtkdata.com` * **IP fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% tab title="Australia" %} * **IP / Server Address:** `aus.rtkdata.com` * **IP fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not browse the mountpoint list — LandStar 8 may time out or return an incomplete list with large casters. {% endhint %} {% endstep %} {% step %} ### Verify GGA position sending 1. In the NTRIP settings, look for a **Send GGA** or **Upload GGA** option and make sure it is **enabled**. 2. GGA is **not always on by default** in LandStar 8 — you must verify this setting. {% hint style="danger" %} RTKdata requires GGA position data to select the nearest base station. Without GGA, the connection will succeed but no corrections will be delivered. Always verify this setting is enabled before starting your survey. {% endhint %} {% endstep %} {% step %} ### Start the RTK survey 1. Tap **Apply** or **OK** to save the rover configuration. 2. LandStar 8 will connect to the internet, then to the RTKdata NTRIP caster. 3. Watch the solution status: **Single** > **Float** > **Fixed**. 4. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## i93 / i90 tilt compensation The i93 and i90 feature IMU-based tilt compensation. Once an RTK Fix is achieved, tilt compensation initializes after a brief walk calibration. You can then measure with the pole tilted without leveling. LandStar 8 displays the tilt angle and compensated position in real time. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in LandStar 8 under your project coordinate system settings if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | -------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | No internet connection (Receiver Internal Network) | SIM card not active, APN misconfigured, or receiver has no modem | Verify the SIM card has data and the APN is correct. If using i76/i73/X7, switch to **Controller Network** — these models may not have a built-in modem. | | No internet connection (Controller Network) | Controller has no data connection | Ensure your Android controller has mobile data or is connected to a Wi-Fi hotspot. | | Selected wrong network source | "Receiver Internal Network" on a receiver without a modem | Switch to **Controller Network** in the Datalink settings. | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address is correct. | | No corrections received | GGA sending disabled | Enable **Send GGA** / **Upload GGA** in the NTRIP settings. This is not always on by default in LandStar 8. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | | NTRIP v2.0 features not available | LandStar 8 version too old | Update to LandStar 8 v3.0 or later for full NTRIP v2.0 support. | ## Tips and tricks * **i93 and i90 built-in 4G modems** provide the most reliable connection — insert a SIM card and select Receiver Internal Network. * **i76, i73, and X7 users** should use Controller Network and tether the controller to a phone hotspot or use the controller's cellular data. * **"Receiver Internal Network" vs "Controller Network"** — remember: Internal = SIM card in the receiver, Controller = internet from your Android device. * **Update to LandStar 8 v3.0+** for NTRIP v2.0 support and improved connection stability. * **Save the rover configuration** so your crew can reuse it across projects without reconfiguring. * **Check correction age** in the LandStar 8 status display. Values above 5 seconds indicate an unstable internet link. * **Keep receiver firmware updated** via CHC's firmware update tool to benefit from the latest RTK engine improvements. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) * [Agriculture](https://rtkdata.com/agriculture/) # Hi-Target V200 / vRTK RTK Setup: Hi-Survey Road Set up the Hi-Target V200 and vRTK with RTKdata NTRIP in Hi-Survey Road. Receiver vs Phone Network, enable GGA (often off), and reach RTK Fixed. The Hi-Target V200 and vRTK are professional survey-grade GNSS receivers by Hi-Target Surveying Instrument Co. Both models feature built-in 4G modems, multi-constellation tracking, and IMU tilt compensation. These receivers are configured through **Hi-Survey Road** field software running on an Android controller or Hi-Target's iHand controller series. ## Requirements * **Hi-Target V200 or vRTK** powered on with clear sky visibility * **Hi-Survey Road** on an Android controller or Hi-Target iHand controller * **Internet connection** via the receiver's built-in 4G modem (SIM card) or the controller's cellular/Wi-Fi connection * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with Hi-Target adapter {% 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 %} ### Connect to the receiver 1. Power on your V200 or vRTK and wait for satellite tracking to begin (LED indicators confirm satellite lock). 2. Open **Hi-Survey Road** on your Android controller. 3. Go to **Device** > **Connect** and select your Hi-Target receiver from the Bluetooth device list. 4. Pair and connect. Hi-Survey Road will display the receiver model and current status. {% endstep %} {% step %} ### Configure the rover work mode 1. In Hi-Survey Road, go to **Device** > **Work Mode** > **Rover**. 2. Under **Datalink**, select **NTRIP**. 3. Choose the internet source: * **Receiver Network** — uses the receiver's built-in 4G modem with a SIM card inserted. Configure the APN for your carrier if prompted. * **Phone Network** — uses the Android controller's internet connection (phone hotspot or mobile data). {% hint style="danger" %} **"Phone Network" vs "Receiver Network"** is the #1 confusion point with Hi-Target receivers. **Receiver Network** = SIM card in the receiver. **Phone Network** = internet from your Android controller/phone. If you select the wrong option, the connection will fail silently with no error message. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **IP / Server Address:** `rtk.rtkdata.com` * **IP fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% tab title="Europe" %} * **IP / Server Address:** `eu.rtkdata.com` * **IP fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% tab title="Australia" %} * **IP / Server Address:** `aus.rtkdata.com` * **IP fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not browse the mountpoint list — Hi-Survey Road may time out or return an incomplete list with large casters. {% endhint %} {% endstep %} {% step %} ### Enable GGA position sending 1. In the NTRIP settings, look for a **Send GGA** or **Upload GGA** toggle and make sure it is **enabled**. 2. GGA is **often OFF by default** in Hi-Survey Road — you must enable this manually. {% hint style="danger" %} RTKdata requires GGA position data to select the nearest base station. Without GGA, the NTRIP connection will appear successful but no correction data will arrive. This is the most common issue with Hi-Target receivers — always enable GGA sending. {% endhint %} {% endstep %} {% step %} ### Start the RTK survey 1. Tap **Apply** or **OK** to save the rover configuration. 2. Hi-Survey Road will connect to the internet, then to the RTKdata NTRIP caster. 3. Watch the solution status: **Single** > **Float** > **Fixed**. 4. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## V200 / vRTK tilt compensation Both the V200 and vRTK include IMU-based tilt compensation. Once an RTK Fix is achieved, tilt compensation initializes after a brief walk calibration. You can then measure with the pole tilted without leveling. Hi-Survey Road displays the tilt angle and compensated position in real time. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in Hi-Survey Road under your project coordinate system settings if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | No internet connection (Receiver Network) | SIM card not active or APN misconfigured | Verify the SIM card has data. Configure the correct APN for your carrier in the network settings. | | No internet connection (Phone Network) | Controller has no data connection | Ensure your Android controller has mobile data or is connected to a Wi-Fi hotspot. | | Selected wrong network source | "Receiver Network" without a SIM card, or "Phone Network" when intending to use the receiver modem | Double-check which internet source is selected. Receiver Network = SIM in receiver. Phone Network = internet from controller. | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address is correct. | | No corrections received | GGA sending disabled (common default) | Enable **Send GGA** / **Upload GGA** in the NTRIP settings. This is often off by default in Hi-Survey Road. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | ## Tips and tricks * **Both V200 and vRTK have built-in 4G modems** — insert a SIM card and select Receiver Network for the most reliable connection. * **Always enable GGA sending** — Hi-Survey Road often has this off by default, which is the most common reason for "connected but no corrections." * **"Phone Network" vs "Receiver Network"** — remember: Receiver = SIM card in the receiver, Phone = internet from your Android device. Selecting the wrong one fails silently. * **Save the work mode configuration** so your crew can reuse it across projects without reconfiguring. * **Check correction age** in the Hi-Survey Road status display. Values above 5 seconds indicate an unstable internet link. * **Keep receiver firmware updated** via Hi-Target's firmware update tool to benefit from the latest RTK engine improvements and constellation support. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # South Galaxy G7 / G6 RTK Setup: SurvX NTRIP Connect the South Galaxy G7 and G6 to RTKdata NTRIP via SurvX. Receiver or phone internet, enable GGA (often off by default), and reach RTK Fixed. The South Galaxy G7 and G6 are professional GNSS receivers by South Surveying & Mapping (a subsidiary of CHCNAV Group). The G7 is the flagship model featuring a built-in 4G modem, IMU tilt compensation, and multi-constellation tracking. The G6 is a mid-range option that may or may not include an internal modem depending on the variant. Both receivers are configured through **SurvX** field software running on an Android controller. ## Requirements * **South Galaxy G7 or G6** powered on with clear sky visibility * **SurvX** field software on an Android controller or tablet * **Internet connection** via the receiver's built-in 4G modem (SIM card — G7) or the controller's cellular/Wi-Fi connection * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with South adapter {% 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 {% hint style="warning" %} SurvX UI labels may vary between versions and regional builds. The software was originally developed in Chinese and translated labels can differ. The steps below use the most common English label names — your version may use slightly different wording. {% endhint %} {% stepper %} {% step %} ### Connect to the receiver 1. Power on your Galaxy G7 or G6 and wait for satellite tracking to begin (LED indicators confirm satellite lock). 2. Open **SurvX** on your Android controller. 3. Go to **Instrument** > **Connect** (or **Device** > **Connect**) and select your South receiver from the Bluetooth device list. 4. Pair and connect. SurvX will display the receiver model and current status. {% endstep %} {% step %} ### Configure the rover work mode 1. In SurvX, go to **Instrument** > **Work Mode** (or **Device** > **Work Mode**). 2. Select **Rover** as the work mode. 3. Under **Datalink**, select **NTRIP**. 4. Choose the internet source: * **Receiver Network** (or **Internal Network**) — uses the receiver's built-in 4G modem with a SIM card inserted. Configure the APN for your carrier if prompted. * **Phone Network** (or **External Network / Controller Network**) — uses the Android controller's internet connection. {% hint style="info" %} If using the receiver's internal modem, you may need to configure the **APN** for your mobile carrier. Common carriers are pre-stored; select yours or enter it manually. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **IP / Server Address:** `rtk.rtkdata.com` * **IP fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% tab title="Europe" %} * **IP / Server Address:** `eu.rtkdata.com` * **IP fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% tab title="Australia" %} * **IP / Server Address:** `aus.rtkdata.com` * **IP fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not browse the mountpoint list — SurvX may time out or return an incomplete list with large casters. {% endhint %} {% endstep %} {% step %} ### Enable GGA position sending 1. In the NTRIP settings, look for a **Send GGA** or **Upload GGA** toggle and make sure it is **enabled**. 2. GGA is **often OFF by default** in SurvX — you must enable this manually. {% hint style="danger" %} RTKdata requires GGA position data to select the nearest base station. Without GGA, the NTRIP connection will appear successful but no correction data will arrive. Always verify GGA sending is enabled before starting your survey. {% endhint %} {% endstep %} {% step %} ### Start the RTK survey 1. Tap **Apply** or **OK** to save the rover configuration. 2. SurvX will connect to the internet, then to the RTKdata NTRIP caster. 3. Watch the solution status: **Single** > **Float** > **Fixed**. 4. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## G7 tilt compensation The Galaxy G7 includes IMU-based tilt compensation. Once an RTK Fix is achieved, tilt compensation initializes after a brief walk calibration. You can then measure with the pole tilted without leveling. SurvX displays the tilt angle and compensated position in real time. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in SurvX under your project coordinate system settings if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------- | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | No internet connection (Receiver Network) | SIM card not active or APN misconfigured | Verify the SIM card has data. Configure the correct APN for your carrier in the network settings. | | No internet connection (Phone Network) | Controller has no data connection | Ensure your Android controller has mobile data or is connected to a Wi-Fi hotspot. | | UI labels do not match this guide | Different SurvX version or regional build | SurvX labels vary between versions. Look for equivalent options — e.g., "External Network" may be labeled "Phone Network" or "Controller Network." | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address is correct. | | No corrections received | GGA sending disabled (common default) | Enable **Send GGA** / **Upload GGA** in the NTRIP settings. This is often off by default in SurvX. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | ## Tips and tricks * **G7's built-in 4G modem** provides the most reliable connection — insert a SIM card and select Receiver Network. * **Always enable GGA sending** — SurvX often has this off by default, which is the most common reason for "connected but no corrections." * **SurvX label inconsistencies** are normal — the software was originally developed in Chinese. If a menu label does not match this guide exactly, look for the closest equivalent. * **Save the work mode configuration** so your crew can reuse it across projects without reconfiguring. * **Check correction age** in the SurvX status display. Values above 5 seconds indicate an unstable internet link. * **Keep receiver firmware updated** via South's firmware update tool to benefit from the latest RTK engine improvements and constellation support. * **G6 users** without a built-in modem should use the controller's internet connection (Phone Network / External Network). ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Agriculture](https://rtkdata.com/agriculture/) # Hemisphere S631 / S321 RTK Setup: PocketMax Connect the Hemisphere S631 and S321 to RTKdata NTRIP via PocketMax for centimeter RTK. Modem or controller internet, GGA, plus VS330 marine setup. The Hemisphere S631 and S321 are professional GNSS receivers by Hemisphere GNSS (a Unicore Communications company). The S631 is the flagship model featuring a built-in 4G modem, multi-constellation tracking, and advanced RTK performance. The S321 is a compact, cost-effective receiver sharing the same NTRIP workflow. Both receivers are configured through **PocketMax** field software running on an Android controller. The Hemisphere VS330, a marine GNSS compass variant, can also connect to RTKdata via terminal commands or GNSS Toolbox. ## Requirements * **Hemisphere S631 or S321** powered on with clear sky visibility * **PocketMax** field software on an Android controller or tablet * **Internet connection** via the receiver's built-in 4G modem (SIM card — S631) or the controller's cellular/Wi-Fi connection * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with Hemisphere adapter {% 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 via PocketMax {% stepper %} {% step %} ### Connect to the receiver 1. Power on your S631 or S321 and wait for satellite tracking to begin (LED indicators confirm satellite lock). 2. Open **PocketMax** on your Android controller. 3. Go to **Config** > **Connect** and select your Hemisphere receiver from the Bluetooth device list. 4. Pair and connect. PocketMax will display the receiver model and current status. {% endstep %} {% step %} ### Configure the GNSS rover corrections 1. In PocketMax, go to **Config** > **GNSS Rover** > **Corrections**. 2. Select **NTRIP Client** as the correction source. 3. Choose the internet source: * **Receiver Modem** — uses the S631's built-in 4G modem with a SIM card inserted. Configure the APN for your carrier if prompted. * **Controller Internet** — uses the Android controller's internet connection (phone hotspot or mobile data). This is the typical option for the S321. {% hint style="info" %} If using the receiver's internal modem, you may need to configure the **APN** for your mobile carrier. Check the receiver's network settings or consult your carrier for the correct APN. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **Host / Caster Address:** `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` {% endtab %} {% tab title="Europe" %} * **Host / Caster Address:** `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` {% endtab %} {% tab title="Australia" %} * **Host / Caster Address:** `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` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not browse the mountpoint list — PocketMax may time out or return an incomplete list with large casters. {% endhint %} {% endstep %} {% step %} ### Verify GGA position sending 1. In the NTRIP settings, ensure **Send GGA** (or **GGA Upload**) is enabled. 2. The receiver must have at least a standalone satellite fix before the NTRIP connection starts. {% hint style="danger" %} RTKdata requires GGA position data to select the nearest base station. Without GGA, the connection will succeed but no corrections will be delivered. {% endhint %} {% endstep %} {% step %} ### Start the RTK survey 1. Tap **Apply** or **OK** to save the rover configuration. 2. PocketMax will connect to the internet, then to the RTKdata NTRIP caster. 3. Watch the solution status: **Autonomous** > **Float** > **Fixed**. 4. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## Hemisphere VS330 (marine variant) The Hemisphere VS330 is a dual-antenna GNSS compass designed for marine applications. It does not use PocketMax — instead, configure NTRIP via **terminal commands** (serial or TCP connection) or **Hemisphere GNSS Toolbox**: 1. Connect to the VS330 via serial port or TCP. 2. Send the NTRIP configuration command with the RTKdata settings (host, port, mountpoint `AUTO`, username, and password). 3. In GNSS Toolbox, navigate to the NTRIP client settings and enter the same parameters as listed in the regional tabs above. Refer to the Hemisphere VS330 Integration Manual for the exact command syntax for your firmware version. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in PocketMax under your project coordinate system settings if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | -------------------------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | No internet connection (Receiver Modem) | SIM card not active or APN misconfigured | Verify the SIM card has data. Configure the correct APN for your carrier in the receiver's network settings. | | No internet connection (Controller Internet) | Controller has no data connection | Ensure your Android controller has mobile data or is connected to a Wi-Fi hotspot. | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address is correct. | | No corrections received | GGA sending disabled | Enable **Send GGA** in the NTRIP settings. RTKdata requires GGA to select the nearest base. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | | VS330 not connecting | Wrong command syntax or firmware version | Verify the NTRIP command syntax matches your VS330 firmware version. Use GNSS Toolbox for a GUI-based alternative. | ## Tips and tricks * **S631's built-in 4G modem** provides the most reliable connection — insert a SIM card and select Receiver Modem to avoid phone hotspot dependency. * **S321 users** should use Controller Internet and tether the controller to a phone hotspot or use the controller's cellular data. * **Save the NTRIP configuration** so your crew can reuse it across projects without reconfiguring. * **Check correction age** in the PocketMax status display. Values above 5 seconds indicate an unstable internet link. * **Hemisphere receivers support RTCM 3.x** messages — this is the format RTKdata delivers. * **Keep receiver firmware updated** via Hemisphere's firmware update utility to benefit from the latest RTK engine improvements. * **For the VS330**, use GNSS Toolbox for easier NTRIP configuration rather than manual terminal commands. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Agriculture](https://rtkdata.com/agriculture/) # GeoMax Zenith60 / 40 RTK Setup: X-PAD Ultimate Set up the GeoMax Zenith60 and Zenith40 with RTKdata NTRIP in X-PAD Ultimate. Receiver 4G or controller internet, mountpoint AUTO, GGA, and Zenith Manager. The GeoMax Zenith60 and Zenith40 are professional survey-grade GNSS receivers by GeoMax (Hexagon). The Zenith60 is the flagship model featuring IMU-based tilt compensation, an integrated 4G LTE modem, and optional UHF radio. The Zenith40 is a mid-range model with similar NTRIP capabilities. Both receivers are configured through **X-PAD Ultimate Survey** software running on an Android controller or tablet, or alternatively via the **Zenith Manager** web interface. ## Requirements * **GeoMax Zenith60 or Zenith40** powered on with clear sky visibility * **X-PAD Ultimate Survey** on an Android controller or tablet (Android 8.0+) * **Internet connection** via the receiver's built-in 4G modem (SIM card inserted), phone hotspot over Wi-Fi, or controller mobile data * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with GeoMax adapter {% 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 via X-PAD Ultimate Survey {% stepper %} {% step %} ### Connect to the receiver 1. Power on your Zenith60 or Zenith40 and wait for satellite tracking to begin (LED indicators will show satellite lock). 2. Open **X-PAD Ultimate Survey** on your controller. 3. Go to **Tool** menu and select **Connect** (or tap the receiver connection icon). 4. Select your Zenith receiver from the Bluetooth device list and pair it. 5. Once connected, X-PAD will display the receiver model and status. {% endstep %} {% step %} ### Set up internet connection 1. If using the **receiver's built-in 4G modem** (Zenith60): insert a SIM card into the receiver's SIM slot. The receiver handles the internet connection internally. 2. If using **controller internet**: ensure your Android device has mobile data or is connected to a phone hotspot. 3. In X-PAD, go to **Tool** > **GNSS Configuration** > **Internet** and verify the connection type matches your setup (Receiver Network for internal SIM, PDA Network for controller internet). {% hint style="warning" %} The Zenith60's built-in 4G LTE modem (Quectel EG25-G) supports LTE FDD, TDD, UMTS, and GSM bands. If using the internal modem, you may need to configure the APN for your mobile carrier under the receiver's network settings. {% endhint %} {% endstep %} {% step %} ### Create an NTRIP rover profile 1. In X-PAD Ultimate, go to **Tool** > **GNSS Configuration** > **Working Mode**. 2. Select **Rover** as the working mode. 3. Under **Connection Mode** or **Data Link**, select **Network** (NTRIP). 4. Tap **New** or **Edit** to configure the NTRIP server profile. 5. Name it **RTKdata**. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not browse the mountpoint table — X-PAD may time out or return an empty list if the source table is large. {% endhint %} {% endstep %} {% step %} ### Enable GGA position sending 1. In the NTRIP profile settings, ensure **Send GGA** (or **Send NMEA GGA to caster**) is set to **On** or **Automatic**. 2. This sends your approximate position to RTKdata so the correct nearest base station corrections are generated for your location. {% hint style="danger" %} RTKdata will not send corrections unless it receives your rover's GGA position. If GGA sending is disabled, the connection will appear successful but no corrections will arrive. {% endhint %} {% endstep %} {% step %} ### Start the RTK survey 1. Tap **Apply** or **OK** to save the rover configuration. 2. Return to the main survey screen and start a new survey or continue an existing project. 3. X-PAD connects to the internet, then to the RTKdata NTRIP caster. 4. Watch the solution status: **Autonomous** > **Float** > **Fixed**. 5. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## Alternative: Setup via Zenith Manager (Web Interface) The Zenith60 and Zenith40 also expose a web-based configuration interface called **Zenith Manager** when connected via Wi-Fi or USB: 1. Connect your phone or laptop to the receiver's Wi-Fi hotspot. 2. Open a browser and navigate to the receiver's IP address (typically shown on the receiver display or in its documentation). 3. In Zenith Manager, go to **Configure** > **Rover** > **Network**. 4. Enter the NTRIP caster details (host, port, mountpoint, username, password) as listed above. 5. Select **Connect GPRS** in the status panel to start receiving corrections. This method is useful for quick testing or when X-PAD is not available. ## Zenith60 tilt compensation The Zenith60 features IMU-based tilt compensation. Once RTK Fix is achieved, tilt compensation activates — you can measure with the pole tilted without leveling. The Cube-a or X-PAD software will prompt you to initialize the IMU sensor if needed (walk a few steps). Initialization typically takes only a few seconds. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in X-PAD under your project coordinate system settings if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ---------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | No internet connection | SIM card not active or APN not configured | Check that the SIM card has data. Configure the correct APN for your carrier in the receiver's network settings. | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address. | | No corrections received | GGA sending disabled | Enable **Send GGA** in the NTRIP profile settings. RTKdata requires GGA to select the nearest base. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | | "Connection failed" in X-PAD | Wrong network type selected | Ensure you selected **Network** (not UHF or Bluetooth) as the data link for NTRIP. | ## Tips and tricks * **The Zenith60's built-in 4G modem** eliminates the need for a phone hotspot — insert a SIM card and the receiver handles internet connectivity independently. * **Save the NTRIP profile** so your entire crew can load it on their controllers without re-entering settings. * **Zenith40 users** without a built-in modem should use the controller's internet (PDA Network) or pair a phone hotspot. * **Check "Correction age"** on the X-PAD status bar. Values above 5 seconds indicate an unstable internet link. * **Keep firmware updated** via GeoMax's firmware update tools to benefit from the latest constellation support and RTK improvements. * **X-PAD Ultimate is also compatible** with other GeoMax GNSS receivers (Zenith06, Zenith10, Zenith20) using the same NTRIP settings. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # Stonex S980A/S900A NTRIP Setup: Cube-a and Web UI Set up the Stonex S980A and S900A with RTKdata NTRIP in Cube-a or the Web UI at 192.168.10.1. Receiver or controller internet, mountpoint AUTO, GGA, and tilt. The Stonex S980A and S900A are professional survey-grade GNSS receivers by Stonex. The S980A is the flagship model with IMU tilt compensation, a built-in 4G modem, and multi-constellation tracking. The S900A is a capable mid-range receiver sharing the same NTRIP workflow. Both receivers are configured through **Stonex Cube-a** field software running on an Android controller, or alternatively through the receiver's **built-in Web UI** accessible at `192.168.10.1`. ## Requirements * **Stonex S980A or S900A** powered on with clear sky visibility * **Stonex Cube-a** field software on an Android controller or tablet * **Internet connection** via the receiver's built-in 4G modem (SIM card), phone hotspot, or controller mobile data * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with Stonex adapter {% 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 via Stonex Cube-a {% stepper %} {% step %} ### Connect to the receiver 1. Power on your S980A or S900A and wait for satellite tracking (LED indicators confirm satellite lock). 2. Open **Stonex Cube-a** on your Android controller. 3. Go to **Tool** > **Connect** and select your Stonex receiver from the Bluetooth device list. 4. Pair and connect. Cube-a will display the receiver model and current status. {% endstep %} {% step %} ### Configure the rover working mode 1. In Cube-a, go to **Tool** > **Working Mode**. 2. Select **Rover** as the working mode. 3. Under **Connection Mode**, select **NTRIP**. 4. If using the **receiver's internal SIM card** for internet: select the network type that uses the receiver's modem and configure the APN for your mobile carrier (common carriers are pre-stored in Cube-a; select **Custom** if yours is not listed). 5. If using **controller internet** (PDA Network): select the option that routes internet through the controller/tablet. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **Host / Caster IP:** `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` {% endtab %} {% tab title="Europe" %} * **Host / Caster IP:** `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` {% endtab %} {% tab title="Australia" %} * **Host / Caster IP:** `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` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. Do not tap "Recover Mountpoint" or "Recupera Mountpoint" to browse the source table — it may time out or return an incomplete list with large casters. Simply type `AUTO` directly. {% endhint %} {% endstep %} {% step %} ### Verify GGA position sending 1. In the NTRIP settings, ensure **Send GGA** (or **Send NMEA position**) is enabled. 2. RTKdata requires your rover's GGA position to select the nearest base station and generate corrections for your location. {% hint style="danger" %} RTKdata will not send corrections unless it receives your rover's GGA position. If GGA sending is disabled, the NTRIP connection will appear successful but no correction data will arrive. {% endhint %} {% endstep %} {% step %} ### Apply and start the survey 1. Tap **OK** and then **Apply** (or **Applica**) to save the rover configuration to the receiver. 2. Return to the main survey screen in Cube-a. 3. Start a new survey or continue an existing project. 4. The receiver connects to the internet, then to the RTKdata NTRIP caster. 5. Watch the solution status: **Autonomous** > **DGPS** > **Float** > **Fixed**. 6. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## Alternative: Setup via Web UI (192.168.10.1) The S980A and S900A also have a built-in web configuration interface: 1. Connect your phone or laptop to the receiver's Wi-Fi hotspot (SSID is typically the receiver serial number). 2. Open a browser and navigate to **`192.168.10.1`**. 3. In the Web UI, go to **Rover Mode** > **Data Link** > **Network**. 4. Enter the Caster Service parameters: host, port, mountpoint, username, and password as listed above. 5. Click **Apply** to save the configuration. 6. The receiver will connect to the NTRIP caster and begin receiving corrections. This method is useful for quick configuration without Cube-a, or when troubleshooting connectivity issues. ## S980A tilt compensation The S980A features IMU-based tilt compensation. Once RTK Fix is achieved, Cube-a will prompt you to initialize the IMU sensor if needed — walk a few steps to calibrate. Initialization typically takes only a few seconds. You can then measure with the pole tilted without leveling. ## Compatible field software In addition to Cube-a, Stonex receivers are compatible with: * **Carlson SurvPC / SurvCE** — configure NTRIP under Equip > GPS Rover > Internet settings * **MicroSurvey FieldGenius** — configure NTRIP under Instrument > GNSS Rover Setup * **QField / QGIS** — use an external NTRIP client app (e.g., Lefebure) to feed corrections via Bluetooth ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in Cube-a under your project coordinate system settings if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------- | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | No internet connection | SIM card not active or APN misconfigured | Check SIM card data plan. Configure the correct APN for your carrier in the network settings (or select Custom in Cube-a). | | Empty mountpoint list | Source table timeout or wrong host | Do not browse — type `AUTO` manually in all caps. Verify the host address. | | No corrections received | GGA sending disabled | Enable **Send GGA** in the NTRIP settings. RTKdata requires GGA to select the nearest base. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | | Web UI not loading | Not connected to receiver Wi-Fi | Connect your device to the receiver's Wi-Fi hotspot first, then navigate to `192.168.10.1`. | | "Connection Mode" not showing NTRIP | Working mode set to Base | Change the working mode to **Rover** first under Tool > Working Mode. | ## Tips and tricks * **The S980A's built-in 4G modem** eliminates the need for a phone hotspot — insert a SIM card and the receiver manages internet connectivity independently. * **Save the NTRIP profile** so your crew can reuse it without re-entering settings each day. * **S900A users** without a built-in modem should use the controller's internet connection. * **Check correction age** in the Cube-a status bar. Values above 5 seconds indicate an unstable internet link. * **The Web UI at 192.168.10.1** is a quick way to verify or change NTRIP settings without launching Cube-a. * **Keep firmware updated** via the Stonex firmware update tool to benefit from the latest GNSS constellation support. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # Tersus Oscar / David RTK Setup: Nuwa App NTRIP Connect the Tersus Oscar and David to RTKdata NTRIP via the Nuwa app. PDA or receiver network, mountpoint AUTO, GGA, and Oscar tilt compensation setup. The Tersus Oscar and David are GNSS receivers by Tersus GNSS. The Oscar is the flagship model featuring IMU-based tilt compensation and a compact smart antenna design for professional surveying. The David is a cost-efficient, palm-sized GNSS receiver designed for surveying, UAV, and agricultural applications. Both receivers are configured through the **Tersus Nuwa** app running on an Android device or controller. ## Requirements * **Tersus Oscar or David** powered on with clear sky visibility * **Tersus Nuwa app** on an Android device or controller * **Internet connection** via the controller/phone mobile data (PDA Network) or the receiver's internal SIM card (Receiver Network, if equipped) * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with Tersus adapter {% 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 via Tersus Nuwa {% stepper %} {% step %} ### Connect to the receiver 1. Power on your Oscar or David receiver and wait for satellite tracking to begin. 2. Open the **Tersus Nuwa** app on your Android device. 3. Go to **Device** (main menu) > **Connect**. 4. Select your Tersus receiver from the Bluetooth device list and pair it. 5. Once connected, Nuwa will display the receiver model, firmware version, and satellite tracking status. {% endstep %} {% step %} ### Create a new rover configuration 1. In Nuwa, go to **Device** > **Rover** > **New** to create a new rover configuration. 2. Name it **RTKdata**. {% endstep %} {% step %} ### Select the data link and protocol 1. Set **Data Link** to one of the following: * **PDA Network** — uses the Android device's internet connection (phone hotspot or mobile data). This is the most common option. * **Receiver Network** — uses a SIM card inserted in the receiver (Oscar models with 4G modem only). 2. Set **Protocol** to **NTRIP**. {% hint style="info" %} **PDA Network** is recommended for most users. It uses the phone/controller's internet connection and does not require a SIM card in the receiver. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **IP (Host):** `rtk.rtkdata.com` * **IP fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mount Point:** `AUTO` {% endtab %} {% tab title="Europe" %} * **IP (Host):** `eu.rtkdata.com` * **IP fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mount Point:** `AUTO` {% endtab %} {% tab title="Australia" %} * **IP (Host):** `aus.rtkdata.com` * **IP fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mount Point:** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. You can also tap the **refresh icon** next to the mountpoint field to fetch the source table, but typing `AUTO` directly is faster and more reliable. {% endhint %} {% endstep %} {% step %} ### Verify GGA position sending Nuwa automatically sends GGA position data to the NTRIP caster when connected as a rover — this is the default behavior and typically does not require manual configuration. However, verify that: 1. GGA sending is not explicitly disabled in the rover settings. 2. The rover has an initial satellite fix (even a standalone fix) before connecting to the caster, so it has a position to send. {% hint style="danger" %} RTKdata requires GGA position data to select the nearest base station. If the rover has no initial position fix, the caster cannot determine which corrections to send. Wait for at least an autonomous position before starting the NTRIP connection. {% endhint %} {% endstep %} {% step %} ### Start the rover 1. Tap **Confirm** to save the rover configuration. 2. Tap **Start** (or the rover will start automatically after confirming). 3. Nuwa connects to the internet, then to the RTKdata NTRIP caster. 4. Watch the solution status in the Nuwa status bar: **Single** > **Float** > **Fixed**. 5. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## Oscar tilt compensation The Oscar features IMU-based tilt compensation. Once RTK Fix is achieved, Nuwa will prompt you to initialize the tilt sensor if needed — walk a few steps to calibrate. Initialization is typically very fast (a few seconds). You can then measure with the pole tilted without leveling. ## David receiver notes The David is a compact, budget-friendly receiver. Key differences from the Oscar: * **No tilt compensation** — the David does not have an integrated IMU. * **Connectivity** — the David may rely on the controller's internet (PDA Network) rather than a built-in modem, depending on the model variant. * **Same Nuwa workflow** — NTRIP configuration steps are identical to the Oscar. ## Compatible field software In addition to Nuwa, Tersus receivers are compatible with: * **SurPad** — third-party Android survey software * **SW Maps** — free Android GIS/survey app with built-in NTRIP client * **Carlson SurvPC** — Windows-based survey software * **QField / QGIS** — use an external NTRIP client or Nuwa in the background ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in Nuwa under your project coordinate system settings if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | No internet connection | Phone/controller has no data | Verify your Android device has mobile data or Wi-Fi connected. If using Receiver Network, check the SIM card and APN settings. | | "Connection failed" | Wrong host or port | Double-check the host address and port `2101`. Try the IP fallback address if the domain does not resolve. | | Mountpoint not found | Typo or wrong case | Type `AUTO` in ALL CAPS. Do not include spaces or extra characters. | | No corrections received | GGA not being sent | Ensure the rover has at least an autonomous fix before connecting. Restart the rover connection if needed. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | | Receiver not found in Bluetooth | Bluetooth not enabled or out of range | Enable Bluetooth on both the receiver and phone. Bring the phone within 10 meters of the receiver. | ## Tips and tricks * **PDA Network is the easiest setup** — it uses your phone's internet directly without needing a SIM card in the receiver. * **Save the rover profile** so you can reuse it across projects without re-entering NTRIP settings. * **Oscar firmware updates** can be applied via USB or over-the-air — keep firmware updated for best RTK performance and constellation support. * **Check correction age** in the Nuwa status bar. Values above 5 seconds indicate an unstable internet link. * **For the David**, consider pairing with a rugged Android phone running Nuwa for a lightweight, portable RTK solution. * **Nuwa supports RTCM 3.1/3.2 transformation messages** (1021-1027) for coordinate system transformations directly in the app. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Robotics](https://rtkdata.com/robotics/) # ComNav T300 / K8 RTK Setup: Survey Master NTRIP Connect the ComNav T300 and K8 to RTKdata NTRIP via Survey Master. Internal modem or PDA CORS, mountpoint AUTO, port 2101, and RTK Quality tips for Fixed. The ComNav (SinoGNSS) T300 and K8 are GNSS receivers by ComNav Technology. The T300 is a widely used professional survey receiver with a built-in 4G modem, UHF radio option, and multi-constellation tracking. The K8 is a compact, cost-effective receiver sharing the same NTRIP workflow. Both receivers are configured through **ComNav Survey Master** field software running on an Android controller. ## Requirements * **ComNav T300 or K8** powered on with clear sky visibility * **Survey Master** field software on an Android controller or tablet * **Internet connection** via the receiver's internal 4G modem (SIM card), phone hotspot, or controller mobile data * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Survey pole** with ComNav adapter {% 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 via Survey Master {% stepper %} {% step %} ### Connect to the receiver 1. Power on your T300 or K8 receiver and wait for satellite tracking to begin. 2. Open **Survey Master** on your Android controller. 3. Turn on Bluetooth on the controller. 4. Go to **Device** > **Connect** and tap **Find Device**. 5. Select the serial number of your ComNav receiver from the Bluetooth device list. 6. Allow pairing. Survey Master will display the receiver information once connected. {% endstep %} {% step %} ### Set the work mode to NTRIP Rover 1. In Survey Master, go to **Device** > **Work Config** (or **Work Mode**). 2. Set **Work Mode** to **Rover**. 3. Set **Data Link** to one of the following: * **Rover NTRIP** (or **Internal NTRIP Client**) — uses the receiver's built-in 4G modem with a SIM card inserted. * **PDA CORS** — uses the Android controller's internet connection (phone hotspot or mobile data). This is useful if the receiver does not have a SIM card. {% hint style="info" %} If using **Internal NTRIP Client** (receiver modem), you will need to configure the **APN** for your mobile carrier. Common APNs are pre-stored; select yours or enter it manually. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields. Select the tab for your region: {% tabs %} {% tab title="North America" %} * **IP / DNS Address:** `rtk.rtkdata.com` * **IP fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint / Source:** `AUTO` {% endtab %} {% tab title="Europe" %} * **IP / DNS Address:** `eu.rtkdata.com` * **IP fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint / Source:** `AUTO` {% endtab %} {% tab title="Australia" %} * **IP / DNS Address:** `aus.rtkdata.com` * **IP fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint / Source:** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in all capital letters. You can also tap **Source List** to browse available mountpoints, but typing `AUTO` directly is faster and avoids source table timeouts. {% endhint %} {% endstep %} {% step %} ### Verify GGA position sending Survey Master automatically sends GGA position data to the NTRIP caster as part of the standard NTRIP handshake. Verify that: 1. GGA sending is not explicitly disabled in the NTRIP settings. 2. The receiver has at least a standalone satellite fix before the NTRIP connection starts. {% hint style="danger" %} RTKdata requires GGA position data to select the nearest base station. Without GGA, the connection will succeed but no corrections will be delivered. {% endhint %} {% endstep %} {% step %} ### Apply and start the survey 1. Tap **Enter** or **Apply** to save the work mode configuration. 2. Survey Master will connect to the NTRIP caster and begin receiving corrections. 3. You can verify the connection status under **Device Info** > **Status**. 4. Watch the solution status: **Single** > **Float** > **Fixed**. 5. Once Fixed, you are ready to collect points, stake out, or run your survey workflow. {% endstep %} {% endstepper %} ## Alternative: Setup via ComNav Web UI ComNav T300 receivers with built-in Wi-Fi also expose a web-based configuration interface: 1. Connect your phone or laptop to the receiver's Wi-Fi hotspot. 2. Open a browser and navigate to the receiver's IP address (check the receiver manual for the default address). 3. Navigate to the RTK work mode settings and enter the NTRIP parameters as listed above. 4. Apply the configuration. ## Known quirk: RTK quality setting {% hint style="warning" %} ComNav receivers have an **RTK Quality** parameter that defaults to **Quick** on some firmware versions. This mode can produce false Fix solutions under marginal conditions. If you notice unreliable Fix positions, change the RTK Quality setting from **Quick** to **Normal** in the receiver's advanced settings. This forces stricter ambiguity resolution and more reliable solutions. {% endhint %} ## Compatible field software In addition to Survey Master, ComNav receivers are compatible with: * **CGSurvey** — ComNav's alternative field software (PDA CORS mode available) * **Carlson SurvPC / SurvCE** — configure NTRIP under Equip > GPS Rover > Internet settings * **MicroSurvey FieldGenius** — configure NTRIP under Instrument > GNSS Rover Setup * **SW Maps** — free Android GIS/survey app with built-in NTRIP client ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). Configure a geoid model in Survey Master under your project coordinate system settings if your project requires orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------- | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | No internet connection (Internal NTRIP) | SIM card or APN issue | Verify the SIM card has data. Configure the correct APN for your carrier. | | No internet connection (PDA CORS) | Controller has no data | Verify your Android device has mobile data or Wi-Fi. | | Mountpoint not found | Typo or wrong case | Type `AUTO` in ALL CAPS. Do not include spaces. | | No corrections received | GGA not being sent | Ensure the receiver has at least a standalone fix. Restart the rover connection. | | False Fix / unreliable positions | RTK Quality set to Quick | Change RTK Quality from **Quick** to **Normal** in advanced receiver settings. | | Stuck on Float | Poor sky conditions or far from base | Move to open sky. Check RTKdata base coverage at [rtkdata.com](https://rtkdata.com). | | Credentials rejected | Using website login instead of RTK credentials | Use the username (starting with `rtk`) and password from your RTK dashboard, not your website account. | | Bluetooth pairing fails | Device not discoverable | Restart the receiver. Ensure Bluetooth is enabled on both devices. Use **Find Device** in Survey Master. | ## Tips and tricks * **The T300's built-in 4G modem** provides reliable internet without needing a phone hotspot — insert a SIM card and select Internal NTRIP Client mode. * **PDA CORS mode** is the quickest way to get started if you do not have a SIM card for the receiver — it routes internet through the controller. * **Save the work configuration** so your crew can reuse it across projects without reconfiguring. * **Check correction age** in the Survey Master status display. Values above 5 seconds indicate an unstable internet link. * **ComNav receivers support RTCM 3.2** including MSM5 messages — this is the format RTKdata delivers. * **Keep firmware updated** via the ComNav firmware update utility to benefit from the latest RTK engine improvements. * **For the K8**, pair with a rugged Android phone running Survey Master for a lightweight, cost-effective RTK solution. ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # Drone RTK Setup: DJI, Autel & Skydio NTRIP Connect DJI, Autel, Skydio and XAG drones to RTKdata NTRIP corrections for centimeter RTK. Setup guides plus universal credentials, port 2101, AUTO. ## Supported Platforms (Ready) Click on your drone model to view the step-by-step setup guide. ### DJI Enterprise (Mapping & Inspection) * [**DJI Mavic 3 Enterprise (3E / 3T / 3M)**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-mavic-3-enterprise-rtk) * [**DJI Matrice Series (M30 / M300 / M350)**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-matrice-4-enterprise-rtk) * [**DJI Dock 3 / Matrice 4D**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-dock-3-matrice-4d) ### DJI Agriculture (Spraying) * [**DJI Agras T50 / T40 / T25 / T30**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-agras-t50-t40-t25) * [**DJI Agras T70P / T100**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-agras-t70p-t100) ### Autel Robotics * [**Autel EVO II Pro RTK V3 / Enterprise (640T)**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/autel-evo-ii-rtk) * [**Autel EVO Max 4T / 4N (and Alpha)**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/autel-evo-max-4t-4n) ### Skydio * [**Skydio X10 / X10D**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/skydio-x10) ### XAG (Agriculture) * [**XAG P100 / P150**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/xag-p100-p150) ### Fixed-Wing / Survey * [**senseFly / AgEagle eBee X / Geo / TAC**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/ebee-x-ebee-geo) ### Open Flight Stacks (any PX4 / ArduPilot drone) * [**Mission Planner (ArduPilot)**](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/mission-planner) * [**QGroundControl (PX4)**](https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/qgroundcontrol) ### Legacy Systems * [**DJI Phantom 4 RTK (P4R)**](https://docs.rtkdata.com/integration-hub/drones-and-uavs/dji-phantom-4-rtk) *** ## Coming Soon / Planned We are currently working on detailed guides for the following platforms. *In the meantime, please use the "Universal Setup" below.* * **Freefly Astro / Inspired Flight** (Auterion NTRIP app — verifying) * **Autel Dragonfish** (verifying; NTRIP port must be in the 2000–2999 range) > **Not compatible with real-time NTRIP (PPK-only workflows):** Wingtra, Quantum Systems Trinity, Delair UX11. These post-process corrections after landing and cannot consume a live caster. > **Need a guide urgently?** Contact Support and we will help you set it up personally. *** ## Universal Setup (For All Other Drones) If your drone is listed in "Coming Soon" or not listed at all, use these standard NTRIP credentials. They work with **99% of all RTK drones**. | Parameter | Value | | ------------------- | ------------------------------------------------------------------------ | | **NTRIP Host (EU)** | `eu.rtkdata.com` | | **NTRIP Host (NA)** | `rtk.rtkdata.com` | | **Port** | `2101` | | **User / Account** | [*Copy from Dashboard*](https://rtkdata.com/my-account/rtk-credentials/) | | **Password** | [*Copy from Dashboard*](https://rtkdata.com/my-account/rtk-credentials/) | | **Mountpoint** | `AUTO` | Ensure your Remote Controller is connected to the internet via **Wi-Fi Hotspot** or a **SIM Card**. The drone itself usually does not connect to the internet; the controller relays the data. *** ## Drone FAQ **How much mobile data does RTK use?** NTRIP correction data consumes approximately **1.5 to 2 MB per hour**. Even a small 1GB data plan supports extensive flight operations. Connection latency matters more than bandwidth. **Can I use my iPhone/Android Hotspot?** Mobile hotspots function but present stability challenges during calls or power-saving mode activation. Professional mapping workflows benefit from a **dedicated 4G Dongle** inserted directly into the controller. **Can I use RTK with a consumer drone (Mavic 3 / Mini 4)?** Consumer models lack RTK hardware components and cannot be enabled via software. An alternative approach involves external GNSS receivers for establishing Ground Control Points using PPK/GCP processing methods. **Can I use one login for multiple drones?** Yes — you can enter the same NTRIP credentials in every drone. But only **one drone can be connected at a time**. If a second drone connects with the same credentials, the first drone gets **disconnected** and loses RTK mid-flight. For simultaneous flights, add a data stream per drone from your [account dashboard](https://rtkdata.com/my-account/). **Do I still need Ground Control Points (GCPs)?** RTK-equipped systems significantly reduce GCP requirements to zero or minimal check points. Traditional workflows typically require five to ten reference points. Maintaining at least one check point provides verification assurance. **Which Coordinate System should I use?** Most DJI platforms expect **WGS84** coordinates. Mountpoint `AUTO` selects optimal reference frames automatically, while specific transformations (ETRS89 for regional compliance) require manual selection. *** ## Get Started Stop struggling with unstable connections and complex base stations. Get centimeter-level accuracy on your drone in less than 5 minutes. **Start your 30-Day Free Trial** — No credit card required. Instant setup. [Get My RTK Credentials Now](https://rtkdata.com/my-account/) **Need a custom Enterprise plan for a fleet?** [Check Pricing](https://rtkdata.com/pricing) or [Book a Meeting](https://sales.rtkdata.com/#use). # DJI Mavic 3 Enterprise RTK Setup: DJI Pilot 2 Set up the DJI Mavic 3 Enterprise (3E, 3T, 3M) with RTKdata Custom Network RTK in DJI Pilot 2 for centimeter NTRIP corrections. Port 2101, mountpoint AUTO. Connect the **DJI Mavic 3 Enterprise RTK** (Mavic 3E, 3T, or 3M) to RTKdata.com's NTRIP correction service for centimeter-level positioning. {% hint style="danger" %} The consumer DJI Mavic 3, Mavic 3 Classic, and Mavic 3 Pro do **NOT** have an RTK module. This guide applies only to the Enterprise series with the built-in RTK antenna. {% endhint %} ## Requirements * **Aircraft:** DJI Mavic 3 Enterprise (3E, 3T, or 3M) with RTK module clipped onto the top of the aircraft * **Controller:** DJI RC Pro Enterprise (the standard RC Pro does not support RTK) * **Software:** DJI Pilot 2 — installed and updated to the latest version * **Firmware:** Aircraft firmware updated via DJI Assistant 2 or DJI Pilot 2 * **Internet:** Wi-Fi hotspot from your phone or a USB 4G dongle plugged into the controller's USB-C port * **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 %} ### Power on and link Power on the Mavic 3 Enterprise and the RC Pro Enterprise controller. Wait for them to link. {% endstep %} {% step %} ### Connect to the internet Establish internet access on the controller: * Connect to a phone Wi-Fi hotspot, **or** * Insert a USB 4G dongle into the controller's USB-C port {% endstep %} {% step %} ### Open DJI Pilot 2 Launch **DJI Pilot 2** on the controller and enter the **camera/flight view** so you see the live video feed. {% endstep %} {% step %} ### Open RTK settings * Tap the **three dots (...)** menu icon in the top-right corner * In the settings panel, tap the **RTK** tab on the left sidebar * Toggle **RTK Positioning** to **ON** {% endstep %} {% step %} ### Select Custom Network RTK Under "RTK Service Type", select **Custom Network RTK**. {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} Only these four mountpoints are valid. Typing local CRS names as mountpoints will result in **no corrections**. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} ### Connect and verify * Tap **Connect** to save and apply the settings * Move the drone **outdoors** to an open area with clear sky view — the RTK module requires a GNSS satellite fix before it can communicate with the NTRIP server * Monitor the RTK status indicator in DJI Pilot 2: | Status | Color | Meaning | | ---------- | ------ | ----------------------------------------------------------------------- | | **SINGLE** | Red | Basic GPS fix acquired. No corrections applied yet. | | **FLOAT** | Yellow | Correction data is being received and processed. Accuracy is improving. | | **FIX** | Green | Centimeter-level accuracy is active. Standard deviation below 2 cm. | Convergence from SINGLE to FIX typically takes **30–90 seconds** in open sky conditions. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} 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. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------- | ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | "No RTK Data Available" | Drone is indoors or has no satellite fix | Move outdoors to open sky. The drone will not send GGA position data to the NTRIP server until it acquires satellites. | | "No RTK Data Available" | No internet on controller | Open the Android browser on the controller to verify connectivity. | | "No RTK Data Available" | Wrong credentials | Re-enter username and password from your RTKdata dashboard. Credentials are case-sensitive. | | RTK stays on FLOAT | Obstructed sky view | Move away from buildings, trees, and power lines. | | RTK stays on FLOAT | Out of base station range | Verify your RTKdata subscription is active and you are within 50 km of a base station. | | Connection drops mid-flight | Weak internet connection | Switch from Wi-Fi hotspot to a USB 4G dongle for more stable connectivity. | | RTK tab missing in Pilot 2 | RTK module not attached | The small RTK antenna module must be physically clipped onto the top of the aircraft. Reseat it firmly. | ## Tips * **Firmware matters.** Some older firmware versions had bugs with Custom Network RTK. Always update to the latest version before troubleshooting. * **RTK module must be physically attached.** The RTK antenna clips onto the top of the aircraft. If it is missing or loose, the RTK tab will not appear in DJI Pilot 2. * **For mapping missions**, enable "RTK always on" in the RTK settings so the drone maintains corrections throughout the entire flight. * **Battery swaps:** After swapping batteries, allow 30–60 seconds for RTK to re-converge to FIX. This is normal behavior. * **Cold weather:** RTK convergence can take slightly longer in very cold conditions. Allow extra time before starting a survey mission. * **Consumer Mavic 3 is not supported.** If you own a standard Mavic 3, Mavic 3 Classic, or Mavic 3 Pro, these drones do not have RTK hardware and cannot use NTRIP corrections. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Surveying](https://rtkdata.com/surveying/) # DJI Matrice 4 Enterprise RTK: NTRIP Setup Guide to connecting DJI Matrice 4E RTK to RTKdata via Custom Network RTK in DJI Pilot 2. Covers 4T RTK and DJI Dock 2 configuration for autonomous operations. Connect the **DJI Matrice 4 Enterprise RTK** (4E RTK or 4T RTK) to RTKdata.com for centimeter-level positioning. This guide also covers configuration for the **DJI Dock 2** autonomous docking station. ## Requirements * **Aircraft:** DJI Matrice 4 Enterprise RTK (4E RTK or 4T RTK) — the non-RTK variant does not support network corrections * **Controller:** DJI RC Plus or DJI RC Pro Enterprise * **Software:** DJI Pilot 2 — updated to the latest version with Matrice 4 series support * **Firmware:** Aircraft and controller firmware updated to the latest version * **Internet:** Phone Wi-Fi hotspot or USB 4G dongle connected to the controller * **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 %} #### Power on and link Power on the Matrice 4 Enterprise RTK and the controller. Wait for the link to establish. {% endstep %} {% step %} #### Connect to the internet Connect the controller to the internet via Wi-Fi hotspot or 4G dongle. Verify connectivity by opening a browser. {% endstep %} {% step %} #### Open DJI Pilot 2 Launch **DJI Pilot 2** and enter the **camera/flight view**. {% endstep %} {% step %} #### Open RTK settings * Tap the **three dots (...)** icon in the top-right corner of the screen * Select the **RTK** tab in the left sidebar of the settings panel * Toggle **RTK Positioning** to **ON** {% endstep %} {% step %} #### Select Custom Network RTK Under "RTK Service Type", select **Custom Network RTK**. {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} Only these four mountpoints are valid. Typing local CRS names as mountpoints will result in **no corrections**. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} #### Connect and verify * Tap **Connect** to save and initiate the connection * Move **outdoors** to an open area with clear sky view — the Matrice 4 needs a satellite fix before it sends position data to the NTRIP server * Monitor the RTK status indicator in DJI Pilot 2: | Status | Color | Meaning | Typical Duration | | ---------- | ------ | ------------------------------------------------------- | ---------------- | | **SINGLE** | Red | Basic GNSS fix acquired. No corrections yet. | Immediate | | **FLOAT** | Yellow | Correction data is being received and processed. | 10–30 seconds | | **FIX** | Green | Centimeter-level accuracy achieved. Std dev below 2 cm. | 30–60 seconds | The Matrice 4's improved multi-frequency GNSS antenna converges noticeably faster than older DJI enterprise platforms. {% hint style="info" %} For autonomous mapping flights, wait until you see **FIX** status before launching the mission. This ensures all geotagged photos have centimeter-level accuracy from the start. {% endhint %} {% endstep %} {% endstepper %} ## DJI Dock 2 configuration The Matrice 4 Enterprise RTK is compatible with the **DJI Dock 2** for fully autonomous remote operations. {% stepper %} {% step %} #### Open FlightHub 2 Configure the NTRIP settings in **DJI FlightHub 2** (cloud platform), not in DJI Pilot 2. {% endstep %} {% step %} #### Navigate to RTK settings Open the dock's RTK configuration panel in FlightHub 2. {% endstep %} {% step %} #### Enter RTKdata.com credentials Enter the same RTKdata.com credentials and server settings listed in the tabs above. {% endstep %} {% step %} #### Verify connectivity The Dock 2 uses its own built-in internet connection (Ethernet or 4G), so the controller's connectivity is not relevant for remote missions. {% endstep %} {% endstepper %} {% hint style="info" %} Dock-based operations require the Dock 2 to have a reliable internet connection at all times. Contact RTKdata.com support if you need assistance configuring NTRIP with DJI Dock 2 and FlightHub 2. {% endhint %} ## Vertical reference (heights) {% hint style="info" %} 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. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ---------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------- | | RTK tab not visible | Non-RTK model | Verify your Matrice 4 is the RTK variant. The standard model does not show RTK settings. | | RTK tab not visible | Outdated Pilot 2 | Update DJI Pilot 2. Early releases may not fully support the Matrice 4 series. | | Stuck on FLOAT | Obstructed environment | Move to an open area away from buildings, dense trees, and metal structures. | | Stuck on FLOAT | Out of range | Verify your RTKdata subscription is active and you are within 50 km of a base station. | | Connection fails immediately | Wrong port | Confirm the port is `2101` (not 2102, 8080, or other defaults from other services). | | Connection fails immediately | Wrong credentials | Verify credentials are from the RTKdata dashboard, not your website login. | | Corrections drop mid-flight | Unstable internet | A USB 4G dongle provides more reliable connectivity than a phone hotspot, especially at altitude. | ## Tips * **Firmware updates are critical.** As a 2025 platform, DJI is actively releasing firmware improvements. Always run the latest version for best RTK performance and stability. * **Faster convergence.** The Matrice 4 has a larger multi-frequency RTK antenna than the Mavic 3 Enterprise, resulting in faster convergence and better multipath rejection near buildings. * **For photogrammetry workflows**, keep RTK enabled for the entire flight rather than just during takeoff. This ensures every photo is geotagged with corrected coordinates. * **Pre-flight checklist:** Power on, wait for satellite lock, verify FIX status, then start your mission. Skipping FIX verification is the most common source of inaccurate survey data. * **After a battery swap**, allow 30–60 seconds for RTK to re-converge before resuming the mission. * **Dual controller support.** If using two RC Plus controllers, only the master controller needs internet for RTK. The slave controller does not handle RTK connectivity. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) * [Utilities](https://rtkdata.com/utilities/) # DJI Dock 2 RTK Setup: FlightHub 2 NTRIP Connect the DJI Dock 2 with Matrice 3D to RTKdata NTRIP via FlightHub 2 for centimeter RTK on unattended missions. Ethernet or 4G, port 2101, AUTO. Connect the **DJI Dock 2** autonomous docking station to RTKdata.com for centimeter-level RTK positioning on remote, unattended drone missions. The Dock 2 is configured entirely through **DJI FlightHub 2** (cloud platform) — not DJI Pilot 2. {% hint style="danger" %} The DJI Dock 2 is configured via **DJI FlightHub 2**, not DJI Pilot 2. All RTK settings are entered in the FlightHub 2 web interface. If you need to configure RTK on a handheld controller with DJI Pilot 2 instead, see the [DJI Matrice 4 Enterprise RTK](/integration-hub/drones-and-uavs/dji-matrice-4-enterprise-rtk) or [DJI Mavic 3 Enterprise RTK](/integration-hub/drones-and-uavs/dji-mavic-3-enterprise-rtk) guides. {% endhint %} ## Key capabilities | Feature | Details | | -------------------------- | -------------------------------------------------- | | **Compatible aircraft** | DJI Matrice 3D, Matrice 3TD | | **Configuration platform** | DJI FlightHub 2 (cloud) | | **RTK service type** | Custom Network RTK | | **Connectivity** | Built-in Ethernet (preferred) or 4G modem | | **RTK fallback** | Falls back to standard GPS if RTK connection drops | | **Correction format** | RTCM 3.x via NTRIP | ## Requirements * **DJI Dock 2** with Matrice 3D or Matrice 3TD aircraft * **DJI FlightHub 2** account with the Dock 2 registered and online * **Internet connection** on the Dock 2 via Ethernet (preferred) or built-in 4G modem with active SIM card * **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 %} ### Log into DJI FlightHub 2 Open **DJI FlightHub 2** in your web browser and log into your organization account. Verify that the Dock 2 appears online in the device list. {% endstep %} {% step %} ### Navigate to the Dock 2 RTK settings 1. Select your **Dock 2** from the device list. 2. Open the dock's **Settings** or **Configuration** panel. 3. Navigate to the **RTK** section. {% endstep %} {% step %} ### Enable RTK and select Custom Network RTK 1. Toggle **RTK Positioning** to **ON**. 2. Under RTK Service Type, select **Custom Network RTK**. {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} Only these four mountpoints are valid. Typing local CRS names as mountpoints will result in **no corrections**. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} ### Save and verify connectivity 1. Click **Save** to apply the RTK configuration. 2. The Dock 2 will attempt to connect to the NTRIP caster using its own internet connection (Ethernet or 4G). 3. Check the RTK status in FlightHub 2 — it should show the connection as active. 4. Launch a test mission and monitor the RTK status on the aircraft: | Status | Color | Meaning | | ---------- | ------ | ------------------------------------------------ | | **SINGLE** | Red | Basic GNSS fix. No corrections applied yet. | | **FLOAT** | Yellow | Correction data is being received and processed. | | **FIX** | Green | Centimeter-level accuracy achieved. | {% hint style="info" %} The Dock 2 establishes the NTRIP connection independently — it does not rely on a handheld controller for internet access. Ensure the Dock 2's network connection is stable and always-on. {% endhint %} {% endstep %} {% endstepper %} ## RTK fallback behavior If the RTK connection drops during a mission (e.g., due to a network outage at the Dock 2 site), the aircraft automatically falls back to standard GPS positioning. The mission continues, but accuracy degrades to meter-level until RTK is restored. FlightHub 2 logs any RTK interruptions for post-mission review. ## Vertical reference (heights) {% hint style="info" %} 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. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | | RTK settings not available in FlightHub 2 | Dock 2 is offline | Verify the Dock 2 has an active internet connection and appears online in FlightHub 2. | | Connection fails | Wrong host or port | Double-check the host address for your region and confirm port is `2101`. | | Authentication error | Wrong credentials | Use the username and password from your RTKdata dashboard, not your website login. Credentials are case-sensitive. | | RTK stays on FLOAT | Poor sky view at dock location | Ensure the Dock 2 is installed in an open area without overhead obstructions (trees, buildings, overhangs). | | RTK drops during mission | Unstable internet at dock site | Ethernet is more reliable than 4G. If using 4G, check signal strength and SIM data plan. | | Aircraft falls back to GPS mid-mission | Temporary network interruption | The aircraft resumes RTK automatically when the connection restores. Review FlightHub 2 logs for the interruption cause. | ## Tips * **Ethernet is the preferred connection method.** It provides a more stable and reliable link than 4G, especially for always-on dock installations. * **Test RTK before deploying the Dock 2 permanently.** Run a test mission after installation to confirm RTK FIX is achievable at the dock location. * **Monitor remotely.** FlightHub 2 provides real-time RTK status for all connected docks. Set up alerts for RTK connection failures. * **Firmware updates matter.** Keep both the Dock 2 and aircraft firmware updated. DJI regularly releases improvements for RTK stability and FlightHub 2 integration. * **Network redundancy.** For critical operations, consider connecting the Dock 2 via Ethernet as the primary link and 4G as a failover. * **The Dock 2 handles RTK independently.** Unlike handheld controller setups, the Dock 2 manages its own internet and NTRIP connection. No phone hotspot or controller is needed for remote missions. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Utilities](https://rtkdata.com/utilities/) * [Construction](https://rtkdata.com/construction/) # DJI Dock 3 / Matrice 4D RTK Setup: FlightHub 2 Connect DJI Dock 3 and the Matrice 4D to RTKdata NTRIP corrections via Custom Network RTK in FlightHub 2. Host, port, and ALL CAPS AUTO mountpoint for centimeter RTK. Connect the **DJI Dock 3** and its **Matrice 4D / 4TD** aircraft to RTKdata.com's NTRIP correction service for centimeter-level positioning. The Matrice 4D uses the same DJI NTRIP client as the Matrice 4 Enterprise line, configured for the docked (drone-in-a-box) workflow through **DJI FlightHub 2**. {% hint style="info" %} For the handheld Matrice 4 Enterprise (non-docked) flow, see [DJI Matrice 4 Enterprise RTK](/integration-hub/drones-and-uavs/dji-matrice-4-enterprise-rtk). This page covers the **docked** Dock 3 / M4D workflow configured in **FlightHub 2**. {% endhint %} ## Requirements * **System:** DJI Dock 3 with a Matrice 4D / 4TD aircraft * **Platform:** **DJI FlightHub 2** (cloud) to manage the dock and its RTK source * **Internet:** The dock's wired/cellular connection * **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 %} ### Open the dock's RTK settings in FlightHub 2 In **DJI FlightHub 2**, open the dock's settings and find the **RTK Service Type**. Select **Custom Network RTK** (third-party NTRIP). {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} DJI requires the mountpoint in **ALL CAPS** (`AUTO`). Lowercase or local CRS names will result in **no corrections**. {% endhint %} {% hint style="danger" %} The RTKdata caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections. RTKdata is single-baseline and location-keyed — it is **not** a VRS service. The DJI NTRIP client sends GGA automatically once the aircraft has a satellite fix. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% step %} ### Apply and verify Fix Save the settings. On the next mission, confirm the aircraft reaches **RTK FIX** before the dock releases it for the flight. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights. Apply a geoid model in post-processing if you need orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | -------------------- | --------------------------------- | ---------------------------------------------------------------------------------- | | No corrections | Wrong RTK Service Type | Select **Custom Network RTK** in FlightHub 2, not DJI's own network | | Mountpoint error | Lowercase mountpoint | Enter `AUTO` in ALL CAPS | | Authentication fails | Wrong credentials | Re-enter username/password from the RTKdata dashboard (username starts with `rtk`) | | Stuck on Float | Aircraft has no satellite fix yet | Allow the aircraft to acquire satellites under open sky | ## Tips * **Same DJI NTRIP client** as the Matrice 4 Enterprise — the correction behavior is identical, just configured in FlightHub 2 for the dock. * **ALL CAPS `AUTO`** is mandatory. * **For the handheld M4 Enterprise**, use the [DJI Matrice 4 Enterprise RTK](/integration-hub/drones-and-uavs/dji-matrice-4-enterprise-rtk) guide instead. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Utilities](https://rtkdata.com/utilities/) * [Construction](https://rtkdata.com/construction/) # DJI Phantom 4 RTK Setup: GS RTK App NTRIP Connect the DJI Phantom 4 RTK (P4R) to RTKdata NTRIP in the GS RTK app for centimeter survey accuracy. Custom Network RTK, port 2101, mountpoint AUTO. Connect the **DJI Phantom 4 RTK** to RTKdata.com for centimeter-level positioning. The P4R is a legacy survey drone still widely used for photogrammetry and mapping. This guide covers the complete NTRIP setup using the **GS RTK app**. {% hint style="danger" %} The Phantom 4 RTK uses the **GS RTK app**, NOT DJI Pilot 2. All menu paths in this guide refer to GS RTK. {% endhint %} ## Requirements * **Aircraft:** DJI Phantom 4 RTK (model designation P4R) * **Controller:** DJI P4R controller with built-in screen (or optional CrystalSky monitor) * **Software:** GS RTK app — installed and updated to the latest available version * **Firmware:** Aircraft firmware updated via DJI Assistant 2 * **Internet:** USB 4G dongle strongly recommended (see warning below) * **RTKdata account:** Active subscription with NTRIP credentials {% hint style="warning" %} The P4R controller's built-in Wi-Fi module is known to be weak. Phone hotspot connections are unreliable beyond a few meters of distance. For professional field use, a **USB 4G dongle** plugged directly into the controller is strongly recommended. This is the single most effective upgrade for reliable RTK connectivity with the P4R. {% endhint %} {% 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 %} ### Power on and link Power on the Phantom 4 RTK and the controller. Wait for them to connect. {% endstep %} {% step %} ### Connect to the internet Plug in your USB 4G dongle, or connect to a phone Wi-Fi hotspot through the controller's Wi-Fi settings. {% endstep %} {% step %} ### Open GS RTK Launch the **GS RTK** app on the controller and enter the **flight/camera view**. {% endstep %} {% step %} ### Open RTK settings Tap the **RTK** menu button (located on the left sidebar or in the top status bar area). {% endstep %} {% step %} ### Select Custom Network RTK In the RTK settings screen, select **Custom Network RTK** as the correction source. {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} Only these four mountpoints are valid. Typing local CRS names as mountpoints will result in **no corrections**. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} ### Connect and verify * Tap **Connect** to save and apply the settings * Move the drone **outdoors** to a location with clear, open sky — the P4R needs a GNSS satellite fix before it sends position data to the NTRIP server * Monitor the RTK status indicator in GS RTK: | Status | Color | Meaning | Typical Duration | | ---------- | ------ | ------------------------------------------------------- | ---------------- | | **SINGLE** | Red | Basic GPS fix. No corrections applied. | Immediate | | **FLOAT** | Yellow | Correction data being processed. Accuracy improving. | 30–60 seconds | | **FIX** | Green | Centimeter-level accuracy achieved. Std dev below 2 cm. | 60–120 seconds | The P4R has a smaller GNSS antenna than newer DJI enterprise drones, so convergence takes slightly longer. Allow up to **2 minutes** in partially obstructed environments. {% hint style="info" %} Check the standard deviation readout in GS RTK. When both horizontal and vertical std dev show values under 0.02 m (2 cm), you have a reliable FIX. {% endhint %} {% endstep %} {% endstepper %} ## Battery swap procedure {% hint style="warning" %} This is the most reported issue with the Phantom 4 RTK. The GS RTK app **does not always automatically reconnect** to the NTRIP server after a battery swap. Follow these steps every time: 1. After powering back on, go into the RTK menu and tap **Connect** again 2. Wait for the status to progress back to **FIX** before resuming your mission 3. Plan your flight missions to complete within a single battery whenever possible to avoid reconnection delays {% endhint %} ## Vertical reference (heights) {% hint style="info" %} 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. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ---------------------------------- | -------------------------- | --------------------------------------------------------------------------------------------------------------- | | "Connection Failed" or timeout | No internet on controller | Open a browser on the controller to verify internet access. | | "Connection Failed" or timeout | 4G dongle not detected | Remove and reinsert the dongle. Some older controller firmware has USB detection issues. | | "Connection Failed" or timeout | Wrong port number | Verify the port is `2101`. Do not use default ports from other NTRIP services. | | RTK never leaves FLOAT | Obstructed sky view | The P4R's smaller antenna is more sensitive to obstructions. Move to a completely open area. | | RTK never leaves FLOAT | Out of base station range | Ensure you are within 50 km of an RTKdata base station. | | RTK never leaves FLOAT | Insufficient wait time | Allow at least 2–3 minutes before concluding FIX is not achievable. The P4R converges slower than newer models. | | GS RTK app freezes | Controller hardware limits | Close and reopen GS RTK. If persistent, restart the controller entirely. | | Connection lost after battery swap | Normal P4R behavior | Re-enter RTK settings and tap Connect after every battery swap. | ## Tips * **Use a USB 4G dongle, not Wi-Fi.** The P4R controller's Wi-Fi antenna is notoriously weak. A 4G dongle provides significantly more stable internet for NTRIP corrections in the field. * **Firmware still matters.** Even though the P4R is a legacy product, DJI has released firmware updates that improved RTK stability. Ensure you are on the latest available version. * **Photo geotagging:** The P4R writes RTK-corrected coordinates directly into photo EXIF data. Verify this in your photogrammetry software by checking that coordinate accuracy values are present in the metadata. * **GS RTK only.** The Phantom 4 RTK works exclusively with GS RTK. Do not attempt to use DJI Pilot 2 — it does not support the P4R. * **Cold starts take longer.** If the drone has been powered off for an extended period or moved to a new location, initial GNSS acquisition and RTK convergence will take longer. Allow extra time. * **Survey-grade results:** For best photogrammetry accuracy, fly overlapping grid patterns at consistent altitude with RTK FIX maintained throughout. If FIX is lost mid-flight, note which photos were captured during FLOAT for post-processing quality control. * **End of life planning.** The P4R is no longer manufactured. Consider migrating to the Mavic 3 Enterprise RTK or Matrice 4 Enterprise RTK for continued DJI support and firmware updates. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Surveying](https://rtkdata.com/surveying/) # DJI Agras T50/T40/T25 RTK Setup: Network NTRIP Configure the DJI Agras T50, T40 and T25 spray drones with RTKdata NTRIP for centimeter RTK. Disable D-RTK 2 Search, pick Custom Network RTK, port 2101. Connect the **DJI Agras T50**, **T40**, or **T25** agricultural drone to RTKdata.com for centimeter-level RTK positioning. Accurate positioning is critical for precision spraying, spreading, and field boundary mapping. {% hint style="danger" %} The Agras series uses the **DJI Agras app**, NOT DJI Pilot 2. All menu paths in this guide are specific to the DJI Agras app. {% endhint %} ## Requirements * **Aircraft:** DJI Agras T50, T40, or T25 * **Controller:** DJI Agras Smart Controller (included with the Agras series) * **Software:** DJI Agras app — updated to the latest version * **Firmware:** Aircraft and controller firmware both updated to the latest version * **Internet:** 4G dongle inserted into the controller's USB port with an active SIM card, or a phone Wi-Fi hotspot * **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 %} ### Power on and link Power on the Agras aircraft and the Smart Controller. Wait for them to link. {% endstep %} {% step %} ### Verify internet connectivity If using a 4G dongle, check the signal indicator. If using a phone hotspot, connect via the controller's Wi-Fi settings. {% endstep %} {% step %} ### Open the DJI Agras app Launch the **DJI Agras** app on the controller and enter the **main flight/operation view**. {% endstep %} {% step %} ### Open RTK settings * Tap the **RTK** icon or navigate to **Settings > RTK** * Toggle **RTK** to **ON** {% endstep %} {% step %} ### Disable D-RTK 2 Search {% hint style="danger" %} You **MUST** disable the **"D-RTK 2 Search"** toggle before proceeding. This toggle tells the drone to scan for a DJI D-RTK 2 Mobile Station base. When enabled, it will **conflict with and override** your Network RTK connection. Turn it **OFF**. This is the single most common setup failure with Agras drones. The toggle is often enabled by default. {% endhint %} {% endstep %} {% step %} ### Select Custom Network RTK Under RTK source / RTK service type, select **Custom Network RTK**. {% hint style="warning" %} Do NOT select "D-RTK 2 Mobile Station". You must specifically choose **Custom Network RTK** to use an NTRIP service like RTKdata.com. {% endhint %} {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} Only these four mountpoints are valid. Typing local CRS names as mountpoints will result in **no corrections**. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} ### Connect and verify * Tap **Connect** or **Save** to apply * Move to an **open field area** with the drone — the aircraft needs a satellite fix before corrections can be applied * Monitor the RTK status indicator: | Status | Color | Meaning | | ----------------------- | ------ | ---------------------------------------------------------------------------- | | **SINGLE / Connecting** | Red | Basic GPS fix. Not yet receiving corrections. | | **FLOAT** | Yellow | Correction data arriving and being processed. Typically lasts 30–60 seconds. | | **FIX** | Green | Full centimeter-level accuracy is active. Ready for precision operations. | {% hint style="warning" %} For agricultural operations, always wait for a **green FIX** status before starting a spraying or spreading mission. Running a mission in FLOAT mode can result in overlap gaps or double-sprayed strips. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights (height above mean sea level). If your farm management software uses a specific coordinate reference, you may want to use `AUTO_WGS84` or `AUTO_ITRF2020` as the mountpoint instead of `AUTO`. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------------------------ | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | Drone connects to D-RTK 2 instead of Network RTK | "D-RTK 2 Search" toggle is ON | Go to RTK settings and turn the D-RTK 2 Search toggle **OFF**. Confirm Custom Network RTK is selected. | | "Authentication Failed" | Wrong credentials | Double-check username and password from RTKdata dashboard. They are case-sensitive. | | "Connection Refused" | Wrong host for your region | Verify the host address matches your region (NA, EU, or AUS). | | RTK stays on FLOAT | Obstructed sky | Move to a more open part of the field, away from tree lines and power lines. | | RTK stays on FLOAT | Weak cellular signal | Ensure the 4G dongle has adequate signal. Rural areas often have poor coverage. | | No internet in the field | Poor cellular coverage | Use a higher-gain 4G antenna, or position yourself where signal strength is strongest. | | RTK drops during spraying runs | Cellular signal loss | The drone falls back to standard GPS and resumes RTK when connectivity returns. Check your SIM data plan for throttling. | ## Tips * **Always disable "D-RTK 2 Search" first.** This is the number one issue Agras users face. Check this toggle every time you configure RTK. * **Field mapping accuracy:** Run a boundary mapping flight with RTK FIX before planning your spray route. This ensures centimeter-level field boundaries. * **Multiple battery operations:** RTK will re-converge after each battery swap. Allow 30–60 seconds for FIX before resuming the mission. * **Firmware updates:** DJI frequently updates the Agras firmware for RTK stability improvements. Check for updates before each season. * **T50 vs T40 vs T25:** The RTK setup process is identical across all three models. The only differences are payload capacity, spray width, and flight performance — not RTK configuration. * **Offline fallback:** If you lose cellular coverage entirely during a mission, the Agras will continue operating on standard GPS. Plan critical spray lines for areas with the best cellular reception. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Agriculture](https://rtkdata.com/agriculture/) # DJI Agras T70P / T100 RTK Setup: Network NTRIP Connect the DJI Agras T70P and T100 to RTKdata NTRIP corrections via Custom Network RTK and the D-RTK 3 AG module. Host, port, and AUTO mountpoint for centimeter spraying accuracy. Connect the **DJI Agras T70P** and **DJI Agras T100** spraying/spreading drones to RTKdata.com's NTRIP correction service for centimeter-level positioning. This 2025 Agras generation uses the **D-RTK 3 AG** module and supports custom Network RTK, just like the earlier T50 / T40 / T25 line. {% hint style="info" %} For the previous generation, see [DJI Agras T50 / T40 / T25](/integration-hub/drones-and-uavs/dji-agras-t50-t40-t25). The setup logic is the same; the RTK hardware on the T70P / T100 is **D-RTK 3 AG**. {% endhint %} ## Requirements * **Aircraft:** DJI Agras T70P or T100 with the **D-RTK 3 AG** module * **Controller:** DJI Agras remote controller running the DJI Agras app * **Internet:** Hotspot or SIM on the controller * **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 %} ### Open RTK settings in the DJI Agras app In the DJI Agras app, open **RTK settings** and choose the **Custom Network RTK** (D-RTK 3 / third-party NTRIP) option as the RTK source. {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="danger" %} The RTKdata caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections. RTKdata is single-baseline and location-keyed — it is **not** a VRS service. The DJI NTRIP client sends GGA automatically once the aircraft has a satellite fix. Enter the mountpoint `AUTO` in **ALL CAPS**. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% step %} ### Connect and verify Fix Connect and confirm the RTK status reads **FIX** before starting field operations. The aircraft must be outdoors with a clear sky view. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights**, not orthometric heights. For agricultural spraying this is usually not an issue, but note it if you export survey-grade elevations. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | -------------------- | -------------------------- | ---------------------------------------------------------------------------------- | | No corrections | DJI's own network selected | Choose **Custom Network RTK** and enter the RTKdata caster | | Mountpoint error | Lowercase mountpoint | Enter `AUTO` in ALL CAPS | | Authentication fails | Wrong credentials | Re-enter username/password from the RTKdata dashboard (username starts with `rtk`) | | Stuck on Float | No satellite fix yet | Operate outdoors under open sky | ## Tips * **Same flow as the T50 / T40 / T25** — the D-RTK 3 AG module keeps the custom Network RTK option. * **ALL CAPS `AUTO`** is mandatory. * **One credential set per drone at a time** — for multiple drones spraying simultaneously, add a data stream per drone in your [account dashboard](https://rtkdata.com/my-account/). ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Agriculture](https://rtkdata.com/agriculture/) # Autel EVO II RTK Setup: Custom Network NTRIP Set up the Autel EVO II Pro RTK V3 and Enterprise 640T with RTKdata Custom NTRIP for centimeter accuracy. Region hosts, port 2101, mountpoint AUTO. Connect the **Autel EVO II Pro RTK V3** to RTKdata.com's NTRIP correction service for centimeter-level positioning. This guide also applies to the **EVO II Enterprise RTK (640T)** thermal variant. {% hint style="danger" %} Autel consumer drones such as the **EVO Nano**, **EVO Lite**, and non-RTK EVO II models do **NOT** have an RTK module. This guide applies only to the EVO II Pro RTK V3 and EVO II Enterprise RTK (640T). {% endhint %} ## Requirements * **Aircraft:** Autel EVO II Pro RTK V3 (or EVO II Enterprise RTK 640T) with built-in RTK module * **Controller:** Autel Smart Controller V3 * **Software:** Autel Explorer app — installed and updated to the latest version * **Firmware:** Aircraft and controller firmware updated to the latest version * **Internet:** Wi-Fi hotspot from your phone or mobile data connection on the controller * **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 %} ### Power on and connect to the internet Power on the EVO II Pro RTK V3 and the Autel Smart Controller V3. Wait for them to link, then connect the controller to the internet via Wi-Fi hotspot or mobile data. {% endstep %} {% step %} ### Open Autel Explorer Launch the **Autel Explorer** app on the Smart Controller V3 and enter the camera/flight view. {% endstep %} {% step %} ### Open RTK settings * Tap **Settings** (gear icon) * Navigate to the **RTK** section * Toggle **RTK** to **ON** {% endstep %} {% step %} ### Select Custom NTRIP Select **Custom NTRIP** as the RTK correction source. {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="warning" %} Only these four mountpoints are valid. Typing local CRS names as mountpoints will result in **no corrections**. Always use **ALL CAPS**. {% endhint %} {% endstep %} {% step %} ### Connect and verify * Tap **Connect** to save and apply the settings * Place the drone **outdoors** in an open area with clear sky view — the RTK module needs a GNSS satellite fix before it can communicate with the NTRIP server * Monitor the RTK status indicator in Autel Explorer: | Status | Meaning | | ---------- | ----------------------------------------------------------------------- | | **SINGLE** | Basic GPS fix acquired. No corrections applied yet. | | **FLOAT** | Correction data is being received and processed. Accuracy is improving. | | **FIX** | Centimeter-level accuracy is active. Standard deviation below 2 cm. | Convergence from SINGLE to FIX typically takes **30–90 seconds** in open sky conditions. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} 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. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | No corrections received | Drone is indoors or has no satellite fix | Move outdoors to open sky. The drone must acquire satellites before sending GGA data to the NTRIP server. | | No corrections received | No internet on controller | Verify connectivity by opening a browser on the Smart Controller V3. | | No corrections received | Wrong credentials | Re-enter username and password from your RTKdata dashboard. Credentials are case-sensitive and the username starts with `rtk`. | | RTK stays on FLOAT | Obstructed sky view | Move away from buildings, trees, and power lines. | | RTK stays on FLOAT | Too far from base station | Verify your RTKdata subscription is active and you are within 50 km of a base station. | | Connection drops mid-flight | Weak internet connection | Use a stable hotspot or ensure strong cellular signal on the controller. | ## Tips * **Firmware matters.** Always update the aircraft and Smart Controller V3 to the latest firmware before troubleshooting connectivity issues. * **EVO II Enterprise RTK (640T)** uses the same NTRIP setup flow — the thermal camera variant follows identical RTK configuration steps. * **For mapping missions**, enable persistent RTK in the mission settings so the drone maintains corrections throughout the entire flight. * **Battery swaps:** After swapping batteries, allow 30–60 seconds for RTK to re-converge to FIX. Best accuracy is achieved within 30 km of the nearest reference station. * **Consumer Autel drones are not supported.** The EVO Nano, EVO Lite, and standard EVO II series do not have RTK hardware. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # Autel EVO Max 4T / 4N RTK Setup: Custom NTRIP Connect the Autel EVO Max 4T, 4N, and Alpha to RTKdata NTRIP corrections. Enable RTK, choose Custom Network RTK, and enter host, port, and AUTO mountpoint for centimeter RTK. Connect Autel's current enterprise drones — the **EVO Max 4T**, **EVO Max 4N**, and **Autel Alpha** — to RTKdata.com's NTRIP correction service for centimeter-level positioning. {% hint style="danger" %} The **EVO Max 4T / 4N** require the **optional Autel EVO Max RTK Module**. A base EVO Max without the module has **no RTK** and cannot use RTKdata. The **Autel Alpha** has RTK built in (no module needed). For the older **EVO II Pro RTK V3 / EVO II Enterprise (640T)**, see the separate [Autel EVO II RTK](/integration-hub/drones-and-uavs/autel-evo-ii-rtk) guide. {% endhint %} {% hint style="warning" %} The EVO Max series and Alpha are controlled by the **Autel Enterprise App** on the **Smart Controller V3** — not the **Autel Explorer** app used by the older EVO II line. Menu names below refer to the Autel Enterprise App. {% endhint %} ## Requirements * **Aircraft:** EVO Max 4T or 4N with the **EVO Max RTK Module** installed — or **Autel Alpha** (built-in RTK) * **Controller:** Autel **Smart Controller V3** * **Software:** **Autel Enterprise App**, updated to the latest version * **Firmware:** Aircraft, RTK module (if applicable), and controller firmware updated to the latest version — version mismatches commonly break RTK * **Internet:** Wi-Fi hotspot tethered to the controller (the controller relays the correction stream) * **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 %} ### Install the RTK module (EVO Max only) On the **EVO Max 4T / 4N**, install the **EVO Max RTK Module**. On the **Autel Alpha**, RTK is built in — skip this step. Update aircraft, module, and Smart Controller V3 firmware to the latest version. {% endstep %} {% step %} ### Connect the controller to the internet Tether the Smart Controller V3 to a phone Wi-Fi hotspot (or other internet source). The controller, not the aircraft, carries the NTRIP stream. {% endstep %} {% step %} ### Enable RTK In the **Autel Enterprise App**, open **Settings (gear icon) → RTK** and turn the **RTK Aircraft Feature** **ON**. {% endstep %} {% step %} ### Select Custom (not Network RTK) Choose **Custom** (Custom Network RTK) as the correction source. {% hint style="warning" %} Do **not** select **"Network RTK."** That is a legacy option Autel does not operate and it will not connect to a third-party caster. All third-party casters, including RTKdata, use **Custom**. {% endhint %} {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `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 website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} Enter the mountpoint **`AUTO`** manually (in ALL CAPS) rather than relying on a station list — RTKdata's `AUTO` is keyed to your position, not a fixed station. {% hint style="danger" %} **GGA must be sent.** The RTKdata caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections. Without GGA, the drone connects but receives no corrections and stays on Float. RTKdata is single-baseline and location-keyed — it is **not** a VRS service. The aircraft must have a satellite fix (be outdoors) so it can report position. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% step %} ### Connect and verify Fix * Save/apply the settings to connect. * Place the drone **outdoors** in an open area so the RTK system acquires satellites. * Watch the RTK status in the live view: | Status | Meaning | | ---------- | -------------------------------------------------------- | | **SINGLE** | Basic GNSS fix. No corrections applied yet. | | **FLOAT** | Corrections received and processing. Accuracy improving. | | **FIX** | Centimeter-level accuracy active (\~1–2 cm). | Convergence typically takes 30–90 seconds in open sky. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights (mean sea level). If your workflow requires orthometric heights, apply a geoid model in your post-processing software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------- | -------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | Won't connect to caster | "Network RTK" selected instead of **Custom** | Switch the correction source to **Custom** | | No RTK option at all | EVO Max RTK Module not installed/detected | Install the module (EVO Max) and confirm firmware is current; Alpha has built-in RTK | | No corrections / stuck on Float | Drone indoors or no satellite fix → no GGA sent | Move outdoors to open sky so the aircraft acquires satellites and reports position | | No corrections | No internet on the controller | Verify the Smart Controller V3 hotspot tether | | Authentication fails | Wrong credentials | Re-enter username/password from the RTKdata dashboard (case-sensitive, username starts with `rtk`) | | RTK keeps dropping | Firmware mismatch (aircraft / module / controller) | Update all three to the latest firmware | ## Tips * **EVO Max needs the RTK module; Alpha has RTK built in.** First check which hardware you have. * **Always pick "Custom"** for RTKdata — "Network RTK" is a non-functional legacy option. * **Enter `AUTO` manually** in ALL CAPS as the mountpoint. * **Firmware first.** Mismatched aircraft/module/controller firmware is the most common RTK failure on this platform. * **Different app from EVO II.** EVO Max/Alpha use the Autel Enterprise App; the EVO II line uses Autel Explorer — don't reuse those screenshots. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) # Skydio X10 / X10D NTRIP Setup: Centimeter RTK Set up the Skydio X10 and X10D with RTKdata NTRIP corrections for centimeter RTK. RTK/PPK attachment, NTRIP host and port, AUTO mountpoint, and RTK Fix verification. Connect the **Skydio X10** (and the **X10D** variant) to RTKdata.com's NTRIP correction service for centimeter-level positioning. RTK and PPK on the X10 are provided by an **optional modular RTK/PPK attachment** — they are not built into the base airframe. {% hint style="danger" %} A base X10 **without** the **Skydio RTK/PPK attachment** (part number `DR4ATTRTK`) has no RTK or PPK capability. The attachment is powered by a **Septentrio Mosaic-X5** multi-constellation GNSS receiver and supports both real-time **RTK** (corrections in flight) and **PPK** (post-processed after landing). This guide covers the real-time **NTRIP RTK** workflow. {% endhint %} ## Requirements * **Aircraft:** Skydio X10 or X10D with the **RTK/PPK attachment** (`DR4ATTRTK`) installed in an attachment bay * **Controller:** Skydio controller with an active internet connection (phone hotspot or tether — the controller, not the aircraft, carries the NTRIP stream) * **Firmware:** Aircraft, attachment, and controller updated to 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 %} ### Install the RTK/PPK attachment Mount the **RTK/PPK attachment** in one of the X10's attachment bays and power on the aircraft and controller. Confirm the controller has internet (hotspot or tether). {% endstep %} {% step %} ### Open RTK setup On the controller, go to **Global Settings → Attachments → RTK/PPK → Set Up RTK**. {% endstep %} {% step %} ### Open network settings Under **Connect to Base Station**, tap **Open Network Settings**. Set **Kinematics Type** to **RTK** (not PPK). {% endstep %} {% step %} ### Enter NTRIP connection settings Select your region and enter the corresponding server details: {% tabs %} {% tab title="North America" %} * **NTRIP Host:** `rtk.rtkdata.com` * **IP Fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mount Point (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Europe" %} * **NTRIP Host:** `eu.rtkdata.com` * **IP Fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mount Point (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Australia" %} * **NTRIP Host:** `aus.rtkdata.com` * **IP Fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mount Point (ALL CAPS):** `AUTO` (recommended) — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} The controller loads the available mount points from the caster's source table — select **`AUTO`** from the list. {% hint style="danger" %} **Keep "Send GGA" enabled.** The RTKdata caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections from it. Without GGA, you connect but receive no corrections and stay on Float. RTKdata is a single-baseline, location-keyed network — it is **not** a VRS service. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% step %} ### Connect and verify Fix * Tap **Connect Now** (Connect to Base Station). * Place the drone **outdoors** with a clear sky view so the Mosaic-X5 acquires satellites before it can report position to the caster. * Watch the RTK status indicator (top-right telemetry): | Status | Meaning | | ---------- | -------------------------------------------------------- | | **SINGLE** | Basic GNSS fix. No corrections applied yet. | | **FLOAT** | Corrections received and processing. Accuracy improving. | | **FIX** | Centimeter-level accuracy active. | Skydio requires an RTK **FIX** before proceeding with the flight. Convergence typically takes 30–90 seconds in open sky. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights (mean sea level). If your workflow requires orthometric heights, apply a geoid model in your post-processing software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ------------------------------- | ----------------------------------------- | -------------------------------------------------------------------------------------------------- | | No corrections / stuck on Float | GGA not being sent (no satellite fix yet) | Move outdoors to open sky so the receiver acquires satellites and reports position | | No corrections | No internet on the controller | Verify the controller's hotspot/tether connectivity | | Authentication fails | Wrong credentials | Re-enter username/password from the RTKdata dashboard (case-sensitive, username starts with `rtk`) | | Mount point not listed | Source table not loaded | Re-open Network Settings so the controller refreshes the source table, then select `AUTO` | | RTK option missing | Attachment not installed/detected | Confirm the RTK/PPK attachment is seated in a bay and firmware is current | ## Tips * **The RTK/PPK attachment is required.** Without `DR4ATTRTK`, the X10 cannot do RTK or PPK. * **Internet runs through the controller**, not the aircraft — use a stable hotspot or tether. * **PPK is also available** via the same Mosaic-X5 attachment if you prefer post-processing over real-time corrections. * **Update firmware first** (aircraft, attachment, controller) before troubleshooting connectivity. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Utilities](https://rtkdata.com/utilities/) * [Transportation](https://rtkdata.com/transportation/) # XAG P100 / P150 RTK Setup: XAG One App NTRIP Connect XAG P100 and P150 ag drones to RTKdata NTRIP corrections via CORS in the XAG One app. Own SIM, RTCM 3.2 MSM4, AUTO mountpoint, and RTK Fix for centimeter accuracy. Connect XAG agricultural drones — **P100 / P100 Pro** and **P150 / P150 Max** — to RTKdata.com as a third-party **CORS (NTRIP)** correction source through the **XAG One** app. {% hint style="danger" %} **Read this first — two hard prerequisites.** XAG RTK normally runs on XAG's own Cloud RTK network over a factory **XAG IoT SIM**, and that SIM **cannot reach third-party casters like RTKdata**. 1. **You must use your own data SIM.** Replace the factory XAG IoT SIM with a personal 4G data SIM so the drone can reach `rtk.rtkdata.com`. The factory SIM is whitelisted to XAG's cloud only. 2. **RTCM3 MSM4 is required — and RTKdata provides it.** XAG's CORS client needs the RTCM3 MSM4 message format; the RTKdata caster streams **RTCM 3.2 with MSM4**, so this requirement is met. If you don't need a third-party caster, XAG's own **XRTK6 Pro / XRTK7** mobile base stations are the simplest RTK path. {% endhint %} {% hint style="warning" %} XAG has **more setup steps** than other platforms — you need a personal data SIM and must select the **CORS** source (not Cloud RTK). RTKdata exposes a single **`AUTO`** mountpoint, so if the XAG One access-point list doesn't show it immediately, use the search box (see Troubleshooting). Run one test connection before a large job. {% endhint %} ## Requirements * **Aircraft:** XAG P100 / P100 Pro or P150 / P150 Max with an RTK module * **Your own 4G data SIM** installed in the drone (the factory XAG IoT SIM will not reach third-party casters) * **Remote/controller:** ACS2 / ARC3 Pro (or equivalent) running the **XAG One** app * **RTKdata account:** Active subscription with NTRIP credentials, serving **RTCM3 MSM4** {% 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 %} ### Install your own data SIM Replace the factory XAG IoT SIM with your personal 4G data SIM so the drone can reach the RTKdata caster. Without this, third-party CORS will not connect. {% endstep %} {% step %} ### Choose CORS (not Cloud RTK) In the **XAG One** app, open the positioning settings and select **CORS** as the source — **not** Cloud RTK. "Cloud RTK" connects to XAG's own network; "CORS" connects to a third-party NTRIP account. {% endstep %} {% step %} ### Enter NTRIP connection settings Select your region and enter the corresponding server details: {% tabs %} {% tab title="North America" %} * **Server / Host:** `rtk.rtkdata.com` * **IP Fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Access point / Mountpoint (ALL CAPS):** `AUTO` — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Europe" %} * **Server / Host:** `eu.rtkdata.com` * **IP Fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Access point / Mountpoint (ALL CAPS):** `AUTO` — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Australia" %} * **Server / Host:** `aus.rtkdata.com` * **IP Fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Access point / Mountpoint (ALL CAPS):** `AUTO` — or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} When the app loads the access-point list, select **`AUTO`** (use the search box if available). {% hint style="danger" %} **GGA must be sent.** The RTKdata caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections. RTKdata is single-baseline and location-keyed — it is **not** a VRS service, and it returns no corrections without GGA. The drone must have a satellite fix (be outdoors). See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% step %} ### Enable RTK and verify Fix Enable RTK mode on the remote (e.g., on the ACS2 long-press the smart key). The RTK indicator should turn green and the status should move past "Locating RTK / Float" to a fixed solution. Operate **outdoors** with a clear sky view. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTKdata delivers **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights (mean sea level). {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Cannot log in to the CORS account | Factory XAG IoT SIM in use | Replace it with your own data SIM | | Login rejected | Caster not serving RTCM3 **MSM4** | Confirm your RTKdata stream is MSM4-compatible | | Fails at the "access point" step | App can't load/select the mountpoint | Confirm `AUTO` appears in the access-point list; this is a known edge with non-mainstream casters — contact RTKdata support | | Connects but stays on Float | GGA not sent (no satellite fix, or client not sending position) | Operate outdoors; if it still won't fix, GGA may not be reaching the caster — contact support | | No internet | SIM/data plan issue | Verify your data SIM has an active plan and signal | ## Tips * **Own SIM is mandatory** for third-party CORS — the factory XAG IoT SIM only reaches XAG's cloud. * **`AUTO` is the only mountpoint** you need — enter it in ALL CAPS. * **P150 / P150 Max** (4G + SIM, XRTK6 Pro/XRTK7) are the strongest candidates for third-party CORS. * **If third-party CORS won't hold a fix**, XAG's own **XRTK6 Pro / XRTK7** mobile base station is the reliable fallback. {% hint style="warning" %} **Need help getting XAG connected?** This setup has more moving parts than other platforms. [Contact RTKdata Support](https://docs.rtkdata.com/support/support) and we'll help you verify it on your aircraft. {% endhint %} ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Agriculture](https://rtkdata.com/agriculture/) # eBee X / Geo / TAC RTK Setup: eMotion NTRIP Connect the senseFly and AgEagle eBee X, eBee Geo, and eBee TAC to RTKdata NTRIP corrections in eMotion. Enter host, port, and AUTO mountpoint for centimeter RTK mapping. Connect the **AgEagle / senseFly eBee X** fixed-wing mapping drone — and the **eBee Geo** and **eBee TAC** variants — to RTKdata.com's NTRIP correction service for real-time centimeter-level positioning. All three share the **eMotion** flight-planning software, whose built-in NTRIP client works with any standard caster. {% hint style="info" %} * **eBee X** — RTK **and** PPK. * **eBee Geo** — RTK only (no PPK). * **eBee TAC** — tactical variant; RTK + PPK. Same eMotion NTRIP setup as the eBee X. {% endhint %} ## Requirements * **Aircraft:** eBee X, eBee Geo, or eBee TAC with RTK * **Software:** **eMotion** (current version) on the ground station laptop/tablet * **Internet:** Connection on the ground station (cellular/Wi-Fi) so eMotion can reach the caster * **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 %} ### Open the RTK / NTRIP settings in eMotion In **eMotion**, open the RTK settings and choose **NTRIP** as the correction source. {% endstep %} {% step %} ### Enter NTRIP connection settings Select your region and enter the corresponding server details: {% tabs %} {% tab title="North America" %} * **Host:** `rtk.rtkdata.com` * **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` {% endtab %} {% tab title="Europe" %} * **Host:** `eu.rtkdata.com` * **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` {% endtab %} {% tab title="Australia" %} * **Host:** `aus.rtkdata.com` * **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` {% endtab %} {% endtabs %} {% hint style="danger" %} **Keep GGA / "send position" enabled.** The RTKdata caster uses your GGA position to select the **nearest reference station** and stream single-baseline RTCM3 corrections. Without GGA, you connect but receive no corrections. RTKdata is single-baseline and location-keyed — it is **not** a VRS service. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). {% endhint %} {% endstep %} {% step %} ### Connect and verify Fix Connect to the caster and confirm the RTK status reaches **Fixed** before launch. The drone must have a clear sky view to acquire satellites and report position. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights (mean sea level). Apply a geoid model in your processing software if you need orthometric heights. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------- | -------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | Connects but stays on Float | GGA / "send position" disabled or no satellite fix | Enable position sending and operate outdoors with clear sky | | Authentication fails | Wrong credentials | Re-enter username/password from the RTKdata dashboard (case-sensitive, username starts with `rtk`) | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS | | No connection | No internet on the ground station | Verify the ground station's cellular/Wi-Fi connection | ## Tips * **One workflow for all three** eBee variants — they share eMotion's NTRIP client. * **eBee Geo is RTK-only** (no PPK), so a reliable NTRIP connection matters even more. * **Enter `AUTO` in ALL CAPS** as the mountpoint. ## Related Industry Solutions * [Drones](https://rtkdata.com/drones/) * [Agriculture](https://rtkdata.com/agriculture/) * [Surveying](https://rtkdata.com/surveying/) * [Environmental Monitoring](https://rtkdata.com/environmental-monitoring/) # Agriculture RTK Setup: NTRIP Auto-Steer Guides RTKdata NTRIP corrections for precision agriculture auto-steer. Compatibility for FieldBee, FJD, Raven, Trimble, Topcon and more, plus field setup tips. RTKdata works with any agricultural guidance system that supports standard NTRIP connections. This page covers compatibility, setup tips, and common issues for precision agriculture. *** ## The Compatibility Rule > **If your guidance display or receiver has an NTRIP menu where you can enter a server address, port, mountpoint, username, and password — it works with RTKdata.** RTKdata delivers standard RTCM 3.x corrections via NTRIP. This is an open industry standard supported by virtually all modern precision agriculture equipment. *** ## Known-Compatible Agriculture Systems ### FieldBee (by eFarmer) * **Compatibility:** Full * **Models:** FieldBee RTK GNSS receiver, FieldBee auto-steer system * **Setup:** Enter RTKdata credentials directly in the FieldBee app under NTRIP settings * **Notes:** Popular aftermarket auto-steer solution. Works on John Deere, Case IH, New Holland, and most other tractors. ### FJ Dynamics (FJD) * **Compatibility:** Full * **Models:** AT-1, AT-2, AT-2 Plus auto-steer systems * **Setup:** NTRIP settings in the FJD controller app * **Notes:** Budget-friendly auto-steer. Supports RTKdata out of the box. ### Raven * **Compatibility:** Full * **Models:** Viper 4, Viper 4+, RS1, Hawkeye * **Setup:** Go to correction source settings, select NTRIP, enter RTKdata server details * **Notes:** Widely used in North American agriculture. ### Trimble Agriculture (NAV 900, GFX-750, GFX-1260) * **Compatibility:** Full — but requires correct setup * **Setup:** Select **"Internet RTK"** or **"Single Base RTCM"** as correction source — **NOT "VRS" or "Network RTK"** * **Warning:** Trimble ag displays default to VRS mode. RTKdata is NOT a VRS network. See the [Trimble Receivers](/integration-hub/gnss-rovers-and-receivers/trimble-receivers) page for detailed instructions. ### Topcon Agriculture * **Compatibility:** Full * **Models:** X35, X25, Horizon displays * **Setup:** Standard NTRIP input in correction settings ### Hemisphere / Outback * **Compatibility:** Full * **Models:** A320, A321, S-Drive, eDriveX * **Setup:** Configure NTRIP in the correction source menu ### AgLeader * **Compatibility:** Full * **Models:** InCommand 800, InCommand 1200 * **Setup:** Configure in RTK correction source settings ### Müller Elektronik * **Compatibility:** Full * **Models:** TRACK-Leader, FIELD-Nav * **Setup:** Standard NTRIP configuration ### CLAAS GPS Pilot * **Compatibility:** Check with dealer * **Notes:** Some CLAAS systems with built-in GPS Pilot may require CLAAS-specific correction services. Check with your CLAAS dealer whether the system accepts standard NTRIP input. ### John Deere StarFire * **Compatibility:** Limited — StarFire receivers cannot connect to third-party NTRIP directly * **Models:** SF1, SF3, SF6 receivers use a proprietary correction format * **Workaround:** Use a third-party GNSS receiver with NTRIP capability (e.g., FJ Dynamics, FieldBee, or a standalone u-blox receiver) and connect it to the tractor's guidance system via serial or CAN bus * **Note:** Aftermarket systems like FieldBee and FJD offer complete replacement guidance with full RTKdata support ### Agricultural Drones * **DJI Agras T50/T40/T25** — Full compatibility. See [DJI Agras setup guide](/integration-hub/drones-and-uavs/dji-agras-t50-t40-t25) * **XAG P100 / P150** — Full compatibility via CORS in the XAG One app. See [XAG setup guide](/integration-hub/drones-and-uavs/xag-p100-p150) *** ## Setup Steps (General) These steps apply to most ag guidance systems: 1. **Find the NTRIP / RTK settings** in your display's correction source menu 2. Enter the RTKdata server details: | Setting | Value | | ----------------- | ---------------------------------------------------------------------------------------- | | **Host / Server** | `rtk.rtkdata.com` (Global) or `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia) | | **Port** | `2101` | | **Mountpoint** | `AUTO` (ALL CAPS) | | **Username** | Your NTRIP username (starts with `rtk`) | | **Password** | Your NTRIP password | 3. **Save and connect** — wait for RTK FIX (usually 30–90 seconds) 4. **Verify accuracy** — check the RTK status indicator on your display *** ## Internet in the Field Agricultural equipment often operates in remote areas. Internet options: | Method | Reliability | Notes | | ----------------------- | ----------- | ------------------------------------------------------------------- | | **Phone hotspot (4G)** | Good | Most common. Mount phone on cab roof for better signal. | | **Dedicated 4G router** | Very good | With external antenna — best for consistent coverage | | **Starlink Mini** | Excellent | Works in remote areas with no cell coverage. Power via 12V adapter. | | **Wi-Fi extender** | Variable | Only if near a building with Wi-Fi | **Data usage:** RTK corrections use approximately **5–10 kbit/s** — negligible even on metered connections. A full day of farming uses less than 50 MB. *** ## Common Issues ### "My auto-steer drifts after working for a while" * Check if RTK dropped from FIX to FLOAT (usually an internet issue) * Verify your phone/hotspot hasn't gone to sleep * Some guidance systems revert to WAAS/SBAS silently when RTK drops — check the correction source indicator ### "Accuracy is worse than expected" * Check distance to nearest base station on the [Coverage Map](https://rtkdata.com/coverage/) * Ensure you're using mountpoint `AUTO` (not `AUTO_WGS84` unless you specifically need WGS84) * Verify you're connected to the nearest regional server ### "RTK disconnects when I cross field boundaries" * This may be a hotspot signal issue — as you drive away from the phone/router, signal weakens * Mount the hotspot device on the tractor, not in a stationary location * Consider a 4G router with external antenna mounted on the cab *** ## Subscription Tips for Farms * **One subscription = one machine** connected at a time * If you run **multiple machines simultaneously**, you need one subscription per machine * **Annual plans** ($33.33/month) offer significant savings over monthly billing for seasonal use * The **5-year plan** is the best value for long-term farm operations See [Pricing FAQ](/get-started/pricing-faq) for full plan details. # AgOpenGPS NTRIP Setup: AgIO RTK Auto-Steer Connect open-source AgOpenGPS and a u-blox ZED-F9P to RTKdata NTRIP via AgIO for 2.5 cm RTK auto-steer. Port 2101, mountpoint AUTO, GGA interval 5. AgOpenGPS is a free, open-source precision agriculture auto-steer system that delivers centimeter-level guidance for a fraction of the cost of proprietary solutions like John Deere StarFire or Trimble RTX. It runs on a Windows tablet mounted in the tractor cab and uses a **u-blox ZED-F9P** GNSS receiver for RTK positioning. The system consists of two programs: **AgOpenGPS** (the main guidance interface) and **AgIO** (the background I/O manager that handles NTRIP connections, serial ports, and UDP communication with the steering hardware). With RTKdata.com providing corrections, AgOpenGPS achieves repeatable pass-to-pass accuracy of 2.5 cm — comparable to systems costing thousands per year in subscriptions. ## Requirements * **Windows tablet or laptop** running AgOpenGPS (v5.x or later) * **u-blox ZED-F9P** receiver board (e.g., Ardusimple simpleRTK2B, SparkFun GPS-RTK2) * **USB cable** connecting the F9P to the tablet * **Internet connection** on the tablet (phone hotspot via Wi-Fi or USB tethering) * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **F9P configured for RTCM3 input** on the correct UART/USB port {% 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 %} ## Method A: Built-in NTRIP client via AgIO (recommended) AgOpenGPS v5+ uses the companion program **AgIO** to manage all NTRIP connections. AgIO runs in the background and handles receiving corrections from the NTRIP caster, then delivers them to the F9P receiver via serial port or UDP. No extra software is needed. {% stepper %} {% step %} ### Connect the F9P receiver 1. Connect the u-blox F9P to your Windows tablet via USB. 2. Open **Device Manager** and note the COM port number assigned to the F9P (e.g., COM3). 3. Ensure the F9P firmware is updated to v1.32 or later using **u-blox u-center**. {% hint style="warning" %} The F9P must be pre-configured to accept RTCM3 corrections on its USB input. Use u-center to verify that **RTCM3 input** is enabled on the USB port. Without this, corrections from AgIO will not reach the receiver. {% endhint %} {% endstep %} {% step %} ### Launch AgIO and configure the GPS port 1. Launch **AgIO** — it typically starts automatically with AgOpenGPS but can also be started independently. 2. In AgIO, click the **GPS / Serial** button to open serial port settings. 3. Select the COM port matching your F9P (e.g., COM3). 4. Set baud rate to **460800** (or match your F9P configuration). 5. Click **Connect**. The AgIO status bar should show satellite count and position data flowing. {% hint style="info" %} AgIO communicates with AgOpenGPS via UDP on the local machine. Once AgIO is receiving GPS data, AgOpenGPS automatically picks it up. You do not need to configure a COM port in AgOpenGPS itself when using AgIO. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings in AgIO 1. In **AgIO**, click the **RTK / NTRIP** button to open the NTRIP client dialog. 2. Ensure the **NTRIP** indicator is **green (ON)**. If it is red, click it to enable NTRIP. 3. Fill in the fields. Select the tab for your region: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} 3. Set the **GGA send interval** (in seconds). A value of **5** is recommended. Setting this to **0** disables GGA sending entirely — do not set to 0. 4. Configure the correction output: * **Send to Serial:** Enable this if your F9P is connected via USB serial and receives corrections on that port. This is the most common setup. * **Send to UDP:** Enable this if your hardware (e.g., All-in-One Teensy board) receives corrections over the network. The default UDP port is **2233**. * Turn off whichever output method you are **not** using. 5. Optionally, tap **Get Source Table** to browse available mountpoints. For RTKdata.com, simply type `AUTO` in ALL CAPS. 6. Click **Connect** or **Enable**. {% hint style="warning" %} **Both Serial and UDP output are enabled by default.** Turn off the one you do not use. If both are on and you only have a serial connection, the extra UDP traffic is harmless but unnecessary. If you only use UDP (Ethernet boards), make sure Serial is off to avoid port conflicts. {% endhint %} {% endstep %} {% step %} ### Verify RTK Fix 1. Return to the main **AgOpenGPS** screen (AgIO continues running in the background). 2. Watch the solution status indicator: **SINGLE** → **FLOAT** → **FIX**. 3. The correction age should display below 3 seconds. 4. In AgIO, you can also verify the NTRIP status: the NTRIP indicator should stay green, and you should see data bytes incrementing for both incoming RTCM and outgoing GGA. 5. Once at FIX, you have centimeter-level accuracy and can begin creating guidance lines. {% hint style="info" %} FIX typically takes 30–90 seconds with good sky visibility. If you stay on FLOAT for more than 5 minutes, check the troubleshooting section below. {% endhint %} {% endstep %} {% endstepper %} ## Method B: External NTRIP client If AgIO's built-in NTRIP client does not work for your setup (e.g., network restrictions, special proxy requirements), use an external NTRIP client such as **Lefebure NTRIP Client** (Windows) or **SNIP** to receive corrections and forward them to the F9P via a serial port. 1. Install Lefebure NTRIP Client on your tablet. 2. Enter the same RTKdata NTRIP settings from the tabs above. 3. Set the output to the F9P's COM port at the matching baud rate. 4. Lefebure forwards RTCM3 data to the F9P, which computes the RTK solution. 5. AgOpenGPS reads the corrected position from the F9P via AgIO — disable the NTRIP client in AgIO to avoid conflicts (set NTRIP indicator to red/OFF). ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**. For agriculture applications, this is typically sufficient since auto-steer guidance uses horizontal positioning. If you need terrain-relative heights for drainage or leveling, apply a local geoid model. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------- | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | COM port not found | F9P not recognized by Windows | Reinstall the u-blox USB driver. Try a different USB cable or port. | | AgIO resets when toggling Serial NTRIP | Expected behavior | AgIO restarts its serial subsystem when you enable/disable Serial NTRIP. Wait for it to reconnect. | | No corrections received | F9P UART/USB misconfigured | Open u-center and verify RTCM3 input is enabled on the USB port. Reflash the F9P configuration file from the AgOpenGPS community. | | Stuck on FLOAT | Base station too far or poor sky | Check RTKdata coverage. Move to open field away from buildings and tree lines. | | NTRIP connects but correction age climbs | Tablet internet dropping | Verify Wi-Fi hotspot connection. Use USB tethering for a more stable link in the cab. | | GGA send interval set to 0 | GGA disabled — caster gets no position | Set the GGA send interval to **5** seconds in AgIO's NTRIP settings. | | Both Serial and UDP active causing issues | Port conflicts or doubled corrections | Turn off the output method you are **not** using (Serial or UDP) in AgIO's NTRIP settings. | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS. Do not attempt to browse the source table. | ## Tips and tricks * **RTKdata + AgOpenGPS delivers RTK guidance for under $200/year** — compared to $1,500+/year for John Deere StarFire SF3 or Trimble CenterPoint RTX. * **Use USB tethering** from your phone to the tablet for the most reliable internet connection in the tractor cab. * **Save an F9P config file** with correct settings so you can reflash quickly if the receiver resets. * **The AgOpenGPS community** on Discourse and GitHub is active — search for "RTKdata" or "NTRIP" for setup threads from other users. * **Update F9P firmware** regularly via u-center. Each firmware release improves multi-constellation tracking and Fix reliability. ## Related Industry Solutions * [Agriculture](https://rtkdata.com/agriculture/) * [Robotics](https://rtkdata.com/robotics/) # John Deere StarFire RTK Setup: NTRIP via Modem Use a John Deere StarFire SF6000/SF7000 with an external NTRIP modem to reach RTKdata for centimeter RTK. Needs mRTK license, port 2101, mountpoint AUTO. Connect a **John Deere StarFire** receiver to RTKdata.com for centimeter-level RTK positioning. StarFire receivers do not have a built-in NTRIP client, so an **external NTRIP modem** (such as CloudBase RTK or similar) is required to deliver RTCM3 corrections to the receiver. {% hint style="danger" %} **StarFire SF1 and SF2 accuracy levels do NOT support RTK.** This guide applies only to StarFire SF6000, SF7000, and SF7500 receivers with the appropriate RTK license activated. {% endhint %} ## Key capabilities | Feature | Details | | -------------------------------- | ------------------------------------------------------------------------ | | **Compatible receivers** | StarFire SF6000, SF7000, SF7500 | | **RTK license** | Mobile RTK (mRTK) activation required | | **SF6000 mRTK license** | Annual subscription | | **SF7000 / SF7500 mRTK license** | Included with RTK Permanent License | | **NTRIP client** | External modem required (e.g., CloudBase RTK) — no built-in NTRIP client | | **Compatible displays** | 2630, 4240, 4640, Gen 4 CommandCenter | | **Correction format** | RTCM 3.x via external modem | | **Not supported** | SF1, SF2 accuracy levels | ## Requirements * **StarFire receiver:** SF6000, SF7000, or SF7500 with **Mobile RTK (mRTK) license** activated * **External NTRIP modem:** CloudBase RTK, Raven CR7, or similar NTRIP-capable modem with serial/CAN output * **John Deere display:** 2630, 4240, 4640, or Gen 4 CommandCenter * **Cellular data connection** on the NTRIP modem (built-in SIM or hotspot) * **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 %} ### Verify mRTK license activation 1. On your John Deere display, navigate to the **StarFire receiver status** page. 2. Confirm that **Mobile RTK (mRTK)** is listed as an active license/feature. 3. If mRTK is not active, contact your John Deere dealer to activate it on your receiver. {% hint style="warning" %} Without the mRTK license, the StarFire receiver will reject third-party RTCM3 corrections. This license enables the receiver to accept corrections from external sources like RTKdata.com. {% endhint %} {% endstep %} {% step %} ### Connect the external NTRIP modem 1. Connect the NTRIP modem (e.g., CloudBase RTK) to the StarFire receiver's correction input port (typically a serial or CAN connection). 2. Power on the modem and ensure it has cellular connectivity (check the modem's signal indicator). 3. Refer to your modem's documentation for the specific cable and port connections. {% hint style="info" %} The NTRIP configuration is done on the **modem's interface** — not on the John Deere display directly. The modem receives RTCM3 corrections from RTKdata.com and forwards them to the StarFire receiver. {% endhint %} {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings on the modem Open the modem's configuration interface (web browser, app, or on-screen menu, depending on the modem model). Enter the following NTRIP settings: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in ALL CAPS. Do not browse the source table — simply type the mountpoint name directly. {% endhint %} {% endstep %} {% step %} ### Connect the modem and verify corrections 1. Save the settings on the modem and initiate the NTRIP connection. 2. The modem should show a connected/active status and begin receiving RTCM3 correction data. 3. Verify on the modem that data bytes are flowing (incoming RTCM corrections). {% endstep %} {% step %} ### Verify RTK status on the John Deere display 1. On the John Deere display, navigate to the **StarFire receiver status** or **GPS status** page. 2. Monitor the accuracy level indicator: | Status | Meaning | | ------------- | -------------------------------------------------------------------- | | **SF1 / SF2** | Standard accuracy. Corrections not being applied. | | **RTK Float** | Correction data is being received and processed. Accuracy improving. | | **RTK Fixed** | Centimeter-level accuracy achieved. Ready for precision operations. | 3. Convergence from Float to Fixed typically takes **30–90 seconds** with clear sky visibility. {% hint style="info" %} If the display continues to show SF1 or SF2 accuracy even after the modem is connected and receiving data, verify that the mRTK license is activated on the receiver. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**. For agriculture applications, this is typically sufficient since auto-steer guidance uses horizontal positioning. If you need terrain-relative heights for drainage or leveling, apply a local geoid model in your farm management software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------------- | ----------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Display shows SF1/SF2 despite modem connected | mRTK license not activated | Contact your John Deere dealer to verify and activate the Mobile RTK (mRTK) license on your StarFire receiver. | | Modem cannot connect to NTRIP | No cellular signal | Verify the modem's SIM card has an active data plan and adequate signal strength in the field. | | Modem connects but no corrections flow | Wrong host or port | Double-check the host address for your region and confirm port is `2101`. | | Authentication failed on modem | Wrong credentials | Use the username and password from your RTKdata dashboard, not your website login. Credentials are case-sensitive. | | Stuck on RTK Float | Poor sky visibility | Move to an open area away from tree lines, buildings, and power lines. | | Stuck on RTK Float | Modem-to-receiver cable issue | Verify the serial/CAN cable between the modem and StarFire receiver is securely connected and the correct port is selected. | | Corrections drop in the field | Weak cellular coverage | Use an external antenna on the modem for better reception in rural areas. | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS on the modem's configuration interface. | ## Tips * **The modem is the NTRIP client.** All NTRIP configuration happens on the external modem, not on the John Deere display. The display only shows the resulting accuracy level. * **CloudBase RTK** is one of the most commonly used modems with John Deere StarFire. It provides a straightforward web interface for NTRIP configuration. * **Cellular coverage in rural areas** is the most common challenge. Consider a modem with an external antenna port and a high-gain antenna for better reception. * **After powering on**, allow the StarFire receiver to acquire a satellite fix before the modem begins sending corrections. This typically takes 1–2 minutes. * **Keep firmware updated** on both the StarFire receiver and the NTRIP modem for best compatibility and performance. * **Multiple machines:** Each machine needs its own NTRIP modem and RTKdata connection. One RTKdata account can support multiple simultaneous connections depending on your subscription plan. ## Related Industry Solutions * [Agriculture](https://rtkdata.com/agriculture/) # CLAAS GPS Pilot RTK Setup: RTK NET Auto-Steer Connect CLAAS GPS Pilot with the SAT 900 receiver to RTKdata via RTK NET NTRIP for centimeter auto-steer. Not locked to CLAAS EASY, port 2101, AUTO. Connect the **CLAAS GPS Pilot** auto-steering system to RTKdata.com for centimeter-level RTK positioning. Newer CLAAS systems with the **SAT 900** receiver (Trimble-based) support standard NTRIP connections and are **not locked to CLAAS EASY** — they accept RTCM 3.1 corrections from any provider, including RTKdata.com. {% hint style="warning" %} This guide applies to newer CLAAS systems with the **SAT 900 receiver** (Trimble-based). Older pre-Trimble CLAAS systems may be locked to proprietary correction services. If you have an older system, check with your CLAAS dealer to confirm third-party NTRIP compatibility. {% endhint %} ## Key capabilities | Feature | Details | | ------------------------- | ------------------------------------------------------- | | **Compatible receiver** | CLAAS SAT 900 (Trimble-based) | | **Compatible displays** | CLAAS S7, S10, CEMIS 1200 | | **Correction mode** | RTK NET (standard NTRIP) | | **Correction format** | RTCM 3.1 from any provider | | **Connectivity** | Built-in communication module | | **RTK Bridging** | 15 cm backup accuracy for up to 20 minutes if RTK drops | | **Locked to CLAAS EASY?** | No — accepts third-party corrections | ## Requirements * **CLAAS GPS Pilot** system with **SAT 900** receiver * **CLAAS display:** S7, S10, or CEMIS 1200 * **RTK activation** enabled on the terminal (may require dealer activation) * **Internet connection** via the built-in communication module (SIM card with active data plan) * **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 %} ### Verify RTK activation 1. On your CLAAS display (S7, S10, or CEMIS 1200), navigate to the **GPS / GNSS settings**. 2. Confirm that **RTK** is listed as an available correction mode. 3. If RTK is not available, contact your CLAAS dealer to activate RTK on the terminal. {% hint style="warning" %} RTK activation may be required as a separate step on the terminal. Without activation, the RTK NET correction mode will not appear in the settings. {% endhint %} {% endstep %} {% step %} ### Verify communication module and SIM card 1. Ensure the built-in communication module has a **SIM card** with an active cellular data plan installed. 2. Check the signal strength indicator on the display to confirm cellular connectivity. 3. The SAT 900's built-in communication module handles the NTRIP connection — no external modem is needed. {% endstep %} {% step %} ### Select RTK NET correction mode 1. Navigate to **GPS Settings** > **Correction Source** (or similar path depending on display model). 2. Select **RTK NET** as the correction mode. 3. This enables the standard NTRIP client on the SAT 900 receiver. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings In the RTK NET configuration screen, enter the following settings: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in ALL CAPS. Do not browse the mountpoint list — enter the mountpoint name directly. {% endhint %} {% endstep %} {% step %} ### Connect and verify RTK status 1. Save the settings and initiate the connection. 2. Monitor the RTK status indicator on the display: | Status | Meaning | | ---------------- | ------------------------------------------------------------------- | | **GPS only** | Basic satellite fix. No corrections applied. | | **DGPS / Float** | Correction data arriving and being processed. | | **RTK Fixed** | Centimeter-level accuracy achieved. Ready for precision operations. | 3. Convergence to RTK Fixed typically takes **30–90 seconds** with clear sky visibility. {% hint style="info" %} If RTK drops during operation, the SAT 900's **RTK Bridging** feature maintains approximately 15 cm accuracy for up to 20 minutes using the receiver's internal algorithms. This prevents guidance interruptions during brief connectivity outages. {% endhint %} {% endstep %} {% endstepper %} ## RTK Bridging The SAT 900 receiver includes **RTK Bridging** — a built-in backup mode that activates automatically when the RTK correction stream is interrupted. RTK Bridging maintains approximately 15 cm accuracy for up to 20 minutes, allowing you to continue field operations without stopping. When the NTRIP connection restores, the system seamlessly returns to full RTK accuracy. ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**. For agriculture applications, this is typically sufficient since auto-steer guidance uses horizontal positioning. If you need terrain-relative heights for drainage or leveling, apply a local geoid model in your farm management software. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ---------------------------------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | RTK NET not available as correction mode | RTK not activated on terminal | Contact your CLAAS dealer to activate RTK on your display/terminal. | | No internet connection | SIM card missing or no data plan | Verify the communication module has an active SIM card with a cellular data plan. | | Connection fails | Wrong host or port | Double-check the host address for your region and confirm port is `2101`. | | Authentication error | Wrong credentials | Use the username and password from your RTKdata dashboard, not your website login. Credentials are case-sensitive. | | Stuck on Float | Poor sky visibility | Move to an open area of the field, away from tree lines and buildings. | | Stuck on Float | Weak cellular signal | Check signal strength on the display. Consider a location with better cellular coverage for initial setup. | | Older system does not accept RTKdata | Pre-Trimble hardware | Older CLAAS systems without the SAT 900 may be locked to proprietary corrections. Check with your CLAAS dealer. | ## Tips * **Not locked to CLAAS EASY.** The SAT 900 receiver accepts RTCM 3.1 corrections from any standard NTRIP caster, including RTKdata.com. * **RTK Bridging is your safety net.** If you briefly lose cellular signal in the field, the 20-minute bridging window prevents guidance disruptions. * **Cellular coverage** is the most common challenge in agricultural environments. Verify signal strength at your field locations before the season starts. * **One SIM card, one connection.** The built-in communication module handles the NTRIP connection directly — no external modem or phone hotspot is needed. * **Keep firmware updated.** CLAAS periodically releases updates for the SAT 900 and display terminals. Check with your dealer for the latest versions. * **S7 vs S10 vs CEMIS 1200:** The NTRIP setup process is the same across all compatible displays. Menu paths may vary slightly between models. ## Related Industry Solutions * [Agriculture](https://rtkdata.com/agriculture/) # Trimble GFX / CFX RTK Setup: Internet NTRIP Configure Trimble GFX-750, GFX-1260 or CFX-750 ag displays with RTKdata NTRIP for centimeter RTK. Pick Internet RTK, never VRS. Port 2101, mountpoint AUTO. Connect a **Trimble GFX-750**, **GFX-1260**, or **CFX-750** precision agriculture display to RTKdata.com for centimeter-level RTK positioning. {% hint style="danger" %} **Critical:** When configuring the GFX-750 or GFX-1260, you must select **"Internet RTK"** as the correction type — NOT "VRS" or "Network RTK". Selecting the wrong type will prevent the connection from working. {% endhint %} ## Key capabilities | Feature | Details | | ----------------------- | -------------------------------------------------------------------------- | | **Compatible displays** | GFX-750, GFX-1260, CFX-750 | | **GFX-750 / GFX-1260** | Built-in NTRIP client via Settings > GNSS Configuration > Corrections | | **CFX-750** | Requires external modem (Raven RV50 or DCM-300) — no built-in NTRIP client | | **NAV controller** | RTK activation required on NAV-500 or NAV-900 | | **Compatible guidance** | EZ-Pilot Pro, Autopilot | | **Correction type** | Internet RTK (not VRS, not Network RTK) | | **Correction format** | RTCM 3.x via NTRIP | ## Requirements * **Trimble GFX-750 or GFX-1260** display with built-in modem, **or** Trimble CFX-750 with an external NTRIP modem (Raven RV50 or DCM-300) * **NAV controller:** NAV-500 or NAV-900 with **RTK activation** * **Internet connection:** Built-in cellular modem (GFX series) or external modem (CFX-750) * **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 %} ## GFX-750 / GFX-1260 setup (built-in NTRIP) {% stepper %} {% step %} ### Verify RTK activation 1. On the GFX display, navigate to **Settings** > **GNSS Configuration**. 2. Confirm that **RTK** is listed as an available correction option. 3. If RTK is not available, the NAV controller (NAV-500 or NAV-900) requires RTK activation. Contact your Trimble dealer. {% endstep %} {% step %} ### Open correction settings 1. Navigate to **Settings** > **GNSS Configuration** > **Corrections**. 2. Select **Internet RTK** as the correction type. {% hint style="danger" %} You **must** select **"Internet RTK"**. Do NOT select "VRS" or "Network RTK" — these are different connection modes that will not work with RTKdata.com's standard NTRIP caster. {% endhint %} {% endstep %} {% step %} ### Select NTRIP as the connection method 1. Under Internet RTK, select **NTRIP** as the connection method. 2. This opens the NTRIP configuration fields. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in ALL CAPS. Do not browse the source table — enter the mountpoint name directly. {% endhint %} {% endstep %} {% step %} ### Connect and verify RTK status 1. Save the settings and initiate the NTRIP connection. 2. Monitor the GNSS status indicator on the GFX display: | Status | Meaning | | -------------------- | ------------------------------------------------------------------- | | **Autonomous / GPS** | Basic satellite fix. No corrections applied. | | **Float** | Correction data arriving and being processed. | | **RTK Fixed** | Centimeter-level accuracy achieved. Ready for precision operations. | 3. Convergence to RTK Fixed typically takes **30–90 seconds** with clear sky visibility. {% endstep %} {% endstepper %} ## CFX-750 setup (external modem required) The CFX-750 is an older display that does not have a built-in NTRIP client or cellular modem. An external modem is required to receive corrections from RTKdata.com. {% stepper %} {% step %} ### Connect an external NTRIP modem 1. Connect a Raven RV50, DCM-300, or similar NTRIP modem to the CFX-750's correction input port. 2. Power on the modem and verify cellular connectivity. {% endstep %} {% step %} ### Configure NTRIP on the external modem 1. Open the modem's configuration interface (web browser or on-screen menu). 2. Enter the same RTKdata.com NTRIP settings from the regional tabs above. 3. Set the modem's output to forward RTCM3 corrections to the CFX-750. {% endstep %} {% step %} ### Verify RTK on the CFX-750 1. On the CFX-750 display, check the GNSS status. 2. The display should progress from GPS to Float to RTK Fixed as corrections are received. 3. If the display does not show RTK, verify that RTK activation is enabled on the NAV controller. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**. For agriculture applications, this is typically sufficient since auto-steer guidance uses horizontal positioning. If you need terrain-relative heights for drainage or leveling, apply a local geoid model. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | RTK not available in correction settings | NAV controller not activated | Contact your Trimble dealer to activate RTK on the NAV-500 or NAV-900. | | Connection fails with "VRS" or "Network RTK" selected | Wrong correction type | Change the correction type to **Internet RTK**. This is the correct setting for RTKdata.com. | | No internet connection (GFX) | Built-in modem has no SIM or signal | Verify the GFX display's internal modem has an active SIM card and cellular signal. | | No internet connection (CFX-750) | External modem not connected | Verify the external modem is powered, has a SIM card, and shows cellular connectivity. | | Authentication error | Wrong credentials | Use the username and password from your RTKdata dashboard, not your website login. Credentials are case-sensitive. | | Stuck on Float | Poor sky visibility | Move to an open area away from buildings, tree lines, and power lines. | | Stuck on Float | NAV controller issue | Restart the NAV controller. If Float persists, verify RTK activation status. | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS. | ## Tips * **"Internet RTK" is the correct setting** — this is the most common configuration mistake on Trimble GFX displays. "VRS" and "Network RTK" are different protocols. * **GFX-750 vs GFX-1260:** The setup process is identical. The GFX-1260 has a larger screen and updated processor, but NTRIP configuration follows the same menu path. * **CFX-750 users** need an external modem. The RV50 cellular modem is the most common choice and has a straightforward web-based configuration interface. * **EZ-Pilot Pro and Autopilot** guidance systems work seamlessly with RTK corrections — no additional configuration is needed on the guidance hardware once RTK is active on the display. * **Keep firmware updated** on the GFX display and NAV controller for best RTK performance and compatibility. * **Save your configuration** after setup. If the display is reset or swapped, you can re-enter settings quickly by referencing your saved configuration. ## Related Industry Solutions * [Agriculture](https://rtkdata.com/agriculture/) # Machine Control RTK Setup: Dozers & Graders RTKdata NTRIP corrections for Topcon, Leica and Trimble machine control on excavators, dozers and graders. 10-20 mm accuracy, port 2101, mountpoint AUTO. Setup guides for using RTKdata.com RTK corrections with machine control systems on excavators, dozers, graders, and other heavy equipment. ## Supported Systems | System | Manufacturer | Machine Types | | ----------------------------------------------------------------------------- | --------------- | ----------------------------------------------- | | [**Topcon 3D-MC / MC-X1**](/integration-hub/machine-control/topcon-3d-mc) | Topcon | Excavators, dozers, graders | | [**Leica iCON iGD4**](/integration-hub/machine-control/leica-icon-igd4) | Leica (Hexagon) | Excavators, dozers, graders | | [**Trimble Earthworks**](/integration-hub/machine-control/trimble-earthworks) | Trimble | Dozers, excavators, graders, compactors, pavers | ## How It Works Machine control systems use RTK corrections to position the bucket, blade, or drum in real time — typically achieving **10–20 mm accuracy**. The GNSS receiver on the machine connects to RTKdata.com via NTRIP (using a cellular modem), receives RTCM3 corrections, and feeds the corrected position to the machine control display. ## Quick Setup All systems use the same RTKdata.com NTRIP settings: ``` Host: eu.rtkdata.com / rtk.rtkdata.com / aus.rtkdata.com Port: 2101 Mountpoint: AUTO Username: (from RTKdata dashboard) Password: (from RTKdata dashboard) GGA: ON (required) ``` Select your system above for step-by-step instructions. # Topcon 3D-MC / MC-X1 NTRIP Setup: Machine RTK Set up Topcon 3D-MC and MC-X1 machine control with RTKdata NTRIP for centimeter RTK. Not locked to TopNET Live. Port 2101, mountpoint AUTO. Connect a **Topcon 3D-MC** or **MC-X1** machine control system to RTKdata.com for centimeter-level RTK positioning on excavators, dozers, and graders. Topcon machine control systems are **not locked to TopNET Live** — they accept RTCM corrections from any standard NTRIP caster. ## Key capabilities | Feature | Details | | -------------------------- | -------------------------------------------------- | | **Compatible systems** | Topcon 3D-MC, MC-X1 | | **Compatible displays** | GX-60, GX-77 | | **Compatible receivers** | MC-R3, MC-I3 | | **MC-I3 connectivity** | Internal 3G/4G modem with SIM slot | | **MC-R3 connectivity** | External modem or phone hotspot required | | **Locked to TopNET Live?** | No — accepts any NTRIP provider | | **Correction format** | RTCM 3.x via NTRIP | | **Configuration path** | Topcon Logo > Tools > Configure Radios > NTRIP tab | ## Requirements * **Topcon 3D-MC or MC-X1** machine control system * **Display:** GX-60 or GX-77 * **Receiver:** MC-R3 or MC-I3 * **Internet connection:** MC-I3 internal modem with active SIM card, or external modem / phone hotspot for MC-R3 * **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 %} ### Power on and verify internet connectivity 1. Power on the machine control system (display and receiver). 2. If using an **MC-I3**: Insert a SIM card with an active data plan into the internal modem slot. Verify cellular signal on the display. 3. If using an **MC-R3**: Connect an external cellular modem or pair with a phone hotspot for internet access. {% endstep %} {% step %} ### Open the NTRIP configuration 1. On the GX-60 or GX-77 display, tap the **Topcon Logo** in the corner of the screen. 2. Navigate to **Tools** > **Configure Radios**. 3. Select the **NTRIP** tab. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in ALL CAPS. Do not browse the source table — enter the mountpoint name directly. {% endhint %} {% endstep %} {% step %} ### Connect and verify RTK status 1. Tap **Connect** or **Apply** to save the settings and initiate the NTRIP connection. 2. Monitor the GNSS/RTK status indicator on the display: | Status | Meaning | | -------------------- | ------------------------------------------------------------------------- | | **Autonomous / GPS** | Basic satellite fix. No corrections applied. | | **DGPS / Float** | Correction data arriving and being processed. | | **RTK Fixed** | Centimeter-level accuracy achieved. Ready for machine control operations. | 3. Convergence to RTK Fixed typically takes **30–90 seconds** with clear sky visibility. {% hint style="info" %} For machine control operations, always wait for **RTK Fixed** before beginning grading, excavation, or dozing. Working in Float mode may result in elevation errors that affect cut/fill accuracy. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights. For machine control, you typically work with a local site calibration or localization that accounts for the geoid. Configure the appropriate vertical datum in your Topcon project settings. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | NTRIP tab not visible | Older firmware | Update the display and receiver firmware. The NTRIP tab may not appear on very old firmware versions. | | No internet (MC-I3) | SIM card missing or no data plan | Verify the SIM card is inserted and has an active cellular data plan. | | No internet (MC-R3) | No external modem connected | Connect an external modem or pair with a phone hotspot. The MC-R3 does not have an internal modem. | | Connection fails | Wrong host or port | Double-check the host address for your region and confirm port is `2101`. | | Authentication error | Wrong credentials | Use the username and password from your RTKdata dashboard, not your website login. Credentials are case-sensitive. | | Stuck on Float | Poor sky visibility | Move the machine to an open area. GNSS antennas on heavy equipment can be partially obstructed by booms, cabs, and nearby structures. | | Stuck on Float | Receiver issue | Power-cycle the receiver. If Float persists, verify the receiver has an RTK-capable license/configuration. | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS. | ## Tips * **Not locked to TopNET Live.** You can use any standard NTRIP caster, including RTKdata.com. No Topcon-specific subscription is required for the NTRIP connection. * **MC-I3 is the simplest setup** — its internal modem with SIM slot means no external devices are needed for internet connectivity. * **MC-R3 users** should consider a dedicated cellular modem mounted on the machine for the most reliable connection, rather than relying on a phone hotspot. * **Site calibration is critical.** Before starting machine control work, perform a site localization/calibration to align RTK coordinates with your design surface. * **Vibration and multipath.** Heavy equipment environments can cause multipath interference. Ensure the GNSS antenna is mounted as high and clear as possible on the machine. * **Keep firmware updated** on both the display and receiver for the latest NTRIP client improvements and constellation support. ## Related Industry Solutions * [Construction](https://rtkdata.com/construction/) # Leica iCON iGD4 RTK Setup: Machine Control Connect Leica iCON iGD4 machine control to RTKdata NTRIP for centimeter RTK on excavators, dozers and graders. Configure on the receiver, port 2101, AUTO. Connect a **Leica iCON iGD4** machine control system to RTKdata.com for centimeter-level RTK positioning on excavators, dozers, and graders. The NTRIP connection is configured on the **receiver** (iCON gps 60/80 or iCG70/160), not on the iGD4 display itself. {% hint style="danger" %} NTRIP settings are configured on the **GNSS receiver**, not on the iGD4 display. The receiver (iCON gps 60/80 or iCG70/160) has the built-in 3G/4G modem and NTRIP client. The display only shows the resulting position and RTK status. {% endhint %} ## Key capabilities | Feature | Details | | ------------------------- | --------------------------------------- | | **Compatible displays** | Leica iCON iGD4, iGD4SP | | **Compatible receivers** | iCON gps 60, iCON gps 80, iCG70, iCG160 | | **NTRIP configured on** | Receiver (not display) | | **Receiver connectivity** | Built-in 3G/4G modem with SIM slot | | **RTK license** | Required on the receiver | | **Machine types** | Excavators, dozers, graders | | **Correction format** | RTCM 3.x via NTRIP | ## Requirements * **Leica iCON iGD4 or iGD4SP** display * **GNSS receiver:** iCON gps 60, iCON gps 80, iCG70, or iCG160 with **RTK license** activated * **SIM card** with active data plan installed in the receiver's built-in modem * **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 %} ### Verify RTK license on the receiver 1. Check that the GNSS receiver (iCON gps 60/80 or iCG70/160) has an active **RTK license**. 2. The RTK license is tied to the receiver, not the display. 3. If RTK is not licensed, contact your Leica Geosystems dealer to activate it. {% hint style="warning" %} Without an RTK license on the receiver, NTRIP connections will not be established even if all settings are entered correctly. {% endhint %} {% endstep %} {% step %} ### Insert SIM card into the receiver 1. Locate the SIM card slot on the GNSS receiver. 2. Insert a SIM card with an active cellular data plan. 3. Power on the receiver and verify cellular signal strength via the receiver's status indicators or the iGD4 display. {% endstep %} {% step %} ### Access the receiver's NTRIP configuration 1. Access the receiver's configuration interface. Depending on the receiver model, this may be via: * The **receiver's web interface** (connect via Wi-Fi or Ethernet and open the configuration page in a browser) * The **Leica iCON field software** on the iGD4 display under the receiver/corrections settings 2. Navigate to the **NTRIP** or **Corrections** configuration section. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields on the receiver: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in ALL CAPS. Do not browse the source table — enter the mountpoint name directly. {% endhint %} {% endstep %} {% step %} ### Connect and verify RTK status 1. Save the settings and initiate the NTRIP connection on the receiver. 2. Monitor the RTK status on the iGD4 display: | Status | Meaning | | -------------------- | ------------------------------------------------------------------------- | | **Autonomous / GPS** | Basic satellite fix. No corrections applied. | | **DGPS / Float** | Correction data arriving and being processed. | | **RTK Fixed** | Centimeter-level accuracy achieved. Ready for machine control operations. | 3. Convergence to RTK Fixed typically takes **30–90 seconds** with clear sky visibility. {% hint style="info" %} For machine control operations, always wait for **RTK Fixed** before beginning grading, excavation, or dozing. Working in Float mode may result in elevation errors that affect cut/fill accuracy. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights. For machine control, you typically work with a local site calibration or localization. Configure the appropriate vertical datum in your Leica iCON project settings. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Cannot find NTRIP settings on the display | NTRIP is configured on the receiver | Access the receiver's configuration interface (web UI or via iCON field software), not the display settings. | | RTK license error | No RTK license on receiver | Contact your Leica dealer to activate the RTK license on the specific receiver unit. | | No internet connection | SIM card missing or inactive | Verify the SIM card is properly inserted in the receiver and has an active data plan. | | Connection fails | Wrong host or port | Double-check the host address for your region and confirm port is `2101`. | | Authentication error | Wrong credentials | Use the username and password from your RTKdata dashboard, not your website login. Credentials are case-sensitive. | | Stuck on Float | Poor sky visibility | Ensure the GNSS antenna is mounted high and clear on the machine, away from obstructions like booms and cabs. | | Stuck on Float | Weak cellular signal | Check the receiver's signal strength. Construction sites in urban canyons or remote areas may have poor coverage. | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS. | ## Tips * **Configure the receiver, not the display.** This is the most important thing to remember with Leica iCON machine control. The receiver owns the NTRIP connection and RTK license. * **The receiver's built-in modem** eliminates the need for external cellular devices. Just insert a SIM card and configure NTRIP. * **iCON gps 80 and iCG160** are the higher-end receivers with faster convergence and better multipath rejection — ideal for demanding machine control environments. * **Site calibration is critical.** Perform a site localization to align RTK coordinates with your design surface before starting machine control work. * **Multiple machines on one site** can each use their own RTKdata connection. Each receiver needs its own SIM card and NTRIP credentials. * **Keep receiver firmware updated** via Leica myWorld for the latest constellation support and NTRIP client improvements. * **iGD4 vs iGD4SP:** Both displays work with the same receivers and NTRIP setup. The iGD4SP adds additional machine control features but does not change the RTK configuration process. ## Related Industry Solutions * [Construction](https://rtkdata.com/construction/) # Trimble Earthworks NTRIP Setup: Machine RTK Connect Trimble Earthworks on a TD520 to RTKdata NTRIP for centimeter RTK on dozers, excavators and graders. Simple Use NTRIP toggle, port 2101, AUTO. Connect a **Trimble Earthworks** machine control system to RTKdata.com for centimeter-level RTK positioning on excavators, dozers, and graders. Earthworks provides a straightforward NTRIP configuration — no VRS confusion like in Trimble Access. ## Key capabilities | Feature | Details | | ------------------------ | ----------------------------------------------------------------- | | **Compatible display** | Trimble TD520 | | **Compatible receivers** | SNR930, MS992, MS995 | | **NTRIP configuration** | GNSS Configuration > Corrections > NTRIP | | **Correction format** | RTCM 3.x via NTRIP | | **RTK license** | Required on the receiver | | **VRS confusion?** | No — Earthworks uses a simple NTRIP toggle, unlike Trimble Access | ## Requirements * **Trimble Earthworks** software on a **TD520** display * **GNSS receiver:** SNR930, MS992, or MS995 with **RTK activation** * **Internet connection:** Built-in cellular modem on the receiver or external modem * **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 %} ### Verify RTK activation on the receiver 1. Confirm that your GNSS receiver (SNR930, MS992, or MS995) has an active **RTK license**. 2. RTK activation is tied to the receiver hardware, not the Earthworks software. 3. If RTK is not activated, contact your Trimble dealer. {% hint style="warning" %} Without RTK activation on the receiver, the NTRIP connection will not deliver corrections even if all settings are entered correctly. {% endhint %} {% endstep %} {% step %} ### Verify internet connectivity 1. Ensure the receiver has internet access via its built-in cellular modem (with active SIM card) or an external modem. 2. Verify signal strength on the display or receiver status indicators. {% endstep %} {% step %} ### Open NTRIP correction settings 1. On the TD520 display running Earthworks, navigate to **GNSS Configuration** > **Corrections**. 2. Under **NTRIP**, set **Use NTRIP** to **Yes**. {% endstep %} {% step %} ### Enter RTKdata.com NTRIP settings Fill in the NTRIP connection fields: {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% 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 website login) * **Mountpoint (ALL CAPS):** `AUTO` {% endtab %} {% endtabs %} {% hint style="warning" %} Type `AUTO` manually in ALL CAPS. Do not browse the source table — enter the mountpoint name directly. {% endhint %} {% endstep %} {% step %} ### Connect and verify RTK status 1. Save the settings. Earthworks will initiate the NTRIP connection. 2. Monitor the GNSS/RTK status indicator on the TD520 display: | Status | Meaning | | -------------------- | ------------------------------------------------------------------------- | | **Autonomous / GPS** | Basic satellite fix. No corrections applied. | | **Float** | Correction data arriving and being processed. | | **RTK Fixed** | Centimeter-level accuracy achieved. Ready for machine control operations. | 3. Convergence to RTK Fixed typically takes **30–90 seconds** with clear sky visibility. {% hint style="info" %} For machine control operations, always wait for **RTK Fixed** before beginning grading, excavation, or dozing. Working in Float mode may result in elevation errors that affect cut/fill accuracy. {% endhint %} {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTK corrections deliver **ellipsoidal heights** (height above the WGS 84 ellipsoid), not orthometric heights. For machine control, you typically work with a local site calibration or localization. Configure the appropriate vertical datum in your Earthworks project settings. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | -------------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------ | | "Use NTRIP" option not available | Outdated Earthworks software | Update Trimble Earthworks to the latest version. | | RTK not available | Receiver not activated | Contact your Trimble dealer to activate RTK on the SNR930, MS992, or MS995 receiver. | | No internet connection | No SIM card or signal | Verify the receiver's cellular modem has an active SIM card with a data plan. Check signal strength. | | Connection fails | Wrong host or port | Double-check the host address for your region and confirm port is `2101`. | | Authentication error | Wrong credentials | Use the username and password from your RTKdata dashboard, not your website login. Credentials are case-sensitive. | | Stuck on Float | Poor sky visibility | Ensure the GNSS antenna is mounted high and clear on the machine. Move away from buildings and dense structures. | | Stuck on Float | Receiver issue | Power-cycle the receiver. If Float persists, verify RTK activation status. | | Mountpoint error | Wrong capitalization | Type `AUTO` in ALL CAPS. | ## Tips * **No VRS confusion.** Unlike Trimble Access (which has separate VRS and NTRIP options that cause confusion), Earthworks uses a simple "Use NTRIP: Yes/No" toggle. Just set it to Yes and enter your credentials. * **TD520 is the standard display** for current Earthworks installations. Older displays may have slightly different menu paths but the same NTRIP settings apply. * **SNR930 vs MS992 vs MS995:** All three receivers support NTRIP and RTK. The configuration is the same — only the receiver hardware capabilities differ (number of channels, tracking performance). * **Site calibration is critical.** Perform a site localization to align RTK coordinates with your design surface before starting machine control work. * **Keep firmware updated** on both the Earthworks software and the GNSS receiver for the latest NTRIP client improvements and constellation support. * **Multiple machines on one site** can each connect to RTKdata.com independently. Each receiver needs its own internet connection and NTRIP credentials. ## Related Industry Solutions * [Construction](https://rtkdata.com/construction/) # RTK Troubleshooting & FAQ: Fix NTRIP Issues RTKdata troubleshooting and FAQ: a 4-point checklist plus fixes for no corrections, FLOAT, auth failures, dropped connections and shifted coordinates. ## Start Here -- The 4-Point Checklist Before investigating further, check these four items. **They resolve about 90% of support requests.** 1. **Credentials:** Are you using the NTRIP credentials from the [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/)? Your website email and password will not work. The NTRIP username starts with `rtk`. 2. **Mountpoint:** Did you type `AUTO` in ALL CAPS? The mountpoint is case-sensitive. `auto`, `Auto`, and `auto_wgs84` will all fail. 3. **Outdoors:** Is your device outside with clear sky visibility? You need at least 5-6 satellites before RTK can work. 4. **GGA enabled:** Is your device sending its position (NMEA GGA) to the caster? Without GGA, the caster cannot assign a base station and you will receive zero data. *** ## Symptom: No Corrections / "Waiting for Base" You are connected (the source table loads or the login succeeds) but no correction data arrives. Throughput shows 0 kB/s. **Things to check:** -GGA output is enabled. Look for "Send NMEA to caster", "Send receiver position", or "Transmit GGA" in your app settings. Set the interval to **1 second (1 Hz)** if adjustable. -You are **outdoors** with a satellite fix. The device needs an autonomous position before it can send GGA. -Mountpoint is exactly `AUTO` (or one of the other valid options, all in ALL CAPS). -Your subscription is active and not expired. -If using DJI: the **drone itself** must have a satellite fix before RTK can connect. Do not test indoors. > **Why this happens:** RTKdata uses your position to select the nearest base station. If the caster never receives your location, it cannot route corrections to you. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). *** ## Symptom: "Auth Failed" / "Invalid Password" The connection is rejected immediately after login. **Things to check:** -You are using NTRIP credentials (username starts with `rtk`), **not** your website email and password. -No trailing spaces were copied with the username or password. Try retyping manually. -Your subscription or free trial has not expired. Check at [My Account](https://rtkdata.com/my-account/). -Another device is not already connected on the same data stream. A second connection will kick the first one off. *** ## Symptom: Stuck on FLOAT Your device is receiving corrections (data throughput is above 0) but accuracy stays at 20-50 cm and never reaches FIX. **Things to check:** * **Sky view:** Move away from tall buildings, dense tree canopy, metal structures, and power lines. RTK needs clear sky above roughly 15 degrees from the horizon. * **Internet quality:** RTK is latency-sensitive. If your connection has more than 1 second of latency, FIX may not be achievable. Use 4G/LTE rather than 3G. Keep your phone close to the controller if using a hotspot. * **Mountpoint:** Confirm you are using `AUTO` in ALL CAPS. * **Wait:** Initial convergence can take up to 90 seconds even in good conditions. If FLOAT persists beyond 2-3 minutes, investigate the points above. * **Coverage:** Verify you are within range of a reference station. Check the [Coverage Map](https://rtkdata.com/coverage/). AUTO selects the nearest base, typically within 30-50 km. * **Disconnect and reconnect** the NTRIP client to force a fresh session. *** ## Symptom: Connection Drops or Times Out You connect successfully but the connection drops after a few seconds, or the hostname cannot be resolved. **Things to check:** * **DNS resolution:** Some older controllers and tablets cannot resolve hostnames. Use the IP fallback instead: | Region | Hostname | IP Fallback | Port | | ------------- | ----------------- | --------------- | ---- | | Europe | `eu.rtkdata.com` | `3.73.41.96` | 2101 | | North America | `rtk.rtkdata.com` | `13.56.117.10` | 2101 | | Australia | `aus.rtkdata.com` | `54.206.56.130` | 2101 | * **Firewall or VPN:** Ensure outbound TCP on port 2101 is not blocked. Disable any VPN. * **Mobile carrier restrictions:** Some carriers block non-standard ports. Try a different network or Wi-Fi hotspot. * **Concurrent connections:** If two devices share the same credentials, they will repeatedly kick each other off. Each simultaneous connection needs its own data stream. *** ## Symptom: Wrong Coordinates or Height Shift You have a solid FIX but your points are consistently shifted by 0.5-1.5 meters compared to local maps or previous survey data. **Things to check:** * **Reference frame mismatch:** The `AUTO` mountpoint delivers corrections in your regional datum (e.g., NAD83, ETRS89, GDA2020). If your GIS or field software expects a different frame, you will see a systematic offset. See [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums). * **Ellipsoidal vs. orthometric heights:** RTKdata delivers ellipsoidal heights. If you compare these to mean-sea-level elevations without applying a geoid model, the difference can range from a few meters to tens of meters depending on location. See [Understanding Heights](/get-started/understanding-heights). * **US Survey Feet vs. International Feet:** In the US, confusion between these two units causes a steady offset of about 1.2 m (4 ft). Check your controller's project unit settings. * **Epoch mismatch:** If you are comparing to old control points, tectonic plate motion may have shifted the ground since those points were established. Consider using the mountpoint that matches the epoch of your control data. *** ## Frequently Asked Questions **Q: Do I need a physical base station on the ground?** No. RTKdata is a Network RTK service. The 20,000+ reference stations in the network act as your base. You only need your rover or drone and an internet connection. **Q: Can I use one set of credentials on two devices at the same time?** No. Each concurrent connection requires its own data stream (subscription). If two devices share the same credentials, the second connection will disconnect the first. Add data streams from your [account dashboard](https://rtkdata.com/my-account/). **Q: What accuracy can I expect?** Under good conditions (open sky, stable internet, within coverage): **1-2 cm horizontal** and **2-3 cm vertical** with a FIX solution. See [Accuracy Expectations](/get-started/accuracy-expectations). **Q: What happens if I lose internet during a flight or survey?** Your device will degrade from FIX to FLOAT (20-50 cm, lasts 10-30 seconds) and then to SINGLE (1-3 m, standard GNSS). Photos or points collected after losing FIX may need adjustment using ground control points. **Q: Does the free trial have any limitations?** No. The 30-day trial provides the same service as paid plans. It ends automatically with no charges. One trial per user. [Start your trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/). **Q: Which mountpoint should I use?** Use `AUTO` unless your project specifically requires WGS84, ITRF2020, or ITRF2014. AUTO matches the regional datum for your area. See [Network & Mountpoints](/get-started/network). *** > **Still stuck?** Email with: > > 1. A screenshot of your NTRIP settings. > 2. A screenshot of the satellite/RTK status on your device. > 3. Your device brand, model, and the app you are using. # Fix NTRIP Connection Issues: No Corrections, FLOAT Fix the most common RTKdata connection problems: no corrections after connecting, stuck on FLOAT, auth failures, dropped sessions and DJI errors. This guide covers the most frequently reported connection problems based on real support conversations. Follow these steps before contacting support. *** ## "Waiting for Corrections" — Nothing Happens After Connecting This is the #1 support request. You're connected but no corrections arrive. ### Checklist | Check | What to do | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **GGA enabled?** | Your device MUST send NMEA GGA messages to the caster. Without GGA, RTKdata cannot determine your position and will not send corrections. Set GGA output to **1 second (1 Hz)**. | | **Outdoors?** | You need a clear sky view with at least 5–6 satellites. RTK will **never** work indoors. | | **Mountpoint in ALL CAPS?** | The mountpoint must be `AUTO`, `AUTO_WGS84`, `AUTO_ITRF2020`, or `AUTO_ITRF2014`. Typing `auto`, `Auto`, or anything else **will not work**. | | **Correct credentials?** | Use your **NTRIP credentials** from the [RTKdata Dashboard](https://rtkdata.com/my-account/rtk-credentials/) — these are different from your website login. Your username typically starts with `rtk`. | | **Internet connection?** | Ensure your device has a stable internet connection (Wi-Fi, mobile hotspot, or 4G dongle). | ### Still not working? Try the **IP fallback** instead of the hostname: | Region | Hostname | IP Fallback | Port | | --------- | ----------------- | --------------- | ---- | | Global | `rtk.rtkdata.com` | `13.56.117.10` | 2101 | | Europe | `eu.rtkdata.com` | `3.73.41.96` | 2101 | | Australia | `aus.rtkdata.com` | `54.206.56.130` | 2101 | *** ## "Cannot Load Mountpoint List" Most devices do **not** auto-populate the mountpoint list. This is normal. **Solution:** Manually type the mountpoint name. Valid options (ALL CAPS): * `AUTO` (recommended) * `AUTO_WGS84` * `AUTO_ITRF2020` * `AUTO_ITRF2014` No other mountpoints exist. Any other value will fail silently. *** ## "Invalid Password" / "Auth Failed" | Cause | Fix | | ------------------------------------------------ | ------------------------------------------------------------------------------------------ | | Using website login instead of NTRIP credentials | Go to [RTK Credentials](https://rtkdata.com/my-account/rtk-credentials/) in your dashboard | | Extra spaces from copy/paste | Re-type username and password manually | | Expired subscription | Check your account status at [My Account](https://rtkdata.com/my-account/) | | Trial ended | Free trial is 30 days, one per user — check if yours has expired | *** ## Stuck on "FLOAT" — Not Reaching FIX FLOAT means your device is receiving corrections but hasn't converged to centimeter accuracy yet. ### Common causes 1. **Obstructed sky view** — Buildings, trees, or structures cause multipath interference. Move to an open area. 2. **Poor internet connection** — Latency above 1 second degrades RTK performance. Switch to a more stable connection. 3. **Wrong mountpoint** — Ensure you're using `AUTO` (ALL CAPS). 4. **Just wait** — Initial convergence can take up to 90 seconds in good conditions. If FLOAT persists beyond 2–3 minutes, check the above. 5. **Too far from base station** — Network RTK works best within 30–50 km of a reference station. Check the [Coverage Map](https://rtkdata.com/coverage/). ### Quick fix sequence 1. Disconnect from the NTRIP service 2. Verify all settings (host, port, mountpoint, credentials, GGA) 3. Move to a location with clear sky view 4. Reconnect 5. Wait 60–90 seconds *** ## Connection Drops or Times Out * **DNS issues on older devices:** Use the IP fallback addresses listed above instead of hostnames. * **Firewall or VPN:** Ensure TCP port **2101** is not blocked. Disable VPN if active. * **Mobile provider restrictions:** Some carriers block non-standard ports. Try connecting via Wi-Fi hotspot from a different device. *** ## Lefebure NTRIP Client — Specific Issues Lefebure is a popular Android NTRIP client. Common setup mistakes: 1. **Enable "Transmit GGA"** — In your NTRIP profile settings, set the GGA interval to **5 or 10 seconds**. Without this, you will receive zero data. 2. **Be outdoors first** — Get a GPS position fix (5–6 satellites minimum) before connecting. 3. **Mountpoint:** Type `AUTO` in ALL CAPS. 4. **If DNS fails:** Use IP `3.73.41.96` (EU) or `13.56.117.10` (global) instead of the hostname. *** ## DJI Drones — Common Problems ### "No RTK Data Available" or "RTK Signal Weak" * Ensure you selected **"Custom Network RTK"** (not D-RTK 2 Mobile Station) * On Agras drones: **Disable D-RTK 2 search** — it conflicts with network RTK * The drone itself (not just the controller) needs a GNSS fix before RTK will connect * Start the drone outdoors, wait for satellite lock, then enable RTK ### "Fail to Enable Network RTK" 1. Check internet connection on the controller 2. Verify NTRIP settings: Host, Port 2101, Mountpoint `AUTO` 3. Restart RTK in DJI Pilot 2: disable RTK → re-enable → reconnect *** ## Emlid Receivers — Common Problems ### "Confirm Login to Resume Data Sync" This Emlid Flow app message means you need to re-authenticate in the app. Sign back in, then retry the NTRIP connection. ### Datum Selection in Emlid Flow * Set to **Global CS** (not a local datum like NAD83) for the NTRIP connection * Apply local datum transformations in post-processing or in your GIS software * See [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums) for details *** ## Before Contacting Support Please include the following in your support request: 1. **Device/app** you're using (brand and model) 2. **Country/region** where you're working 3. **Exact error message** (screenshot if possible) 4. **NTRIP settings** you entered (host, port, mountpoint — do NOT share your password) 5. **RTK status** shown on your device (SINGLE / FLOAT / FIX) # DJI RTK Troubleshooting: Fix Stuck on Converging Fix DJI drones stuck on "Converging" with RTKdata: distance checks, pre-flight sequence, battery-swap re-convergence and Custom Network RTK setup. This guide addresses the most common RTK issues with DJI drones: Mavic 3 Enterprise, Matrice 4 Enterprise, Matrice 350 RTK, Phantom 4 RTK, Inspire 3, and Agras series. If your DJI drone shows "Converging" but never reaches "FIX", start here. *** ## "Converging" — RTK Not Reaching FIX DJI drones are strict about RTK status. They require a stable FIX before enabling RTK-assisted flight. "Converging" means the drone is receiving corrections but hasn't locked to centimeter accuracy yet. ### Decision Tree: What To Do ``` RTK shows "Converging" for more than 2 minutes | +-- Are you within 30 km of a base station? | | | +-- YES --> Check environment (open sky? no buildings/trees nearby?) | | | | | +-- Good sky view --> Wait up to 3 minutes. Try restart sequence below. | | +-- Obstructed --> Move to open area, restart. | | | +-- NO --> Check distance on Coverage Map | | | +-- 30-50 km: FIX possible but sensitive. Be patient, ensure perfect sky view. | +-- 50+ km: FIX unlikely. Consider Float-mode flight or local base station. | +-- Is your internet connection stable? | +-- Weak hotspot / VPN active --> Switch to stronger connection, disable VPN +-- Stable 4G/5G --> Continue troubleshooting below ``` *** ## Distance Matters Distance to the nearest base station is the single biggest factor for DJI RTK success. Check the [RTKdata Coverage Map](https://rtkdata.com/coverage/) before flying — if you're within the colored zones, RTK FIX is achievable. > **If you are far from the nearest station and stuck on "Converging" — distance is likely the issue, not your settings.** *** ## Pre-Flight RTK Checklist Follow this exact sequence every time: 1. **Power on the drone outdoors** (not indoors, not in a vehicle) 2. **Wait for GNSS satellite lock** — DJI Pilot 2 shows satellite count (need 10+ for best results) 3. **Verify internet connection** on the controller (Wi-Fi, hotspot, or 4G dongle) 4. **Enable Network RTK** in DJI Pilot 2 5. **Wait for RTK FIX** — keep the drone stationary on the ground 6. **Do NOT move the drone** during convergence — DJI needs a stable initialization 7. Once FIX is achieved, you can take off *** ## Battery Swap Procedure Swapping the battery **resets the RTK module**. The drone must re-converge from scratch. **After every battery swap:** 1. Power on the drone (keep it on the ground) 2. Wait for satellite lock (check satellite count in DJI Pilot 2) 3. Re-enable Network RTK if it doesn't auto-reconnect 4. Wait for FIX before takeoff — this may take 30–90 seconds 5. Do NOT rush — starting a mission before FIX will result in poor accuracy *** ## Common DJI Error Messages ### "No RTK Data Available" **Causes:** * Selected "D-RTK 2 Mobile Station" instead of "Custom Network RTK" * On Agras drones: D-RTK 2 search is enabled and conflicts with network RTK * Drone does not have a GNSS fix yet (needs satellites first, then RTK) **Fix:** 1. Go to RTK settings in DJI Pilot 2 2. Select **Custom Network RTK** (not D-RTK 2) 3. On Agras: disable "D-RTK 2 Search" toggle 4. Ensure the drone has satellite lock before enabling RTK ### "Fail to Enable Network RTK" 1. Check controller internet connection 2. Verify NTRIP settings: Host, Port `2101`, Mountpoint `AUTO` 3. Toggle RTK off → wait 5 seconds → toggle on again 4. If persistent: restart DJI Pilot 2 app completely ### "RTK Signal Weak" This usually means FLOAT status with poor convergence: * Check distance to nearest base station * Improve sky view (avoid buildings, trees, metal structures near takeoff) * Ensure stable internet (latency matters for RTK) *** ## Map Pilot Pro vs. DJI Pilot 2 If you use **Map Pilot Pro** (by Maps Made Easy) instead of DJI Pilot 2: * Map Pilot Pro has its **own NTRIP settings** — it does NOT inherit RTK settings from DJI Pilot 2 * Use port `2101` (NOT port `2103` which some versions default to) * You must configure Host, Port, Mountpoint, and Credentials separately in Map Pilot Pro * After configuring, verify RTK status within Map Pilot Pro before starting a mission *** ## "Allow Takeoff in Float" Setting DJI Pilot 2 has an option to allow takeoff even when RTK is in FLOAT (not FIX): * **Where:** RTK Settings > Allow Non-Fixed RTK Takeoff * **When to use:** When you're in a 30-50 km zone and FIX is intermittent * **Accuracy in Float:** Typically 10-30 cm (enough for photogrammetry, not for survey-grade GCPs) * **Warning:** Your flight data will be tagged as FLOAT, which may affect processing in DJI Terra or Pix4D *** ## DJI Drone Compatibility All DJI Enterprise/Agras drones with RTK capability work with RTKdata: | Drone | RTK Module | Notes | | ------------------------ | ---------- | -------------------------------- | | Mavic 3 Enterprise RTK | Built-in | Most popular model | | Matrice 4 Enterprise RTK | Built-in | Newest model | | Matrice 350 RTK | Built-in | Heavy-lift platform | | Matrice 300 RTK | Built-in | Previous generation | | Phantom 4 RTK | Built-in | Legacy, still supported | | Inspire 3 | Built-in | Cinema/survey platform | | Agras T50/T40/T25 | Built-in | Agricultural spraying | | DJI Dock 2 | Remote RTK | Requires stable internet at dock | > **DJI consumer drones (Mini, Air, Mavic 3 non-Enterprise) do NOT have RTK capability and cannot use RTKdata.** *** ## Internet Connection Tips for DJI DJI drones need a stable internet connection **on the controller** (not the drone itself): | Method | Reliability | Notes | | -------------------------------- | ----------- | -------------------------- | | Phone hotspot (4G/5G) | Good | Most common setup | | USB 4G dongle on controller | Very good | Recommended for field work | | Controller built-in 4G (RC Plus) | Excellent | Best option if available | | Wi-Fi from nearby building | Variable | Signal may drop in flight | **Tips:** * Keep the hotspot device close to the controller * Disable VPN — it adds latency that degrades RTK * If connection drops mid-flight, RTK will switch to FLOAT automatically (flight continues safely) *** ## Still Not Working? Before contacting support, please note: 1. Your **drone model** and **DJI Pilot 2 version** 2. Your **location** (country/region) 3. **Distance to nearest base station** (check Coverage Map) 4. Screenshot of your **NTRIP settings** in DJI Pilot 2 5. Screenshot of the **RTK status screen** showing the error 6. How long you waited for convergence Contact with this information. # Host a Base Station: Earn Free RTK Corrections Host an RTKdata GNSS reference station and earn 1 year of free RTK. See the sky view, USB-C power, Wi-Fi requirements and 12-24 hour calibration process. If you're in an area with limited coverage, you can host a GNSS base station and get **1 year of free RTK service** in return. *** ## What We Provide * A **compact GNSS reference station** (roughly the size of a large water bottle) * Pre-configured and ready to install — no technical setup required * Remote monitoring and maintenance by the RTKdata team * **1 year of free RTK corrections** for your account *** ## What You Provide | Requirement | Details | | -------------- | ------------------------------------------------------------------------------------------- | | **Location** | A spot with clear, unobstructed sky view (roof, pole, fence post) | | **Power** | 1.5W via USB-C — a standard phone charger is sufficient | | **Wi-Fi** | 2.4 GHz network, always-on — the station uses approximately 5 kbit/s (negligible bandwidth) | | **Permanence** | The station must remain stationary. Any movement invalidates the calibration. | | **Protection** | Sheltered from direct rain/snow on the USB port. The antenna itself is weatherproof. | *** ## Installation Requirements ### Sky View The station needs a **clear view of the sky** in all directions, ideally down to 10–15 degrees above the horizon. **Good locations:** * Rooftop (flat or pitched — both work) * Top of a pole or fence post * Open balcony with no overhead cover **Bad locations:** * Under a metal roof or overhang * Near large trees that block the sky * Inside a building or garage * Next to tall walls or structures on multiple sides ### Height The station does **not** need to be extremely high. A rooftop at normal building height (3–10 m) is ideal. Putting it on a tall cell tower adds cost and complexity without meaningful accuracy improvement — low-elevation satellites (near the horizon) are actually the least reliable for RTK. *** ## The Process 1. **You send us your location** — GPS coordinates or a Google Maps pin 2. **We evaluate coverage** — Is there a gap? Would a station here help the network? 3. **We ship the station** — Pre-configured, ready to install 4. **You install it** — Mount it in a good sky-view location, connect power and Wi-Fi 5. **Auto-calibration** — The station calibrates automatically over 12–24 hours 6. **Station goes live** — It starts providing corrections to the RTKdata network *** ## Calibration Period After installation, the station needs **12–24 hours** to determine its precise position. During this time: * The station is collecting satellite observations * RTKdata servers compute the exact antenna position * No manual input or configuration is needed * The station will appear on the coverage map after calibration completes > **Do NOT move the station during or after calibration.** Even a few centimeters of movement will require re-calibration. *** ## Frequently Asked Questions ### "Is the station data private / only for me?" No. The station becomes part of the RTKdata public network. All subscribers in range can use it. In return, you get 1 year of free service. ### "Can I access the raw data (RINEX) from the station?" Raw observation data is managed by RTKdata. Contact support if you have a specific need for base station observation files. ### "What if my internet goes down?" The station will buffer briefly and reconnect automatically. Short outages (minutes) are fine. Extended outages (days) will take the station offline until connectivity is restored. ### "What if I move or need to remove the station?" Contact us before removing the station. We'll coordinate the return or relocation. If you relocate the station yourself, it will need to re-calibrate (12–24 hours). ### "Does it need a SIM card or cellular connection?" No. Wi-Fi is sufficient. The data rate is approximately 5 kbit/s — less than streaming a single song. Any standard home or office Wi-Fi works. ### "What about power consumption?" The station draws approximately 1.5 watts — less than a phone charger. Annual electricity cost is negligible (under $2/year). *** ## Interested? Send your proposed location to with: 1. **GPS coordinates** or a Google Maps link of the installation site 2. **Photos** of the proposed mounting location (showing sky view) 3. **Confirmation** that you can provide permanent power (USB-C) and Wi-Fi (2.4 GHz) We'll evaluate the location and get back to you within a few business days. # Support: Fix RTK FIX & NTRIP Issues Get RTKdata support fast: self-service guides, quick fixes for RTK FIX issues, regional host details and exactly what info to send the support team. ## Overview Structured approach to resolving RTK connection issues, with self-service resources and efficient troubleshooting. *** ## Self-Service Resources * [Quick Start Guide](https://docs.rtkdata.com/get-started/quick-start) * [Troubleshooting & FAQ](https://docs.rtkdata.com/support/troubleshooting-and-faq) * [Free Trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) for coverage validation *** ## Information to Provide When Contacting Support When reaching out, please include: 1. **Username** and regional host details 2. **Exact mountpoint** (case-sensitive) 3. A **GGA sentence** from a failed session 4. **Receiver and application** information 5. Specific **error messages** encountered 6. **Testing timestamp and location** *** ## Common Quick Fixes * Enable **GGA transmission** outdoors * Switch correction format to **RTCM3** * Verify **password** accuracy (use RTK credentials, not website login) * Confirm proper **datum/epoch** settings * Use correct **survey foot units** (US Survey Feet vs. International Feet) *** ## Contact Information * **Email:** * **Subject line suggestion:** "URGENT -- Can't get RTK FIX" * **Response target:** Same business day for field-blocking issues *** ## Regional Connection Details | Region | Hostname | Port | Mountpoint | | ------------- | ----------------- | ------ | ---------- | | North America | `rtk.rtkdata.com` | `2101` | `AUTO` | | Europe | `eu.rtkdata.com` | `2101` | `AUTO` | | Australia | `aus.rtkdata.com` | `2101` | `AUTO` | # FAQ: NTRIP Setup, Accuracy & Billing Answers to common RTKdata.com questions on NTRIP setup, hosts and mountpoints, GGA, accuracy and coordinate frames, global coverage, device compatibility, and billing. ## Getting Started **How do I connect quickly?** Follow the [Quick Start](/get-started/quick-start), then check the [Network & Mountpoints](/get-started/network) page. In short: use the regional hostname (NA/EU/AUS), Port `2101`, mountpoint `AUTO` (ALL CAPS), and make sure your app or device sends NMEA GGA to the caster. **What is GNSS RTK in simple terms?** RTK is a real-time correction method that uses fixed base stations and streams corrections to your rover over the internet (NTRIP), delivering centimeter-level accuracy in open sky. *** ## Connection & Settings **Which server (host) should I use?** Use the hostname closest to you. If your device only accepts numbers or DNS is blocked, use the IP fallback: | Region | Hostname | IP Fallback | Port | | ------------- | ----------------- | --------------- | ------ | | North America | `rtk.rtkdata.com` | `13.56.117.10` | `2101` | | Europe | `eu.rtkdata.com` | `3.73.41.96` | `2101` | | Australia | `aus.rtkdata.com` | `54.206.56.130` | `2101` | **Which mountpoint should I choose?** Use `AUTO` unless your workflow explicitly needs a global frame. AUTO applies the regional frame automatically (e.g., NAD83(2011) in the US, ETRS89 in Europe, GDA2020 in Australia). For global frames choose `AUTO_WGS84` or `AUTO_ITRF2020`. **Do I need to send GGA?** Yes. The caster needs your position (NMEA GGA) to select the nearest base station. Enable "Send GGA to caster" in your app or device. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials). **What correction format should my rover accept?** RTCM 3.x over NTRIP. Most modern GNSS receivers and apps support this out of the box. *** ## Accuracy, Frames & Heights **What accuracy should I expect?** In open sky: \~1–2 cm horizontal and 2–4 cm vertical with RTK FIX. Sky view, antenna quality, and distance to the nearest base station all affect results. **What's the difference between AUTO, AUTO\_WGS84 and AUTO\_ITRF2020?** * **AUTO** — applies the regional frame automatically (NAD83 / ETRS89 / GDA2020 / NZGD2000) * **AUTO\_WGS84** — uses global WGS84 * **AUTO\_ITRF2020** — uses ITRF2020 * **AUTO\_ITRF2014** — uses ITRF2014 Pick the one that matches your project's coordinate system. **Why do my elevations look "off"?** RTKdata delivers ellipsoidal heights. Apply a geoid model (e.g., EGM2008, GEOID18, AUSGeoid2020) in your GIS or field software to get orthometric heights (mean sea level). See [Understanding Heights](/get-started/understanding-heights). *** ## Coverage & Performance **Is coverage limited to North America, Europe, and Australia?** No — those are regional server endpoints. Coverage is global with 20,000+ reference stations. The network assigns the nearest base using your GGA position, regardless of which endpoint you connect to. Always validate with a quick outdoor FIX test. **When does RTK perform best?** In open environments with clear satellite view and minimal multipath (away from trees, buildings, metal structures). *** ## Devices & Compatibility **What equipment is compatible?** Any rover, drone, or app that supports NTRIP and RTCM 3.x. See the [Integration Hub](/integration-hub/integration-hub) for step-by-step guides covering DJI, Emlid, Trimble, Leica, ArduSimple, and more. **Do I need my own base station?** No. RTKdata is a Network RTK service — the 20,000+ reference stations act as your base. You only need your rover and an internet connection. **How many devices can I use per subscription?** One active connection at a time. If a second device connects with the same credentials, the first gets disconnected. For simultaneous use, add data streams from your [account dashboard](https://rtkdata.com/my-account/). *** ## Accounts, Plans & Billing **Do you offer a free trial?** Yes — 30 days, full access, no credit card required. It ends automatically. [Start Free Trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) **What are the prices?** See the [Pricing](https://rtkdata.com/pricing/) page for current monthly, annual, and 5-year plans. **Can I cancel and resume later?** Yes. Manage your subscription from your [account dashboard](https://rtkdata.com/my-account/). No lock-in, no penalties. *** ## Troubleshooting & Support **I'm connected but getting no corrections.** Almost always: GGA is not being sent. Enable "Send GGA to caster" in your app settings, confirm mountpoint = `AUTO` (ALL CAPS), and ensure you're outdoors. See [Troubleshooting & FAQ](/support/troubleshooting-and-faq). **Which port should my firewall allow?** TCP `2101` outbound. **How do I contact support?** Email . Include your username, region/host, mountpoint, device model, and screenshots of your NTRIP settings and RTK status. *** ## Legal & Company * [Imprint](https://rtkdata.com/imprint/) * [Privacy Policy](https://rtkdata.com/privacy-policy/) * [Terms of Service](https://rtkdata.com/terms/) # Commercial: Pricing, Invoicing & Plans Your hub for buying RTKdata.com at scale: pricing and plans, procurement and VAT invoicing, enterprise volume licensing, contracts, and partner options. Everything procurement, billing, and legal needs to roll out RTKdata.com at scale. * [Pricing & Plans](/commercial/pricing-and-plans) — monthly, annual, and free trial * [Procurement & Invoicing](/commercial/procurement-and-invoicing) — VAT, invoices, payment methods * [Enterprise & Volume](/commercial/enterprise-and-volume) — quotes, multi-license, support options * [Contracts & Legal](/commercial/contracts-and-legal) — Imprint, Terms of Service, Privacy * [Partner Program](/commercial/partner-program) — referral and affiliate options # Pricing & Plans: RTK Subscription Costs Compare RTKdata.com plans: a 30-day free trial, monthly and annual NTRIP subscriptions, and enterprise volume licensing, with centimeter-level RTK and global coverage. ## Plans | Plan | Price | Details | | -------------- | -------------- | ------------------------------------------------------------- | | **Free Trial** | $0 for 30 days | One trial per user/device, auto-ends, no credit card required | | **Monthly** | $40/month | One license, one data stream | | **Annual** | $400/year | Save 17% vs monthly | | **Enterprise** | Custom | Volume licensing, multi-device, dedicated support | ## Buy / Start Trial * [View Pricing](https://rtkdata.com/pricing/) * [Start 30-Day Free Trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) ## What You Get * Centimeter-level RTK via NTRIP (RTCM 3.x) * Multi-constellation GNSS (GPS, Galileo, BeiDou, GLONASS) * NTRIP credentials to enter in your GNSS device or app (see [Quick Start](/get-started/quick-start)) * Global coverage — check the [Coverage Map](/get-started/coverage-map) * One data stream per license (one active device at a time) {% hint style="info" %} Taxes/VAT may apply depending on your location (e.g., 19% VAT in Germany). Check the invoice in your checkout confirmation. {% endhint %} *** ## Ready to Talk? Book a 15-minute call with our team to plan your RTK rollout, check coverage, or discuss enterprise licensing. [Book a Call](https://sales.rtkdata.com/#use) # Procurement & Invoicing: VAT & Billing How RTKdata.com handles billing: company and VAT details, automatic invoices, credit-card payment, instant credential delivery, and vendor onboarding documents. ## Company & Legal * **Kansi Solutions GmbH**, Rotenbergerweg 24, 66640 Namborn, Germany * HRB 107712 (Local Court Saarbrücken) * VAT ID: DE346326134 * See [Contracts & Legal](/commercial/contracts-and-legal) for Terms of Service, Privacy Policy, and Imprint ## Invoices & VAT * Invoices are issued automatically via the checkout system * VAT (e.g., 19% in Germany) is shown where applicable * Need a PDF invoice or custom billing fields? Include your company details during checkout or contact [Sales](https://rtkdata.com/contact/) ## Payment & Licenses * Monthly or annual subscriptions via credit card * Credentials are delivered immediately after payment confirmation * One license = one data stream (one active device at a time) ## W-9 / Company Documents For vendor onboarding or company documentation requests, email or use the [Contact page](https://rtkdata.com/contact/). # Enterprise RTK: Volume NTRIP Licensing Roll out RTKdata.com RTK corrections across many devices with volume licensing, VAT-ready invoicing, purchase orders, connectivity guidance, and priority support. ## Why Enterprise RTKdata.com? * **Scale fast** — roll out corrections to dozens or hundreds of devices with one contract * **Save money** — volume licensing and annual plans reduce per-device cost * **Stay compliant** — VAT-ready invoices, company legal details, and purchase order flow * **Be secure** — firewall/APN allow-list guidance (Port 2101/TCP), enterprise connectivity checklists * **Get support** — priority SLA and a dedicated account contact ## What We Offer * **Volume licensing** (multi-device) with tailored discounts * **Account coordination & invoicing support** — VAT, POs, consolidated billing * **Connectivity guidance** — firewall/APN allow-list for Port 2101/TCP * **Priority support options** — SLA, fast response, onboarding help ## Next Steps 1. [Start a Free Trial](https://rtkdata.com/try-rtk-corrections-free-for-30-days/) to test coverage in your region (auto-ends, no risk) 2. [Book a Call](https://sales.rtkdata.com/#use) with our enterprise team to discuss licensing and deployment 3. Or [Contact Sales](https://rtkdata.com/contact/) for a formal quote # Contracts & Legal: Terms & Privacy Legal references for RTKdata.com: Terms of Service, Privacy Policy, and Imprint, plus Kansi Solutions GmbH company details, VAT ID, and support contacts. Official legal references (hosted on rtkdata.com): * [Terms of Service](https://rtkdata.com/terms/) * [Privacy Policy](https://rtkdata.com/privacy-policy/) * [Imprint / Legal Notice](https://rtkdata.com/imprint/) *** ## Company **Kansi Solutions GmbH** · Rotenbergerweg 24 · 66640 Namborn · Germany HRB 107712 · VAT ID DE346326134 (see [Imprint](https://rtkdata.com/imprint/)). Expertise you can trust: We provide expert support directly from Germany — the birthplace of the NTRIP protocol. We ensure your GNSS equipment receives the most reliable corrections, backed by the engineering standards of the region where network RTK was invented. *** ## Support & Contact * Technical support: * Sales: [Contact](https://rtkdata.com/contact/) # Partner Program: Affiliate & OEM Deals Earn commissions referring customers to RTKdata.com through the affiliate program, or reach out about co-marketing, white-label, and OEM integration partnerships. ## Affiliate Program Earn commissions by referring customers to RTKdata.com. * **Partner Program:** [rtkdata.com/partner-program](https://rtkdata.com/partner-program/) — details, sign up, and start earning ## Co-Marketing & OEM Partnerships For co-marketing, white-label, or OEM integration partnerships, contact our team: * [Contact Sales](https://rtkdata.com/contact/) * Email: