> 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/stonex-x200go-x120go.md).

# Stonex X120GO RTK & X200GO Setup: NTRIP in GOapp

Connect Stonex X200GO, X120GO V2 and X70GO SLAM scanners to RTKdata: RTK Settings in GOapp, custom server, AUTO mountpoint, tablet hotspot and real fix checks.

The **Stonex X200GO** and **X120GO V2** are handheld SLAM laser scanners with built-in GNSS. To set up Stonex X120GO RTK or X200GO RTK with RTKdata, add RTKdata in the **Stonex GOapp** under **RTK Settings** as a custom NTRIP server, with the RTKdata host for your region, port `2101` and the `AUTO` mountpoint. The **X70GO** and the first-generation X120GO (V1) get RTK through a separate module, the **RTK70 GO** or **RTK120 GO**, which is set up in the same app. With a fixed RTK solution, GOapp can orient the real-time point cloud in your target coordinate system while you scan.

The built-in GNSS steps follow the current GOapp 2.10 screens. The RTK module steps follow the Stonex X70GO user guide (April 2025) and the first-generation X120GO user guide (February 2024). Screenshots in other Stonex manuals can look different.

Current app version when this page was written: Stonex GOapp 2.10.13 (September 2026).

These are the values you enter in GOapp, and the field names in bold match the app. Choose the server closest to your work area. All three servers share the same base station network; the difference is routing latency, see [NTRIP Server Settings](/get-started/network.md).

{% tabs %}
{% tab title="North America" %}

* **Host (domain)** in **Server Address**: `rtk.rtkdata.com`
* **Host (IP fallback)** in **Server Address**: `13.56.117.10`, only if the hostname does not connect
* **Port:** `2101`
* **Username / Password** in **Username** and **Password**: From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login
* **Mountpoint (ALL CAPS)** in **Mount Point**: `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`
  {% endtab %}

{% tab title="Europe" %}

* **Host (domain)** in **Server Address**: `eu.rtkdata.com`
* **Host (IP fallback)** in **Server Address**: `3.73.41.96`, only if the hostname does not connect
* **Port:** `2101`
* **Username / Password** in **Username** and **Password**: From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login
* **Mountpoint (ALL CAPS)** in **Mount Point**: `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`
  {% endtab %}

{% tab title="Australia" %}

* **Host (domain)** in **Server Address**: `aus.rtkdata.com`
* **Host (IP fallback)** in **Server Address**: `54.206.56.130`, only if the hostname does not connect
* **Port:** `2101`
* **Username / Password** in **Username** and **Password**: From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login
* **Mountpoint (ALL CAPS)** in **Mount Point**: `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`
  {% endtab %}
  {% endtabs %}

| Field                              | Value                                                                                                                                                    |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Label**                          | `RTKdata` (any name you like)                                                                                                                            |
| **Server Address** (North America) | `rtk.rtkdata.com`, IP fallback `13.56.117.10`                                                                                                            |
| **Server Address** (Europe)        | `eu.rtkdata.com`, IP fallback `3.73.41.96`                                                                                                               |
| **Server Address** (Australia)     | `aus.rtkdata.com`, IP fallback `54.206.56.130`                                                                                                           |
| **Port**                           | `2101`                                                                                                                                                   |
| **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                                                                                                        |
| **Mount Point**                    | `AUTO` (recommended), or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84`                                                                                  |

* Enter only the hostname in **Server Address**, without `http://` and without `:2101`. The port has its own field.
* Use the hostname first. The Stonex user guide shows a hostname in **Server Address** with a **Fixed** solution. Switch to the IP fallback only as described under *If the hostname does not connect* in the troubleshooting section.
* Enter the mountpoint in capitals, exactly as shown. **Automatic** under **Mount Point** in GOapp is a search mode, not the `AUTO` mountpoint.
* Type the username and password instead of pasting them, with no spaces at the start or end.
* One set of credentials allows one connection at a time. A second scanner or rover running at the same time needs its own data stream, see [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices).
* If the scanner was used with another correction service before, add a new **+ Custom** entry with these values and select it.

## Requirements

