> 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/xgrids-lixel-l3.md). # XGRIDS Lixel L3 RTK Setup: NTRIP in LixelGO Set up RTKdata on the XGRIDS Lixel L3 with built-in RTK: Host, port 2101 and AUTO in LixelGO, why the L3 still needs internet for RTK and what the IP field is. The **XGRIDS Lixel L3** is a handheld SLAM LiDAR scanner with a built-in GNSS RTK module and its own 4.3-inch display. XGRIDS presented it at INTERGEO 2026 in Munich on 15 September 2026, in a 16-channel and a 32-channel version. This guide covers the Lixel L3 RTK setup with RTKdata NTRIP corrections: you enter the RTKdata details in the **LixelGO** app, and the AUTO mountpoint uses the scanner's position to pick the nearest reference station. {% hint style="warning" %} **Status, September 2026:** XGRIDS has not published a user manual for the Lixel L3 yet. The steps on this page follow the LixelGO **RTK Settings** screen that XGRIDS documents for the Lixel K2 and L2 Pro. This page will be updated as soon as L3 screens are available. {% endhint %} RTKdata values for LixelGO **RTK Settings**, tab **Account Settings**. Choose the server closest to your work area; all three servers share the same base station network (see [NTRIP Server Settings](/get-started/network.md)). {% tabs %} {% tab title="North America" %} * **Host** (domain): `rtk.rtkdata.com` * **Host** (IP fallback): `13.56.117.10`, only if LixelGO rejects the domain, or if **NTRIP** stays red with the domain although internet and credentials are correct * **Port:** `2101` * **Username** / **Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login * **Mountpoint** (ALL CAPS): `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Europe" %} * **Host** (domain): `eu.rtkdata.com` * **Host** (IP fallback): `3.73.41.96`, only if LixelGO rejects the domain, or if **NTRIP** stays red with the domain although internet and credentials are correct * **Port:** `2101` * **Username** / **Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login * **Mountpoint** (ALL CAPS): `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Australia" %} * **Host** (domain): `aus.rtkdata.com` * **Host** (IP fallback): `54.206.56.130`, only if LixelGO rejects the domain, or if **NTRIP** stays red with the domain although internet and credentials are correct * **Port:** `2101` * **Username** / **Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/), not your website login * **Mountpoint** (ALL CAPS): `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} All fields in **Account Settings** at a glance: | Field | Value | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Type** | `Custom` | | **Ellipsoid** | `WGS84` (in China: `CGCS2000`) | | **Host** | North America `rtk.rtkdata.com`, Europe `eu.rtkdata.com`, Australia `aus.rtkdata.com` | | **Host** (IP fallback) | North America `13.56.117.10`, Europe `3.73.41.96`, Australia `54.206.56.130` | | **Port** | `2101` | | **Mountpoint** | `AUTO` in capital letters (alternatives: `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84`) | | **Username** | From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). It starts with `rtk` and is not your website login | | **Password** | From *RTK Credentials*, not your website password | | **No password required** | Leave unchecked | ## What do you need before setting up RTK on the Lixel L3? To set up RTK on the XGRIDS Lixel L3 with RTKdata you need the scanner, a current LixelGO app on a supported phone, an internet connection for the corrections, active RTKdata credentials and RTKdata coverage at your site. * **XGRIDS Lixel L3**, charged, outdoors with a clear view of the sky * **LixelGO** in the current version: on iOS from the App Store, on Android from Google Play (LixelGO by XGRIDS LIMITED). Do not install the Android APK from the XGRIDS download page: in September 2026 it was still LixelGO 1.2.5. If LixelGO is not listed in Google Play in your country, ask your XGRIDS dealer for the current APK. LixelGO 2.1.2 was current in September 2026; its release notes do not mention the L3. * **Phone** with Android 12 or later or an iPhone 12 or later (XGRIDS minimum; phones with 4 GB RAM or less are currently not supported) * **Internet for corrections:** a phone with mobile data, or a Wi-Fi network with internet access * **RTKdata account** with active RTK credentials (username starts with `rtk`) * **RTKdata coverage** at your site: check the [Coverage Map](/get-started/coverage-map.md) before field work * **LixelStudio** for the coordinate transformation and your deliverables The labels on this page come from the English LixelGO interface. LixelGO switches its language automatically, so on a phone set to another language the labels differ. {% 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 %} ## Does the Lixel L3 have built-in RTK? Yes, the XGRIDS Lixel L3 has a built-in GNSS RTK module (XGRIDS specification: "RTK module: Supported (built-in)"), so it needs no add-on RTK module and takes its corrections from an NTRIP service such as RTKdata. * **GNSS:** BDS, GPS, GLONASS, Galileo, QZSS, IRNSS and SBAS * **RTK accuracy (XGRIDS specification):** 0.8 cm + 1 ppm horizontal, 1.5 cm + 1 ppm vertical, and about 2.5 cm (RMSE) absolute accuracy in real time * **Wireless:** the specification lists Wi-Fi and Bluetooth and no cellular modem, so corrections need an outside internet connection * **Survey pole:** the pole mount is mechanical and serves for capturing control points ("Mounts to survey poles you already own"). XGRIDS documents no input for corrections or positions from an external GNSS rover. ## Does the L3 need a phone or Wi-Fi with internet for RTK? Yes, the XGRIDS Lixel L3 needs an internet connection for RTKdata corrections, through a phone with mobile data or a Wi-Fi network with internet access, even though it can run a scan without a phone. XGRIDS states that the L3 "runs the scan independently, with no phone connection required". That covers scanning. Because the specification lists no cellular modem, the NTRIP corrections still have to come over a phone or a Wi-Fi network with internet. For the K2 and L2 Pro, XGRIDS documents these connection methods: | Method | How scanner and phone connect | Internet for NTRIP | | ----------------------------------------------- | ----------------------------------------- | ------------------------------------------------------------------------------- | | **Quick Connect Mode** (recommended by XGRIDS) | The phone joins the scanner's Wi-Fi | Mobile data on the phone, because the phone's Wi-Fi is connected to the scanner | | **Hotspot Mode** (iOS: **Direct Connect Mode**) | The scanner joins the phone's hotspot | Mobile data on the phone | | **Bridge Mode** | Scanner and phone share one Wi-Fi network | The shared network needs internet access | Internet column: XGRIDS FAQ, XGRIDS dealer guides and an earlier LixelGO version for Android (1.2.5). Which of these methods the L3 offers, and whether the L3 or LixelGO opens the NTRIP connection, has not been published yet. * **Switch mobile data on** before you connect. A tablet without mobile data gets no corrections in **Quick Connect Mode**. * **Keep LixelGO open** during the scan. For the K2 and L2 Pro, XGRIDS notes that "if the LixelGO app is closed, the device will lose the fixed solution". On Android, allow LixelGO to run in the background. * **Hotspot problems:** if the scanner does not join the phone's hotspot, work through the XGRIDS hotspot checklist in [XGRIDS Lixel K1, K2 & L2 Pro](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-k1-k2-l2-pro.md#hotspot-mode): **Hide Network** off, no VPN, a hotspot password of letters and numbers only, and the 5 GHz band if the connection still fails. ## Where do you enter the Lixel L3 RTK and NTRIP settings? You enter the RTKdata NTRIP settings for the XGRIDS Lixel L3 in the LixelGO app under **RTK Settings** > **Account Settings**, the screen XGRIDS documents for the Lixel K2 and L2 Pro: **Type** `Custom`, **Ellipsoid** `WGS84`, **Host** `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia), **Port** `2101`, **Mountpoint** `AUTO`, and the username and password from *RTK Credentials* in your RTKdata dashboard, with **GNSS Mode** set to **RTK** under **Advanced Settings**. XGRIDS has not published an L3 version of this screen. An XGRIDS dealer also places the L3 NTRIP settings in LixelGO, based on the sister models. The L3 display has a **Settings** menu with the entry **GNSS Configuration**. XGRIDS has not documented what this entry contains, so this guide uses LixelGO. {% stepper %} {% step %} ### Install LixelGO and sign in 1. Install the current **LixelGO** version from the App Store or Google Play, not the APK from the XGRIDS download page. On an iPhone, use the international LixelGO app, not the China edition. 2. Sign in with your XGRIDS account and activate the scanner if LixelGO asks for it. 3. Turn off any VPN on the phone. 4. Before the first scan, check the device time on the L3 display under **Settings** > **Timecode Calibration**, or in LixelGO. One distributor unit arrived set to UTC+8. {% endstep %} {% step %} ### Connect LixelGO to the L3 For the K2 and L2 Pro, XGRIDS documents three connection methods: **Quick Connect Mode** (recommended), **Hotspot Mode** (on iOS: **Direct Connect Mode**) and **Bridge Mode**. Which of them the L3 offers has not been published yet. Use the method LixelGO offers for your scanner and check the internet requirements in the section on phones and Wi-Fi above. {% hint style="warning" %} The field **IP** in **Step 3: Confirm device and phone share the same network** is the scanner's local network address. XGRIDS screenshots label this step **Step 3: Verify the device is on the same network as the mobile device**, with a **Verify** button. LixelGO fills the address in automatically. It is not the caster: the RTKdata details go only into **RTK Settings** > **Host**. {% endhint %} {% endstep %} {% step %} ### Open RTK Settings On the device screen in LixelGO, tap the satellite icon, or open **Settings** > **RTK Settings**. The screen has two tabs, **Account Settings** and **Advanced Settings**. The satellite tile shows the satellite count and the status, for example **None** or **Single**. {% endstep %} {% step %} ### Check the GNSS mode In **Advanced Settings**, set **GNSS Mode** to **RTK**, not **PPK**. In other modes LixelGO refuses the NTRIP login. Leave the satellite system selection at its default. XGRIDS notes: "After RTK changes, the device may need to be restarted." {% endstep %} {% step %} ### Enter your RTKdata account In **Account Settings**: 1. **Type:** `Custom`. **Qianxun SI** and **China Mobile** are services in China. 2. **Ellipsoid:** `WGS84` (in China: `CGCS2000`). Do not choose **OTHER**. 3. **Host:** the domain of your region, `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia). If LixelGO rejects it, or if **NTRIP** stays red with the domain although internet and credentials are correct, see [If LixelGO does not accept the domain](#if-lixelgo-does-not-accept-the-domain). 4. **Port:** `2101` 5. **Username** and **Password:** from *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). Type them instead of pasting, with no spaces at the start or end. 6. **No password required:** leave unchecked. 7. **Mountpoint:** type `AUTO` in capital letters. If you load the mountpoint list instead, pick `AUTO` from it. Use port `2101` only. An earlier LixelGO version for Android (1.2.5) switches to an encrypted TLS connection automatically on port 2102. For the K2 and L2 Pro, XGRIDS advises waiting about five minutes after you change **Ellipsoid** before you start work. One set of credentials allows one connection at a time. 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). {% hint style="info" %} The RTKdata sourcetable loads without a login. If LixelGO shows a mountpoint list, that proves neither your credentials nor a correction stream (checked on 25 September 2026). Only **NTRIP** in green and the status **Fixed** confirm the connection. {% endhint %} {% endstep %} {% step %} ### Save the profile Tap the save icon. In the **Save Configuration** dialog, pick a slot such as **Configuration 1** and tap **Save**. LixelGO stores up to five profiles and logs in automatically with the saved one next time. {% endstep %} {% step %} ### Connect under open sky 1. Go outside with a clear view of the sky and wait until the satellite tile shows **Single**. 2. Tap **Connect**. 3. The indicators **RTK** and **NTRIP** turn green. 4. Wait for the status **Fixed** before you start the scan. Under open sky, most RTKdata users reach an RTK fix in 5 to 20 seconds. If **Fixed** does not appear within 90 seconds, work through [Troubleshooting](#troubleshooting). {% hint style="warning" %} **AUTO needs the scanner's position.** The AUTO mountpoint picks the base station from the position the device sends (NMEA GGA). Without it, the login succeeds, but no corrections arrive. The LixelGO **RTK Settings** screen documented for the K2 and L2 Pro has no GGA switch, so there is nothing to turn on. XGRIDS has not published how the L3 sends its position. An earlier LixelGO version for Android (1.2.5) sends it at the earliest 5 seconds after login, so a short wait after **Connect** is normal. Always connect under open sky and wait for **Single** first. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). {% endhint %} {% endstep %} {% endstepper %} ## What is the IP field in the LixelGO connection wizard? In the LixelGO connection wizard, the field **IP** under **Step 3: Confirm device and phone share the same network** holds the Lixel scanner's local network address, which LixelGO fills in automatically, and the RTKdata caster address does not go there. XGRIDS describes it this way: "After the Wi-Fi is configured, the IP address is written automatically." In XGRIDS documentation screenshots the same step reads **Step 3: Verify the device is on the same network as the mobile device**, with a **Verify** button. Leave the entry as it is. In **Bridge Mode**, XGRIDS support advises restarting the phone's hotspot or the phone if this address looks like X.X.1.X. The RTKdata caster address belongs only in **RTK Settings** > **Host**. In every LixelGO RTK screen XGRIDS has documented, this field is called **Host**, and an XGRIDS screenshot shows a hostname typed into it. An earlier LixelGO version for Android (1.2.5) also resolves hostnames. Enter the domain of your region there, for example `eu.rtkdata.com` in Europe. If LixelGO answers with "Invalid host or port" or "Invalid IP service address", or if **NTRIP** stays red with the domain although internet and credentials are correct, see [If LixelGO does not accept the domain](#if-lixelgo-does-not-accept-the-domain). ## How do you know the L3 has a usable fix? The XGRIDS Lixel L3 has a usable RTKdata fix when LixelGO shows the indicators **RTK** and **NTRIP** in green and the status **Fixed**, with more than 10 satellites (XGRIDS dealer guidance), before you start the scan. This is the status display XGRIDS documents for the K2 and L2 Pro. The status moves from **None** to **Single**, then to float, then to **Fixed**. Green indicators alone are not enough: start scanning only at **Fixed**. XGRIDS has not published scanning limits for the L3. For the Lixel K2, which also has built-in RTK, XGRIDS specifies: * Walk more than 10 m while the status is **Fixed**. * Keep stretches without a fix under 50 m. * Collect more than 100 valid RTK points for the transformation in LixelStudio. * Keep the tilt within 15 degrees while walking. Do not switch NTRIP accounts during a scan; LixelGO warns: "Switching NTRIP accounts during scan affects accuracy." When the job is done, tap **Disconnect**. ## Which ellipsoid and coordinate system should you use with AUTO? With the RTKdata AUTO mountpoint, set **Ellipsoid** to **WGS84** in LixelGO for the XGRIDS Lixel L3 (**CGCS2000** in China, never **OTHER**) and choose the projected coordinate system of your regional datum by EPSG code in LixelStudio. {% hint style="info" %} **Datum with AUTO:** use AUTO, keep **Ellipsoid** on **WGS84**, do not apply a WGS84-to-regional transformation, and check one control point. AUTO delivers corrections in your region's local datum, for example NAD83(2011) in the USA, NAD83(CSRS)v7 in Canada, ETRS89 (realization ETRF2000) in Europe and GDA2020 in Australia. The datum for every region is listed in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md). LixelGO still shows WGS84: here the field names the ellipsoid setting of the screen, not the reference frame. {% endhint %} XGRIDS specifies real-time coordinate conversion on the L3 for WGS84 and CGCS2000 only and has not published which projection this real-time output uses, so take your deliverables from LixelStudio. ETRS89, NAD83 and GDA2020 use the GRS80 ellipsoid, which is nearly identical to WGS84, and XGRIDS itself uses **Custom** with WGS84 for the national datums JGD2011 and KGD2002 in its RTK Setting Guide. LixelStudio handles L3 data the same way as data from the sister models; the full steps are in [XGRIDS Lixel K1, K2 & L2 Pro](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-k1-k2-l2-pro.md#georeference-the-scan-in-lixelstudio). What matters with AUTO: * Leave **High-Precision Optimization** off in **Project Processing**. XGRIDS marks it as mutually exclusive with **Coordinate Transformation**. * In **Coordinate Transformation**, enable GNSS with **RTK Module** as the source and choose the projected system of your regional datum by EPSG code as the target. If LixelStudio asks for seven transformation parameters, load a text file containing `0 0 0 0 0 0 1`, the null transformation from the XGRIDS RTK Setting Guide, and no official WGS84-to-regional parameters. * Heights stay ellipsoidal, so control points for **Accuracy Check** need ellipsoidal heights in the same coordinate system as the GNSS target. See [Understanding Heights](/get-started/understanding-heights.md) for geoid models. XGRIDS dealer documentation states that the LixelStudio projection engine does not currently support zones based on Lambert Conformal Conic, which rules out many US State Plane zones. If your deliverable needs such a zone, process in UTM or a Transverse Mercator zone of your regional datum and convert in your GIS or CAD software. Use `AUTO_WGS84` or `AUTO_ITRF2020` only when the deliverable must be in a global frame. `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) in the middle of the current year. LixelStudio then needs a real datum transformation into the target system, and the null transformation above no longer applies. For the full workflow from RTK trajectory to a georeferenced point cloud, see [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md). ## Troubleshooting The L3 has its RTK module built in, so checks for plug-in RTK modules do not apply. | Problem | Cause | Fix | | ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **RTK** green, **NTRIP** red | The NTRIP connection has no internet, or credentials or mountpoint are wrong | Check mobile data on the phone (**Quick Connect Mode**) or internet on the shared Wi-Fi (**Bridge Mode**). Then retype username and password, then check the mountpoint `AUTO`. Tap **Disconnect**, then **Connect**. If **NTRIP** stays red and the mountpoint list does not load with the domain, enter the IP fallback of your region in **Host**. | | **NTRIP** red in **Bridge Mode**, although the Wi-Fi has internet | The network blocks outbound TCP on port 2101, for example through a firewall or VPN | Allow outbound TCP on port `2101` on that network, or connect through the phone's mobile data instead. | | Mountpoint list loads, **NTRIP** stays red | The RTKdata sourcetable loads without a login | A visible list proves neither credentials nor a correction stream. Retype the credentials from *RTK Credentials*, without spaces at the start or end. | | No corrections with the mountpoint typed by hand | Mountpoint in lower case or misspelled | Type `AUTO` in capital letters. Mountpoint names are case-sensitive. | | "Invalid host or port" or "Invalid IP service address" | LixelGO does not accept the host entry | Check the spelling of the domain of your region and the port `2101`. If the message stays, see [If LixelGO does not accept the domain](#if-lixelgo-does-not-accept-the-domain) below. | | LixelGO refuses the NTRIP login | **GNSS Mode** is set to **PPK** | In **Advanced Settings**, set **GNSS Mode** to **RTK** and restart the scanner if asked. | | Connected, but no **Fixed** | Obstructed sky, few satellites, or the connection was opened indoors, so the caster had no usable position | Move into open sky. Tap **Disconnect**, wait for **Single**, tap **Connect**. Start scanning at **Fixed** with more than 10 satellites. | | Connection drops again and again | More devices are connected at the same time than your account has data streams, or LixelGO was closed | Every device connected at the same time needs its own data stream ([Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices)). Keep LixelGO open during the scan. | | Scanner does not join the phone's hotspot | Hidden network, VPN or special characters | Turn off **Hide Network** and any VPN, use letters and numbers only, try the 5 GHz band. | | Heights differ from benchmarks by many meters | RTKdata delivers ellipsoidal heights | Apply a geoid in LixelStudio. See [Understanding Heights](/get-started/understanding-heights.md). | | Point cloud not georeferenced in LixelStudio | **High-Precision Optimization** was on, or too little walking while **Fixed** | Turn **High-Precision Optimization** off. In the field, walk more than 10 m while **Fixed**. | ### Why is NTRIP red on the Lixel L3 while RTK is green? On the XGRIDS Lixel L3, **RTK** green and **NTRIP** red means the NTRIP connection to the RTKdata caster is not working: check mobile data on the phone (**Quick Connect Mode**) or internet on the shared Wi-Fi (**Bridge Mode**), then the username and password from *RTK Credentials*, then the mountpoint `AUTO`, then the IP fallback of your region in **Host**. For the L2 Pro, XGRIDS explains this combination as "The NTRIP network is not connected. Check whether the phone has internet access", and an XGRIDS dealer applies the same status logic to the L3. Tap **Disconnect** before each change and **Connect** again outdoors after **Single**. ### If LixelGO does not accept the domain The domain of your region stays the recommended entry in **Host**. Enter the IP fallback of your region in **Host** instead in either of these cases: * LixelGO still shows "Invalid host or port" or "Invalid IP service address" after you checked the spelling. * **NTRIP** stays red with the domain although the internet connection and the credentials are correct, for example when the mountpoint list does not load with the domain. The IP fallbacks are `13.56.117.10` (North America), `3.73.41.96` (Europe) and `54.206.56.130` (Australia). **Port** `2101` and **Mountpoint** `AUTO` stay the same. For connection problems that are not specific to the L3, see [Fix NTRIP Connection Issues](/support/common-connection-issues.md). ## Frequently asked questions ### Does the XGRIDS Lixel L3 have integrated RTK? Yes, the XGRIDS Lixel L3 has an integrated GNSS RTK module, listed by XGRIDS as "RTK module: Supported (built-in)". It still needs NTRIP corrections over an internet connection to reach a fix, for example from RTKdata with the mountpoint `AUTO` on port `2101`. ### Can the Lixel L3 use my own NTRIP correction service? Yes, LixelGO has the account type **Custom** for correction services outside mainland China, and XGRIDS tells users to get the RTK account from their GNSS service provider. For RTKdata, enter the domain of your region (for example `eu.rtkdata.com` in Europe), port `2101` and the mountpoint `AUTO`. 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). XGRIDS has not published L3-specific screens yet. ### Does the Lixel L3 NTRIP field only accept an IP address? No published source says that the Lixel L3 only accepts an IP address. In LixelGO the caster field is called **Host**, and XGRIDS documentation shows a hostname typed into it; the field labelled **IP** in the connection wizard is the scanner's local address and is filled in automatically. For RTKdata, enter `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia) in **Host**, and use the IP fallback `13.56.117.10`, `3.73.41.96` or `54.206.56.130` only if LixelGO rejects the domain, or if **NTRIP** stays red with the domain although internet and credentials are correct. ### Does the Lixel L3 work without a phone? The Lixel L3 scans without a phone, but RTKdata corrections still need internet, from a phone with mobile data or a Wi-Fi network with internet access. XGRIDS has not published whether the L3 can fetch corrections without LixelGO. ### Which coordinate systems does the Lixel L3 support in real time? XGRIDS specifies real-time coordinate conversion on the Lixel L3 for WGS84 and CGCS2000 only. With the RTKdata AUTO mountpoint, set **Ellipsoid** to **WGS84** (**CGCS2000** in China) and assign the projected system of your regional datum in LixelStudio. ## Related Guides * [LiDAR & SLAM Scanner RTK Setup](/integration-hub/lidar-scanners-and-mobile-mapping.md): all scanner guides and the common RTKdata settings * [XGRIDS Lixel K1, K2 & L2 Pro](/integration-hub/lidar-scanners-and-mobile-mapping/xgrids-lixel-k1-k2-l2-pro.md): the same LixelGO RTK Settings screen, with LixelStudio details * [NTRIP Server Settings](/get-started/network.md): the regional hosts, IP fallbacks, port and mountpoints in one table * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why the caster needs the scanner's position before it sends corrections * [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which regional datum AUTO delivers in each country * [Georeference SLAM Point Clouds with RTK](/integration-hub/lidar-scanners-and-mobile-mapping/georeferencing-slam-point-clouds-with-rtk.md): the datum workflow for SLAM scans from field to deliverable * [Understanding Heights](/get-started/understanding-heights.md): why RTKdata delivers ellipsoidal heights and how to apply a geoid * [Account & Credentials](/get-started/account-and-credentials.md): where to find RTK Credentials, and one connection per data stream * [Fix NTRIP Connection Issues](/support/common-connection-issues.md): general checks when corrections do not arrive or the fix stays on float * [Coverage Map](/get-started/coverage-map.md): check RTKdata coverage at your site before field work ## Quick reference * **LixelGO:** current version from the App Store or Google Play; satellite icon or **Settings** > **RTK Settings**; in **Advanced Settings**, **GNSS Mode** = **RTK** * **Account Settings:** **Type** `Custom`, **Ellipsoid** `WGS84`, **Host** `rtk.rtkdata.com` / `eu.rtkdata.com` / `aus.rtkdata.com`, **Port** `2101`, **Mountpoint** `AUTO`, **Username** and **Password** from *RTK Credentials* * **Internet:** phone with mobile data or Wi-Fi with internet access; keep LixelGO open during the scan * **GGA:** no switch in LixelGO, connect outdoors after **Single** * **Fix:** outdoors, wait for **Single**, tap **Connect**, **RTK** and **NTRIP** green, scan only at **Fixed** * **LixelStudio:** EPSG target in your regional datum, `0 0 0 0 0 0 1` if seven parameters are requested, **High-Precision Optimization** off, heights ellipsoidal --- # 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/xgrids-lixel-l3.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.