> 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/greenvalley-ligrip.md). # GreenValley LiGrip RTK Setup: O2, O2 Lite & SE NTRIP Connect GreenValley LiGrip O2, O2 Lite, SE RTK and H300 to RTKdata in the RTK link screen. Also covers Topcon CR-S1 and Sokkia SR-S1 / SR-S2 in MAGNET Flow. The **GreenValley LiGrip** handheld SLAM LiDAR scanners accept a custom NTRIP caster, so you can georeference LiGrip RTK-SLAM scans with RTKdata corrections. You enter the caster in the GreenValley app under **RTK link**, not on the scanner. The app passes the settings to the scanner, and the internet connection for corrections comes from your phone's hotspot (O2, O2 Lite, SE RTK) or from a SIM card in the RTK module (O1 Lite, H300, H120). MAGNET Flow shows the same RTK link screen for the Topcon CR-S1 and the Sokkia SR-S1 / SR-S2. Current app version when this page was written: GreenValley 2.1.5 for Android and GreenValley App International 2.0.6 for iOS (September 2026). The screen labels on this page follow the Android app. | Field | Value | | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **the server** | `Custom` | | **Domain Name/IP Address** (host) | North America `rtk.rtkdata.com` (IP fallback `13.56.117.10`), Europe `eu.rtkdata.com` (IP fallback `3.73.41.96`), Australia `aus.rtkdata.com` (IP fallback `54.206.56.130`). Use the IP only if the hostname is not accepted | | **port** | `2101` | | **Source List** (mountpoint) | `AUTO` in capital letters (alternatives: `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84`) | | **Username** | From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). Starts with `rtk`, not your website login | | **Password** | From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login | | **NMEA GGA** | No setting in the RTK link screen. Submit the settings outdoors with satellites in view | Select the tab for your region. Choose the server closest to your working area: all three servers share the same base station network, and the difference is routing latency (see [NTRIP Server Settings](/get-started/network.md)). {% tabs %} {% tab title="North America" %} * **Host (domain):** `rtk.rtkdata.com`, in **Domain Name/IP Address** * **Host (IP fallback):** `13.56.117.10`, in **Domain Name/IP Address** only if the hostname is not accepted * **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 **Username** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, in **Source List** {% endtab %} {% tab title="Europe" %} * **Host (domain):** `eu.rtkdata.com`, in **Domain Name/IP Address** * **Host (IP fallback):** `3.73.41.96`, in **Domain Name/IP Address** only if the hostname is not accepted * **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 **Username** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, in **Source List** {% endtab %} {% tab title="Australia" %} * **Host (domain):** `aus.rtkdata.com`, in **Domain Name/IP Address** * **Host (IP fallback):** `54.206.56.130`, in **Domain Name/IP Address** only if the hostname is not accepted * **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 **Username** and **Password** * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014`, in **Source List** {% endtab %} {% endtabs %} `AUTO` sends the scanner corrections from the nearest reference station and delivers them in your region's datum. Use one of the `AUTO_` frames only when your project has to stay in ITRF2020, ITRF2014 or WGS84. **IP fallback.** Enter the hostname first. If the app reports **CORS server login failed, please check IP and port**, enter the IP fallback of the same region and keep port `2101` (see [What if the scanner does not accept the hostname?](#what-if-the-scanner-does-not-accept-the-hostname)). ## Requirements * **LiGrip with GNSS:** O2, O2 Lite with GNSS module and antenna, or SE RTK (the SE without RTK has no GNSS). The O1 Lite, H300 and H120 need the optional **RTK module**, and the H300 and H120 also need a backpack, vehicle or drone kit. * **App on your phone:** "GreenValley" for Android or "GreenValley App International" for iOS 15.0 or later. The Topcon CR-S1 and Sokkia SR-S1 / SR-S2 use **MAGNET Flow**. The scanner has to be activated once in the app (**ACTIVATE**), which needs internet on the scanner. * **Phone with a SIM card and mobile data** for the O2, O2 Lite and SE RTK, because these scanners go online through the phone's hotspot. The O2 requires the phone hotspot for RTK. GreenValley's SE manual describes a relay mode through a portable Wi-Fi for phones that cannot open a hotspot, so that you can control the scanner. GreenValley's RTK instructions do not describe RTK over relay. If you try it, the portable Wi-Fi has to be online itself. A Wi-Fi-only tablet provides neither a hotspot nor mobile data. GreenValley's O2 FAQ lists Android 8, 6 GB RAM and built-in GPS as the minimum. * **SIM card with a data plan** in the RTK module for the O1 Lite, H300 and H120. * **RTKdata account** with active RTK credentials (username starts with `rtk`). * **RTKdata coverage** in your working area: check the [coverage map](/get-started/coverage-map.md) before the job. * **Open sky** for configuration and initialization. * **LiDAR360MLS** in a version that supports your model (see the model table below). {% 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 LiGrip models support network RTK? The GreenValley LiGrip O2, O2 Lite (GNSS version) and SE RTK have GNSS built in and accept a custom NTRIP caster such as RTKdata, while the LiGrip O1 Lite, H300 and H120 need the optional RTK module with its own SIM card. | Model | GNSS for RTK | **Data link** | LiDAR360MLS version | | ---------------- | ---------------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------ | | O2 | Built in | **Phone Network** | 8.2.2 or later | | O2 Lite | Built in (GNSS version) | **Phone Network** | 8.2.1 or later | | SE RTK | Built in (the SE without RTK has no GNSS) | **Phone Network** | 9.1 or later | | O1 Lite | RTK module with 4G modem and nano SIM | **Host Network** | 7.2 or later | | H300, H300(B.00) | RTK module plus backpack, vehicle or drone kit | **Host Network** | 8.0 or later, H300(B.00) 8.2.1 or later | | H120 | RTK module plus backpack, vehicle or drone kit | **Host Network** | Before 9.0 for SLAM processing. From 9.0, only the H120(A.10) is still processed with SLAM | * **H300:** GreenValley discontinued the H300 in June 2026. Existing units keep getting support from GreenValley or the local partner. * **H120M, GH120 and V100** still appear in the app, but LiDAR360MLS 9.0 and later no longer process them with SLAM. * **O2 Pro:** not in the device list of the Android app 2.1.5, so this page does not cover its setup. * **Correction format:** GreenValley's brochures list RTCM V3.X (O2 Lite) and RTCM V3.\* (SE). 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). {% hint style="warning" %} GreenValley notes on its H300 product page that RTK-SLAM is not available in some regions and refers to local sales partners for details. Ask your dealer before you plan an RTK job. {% endhint %} ## Where does the LiGrip get internet for corrections? The LiGrip O2, O2 Lite and SE RTK reach the RTKdata caster through your phone's hotspot (**Data link** shows **Phone Network**), while the LiGrip O1 Lite, H300 and H120 go online through a SIM card with a data plan in the RTK module (**Data link** shows **Host Network**). {% tabs %} {% tab title="Phone Network: O2, O2 Lite, SE RTK" %} 1. Open the GreenValley app, choose **LiGrip** and your model. 2. **O2:** when the app asks **Do you use RTK?**, tap **Yes**. RTK on the O2 requires the AP hotspot connection, and answering **No** leaves you without RTK. **SE RTK:** answer the hotspot question with **Yes**. 3. Join the scanner's Wi-Fi `LiGrip -****` (default password `greenvalley`) and send the name and password of your phone's hotspot under **Hotspot Configuration Information**. Then switch the hotspot on. On iPhone, enable **Maximize Compatibility**. 4. If the app asks you to switch mobile data off while connecting, switch it back on after **Connect Device** and before you open **RTK link**. Without mobile data the Android app refuses to submit and shows **Please turn on the mobile data.** 5. Keep the hotspot running for the whole scan. GreenValley's O2 FAQ recommends a phone used only for scanning, power saving off, and switching the hotspot on shortly before use, because calls, power saving and hotspots that switch off on their own cut the scanner's connection. 6. On iPhone, allow **Local Network** for the app and turn on location services. GreenValley's iOS screenshots show **Data Link** as **Host Network** for O-series scanners, while the Android app shows **Phone Network**. This page follows the Android app. {% endtab %} {% tab title="Host Network: O1 Lite, H300, H120" %} 1. Insert a SIM card with a data plan into the RTK module. On the O1 Lite, place the nano SIM in the holder and slide the holder into the bottom of the module. 2. Mount and connect the module. **O1 Lite:** module on the **RTK Bracket**, connected with the **LEMO Cable**. **H300 and H120:** backpack, vehicle or drone kit with GNSS antenna, **GNSS Feeder Cable** to the GNSS port of the module, **RTK Connection Cable** to the **RTK** port of the battery box. Without module and kit, the H300 and H120 have no GNSS. 3. Connect your phone to the scanner's Wi-Fi. The internet for corrections comes from the SIM in the module. 4. A SIM supplied with the module from the factory is free for one year. After that it has to be topped up through the QR code or recharge card ID on the module. 5. Older RTK module firmware did not work with SIM cards from the EU or with SIM cards that have a PIN. Update the module firmware before you use such a SIM. 6. With the backpack kit, select the backpack mode in the app and extend the telescopic pole fully. A wrong mode applies the wrong lever arm and increases the deviation at control points. {% endtab %} {% endtabs %} ## How do you set up LiGrip RTK in the RTK link screen? In the GreenValley app, tap **Start Operation** to open **Collection Management**, tap the gear icon at the top right and choose **RTK link**. Then enter `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia) in **Domain Name/IP Address**, port `2101`, **Source List** `AUTO` and your RTKdata username and password, and tap **SUBMIT** outdoors. {% stepper %} {% step %} ### Go outside with a clear view of the sky Power on the scanner outdoors. The app refuses to submit RTK settings without satellites and shows **The current number of satellites is 0, and RTK is not supported.** Configure RTK in the app: GreenValley's manuals state that RTK cannot be configured when using button collection. {% hint style="warning" %} `AUTO` picks the base station from the scanner's position (NMEA GGA). The RTK link screen has no GGA setting. Without a position the login still succeeds, but no corrections arrive, see [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). Stay outdoors and wait until the scanner has a position of its own before you tap **SUBMIT**. {% endhint %} {% endstep %} {% step %} ### Open RTK link After **Connect Device**, tap **Start Operation** to open the **Collection Management** screen, then tap the gear icon at the top right and choose the **RTK link** tile. Older app versions look different. {% endstep %} {% step %} ### Check the preset fields * **Data link:** locked. It shows **Phone Network** on the O2, O2 Lite and SE RTK and **Host Network** on the O1 Lite, H300 and H120. * **Communication Protocol:** locked to **CORS**. * **the server:** **Custom**. In every app language except Chinese this is preset and there is nothing to change. In the Chinese interface the app loads built-in servers with locked fields: choose **Custom**, the last entry in the list, or switch the app language. {% endstep %} {% step %} ### Host Network only: SIM settings **PIN code**, **APN**, **APN Username** and **APN Password** appear only when the scanner reports an international RTK module. Enter the SIM PIN only if the SIM is locked with a PIN, and the APN values only if your carrier requires them. Otherwise leave these fields empty. {% endstep %} {% step %} ### Enter the RTKdata connection * **Domain Name/IP Address:** the hostname for your region, `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia). Only if the hostname is not accepted, the IP fallback of the same region: `13.56.117.10`, `3.73.41.96` or `54.206.56.130`. * **port:** `2101`. GreenValley's manuals say the port depends on the coordinate system. That convention does not apply to RTKdata: the port is always `2101`, and the mountpoint sets the frame. * **Source List:** type `AUTO` in capital letters. After IP and port, a download arrow for the list appears only with firmware that supports it, so do not wait for it. * **Username** and **Password:** your RTKdata credentials from *RTK Credentials*. Type them instead of pasting. The icon at the top right of the RTK link screen lists earlier configurations, and the icon next to **Username** lists earlier accounts. One set of RTKdata credentials allows one connection at a time. Every scanner, rover or app 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). {% hint style="info" %} The app removes every space from every field. With an international RTK module it hands all values to the module as one comma-separated string, so do not use commas in the username or password. If your credentials contain a space or a comma, contact . {% endhint %} {% hint style="info" %} The RTKdata sourcetable loads without a login (checked September 2026). A mountpoint list on screen proves neither your credentials nor a working correction stream. If you download the list, pick `AUTO` from it. {% endhint %} {% endstep %} {% step %} ### Tap SUBMIT and wait for Fixed Tap **SUBMIT**. When the scanner uses your phone's hotspot, mobile data has to be on at this moment. * Success: **RTK configuration successful (Fixed Solution)**, or **RTK configuration successful (Floating point solution), please wait for fixed solution** while the solution converges. * The status panel shows **GNSS** with **Fixed**. * **H300 RTK module:** the RTK, 4G and POW lights stay on. * **O1 Lite:** the RTK status light stays on. Red means "Configuration in progress". {% hint style="warning" %} From O1 Lite firmware V3.5.0 the scanner no longer reuses the last RTK configuration and only delivers a single point solution. Open **RTK link** and tap **SUBMIT** again before every scan, also before scans you start with the button. {% endhint %} {% endstep %} {% step %} ### Initialize and scan 1. Create the project with **NEW PROJECT** and a **Project name:**. Set **Coordinate System Settings:** as described in the coordinate system section below and tap **OK**. 2. On the **Start Collection** screen, set **Scene** to match the site: Outdoor, Indoor, Outdoor+Indoor, and on the O2 series also Open Area. LiDAR360MLS processes Open Area scans differently, and this page does not cover Open Area processing. 3. If you scan from the telescopic pole (O2 Lite, SE RTK), set **Equipment form** to **pole**, enter the **Pole height** and choose **RTK+SLAM** under **Collection Mode**. In all other cases, leave the handheld setting. 4. Tap **START COLLECTION** and hold the scanner still during initialization. GreenValley's manuals recommend at least 20 satellites for initialization. 5. GreenValley support recommends walking a figure eight before and after the scan. 6. Keep indoor and outdoor parts in separate scans. Corrections do not work indoors. {% endstep %} {% endstepper %} ## What if the scanner does not accept the hostname? If the LiGrip shows **CORS server login failed, please check IP and port** after you enter the RTKdata hostname, replace it with the IP fallback of the same region (North America `13.56.117.10`, Europe `3.73.41.96`, Australia `54.206.56.130`) and keep port `2101`. The field is called **Domain Name/IP Address**, and GreenValley's manuals describe a domain name as valid input. All manufacturer examples, including Sokkia's guide for MAGNET Flow, use IP addresses, though, and no published source shows a LiGrip reaching Fixed with a hostname. That is why the IP fallback sits right next to the hostname. [NTRIP Server Settings](/get-started/network.md) lists the IP fallback for each regional server, for devices that cannot resolve hostnames. 1. Try the hostname for your region first: `rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com`. 2. If the login fails with the message above, or with any other connection error, check that **port** is `2101` and enter the IP of the same regional server before you change anything else. 3. If the error stays with an IP, check the phone's mobile data (Phone Network) or the SIM in the RTK module (Host Network). ## How do you set up Topcon CR-S1 or Sokkia SR-S in MAGNET Flow? The Topcon CR-S1 and the Sokkia SR-S1 / SR-S2 connect to RTKdata in MAGNET Flow through the same RTK link screen as the GreenValley app: tap **Start Operation**, the gear icon and **RTK Link**, answer **Yes** to the RTK question, enter `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia) in **Domain Name/IP Address**, port `2101`, **Source List** `AUTO` and your RTKdata credentials, tap Enter on the keyboard after the mountpoint and tap **Submit**. 1. Open MAGNET Flow and join the scanner's Wi-Fi: `TOPCON CR S1_...`, `SOKKIA SR S1_...` or `SOKKIA SR S2_...`. 2. Send your phone's hotspot details to the scanner when MAGNET Flow asks for them, then switch the hotspot on. On iPhone, allow Location and **Local Network**, keep Cellular Data on and enable **Maximize Compatibility**. 3. Tap **Start Operation**, then the gear icon at the top right, then **RTK Link**. When asked whether you want to use RTK, tap **Yes**. 4. **Data link** shows **Phone Network**, **Communication Protocol** shows **CORS** and **the server** shows **Custom**. Enter: * **Domain Name/IP Address:** `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia). IP fallback of the same region: `13.56.117.10`, `3.73.41.96` or `54.206.56.130` * **port:** `2101` * **Source List:** `AUTO`, then tap the Enter key at the bottom right of the on-screen keyboard * **Username** and **Password:** your RTKdata credentials from *RTK Credentials* 5. Tap the blue **Submit** button and wait for Fixed. Sokkia's quick guide shows another correction service with its own IP, port and mountpoint. Replace all three with the RTKdata values. If you are looking for a Topcon or Sokkia GNSS receiver in MAGNET Field, which is a different app, see [Topcon HiPer VR / HR](/integration-hub/gnss-rovers-and-receivers/topcon-hiper-vr-hr.md) and [Sokkia GCX3 / GRX3](/integration-hub/gnss-rovers-and-receivers/sokkia-gcx3-grx3.md). ## Which coordinate system and geoid should you use? For GreenValley LiGrip scans with RTKdata, use the `AUTO` mountpoint, which delivers your region's datum, and pick the coordinate system of that datum under **Custom Selection** if the list offers it. For gravity-related heights, add your geoid in LiDAR360MLS. {% hint style="info" %} **Datum with AUTO** * `AUTO` delivers your region's datum, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe and GDA2020 in Australia. For every region, see the table in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md). * `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver ITRF2020 or ITRF2014 at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) at the middle of the current year. * **Project in the app:** under **Coordinate System Settings:** choose **Custom Selection**, then **Settings**, and search for the system of your regional datum in the same zone if it is listed. Check at a known point first that no additional transformation is applied. * **If it is not listed:** keep **Automatic** (`WGS 84 / UTM zone `). The project is then labelled WGS 84, while `AUTO` delivers corrections in your regional datum. Declare your regional datum in your processing or GIS workflow instead of transforming from WGS84, and check the result at a known control point (see [Matching the Frame in Your Processing Software](/get-started/coordinate-systems-and-datums.md#matching-the-frame-in-your-processing-software)). * **Heights:** RTKdata delivers ellipsoidal heights. See [Understanding Heights](/get-started/understanding-heights.md). * **Control points:** measure them in the same datum and with the same correction source as the scan. {% endhint %} For the full datum workflow from scanner to control points and processing, see [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md). ### Heights in LiDAR360MLS 1. Copy the geoid for your country as a TIF file (latitude and longitude grid) into the **geoid** folder of the LiDAR360MLS installation. 2. In the **New Project Wizard**, open **Configure Coordinate System** and create a vertical coordinate system with **Datum Type:** **Gravity-related**. 3. Add the geoid under **Geoid Model:** with **Add Geoid**. 4. After you create the project, compare the ellipsoidal height with the grid elevation. If the two values differ, the geoid has been applied. Without a target coordinate system, LiDAR360MLS projects the result to WGS84 UTM. ### RTK-SLAM processing in LiDAR360MLS * For scenes other than Open Area, run **Process GNSS** with **External Input** and load the POS file from the Rover folder. LiDAR360MLS then uses the coordinate system stored in the RTK file. This page does not cover Open Area processing. * From LiDAR360MLS 9.1, **Optimize GNSS** (H300(B.00), O2, O2 Lite) helps against false fixes. It is off by default. * Check the minimum LiDAR360MLS version for your model in the model table above. ## Troubleshooting | Message or symptom | Cause | Fix | | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **CORS server login failed, please check IP and port** | Hostname not accepted or not resolved, or wrong port | Keep **port** `2101`. Replace the hostname with the IP fallback of the same region: North America `13.56.117.10`, Europe `3.73.41.96`, Australia `54.206.56.130`. | | **Differential data collection failed, please check CORS login username and password or if they are occupied by other devices** | Wrong mountpoint, wrong credentials, or the credentials are in use on another device | Check in this order: 1) **Source List** is exactly `AUTO`. 2) Username and password come from *RTK Credentials*, the username starts with `rtk`, both typed without spaces. 3) No other device is connected with the same credentials ([one connection per data stream](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices)). | | Login accepted, but no corrections arrive | The caster has no position from the scanner (NMEA GGA), so `AUTO` cannot assign a base station | Stay outdoors with open sky, wait for satellites and tap **SUBMIT** again. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). If corrections still do not arrive, send your RTK username, the scanner model and the time of the attempt to . RTKdata's session logs show whether the scanner's position reached the caster. | | **Please turn on the mobile data.** | O2, O2 Lite or SE RTK on the phone hotspot: the phone has no mobile data connection | Switch mobile data on, keep the hotspot running and tap **SUBMIT** again. | | **The current number of satellites is 0, and RTK is not supported.** | Configured indoors or without sky view | Go outside with open sky and submit again. | | **Please enter the source list** | **Source List** is empty | Type `AUTO`. | | **Abnormal network connection, please check the installation of the SIM card**, or no 4G service | Host Network: SIM seated wrongly, PIN, APN, no data left, or old module firmware | Check the SIM and its data plan, enter the **PIN code** or remove the PIN, set the APN from your carrier, update the module firmware. If the 4G light on the module is off, there is usually no network, no signal or no data volume. | | **Network communication abnormality, please check APN parameters or surrounding network environment** | Wrong APN | Enter the APN values from your carrier. | | **Abnormal network connection, please configure it in a place with good network signal** | The scanner is connected to a Wi-Fi network without internet access | Use the phone hotspot with mobile data on. If you connect through a portable Wi-Fi (relay mode), it has to be online itself. GreenValley's RTK instructions do not describe RTK over relay. | | **RTK is not enabled and does not support coordinate system selection** | RTK not configured yet | Submit the **RTK link** settings first, then create the project. | | O1 Lite only delivers a single point solution | Firmware V3.5.0 or later does not reuse the last RTK configuration | Open **RTK link** and tap **SUBMIT** before every scan. | | No network connection on iPhone | **Local Network** or location permission missing | Allow **Local Network** for the app and turn on location services. | | H300 or H120 shows no RTK working status | No RTK module or no backpack, vehicle or drone kit | Add the RTK module and a kit. | | `AUTO` appears in the list, but no fix | The sourcetable loads without a login | If the login fails, work through the **Differential data collection failed** row. If the login succeeds, work through the **Login accepted, but no corrections arrive** row. | | Stays on **Floating point solution** and does not reach **Fixed** | Limited sky view, too few satellites, or the nearest reference station is far away (GreenValley's O2 FAQ gives a typical RTK operating radius of 10 to 15 km) | Move to open sky and wait for enough satellites (GreenValley's manuals recommend at least 20 for initialization), check the [coverage map](/get-started/coverage-map.md) for your area, then see [Fix NTRIP Connection Issues](/support/common-connection-issues.md). If fixed solutions stay rare, add ground control points. | | Layered or shifted points between tall buildings | False RTK fixes | In LiDAR360MLS 9.1 or later, enable **Optimize GNSS**, remove false fixes and add ground control points. | For connection problems that are not specific to the LiGrip, see [Fix NTRIP Connection Issues](/support/common-connection-issues.md). ## Related Guides * [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md): all LiDAR scanner guides and the shared connection values * [NTRIP Server Settings](/get-started/network.md): regional hostnames, IP fallbacks, port and mountpoints * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): how `AUTO` uses the scanner's position to pick a base station, and the correction format * [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which datum `AUTO` delivers in each region * [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): scanner, control points and processing in one datum * [Understanding Heights](/get-started/understanding-heights.md): ellipsoidal and orthometric heights and geoid models * [Account & Credentials](/get-started/account-and-credentials.md): where to find your RTK credentials and how many devices can connect at once * [Coverage Map](/get-started/coverage-map.md): check RTKdata coverage for your working area before the job * [Fix NTRIP Connection Issues](/support/common-connection-issues.md): what to check when the login works but no corrections arrive * [Topcon HiPer VR / HR](/integration-hub/gnss-rovers-and-receivers/topcon-hiper-vr-hr.md): Topcon GNSS receivers in MAGNET Field, not MAGNET Flow * [Sokkia GCX3 / GRX3](/integration-hub/gnss-rovers-and-receivers/sokkia-gcx3-grx3.md): Sokkia GNSS receivers in MAGNET Field, not MAGNET Flow ## Frequently asked questions ### How do I enter a custom NTRIP caster in the GreenValley LiGrip RTK link screen? In the GreenValley app, tap **Start Operation** to open **Collection Management**, tap the gear icon, choose **RTK link** and leave **the server** on **Custom**. For RTKdata, enter the hostname for your region (`rtk.rtkdata.com` for North America, `eu.rtkdata.com` for Europe or `aus.rtkdata.com` for Australia) in **Domain Name/IP Address**, `2101` in **port**, `AUTO` in **Source List** and your RTK credentials, then tap **SUBMIT** outdoors. If the hostname is not accepted, use the IP fallback of the same region (`13.56.117.10`, `3.73.41.96` or `54.206.56.130`). ### Why does the GreenValley app say Please turn on the mobile data? When the LiGrip O2, O2 Lite or SE RTK uses your phone's hotspot, it reaches the RTKdata caster (or any other NTRIP caster) through the phone's mobile data, so the Android app blocks **SUBMIT** while the phone has no mobile data connection. Switch mobile data back on after connecting to the scanner and keep the hotspot running. ### Does the LiGrip H300 RTK module need its own SIM card? Yes. The LiGrip H300 reaches the RTKdata caster through a SIM card with a data plan in its RTK module (**Data link**: **Host Network**), and it also needs a backpack, vehicle or drone kit. **PIN code** and APN fields appear only for international RTK modules, and older module firmware did not accept EU SIM cards or SIM cards with a PIN. ### How do I set up network RTK on the Topcon CR-S1 or Sokkia SR-S1? In MAGNET Flow, tap **Start Operation**, the gear icon and **RTK Link**, answer **Yes** to the RTK question and enter `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia) in **Domain Name/IP Address**, port `2101`, **Source List** `AUTO` and your RTKdata credentials. Tap Enter on the keyboard after the mountpoint, then tap **Submit**. ### How do I apply a geoid in LiDAR360MLS for LiGrip RTK data? Copy the geoid for your country as a TIF file into the **geoid** folder of the LiDAR360MLS installation. In the **New Project Wizard**, open **Configure Coordinate System**, create a vertical system with **Datum Type:** **Gravity-related** and add the geoid with **Add Geoid**, then check that ellipsoidal height and grid elevation differ. Without a geoid, heights from RTKdata stay ellipsoidal. ## Quick reference * **Path:** GreenValley app > **Start Operation** (opens **Collection Management**) > gear icon > **RTK link** (MAGNET Flow: **Start Operation** > gear icon > **RTK Link** > **Yes**). * **Host and port:** `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia), port `2101`. IP fallback only if the hostname is not accepted: `13.56.117.10`, `3.73.41.96`, `54.206.56.130`. * **Mountpoint and login:** **Source List** `AUTO`, **Username** and **Password** from *RTK Credentials* (username starts with `rtk`). * **Position:** no GGA setting in the RTK link screen, so submit outdoors once the scanner has satellites in view. * **Internet:** phone hotspot with mobile data on (O2, O2 Lite, SE RTK), or a SIM with data in the RTK module (O1 Lite, H300, H120). * **Finish:** tap **SUBMIT** outdoors and wait for **RTK configuration successful (Fixed Solution)**. --- # 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/greenvalley-ligrip.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.