* **Stonex X200GO or X120GO V2** with the RTK bracket and GNSS antenna, or an **X70GO / X120GO V1** with the **RTK70 GO** or **RTK120 GO** module
* **Stonex GOapp 2.10.13** from the official store: **Stonex GOapp** in the Apple App Store or **GOapp** on Google Play, on Android 10 or later or iOS 13 or later. Do not install a GOapp APK file from a dealer download link: one such file is version 2.6.6, older than the first GOapp version with X200GO support (2.8.10).
* **Tablet or phone with a SIM and mobile data** that can share its connection as a Wi-Fi hotspot (X200GO, X120GO V2). A Wi-Fi-only iPad has no Personal Hotspot, and your mobile plan must allow hotspot use. Stonex asks for a SIM card in the tablet that does not need a username and password.
* **Nano-SIM without PIN** and with mobile data for the RTK module (X70GO, X120GO V1)
* **RTKdata account** with active RTK credentials (username starts with `rtk`)
* **RTKdata coverage** at your site: check the [coverage map](/get-started/coverage-map.md) before you go out
* **Open sky** for the first fix before you start scanning
* **GOpost** for post-processing runs only on Windows with an NVIDIA graphics card. Keep project paths free of special characters.

{% 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 XGO generation do you have?

The Stonex X200GO and X120GO V2 have built-in GNSS and are set up for RTKdata in GOapp under **RTK Settings**, while the X70GO and the first-generation X120GO (V1) need a separate RTK module with its own SIM card, set up in the GOapp tab **S-RTK**.

| Model                    | How to recognise it                                                                      | RTK hardware         | Where you enter RTKdata                |
| ------------------------ | ---------------------------------------------------------------------------------------- | -------------------- | -------------------------------------- |
| X200GO                   | Two 12 MP cameras, RTK bracket with GNSS antenna on the back of the scanner              | Built in             | GOapp: **Settings** > **RTK Settings** |
| X120GO V2                | Two 12 MP cameras, RTK bracket with GNSS antenna on the back of the scanner              | Built in             | GOapp: **Settings** > **RTK Settings** |
| X120GO V1 (2022 to 2024) | Three 5 MP cameras, separate RTK module with its own SIM                                 | **RTK120 GO** module | GOapp tab **S-RTK** > **CORS**         |
| X70GO                    | No RTK bracket on the scanner; the optional RTK70 GO module sits in a holder on the back | **RTK70 GO** module  | GOapp tab **S-RTK** > **CORS**         |

{% hint style="warning" %}
Copies of the 2024 X120GO user guide are easy to find online. It covers the first generation with the RTK120 GO module, the **APN** screen and the **S-RTK** tab. Those steps do not apply to the X120GO V2 or the X200GO: there is no APN field, and the SIM goes into the tablet, not into the scanner. The current Stonex guide is the [X200GO user guide Ver.1.4](https://files.tech4map.fr/Manuels/X200GO_UserGuide_ENG.pdf) (January 2026, PDF hosted by a Stonex dealer), which also covers the X120GO V2.
{% endhint %}

{% hint style="info" %}
An X120GO V1 in the backpack configuration with a **Stonex SC600+** receiver takes its corrections through the SC600+, not through GOapp. Enter the connection values above in the NTRIP client of the SC600+ web interface. Whether the SC600+ accepts the hostname is not documented; if it does not connect, use the IP fallback for your region from the tabs above.
{% endhint %}

## Where does the scanner get internet for RTK?

For the Stonex X200GO and X120GO V2, internet for RTKdata corrections comes from the tablet or phone that runs GOapp: the SIM card with mobile data goes into the tablet, not into the scanner, and the scanner is bound to the tablet's Wi-Fi hotspot. The X70GO and X120GO V1 get internet from a Nano-SIM in the RTK module instead.

{% tabs %}
{% tab title="X200GO / X120GO V2" %}

1. Put a SIM with mobile data into the tablet or phone. Check that it can share internet: a Wi-Fi-only iPad has no **Personal Hotspot**, and the mobile plan must allow hotspot use.
2. Turn on Bluetooth and the Wi-Fi hotspot on the tablet, and note the hotspot name and password. On an iPhone or iPad, turn on **Allow Others to Join** and, as a precaution, **Maximize Compatibility**. On Android, set the hotspot to the 2.4 GHz band as a precaution.
3. Open GOapp with the tablet online. Without internet, device activation can fail (**Device activation failed**).
4. Switch on the scanner: hold the power button for 3 seconds and wait about a minute.
5. In GOapp, tap **Add Now** (first start) or **+**, tap the Bluetooth symbol and select the scanner by its serial number.
6. In the scanner's Wi-Fi list under **Available**, choose the tablet's hotspot, not an office or site Wi-Fi. Enter the hotspot password and tap **Confirm**.
7. The scanner appears on the GOapp home screen with a green dot.

Next time, turn on the hotspot before you open GOapp and the scanner reconnects on its own. If you change the tablet or the hotspot, bind the scanner again.
{% endtab %}

{% tab title="X70GO / X120GO V1 (RTK module)" %}

1. Insert a Nano-SIM without PIN and with mobile data into the **RTK70 GO** or **RTK120 GO** module.
2. Mount the module in its holder on the back of the scanner, connect it to the scanner with the cable and attach the antenna.
3. Switch on the scanner. The module starts with it and its LEDs flash red.
4. Connect the tablet to the scanner over Wi-Fi. In GOapp, open the **S-RTK** tab at the bottom, tap **Disconnected** and pair the module over Bluetooth. The display changes to **Connected** or to the module serial number (`SRTK...`).
5. Open **APN**. On the **Access Point Names** screen, enter your carrier's APN and, if the carrier requires them, the SIM **Username** and **Password**. Tap **Save**.

The module's modem supports LTE FDD bands B1, B3, B5 and B8, LTE TDD bands B34, B38, B39, B40 and B41, and GSM 900/1800. It does not support B2, B4, B12, B13, B20, B28 or B66. Check that your carrier covers the site on the supported bands before you rely on the module.
{% endtab %}
{% endtabs %}

## How do you set up Stonex X120GO RTK in GOapp RTK Settings?

On a Stonex X200GO or X120GO V2, tap the scanner on the GOapp home screen, open **Settings** > **RTK Settings**, set **Device** > **Data link** to **Phone network**, add a **+ Custom** server with the RTKdata host for your region (for example `eu.rtkdata.com`) and port `2101`, enter your RTKdata username and password, select the `AUTO` mountpoint and tap **Save**; internet comes from the tablet's Wi-Fi hotspot. The RTK module (X70GO, X120GO V1) uses the same fields under **CORS**.

{% stepper %}
{% step %}

### Mount the GNSS antenna

On the X200GO and X120GO V2, screw the RTK bracket with the GNSS antenna onto the back of the scanner and plug the antenna cable into the scanner, red mark to red mark. Without this antenna the scanner has no RTK position.

On the X70GO and X120GO V1, the antenna connects to the RTK module, as described in the module tab of the internet section.
{% endstep %}

{% step %}

### Open the correction settings

{% tabs %}
{% tab title="X200GO / X120GO V2" %}

1. On the GOapp home screen, tap the scanner with the green dot. The standby page with **Start work** opens.
2. Tap the settings icon in the top right corner. **Settings** opens.
3. Choose **RTK Settings**.

In GOapp 2.10 the **Settings** list shows **Device Name**, **LiDAR**, **RTK Settings**, **Camera Params**, **Wi-Fi Settings**, **Format SSD**, **Point Cloud Display**, **Firmware** and **Usage Mode**.
{% endtab %}

{% tab title="X70GO / X120GO V1 (RTK module)" %}

1. In GOapp, open the **S-RTK** tab with the module connected.
2. Open **CORS**. The **CORS Settings** screen opens.
   {% endtab %}
   {% endtabs %}
   {% endstep %}

{% step %}

### Set the data link to Phone network

On the X200GO and X120GO V2:

1. In **RTK Settings**, open **Device**.
2. Set **Data link** to **Phone network**.
3. Tap the blue button to apply the setting.

The Stonex manuals do not show this step, and it is easy to miss. The RTKdata team confirmed it by working through the GOapp menu on the scanner.
{% endstep %}

{% step %}

### Add RTKdata as a custom server

1. Under **Connect Server**, open the list and choose **+ Custom** at the top.
2. In the **Custom** dialog, enter:
   * **Label:** `RTKdata`
   * **Server Address:** the host for your region, `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia)
   * **Port:** `2101`
3. Save with the round check-mark button at the bottom. The entry appears as a card in the list.

On the RTK module, the **CORS Settings** screen has the same **Connect Server** list and **Custom** dialog.
{% endstep %}

{% step %}

### Select the entry and enter your credentials

1. Select **RTKdata** under **Connect Server**. The line below it shows the host and port, for example `eu.rtkdata.com:2101`.
2. Enter **Username** and **Password** from *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). The username starts with `rtk`.
   {% endstep %}

{% step %}

### Select the AUTO mountpoint

**Automatic** under **Mount Point** is GOapp's search mode, not the RTKdata `AUTO` mountpoint. Use one of the two modes:

* **Automatic:** tap the grey bar with the `>` arrow. The **Mount Point** dialog loads the mountpoint list from the server. The list can show more entries than `AUTO`: select `AUTO` and confirm with the check mark. Do not use the blue button to the right of the bar: it only shows mountpoints you connected to before.
* **Manual:** switch to **Manual**, tap the grey bar and type `AUTO` exactly, in capitals. Use this mode if `AUTO` does not appear in the list.

{% hint style="info" %}
**AUTO needs your position.** The `AUTO` mountpoint chooses the base station from the device's position (NMEA GGA). Without GGA the device logs in successfully but receives no corrections, see [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). GOapp has no setting for this and Stonex does not document it, so there is nothing to switch on. Before you tap **Save**, wait outside with open sky until the scanner has a position of its own: the GNSS LED shows red, solid (Single solution) instead of red, flashing slowly (No positioning). After **Save**, stay outside and wait. If the status stays on **Single** although the hotspot has mobile data and the credentials are right, contact <support@rtkdata.com>.
{% endhint %}
{% endstep %}

{% step %}

### Save and check the settings

{% tabs %}
{% tab title="X200GO / X120GO V2" %}

1. Tap **Save**. GOapp shows **Operation successful**.
2. In the **Device State** box, check **Server Address** (your regional host with `:2101`, for example `eu.rtkdata.com:2101`), your **Username** and **Mount Point** `AUTO`.

**Differential Data: Normal** in the same box is not proof that corrections arrive, because GOapp shows it even when nothing is configured. Check the fix status as described in the next section.
{% endtab %}

{% tab title="X70GO / X120GO V1 (RTK module)" %}

1. Tap **Save**.
2. **Account Good** appears at the bottom of the screen. Wait until the main page shows **Fixed**, then start scanning.
3. The module stores its position on its own SD card, as a `.fmnav` file in the `Nav` folder. For GOpost, copy the file with the matching time stamp into the project folder, choose **New** and check the file in the **GNSS** row.

If the module loses the fix for a long time, open **CORS** again and tap **Save**.
{% endtab %}
{% endtabs %}
{% endstep %}
{% endstepper %}

## How do you know corrections are really arriving?

RTKdata corrections are really arriving on a Stonex X200GO or X120GO V2 when the GOapp standby page shows **Fixed** in the top right corner, or when the scanner's GNSS LED is solid green. **Differential Data: Normal** in **Device State** is not proof, because GOapp shows it even with no server, username or mountpoint set.

The standby page shows the solution and the satellite count in the top right corner:

| Status     | Meaning                        | What to do                                                                      |
| ---------- | ------------------------------ | ------------------------------------------------------------------------------- |
| **Single** | No corrections in use          | Check hotspot, mobile data, credentials and mountpoint, then tap **Save** again |
| **Float**  | Corrections arrive, no fix yet | Stay under open sky and wait                                                    |
| **Fixed**  | RTK fix                        | Hold it for at least one minute, then start the scan                            |

The first fix after switching on can take a while. Wait outside with a clear view of the sky before you change any setting.

GNSS LED on the scanner:

| GNSS LED               | Status                |
| ---------------------- | --------------------- |
| Green, solid           | Fixed solution        |
| Green, flashing slowly | Float solution        |
| Red, solid             | Single solution       |
| Blue, solid            | Pseudo-range solution |
| Red, flashing slowly   | No positioning        |
| Red, flashing fast     | No network            |

Tap the brackets icon `{ }` in the top right corner of **RTK Settings** to check whether correction data is being received.

{% hint style="info" %}
The RTKdata sourcetable loads without a login. A visible mountpoint list in the **Mount Point** dialog proves neither that your credentials are right nor that corrections are flowing (checked on 25 September 2026).
{% endhint %}

### Before and during the scan

* Stay in **Fixed** for at least one minute before you tap **Start work**. Only data in Fixed solution is used for orientation.
* Keep **Fixed** for at least 50% of the scan time. For mixed scans, scan at least 50% outdoors and capture outdoor areas before and after indoor sections.
* If the fix does not come back outdoors after an indoor section, open **Settings** > **RTK Settings** and save the **Mount Point** again. On the RTK module, open **CORS** and save again.
* After you stop the scan, wait about 1/25 of the scan time before switching off, longer with **Real-time Orientation**, so the scanner can finish the real-time point cloud. Then hold the power button until all indicators are off.
* SLAM needs geometry. Stonex asks for geometric elements within a 50 m range and does not recommend environments that are too open. A fixed RTK solution does not replace that geometry.

## Which projection settings should you use with AUTO?

With the RTKdata `AUTO` mountpoint, match the mountpoint to the GOapp **Target Projection**: keep `AUTO` for a regional target system, because it delivers your region's local datum, and use `AUTO_WGS84` only when the target is a `WGS 84 / UTM zone` system and the result should stay global.

`AUTO` delivers, for example, NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe and GDA2020 in Australia. `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver ITRF2020 and ITRF2014 at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) in the middle of the current year. The datum for every region is listed in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md).

