> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/integration-hub/lidar-scanners-and-mobile-mapping.md).

# LiDAR Scanner RTK Setup: SLAM & Mobile Mapping NTRIP

RTK setup guides for SLAM scanners, LiDAR payloads and mobile mapping: XGRIDS, FJD Trion, CHCNAV, Emesent, GeoSun and more with the RTKdata AUTO mountpoint.

These guides cover the LiDAR scanner RTK setup with RTKdata NTRIP corrections for handheld SLAM scanners, backpack and vehicle mobile mapping systems and LiDAR drone payloads. Every guide uses the AUTO mountpoint, which picks the nearest reference station from the position the scanner reports, so the SLAM point cloud can be georeferenced with the RTK positions recorded during the scan.

This page collects what all scanners have in common: the connection values, the ways a scanner gets internet, the checks before a scan, and the mountpoint and datum rules. The device guides below add the manufacturer's field names and screens.

RTKdata connection settings for every scanner on this page:

| Region            | Hostname (preferred) | 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` |

| Field                  | Value                                                                                                                                                    |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Host**               | `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia). Choose the server closest to your work area.              |
| **Host (IP fallback)** | `13.56.117.10` (North America), `3.73.41.96` (Europe), `54.206.56.130` (Australia). Only if the scanner does not accept the hostname. GeoSun: IP first.  |
| **Port**               | `2101`                                                                                                                                                   |
| **Mountpoint**         | `AUTO` in capital letters. Alternatives: `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84`                                                                  |
| **Username**           | From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). It starts with `rtk` and is not your website login. |
| **Password**           | From *RTK Credentials*, not your website password                                                                                                        |
| **NMEA GGA**           | Required. The scanner has to report its position, otherwise the login succeeds but no corrections arrive.                                                |

All three servers share the same base station network; the difference is routing latency. Full reference: [NTRIP Server Settings](/get-started/network.md).

{% 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 %}

## Which LiDAR scanners can use RTKdata corrections?

The XGRIDS Lixel K1, K2, L2 Pro and L3, FJD Trion P1, P2 and S2, CHCNAV RS10 / RS30, 3DMakerpro Eagle and Raven, Stonex X200GO and X120GO, GreenValley LiGrip, Emesent GX1 and Hovermap, Inertial Labs RESEPI / Teledyne EchoONE, GeoSun GS-200G, GS-100G and GS-130G, SkylandX MetaCam Air 2 and MetaCam Air, and SHARE SLAM S20, C1 Pro, S20 SE RTK and S100 can use RTKdata corrections in the RTK configurations listed below, because each one accepts a custom NTRIP caster in its app, in its web interface or in the external GNSS rover it works with.

