> 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/stonex-s999-s880.md). # Stonex S999 & S880 RTK Setup: NTRIP in Cube-a 7 and Web UI Stonex S999 NTRIP setup, also for the S880: connect to RTKdata in Cube-a 7 (Internal Network or Phone Network) or the Web UI, with AUTO, GGA and an LED check. The **Stonex S999** and **S880** are GNSS survey rovers with a built-in 4G modem, an IMU for tilt compensation and a camera for stakeout; the S999 has two cameras. To set up NTRIP on a Stonex S999 or S880 with RTKdata, open **Device** > **Working Mode** > **Rover** in Stonex Cube-a, choose **Internal Network** (SIM in the receiver) or **Phone Network** (internet from the controller) under **Datalink**, and enter the RTKdata host for your region in **IP:** (`rtk.rtkdata.com` for North America, `eu.rtkdata.com` for Europe or `aus.rtkdata.com` for Australia), port `2101` in **Port:**, your RTK credentials and the `AUTO` mountpoint. Without Cube-a, enter the same values in the receiver's Web UI at `192.168.10.1`: **Working mode settings**, tab **Rover**, **Current Datalink :** **Network**, with **Connect Mode** set to **NTRIP**. The Cube-a steps follow the Stonex Cube-a 7.0 User Manual. The Web UI steps follow the Stonex S999 User Manual (May 2025) and the S880 User Manual (August 2024), which describe the Web UI and the NTRIP settings of both receivers in the same words. Labels can differ in other Cube-a versions. Current app version when this page was written: Stonex Cube-a v7 7.2.05 (Google Play, 31 July 2026). {% hint style="warning" %} **Use one configuration route per receiver.** Set up NTRIP either in Cube-a or in the Web UI, not in both. Stonex dealers report from experience that Cube-a writes its own configuration and overwrites any setup made earlier in the Web UI, such as the NTRIP and SIM settings. In Cube-a, **Apply** starts the receiver in rover mode with the Cube-a settings. With **Phone Network**, Cube-a also sets the receiver's datalink to Bluetooth, as the Stonex manual describes. Opening the Web UI only to read a status, for example the Network section under Information, does not change the setup. {% endhint %} These are the values you enter, and the field names in bold match Cube-a and the Web UI. Choose 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)** in **IP:** (Cube-a) or **Caster Address** (Web UI): `rtk.rtkdata.com` * **Host (IP fallback):** `13.56.117.10`, only if the hostname is rejected or does not connect * **Port:** `2101`, in **Port:** (Cube-a) or **Caster Port** (Web UI) * **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)** in **IP:** (Cube-a) or **Caster Address** (Web UI): `eu.rtkdata.com` * **Host (IP fallback):** `3.73.41.96`, only if the hostname is rejected or does not connect * **Port:** `2101`, in **Port:** (Cube-a) or **Caster Port** (Web UI) * **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)** in **IP:** (Cube-a) or **Caster Address** (Web UI): `aus.rtkdata.com` * **Host (IP fallback):** `54.206.56.130`, only if the hostname is rejected or does not connect * **Port:** `2101`, in **Port:** (Cube-a) or **Caster Port** (Web UI) * **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 %} | Field | Value | | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Connect Mode:** (Cube-a), **Connect Mode** (Web UI) | **NTRIP** | | **Name:** under **CORS Settings** (Cube-a) | Your own entry for RTKdata, not a saved entry of another correction service | | **IP:** (Cube-a), **Caster Address** (Web UI), North America | `rtk.rtkdata.com`, IP fallback `13.56.117.10` | | **IP:** (Cube-a), **Caster Address** (Web UI), Europe | `eu.rtkdata.com`, IP fallback `3.73.41.96` | | **IP:** (Cube-a), **Caster Address** (Web UI), Australia | `aus.rtkdata.com`, IP fallback `54.206.56.130` | | **Port:** (Cube-a), **Caster Port** (Web UI) | `2101` | | **User:** and **Password** under **CORS Account** (Cube-a), **User** and **Password** (Web UI) | From *RTK Credentials* in your [account dashboard](https://rtkdata.com/my-account/rtk-credentials/). The username starts with `rtk` and is not your website login. | | **MountPoint:** (Internal Network), **Corrections** (Phone Network), **Mountpoint** (Web UI) | `AUTO` (recommended), or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84`. In Cube-a, select it from the loaded list; in the Web UI, type it. | | **GGA Upload Interval(s):** (Internal Network), **Send GGA delay \[sec]:** (Phone Network), **Upload GGA** (Web UI) | `1`, in the Web UI **1 S** | | **Automatically connect to network:** (Cube-a), **Auto Connect** (Web UI) | On, in the Web UI **YES** | | **Network Relay:** (Internal Network) | Off | | **Operator:** and **APN Name:** (Cube-a), **APN** (Web UI) | The APN of your SIM provider, only for a SIM in the receiver | * Enter only the hostname in the address field, without `:2101`. The port has its own field. * In the Web UI, the Stonex manuals show a hostname in **Caster Address**, so use the hostname there. * Cube-a names the host field **IP:**, and the Stonex screenshots show IP addresses in it. Enter the hostname first. If Cube-a rejects it or does not connect, enter the IP fallback for your region, as described under *If the hostname does not connect* in the troubleshooting section. * Mountpoint names are case sensitive: `AUTO` in capitals. * One set of credentials allows one connection at a time. A second rover running at the same time needs its own data stream, see [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices). ## Requirements * **Stonex S999 or S880** with a clear view of the sky * **Stonex Cube-a 7** on an Android controller, with a Cube-a license code. The Cube-a 7.0 user manual states that one license code unlocks Cube-a on one device only. To move a purchased license to another controller, tap **Deactivate** under **Activation info** first; the manual allows this at most three times, and not for a demo license. * **Or**, without Cube-a: a **smartphone or laptop with a browser** for the receiver's Web UI * **Internet for the receiver:** a **Nano-SIM without PIN** and with mobile data in the receiver, inserted while the receiver is switched off, or mobile data or a hotspot on the controller (Cube-a **Phone Network** only) * **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 you go out * **Survey pole**, required for the tilt sensor calibration {% 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 Stonex guide fits your receiver? This guide covers the Stonex S999 and S880; other Stonex receivers and scanners have their own RTKdata guides, because their apps and internet options differ. | Stonex device | RTKdata guide | Where you set up NTRIP | | ---------------------- | ------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | | S999, S880 | This page | Cube-a 7 or the receiver Web UI | | S980A, S900A | [Stonex S980A / S900A](/integration-hub/gnss-rovers-and-receivers/stonex-s980a-s900a.md) | Cube-a or the receiver Web UI | | S1000, S950 | [Stonex S1000 / S950](/integration-hub/gnss-rovers-and-receivers/stonex-s1000-s950.md) | Cube-a, the S950 also in its Web UI | | S599, S590 | [Stonex S599 / S590](/integration-hub/gnss-rovers-and-receivers/stonex-s599-s590.md) | Cube-a, the S599 also in its Web UI; no modem, internet from the controller or a hotspot | | S80G, S60G, S55G, S90G | [Stonex S80G / S60G / S55G / S90G](/integration-hub/gnss-rovers-and-receivers/stonex-s80g-s60g-s55g-s90g.md) | Android controllers with RTK GNSS: Cube-a on the controller, Phone Network | | X200GO, X120GO | [Stonex X200GO / X120GO](/integration-hub/lidar-scanners-and-mobile-mapping/stonex-x200go-x120go.md) | SLAM laser scanners, set up in GOapp | ### What differs between the S999 and the S880? For the NTRIP setup, the S999 and S880 are the same: Stonex describes identical Web UI and NTRIP settings for both receivers. The differences that matter during setup are the cameras and one extra datalink option on the S880. | | S999 | S880 | | ----------------------------------------------------------- | ---------------------------------------- | ------------------------------------------------- | | Cameras | Two: a below camera and a frontal camera | One camera for stakeout | | **Current Datalink :** options in the Web UI, tab **Rover** | **UHF**, **Network**, **Bluetooth** | **UHF**, **Network**, **External**, **Bluetooth** | | Datalink for RTKdata in the Web UI | **Network** | **Network** | ## Should you set up the S999 or S880 in Cube-a or in the Web UI? Set up the S999 or S880 in Cube-a if you survey with a licensed Stonex Cube-a on an Android controller, and in the Web UI at `192.168.10.1` if you have no Cube-a license; then stay with that route for the NTRIP setup of this receiver. | | Cube-a 7 | Web UI at `192.168.10.1` | | ------------------------ | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ | | What you need | Android controller with a licensed Cube-a | Phone or laptop with a browser, connected to the receiver's Wi-Fi hotspot | | Internet for corrections | SIM in the receiver (**Internal Network**) or the controller's internet (**Phone Network**) | SIM in the receiver (**SIM CARD NETWORK**) or a Wi-Fi network (**Wi-Fi Client**) | | Mountpoint | Select `AUTO` from the list loaded with **Get Mountpoint (RTK network)** or **GET ACCESS POINT** | Type `AUTO`, or load the list with **Get Mountpoint** | | Reuse | **Save to Configurations** stores the setup for later use | With **Auto Connect** set to **YES**, the receiver uses the last settings to connect at start-up | ## How do you set up NTRIP on the Stonex S999 or S880 in Cube-a? In Cube-a, connect the receiver under **Device** > **Communication**, open **Device** > **Working Mode** > **Rover**, pick **Internal Network** or **Phone Network** under **Datalink**, fill in the RTKdata host, port `2101`, your RTK credentials and the `AUTO` mountpoint, then set the antenna height and tap **Apply**. {% stepper %} {% step %} ### Insert the SIM (receiver SIM only) Skip this step if the receiver gets internet from the controller (**Phone Network**). 1. With the receiver switched off, insert a Nano-SIM without PIN code into the **Sim card slot** and lock it by sliding the metal cover. 2. Hold the power button until you hear a beep. After three short beeps, the receiver is ready. {% endstep %} {% step %} ### Connect Cube-a to the receiver 1. Tap **Device** at the bottom of Cube-a and open **Communication**. 2. Set **Device Type:** to **Stonex GNSS** and **Communication Mode:** to **Bluetooth**. 3. Tap **Search**, select your receiver's serial number in the **Bluetooth Name** column and tap **Connect**. **QR** scans the code on the bottom of the receiver, but only after a Bluetooth search: Cube-a looks for the serial number among the devices it has found. For the camera functions over Wi-Fi, see *Camera, AR stakeout and the internet connection* below. {% endstep %} {% step %} ### Open the rover settings Open **Device** > **Working Mode** > **Rover**. The page **Rover mode settings** opens with the sections **Options**, **Datalink**, **Antenna Parameters** and **Satellite Systems**. {% endstep %} {% step %} ### Choose the internet route and enter RTKdata Under **Datalink**, open the **Communication Mode:** drop-down and select the route, then tap the button below the drop-down to open its settings page. {% tabs %} {% tab title="Internal Network (SIM in the receiver)" %} The page **Rover network settings** opens. 1. **Connect Mode:** select **NTRIP**. 2. **Connection Options:** set **GGA Upload Interval(s):** to `1` (the manual gives 5 seconds as the default, which also works), turn **Automatically connect to network:** on and leave **Network Relay:** off. 3. **APN Settings:** select your carrier under **Operator:**, or select **Custom** and enter **APN Name:**, plus **User:** and **Password** if your SIM provider requires them. Do not keep example values. 4. **CORS Settings:** under **Name:**, add your own entry for RTKdata or fill in the fields directly; do not use a saved entry of another correction service. Enter the host for your region in **IP:** and `2101` in **Port:**. 5. **CORS Account:** enter **User:** and **Password** from *RTK Credentials*, and tick **Show password** to check them. 6. **Get MountPoint Settings:** tap **Get Mountpoint (RTK network)**. The download needs internet on the receiver SIM or, with **Phone network access:** turned on, on the controller. If the receiver SIM is not online yet, turn on **Phone network access:** first. If the controller has no SIM of its own, connect it to a phone hotspot for this download, as the Cube-a manual describes for **Phone Network**; Cube-a stays connected to the receiver over Bluetooth. 7. **MountPoint Settings:** select `AUTO` under **MountPoint:**. The list can show more entries than `AUTO`: select `AUTO`. 8. Tap **OK**. {% endtab %} {% tab title="Phone Network (controller internet)" %} The controller needs internet from its own SIM or from a hotspot. The page **Send diff. from controller** opens. 1. **Connect Mode:** select **NTRIP**. 2. **CORS Settings:** check **Name:** first and do not keep a saved entry of another correction service. Add your own entry for RTKdata or fill in the fields directly: the host for your region in **IP:** and `2101` in **Port:**. 3. **CORS Account:** enter **User:** and **Password** from *RTK Credentials*, and tick **Show password** to check them. 4. **MountPoint:** tap **GET ACCESS POINT**, then select `AUTO` under **Corrections**. The list can show more entries than `AUTO`: select `AUTO`. 5. Turn **Automatically connect to network:** on and set **Send GGA delay \[sec]:** to `1`. 6. Tap **Start**. The **Receive:** bar fills when data arrives. Tap **OK**. {% endtab %} {% endtabs %} Both pages show **Notify when base coordinates change:** under **CORS Settings**. With `AUTO`, the message it shows is expected after the caster switches to a closer station, and it is not an error. {% hint style="info" %} **AUTO needs your position.** The `AUTO` mountpoint chooses the base station from the receiver's position, which the receiver sends as NMEA GGA at the interval you set. The Stonex manuals document no separate GGA switch, so do not leave the interval empty or at 0. Without a position, the receiver logs in but receives no corrections, see [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). Before you connect, wait outside with open sky until the receiver has a position of its own: at least **SINGLE** in Cube-a, or a flashing green satellite LED. Leave **Fake GGA coordinates** and **Forced GGA** off. The Cube-a manual describes them as "only for test", and with a fake position `AUTO` picks the base station for the wrong place. {% endhint %} {% endstep %} {% step %} ### Set the antenna height and apply 1. Back on **Rover mode settings**, set **Measured Height:** and **Measurement Type:** under **Antenna Parameters**. 2. Tap **Apply**. 3. Optional: tap **Save to Configurations** to reuse the setup later or in a new project without entering all parameters again. {% endstep %} {% step %} ### Wait for FIXED Stay outside with open sky and check the solution as described in *How do you know corrections are really arriving?* below. {% endstep %} {% endstepper %} ## How do you set up NTRIP in the S999 or S880 Web UI at 192.168.10.1? Connect a phone or laptop to the receiver's Wi-Fi hotspot, open `192.168.10.1`, log in, set **Current Datalink :** to **Network** on the **Rover** tab, choose **SIM CARD NETWORK** or **Wi-Fi Client**, and set **Connect Mode** to **NTRIP** with the RTKdata host in **Caster Address**, `2101` in **Caster Port**, `AUTO` in **Mountpoint**, **Upload GGA** at **1 S**, your RTK credentials and **Auto Connect** at **YES**, then tap **Save**. {% stepper %} {% step %} ### Prepare the phone and join the receiver hotspot 1. Copy your username and password from *RTK Credentials* first. While the phone is connected to the receiver hotspot, it usually has no internet. 2. Turn off mobile data on the phone, a Stonex dealer tip that keeps the phone on the receiver hotspot. 3. Connect to the receiver's Wi-Fi hotspot. Its name is the receiver serial number, and the Stonex manual shows it as an open network. Management > Security can also set a hotspot password, so a used receiver may ask for one. If several receivers are in range, check the serial number. {% endstep %} {% step %} ### Log in 1. Open `192.168.10.1` in the browser. 2. Enter **User** `admin` and **Password** `password`, the standard credentials in the Stonex manuals, and tap **Login**. The password can be changed under Management > Security, so a used receiver may have a different one. 3. When the browser offers to save the password, decline. Otherwise autofill can later put `admin` and `password` into the NTRIP fields. {% endstep %} {% step %} ### Enable the modem (SIM only) For a SIM in the receiver, open the Device Settings page, turn on **Network Enable** under **Hardware configuration** and tap **Save**. The Stonex manual describes this switch as "Enable 2G/3G/4G network", and its screenshot shows it off. {% endstep %} {% step %} ### Set the datalink to Network On the dashboard, open **Working mode settings**, select the **Rover** tab and set **Current Datalink :** to **Network**. {% endstep %} {% step %} ### Choose the internet connection Under **Network Link**, choose one: * **SIM CARD NETWORK:** enter your provider's **APN**, plus **APN User** and **APN Password** if the provider requires them. * **Wi-Fi Client:** enter **SSID** and **Password** of the Wi-Fi network. Both may contain only letters and digits. The receiver hotspot then switches off, and the Web UI is only reachable at the IP address the Wi-Fi network assigns to the receiver. {% endstep %} {% step %} ### Enter the NTRIP settings 1. **Connect Mode:** **NTRIP** 2. **Caster Address:** the host for your region, for example `eu.rtkdata.com`. The Stonex manual shows a hostname in this field. 3. **Caster Port:** `2101` 4. **Mountpoint:** type `AUTO` in capitals. **Get Mountpoint** loads the list instead, but only once internet, **Caster Address** and **Caster Port** are set. 5. **Upload GGA:** **1 S**. The Stonex manual says that "the GGA upload must be set at 1 second at least" when the network needs the rover position. 6. **User** and **Password:** from *RTK Credentials*. If the browser filled in `admin` or `password`, clear both fields and type your RTK credentials. 7. **Auto Connect:** **YES**. The receiver then connects with the last settings at start-up. {% endstep %} {% step %} ### Save and check 1. Tap **Save** and wait for the confirmation message. After switching to **Wi-Fi Client**, the message may not appear, because the connection to the hotspot drops. 2. On the dashboard, check **Actual datalink setting** and **Position Status**. Without corrections, the Stonex screenshot shows **Single**. 3. If **Actual datalink setting** and **Position Status** do not change after **Save**, switch the receiver off and on. With **Auto Connect** set to **YES**, the Stonex manual says that the receiver connects with the last settings at start-up. 4. **Expire on** on the dashboard shows when the receiver registration expires. {% endstep %} {% endstepper %} ## Where does the receiver get internet: its own SIM or the controller? The S999 and S880 get internet for RTKdata corrections either from a Nano-SIM in the receiver's own 4G modem or from the controller running Cube-a; in the Web UI, the receiver can also join a Wi-Fi network as a client. | Internet source | Cube-a | Web UI | What you need | | ------------------- | ------------------------ | ------------------------------------------------ | ------------------------------------------------------------------------------------------------- | | SIM in the receiver | **Internal Network** | **SIM CARD NETWORK**, with **Network Enable** on | Nano-SIM without PIN and with mobile data, inserted with the receiver off, and the provider's APN | | Controller internet | **Phone Network** | Cube-a only | SIM with mobile data in the controller, or the controller on a hotspot | | Wi-Fi network | Not covered on this page | **Wi-Fi Client** | SSID and password with letters and digits only; the receiver hotspot switches off | * Test a new SIM in a phone first: PIN off, mobile data working. Check the data volume, especially on a prepaid SIM. * Some mobile carriers block port 2101. If the receiver SIM does not connect, try **Phone Network** with the controller's internet as a cross-check, see [Troubleshooting & FAQ](/support/troubleshooting-and-faq.md). ### Camera, AR stakeout and the internet connection When Cube-a connects to the receiver over its Wi-Fi hotspot (**Communication Mode:** **WIFI**), for example for the camera functions, the controller's Wi-Fi is taken by the receiver hotspot, which has no internet. * Use **Internal Network** with a SIM in the receiver for NTRIP in this mode. * Stonex dealers report that **Phone Network** with a SIM in the controller works in this mode only if Android keeps mobile data on while Wi-Fi is connected: turn on the Android developer option "Mobile data always active". * A phone hotspot cannot provide the controller's internet in this mode, because the controller's Wi-Fi is already connected to the receiver. * The camera functions need **WIFI Frequency** set to **5G** on the Device Settings page of the Web UI, according to the Stonex manual. * For NTRIP without the camera, connect Cube-a over **Bluetooth**. ## How do you know corrections are really arriving? RTKdata corrections are really arriving on the S999 or S880 when Cube-a **Device** > **GNSS Status** shows **FLOAT** or **FIXED** with a low **Differential correction age** (the Cube-a manual says it is generally less than 5 seconds) and the datalink LED on the receiver flashes green. A solid green datalink LED or **DGNSS** alone is not proof. | Solution in Cube-a | Meaning | What to do | | ------------------ | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | **NO FIX** | No position: Cube-a is not connected to the receiver, or the receiver sees no satellites | Check the Bluetooth connection and move outside | | **SINGLE** | No differential corrections | Check the internet route, credentials, mountpoint and GGA interval | | **DGNSS** | Corrections from SBAS satellites, or from the base without a better solution | Not proof of NTRIP. Check **Differential correction age**, the **Receive:** bar and the datalink LED | | **FLOAT** | Corrections from the base arrive, RTK not solved yet | Stay under open sky and wait | | **FIXED** | RTK fix | Start measuring | * **Device** > **Datalink Status** shows the details of the datalink. * With **Phone Network**, the **Receive:** bar on **Send diff. from controller** shows the data flow. * In the Web UI, check **Position Status** and **Actual datalink setting** on the dashboard. Receiver LEDs: | LED | State | Meaning | | --------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------- | | Satellite | Flashing red | Position not calculated | | Satellite | Flashing green | Position calculated without a fixed solution | | Satellite | Green, solid | Fixed solution | | Satellite | Flashing green and red alternately | GNSS board abnormal | | Datalink | Green, solid | Datalink set, but no data arriving. The S880 manual: "datalink set but there is no data transfer" | | Datalink | Flashing green | Corrections arriving | | Datalink | Flashing blue | Raw data recording. On the S999, the LED then does not show whether corrections arrive | | Datalink (S880) | Flashing light blue | Raw data recording while corrections arrive | {% hint style="info" %} **No format setting needed.** The S999 and S880 manuals list RTCM 3.2 as a rover input format, and both receivers detect the correction format automatically. RTKdata streams RTCM 3.2 with MSM4 messages (1074, 1084, 1094, 1114, 1124, 1134) and 1005. Cube-a shows the differential mode as **AUTO** because the receiver decodes the messages; this is not the mountpoint. {% endhint %} ## Which coordinate system should you use with AUTO in Cube-a? With the RTKdata `AUTO` mountpoint, select a Cube-a project coordinate system that matches the regional datum `AUTO` delivers at your position, for example NAD83(2011) in the USA or ETRS89 in Europe, and do not select **RTCM1021-1027** in **Coordinate system parameters type**. ### Coordinate system and heights with AUTO * `AUTO` delivers your region's datum, chosen from your GGA position: for example NAD83(2011), epoch 2010.0, in the USA; NAD83(CSRS)v7, epoch 2010.0, in Canada; ETRS89 (realization ETRF2000), epoch 2010.0, in Europe; and GDA2020, epoch 2020.0, in Australia. For regions not listed, `AUTO` falls back to WGS84(G2139) at the mid-year epoch. The datum for every region is listed in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md). * `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver ITRF2020 and ITRF2014 at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) at the mid-year epoch. * In Cube-a, open **Configure** > Coordinate System, tap **Existing Use/Change** and then **Default Systems**, filter the list by country or by word, select the system that matches the datum of your mountpoint and tap **OK**. * In **Coordinate system parameters type**, do not select **RTCM1021-1027**. The Cube-a manual reserves it for networks that send these messages ("if the CORS you use sends them out"), and the RTKdata stream carries MSM4 and 1005, not 1021 to 1027. * Do not switch on **ITRF Conversion** in addition to `AUTO`. The Cube-a manual warns that this conversion "is applied to all points in the current project". * Heights are ellipsoidal. Apply a geoid under **Configure** > Coordinate System > **Geoid files**, see [Understanding Heights](/get-started/understanding-heights.md). * A consistent offset of 50 cm to 1 m against local survey control usually means a datum mismatch, see [Why Your Coordinates May Be Offset](/get-started/coordinate-systems-and-datums.md#why-your-coordinates-may-be-offset). * While you move, `AUTO` can hand off to a closer station. Cube-a then shows the message behind **Notify when base coordinates change:**; this is expected and not an error. * The Web UI dashboard shows the position as WGS84 coordinates. That is only the display and does not change the datum of the corrections. * Satellite corrections (SBAS, B2B PPP, Galileo HAS), if enabled on the receiver, take over after the **RTK timeout** when no RTK corrections arrive. The Stonex manual warns: "Different source of corrections could use different reference frame." Check for **FIXED** before you store points. ## How do you turn on tilt compensation after the fix? Turn on tilt compensation on the S999 or S880 once you have a FIXED solution: in Cube-a, open **Configure** > **System Settings** > **Sensor Options**, select **Pole Tilt Correction** (marked **Requires a FIXED solution**) and tap **OK**. Before the first use, calibrate the sensor: 1. Wait for **FIXED**. The Stonex manual makes a fixed solution mandatory for the calibration. 2. Set the pole to 1.8 m and enter the same height in Cube-a. 3. Open **Calibrate** > **Calibrate Sensor**. On **IMU Calibration**, wait for **READY TO CALIBRATE** and tap **Start**. 4. Keep the pole tip on the same point and move the receiver back and forth for about 15 seconds in each of four directions, between 45 and 60 degrees from vertical, as Cube-a guides you. 5. The calibration is complete when Cube-a shows its completion message: **Calibration Terminated** in the S999 and S880 manuals, **Calibration completed** in the Cube-a 7.0 manual. During the survey, follow the initialization prompts on screen. If they keep coming back, check the correction link and **Differential correction age** first: Stonex dealers report that poor correction reception can cause repeated prompts. ## Troubleshooting | Problem | Cause | Fix | | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | NTRIP or SIM settings made in the Web UI are gone, or the receiver behaves unpredictably | Cube-a and the Web UI both used for the setup. Stonex dealers report that Cube-a overwrites a setup made earlier in the Web UI, and **Phone Network** sets the datalink to Bluetooth | Use one route per receiver. If the setup is mixed up, use **Restore Factory Settings** in the Web UI (Management > Tools) and set up the receiver once in the route you keep | | Controller on the receiver Wi-Fi (camera), **Phone Network** selected, status stays **SINGLE** | The NTRIP traffic goes into the receiver hotspot, which has no internet | Use **Internal Network** with a SIM in the receiver, or, as Stonex dealers report, turn on the Android developer option "Mobile data always active". For NTRIP without the camera, connect over **Bluetooth** | | Datalink LED solid green, but no fix | Solid green only means the datalink is set; no data arrives | Check GGA and position, credentials and internet. Corrections arrive when the LED flashes green and **Differential correction age** stays low | | Test indoors or in a vehicle: login works, no corrections | No position, so no usable GGA; `AUTO` cannot assign a base station | Test outside under open sky and wait for a position of your own (satellite LED flashing green) | | Phone or controller does not see the S999 hotspot | The hotspot runs on 5 GHz and the device supports only 2.4 GHz | Open the Web UI with a 5 GHz capable device and change **WIFI Frequency** if needed (the camera functions need **5G**). Cube-a over **Bluetooth** is not affected | | `192.168.10.1` does not load or shows another receiver | The phone switched to mobile data or another Wi-Fi, or joined the wrong receiver | Turn off mobile data, check the serial number in the hotspot name and reload the page | | Cube-a does not open without a license code | The Cube-a 7.0 manual: the software cannot be unlocked without the correct license code, and one code works on one device | Check the license code for this controller. To move a purchased license to a new controller, tap **Deactivate** under **Activation info** on the old one first (at most three times, not for a demo license). Without a license, set up NTRIP in the Web UI | | Web UI unreachable after **Wi-Fi Client** was set | **Wi-Fi Client** switches off the receiver hotspot | Connect Cube-a over **Bluetooth** and set **Device** > **WiFi Mode Settings** to **MASTER**, or join the same Wi-Fi network and open the Web UI at the IP address that network assigned to the receiver | | Receiver does not join the Wi-Fi network or phone hotspot | Special characters in **SSID** or **Password**, or hotspot settings | Use letters and digits only. Stonex dealers recommend a phone hotspot with WPA2 on 2.4 GHz and mobile data on | | SIM does not go online | SIM with PIN, SIM inserted while the receiver was on, or APN missing | Remove the PIN in a phone, insert the SIM with the receiver off, enter the provider's APN | | Modem online, but no NTRIP connection | No data volume or roaming on the SIM, or the carrier blocks port 2101 | Test the SIM in a phone, check the Network section under Information in the Web UI, and try **Phone Network** as a cross-check, see [Troubleshooting & FAQ](/support/troubleshooting-and-faq.md) | | SIM route in the Web UI does not come online | Possibly **Network Enable** is off; the Stonex screenshot shows it off | Turn on **Network Enable** under **Hardware configuration** and tap **Save** | | Status stays **SINGLE** after a correct setup | Wrong internet route: **Internal Network** without a SIM in the receiver, or **Phone Network** without internet on the controller | Match the route to where the SIM is | | Corrections stop 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) | | Caster rejects the login in the Web UI | Browser autofill put the Web UI login `admin` / `password` into **User** and **Password** | Turn off password saving for the Web UI, clear both fields and type the username (starts with `rtk`) and password from *RTK Credentials* | | Receiver beeps and tracks no satellites | Receiver registration expired. The Stonex manual: "If the registration has expired the device will beep and it will not track satellites." | Check **Expire on** on the Web UI dashboard or **Device** > **Register** in Cube-a, and ask your Stonex dealer for a new code | | SIM or NTRIP setup gone after a firmware update | The Stonex manual asks for a factory reset after each firmware update, which resets the configuration | Set up the receiver again or load your **Save to Configurations** entry. If Cube-a no longer finds the receiver, delete the Bluetooth pairing on the Android device and pair again | | Cube-a rejects the hostname in **IP:** or does not connect | Hostname in the Cube-a rover field is not documented by Stonex | Enter the IP fallback for your region, see *If the hostname does not connect* below | | Mountpoint list in Cube-a stays empty | Neither the receiver SIM nor the controller has internet for the download | Turn on **Phone network access:** and give the controller internet, from its own SIM or a phone hotspot (Cube-a stays connected over Bluetooth). Tap **Get Mountpoint (RTK network)** again and select `AUTO`. To see whether the receiver SIM is online, read the Network section under Information in the Web UI without changing settings there | | Web UI: nothing changes after **Save** | The Stonex manuals do not say whether NTRIP starts right after **Save** | Switch the receiver off and on. With **Auto Connect** set to **YES**, it connects with the last settings at start-up | | No corrections with a lowercase mountpoint | Mountpoint names are case sensitive | Select or type `AUTO` in capitals | | **QR** finds no receiver | No Bluetooth search before scanning | Tap **Search** first, then **QR** or select the serial number | | Warning about changed base coordinates during the survey | `AUTO` switched to a closer station | Expected with `AUTO`, not an error | | Positions a few decimetres off with a seemingly good status | Satellite corrections (SBAS, B2B PPP, Galileo HAS) in use after the **RTK timeout**, possibly in another reference frame | Store points only in **FIXED**; turn off satellite corrections if needed | | Project without the expected transformation | **RTCM1021-1027** selected as **Coordinate system parameters type** | Select a coordinate system that matches the datum of `AUTO` under **Configure** > Coordinate System > **Existing Use/Change** > **Default Systems** | | Tilt calibration not possible or tilt readings off | No **FIXED** solution, or the pole height in Cube-a differs from the real one | Wait for **FIXED**, set the pole to 1.8 m and the same height in Cube-a, then calibrate | | `AUTO` picks a distant or wrong base station | **Fake GGA coordinates** or **Forced GGA** on | Turn both off | ### If the hostname does not connect The Web UI takes a hostname in **Caster Address**. In Cube-a, the host field is called **IP:** and Stonex documents only IP addresses for the rover. Keep the hostname for your region whenever it connects. Use the IP fallback only if Cube-a rejects the hostname or the status stays on **SINGLE** although internet, credentials and mountpoint are right: enter the IP for your region in **IP:** and keep port, credentials and mountpoint. | Region | Hostname (preferred) | IP fallback for **IP:** | **Port:** | Mountpoint | | ------------- | -------------------- | ----------------------- | --------- | ---------- | | North America | `rtk.rtkdata.com` | `13.56.117.10` | `2101` | `AUTO` | | Europe | `eu.rtkdata.com` | `3.73.41.96` | `2101` | `AUTO` | | Australia | `aus.rtkdata.com` | `54.206.56.130` | `2101` | `AUTO` | For connection problems that are not specific to Stonex receivers, see [Common Connection Issues](/support/common-connection-issues.md). ## Frequently asked questions ### Does the Stonex S999 need its own SIM card for NTRIP? No. The S999 can take a Nano-SIM without PIN in its own 4G modem (Cube-a **Internal Network**, Web UI **SIM CARD NETWORK**), but in Cube-a it can also receive RTKdata corrections through the controller's internet with **Phone Network**. In the Web UI, the alternative to a SIM is **Wi-Fi Client**, which connects the receiver to a Wi-Fi network and switches off its hotspot. ### Can I type AUTO in Cube-a, or do I have to pick it from the list? Pick it from the list: load the RTKdata mountpoint list with **Get Mountpoint (RTK network)** (Internal Network) or **GET ACCESS POINT** (Phone Network) and select `AUTO`. The Cube-a 7.0 manual describes the mountpoint as a drop-down that you fill this way, and it does not describe typing a mountpoint. The list can show more entries than `AUTO`. The download needs internet on the receiver SIM or, with **Phone network access:** turned on, on the controller; if the list stays empty, see the troubleshooting table. In the Web UI, you can type `AUTO` into **Mountpoint**. ### Why is the datalink LED solid green but there is still no fix? A solid green datalink LED only means that the datalink is set; RTKdata corrections arrive when the LED flashes green. The S880 manual describes solid green as "datalink set but there is no data transfer". Check that the receiver has a position of its own outside under open sky, that the RTK credentials and `AUTO` are right, and that the SIM or controller has internet. In Cube-a, **Differential correction age** shows whether corrections are flowing. ### Can I set up the S880 in the Web UI and then keep working in Cube-a? Not for the NTRIP setup: if you survey in Cube-a, set up the RTKdata connection in Cube-a. Stonex dealers report that Cube-a writes its own configuration and overwrites any setup made earlier in the Web UI, and with **Phone Network** Cube-a sets the datalink to Bluetooth, as the Stonex manual describes. If the receiver behaves unpredictably after mixing both, restore factory settings in the Web UI and set it up once. ### Why does my phone not see the S999 Wi-Fi hotspot? A common cause is that the hotspot runs on 5 GHz while the phone or controller supports only 2.4 GHz. Stonex dealers report that the S999 ships with the hotspot set to 5 GHz; the band is changed in the Web UI under **WIFI Frequency**, so the first connection needs a 5 GHz capable device. The hotspot is also missing after **Wi-Fi Client** was set in the Web UI. Its name is the receiver serial number. You need the hotspot only for the Web UI setup of RTKdata NTRIP and for the camera functions; Cube-a over **Bluetooth** does not need it. ## Quick reference 1. Pick one route per receiver: Cube-a or the Web UI. For a SIM in the receiver: Nano-SIM without PIN, inserted with the receiver off. 2. Cube-a: **Device** > **Communication** (**Stonex GNSS**, **Bluetooth**, **Search**, **Connect**), then **Device** > **Working Mode** > **Rover**, **Datalink** > **Communication Mode:** **Internal Network** or **Phone Network**. 3. **Connect Mode:** **NTRIP**, **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`, **User:** and **Password** from *RTK Credentials*. 4. Load the list with **Get Mountpoint (RTK network)** or **GET ACCESS POINT**, select `AUTO`, GGA interval `1`, **Automatically connect to network:** on, **OK**, antenna height, **Apply**. 5. Web UI instead: receiver hotspot (serial number), `192.168.10.1`, **Rover** > **Current Datalink :** **Network**, **SIM CARD NETWORK** with **APN** or **Wi-Fi Client**, **Connect Mode** **NTRIP**, **Caster Address**, **Caster Port** `2101`, **Mountpoint** `AUTO`, **Upload GGA** **1 S**, **Auto Connect** **YES**, **Save**. 6. Wait outside for **FIXED** and a flashing green datalink LED; solid green alone is not proof. Then enable **Pole Tilt Correction**. ## Related Guides * [NTRIP Server Settings](/get-started/network.md): the regional hosts, IP fallbacks, port and mountpoints in one reference * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why the caster needs your position before it sends corrections * [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which datum `AUTO` and its variants deliver in each region * [Understanding Heights](/get-started/understanding-heights.md): ellipsoidal and orthometric heights, and how to apply a geoid * [Account & Credentials](/get-started/account-and-credentials.md): where to find your RTK credentials and how many devices can connect at once * [Common Connection Issues](/support/common-connection-issues.md): what to check when corrections do not arrive or the fix stays on Float * [Troubleshooting & FAQ](/support/troubleshooting-and-faq.md): port 2101, firewalls and carrier restrictions * [Coverage Map](/get-started/coverage-map.md): check the station coverage at your site before you go out * [Stonex S980A / S900A](/integration-hub/gnss-rovers-and-receivers/stonex-s980a-s900a.md): RTKdata setup for the Stonex S980A and S900A in Cube-a and the receiver web interface * [Stonex S1000 / S950](/integration-hub/gnss-rovers-and-receivers/stonex-s1000-s950.md): RTKdata setup for the Stonex rovers with laser distance meter * [Stonex S599 / S590](/integration-hub/gnss-rovers-and-receivers/stonex-s599-s590.md): RTKdata setup for the Stonex rovers without a modem, with internet from the controller or a hotspot * [Stonex X200GO / X120GO](/integration-hub/lidar-scanners-and-mobile-mapping/stonex-x200go-x120go.md): RTKdata setup for the Stonex SLAM laser scanners in GOapp * [GNSS Rovers & Receivers](/integration-hub/gnss-rovers-and-receivers.md): all receiver guides and the universal NTRIP parameters --- # 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/stonex-s999-s880.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.