To orient the real-time point cloud:

1. Tap **Start work**. On **Job Configuration**, set **Real-time Orientation** to active instead of **Disable**. GOapp notes: "The real-time orientation function needs to be used in conjunction with RTK". Older manuals show this setting as a switch.
2. On the **Real-time Orientation** page, fill in **Source Projection** (Stonex's screenshot shows `WGS`) and **Target Projection** (for example a `WGS 84 / UTM zone` system). If a value is missing, GOapp shows **Some parameters are missing. Please configure all projection parameters.**
3. Tap **Confirm** on **Job Configuration**.
4. **Parameter Initializing...** appears with the countdown **The remaining time of still**. Hold the scanner still and keep people and objects from moving in front of it.

{% hint style="warning" %}
**Check the datum on your first project.** GOapp labels the source as `WGS`, while `AUTO` delivers your region's local datum. Stonex does not document whether GOapp applies a transformation between **Source Projection** and **Target Projection**. Match the mountpoint to the target system (`AUTO` for a regional system, `AUTO_WGS84` for `WGS 84 / UTM zone`) and check a known control point on the first project before you rely on the result. A consistent offset of 50 cm to 1 m against local survey control usually means a datum mismatch, see [Why Your Coordinates May Be Offset](/get-started/coordinate-systems-and-datums.md#why-your-coordinates-may-be-offset).
{% endhint %}

To check a control point, align the cross in the centre of the scanner base with the point. During the scan, tap **Add GCP** in GOapp, or press the control point button on the side of the handle (not the power button) and wait for the beep. GOapp marks each collected point with a yellow square along the motion track. Compare the point in the processed point cloud with its known coordinates. If you measure those coordinates yourself with an RTKdata rover, use the same mountpoint as for the scan.

{% hint style="info" %}
**Heights are ellipsoidal.** RTKdata delivers ellipsoidal heights, and the GOapp orientation page has no geoid field. Apply the geoid in your downstream software and check a height benchmark on the first project. See [Understanding Heights](/get-started/understanding-heights.md).
{% endhint %}

For the RTK module (X70GO, X120GO V1), Stonex states that GOpost asks for the coordinate type and reference system when you import the module's `.fmnav` file, and orients the point cloud in the reference system of the RTK data. The mountpoint therefore sets the frame of the point cloud. For built-in GNSS data (X200GO, X120GO V2), Stonex does not document this.

For the frame questions that all SLAM scanners share, see [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md).

## How does RTK work with the X200GO on a drone?

On a drone, the Stonex X200GO runs in **Payload Mode** and uses the drone's RTK data, so RTKdata is set up in the drone controller (for example DJI Pilot 2 on a Matrice 300 or 350 RTK), not in GOapp **RTK Settings**. Whether the drone passes those corrections on to the scanner has not been confirmed yet.

1. Connect the drone to its controller and set the RTK corrections in the drone interface. For RTKdata in DJI Pilot 2 on a Matrice 300 RTK or 350 RTK, see [DJI Matrice 300 / 350 RTK & M30T](/integration-hub/drones-and-uavs/dji-matrice-300-350-m30t.md).
2. In GOapp, open **Settings** > **Usage Mode** and choose **Payload Mode**.
3. When you tap **Start work**, deselect **Real-time Orientation**. The scanner uses the drone's RTK data.
4. In GOpost, choose the platform **UAV mount**.

* The Stonex user guide describes drone data collection for both the X200GO and the X120GO, while the GOapp changelog names Payload Mode support for the X200GO.
* The X200GO brochure (February 2026) lists DJI M300/350 with RTK. For the [DJI M400](/integration-hub/drones-and-uavs/dji-matrice-400.md) it lists PPK, not RTK.
* During the flight, especially far from the takeoff point, the scanner can lose its connection to GOapp and the preview disappears. Stonex states that data is still recorded correctly. After landing, reconnect and stop the scan.

{% hint style="warning" %}
**Check the first flight.** Compare the point cloud with known control points before you rely on RTK positions from the drone.
{% endhint %}

## Troubleshooting

| Problem                                                                            | Cause                                                                                                                                                             | Fix                                                                                                                                                                                                                                                                                                                                                        |
| ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Status stays **Single**, GNSS LED red and flashing fast (No network)               | No internet: hotspot off, no mobile data, or the scanner joined another Wi-Fi                                                                                     | Check mobile data and hotspot on the tablet, turn the hotspot on before opening GOapp, and bind the scanner to the tablet hotspot again                                                                                                                                                                                                                    |
| **Differential Data: Normal**, but the status stays **Single**                     | The badge does not show incoming corrections                                                                                                                      | Tap the brackets icon `{ }` in the top right corner of **RTK Settings** to check whether correction data is being received. Check **Device State** for your regional host with `:2101`, your username and `AUTO`, re-type the credentials from *RTK Credentials* and tap **Save**                                                                          |
| Status stays **Single** although internet and settings are right                   | Possibly no position (GGA) reaching the caster, the hostname not connecting, or an account issue                                                                  | Stay outside with open sky for a few minutes. If nothing changes, try the IP fallback as described below, then contact <support@rtkdata.com>                                                                                                                                                                                                               |
| No mountpoint selected because **Automatic** looked like `AUTO`                    | **Automatic** is GOapp's search mode, not the `AUTO` mountpoint                                                                                                   | Tap the grey bar and select `AUTO`, or switch to **Manual** and type `AUTO`, then **Save**                                                                                                                                                                                                                                                                 |
| Old or unknown mountpoints in the list                                             | The blue button shows earlier connections                                                                                                                         | Tap the grey bar instead and select `AUTO`, then **Save**                                                                                                                                                                                                                                                                                                  |
| No connection with `:2101` or `http://` in **Server Address**                      | Port or protocol typed into the address field                                                                                                                     | Enter only the host, for example `eu.rtkdata.com`, in **Server Address** and `2101` in **Port**                                                                                                                                                                                                                                                            |
| No fix after an indoor section                                                     | The correction link may not recover by itself                                                                                                                     | Open **Settings** > **RTK Settings** and save the **Mount Point** again (RTK module: save **CORS** again)                                                                                                                                                                                                                                                  |
| Real-time point cloud not georeferenced                                            | **Real-time Orientation** left on **Disable**, or the scanner was switched off too early                                                                          | Enable it on **Job Configuration**, and after stopping wait about 1/25 of the scan time before switching off                                                                                                                                                                                                                                               |
| **Some parameters are missing. Please configure all projection parameters.**       | Projection settings incomplete                                                                                                                                    | Fill in **Source Projection** and **Target Projection**, then tap **Confirm**                                                                                                                                                                                                                                                                              |
| Heights tens of metres off                                                         | Ellipsoidal heights, no geoid applied                                                                                                                             | Apply a geoid model, see [Understanding Heights](/get-started/understanding-heights.md)                                                                                                                                                                                                                                                                    |
| Point cloud distorted although the status was **Fixed**                            | Too little geometry within 50 m for SLAM                                                                                                                          | Scan where walls, buildings or other structures are within range. RTK does not replace SLAM geometry.                                                                                                                                                                                                                                                      |
| Status stays **Single** at a site without mobile coverage                          | Without mobile data, no corrections reach the scanner                                                                                                             | Collect control points during the scan with **Add GCP** or the control point button, and match them with their known coordinates in GOpost to georeference the scan                                                                                                                                                                                        |
| **Fixed**, but positions a few centimetres off known points                        | RTK accuracy drops with the distance to the base station. Stonex specifies the built-in GNSS at 0.8 cm + 1 ppm horizontal and 1.5 cm + 1 ppm vertical (RTK, RMS). | Check the station coverage at your site on the [coverage map](/get-started/coverage-map.md) and see [Accuracy Expectations](/get-started/accuracy-expectations.md). A steady offset of 50 cm to 1 m usually means a datum mismatch instead, see [Which projection settings should you use with AUTO?](#which-projection-settings-should-you-use-with-auto) |
| Corrections stop when a second 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).                                                                                                                                                                                                   |
| **Device activation failed**                                                       | GOapp opened without internet                                                                                                                                     | Open GOapp with the tablet online                                                                                                                                                                                                                                                                                                                          |
| RTK module has no network                                                          | SIM with PIN, APN missing, or LTE band not supported                                                                                                              | Remove the PIN, enter the APN under **APN**, and check coverage on the supported bands                                                                                                                                                                                                                                                                     |
| GOpost: **Path not supported, please make sure no special character is included!** | Special characters, for example umlauts, in the project path                                                                                                      | Use a short path such as `C:\scans\project01`                                                                                                                                                                                                                                                                                                              |

### If the hostname does not connect

GOapp takes a hostname in **Server Address**, and an IP address works as well. Keep the hostname for your region whenever it connects. Use the IP fallback only if the status stays on **Single** although the hotspot has mobile data and the credentials and mountpoint are right: add a second **+ Custom** entry with the IP for your region in **Server Address** and keep port, credentials and mountpoint.

| Region        | Hostname (preferred) | IP fallback for **Server Address** | **Port** | **Mount Point** |
| ------------- | -------------------- | ---------------------------------- | -------- | --------------- |
| North America | `rtk.rtkdata.com`    | `13.56.117.10`                     | `2101`   | `AUTO`          |
| Europe        | `eu.rtkdata.com`     | `3.73.41.96`                       | `2101`   | `AUTO`          |
| Australia     | `aus.rtkdata.com`    | `54.206.56.130`                    | `2101`   | `AUTO`          |

For connection problems that are not specific to the XGO scanners, see [Common Connection Issues](/support/common-connection-issues.md).

## Frequently asked questions

### Does the Stonex X120GO V2 need a SIM card for RTK?

Not in the scanner. The X120GO V2 gets internet for RTKdata corrections from a SIM with mobile data in the tablet or phone that runs GOapp, and the scanner is bound to that device's Wi-Fi hotspot. Only the first-generation X120GO (V1) and the X70GO use a SIM, inside the RTK120 GO or RTK70 GO module.

### Why does GOapp show Differential Data: Normal but the scanner stays on Single?

**Differential Data: Normal** does not mean that corrections are arriving: GOapp shows it even when no server, username or mountpoint is set. Only **Fixed** on the standby page or a solid green GNSS LED confirms RTK. To check whether correction data is being received at all, tap the brackets icon `{ }` in the top right corner of **RTK Settings**. If the scanner stays on **Single**, check the hotspot and mobile data, re-type the RTKdata credentials, confirm `AUTO` in **Device State** and tap **Save** again.

### How do I set up NTRIP on the Stonex X200GO in GOapp?

Tap the X200GO on the GOapp home screen, open **Settings** > **RTK Settings**, set **Device** > **Data link** to **Phone network** and apply it with the blue button, add a **+ Custom** entry under **Connect Server** with **Server Address** set to the RTKdata host for your region (`rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com`) and **Port** `2101`, select it, enter your RTKdata **Username** and **Password**, tap the grey **Mount Point** bar and select `AUTO` (**Automatic** is GOapp's search mode, not the `AUTO` mountpoint), and tap **Save**. Internet comes from the tablet's Wi-Fi hotspot, with the scanner bound to it.

### Is Automatic under Mount Point the same as the AUTO mountpoint?

No. **Automatic** is GOapp's search mode for the **Mount Point** field: tapping the grey bar loads the mountpoint list from the server. `AUTO` is the RTKdata mountpoint you select in that list, or type in capitals in **Manual** mode.

### How long should the X200GO stay fixed before I start scanning?

At least one minute. Before you start scanning with RTKdata corrections, stay in **Fixed** for at least one minute. Stonex asks for this and for at least 50% of the scan time in **Fixed**, because only data in Fixed solution is used for orientation.

### Which RTK corrections does the X200GO use in payload mode?

In **Payload Mode** the X200GO uses the drone's RTK data, so RTKdata is set up in the drone controller (see the [DJI Matrice 300 / 350 guide](/integration-hub/drones-and-uavs/dji-matrice-300-350-m30t.md)), not in GOapp **RTK Settings**. Stonex says to deselect **Real-time Orientation**. Whether those corrections reach the payload has not been confirmed yet. For the [DJI M400](/integration-hub/drones-and-uavs/dji-matrice-400.md), the X200GO brochure lists PPK instead of RTK.

## Quick reference

1. Tablet: SIM with mobile data, hotspot on (2.4 GHz as a precaution), GOapp 2.10.13 from the store, scanner bound to the hotspot.
2. **Settings** > **RTK Settings** > **Device** > **Data link**: **Phone network** (blue button), then **Connect Server** > **+ Custom**: **Server Address** `rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com` (IP fallback `13.56.117.10`, `3.73.41.96` or `54.206.56.130`), **Port** `2101`, round check mark.
3. **Username** and **Password** from *RTK Credentials*, **Mount Point** `AUTO` (grey bar or **Manual**), **Save**.
4. Wait outside for **Fixed** (not **Differential Data: Normal**), hold it one minute, then **Start work** with **Real-time Orientation** enabled.
5. RTK module (X70GO, X120GO V1): Nano-SIM without PIN, **S-RTK** > **APN**, then **CORS** with the same values until **Account Good**.

## Related Guides

* [LiDAR & SLAM Scanner RTK Setup](/integration-hub/lidar-scanners-and-mobile-mapping.md): all LiDAR scanner and mobile mapping guides with the shared connection settings
* [NTRIP Server Settings](/get-started/network.md): the regional hosts, IP fallbacks, port and mountpoints in one reference
* [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why the caster needs your position before it sends corrections
* [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which datum `AUTO` and its variants deliver in each region
* [Understanding Heights](/get-started/understanding-heights.md): ellipsoidal and orthometric heights, and how to apply a geoid
* [Account & Credentials](/get-started/account-and-credentials.md): where to find your RTK credentials and how many devices can connect at once
* [Common Connection Issues](/support/common-connection-issues.md): what to check when corrections do not arrive or the fix stays on Float
* [Coverage Map](/get-started/coverage-map.md): check the station coverage at your site before you go out
* [Accuracy Expectations](/get-started/accuracy-expectations.md): the accuracy to expect from RTK corrections at your distance to the nearest base station
* [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): matching the datum of RTK positions, control points and the processing project for SLAM scans
* [Stonex S980A / S900A](/integration-hub/gnss-rovers-and-receivers/stonex-s980a-s900a.md): RTKdata setup for Stonex GNSS receivers in Cube-a and the receiver web interface
* [DJI Matrice 300 / 350 RTK & M30T](/integration-hub/drones-and-uavs/dji-matrice-300-350-m30t.md): RTKdata in DJI Pilot 2, for the drones the X200GO brochure lists for Payload Mode with 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/stonex-x200go-x120go.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.