> 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/chcnav-rs10-rs30.md). # CHCNAV RS10 RTK Setup (RS30): NTRIP in SmartGo Neo Connect the CHCNAV RS10 and RS30 SLAM scanners to RTKdata NTRIP: RTK settings in SmartGo Neo, Type CORS, AUTO source list, tablet mobile data and CoPre datum. To get CHCNAV RS10 RTK corrections from RTKdata, you enter the NTRIP login in the Android app **SmartGo Neo**. The **CHCNAV RS10** is a handheld SLAM laser scanner with a built-in GNSS RTK receiver. CHCNAV lists it as **RS10 (16 lines)** and **RS10 (32 lines)**, and dealers sell the 32-line version as the **RS30**. Both versions are operated from SmartGo Neo. With a fixed RTK solution during capture, CHCNAV's post-processing software CoPre uses the RTK positions to optimize the SLAM trajectory, so the point cloud gets absolute coordinates instead of a relative frame. The NTRIP connection runs over the mobile data of the tablet or phone that runs SmartGo Neo. | Field | Value | | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Type** | `CORS` | | **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` | | **User name** | 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 the same *RTK Credentials* page | | **Source list** (mountpoint) | `AUTO` in ALL CAPS (alternatives: `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84`) | | **Use Broadcast RTCM** | Off | | NMEA GGA | No switch. SmartGo Neo sends the scanner position itself, so tap **Connect** only after the status bar shows satellites and **Single** | Pick the server closest to your work area. All three servers share the same base station network, see [NTRIP Server Settings](/get-started/network.md). Enter the host name first. The IP address is only a fallback for when SmartGo Neo cannot resolve the host name, see [If the server address does not resolve](#if-the-server-address-does-not-resolve). ## What do you need to connect a CHCNAV RS10 or RS30? To connect a CHCNAV RS10 or RS30 to RTKdata, you need the scanner, an Android tablet or phone with SmartGo Neo and working mobile data, and your RTKdata RTK credentials. * **CHCNAV RS10** (16 lines) or **RS30** (RS10, 32 lines), charged, and a clear view of the sky for the RTK part of the setup * **Android tablet or phone:** the supplied **LT800** tablet (Android 12, dual-SIM 4G) with a data SIM, or your own Android phone with Android 7.0 or later. There is no iOS app. * **SmartGo Neo** from Google Play (version 1.5.6.1 from 14 July 2026, listed for "all CHC Navigation SLAM devices"), or **SmartGo 1.5.5** from your dealer. Both show the same RTK settings screen. * **Mobile data** on that tablet or phone, see the next section * **RTKdata account** with active RTK credentials (username starts with `rtk`). One set of credentials allows one connection at a time, so every device 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). * **Coverage** in your work area: check it on the [Coverage Map](/get-started/coverage-map.md) before the job. * **Firmware:** CHCNAV's support portal lists `RS10_v1.9.3` as the current RS10 firmware. CHCNAV does not document a minimum firmware for CORS. SmartGo Neo shows the firmware version once it is connected to the scanner. * **Device authorization** on rental and demo units: check **Device authorization status** in SmartGo Neo before the job, with internet on the tablet. An expired authorization shows **The device authorization has expired.** and blocks projects. * **CoPre 2** for post-processing, on a PC with an NVIDIA graphics card ("Only NVIDIA is supported, GTX1050ti and above") and at least 16 GB RAM (64 GB recommended) This page covers the RS10 in SmartGo Neo. CHCNAV GNSS rovers such as the i93 or i90 are set up in LandStar 8 instead, see [CHC i93 / i90 / X7](/integration-hub/gnss-rovers-and-receivers/chc-i93-i90.md). That guide does not cover the RS10, and a LandStar route for the RS10 is not documented here. {% 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 %} ## Why does the tablet need mobile data while it is on the scanner Wi-Fi? The tablet needs mobile data because its Wi-Fi is connected to the CHCNAV RS10's own network `SLAM-XXXXX`, which has no internet access, so the NTRIP connection to RTKdata can only run over the mobile data of the tablet or phone. {% hint style="warning" %} **Internet path for RTK with the RS10** * The LT800 tablet (with a data SIM) or your Android phone joins the scanner Wi-Fi `SLAM-XXXXX`. That network has no internet. * NTRIP therefore needs the mobile data of the tablet or phone. Turn on mobile data, and data roaming if you use a foreign SIM. * CHCNAV's product FAQ mentions 4G for the RS10, but the RS10 user manual lists no SIM slot on the scanner (on/off button, Type-C port, battery compartment, handle and range pole hole), so the data SIM for RTKdata NTRIP goes into the LT800 tablet or your phone. * A phone hotspot is not an option, because the tablet's Wi-Fi is already taken by the scanner. * A SIM that shows signal but has no data gives no connection. Before the job, open a web page on the tablet while it is connected to `SLAM-XXXXX`. * The LT800 datasheet does not list LTE bands 13, 14, 66 and 71, which several North American networks rely on. In the US and Canada, choose a SIM that works on the bands the LT800 supports, or use your own Android phone. {% endhint %} ## How do you fill in CHCNAV RS10 RTK settings in SmartGo Neo? You fill in the CHCNAV RS10 RTK settings in SmartGo Neo under **Start capture** > settings icon > receiver icon > **RTK settings**: switch on **RTK enabled**, set **Type** to **CORS**, enter the RTKdata host for your region (`rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com`), port `2101` and your RTK credentials, and choose `AUTO` from the downloaded source list. Current app version when this page was written: SmartGo Neo 1.5.6.1 (July 2026). CHCNAV's RS10 user manual from April 2024 shows an older version of this screen, for example **Use RTK or not** instead of **RTK enabled**. {% stepper %} {% step %} ### Power on the RS10 and join its Wi-Fi 1. Hold the **ON/OFF key** for 5 seconds. The green LED blinks during the self-check and stays solid green when the scanner is ready. 2. On the tablet or phone, open the Android Wi-Fi settings and join `SLAM-XXXXX` (XXXXX are the last five characters of the serial number). There is no password. 3. After 5 to 10 seconds Android reports **Can't connect to the internet**. Do not tap any option in that notice. Go back and close it. 4. Open SmartGo Neo, check the scanner under **Wi-Fi name:** (SmartGo 1.5.5: **WiFi name:**) and tap **Connect device**. If the Wi-Fi name shows as unknown, turn on Android location services and connect again. If the connection to the scanner fails, SmartGo Neo asks you to turn off mobile data (**Please check and confirm that the mobile cellular network is turned off.**). Do that only to get the scanner connected, then continue with the next step. {% endstep %} {% step %} ### Turn mobile data back on 1. Turn mobile data on again while the Wi-Fi stays connected to `SLAM-XXXXX`. 2. Open a web page in the browser to confirm that the tablet has internet. 3. If SmartGo Neo still reports no internet with mobile data on, choose **Forget network** for `SLAM-XXXXX` in the Android Wi-Fi settings and join it again. Without mobile data, SmartGo Neo shows **Please open the mobile network.** {% endstep %} {% step %} ### Open RTK settings 1. Tap **Start capture**. The status bar at the top shows the satellite count and the solution status, for example **Single**. 2. Tap the settings icon at the top right. CHCNAV's April 2024 RS10 manual shows it as a slider icon, a July 2026 dealer tutorial for SmartGo Neo as a small gear. 3. In the icon column on the left, tap the receiver (rover) icon. **RTK settings** opens. The icons in this window have no text labels. {% endstep %} {% step %} ### Enable RTK and choose Type CORS 1. Switch on **RTK enabled** (called **Use RTK or not** in the April 2024 manual) and confirm **Please confirm whether to use RTK?**. 2. Set **Type** to **CORS**. 3. Do not choose **Huace CORS**, **Qianxun CORS**, **One-Click fixed**, **APIS**, **RTK** or **Single base station (Direct IP)**. They belong to other correction services or to a direct link with a base or receiver, not to an NTRIP caster login such as RTKdata. The type can only be changed while the correction link is disconnected. Otherwise SmartGo Neo shows **Please disconnect the differential connection, and then switch the service type.** {% hint style="info" %} **GeoCue TrueView GO 116S / 132S:** GeoCue's TrueView GO user guide also describes a CORS login under RTK settings. If your GeoCue app lists **GeoCue CORS** under **Type**, choose **CORS** for RTKdata NTRIP, not **GeoCue CORS**. {% endhint %} {% endstep %} {% step %} ### Enter server, port and credentials Select the tab for your region and enter the values directly in the fields of the **RTK settings** screen: {% tabs %} {% tab title="North America" %} * **Host (domain):** `rtk.rtkdata.com`, in **Server address** * **Host (IP fallback):** `13.56.117.10`, in **Server address** only if SmartGo Neo reports **Server address resolution error, please check and try again.** although the tablet has internet * **Port:** `2101`, in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, in **User name** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, in **Source list** after **Download source list** (next step) {% endtab %} {% tab title="Europe" %} * **Host (domain):** `eu.rtkdata.com`, in **Server address** * **Host (IP fallback):** `3.73.41.96`, in **Server address** only if SmartGo Neo reports **Server address resolution error, please check and try again.** although the tablet has internet * **Port:** `2101`, in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, in **User name** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, in **Source list** after **Download source list** (next step) {% endtab %} {% tab title="Australia" %} * **Host (domain):** `aus.rtkdata.com`, in **Server address** * **Host (IP fallback):** `54.206.56.130`, in **Server address** only if SmartGo Neo reports **Server address resolution error, please check and try again.** although the tablet has internet * **Port:** `2101`, in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login, in **User name** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, in **Source list** after **Download source list** (next step) {% endtab %} {% endtabs %} Notes on the fields: * **Server address** takes a host name. CHCNAV's RS10 manual shows one in this field with a running transmission. Pick the server closest to your work area, see [NTRIP Server Settings](/get-started/network.md). * **Port:** CHCNAV's manual says the port must match the coordinate system you want. That note applies to CHCNAV's and Qianxun's own services. With RTKdata the port is always `2101`, and the mountpoint sets the reference frame. * **User name** accepts up to 30 characters. Type the credentials instead of pasting them, and make sure there is no space at the start or end. {% hint style="warning" %} Do not add the server through **Server Mgmt** > **Add server**. Whether that dialog stores a host name is not documented, and the **IP:** shown in its **Server list** is only a display label. Typing the host name into **Server address** on the RTK settings screen is the documented way. {% endhint %} {% endstep %} {% step %} ### Download the source list and choose AUTO 1. Tap **Download source list**. If a correction link is running, SmartGo Neo disconnects it first (**Get source list will break the connection first, sure to get the source list.**). 2. Open **Source list** and choose `AUTO`. The search icon filters the list. The list can show further entries, and `AUTO` is the one this documentation covers. 3. Choose `AUTO_ITRF2020`, `AUTO_ITRF2014` or `AUTO_WGS84` only if your project needs a fixed global frame, see the CoPre section below. Without a downloaded list, SmartGo Neo reports **Please select mount point from the source table.** {% hint style="info" %} The RTKdata sourcetable loads without a login. **Get source list successfully** and a visible mountpoint list therefore prove neither that your credentials are correct nor that corrections are flowing (checked on 25 September 2026). The credentials are only checked when you tap **Connect**. {% endhint %} {% endstep %} {% step %} ### Leave Use Broadcast RTCM off Keep **Use Broadcast RTCM** switched off. The option waits for the coordinate system messages RTCM 1021 to 1027, which RTKdata does not send (**Please wait to receive the network RTCM coordinate system.**). 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). {% endstep %} {% step %} ### Connect outdoors and wait for Fixed 1. Stay outdoors until the status bar shows satellites and **Single**. 2. Tap **Connect**. 3. SmartGo Neo shows **Differential data transmission in progress.**, and the solution status moves from **Single** through **Float** to **Fixed**. Wrong credentials only show up at this point, for example as **Incorrect username or password** or **Authentication failed**. {% hint style="warning" %} The `AUTO` mountpoint needs the scanner's position (NMEA GGA) to choose the nearest base station. A connection without a position logs in successfully but receives no corrections, see [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). SmartGo Neo has no GGA switch, because the app sends the device position itself. If the scanner has no position yet, SmartGo Neo reports **No device location information. Please check if the device is connected and can search for stars normally.** Wait outdoors for satellites and **Single**, then tap **Connect** again. {% endhint %} {% endstep %} {% endstepper %} ## How do you check the fix before you start capture? Before you start a CHCNAV RS10 project, check that SmartGo Neo shows **Differential data transmission in progress.** and the solution status **Fixed**, because the RTK settings cannot be changed once capture is running. * **Set up RTK first.** During capture, SmartGo Neo blocks changes with **Unable to switch while capturing.** (for **Use Broadcast RTCM**: **Modification not allowed while capturing.**). * **Start the project at Fixed.** Tap the round button on the left, enter a **Project name** made of letters and digits, and confirm with **OK**. Choose a scene with satellite reception, such as **Outdoor**, and hold the scanner still for about 2 seconds while it initializes. * **Watch the solution during capture.** Keep an eye on **GNSS solution** and **Differential age**. CoPre can only use the RTK positions where the real-time solution was valid, see the CoPre section below. * **Use SmartGo Neo, not One-Key mode.** In One-Key mode, started with the key on the scanner only, there is no CORS login. * **Record control points** with **Add control Points** if you want to check the absolute accuracy later. In pole mode, enter the pole height. ## When do you still need loops with RTK? With the CHCNAV RS10 and RTKdata corrections, RTK replaces loops only when more than 70% of the scan area has good GNSS reception. Everywhere else, CHCNAV's operating procedure requires a loop once the trajectory goes beyond 300 m, with an overlap of more than 20%. * **Open areas with good reception on more than 70% of the area:** the RS10 calibrates SLAM position and attitude with RTK in real time, and no loop is needed. * **Underground parking, urban canyons, forestry and built-up areas:** no loop within 300 m, a loop is required beyond 300 m, and the loop should overlap by more than 20%. * **Short GNSS dropouts:** users report visible drift after the scanner lost GNSS for only a few seconds, for example on long road scans. Where the sky is blocked, walk loops even with RTK and check the result at a control point. Field practice reported by users is a loop every 30 to 60 m where GNSS drops out, and a loop every few hundred feet on road corridors. ## How do you get georeferenced coordinates in CoPre? You get georeferenced coordinates from a CHCNAV RS10 scan with RTKdata by creating the CoPre task with **Projected Coordinate System**, choosing the EPSG system of the regional datum that the `AUTO` mountpoint delivers, for example ETRS89 / UTM in Europe, NAD83(2011) State Plane in the USA, NAD83(CSRS) / UTM in Canada or GDA2020 / MGA in Australia, and running **RTK POS Optimization**. 1. Switch the RS10 off, connect it by USB-C and copy the project folders to the PC. Use a folder path with English characters only and no spaces. If the scanner is switched on, the PC does not show it as a drive. 2. Create a task (**Create**). In the coordinate system window, choose **Projected Coordinate System**, not **Relative Coordinate System**. 3. Under **Standard Coord System**, search by EPSG for the system that matches your mountpoint, for example an ETRS89 / UTM zone in Europe, a NAD83(2011) State Plane zone in the USA or a NAD83(CSRS) / UTM zone in Canada with `AUTO`. In the USA, pick the State Plane variant with the unit your project uses, see [US Survey Feet vs. International Feet](/get-started/coordinate-systems-and-datums.md#us-survey-feet-vs-international-feet). 4. For heights above the geoid, set a **Geoid model**. 5. Open **Optimize Data** (or **Main View** > **SLAM Processing** > **Optimize Accuracy**), select the projects and choose **RTK POS Optimization** in **Step 2 GNSS Trajectory Optimization**. If you use ground control, also enable **Use TGCP for Trajectory Optimization**. 6. Check the result at a control point that is in the same coordinate system as the task and the mountpoint. Current app version when this page was written: CoPre 2.11.1 (July 2026). CoPre's December 2023 manual and the April 2024 RS10 manual use older labels for the optimization step, such as **Load Real-Time Data** and **Auto Accuracy Optimization**. Choose **Standard Coord System** rather than **Customize Coord System** where you can: according to CoPre's manual, EPSG information is only recorded under a standard coordinate system. For the datum logic that applies to all SLAM scanners, see [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md). {% hint style="warning" %} **Datum in CoPre with RTKdata AUTO** * `AUTO` delivers the regional datum for the scanner's position, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe and GDA2020 in Australia. Regions without their own entry get WGS84(G2139) at the mid-year epoch. The full list per country is in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md). * In CoPre, pick the matching regional system under **Standard Coord System**, for example ETRS89 / UTM, NAD83(2011) State Plane, NAD83(CSRS) / UTM or GDA2020 / MGA. * `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver ITRF2020 and ITRF2014 at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) at the mid-year epoch. Use these global mountpoints only together with a WGS84-based coordinate system in CoPre. * CoPre allows one coordinate system per task. Scans made with different mountpoints go into separate tasks. * CoPre's manual does not say whether CoPre applies its own datum transformation when you pick an EPSG system. Check the first project at a known control point. A steady offset of 50 cm to 1 m against local control usually points to a datum mismatch, see [Why Your Coordinates May Be Offset](/get-started/coordinate-systems-and-datums.md#why-your-coordinates-may-be-offset). * Keep **Use Broadcast RTCM** off. CoPre cannot process RTCM projects and normal SLAM projects in the same task. {% endhint %} {% hint style="warning" %} If the real-time RTK is not valid, **RTK POS Optimization** processes the scan in pure SLAM mode without an error message. The point cloud then has no reliable absolute position. Watch **GNSS solution** and **Differential age** during capture, and check a control point after processing. For a scan without valid RTK, CoPre offers **PPK POS Optimization** with base station observation data (RINEX 3.02 or later, antenna height reduced to the phase center), or ground control with **Use TGCP for Trajectory Optimization**. See [Is RTK or PPK better for a handheld SLAM scanner?](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md#is-rtk-or-ppk-better-for-a-handheld-slam-scanner). {% endhint %} {% hint style="info" %} RTKdata corrections deliver **ellipsoidal heights**, not heights above mean sea level. Set a **Geoid model** in the CoPre task if you need orthometric heights, and check the height at a control point. See [Understanding Heights](/get-started/understanding-heights.md). {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Server address resolution error, please check and try again.** | The tablet cannot resolve the host name, usually because it has no internet | Check mobile data by opening a web page. If the error stays while the tablet has internet, enter the IP fallback for your region, see below. | | **Please open the mobile network.** | Mobile data is off on the tablet or phone | Turn mobile data on. The Wi-Fi stays on `SLAM-XXXXX`. | | SmartGo Neo reports no internet although mobile data is on | Android Wi-Fi connection to the scanner | Choose **Forget network** for `SLAM-XXXXX`, join it again, and close **Can't connect to the internet** without tapping an option. | | **Get source list successfully**, then **Incorrect username or password** or **Authentication failed** on **Connect** | Most likely wrong credentials. The source list loads without a login. | Use the username and password from *RTK Credentials*, not your website login. Type them, with no space at the start or end. **Clear account** deletes saved credentials. | | **Please select mount point from the source table.** | No mountpoint chosen | Tap **Download source list**, then choose `AUTO` in **Source list**. | | No **Fixed**, and **Source list** shows an entry other than `AUTO` or an `AUTO_` variant | A different sourcetable entry was chosen. This guide covers only `AUTO`, `AUTO_ITRF2020`, `AUTO_ITRF2014` and `AUTO_WGS84`. | Tap **Disconnect**, choose `AUTO` in **Source list** and tap **Connect**. | | **No device location information. Please check if the device is connected and can search for stars normally.** | The scanner has no GNSS position yet | Go outdoors, wait for satellites and **Single**, then tap **Connect**. | | **Please wait to receive the network RTCM coordinate system.** | **Use Broadcast RTCM** is on | Switch it off. RTKdata does not send RTCM 1021 to 1027. | | No **Use RTK or not** switch as shown in the April 2024 RS10 manual | SmartGo Neo 1.5.6.1 and SmartGo 1.5.5 label this switch **RTK enabled** | Switch on **RTK enabled** instead. | | **Please disconnect the differential connection, and then switch the service type.** | Type changed while connected | Tap **Disconnect**, then set **Type** to **CORS**. | | **Unable to switch while capturing.** | RTK changed during capture | Set up RTK and wait for **Fixed** before you start the project. | | **The account is already signed in on another device.** | Most likely the same credentials are in use on a second device | Disconnect the other device, or use one data stream per device that runs at the same time. See [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices). | | Status stays at **Float** | Blocked sky view | Move to open sky and wait for **Fixed** before you start the project. | | No connection after following the port note in CHCNAV's manual | **Port** changed to a CHCNAV or Qianxun service port | Set **Port** back to `2101`. The mountpoint selects the frame. | | **The device authorization has expired.** or **Failed to open project, device not authorized.** | Expired authorization, typical for rental or demo units | Check **Device authorization status** in SmartGo Neo with internet on the tablet, or contact your dealer. | | The PC does not show the RS10 as a drive | The scanner is switched on | Switch the RS10 off, then connect it by USB-C. | | Point cloud in CoPre has relative coordinates | **Relative Coordinate System** in the task, or no valid RTK during capture | Create the task with **Projected Coordinate System**, make sure the capture ran at **Fixed**, and check a control point. | | Unusable coordinates after projection in an older CoPre version | Older versions preset **WGS84 / Gaussian Projection / 114E** | Choose your system under **Standard Coord System** by EPSG. | ### If the server address does not resolve If **Server address resolution error, please check and try again.** persists while the tablet has internet, enter the RTKdata IP fallback of your region in **Server address**: `13.56.117.10` (North America), `3.73.41.96` (Europe) or `54.206.56.130` (Australia). Port, credentials and source list stay the same. Switch back to the host name once it resolves, because [NTRIP Server Settings](/get-started/network.md) lists the host name as the preferred entry. If the connection still fails or SmartGo Neo does not reach **Fixed**, email with your RTKdata username, region host, mountpoint, the SmartGo Neo version, the exact message and screenshots of **RTK settings** and the status bar. For connection problems that are not specific to the RS10, see [Fix NTRIP Connection Issues](/support/common-connection-issues.md). ## Frequently asked questions ### How do I connect the CHCNAV RS10 to a third-party NTRIP caster? In SmartGo Neo, open **RTK settings**, switch on **RTK enabled**, set **Type** to **CORS**, enter the caster's server address, port, user name and password, tap **Download source list**, choose the mountpoint and tap **Connect**. For RTKdata the values are the host for your region (`rtk.rtkdata.com` in North America, `eu.rtkdata.com` in Europe, `aus.rtkdata.com` in Australia), port `2101` and the mountpoint `AUTO`, with the credentials from *RTK Credentials* in your RTKdata account. ### Why can't my RS10 connect to CORS while the tablet is on the scanner Wi-Fi? The CHCNAV RS10 Wi-Fi `SLAM-XXXXX` has no internet access, so the tablet or phone must reach the CORS caster, for RTKdata `rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com` on port `2101`, over its own mobile data. Turn mobile data back on after joining the scanner Wi-Fi and check that a web page loads. If SmartGo Neo still reports no internet, choose **Forget network** for `SLAM-XXXXX` and join it again. A phone hotspot does not help, because the tablet's Wi-Fi is already in use. ### Should Use Broadcast RTCM be enabled for RTKdata? No. **Use Broadcast RTCM** waits for the coordinate system messages RTCM 1021 to 1027, and RTKdata does not send them. Leave it off on the CHCNAV RS10 and set the coordinate system in CoPre instead. ### Does the RS10 still need loops when RTK is fixed? Even with a **Fixed** solution from RTKdata corrections, the CHCNAV RS10 can skip loops only when more than 70% of the area has good GNSS reception, according to CHCNAV's operating procedure. In other areas no loop is needed within 300 m, but beyond 300 m a loop is required, with more than 20% overlap. Short GNSS dropouts can still cause drift, so check the result at a control point. ### Is the RS30 set up the same way as the RS10? Yes. RS30 is the name dealers use for the RS10 (32 lines), which CHCNAV lists on the same RS10 datasheet as the 16-line version. Both are operated from SmartGo Neo, so the RTKdata settings on this page apply to both. ### Does this setup apply to the GeoCue TrueView GO 116S / 132S? This page is written for the CHCNAV RS10 in SmartGo Neo. GeoCue's TrueView GO user guide also describes a CORS login in the RTK settings of the app. For RTKdata, enter the values from the table at the top of this page: the host for your region (`rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com`), port `2101`, the mountpoint `AUTO` and the credentials from *RTK Credentials*. If the GeoCue app lists **GeoCue CORS** under **Type**, choose **CORS**, not **GeoCue CORS**. ## Related Guides * [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md): all LiDAR and SLAM scanner guides in this category * [NTRIP Server Settings](/get-started/network.md): regional hosts, IP fallbacks, port 2101 and which server to pick * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): how `AUTO` uses the device position to pick a base station, and which correction format RTKdata streams * [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which regional datum `AUTO` delivers in each country, and how to spot a datum mismatch * [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): the datum and height workflow for SLAM scans across scanner brands * [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 your RTK credentials and how data streams work with several devices * [Fix NTRIP Connection Issues](/support/common-connection-issues.md): what to check when you log in but no corrections arrive * [Coverage Map](/get-started/coverage-map.md): check base station coverage in your work area before the job * [CHC i93 / i90 / X7](/integration-hub/gnss-rovers-and-receivers/chc-i93-i90.md): CHCNAV GNSS rovers in LandStar 8, a guide that does not cover the RS10 ## Quick reference 1. Join `SLAM-XXXXX` on the tablet, keep mobile data on, open SmartGo Neo and tap **Connect device**. 2. **Start capture** > settings icon > receiver icon > **RTK settings**: **RTK enabled** on, **Type** **CORS**. 3. **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`, **User name** and **Password** from *RTK Credentials*, **Download source list** > `AUTO`, **Use Broadcast RTCM** off. 4. Outdoors, wait for **Single**. SmartGo Neo sends the position (GGA) itself. Tap **Connect**, wait for **Fixed**, then start the project. 5. CoPre: **Projected Coordinate System**, EPSG system of the regional datum that `AUTO` delivers, **Geoid model**, **RTK POS Optimization**, then check a control point. --- # 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/chcnav-rs10-rs30.md?ask=&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.