| Scanner (also covers)                                                                                                                                                                         | App or software                                                               | Where the NTRIP settings go                                                                                             | Internet for corrections                                                                                                                                 | Guide                                                                                                                |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| XGRIDS Lixel K1 (LixelKity K1), K2, L2 Pro                                                                                                                                                    | LixelGO (iOS, Android)                                                        | **RTK Settings** > **Account Settings**, **Type** **Custom**                                                            | Phone mobile data in **Quick Connect Mode**, phone hotspot in **Hotspot Mode** (iOS: **Direct Connect Mode**), or Wi-Fi with internet in **Bridge Mode** | [XGRIDS Lixel K1 / K2 / L2 Pro](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-k1-k2-l2-pro.md)     |
| XGRIDS Lixel L3 (16 and 32 channels)                                                                                                                                                          | LixelGO                                                                       | **RTK Settings**, as documented for the K2 and L2 Pro                                                                   | Phone with mobile data, or Wi-Fi with internet                                                                                                           | [XGRIDS Lixel L3](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-l3.md)                             |
| FJD Trion P1 with RTK Module (SR), P2, S2 (S2 PRO, S2 MAX)                                                                                                                                    | FJD Trion Scan (iOS, Android)                                                 | **Settings** > **RTK Settings** > **Rover** (older app versions: **Mobile Station Settings**) > **Add**, **Ntrip** card | Scanner joins the phone's personal hotspot (network mode)                                                                                                | [FJD Trion P1 / P2 / S2](/integration-hub/lidar-scanners-and-mobile-mapping/fjd-trion-p1-p2-s2.md)                   |
| CHCNAV RS10 (16 lines), RS10 (32 lines), sold as RS30                                                                                                                                         | SmartGo Neo (Android)                                                         | **RTK settings**, **Type** **CORS**                                                                                     | Tablet or phone on the scanner Wi-Fi `SLAM-XXXXX`, internet from its mobile data                                                                         | [CHCNAV RS10 / RS30](/integration-hub/lidar-scanners-and-mobile-mapping/chcnav-rs10-rs30.md)                         |
| 3DMakerpro Eagle with factory RTK module, Raven Max RTK, Raven with RTK module (Hawk with RTK kit)                                                                                            | Scanner **GPS** screen, RayStudio on Windows                                  | **GPS** screen, **Connect GPS** and **RTK** on                                                                          | Phone hotspot or site Wi-Fi through **Link Hotspots**                                                                                                    | [3DMakerpro Eagle / Raven](/integration-hub/lidar-scanners-and-mobile-mapping/3dmakerpro-eagle-raven.md)             |
| Stonex X200GO, X120GO V2; X70GO with RTK70 GO, X120GO V1 with RTK120 GO                                                                                                                       | Stonex GOapp                                                                  | **Settings** > **RTK Settings** > **+ Custom** (module: **S-RTK** > **CORS**)                                           | Hotspot of the tablet or phone with a SIM (module: Nano-SIM in the module)                                                                               | [Stonex X200GO / X120GO / X70GO](/integration-hub/lidar-scanners-and-mobile-mapping/stonex-x200go-x120go.md)         |
| GreenValley LiGrip O2, O2 Lite, SE RTK; O1 Lite, H300, H120 with RTK module; Topcon CR-S1, Sokkia SR-S1 / SR-S2                                                                               | GreenValley app; MAGNET Flow for Topcon and Sokkia                            | **Collection Management** > gear icon > **RTK link**                                                                    | **Phone Network** (phone hotspot) or **Host Network** (SIM in the RTK module)                                                                            | [GreenValley LiGrip](/integration-hub/lidar-scanners-and-mobile-mapping/greenvalley-ligrip.md)                       |
| Emesent GX1 (backpack, survey pole, handheld, vehicle mount)                                                                                                                                  | Emesent Commander (Android)                                                   | **Scanner settings** > **NTRIP profile** > **+ NEW**                                                                    | nano-SIM in the GX1                                                                                                                                      | [Emesent GX1](/integration-hub/lidar-scanners-and-mobile-mapping/emesent-gx1.md)                                     |
| Emesent Hovermap ST / ST-X with Backpack RTK or Vehicle RTK                                                                                                                                   | NTRIP client of the rover: Emlid Flow, Trimble web interface, Leica Captivate | In the GNSS rover, not in the Hovermap                                                                                  | SIM in the rover, or mobile data of the tablet or phone                                                                                                  | [Emesent Hovermap RTK](/integration-hub/lidar-scanners-and-mobile-mapping/emesent-hovermap-backpack-vehicle-rtk.md)  |
| Inertial Labs RESEPI (GEN-II, LITE, Ultra LITE), Teledyne EchoONE                                                                                                                             | Web GUI in the browser                                                        | **Settings > Connectivity > RTCM corrections**, **Connection** **NTRIP Client**                                         | USB LTE modem on the payload                                                                                                                             | [Inertial Labs RESEPI / EchoONE](/integration-hub/lidar-scanners-and-mobile-mapping/inertial-labs-resepi-echoone.md) |
| GeoSun GS-200G, GS-100G, GS-130G (GS-203G: app and pairing not documented by GeoSun yet, steps checked against the GS-200G and GS-100G documentation only)                                    | GeosunMeasure (formerly GnssMeasure, Android)                                 | Gear icon > **RTK** > **RTK Settings**. IP address instead of hostname, as GeoSun instructs                             | Android phone on the scanner (Wi-Fi on the GS-200G, USB on the GS-100G and GS-130G), internet from its mobile data                                       | [GeoSun GS-200G / GS-100G](/integration-hub/lidar-scanners-and-mobile-mapping/geosun-gs-handheld.md)                 |
| SkylandX MetaCam Air 2, MetaCam Air (first generation); MetaCam Pro with RTK module (RTK steps shown by SkylandX on the Air 2 and Air only, check the labels on the Pro)                      | MetaCam Go (iOS, Android)                                                     | **Start** > gear icon (**Settings**) > **RTK**, **Enable RTK Account** on, then **Edit Account**                        | Phone on the scanner Wi-Fi `MetaCam-...`, internet from its mobile data (iPhone: manual IP address for that Wi-Fi)                                       | [SkylandX MetaCam Air 2 / Air](/integration-hub/lidar-scanners-and-mobile-mapping/skylandx-metacam.md)               |
| SHARE SLAM S20, SHARE C1 PRO, SHARE SLAM S20 SE RTK, SHARE SLAM S100-16 / S100-32 / S100-32 PRO; S20 SE and C1 with the RTK module kit (SHARE3DCAM C10: RTK steps not published by SHARE yet) | SHARE Capture (iOS, Android)                                                  | **Start** > gear icon > **RTK**, **RTK Account Switch** on, then **Edit Account**, **Account Type** **User-Defined**    | Phone on the scanner Wi-Fi, internet from its mobile data                                                                                                | [SHARE SLAM S20 / C1 Pro / S100](/integration-hub/lidar-scanners-and-mobile-mapping/share-slam-s20-c1-pro-s100.md)   |

