> 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/share-slam-s20-c1-pro-s100.md). # SHARE SLAM S20 RTK Setup (C1 Pro, S100): SHARE Capture NTRIP Connect a SHARE SLAM S20, C1 Pro, S20 SE RTK or S100 to RTKdata NTRIP in SHARE Capture: phone mobile data, server, port 2101, AUTO and the FIXED check. This page covers the SHARE SLAM S20 RTK setup with RTKdata NTRIP corrections for the SHARE3DCAM (SHAREUAV) handheld and backpack SLAM scanners: the **SHARE SLAM S20**, the **SHARE C1 PRO**, the **SHARE SLAM S20 SE RTK**, the **SHARE SLAM S20 SE** and **SHARE C1** with the RTK module kit, and the **SHARE SLAM S100-16**, **S100-32** and **S100-32 PRO**. All of them are set up in the **SHARE Capture** app (listed as **SHARECapture** by SHAREUAV LTD in the App Store and on Google Play), and the scans are georeferenced in **SHARE PointClouds Studio** on Windows. The SHARE3DCAM C10 is listed in the model table below with what applies to it. For RTKdata you turn on **RTK Account Switch** in the **RTK** tab of SHARE Capture and enter your RTKdata NTRIP credentials under **Edit Account** with **Account Type** **User-Defined**. SHARE's specifications list Wi-Fi (and Bluetooth on the S20) as the scanners' connections and no cellular connection, so the corrections come through your phone: the phone sits on the scanner's Wi-Fi, and SHARE Capture fetches the corrections over the phone's mobile data. Enter these values in SHARE Capture under **Start** > gear icon > **RTK** > **Edit Account**. Select the tab for your region and use 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):** `rtk.rtkdata.com` in **Server** (preferred) * **Host (IP fallback):** `13.56.117.10` in **Server**, if **Setup Failed** stays although mobile data is on and **Account**, **Password**, **Port** and **Mount Point** are correct, or if **RTK Status:** stays on **Connecting** * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/) in **Account** and **Password**, not your website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended) in **Mount Point**, or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` {% endtab %} {% tab title="Europe" %} * **Host (domain):** `eu.rtkdata.com` in **Server** (preferred) * **Host (IP fallback):** `3.73.41.96` in **Server**, if **Setup Failed** stays although mobile data is on and **Account**, **Password**, **Port** and **Mount Point** are correct, or if **RTK Status:** stays on **Connecting** * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/) in **Account** and **Password**, not your website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended) in **Mount Point**, or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` {% endtab %} {% tab title="Australia" %} * **Host (domain):** `aus.rtkdata.com` in **Server** (preferred) * **Host (IP fallback):** `54.206.56.130` in **Server**, if **Setup Failed** stays although mobile data is on and **Account**, **Password**, **Port** and **Mount Point** are correct, or if **RTK Status:** stays on **Connecting** * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/) in **Account** and **Password**, not your website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended) in **Mount Point**, or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` {% endtab %} {% endtabs %} All SHARE Capture values at a glance: | Field | Value | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **RTK Account Switch** | On (blue). Grey means RTK is off. | | **Account Type** | `User-Defined` | | **Account** | 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 | | **Server**, North America | `rtk.rtkdata.com`, IP fallback `13.56.117.10` | | **Server**, Europe | `eu.rtkdata.com`, IP fallback `3.73.41.96` | | **Server**, Australia | `aus.rtkdata.com`, IP fallback `54.206.56.130` | | **Port** | `2101`, digits only | | **Mount Point** | `AUTO` in capital letters. Alternatives: `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` | | NMEA GGA | No switch in SHARE Capture. Outdoors, wait for **SINGLE** before you tap **Confirm**. | **Server** is a text field, so enter the host name first, without `http://` and without a port, because **Port** is a separate field. Use the IP fallback of the same region if **Setup Failed** stays although mobile data is on and **Account**, **Password**, **Port** and **Mount Point** are correct, or if **RTK Status:** stays on **Connecting**. SHARE Capture has no GGA switch: give the scanner a position outdoors before you tap **Confirm**, as described in the steps below. ## Which SHARE scanners can use RTKdata corrections? The SHARE SLAM S20, SHARE C1 PRO, SHARE SLAM S20 SE RTK and SHARE SLAM S100 series can use RTKdata NTRIP corrections in SHARE Capture with a **User-Defined** account. The SHARE SLAM S20 SE and SHARE C1 need the RTK module kit first, and SHARE has not published the RTK steps for the SHARE3DCAM C10 yet. | Model | RTK | Status of the steps on this page | | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | SHARE SLAM S20 | Built in (SHARE: "Built-in standard"; S20 manual: "integrated RTK module") | Shown by SHARE in the *SHARE SLAM S20 User Manual V2.0* (section 3.5.1, RTK Setting) and in the S20 Quick Guide | | SHARE C1 PRO | Built in (SHARE: "Integrated RTK Positioning") | SHARE's store: "This product differs from the S20 only in color", so the S20 steps apply | | SHARE SLAM S20 SE RTK | Detachable RTK module (SHARE: "Detachable as standard") | Same **RTK** tab in SHARE Capture as the S20. Check in step 3 that the app detects the module. | | SHARE SLAM S20 SE, SHARE C1 | Only with the **RTK module + Positioning board kit** fitted (SHARE: "Applicable product models: SHARE C1 ; SHARE SLAM S20 SE") | With the kit fitted, the steps on this page apply. Without the kit there is no RTK: georeference with control points. | | SHARE SLAM S100-16, S100-32, S100-32 PRO (backpack) | Built in (SHARE: "Upgraded RTK for Precise Positioning") | Shown by SHARE3DCAM in its video *SHARE SLAM S100 Series Unboxing & Setup Tutorial*: "Go to settings, turn on RTK, tap edit account" | | SHARE3DCAM C10-16, C10-32, C10-32 PRO (backpack) | Built in (SHARE: "High-Accuracy IMU + RTK + SLAM") | Supported by SHARE Capture 2.6.1 according to SHARE's release notes. SHARE has not published the RTK steps for the C10 yet, check the labels on your unit. | For other scanners, see [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md). ## What do you need before connecting a SHARE SLAM S20 or S100? To connect a SHARE SLAM S20, C1 PRO, S20 SE RTK or S100 to RTKdata you need the scanner with its RTK hardware, the SHARE Capture app on a phone with a SIM and mobile data, current scanner firmware, active RTKdata NTRIP credentials and RTKdata coverage at your site, plus SHARE PointClouds Studio on a Windows PC for georeferencing. * **Scanner with RTK hardware.** S20, C1 PRO and S100: nothing to mount. S20 SE RTK: the detachable RTK module. S20 SE and C1: the **RTK module + Positioning board kit**. See the model table above. * **SHARE Capture** (**SHARECapture**, SHAREUAV LTD) from Google Play or the App Store. The App Store listing states: "Requires iOS 14.0 or later." On Android you can also install the APK from SHARE's download page on share3dcam.com. * **Android phone with a SIM and mobile data switched on.** The phone's Wi-Fi is taken by the scanner, so the corrections come over mobile data, see the next section. For an iPhone, read the note in the next section. * **Bluetooth and Wi-Fi on** at the phone. Allow the location, Bluetooth and Wi-Fi permissions when SHARE Capture asks for them on the first start. * **RTKdata account** with active RTK credentials (username starts with `rtk`). * **Coverage at your site.** Check the [RTKdata coverage map](/get-started/coverage-map.md) before the job. * **SHARE PointClouds Studio V2.6** on a PC that meets SHARE's requirements: 64-bit Windows 11, an RTX 3060 or better graphics card with at least 8 GB of dedicated video memory for point clouds, at least 64 GB of RAM and at least 100 GB of free storage. {% 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 %} The labels on this page come from the English SHARE Capture 2.6.1 interface. Where the *SHARE SLAM S20 User Manual V2.0* shows an older label, it is given in brackets. Current app version when this page was written: SHARE Capture 2.6.1 (September 2026). ### Before your first field day Do these steps in the office the day before, with the phone online: 1. **SHARE account.** In SHARE Capture, tap **Sign up**, register with your email address and log in. 2. **Connect the scanner once.** Connect it as in step 2 below. If SHARE Capture shows **Device Unactivated**, activate the scanner there with **Activate Now** and fill in **Company:**, **Contact:**, **Supplier:** and **Contact Info:**. Do this in the office, not in the field. 3. **Service firmware.** When SHARE Capture offers a firmware update, or under **Upgrade Management**, tap **Preload and Auto-Upgrade** (**Pre-loaded and Updated automatically** in SHARE's app introduction) to download the firmware to the phone, then tap **Upgrade**. The scanner can restart several times during the update. Wait until it has finished. 4. **System firmware.** SHARE Capture does not install the system firmware itself. If it shows **The device system firmware needs to be updated manually. Please visit this download address using a computer browser.**, download the file on a PC from SHARE's [Firmware Upgrade Download](https://www.share3dcam.com/en/gujian.html) page. If your model is not listed there, ask SHARE support for the file. Take the TF card out of the scanner, copy the file to the root directory of the card, insert the card again and restart the scanner. The update takes a few minutes up to ten minutes and is finished when the blue light stays on. Charge the scanner above 25 % first, as SHARE Capture asks. ## Where does a SHARE scanner get internet for RTK corrections? A SHARE SLAM S20, C1 PRO, S20 SE RTK or S100 gets its RTKdata corrections through SHARE Capture on your phone: the phone joins the scanner's Wi-Fi, which has no internet access, and SHARE Capture fetches the corrections over the phone's mobile data. The scanner Wi-Fi is named after the model and serial number (the S20 manual shows `SLAM S20-xxxxxx`). Without mobile data SHARE Capture shows **No mobile network detected. Please turn on mobile data or insert a SIM card.** or **Network exception, please configure your phone to obtain a cellular network connection and try again.** {% hint style="warning" %} **If the phone's Wi-Fi is connected to the scanner, the internet has to come from mobile data.** Turn mobile data on before you connect, and data roaming if you use your SIM abroad. A Wi-Fi-only tablet, a phone without a SIM or a phone with mobile data switched off gets no corrections. A hotspot from a second device does not replace the mobile data either, because the phone's Wi-Fi is taken by the scanner. {% endhint %} * **iPhone.** Keep mobile data allowed for SHARECapture in the iOS settings. Test the setup the day before with exactly this iPhone, outdoors, until SHARE Capture shows **FIXED**. If you want to be sure, use an Android phone with a SIM. * **Proxy off.** SHARE Capture warns **The app is currently using a proxy network, which may prevent it from connecting to the device properly. Please turn off the proxy and try again.** * **Reception.** Tap **Confirm** in step 6 at a spot with good mobile reception. The [SkylandX MetaCam](/integration-hub/lidar-scanners-and-mobile-mapping/skylandx-metacam.md) and the [CHCNAV RS10 / RS30](/integration-hub/lidar-scanners-and-mobile-mapping/chcnav-rs10-rs30.md) use the same pattern with the phone or tablet on the scanner Wi-Fi. ## How does the SHARE SLAM S20 RTK setup work in SHARE Capture? To set up SHARE SLAM S20 RTK with RTKdata, you tap **Start** in SHARE Capture, open the gear icon at the top right, select the **RTK** tab, turn on **RTK Account Switch**, tap **Edit Account**, keep **Account Type** on **User-Defined** and enter **Server** `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia), **Port** `2101`, **Mount Point** `AUTO`, and the username and password from *RTK Credentials* in **Account** and **Password**, then you tap **Confirm** outdoors and wait for **FIXED**. {% stepper %} {% step %} ### Power on the scanner outdoors {% tabs %} {% tab title="Handheld (S20, C1 PRO, S20 SE, C1)" %} 1. Short press and then long press the battery button at the bottom of the grip battery. 2. Wait about one minute. The scanner vibrates slightly, and the status light stays solid blue (**Boot Completed** in the LED table of the S20 manual). {% endtab %} {% tab title="Backpack (S100)" %} 1. Slide the storage module into the Type-C port at the back until it clicks. 2. Turn the knob at the bottom to unlock, insert the battery, then tighten the knob to lock it. 3. Press the power button briefly, then hold it. SHARE3DCAM's S100 tutorial: "When the light turns blue, it's on." {% endtab %} {% endtabs %} SHARE3DCAM C10: SHARE has not published the power-on steps for the C10 yet. Follow the documentation that came with your unit. {% endstep %} {% step %} ### Connect SHARE Capture to the scanner 1. Turn on Bluetooth and Wi-Fi on the phone. Leave mobile data on. 2. Open SHARE Capture and log in. 3. The first time, tap **Connect Device**. SHARE Capture searches for nearby scanners and lists them. Select your scanner by its serial number (SN). If your app shows **Select Others** instead, as in the S20 manual V2.0, tap it and pick the scanner and its Wi-Fi network `SLAM S20-xxxxxx`. 4. When the prompt shows the SN and **Encrypted**, tap **Connect**. 5. The scanner is connected when the red dot at the top left turns green. Next time, turn on Wi-Fi and Bluetooth and tap **Quick Connection** to connect to the scanner you used last. {% endstep %} {% step %} ### Check that SHARE Capture detects the RTK module Tap the **Normal** icon to open **HMS** (**Health Management System**) and check the status of **RTK**. If SHARE Capture reports **RTK module not detected**, the scanner has no working RTK module: an S20 SE or C1 without the kit, or a module that is not fitted correctly. Fit the module and check **HMS** again. {% endstep %} {% step %} ### Open the RTK tab and turn on RTK Account Switch 1. Tap **Start**. The scan screen opens with the status **Ready**. 2. Tap the gear icon at the top right and select the **RTK** tab, next to **Display**. 3. Turn on **RTK Account Switch**. The switch turns blue; grey means RTK is off. 4. Tap **Edit Account**. {% endstep %} {% step %} ### Enter your RTKdata account in Edit Account 1. **Account Type:** **User-Defined** (**user-defined** in the S20 manual screenshot). It is the default. 2. **Account:** your NTRIP 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. 3. **Password:** the NTRIP password from *RTK Credentials*, not your website password. 4. **Server:** the host name for your region, `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia), without `http://` and without a port. Use the IP fallback from the region tabs at the top of this page if **Setup Failed** stays although mobile data is on and all other values are correct, or if **RTK Status:** stays on **Connecting**. 5. **Port:** `2101`, digits only. 6. **Mount Point:** scroll down the form, the field sits below **Port**. Type `AUTO` in capital letters. If SHARE Capture shows a note about WGS84 at **Port** (app text **Enter the port corresponding to WGS84**), keep `2101`. The note belongs to the presets for services in mainland China. With RTKdata you choose the reference frame with the mountpoint. {% hint style="info" %} There is no coordinate system field for a **User-Defined** account. SHARE's videos mention choosing a coordinate system: with RTKdata you set the datum later in SHARE PointClouds Studio, see the Studio section below. {% endhint %} {% hint style="info" %} **AUTO needs your scanner's position.** The caster picks the nearest base station from the position your scanner reports (NMEA GGA). Without a position the login succeeds, but no corrections arrive. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). SHARE Capture has no GGA switch, so wait outdoors until the status at the top shows **SINGLE** before you tap **Confirm**. {% endhint %} {% hint style="info" %} Type the username and password instead of pasting them, and check that no field starts or ends with a space. One set of credentials allows one connection at a time, so every scanner or other 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). {% endhint %} {% endstep %} {% step %} ### Save the account with Confirm 1. Outdoors under open sky, wait until the **RTK** tab shows **Satellites** and a position, and the status at the top shows **SINGLE**. 2. At a spot with good mobile reception, tap **Confirm**, not **Exit**. **Exit** closes the form without saving. 3. SHARE Capture shows **Processing…**, then **Success** or **Setup Failed**. **Success** is not a fix yet. It does not show that corrections are arriving. Continue with the next step. Next time, tapping **Confirm** in the **RTK** tab is enough (S20 manual, section 3.5.1). Saved accounts appear under **Previous Accounts**. Before each scan, check that **RTK Account Switch** is still on. {% endstep %} {% step %} ### Wait for FIXED 1. Under **RTK Status:**, check for **Receiving Data**. The other values are **Disconnected**, **Connecting** and **Offline**. 2. The status at the top moves from **SINGLE** through **FLOAT** to **FIXED**. 3. Start the project only at **FIXED**. SHARE's S20 Quick Guide: "Check the RTK Status and wait for RTK FIXED before scanning." On the S20 and the C1 PRO, the right-hand light on the scanner shows the RTK status during operation, according to the LED table in the S20 manual: a slow green flash at **RTK Fixed (normal)**, slow yellow at single or float, slow red when there is a GPS signal but no RTK corrections, slow blue when RTK is off or there is no GPS signal, and solid red at **RTK Abnormality**. The left-hand light shows the device status. SHARE Capture stays the reference. SHARE documents no RTK light for the S100 and the C10. {% endstep %} {% endstepper %} ## How do you know the SHARE scanner has a usable RTK fix? A SHARE SLAM S20, C1 PRO, S20 SE RTK or S100 has a usable RTK fix from RTKdata when **RTK Status:** in SHARE Capture shows **Receiving Data** and the status at the top shows **FIXED**; **Success** after **Confirm** and **Receiving Data** on their own are not a fix. * The status at the top shows **NONE**, **SINGLE**, **DGPS**, **FLOAT** or **FIXED**. **DGPS** and **FLOAT** with **Receiving Data** mean that corrections are arriving, but there is no RTK fix yet. Only **FIXED** counts. * Tap **RTK Status** to see **Latitude**, **Longitude**, **Elevation** and **Satellites**. SHARE's S20 manual labels this height value **Ellipsoid**, so treat it as an ellipsoidal height, not a height above sea level, see [Understanding Heights](/get-started/understanding-heights.md). * **GNSS Fusion** in SHARE PointClouds Studio needs, in SHARE's words, "a sufficient number of fixed solutions during the scan", so start the scan only at **FIXED**. {% hint style="warning" %} **Success is not a fix.** **Success** after **Confirm** does not show that corrections are arriving, and **Receiving Data** alone does not show a fix. Only **FIXED** in the status at the top counts. {% endhint %} ### Scanning with RTK * On the scan screen, tap **Start** at **Ready**. In **Pre-Work Inspection**, check **HMS**, **RTK**, the battery and the storage. * Choose the **Acquisition Mode** (**Capture Mode** in the S20 manual screenshot), enter a **Project Name** that uses only letters, numbers, `_`, `-` and `.`, without spaces, set **Time Interval(s)** and tap **Next**. * Keep the scanner still on a flat surface while it initializes. * Walk the first 30 m in an S pattern. SHARE Capture: "To improve RTK fusion quality, it is recommended to collect data in an "S" pattern for the first 30m". Keep the speed under 1 m per second, as the S20 Quick Guide recommends. * If SHARE Capture shows **Current walking pattern affects post-processing RTK fusion quality, please move 2m or more to the left or right immediately**, move sideways as the prompt asks. At **RTK Collection Alert**, SHARE Capture recommends a new project, see the troubleshooting table below. * S100: the storage module must be in place. Without it SHARE Capture shows **No storage card detected. Please retry after inserting a storage card.** * Start and end the scan outdoors under open sky. ## Which coordinate system do you set in SHARE PointClouds Studio? With the RTKdata `AUTO` mountpoint, you process the scan in SHARE PointClouds Studio with **GNSS Fusion** and **Trajectory Source** **Built-in RTK Trajectory**, set **Original Horizontal Coordinate System** to your regional datum instead of the preset **WGS 84**, for example ETRS89 (`EPSG:4258`) in Europe or NAD83(2011) (`EPSG:6318`) in the USA, and choose a projected system on the same datum under **Target Coordinate System**, for example ETRS89 / UTM zone 32N. {% hint style="warning" %} **Studio presets WGS 84 as source and a Chinese CGCS2000 projection as target. Change both before you process.** {% endhint %} `AUTO` delivers the corrections in the regional datum for your position, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe, GDA2020 in Australia, NZGD2000 in New Zealand and SIRGAS2000 in South America. For regions without a listed regional datum, `AUTO` falls back to WGS84(G2139) at the mid-year epoch. `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver ITRF at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) at the mid-year epoch. The datum and epoch for every country are in the [RGCS table in Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md#regional-geodetic-coordinate-system-rgcs). SHARE describes **Original Horizontal Coordinate System** as "The original geographic coordinate system of the RTK account during data acquisition. If the system cannot retrieve this information automatically, you must configure it manually." With a **User-Defined** account there is no coordinate system in SHARE Capture, so declare the datum of your mountpoint here: | Mountpoint | Where you scan | Original Horizontal Coordinate System | | ------------ | --------------------------- | ------------------------------------- | | `AUTO` | Europe | `EPSG:4258` (ETRS89) | | `AUTO` | USA, except Hawaii and Guam | `EPSG:6318` (NAD83(2011)) | | `AUTO` | Canada | `EPSG:4617` (NAD83(CSRS)) | | `AUTO` | Australia | `EPSG:7844` (GDA2020) | | `AUTO` | South America | `EPSG:4674` (SIRGAS 2000) | | `AUTO` | New Zealand | `EPSG:4167` (NZGD2000) | | `AUTO_WGS84` | Anywhere | `EPSG:4326` (WGS 84) | Steps for SHARE PointClouds Studio V2.6: 1. In the reconstruction task, switch on **GNSS Fusion**. SHARE: "you can enable GNSS Fusion or Control Point Calibration for the corresponding task", so do not use **Control Point Calibration** in the same task. 2. Set **Trajectory Source** to **Built-in RTK Trajectory**. 3. Under **Source Coordinate System**, open **Original Horizontal Coordinate System** and click **Horizontal Coordinate System Database** (**Choose Horizontal Coordinate System Database** in the screenshots of SHARE's Studio manual). Enter the name or the EPSG code in the search (**Authorization Code**), select the entry from the table above and click **OK**. Do not accept the preset **WGS 84** or the entries **Auto-detection** and **China Geodetic Coordinate System 2000** without checking: with `AUTO`, the source is your regional datum. 4. Under **Target Coordinate System**, keep **Known Coordinate System** and open **Horizontal Setting** (**Horizontal Coordinate** in some views). Choose the projected system of the same datum by EPSG code, for example 25832 (ETRS89 / UTM zone 32N) or 6346 (NAD83(2011) / UTM zone 17N). Replace the preset **CGCS2000 / 3-degree Gauss-Kruger...**, which is the Chinese system. 5. Leave **Height Offset(m)** on `0`, unless you want a fixed height offset for the whole point cloud. 6. Process the task and check the result at one known control point. {% hint style="info" %} **Use AUTO, declare the AUTO datum as source, choose a target on the same datum, do not add a WGS84-to-national transformation, check one control point.** {% endhint %} * **Exactly one transformation.** Do not add a WGS84-to-national datum transformation on top of the source and target systems. SHARE does not document how Studio relates the source to the target datum or whether it handles epochs, so the control point is your check. A consistent offset of 50 cm to 1 m against control is 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). Check **Original Horizontal Coordinate System** first. * **Datum not in the list.** In Canada, choose the NAD83(CSRS) entry, or a v7 entry if Studio lists one. If your datum is not in the list, ask . * **Global mountpoints.** Use `AUTO_ITRF2020` or `AUTO_WGS84` only when the deliverable must stay in a global frame. With `AUTO_WGS84`, the source is `WGS 84` (`EPSG:4326`); with `AUTO_ITRF2020` or `AUTO_ITRF2014`, choose the matching ITRF frame. Keep one mountpoint per project. * **WGS84 labels.** Why scanner software often says WGS84 while `AUTO` delivers your regional datum is explained in [Georeference SLAM Point Clouds with RTK](/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). ### Heights and control points * **Treat the heights as ellipsoidal.** **GNSS Fusion** offers only **Height Offset(m)**, and SHARE's Studio manual describes no geoid model. For heights above sea level, apply the geoid of your region in your CAD or GIS software, or transform the finished point cloud to control points with **Coordinate Transformation**. A difference of 10 to 50+ m against benchmarks is the geoid separation. See [Understanding Heights](/get-started/understanding-heights.md). * **Coordinate Transformation** needs at least three valid control points, according to SHARE's FAQ, and writes the result as `originalname_converted.las`. * **GNSS Fusion** and **Control Point Calibration** are alternatives for one task, not a combination. ### PPK as a fallback **Trajectory Source** also offers **GNSS Trajectory (PPK)**. SHARE's Studio manual states that only POS files in the format defined by RTKLIB are supported. PPK needs base station observation data for the whole scan, usually from a base station you run yourself, and the RTKdata NTRIP stream does not replace those observations. Decide before the scan, 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). ## Why does SHARE Capture show Setup Failed or never reach FIXED? SHARE Capture shows **Setup Failed** or stays below **FIXED** with RTKdata when the phone has no mobile internet, the credentials, the port or the mountpoint are wrong, or the scanner has no position yet; check mobile data first, retype **Account** and **Password**, check **Port** `2101` and **Mount Point** `AUTO`, wait outdoors for **SINGLE**, and use the regional IP fallback in **Server** last. Work through it in this order: 1. **Phone internet.** Mobile data on, a SIM with a data plan, data roaming on abroad, proxy off. Tap **Confirm** once more at a spot with good mobile reception. 2. **Account and Password.** Retype both from *RTK Credentials*, without spaces and without automatic capitals. The username starts with `rtk`. If both are right, check at [My Account](https://rtkdata.com/my-account/) that your trial or subscription is active. 3. **Port and Mount Point.** **Port** reads `2101`, digits only. **Mount Point** reads `AUTO` exactly, in capital letters. 4. **Position.** Outdoors, wait until the status at the top shows **SINGLE**, then tap **Confirm** again. 5. **IP fallback.** Enter the IP fallback of your region in **Server** (`13.56.117.10` North America, `3.73.41.96` Europe, `54.206.56.130` Australia), keep **Port** `2101` and **Mount Point** `AUTO`, and tap **Confirm**. 6. **Second device.** If another device uses the same credentials at the same time, disconnect it or add a data stream. After two **Setup Failed** in a row, do not keep tapping **Confirm**. Check the values first. ## Troubleshooting | What you see | Likely cause | What to do | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **No mobile network detected. Please turn on mobile data or insert a SIM card.** or **Network exception, please configure your phone to obtain a cellular network connection and try again.** | No mobile data on the phone | Insert a SIM with a data plan, turn on mobile data, and data roaming abroad. A Wi-Fi-only tablet or the hotspot of a second device does not help. | | **Setup Failed** after **Confirm** | No or weak mobile internet, then wrong credentials, a wrong port or mountpoint, an ended RTKdata trial or subscription, or a host name that does not connect | Check mobile data and reception first. Then retype **Account** and **Password** (the username starts with `rtk`) and check at [My Account](https://rtkdata.com/my-account/) that your trial or subscription is active. SHARE Capture lists "The account has expired" among the possible reasons. Check **Port** `2101` with digits only and **Mount Point** exactly `AUTO`. Last, enter the IP fallback of your region in **Server**: `13.56.117.10` (North America), `3.73.41.96` (Europe) or `54.206.56.130` (Australia). After two **Setup Failed**, check the values before you tap **Confirm** again. | | **RTK Status:** stays on **Connecting** | No internet on the phone, or the host name does not connect | Check mobile data, then enter the IP fallback of your region in **Server** and tap **Confirm**. | | **Success**, but no **FIXED** | **Success** is not a fix | Check **Receiving Data** under **RTK Status:**, then wait outdoors for **FIXED**. | | S20 and C1 PRO: the right-hand light flashes slowly red | GPS signal, but no corrections (SHARE: "GPS signal exists, but no RTK or RTCM") | Check mobile data, **Account**, **Password**, **Server**, **Port** and **Mount Point** `AUTO`, wait outdoors for **SINGLE** and tap **Confirm** again. | | **Receiving Data**, but **SINGLE**, **DGPS** or **FLOAT** | No position at the caster yet, a blocked sky, or a long distance to the nearest station | Stay outdoors under open sky and wait. If it does not change, tap **Confirm** again after the status shows **SINGLE**, and check the site on the [Coverage Map](/get-started/coverage-map.md). | | **RTK connection has been interrupted. Do you want to try reconnecting?** | The phone lost mobile coverage, for example indoors | Tap **Retry**. From the third time SHARE Capture shows **RTK connection failed multiple times. Please check the network environment and connection information, then manually reconnect.**: check the network, then tap **Confirm** again in the **RTK** tab. | | **Illegal area, RTK is disabled!** | The scanner reports that it is outside its sales region, and SHARE Capture restricts RTK. This is not a caster problem. | Contact SHARE support or the seller of the scanner. | | **RTK module not detected** | No RTK module, or the module is not fitted correctly | S20 SE and C1: fit the **RTK module + Positioning board kit**. Check **HMS** again. | | **Account Type** shows more entries than **User-Defined** | The phone language is set to Chinese | Choose **User-Defined**, the other entries are presets for services in mainland China. | | **No permission to use WiFi.**, **Wifi is not permitted** or **Bluetooth is not permitted** | SHARE Capture has no permission | Allow location, Bluetooth and Wi-Fi for SHARE Capture in the phone settings, and turn Bluetooth and Wi-Fi on. | | **The app is currently using a proxy network...** | A proxy is active on the phone | Turn off the proxy and try again. | | **The device system firmware needs to be updated manually...** | The system firmware is out of date | Update it with a PC and the TF card, see **Before your first field day** above. | | S100: **No storage card detected. Please retry after inserting a storage card.** | The storage module is not in place | Slide the storage module into the Type-C port at the back until it clicks. | | **RTK Collection Alert** during the scan | The project does not meet SHARE's requirements for RTK fusion in post-processing | SHARE Capture recommends a new project: tap **End Current Project** rather than **I Understand, Continue Collection**, move to open sky, wait for **FIXED** and start again. Walk the first 30 m in an S pattern. | | Point cloud consistently 50 cm to 1 m off at control points | **Original Horizontal Coordinate System** does not match the `AUTO` datum, for example left on **WGS 84** | Set the source to the `AUTO` datum of your region and a target on the same datum, then process again. | | Point cloud in a Chinese projection | **Target Coordinate System** left on the preset **CGCS2000 / 3-degree Gauss-Kruger...** | Choose a projected system on your regional datum under **Horizontal Setting**. | | Heights differ from benchmarks by tens of metres | Ellipsoidal heights, no geoid applied | Apply a geoid model, or use **Coordinate Transformation** with control points. See [Understanding Heights](/get-started/understanding-heights.md). | | Corrections drop 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). | For connection problems that are not specific to SHARE Capture, for example a login that succeeds without corrections, see [Fix NTRIP Connection Issues](/support/common-connection-issues.md). ## Frequently asked questions ### Does the SHARE C1 or S20 SE have RTK? The SHARE C1 and SHARE SLAM S20 SE have RTK only with the **RTK module + Positioning board kit**. SHARE lists the kit for "SHARE C1 ; SHARE SLAM S20 SE". Without it, **HMS** in SHARE Capture reports **RTK module not detected** and the scanner cannot use RTKdata corrections. The SHARE SLAM S20 SE RTK comes with the detachable RTK module, and the SHARE C1 PRO has RTK built in. ### Is the SHARE C1 Pro the same scanner as the S20? SHARE's official store says of the C1 PRO: "This product differs from the S20 only in color." Like the SHARE SLAM S20, the C1 PRO has integrated RTK, and the S20 steps on this page apply to it. ### Can I use a third-party NTRIP service like RTKdata in SHARE Capture? Yes. SHARE writes: "You can open RTK and log in to the network CORS account, which supports network CORS of NTRIP protocols." In the **RTK** tab, turn on **RTK Account Switch**, tap **Edit Account**, choose **Account Type** **User-Defined** and enter **Account**, **Password**, **Server**, **Port** and **Mount Point**. 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). SHARE does not list which RTCM messages the scanner's GNSS receiver expects. ### Why does SHARE Capture show no coordinate system field for my RTKdata account? A **User-Defined** account in SHARE Capture has no coordinate system field. SHARE's videos say "Select desired coordinate system" or "choose your coordinate system", but with RTKdata the frame comes from the mountpoint: `AUTO` delivers your regional datum. You declare that datum in SHARE PointClouds Studio as **Original Horizontal Coordinate System** when you process the scan with **GNSS Fusion**. ### Does SHARE Capture need mobile data on my phone for RTK? Yes. The phone sits on the scanner Wi-Fi, which has no internet, so SHARE Capture fetches the RTKdata corrections over the phone's mobile data. Without it the app shows **No mobile network detected. Please turn on mobile data or insert a SIM card.** Use an Android phone with a SIM and mobile data on, and data roaming abroad. With an iPhone, keep mobile data allowed for SHARECapture and test the setup up to **FIXED** before the first job. ## Related Guides * [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md): all scanner guides and the shared RTKdata connection settings * [NTRIP Server Settings](/get-started/network.md): regional hosts, IP fallbacks, port 2101 and the AUTO mountpoints * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why `AUTO` needs your scanner's position 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 why a datum mismatch shows as a steady offset * [Understanding Heights](/get-started/understanding-heights.md): ellipsoidal and orthometric heights, and when a geoid model is needed * [Account & Credentials](/get-started/account-and-credentials.md): where to find your 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 RTKdata coverage at your site before the job * [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): datum and target system choices for every SLAM scanner, WGS84 labels, and RTK against PPK * [SkylandX MetaCam Air 2 / Air](/integration-hub/lidar-scanners-and-mobile-mapping/skylandx-metacam.md): another handheld scanner whose phone sits on the scanner Wi-Fi and uses its mobile data for NTRIP * [CHCNAV RS10 / RS30](/integration-hub/lidar-scanners-and-mobile-mapping/chcnav-rs10-rs30.md): a scanner whose tablet or phone sits on the scanner Wi-Fi and uses its mobile data for NTRIP * [XGRIDS Lixel K1 / K2 / L2 Pro](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-k1-k2-l2-pro.md): LixelGO, where the app also carries the corrections over the phone's mobile data ## Quick reference 1. The day before: SHARE Capture 2.6.1 from Google Play or the App Store, SHARE account, scanner connected once, service and system firmware updated. Mobile data on, data roaming abroad. 2. Power on outdoors, **Connect Device** (next time **Quick Connection**), then **Normal** > **HMS**: **RTK** detected. 3. **Start** > gear icon > **RTK**: **RTK Account Switch** on, **Edit Account**, **Account Type** **User-Defined**, **Account** and **Password** from *RTK Credentials*, **Server** `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`, **Mount Point** `AUTO`. 4. Outdoors, wait for **SINGLE**, tap **Confirm**, check **Receiving Data** under **RTK Status:**, and scan only at **FIXED**. 5. SHARE PointClouds Studio: **GNSS Fusion** with **Built-in RTK Trajectory**, **Original Horizontal Coordinate System** set to the `AUTO` datum of your region, a projected target on the same datum, then check one 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/share-slam-s20-c1-pro-s100.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.