> 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/gnss-rovers-and-receivers/woncan-litesurvey.md). # Woncan LiteSurvey RTK Setup: NTRIP in LiteSurvey Pro Set up RTKdata NTRIP on the Woncan LiteSurvey 2, 2 Pro and 2 mini in LiteSurvey Pro: host, port 2101, AUTO from the mountpoint list, fix and mock location. This page covers the Woncan LiteSurvey RTK setup with RTKdata NTRIP corrections for the **LiteSurvey 2** and the **LiteSurvey 2 Pro**, with notes on the **LiteSurvey 2 mini**. The LiteSurvey receivers are GNSS RTK receivers for smartphones and tablets, not LiDAR or SLAM scanners. The LiteSurvey 2 and 2 Pro connect wirelessly to the **LiteSurvey Pro** app on iOS, iPadOS or Android. The LiteSurvey 2 mini plugs into the phone's USB-C port, and the Google Play listing of LiteSurvey Pro names Bluetooth or USB as the connection on Android. In every case the app runs the NTRIP connection over the phone's internet connection. The LiDAR link is the phone, not the receiver: on supported receiver models with the required mounting hardware, AR-assisted photo measurement in LiteSurvey Pro uses a LiDAR-equipped iPhone or iPad, or ARCore on compatible Android devices, and the LiteSurvey receiver supplies the RTK position. Woncan: "Availability depends on the Apple device, receiver model, and accessories." For RTKdata you add one NTRIP account in LiteSurvey Pro and pick `AUTO` from the mountpoint list. Enter these values in LiteSurvey Pro under **Settings** > **GNSS corrections** > **+ Add NTRIP 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 **Host address / IP** (preferred) * **Host (IP fallback):** `13.56.117.10` in **Host address / IP**, only if the host name does not connect * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/) in **Username** and **Password** under **Account details**, not your website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended), tapped in the **Mountpoint** list, or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Europe" %} * **Host (domain):** `eu.rtkdata.com` in **Host address / IP** (preferred) * **Host (IP fallback):** `3.73.41.96` in **Host address / IP**, only if the host name does not connect * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/) in **Username** and **Password** under **Account details**, not your website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended), tapped in the **Mountpoint** list, or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Australia" %} * **Host (domain):** `aus.rtkdata.com` in **Host address / IP** (preferred) * **Host (IP fallback):** `54.206.56.130` in **Host address / IP**, only if the host name does not connect * **Port:** `2101` in **Port** * **Username / Password:** From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/) in **Username** and **Password** under **Account details**, not your website login * **Mountpoint (ALL CAPS):** `AUTO` (recommended), tapped in the **Mountpoint** list, or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} All LiteSurvey Pro values at a glance: | Field | Value | | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Account name** | Any profile name, for example `RTKdata Europe`. This is not your username. | | Drop-down below **Account name** | **NTRIP** | | **Host address / IP**, North America | `rtk.rtkdata.com`, IP fallback `13.56.117.10` | | **Host address / IP**, Europe | `eu.rtkdata.com`, IP fallback `3.73.41.96` | | **Host address / IP**, Australia | `aus.rtkdata.com`, IP fallback `54.206.56.130` | | **Port** | `2101` | | **Mountpoint** | `AUTO` in capital letters, tapped in the list after the refresh icon. 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 | **Host address / IP** is a text field, and Woncan's own setup video enters a host name there and reaches **Fixed**. Enter the host name first, without `http://` and without a port, and use the IP fallback of the same region only if the host name does not connect. The NTRIP form in LiteSurvey Pro has no GGA option: give the receiver a position outdoors before you connect, as described in the steps below. ## What do you need before connecting a LiteSurvey receiver? To connect a Woncan LiteSurvey 2, 2 Pro or 2 mini to RTKdata you need the receiver, the LiteSurvey Pro app on a phone or tablet with internet access, active RTKdata NTRIP credentials and RTKdata coverage at your site. * **LiteSurvey receiver**, charged. The LiteSurvey 2 mini draws its power from the phone. * **LiteSurvey Pro** from the [App Store](https://apps.apple.com/us/app/litesurvey-pro/id6503436604) (iOS or iPadOS 16 or later, iPhone and iPad) or [Google Play](https://play.google.com/store/apps/details?id=com.woncan.litegps.play) (Android), published by Woncan (Hong Kong) Limited. Do not install the app "Lite-Survey": it is a separate Woncan app for the China market. * **Internet on the phone**, over mobile data or Wi-Fi. LiteSurvey Pro runs the NTRIP connection over the phone's network connection and passes the corrections to the receiver. * **RTKdata account** with active RTK credentials (username starts with `rtk`). Every receiver that is connected at the same time needs its own data stream. * **Coverage at your site.** Check the [RTKdata coverage map](/get-started/coverage-map.md) before the job. * **Open sky** for the first position and the fix. {% 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 LiteSurvey models this page covers | Model | Connection to the phone | Notes | | ----------------- | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | LiteSurvey 2 | Wireless: Bluetooth on Android, MFi on iOS | Sold as **Dual-band L1/L5** and **Multi-band L1/L2/L5** variants. The NTRIP setup in LiteSurvey Pro is the same. | | LiteSurvey 2 Pro | Wireless: Bluetooth on Android, MFi on iOS | Shows as LSK-A650 under **Settings** > **Device information** | | LiteSurvey 2 mini | USB-C plug, powered by the phone | LiteSurvey Pro for Android connects receivers "through Bluetooth or USB". This page does not cover the USB connection steps. For the mini on an iPhone, check with Woncan first. | | LiteSurvey Range | Not covered | Listed as "Coming soon" in the Woncan shop in September 2026 | This page does not cover the first-generation LiteSurvey GPS or the Lite RTK receivers that Woncan sells in China with the separate Lite-Survey app. ### App version and firmware Woncan rebuilt LiteSurvey Pro in version 2.0.0 (31 August 2026), including the device connectivity, and released 2.0.1 on 11 September 2026. The NTRIP screens described on this page come from Woncan videos recorded with LiteSurvey Pro 1.x, so labels and paths in 2.0.1 can differ. Update LiteSurvey Pro before the first job. The labels on this page come from the English LiteSurvey Pro interface. The app is available in other languages, and the **Settings** tab has a **Language** entry. Woncan's product pages and videos list no receiver firmware version numbers. To update the firmware, keep the receiver connected and the phone online: 1. Open **Settings** > **Device information** > **Firmware update**. **Device information** only appears in **Settings** while a receiver is connected. 2. Keep the receiver close to the phone until the progress reaches 100%. 3. Follow the **Notice** that LiteSurvey Pro shows afterwards: power the receiver off and on, wait about 10 seconds and do not switch it off while the LEDs are dark. It is ready when the LEDs flash. If it does not reconnect, remove it in the phone's Bluetooth settings and pair it again. **Confirm** closes the notice. Current app version when this page was written: LiteSurvey Pro 2.0.1 (September 2026). ## How do you pair the receiver with LiteSurvey Pro? Before RTKdata corrections can reach a LiteSurvey 2 or 2 Pro, you pair the receiver with LiteSurvey Pro: switch it on, tap **Tap to connect device** in the **Map** tab and pick the receiver in the system dialog of iOS or Android. {% tabs %} {% tab title="iOS / iPadOS" %} 1. Switch the receiver on. 2. In LiteSurvey Pro, open **Map** and tap **Tap to connect device**. 3. iOS shows **Select An Accessory**. Pick your receiver. 4. If the receiver is not listed, pair it in the iOS Settings under Bluetooth first. LiteSurvey Pro notes that device names begin with "LSG" or "LSK". {% endtab %} {% tab title="Android" %} 1. Switch the receiver on. 2. In LiteSurvey Pro, open **Map** and tap **Tap to connect device**. 3. Android shows **Choose a device to be managed by LiteSurvey Pro**. Pick your receiver, not **Don't allow**. {% endtab %} {% endtabs %} **LiteSurvey 2 mini:** plug it into the USB-C port of an Android phone and open LiteSurvey Pro, which connects receivers "through Bluetooth or USB" on Android according to its Google Play listing. Woncan's videos do not show the USB steps, so this page does not describe them. If LiteSurvey Pro does not detect the mini, contact Woncan support. The NTRIP account in the next section is set up under **Settings** > **GNSS corrections** in the same way, however the receiver is connected. **Device information** and **Mock location** only appear in **Settings** while a receiver is connected, so pair the receiver before you look for them. ## How does the Woncan LiteSurvey RTK setup work in GNSS corrections? For the Woncan LiteSurvey RTK setup you add RTKdata as an NTRIP account in LiteSurvey Pro under **Settings** > **GNSS corrections** > **+ Add NTRIP account**: **Host address / IP** `rtk.rtkdata.com` (North America), `eu.rtkdata.com` (Europe) or `aus.rtkdata.com` (Australia), **Port** `2101`, **Mountpoint** `AUTO` from the list, and **Username** and **Password** from *RTK Credentials* in your RTKdata dashboard. {% stepper %} {% step %} ### Wait for a position outdoors 1. Take the paired receiver outdoors under open sky. 2. Wait until the top of the map shows coordinates, the satellite count and the status **Single**. 3. Before a profile is connected, the correction tile on the map shows **N/A** on Android and **Disconnect** in the iOS app 1.x. {% hint style="info" %} **AUTO needs your receiver's position.** The caster picks the nearest base station from the position your device 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). LiteSurvey Pro has no GGA option in the NTRIP form, so wait outdoors until the map shows **Single** with coordinates before you connect. {% endhint %} {% endstep %} {% step %} ### Open GNSS corrections Open the **Settings** tab and tap **GNSS corrections**. In Woncan's Android video, a tap on the **N/A** tile on the map opens the same page. {% endstep %} {% step %} ### Add the NTRIP account 1. Tap **+ Add NTRIP account**. 2. **Account name:** a name for the profile, for example `RTKdata Europe`. This is only the profile name, not your username. 3. Leave the drop-down below it on **NTRIP**. 4. Under **Host Configuration**, **Host address / IP:** 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 only if the host name does not connect. 5. **Port:** `2101`. {% endstep %} {% step %} ### Pick AUTO from the mountpoint list 1. With **Host address / IP** and **Port** filled in, tap the refresh icon next to **Mountpoint**. LiteSurvey Pro shows **Mountpoint list retrieved** and opens the list. 2. Tap `AUTO` in the list. The field does not fill itself, so check afterwards that **Mountpoint** reads exactly `AUTO`. 3. The list can show more entries than `AUTO`, `AUTO_ITRF2020`, `AUTO_ITRF2014` and `AUTO_WGS84`: pick `AUTO` unless your project needs one of the global frames. {% hint style="info" %} The RTKdata mountpoint list loads without a login. A visible list with `AUTO` proves neither your credentials nor a running correction stream. {% endhint %} {% endstep %} {% step %} ### Enter your credentials and save 1. Under **Account details**, **Username:** from *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). It starts with `rtk`. 2. **Password:** from *RTK Credentials*, not your website password. 3. Tap **Save**. {% 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 receiver 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 %} ### Connect the RTKdata profile 1. Back in **GNSS corrections**, tap the RTKdata profile under **NTRIP accounts (Tap account to connect)**. 2. Check that the RTKdata profile now sits at the top with **Disconnect**. LiteSurvey Pro reconnects on its own (Woncan: "The device will automatically reconnect to your phone and the RTK network."), so a profile you used before can stay active if you skip this check. 3. To change the profile later, tap the pencil icon on it. {% hint style="warning" %} **NTRIP connection success does not prove a valid login.** LiteSurvey Pro can show **NTRIP connection success** while no corrections arrive, for example when **Username** is empty or the `rtk` username only went into **Account name**. Only **Float** or **Fixed** with a running correction age on the map tile counts. {% endhint %} {% endstep %} {% endstepper %} ## How do you know the LiteSurvey has an RTK fix? A LiteSurvey 2, 2 Pro or 2 mini has an RTK fix from RTKdata when the map in LiteSurvey Pro shows **Fixed** with centimetre values and the correction tile shows a running correction age. * The status moves from **Single** to **Float** to **Fixed**. Woncan's screens show values such as `Fixed 0.020 m/0.030 m`. * In LiteSurvey Pro 2.0 the correction tile shows **Ntrip** and the correction age, for example 1.0 s. In app 1.x it shows the profile name and the correction age. * If the status stays **Single** and the tile shows no correction age, no corrections arrive, even after **NTRIP connection success**. Work through the checklist in [Why does LiteSurvey Pro say NTRIP connection success but stay on Single?](#why-does-litesurvey-pro-say-ntrip-connection-success-but-stay-on-single) * The NTRIP client runs in LiteSurvey Pro. Woncan: "Keep the app running in the background." When the app is closed, the receiver gets no corrections. On Android, turn battery optimisation off for LiteSurvey Pro, so that Android does not stop the app when the screen turns off. ## How do other apps use the LiteSurvey RTK position? Other apps get the LiteSurvey RTK position with RTKdata corrections through LiteSurvey Pro: on Android through mock location, on iOS through MFi. In both cases LiteSurvey Pro stays the NTRIP client and has to keep running. {% tabs %} {% tab title="Android" %} 1. In the Android developer options, set **Select mock location app** to LiteSurvey Pro. 2. In LiteSurvey Pro, open **Settings** and turn on **Mock location**. The row only appears while a receiver is connected. 3. Keep LiteSurvey Pro running in the background, then open the other app. Both settings are needed. With only one of them, other apps keep using the phone's own GPS. {% endtab %} {% tab title="iOS / iPadOS" %} Woncan: "Through MFi, iOS automatically replaces internal GPS with RTK coordinates". There is no mock location setting on iOS. 1. Pair the receiver and connect the RTKdata profile in LiteSurvey Pro. 2. Keep LiteSurvey Pro running in the background, then open the other app. 3. Other apps still display an accuracy of about 5 m. Woncan: "iOS limits UI display accuracy to 5m" and "Actual positioning achieves centimeter-level precision". Check the RTK status in LiteSurvey Pro, not the accuracy shown in the other app. {% endtab %} {% endtabs %} If the other app is Esri Field Maps, set up a location profile. Esri states: "The default profile assumes that provided locations are in the WGS 1984 coordinate system." With `AUTO` the positions arrive in your regional datum, so give the location profile the datum that `AUTO` delivers in your region, see the next section, and check one control point. ## Which coordinate system should the project use with AUTO? With the RTKdata `AUTO` mountpoint, a LiteSurvey Pro project should use a coordinate system on the regional datum that `AUTO` delivers at your position, chosen by EPSG code under **Project details** > **Map Projection**, with exactly one transformation and a check at a known control point. {% hint style="info" %} **Use AUTO, pick an EPSG system on your regional datum, do not use Helmert 7-params for a WGS84 conversion, check one control point.** {% 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 and GDA2020 in Australia. For regions without a listed regional datum, `AUTO` falls back to WGS84(G2139) at the mid-year epoch. The full list per country is in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md). `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver ITRF at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) at the mid-year epoch. Use them only when the deliverable must be in a global frame, and keep one mountpoint per project. Steps with the labels from LiteSurvey Pro 1.x (check them in 2.0.1): 1. Open the project, then **Project details** > **Map Projection**. 2. Tap **Projection not set** and choose the option to browse EPSG parameters near the project location, then **Select location** > **Confirm**. The alternatives are **Copy parameters from existing project** and **Enter parameters manually**. 3. In **Edit projection parameters**, check the EPSG system, for example **Ellipsoid**, **Map Projection**, **Latitude of natural origin (°)** and **Longitude of natural origin (°)**, and tap **Save**. Pick a projected system on your regional datum, for example EPSG 25832 (ETRS89 / UTM zone 32N) or 6346 (NAD83(2011) / UTM zone 17N). 4. **Map Projection** then shows **Ellipsoid**, **Projection method** and **Helmert 7-params**. With `AUTO`, do not use **Helmert 7-params** for an extra WGS84-to-national transformation: the corrections already arrive in the regional datum, and a second transformation shifts the points again. Use exactly one transformation. 5. Measure one known control point. A consistent offset of 50 cm to 1 m points to a datum mismatch, not an accuracy problem, see [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md). ### Heights and RTK photos * RTKdata delivers ellipsoidal heights. For heights above sea level, apply a geoid model: the App Store description of LiteSurvey Pro lists "supported geoid models" for projects. The difference can be 10 to 50+ m, see [Understanding Heights](/get-started/understanding-heights.md). * In Woncan's geotagging video, the EXIF altitude of an RTK photo is the ellipsoidal height, and with `AUTO` the photo position is in your regional datum. Set the frame and the height type in your photogrammetry or GIS software to match, see [Matching the Frame in Your Processing Software](/get-started/coordinate-systems-and-datums.md#matching-the-frame-in-your-processing-software). * If heights at a control point are off although LiteSurvey Pro shows **Fixed**, check the pole height and, on receivers with tilt compensation, the tilt setup in LiteSurvey Pro before you look at the datum. * Export RTK photos directly from LiteSurvey Pro through file or email apps. Woncan: "Avoid messaging apps to prevent losing high-precision positioning data from image compression". ## Why does LiteSurvey Pro say NTRIP connection success but stay on Single? LiteSurvey Pro can show **NTRIP connection success** without a valid RTKdata login or correction stream, so only **Float** or **Fixed** with a running correction age on the map tile proves that corrections arrive. The usual causes are an empty **Username**, the `rtk` username in **Account name** instead of **Username**, an empty or wrong **Mountpoint**, or a connection made before the receiver had a position. The RTKdata mountpoint list loads without a login, so a loaded list and a success message can appear with wrong or missing credentials. Work through it in this order: 1. Tap **Disconnect** on the RTKdata profile. 2. Open the profile with the pencil icon and check that your `rtk` username is in **Username** under **Account details**, not only in **Account name**. 3. Retype **Username** and **Password** from *RTK Credentials*, without spaces and without automatic capitals. 4. Check that **Mountpoint** reads exactly `AUTO`. If it is empty, tap the refresh icon and tap `AUTO` in the list. 5. Check **Host address / IP** (the host name of your region, no `http://`, no port) and **Port** `2101`. If the mountpoint list does not load with the host name, enter the IP fallback of your region (`13.56.117.10` North America, `3.73.41.96` Europe, `54.206.56.130` Australia). 6. Tap **Save**, go outdoors and wait until the map shows **Single** with coordinates. 7. Tap the RTKdata profile under **NTRIP accounts (Tap account to connect)** and check that it sits at the top with **Disconnect**. 8. If another device uses the same credentials at the same time, disconnect it or add a data stream. ## Troubleshooting | What you see | Likely cause | What to do | | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **NTRIP connection success**, status stays **Single**, no correction age | Empty **Username**, username only in **Account name**, empty or wrong **Mountpoint**, or connected before the receiver had a position | Follow the checklist in the previous section, in that order. | | An error message when you tap the RTKdata profile, instead of **NTRIP connection success** | Wrong **Password** for your `rtk` username | Retype **Password** from *RTK Credentials*, not your website password, and tap **Save**. | | Status stays **Float** while the correction age keeps running | Blocked sky or multipath, or corrections the receiver cannot fully use | Move to open sky away from buildings and trees, hold the receiver still and wait. If it stays on **Float**, send the model and variant (for example LiteSurvey 2 **Dual-band L1/L5** or **Multi-band L1/L2/L5**, or LiteSurvey 2 Pro), the time and your location to . | | Correction tile shows **N/A** | No NTRIP profile connected yet | Outdoors, wait for **Single**, then tap the RTKdata profile under **NTRIP accounts (Tap account to connect)**. | | **Mountpoint** stays empty after the refresh | LiteSurvey Pro does not fill the field itself | Tap `AUTO` in the list and check the field. | | Mountpoint list does not load | **Host address / IP** or **Port** empty or wrong, or no internet on the phone | Check the host name for typos, with no `http://` and no port, and **Port** `2101`. Check the phone's mobile data or Wi-Fi. If the list still does not load, enter the IP fallback of your region. | | Mountpoint list loads on one network but not on another, for example on mobile data but not on a Wi-Fi network | A firewall, a VPN or the network blocks outbound TCP port 2101 | Use another network or turn the VPN off. See [NTRIP Server Settings](/get-started/network.md). | | Another profile sits at the top with **Disconnect** | LiteSurvey Pro reconnected to the profile used before | Tap the RTKdata profile under **NTRIP accounts (Tap account to connect)**. | | iOS: receiver not listed in **Select An Accessory** | Receiver not paired in iOS | Pair it in the iOS Settings under Bluetooth. Device names begin with "LSG" or "LSK". | | A message that the LiteSurvey device "is not authorized", or that the trial for the device has ended | Device authorization at Woncan, not an RTKdata issue | Contact Woncan support at the address given in the message. | | **Device information** or **Mock location** missing in **Settings** | No receiver connected | Pair the receiver first. | | Receiver does not reconnect after a firmware update | Receiver not yet restarted as the **Notice** describes | Follow the **Notice**: power off and on, wait about 10 seconds, and if needed remove the receiver in the phone's Bluetooth settings and pair it again. | | Other apps on an iPhone show about 5 m accuracy | iOS limits the accuracy that other apps display | Check **Fixed** in LiteSurvey Pro and keep the app running. | | Other Android apps still use the phone's GPS | Mock location only half set up | Set **Select mock location app** to LiteSurvey Pro and turn on **Mock location** in LiteSurvey Pro. | | Fix is lost when LiteSurvey Pro is closed | The NTRIP client runs in the app | Keep LiteSurvey Pro running in the background. | | Fix is lost when the phone screen turns off (Android) | Android stops LiteSurvey Pro in the background | Turn battery optimisation off for LiteSurvey Pro in the Android settings and keep the app running. | | RTK photos lose precision after sharing | Image compression in a messaging app | Export directly from LiteSurvey Pro through file or email apps. | | Consistent offset of 50 cm to 1 m at a control point | Datum mismatch or a second transformation | Follow [Which coordinate system should the project use with AUTO?](#which-coordinate-system-should-the-project-use-with-auto) | | 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 LiteSurvey Pro, for example a login that succeeds without corrections, see [Fix NTRIP Connection Issues](/support/common-connection-issues.md). ## Frequently asked questions ### Can I use a third-party NTRIP service with LiteSurvey Pro? Yes. **+ Add NTRIP account** under **Settings** > **GNSS corrections** has a free text field **Host address / IP**, and Woncan's own setup video connects to a third-party NTRIP service by host name and reaches **Fixed**. For RTKdata, enter the host of your region, **Port** `2101`, your RTK credentials and `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). ### Does a LiteSurvey receiver need its own SIM card? No. LiteSurvey Pro runs the NTRIP connection to RTKdata over the phone's mobile data or Wi-Fi and passes the corrections to the receiver. Keep LiteSurvey Pro running while you work, because the corrections stop when the app is closed. ### Why do other apps on my iPhone still show about 5 m accuracy? With a LiteSurvey receiver and RTKdata corrections, other iPhone apps still show an accuracy of about 5 m because iOS limits the value they display. Woncan states "iOS limits UI display accuracy to 5m" while "Actual positioning achieves centimeter-level precision". Check that LiteSurvey Pro shows **Fixed** with a running RTKdata correction age, and keep LiteSurvey Pro running in the background. ### Is the Woncan LiteSurvey a LiDAR scanner? No. The LiteSurvey 2, 2 Pro and 2 mini are GNSS RTK receivers for phones and tablets, and they connect to RTKdata through an NTRIP account in LiteSurvey Pro, see the setup steps above. On supported receiver models with the required mounting hardware, AR-assisted photo measurement in LiteSurvey Pro uses a LiDAR-equipped iPhone or iPad, or ARCore on compatible Android devices, and the receiver adds the RTK position. For handheld SLAM scanners with RTK, see [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md). ### Which app do I need, LiteSurvey Pro or Lite-Survey? LiteSurvey Pro is the app for connecting a LiteSurvey 2, 2 Pro or 2 mini to RTKdata: published by Woncan (Hong Kong) Limited in the App Store and on Google Play. "Lite-Survey" is a separate Woncan app for the China market and its Lite RTK receivers. All steps on this page use LiteSurvey Pro. ## Quick reference 1. LiteSurvey Pro 2.0.1 from the App Store (iOS or iPadOS 16 or later) or Google Play, receiver firmware updated under **Settings** > **Device information** > **Firmware update**. 2. **Map** > **Tap to connect device**, then pick the receiver in **Select An Accessory** (iOS) or **Choose a device to be managed by LiteSurvey Pro** (Android). 3. **Settings** > **GNSS corrections** > **+ Add NTRIP account**: **Account name** of your choice, **NTRIP**, **Host address / IP** `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`, refresh icon next to **Mountpoint** and tap `AUTO`, **Username** and **Password** from *RTK Credentials*, then **Save**. 4. Outdoors, wait for **Single**, tap the RTKdata profile under **NTRIP accounts (Tap account to connect)** and check that it sits at the top with **Disconnect**. 5. Work only with **Fixed** and a running correction age. **NTRIP connection success** alone is not a fix. 6. Project: **Project details** > **Map Projection**, EPSG system on your regional datum, no **Helmert 7-params** for a WGS84 conversion, check one control point. ## Related Guides * [GNSS Rovers & Receivers](/integration-hub/gnss-rovers-and-receivers.md): all receiver guides and the shared RTKdata connection settings * [Bad Elf Flex Mini](/integration-hub/gnss-rovers-and-receivers/bad-elf-flex-mini.md): another pocket RTK receiver that gets its corrections through a phone app * [Emlid Reach RX / RX2](/integration-hub/gnss-rovers-and-receivers/emlid-reach-rx-rx2.md): a compact RTK receiver with NTRIP and mock location set up in Emlid Flow * [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 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 how to match the frame in processing software * [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 * [QField / QGIS](/integration-hub/ntrip-clients-and-field-software/qfield.md): a field app on Android that reads the corrected position through mock location * [LiDAR Scanners & Mobile Mapping](/integration-hub/lidar-scanners-and-mobile-mapping.md): RTK setup for handheld SLAM scanners, when you need a point cloud instead of a phone-based measurement --- # 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/gnss-rovers-and-receivers/woncan-litesurvey.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.