If your scanner is not listed, the values above are the same for any NTRIP client. [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md) explains what the caster expects from the device.

## What does a LiDAR scanner RTK setup with RTKdata need?

A scanner needs the RTKdata host for your region (`rtk.rtkdata.com` for North America, `eu.rtkdata.com` for Europe, `aus.rtkdata.com` for Australia), port `2101`, the mountpoint `AUTO` in capital letters and the NTRIP username and password from *RTK Credentials*, and it has to report its position (NMEA GGA) to the caster before corrections flow.

Each app names these fields differently. This is where the values go:

| Scanner and app                                                                                                                                                                                       | Host                                          | Port            | Mountpoint      | Username and password                               |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | --------------- | --------------- | --------------------------------------------------- |
| [XGRIDS Lixel K1, K2, L2 Pro](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-k1-k2-l2-pro.md), [L3](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-l3.md) (LixelGO) | **Host**                                      | **Port**        | **Mountpoint**  | **Username**, **Password**                          |
| [FJD Trion](/integration-hub/lidar-scanners-and-mobile-mapping/fjd-trion-p1-p2-s2.md) (Trion Scan)                                                                                                    | **Server Address**                            | **Port**        | **Node**        | **Username**, **Password**                          |
| [CHCNAV RS10 / RS30](/integration-hub/lidar-scanners-and-mobile-mapping/chcnav-rs10-rs30.md) (SmartGo Neo)                                                                                            | **Server address**                            | **Port**        | **Source list** | **User name**, **Password**                         |
| [3DMakerpro Eagle / Raven](/integration-hub/lidar-scanners-and-mobile-mapping/3dmakerpro-eagle-raven.md) (**GPS** screen)                                                                             | **Address**                                   | **Port**        | **Mount Point** | **Username**, **Password**                          |
| [Stonex XGO](/integration-hub/lidar-scanners-and-mobile-mapping/stonex-x200go-x120go.md) (GOapp)                                                                                                      | **Server Address**                            | **Port**        | **Mount Point** | **Username**, **Password**                          |
| [GreenValley LiGrip](/integration-hub/lidar-scanners-and-mobile-mapping/greenvalley-ligrip.md) (GreenValley app, MAGNET Flow)                                                                         | **Domain Name/IP Address**                    | **port**        | **Source List** | **Username**, **Password**                          |
| [Emesent GX1](/integration-hub/lidar-scanners-and-mobile-mapping/emesent-gx1.md) (Commander)                                                                                                          | **Address**                                   | **Port**        | **Mount point** | **Username**, **Password**                          |
| [Emesent Hovermap](/integration-hub/lidar-scanners-and-mobile-mapping/emesent-hovermap-backpack-vehicle-rtk.md) rover (Emlid Flow / Trimble web interface)                                            | **Address** / **Ntrip Caster http(s)://**     | **Port**        | **Mount Point** | **Username** (Trimble: **User Name**), **Password** |
| [Inertial Labs RESEPI / EchoONE](/integration-hub/lidar-scanners-and-mobile-mapping/inertial-labs-resepi-echoone.md) (web GUI)                                                                        | **Caster**                                    | **Port**        | **Mount point** | **User**, **Password**                              |
| [GeoSun GS-200G / GS-100G](/integration-hub/lidar-scanners-and-mobile-mapping/geosun-gs-handheld.md) (GeosunMeasure)                                                                                  | **IP Address**, an IP address, not a hostname | **Port Number** | **Mount Point** | **Account**, **Password**                           |
| [SkylandX MetaCam Air 2 / Air](/integration-hub/lidar-scanners-and-mobile-mapping/skylandx-metacam.md) (MetaCam Go, **Edit Account**)                                                                 | **Server**                                    | **Port**        | **Mount Point** | **Account**, **Password**                           |
| [SHARE SLAM S20 / C1 Pro / S100](/integration-hub/lidar-scanners-and-mobile-mapping/share-slam-s20-c1-pro-s100.md) (SHARE Capture, **Edit Account**)                                                  | **Server**                                    | **Port**        | **Mount Point** | **Account**, **Password**                           |

**Hostname or IP address.** Enter the hostname of the server closest to your work area, without `http://` and without `:2101`, because the port has its own field. Use the IP fallback only if the scanner does not accept the hostname or cannot resolve it, for example when SmartGo Neo shows **Server address resolution error, please check and try again.** although the tablet or phone has internet. GeoSun is the exception: GeoSun instructs users to enter an IP address, not a domain name, in the **IP Address** field of GeosunMeasure, so the [GeoSun guide](/integration-hub/lidar-scanners-and-mobile-mapping/geosun-gs-handheld.md) starts with the IP address for your region.

**Mountpoint list.** Some apps load the mountpoint list from the caster, for example **Source Node** in Trion Scan, **Download source list** in SmartGo Neo, the button next to **Mountpoint** in LixelGO or the icon next to **Mount Point** in MetaCam Go. Pick `AUTO` from that list. The RTKdata sourcetable loads without a login, so a visible mountpoint list proves neither your credentials nor a correction stream (checked on 25 September 2026).

**Position (NMEA GGA).** `AUTO` selects the nearest reference station from the position the scanner sends as NMEA GGA. Without it the login still succeeds, but no correction data arrives. Of the apps on this page, only Emlid Flow, used on the Hovermap rovers, has a documented switch for it (**Send receiver's position to the provider**). The RESEPI web GUI states that "RESEPI sends back GPGGA messages with its current position for virtual reference stations". SmartGo Neo has no GGA setting and reports a missing position with **No device location information. Please check if the device is connected and can search for stars normally.** LixelGO and the other scanner apps have no GGA switch, and their manufacturers do not document when the position is sent, so power the scanner on outdoors, wait until it shows its own position and connect only then. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md).

**Credentials.** Type the username and password rather than pasting them, with no space at the start or end. One set of credentials allows one connection at a time, so a second scanner, rover or drone that is connected at the same time needs its own data stream. See [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices).

## Where does a SLAM scanner get internet for NTRIP?

A SLAM scanner gets internet for RTKdata NTRIP corrections in one of five ways: through the app on your phone, through your phone's hotspot, through a phone or tablet that sits on the scanner's own Wi-Fi or USB and uses its mobile data, through its own SIM or LTE modem, or through an external rover or drone that receives the corrections instead.

1. **The app relays the corrections over the phone's mobile data.** LixelGO in **Quick Connect Mode**, the default since LixelGO 1.3.0 (RTK in this mode needs scanner firmware 3.1.1 or later), for the XGRIDS Lixel K1, K2 and L2 Pro.
2. **The scanner joins your phone's hotspot.** FJD Trion in network mode, Stonex X200GO and X120GO V2 on the tablet hotspot, 3DMakerpro Eagle and Raven through **Link Hotspots**, GreenValley LiGrip O2, O2 Lite and SE RTK with **Phone Network**, and LixelGO in **Hotspot Mode** (iOS: **Direct Connect Mode**). LixelGO **Bridge Mode** and the 3DMakerpro scanners also work with a site Wi-Fi that has internet access. FJD specifies 2.4 GHz Wi-Fi for the Trion scanners, and XGRIDS, 3DMakerpro and GreenValley tell iPhone users to turn on **Maximize Compatibility** for the hotspot.
3. **A phone or tablet on the scanner uses its own mobile data.** The CHCNAV RS10 tablet is on the scanner Wi-Fi `SLAM-XXXXX`, the phone on a GeoSun GS-200G is on the scanner Wi-Fi (**WIFI Connect**), the GS-100G and GS-130G connect the phone by USB cable (**USB Connect**), the phone on a SkylandX MetaCam Air 2 or Air is on the scanner Wi-Fi `MetaCam-...`, an iPhone with a manual IP address for that Wi-Fi, and the phone on a SHARE SLAM S20, C1 Pro, S20 SE RTK or S100 is on the scanner Wi-Fi.
4. **The scanner has its own SIM or LTE modem.** Emesent GX1 with a nano-SIM, RESEPI and EchoONE with a USB LTE modem, LiGrip O1 Lite, H300 and H120 with a SIM in the RTK module (**Host Network**), and the Stonex RTK70 GO and RTK120 GO modules with a Nano-SIM.
5. **An external rover or the drone receives the corrections.** A Hovermap gets RTK from the Emlid, Trimble or Leica rover on its Backpack RTK or Vehicle RTK kit. A Stonex X200GO in **Payload Mode** uses the drone's RTK data on the DJI M300 and M350 (for the [DJI M400](/integration-hub/drones-and-uavs/dji-matrice-400.md), Stonex lists PPK instead of RTK), and so does an XGRIDS L2 Pro on an M300 or M350 with **GNSS Mode** **DJI** and **RTK Type** **Aerial RTK**. For RTKdata on a DJI M300 or M350, see [DJI Matrice 300 / 350 RTK](/integration-hub/drones-and-uavs/dji-matrice-300-350-m30t.md). Whether the drone's RTKdata corrections reach the payload has not been confirmed yet.

{% hint style="warning" %}
**If the phone's Wi-Fi is connected to the scanner, the internet has to come from mobile data.** This applies to LixelGO **Quick Connect Mode**, the CHCNAV RS10, the GeoSun GS-200G, the SkylandX MetaCam Air 2 and Air, and the SHARE SLAM S20, C1 Pro, S20 SE RTK and S100. A Wi-Fi-only tablet, a phone without a SIM or a phone with mobile data switched off gets no corrections in these setups. A phone hotspot also needs mobile data and a plan that allows hotspot use.
{% endhint %}

## What should you check before you start a scan?

Before you start a scan with RTKdata corrections, check that the scanner is outdoors under open sky, has internet, has reported its own position and shows the manufacturer's fix indicator, not only a connected state.

* **Coverage.** Check that your site is covered on the [Coverage Map](/get-started/coverage-map.md) before the job.
* **Internet on.** Mobile data on the phone or tablet, the hotspot running, or data on the SIM in the scanner, module or rover.
* **App open during the scan.** When the app relays the corrections (LixelGO **Quick Connect Mode**), keep LixelGO open and, on Android, allow it to run in the background. XGRIDS notes that "if the LixelGO app is closed, the device will lose the fixed solution".
* **Position before connecting.** Power on outdoors and wait until the scanner shows satellites and its own position (**Single** in most apps), then connect.
* **RTK set up before capture.** SmartGo Neo blocks RTK changes during capture (**Unable to switch while capturing.**), and LixelGO warns **Switching NTRIP accounts during scan affects accuracy.**
* **Start and end outdoors.** Start recording only at the fix indicator in the table below, and end the scan under open sky as well.
* **Hovermap order.** Switch on the rover first and the Hovermap only after the rover has a fix.
* **One login per device.** Disconnect any other device that uses the same credentials, or add a data stream for it.

{% hint style="warning" %}
**"Connected" is not "Fixed".** A successful login only means the caster accepted your credentials. If the scanner has not sent its position yet, the session looks exactly like this: logged in, but no correction data. Wait for the fix indicator of your scanner.
{% endhint %}

| Scanner                                                                                                                                                                                     | Wait for this before you scan                                                                                                                                     | Not yet a fix                                                                             |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| [XGRIDS Lixel K1, K2, L2 Pro](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-k1-k2-l2-pro.md), [L3](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-l3.md) | **Fixed** in LixelGO, with more than 10 satellites                                                                                                                | **RTK** and **NTRIP** green on their own                                                  |
| [FJD Trion P1, P2, S2](/integration-hub/lidar-scanners-and-mobile-mapping/fjd-trion-p1-p2-s2.md)                                                                                            | Green check mark on the **Ntrip** card and **RTK Status** **Fixed**                                                                                               | Yellow check mark, **Connected Successfully**                                             |
| [CHCNAV RS10 / RS30](/integration-hub/lidar-scanners-and-mobile-mapping/chcnav-rs10-rs30.md)                                                                                                | **Fixed**, with **Differential data transmission in progress.**                                                                                                   | **Get source list successfully**                                                          |
| [3DMakerpro Eagle / Raven](/integration-hub/lidar-scanners-and-mobile-mapping/3dmakerpro-eagle-raven.md)                                                                                    | No documented fix indicator: start outdoors after **GPS Connection Successful** or the keep-still countdown, then check the exported project for `RTK_XXXXXX.bin` | **Connect success!** after **Save**                                                       |
| [Stonex X200GO / X120GO V2](/integration-hub/lidar-scanners-and-mobile-mapping/stonex-x200go-x120go.md)                                                                                     | **Fixed** at the top right of the GOapp standby page                                                                                                              | **Differential Data: Normal** in **Device State**                                         |
| [GreenValley LiGrip](/integration-hub/lidar-scanners-and-mobile-mapping/greenvalley-ligrip.md)                                                                                              | **RTK configuration successful (Fixed Solution)**                                                                                                                 | `AUTO` visible in **Source List**                                                         |
| [Emesent GX1](/integration-hub/lidar-scanners-and-mobile-mapping/emesent-gx1.md)                                                                                                            | **Last correction** keeps updating (Emesent documents no fix wording for the GX1)                                                                                 | A mountpoint list in **Select mount point**                                               |
| [Emesent Hovermap](/integration-hub/lidar-scanners-and-mobile-mapping/emesent-hovermap-backpack-vehicle-rtk.md)                                                                             | **RTK Fix** on the Commander **Connectivity** page                                                                                                                | **RTK Single**                                                                            |
| [Inertial Labs RESEPI / EchoONE](/integration-hub/lidar-scanners-and-mobile-mapping/inertial-labs-resepi-echoone.md)                                                                        | **GNSS Solution** `COMPUTED,NARROW INTEGER` (newer GUI: **Lat STD**, **Lon STD** and **Alt STD** at centimeter level)                                             | The base block on the **Status** page alone, the orange GNSS LED, `COMPUTED,NARROW FLOAT` |
| [GeoSun GS-200G / GS-100G](/integration-hub/lidar-scanners-and-mobile-mapping/geosun-gs-handheld.md)                                                                                        | **RTK:Fixed Solution**, with the **RTCM** counter rising                                                                                                          | **RTK server connection successful**                                                      |
| [SkylandX MetaCam Air 2 / Air](/integration-hub/lidar-scanners-and-mobile-mapping/skylandx-metacam.md)                                                                                      | **Fixed** in MetaCam Go, with **Station Status: Connected** and a **Differential Age** value                                                                      | **Test Network** **OK**, **Set RTK account successfully!**                                |
| [SHARE SLAM S20 / C1 Pro / S100](/integration-hub/lidar-scanners-and-mobile-mapping/share-slam-s20-c1-pro-s100.md)                                                                          | **FIXED** in the status at the top of SHARE Capture, with **Receiving Data** under **RTK Status:**                                                                | **Success** after **Confirm**, **DGPS**, **FLOAT**                                        |

## Which mountpoint and datum should a scanner use?

On RTKdata, use the mountpoint `AUTO` in capital letters: it delivers your regional datum, for example NAD83(2011) in the USA, ETRS89 in Europe and GDA2020 in Australia, and a global mountpoint is only needed when the deliverable has to stay in a global frame.

| Mountpoint          | Delivers                                                                                                                                 |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **`AUTO`**          | **Recommended.** Your region's datum, see the full table in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md) |
| **`AUTO_ITRF2020`** | ITRF2020 at the current epoch                                                                                                            |
| **`AUTO_ITRF2014`** | ITRF2014 at the current epoch                                                                                                            |
| **`AUTO_WGS84`**    | WGS84(G2139) at the mid-year epoch                                                                                                       |

{% hint style="info" %}
**Datum with AUTO:** `AUTO` delivers the regional datum for your position, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe and GDA2020 in Australia. Regions the table does not list get WGS84(G2139) at the mid-year epoch. Many scanner apps still label the data WGS84. Declare the regional datum in your processing project instead of transforming from WGS84 a second time, and check one control point.
{% endhint %}

* **Capital letters.** Mountpoint names are case sensitive. The 3DMakerpro manuals show the preset `Auto`: change it to `AUTO`.
* **Global mountpoints.** Use `AUTO_ITRF2020`, `AUTO_ITRF2014` or `AUTO_WGS84` only for deliverables in a global frame. The conversion to a local system then happens in your processing software.
* **One mountpoint per project.** Scans on `AUTO` and on a global mountpoint sit in different frames and do not line up.
* **Moving scanners.** On backpack and vehicle routes, `AUTO` can hand off to a closer station as you move, based on the updated position.
* **Datum offset.** A consistent 50 cm to 1 m offset against local control is almost always a datum mismatch, not an accuracy problem. See [Why Your Coordinates May Be Offset](/get-started/coordinate-systems-and-datums.md#why-your-coordinates-may-be-offset).
* **Heights.** RTKdata delivers ellipsoidal heights. A difference of 10 to 50+ m against benchmarks is the geoid separation, so apply a geoid model. See [Understanding Heights](/get-started/understanding-heights.md).

The settings in LixelStudio, Trion Model, CoPre, RayStudio, GOapp, LiDAR360MLS, Aura, PCMasterPro and PointCloudCreater are covered in [Georeferencing SLAM Scans](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md) and in each device guide. MetaCam Studio is covered in the [SkylandX MetaCam guide](/integration-hub/lidar-scanners-and-mobile-mapping/skylandx-metacam.md#how-do-you-georeference-a-metacam-scan-in-metacam-studio). SHARE PointClouds Studio is covered in the [SHARE guide](/integration-hub/lidar-scanners-and-mobile-mapping/share-slam-s20-c1-pro-s100.md#which-coordinate-system-do-you-set-in-share-pointclouds-studio).

## Why does the scanner connect but never reach a fix?

Most often the RTKdata caster has not received the scanner's position (NMEA GGA) yet, so the login succeeds but no corrections arrive; the other common causes are a mountpoint that is not `AUTO` in capital letters, RTKdata credentials in use on a second device and a blocked view of the sky.

| What you see                                                                                                                                                               | Likely cause                                                                             | What to do                                                                                                                                               |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Login rejected, for example **RTK password incorrect** (LixelGO) or **Incorrect username or password** (SmartGo Neo)                                                       | Website login used, a typo, or a space in the field                                      | Retype the username (starts with `rtk`) and password from *RTK Credentials*.                                                                             |
| Logged in, but no correction data                                                                                                                                          | No position sent to the caster yet, or the mountpoint is misspelled                      | Go outdoors, wait for the scanner's own position and reconnect. Check that the mountpoint reads `AUTO` in capital letters.                               |
| Server connection fails: **Server address resolution error, please check and try again.** (SmartGo Neo) or **CORS server login failed, please check IP and port** (LiGrip) | The host or port is wrong, the device cannot resolve the hostname, or it has no internet | Check the internet connection first, then check the host and port `2101`. If both are right, enter the IP fallback for your region and keep port `2101`. |
| No connection on site Wi-Fi, a company network or a VPN                                                                                                                    | Outbound TCP on port `2101` is blocked                                                   | Switch to the phone's mobile data or hotspot. See [NTRIP Server Settings](/get-started/network.md).                                                      |
| Stays on **Single** or **Float**                                                                                                                                           | Blocked sky, too few satellites, or a long distance to the nearest station               | Move to open sky, hold the scanner still, and check the site on the [Coverage Map](/get-started/coverage-map.md).                                        |
| Corrections stop when another device connects                                                                                                                              | Two devices on one set of credentials                                                    | One data stream allows one connection. See [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices). |
| Heights differ from benchmarks by tens of metres                                                                                                                           | Ellipsoidal heights, no geoid applied                                                    | Apply a geoid model. See [Understanding Heights](/get-started/understanding-heights.md).                                                                 |

Device-specific messages are in the troubleshooting table of each guide. For the full checklist, see [Fix NTRIP Connection Issues](/support/common-connection-issues.md).

## Frequently asked questions

### Can I use my own NTRIP service with a handheld SLAM scanner?

Yes. The XGRIDS Lixel, FJD Trion, CHCNAV RS10 and RS30, 3DMakerpro Eagle and Raven, Stonex X200GO and X120GO, GreenValley LiGrip, Emesent GX1, GeoSun GS-200G, GS-100G and GS-130G, SkylandX MetaCam Air 2 and Air, and SHARE SLAM S20, C1 Pro, S20 SE RTK and S100 scanners, the Inertial Labs RESEPI and Teledyne EchoONE payloads and the GNSS rovers used with the Emesent Hovermap accept a third-party NTRIP caster such as RTKdata: you enter host, port, mountpoint, username and password in the app, the web GUI or the rover. In LixelGO you choose **Type** **Custom**, in SmartGo Neo **Type** **CORS** and in Stonex GOapp **+ Custom**; in the GreenValley app **the server** already shows **Custom** in every app language except Chinese. In SHARE Capture you turn on **RTK Account Switch**, tap **Edit Account** and choose **Account Type** **User-Defined**. FJD notes that "the CORS account needs to be purchased by yourself". RTKdata streams RTCM 3.2 with MSM messages, see [Correction format](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md#correction-format). A base station of your own is not needed, because the corrections arrive over NTRIP.

### Does my LiDAR scanner need a SIM card for RTK corrections?

Only some do: for RTKdata NTRIP corrections, most handheld SLAM scanners use the mobile data of the phone or tablet that runs the app, so the SIM goes into the phone. The Emesent GX1 needs a nano-SIM, RESEPI and EchoONE payloads need a USB LTE modem with a data SIM, the LiGrip O1 Lite, H300 and H120 need a SIM in the RTK module, and the Stonex RTK70 GO and RTK120 GO modules take a Nano-SIM.

### Which mountpoint should I use for a SLAM LiDAR scanner?

With RTKdata, use the mountpoint `AUTO`, typed in capital letters. It picks the nearest reference station from the scanner's position and delivers your regional datum. Choose `AUTO_ITRF2020`, `AUTO_ITRF2014` or `AUTO_WGS84` only when the deliverable has to be in that global frame.

### Which datum does my scanner record with the AUTO mountpoint?

With the RTKdata `AUTO` mountpoint, the RTK positions are in your regional datum, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe or GDA2020 in Australia, as listed in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md#regional-geodetic-coordinate-system-rgcs). Many scanner apps and processing programs still label the data WGS84, so declare the regional datum in the processing project instead of transforming from WGS84 a second time. The settings per scanner program are in [Georeferencing SLAM Scans](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md#why-does-my-scanner-software-say-wgs84-when-i-use-auto).

### Do LiDAR drone payloads use the drone's RTK corrections?

It depends on the payload. Inertial Labs RESEPI and Teledyne EchoONE have their own GNSS receiver and take RTKdata corrections only through the **RTCM corrections** block of their own web GUI, so RTK in the drone does not reach them. The Stonex X200GO in **Payload Mode** and the XGRIDS L2 Pro with **RTK Type** **Aerial RTK** use the drone's RTK instead, so their corrections are set up in the drone controller, for example on a [DJI Matrice 300 or 350 RTK](/integration-hub/drones-and-uavs/dji-matrice-300-350-m30t.md). Whether corrections that the drone receives from RTKdata reach the payload has not been confirmed yet for either scanner, so check the first flight against known control points. For the [DJI M400](/integration-hub/drones-and-uavs/dji-matrice-400.md), Stonex lists PPK instead of RTK for the X200GO.

## Quick reference

```
Host:        rtk.rtkdata.com (North America) / eu.rtkdata.com (Europe) / aus.rtkdata.com (Australia)
IP fallback: 13.56.117.10 / 3.73.41.96 / 54.206.56.130 (GeoSun: enter the IP first)
Port:        2101
Mountpoint:  AUTO (ALL CAPS)
Username:    from RTK Credentials, starts with "rtk"
Password:    from RTK Credentials
GGA:         required; connect outdoors after the scanner shows its own position
```

1. Give the scanner internet: app relay, phone hotspot, mobile data on the phone at the scanner, its own SIM or LTE modem, or the rover or drone.
2. Enter host, port `2101`, `AUTO` and your RTK credentials in the fields named in your scanner's guide.
3. Outdoors, wait for the scanner's own position, then connect.
4. Start and end the scan outdoors, and start recording only at your scanner's fix indicator.
5. Process in the regional datum that `AUTO` delivers, apply a geoid for heights above sea level, and check a control point.

## Related Guides

* [XGRIDS Lixel K1 / K2 / L2 Pro](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-k1-k2-l2-pro.md): LixelGO **RTK Settings**, the three connection modes and georeferencing in LixelStudio
* [XGRIDS Lixel L3](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-l3.md): the L3 with built-in RTK, its LixelGO settings and the local **IP** field in the connection wizard
* [FJD Trion P1 / P2 / S2](/integration-hub/lidar-scanners-and-mobile-mapping/fjd-trion-p1-p2-s2.md): the **Ntrip** card in Trion Scan, the phone hotspot and **GNSS Fusion** in Trion Model
* [CHCNAV RS10 / RS30](/integration-hub/lidar-scanners-and-mobile-mapping/chcnav-rs10-rs30.md): **RTK settings** in SmartGo Neo, tablet mobile data and RTK optimization in CoPre
* [3DMakerpro Eagle / Raven](/integration-hub/lidar-scanners-and-mobile-mapping/3dmakerpro-eagle-raven.md): the scanner **GPS** screen, **Link Hotspots** and **RTK Calibration** in RayStudio
* [Stonex X200GO / X120GO / X70GO](/integration-hub/lidar-scanners-and-mobile-mapping/stonex-x200go-x120go.md): GOapp **RTK Settings**, the RTK70 GO and RTK120 GO modules and **Payload Mode**
* [GreenValley LiGrip](/integration-hub/lidar-scanners-and-mobile-mapping/greenvalley-ligrip.md): the **RTK link** screen, **Phone Network** against **Host Network** and MAGNET Flow for Topcon and Sokkia
* [Emesent GX1](/integration-hub/lidar-scanners-and-mobile-mapping/emesent-gx1.md): the nano-SIM, the NTRIP profile in Commander and the base CRS in Aura
* [Emesent Hovermap RTK](/integration-hub/lidar-scanners-and-mobile-mapping/emesent-hovermap-backpack-vehicle-rtk.md): NTRIP on the Emlid, Trimble or Leica rover and the start order for Backpack and Vehicle RTK
* [Inertial Labs RESEPI / EchoONE](/integration-hub/lidar-scanners-and-mobile-mapping/inertial-labs-resepi-echoone.md): the **RTCM corrections** block in the web GUI, the USB LTE modem and the fix check on the **Status** page
* [GeoSun GS-200G / GS-100G](/integration-hub/lidar-scanners-and-mobile-mapping/geosun-gs-handheld.md): GeosunMeasure **RTK Settings** with the IP address for your region, and what GeoSun has published on the GS-203G so far
* [SkylandX MetaCam Air 2 / Air](/integration-hub/lidar-scanners-and-mobile-mapping/skylandx-metacam.md): **Enable RTK Account** in the MetaCam Go **RTK** tab, the manual IP address for the iPhone on the scanner Wi-Fi and **RTK** under **Optimizer** in MetaCam Studio
* [SHARE SLAM S20 / C1 Pro / S100](/integration-hub/lidar-scanners-and-mobile-mapping/share-slam-s20-c1-pro-s100.md): **RTK Account Switch** and **Edit Account** in SHARE Capture, the phone's mobile data on the scanner Wi-Fi and **GNSS Fusion** in SHARE PointClouds Studio
* [Georeferencing SLAM Scans](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): `AUTO` against the global mountpoints, WGS84 labels in scanner software, datum offsets and heights
* [NTRIP Server Settings](/get-started/network.md): the regional hosts, IP fallbacks and mountpoints used on this page
* [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why the scanner's position decides whether corrections arrive
* [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): the full table of regional datums that `AUTO` delivers
* [Understanding Heights](/get-started/understanding-heights.md): ellipsoidal and orthometric heights and how to apply a geoid model
* [Account & Credentials](/get-started/account-and-credentials.md): where to find *RTK Credentials* and how many devices can connect at once
* [Fix NTRIP Connection Issues](/support/common-connection-issues.md): what to check when the login works but no corrections arrive
* [Coverage Map](/get-started/coverage-map.md): check the reference station coverage for your site before the job
* [DJI Matrice 300 / 350 RTK](/integration-hub/drones-and-uavs/dji-matrice-300-350-m30t.md): RTKdata on the drone when the LiDAR payload uses the drone's RTK


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rtkdata.com/integration-hub/lidar-scanners-and-mobile-mapping.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.