> 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-s1000-s950.md). # Stonex S950 & S1000 NTRIP Setup: Cube-a and S950 Web UI Connect the Stonex S1000 or S950 to RTKdata NTRIP in Cube-a 7, or the S950 in its Web UI: receiver SIM or controller internet, AUTO mountpoint, GGA and tilt. To set up NTRIP on the **Stonex S950** or **S1000** with RTKdata, open **Stonex Cube-a** on the Android controller, go to **Device** > **Working Mode** > **Rover**, set the **Datalink** to **Internal Network** (SIM in the receiver) or **Phone Network** (internet from the controller), and enter the RTKdata host for your region (`rtk.rtkdata.com`, `eu.rtkdata.com` or `aus.rtkdata.com`) in **IP:**, `2101` in **Port:**, your RTK credentials under **CORS Account** and the `AUTO` mountpoint from the loaded mountpoint list. The S950 can also be set up in its **Web UI** at `192.168.10.1` under **Working mode**, with the same values in **Connection Settings**. The S1000 is set up in Cube-a only. The S1000 and S950 are Stonex GNSS rovers with IMU tilt compensation, cameras for AR stakeout, a laser distance meter and a modem for a Nano SIM. Stonex describes Cube-a as compatible with all Stonex GNSS receivers. Stonex has not published an S1000 user manual (September 2026). The Cube-a steps are the same as for the S950 and follow the Cube-a 7.0 user manual (April 2025). The S950 Web UI steps follow the S950 user manual (September 2025, Ver. 1.0). Current app version when this page was written: **Stonex Cube-a v7** 7.2.05 (Google Play, 31 July 2026). Labels can differ in other versions. These are the values you enter in Cube-a or in the S950 Web UI, and the field names in bold match the software. 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 **Server Address** (S950 Web UI): `rtk.rtkdata.com` * **Host (IP fallback):** `13.56.117.10`, only if the hostname is rejected or does not connect * **Port** in **Port:** or **Server Port**: `2101` * **Username / Password** in **CORS Account** (Cube-a) or **User** and **Password** (Web UI): 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 **Server Address** (S950 Web UI): `eu.rtkdata.com` * **Host (IP fallback):** `3.73.41.96`, only if the hostname is rejected or does not connect * **Port** in **Port:** or **Server Port**: `2101` * **Username / Password** in **CORS Account** (Cube-a) or **User** and **Password** (Web UI): 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 **Server Address** (S950 Web UI): `aus.rtkdata.com` * **Host (IP fallback):** `54.206.56.130`, only if the hostname is rejected or does not connect * **Port** in **Port:** or **Server Port**: `2101` * **Username / Password** in **CORS Account** (Cube-a) or **User** and **Password** (Web UI): 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) / **Connection Mode** (S950 Web UI) | `NTRIP` | | **CORS Settings** > **Name:** (Cube-a) | A new entry for RTKdata, or leave the list and fill in the fields directly | | **IP:** / **Server Address** (North America) | `rtk.rtkdata.com`, IP fallback `13.56.117.10` | | **IP:** / **Server Address** (Europe) | `eu.rtkdata.com`, IP fallback `3.73.41.96` | | **IP:** / **Server Address** (Australia) | `aus.rtkdata.com`, IP fallback `54.206.56.130` | | **Port:** / **Server Port** | `2101` | | **User:** / **User** | 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 | | **MountPoint:** (Internal Network) / **Corrections** (Phone Network) / **Mount Point** (Web UI) | `AUTO` (recommended), or `AUTO_ITRF2020`, `AUTO_ITRF2014`, `AUTO_WGS84` | | **GGA Upload Interval(s):** (Internal Network) | `1` | | **Send GGA delay \[sec]:** (Phone Network) | `1` | | **Fake GGA coordinates**, **Forced GGA**, **Record diff. corrections** (Phone Network) | Off | | **Automatically connect to network:** | On | | **Network Relay:** (Internal Network) | Off | * Enter only the hostname in **IP:** or **Server Address**, without `http://` and without `:2101`. The port has its own field. * Use the hostname first. The Cube-a manual does not say whether the rover field **IP:** takes a hostname, and the S950 Web UI labels **Server Address** as an IP address. If the hostname is rejected or does not connect, enter the IP fallback for your region instead. * In Cube-a, load the mountpoint list and select `AUTO`. The list can show more entries than `AUTO`: select `AUTO`. In the S950 Web UI you can type `AUTO` in capitals. * One set of credentials allows one connection at a time. Keep only one connection path active on the receiver (for example, turn off **Automatically connect to network:** on **Internal Network** while you test **Phone Network**); a second rover needs its own data stream, see [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices). * If Cube-a still holds an entry from another correction service, do not reuse it. Add a new entry for RTKdata or type the values into the fields. RTKdata streams RTCM 3.2 with MSM4 messages (1074, 1084, 1094, 1114, 1124, 1134) and the station message 1005. The S950 manual states: "In Rover mode, S950 automatically recognizes the RTK corrections format between: RTCM 3.2, RTCM 3.0", so the S950 needs no format setting. For receivers that accept only legacy RTCM messages, see [Correction format](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md#correction-format). ## Requirements * **Stonex S1000 or S950** * **Android controller with a licensed Stonex Cube-a 7**, required for the S1000. Cube-a cannot be unlocked without its license code, and the license is bound to the Android device it was registered on: Stonex states that "you cannot use the same purchase code to unlock a copy of the program that is installed on another device". Take the controller that holds the license into the field. * **For Internal Network:** a **Nano SIM without PIN** with mobile data, and your carrier's **APN**. The S950 manual says to insert the card while the receiver is off and to lock it by sliding the metal cover. The S1000 brochure lists a Nano SIM as well; use a card without PIN there too. Test a new SIM in a phone first: PIN off, mobile data working, enough data volume. * **For Phone Network:** mobile data on the controller, from its own SIM or from a Wi-Fi hotspot * **For the S950 Web UI:** a smartphone or PC with a browser * **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 * **Open sky** for the first position, and a **survey pole** for tilt compensation {% 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 S950 and S1000; 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 | | ---------------------- | ------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | | S1000, S950 | This page | Cube-a, the S950 also in its Web UI | | S999, S880 | [Stonex S999 / S880](/integration-hub/gnss-rovers-and-receivers/stonex-s999-s880.md) | 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 | | 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 | On this page, the S1000 is set up in Cube-a only. The S950 Web UI steps apply to the S950 alone. **Stonex S890:** the printed Stonex Surveying Products Catalog 2026 lists the S890 as "S890 5W RADIO". Stonex has not published a user manual for the S890 (September 2026), so this page does not cover its setup. ## How do you set up NTRIP on the Stonex S950 or S1000 in Cube-a? To connect the S950 or S1000 to RTKdata 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**. The steps are the same for the S950 and the S1000. {% 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 slot. On the S950, use the **Sim card slot** and lock the card by sliding the metal cover. 2. Switch the receiver on. On the S950, hold the power button until you hear a beep. 3. Have your carrier's APN at hand. Cube-a asks for it in the network settings. {% 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 AR stakeout, the cameras or the laser over Wi-Fi, see [How do you keep corrections running with AR stakeout, camera or laser?](#how-do-you-keep-corrections-running-with-ar-stakeout-camera-or-laser) 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. See [Receiver SIM or controller internet](#receiver-sim-or-controller-internet-which-cube-a-datalink-do-you-need) if you are not sure which route fits. {% 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)**. Cube-a downloads the list through the receiver's network or through the controller's own mobile connection. If the receiver SIM is not online yet, turn on **Phone network access:** first. 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`. Leave **Fake GGA coordinates**, **Forced GGA** and **Record diff. corrections** off; the Cube-a manual describes the recording as "only for debug". 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); the next step shows when to connect. 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. {% hint style="warning" %} **Wait for your own position first.** Put the receiver under open sky and wait until Cube-a shows at least **SINGLE** before you tap **Apply** (with **Phone Network**, before **Start**). Started indoors, in a vehicle or right after power-on, the receiver has no position to send, and `AUTO` cannot assign a base station. {% endhint %} {% 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?](#how-do-you-know-corrections-are-really-arriving) below. {% endstep %} {% endstepper %} ## Receiver SIM or controller internet: which Cube-a datalink do you need? For RTKdata corrections on the S950 or S1000, choose **Internal Network** when the receiver has its own Nano SIM with mobile data, and **Phone Network** when the internet comes from the controller, from its SIM or a Wi-Fi hotspot. With AR stakeout, the cameras or the laser in use, **Internal Network** is the more robust choice. | | Internal Network | Phone Network | | ---------------------------------- | -------------------------------- | ------------------------------------------------- | | Internet from | Nano SIM in the receiver | Controller: its own SIM, or a Wi-Fi hotspot | | Cube-a page | **Rover network settings** | **Send diff. from controller** | | Mountpoint list | **Get Mountpoint (RTK network)** | **GET ACCESS POINT** | | GGA field | **GGA Upload Interval(s):** | **Send GGA delay \[sec]:** | | With AR stakeout, cameras or laser | Recommended | Only if Android keeps mobile data active on Wi-Fi | * **Phone Network** is a rover mode: the corrections come in over the controller's internet and Cube-a passes them to the receiver. Stonex notes that "This communication mode is only for rover." * With **Phone Network**, the S950 manual says Cube-a sets the receiver datalink to Bluetooth. That is normal, see the Web UI section below. * If the receiver SIM does not connect, a quick test with **Phone Network** shows whether the problem is the SIM or APN: if corrections arrive over the controller, check the SIM, the APN and whether your carrier allows port 2101, see [Troubleshooting & FAQ](/support/troubleshooting-and-faq.md). ## How do you set up NTRIP in the S950 Web UI? To connect the S950 to RTKdata in its Web UI, connect a phone or PC to the receiver's Wi-Fi hotspot, open `192.168.10.1`, log in, and on the **Working mode** page set **System Mode** to **Rover**, **Current Datalink** to **Network**, the SIM under **Internet Settings** and the RTKdata values under **Connection Settings**, then save. This path is documented for the S950 only; set up the S1000 in Cube-a. {% hint style="warning" %} **No GGA field in the S950 Web UI.** The network page of the S950 Web UI has no GGA setting, and Stonex does not document whether the receiver sends its position to the caster when it is set up this way. If the rover stays on **SINGLE** after the Web UI setup, set it up in Cube-a with **Internal Network** and **GGA Upload Interval(s):** `1` instead. **Use one setup path.** Do not switch back and forth between Cube-a and the Web UI. Settings applied from Cube-a change the receiver datalink: with **Phone Network**, Cube-a sets it to Bluetooth, so the Web UI then shows **Current Datalink** **Bluetooth**. That is normal according to the S950 manual. Do not change it back to **Network** in the Web UI. {% endhint %} {% stepper %} {% step %} ### Log in to the Web UI 1. Insert the Nano SIM as described under Requirements, with the receiver switched off, then switch the S950 on. 2. Connect the phone or PC to the receiver's Wi-Fi hotspot. The hotspot name is the receiver serial number. 3. Open `192.168.10.1` in a browser. 4. On **Login**, enter **User** `admin` and **Password** `admin`, the standard credentials in the S950 user manual, and tap **Submit**. {% endstep %} {% step %} ### Set the rover and the network datalink On the page **Working mode**, set **System Mode** to **Rover** and **Current Datalink** to **Network**. {% endstep %} {% step %} ### Set up the SIM Under **Internet Settings**: 1. Set **Network Link** to **SIM Card Network**. 2. Enter your carrier's **APN**. It is required. 3. Fill in **APN User** and **APN Password** only if your carrier requires them. {% endstep %} {% step %} ### Enter the RTKdata connection Under **Connection Settings**: 1. Set **Connection Mode** to **NTRIP**. 2. **Server Address:** the host for your region, for example `eu.rtkdata.com`. If it does not connect, enter the IP fallback for your region from the tabs above. 3. **Server Port:** `2101`. 4. **Mount Point:** type `AUTO` in capitals. You can also tap **Get Mountpoint** and select `AUTO` in **Select Mountpoint**; this needs a working internet connection and the server address and port set first. 5. **User** and **Password:** from *RTK Credentials*, not your website login. {% endstep %} {% step %} ### Save and check 1. Tap **Save** at the bottom of the **Working mode** page (the Stonex manual shows it there for the UHF datalink). 2. Open **Information** > **Network** and check **Caster Address** (your regional host or IP) and **Mount Point** `AUTO`. The same section also lists **Signal Level** and **IMEI**, which help when you check the SIM connection. 3. The **Dashboard** shows the working mode, the satellites in use, the quality of the solution and the expiry date of the receiver registration. Wait outside with open sky for **FIXED**. {% endstep %} {% endstepper %} ## How do you keep corrections running with AR stakeout, camera or laser? On the S950, Cube-a connects to the receiver over Wi-Fi for AR stakeout, the cameras and the laser, so take the RTKdata corrections through **Internal Network** with a SIM in the receiver. **Phone Network** with a SIM in the controller works only if Android keeps mobile data active while on Wi-Fi, and a smartphone hotspot cannot provide the internet in this mode. Stonex requires the Wi-Fi connection for AR stakeout on the S950, and a Stonex dealer FAQ states the same for the S950 laser and cameras. 1. In the Android Wi-Fi settings, connect the controller to the receiver's hotspot. On the S950, the hotspot name is the receiver serial number. 2. In Cube-a, open **Device** > **Communication**, set **Communication Mode:** to the Wi-Fi option and tap **Connect**. 3. Set up the corrections with **Internal Network**, as in the Cube-a steps above. 4. Only if you need **Phone Network** with a SIM in the controller: turn on the Android developer option **Mobile data always active**, so the controller keeps using mobile data while its Wi-Fi is connected to the receiver. 5. Do not use a smartphone hotspot as the controller's internet here. The dealer FAQ states that receiving corrections through a smartphone hotspot is not possible in this mode. {% hint style="info" %} On the S950, connect over Wi-Fi before you start. The same dealer FAQ reports that choosing a laser measurement while Cube-a is connected over Bluetooth makes Cube-a switch to Wi-Fi, which can cause conflicts. {% endhint %} * **AR stakeout:** the S950 manual asks for the control panel facing you, the Wi-Fi connection and active tilt correction. In Cube-a, open **Survey** > **Point Stakeout**, select the point, tap **Stake point** and then **AR**. * **S950 laser:** open **Survey** > **Point Survey**, choose the point type **Point by GPS+Diastimeter** and tap **Store**. Cube-a stores the coordinates, not the measured distance. * **S1000:** the S1000 brochure lists AR stakeout and a laser distance meter. Stonex has not documented the Cube-a menu for the S1000 laser. ### Turn on tilt compensation Tilt compensation works only with a **FIXED** solution. Turn it on in Cube-a and calibrate the IMU once with the correct pole height. 1. Open **Configure** > **System Settings** > **Sensor Options** (or **Calibrate** > **Sensor Options**) and select **Pole Tilt Correction** ("Requires a FIXED solution"). Tap **OK**. 2. In survey mode, after **FIXED**, follow the initialization screens: draw a circle on the ground with the pole tip, then move the receiver back and forth for a few seconds, rotate it by 90 degrees and repeat. 3. To calibrate, open **Calibrate** > **Calibrate Sensor** (screen **IMU Calibration**). A **FIXED** solution is required. Set the pole to 1.8 m and enter the same height in Cube-a. Slowly move the pole back and forth to initialize the IMU, then tap **Start**. Keep the pole tip on a fixed point on the ground and tilt the receiver back and forth in four directions, turning it by 90 degrees for each new section, until each section shows 50/50, reaching at least 45 and not more than 60 degrees, until **Calibration complete** appears. These steps come from the S950 user manual. On the S1000, follow the calibration screens Cube-a shows: the Cube-a manual says the **Calibrate Sensor** page depends on the connected receiver, requires a **FIXED** solution and warns that an incorrect antenna height makes the calibration inaccurate. ## How do you know corrections are really arriving? RTKdata corrections are really arriving on the S950 or S1000 when Cube-a shows **FLOAT** or **FIXED** and the differential correction age stays low, which the Cube-a manual gives as generally under 5 seconds. **DGNSS** alone does not prove an NTRIP connection, because Cube-a also shows it for corrections from SBAS satellites. Open the solution from the Cube-a status bar or under **Device** > **GNSS Status**: | Solution | Meaning (Cube-a manual) | What to do | | ---------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------- | | **NO FIX** | No position: not connected to the receiver, or no satellites | Check the Cube-a connection and the view of the sky | | **SINGLE** | No differential corrections | Check SIM or controller internet, credentials, `AUTO` and GGA | | **DGNSS** | Corrections from SBAS satellites, or from the base without a better solution | Do not treat it as proof of NTRIP; wait under open sky | | **FLOAT** | Corrections arrive, RTK not solved yet | Stay under open sky and wait | | **FIXED** | RTK fix, the final solution | Start measuring | * **Differential correction age** in **GNSS Status** is the delay of the incoming corrections. In RTK mode it is generally under 5 seconds (Cube-a manual); higher values point at a slow data connection. * With **Phone Network**, the **Receive:** bar on **Send diff. from controller** shows whether data is flowing. * On the S950, the datalink indicator on the front panel is green when "the differential corrections are being received/transmitted" (S950 manual). * The differential mode in **GNSS Status** always reads AUTO, because the receiver decodes the corrections. It is not the mountpoint. * If the solution stays on **FLOAT** for a long time although corrections arrive, use **Device** > **RTK Reset**. Stonex: "This function forces the GNSS board re-initialization". {% hint style="info" %} **Coming from an S980A or S900A?** The Cube-a manual lists a-RTK, which keeps RTK precision for a while after the corrections stop, as "only available with the GNSS A-Series receivers". Do not rely on it with the S1000 or S950. On the S950, **RTK Timeout \[6-8100]** in the Web UI **Satellite settings** sets how many seconds without corrections drop the fixed solution; Stonex's screenshot shows 30, so do not set it lower. {% endhint %} ## Which coordinate system should you use with AUTO in Cube-a? With the RTKdata `AUTO` mountpoint, choose the Cube-a project coordinate system that matches the datum `AUTO` delivers for your region, for example NAD83(2011) in the USA or ETRS89 (realization ETRF2000) in Europe; do not add **ITRF Conversion** and do not choose **RTCM1021-1027**. ### Coordinate system and heights with AUTO * **What AUTO delivers:** the regional datum for the position in your GGA, 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. Regions not listed get WGS84(G2139) at the mid-year epoch. `AUTO_ITRF2020` and `AUTO_ITRF2014` deliver ITRF2020 and ITRF2014 at the current epoch, and `AUTO_WGS84` delivers WGS84(G2139) at the mid-year epoch. The full table is in [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md). * **Project coordinate system:** when you create the project, tap **List** and pick the system that matches the `AUTO` datum for your region. For an existing project, change it under **Configure** > **Coordinate System**. * **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"; RTKdata sends 1005 and MSM4, not 1021 to 1027. * **ITRF Conversion:** leave it off with `AUTO`. The Cube-a manual warns that "this conversion is applied to all points in the current project". * **Heights:** RTKdata delivers ellipsoidal heights. For orthometric heights, enable a geoid under **Configure** > coordinate system > **Geoid files**; your own geoid files go into the `stonexcube` > `Geoid` folder. See [Understanding Heights](/get-started/understanding-heights.md). * **Offset against control:** 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). ## Troubleshooting | Problem | Cause | Fix | | --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | S950 set up in the Web UI, status stays **SINGLE** | The Web UI has no GGA setting; whether the receiver sends GGA this way is not documented | Set up the S950 in Cube-a with **Internal Network** and **GGA Upload Interval(s):** `1` | | Connected, but no corrections | GGA interval 0 or empty, or **Fake GGA coordinates** / **Forced GGA** on | Set **GGA Upload Interval(s):** or **Send GGA delay \[sec]:** to `1`, turn Fake and Forced GGA off | | No corrections after connecting indoors or in a vehicle | No own position to send, so `AUTO` cannot assign a base | Go outside with open sky, wait for at least **SINGLE**, then **Apply** or **Start** again | | **Internal Network** gets no internet | SIM with PIN, or inserted while the receiver was on | Remove the PIN on the SIM, insert it with the receiver off, enter the APN | | Carrier not in the **Operator:** list, or the wrong entry chosen | Only some carriers are stored in Cube-a | Choose **Custom** and enter the carrier's APN by hand | | Modem has network, but the caster does not connect | Company, M2M or IoT SIM with a private APN or firewall that blocks port 2101 | Test with **Phone Network** over the controller's internet. If that works, the SIM or APN is the problem, see [Troubleshooting & FAQ](/support/troubleshooting-and-faq.md) | | Receiver beeps and tracks no satellites | Receiver registration expired (not the Cube-a license); the S950 manual: "If the registration has expired the device will beep and it will not track satellites." | Check the expiry date in Cube-a **Device** > **Register**, or on the S950 in the Web UI **Dashboard**. A new code comes from your Stonex dealer: enter it in Cube-a under **Device** > **Register**, or on the S950 in the Web UI **Management** registration field, then tap **Submit** | | Cube-a does not start on your own phone or tablet | The Cube-a license is bound to the device it was registered on | Use the licensed controller. Cube-a shows the license under **Tools** > **Version and Update** > **Activation info** | | **Phone Network** gets no corrections while Cube-a uses the receiver Wi-Fi | Android prefers the Wi-Fi link to the receiver and stops using mobile data | Use **Internal Network** with a SIM in the receiver, or turn on the Android developer option **Mobile data always active** | | No corrections through a smartphone hotspot with laser or camera | Not possible in this mode (Stonex dealer FAQ) | Use a SIM in the receiver (**Internal Network**) or a SIM in the controller (**Phone Network**) | | S950 behaves oddly in Cube-a after choosing a laser measurement | Cube-a switches from Bluetooth to Wi-Fi, which can cause conflicts (dealer FAQ) | Connect over Wi-Fi from the start and use **Internal Network** | | Web UI shows **Current Datalink** **Bluetooth** | Normal with Cube-a **Phone Network** | Leave it. Changing it to **Network** breaks the Cube-a setup | | Receiver hotspot not visible, `192.168.10.1` and the Cube-a Wi-Fi connection fail | Receiver Wi-Fi set to CLIENT, where "its WiFi is not visible" | Connect over Bluetooth in Cube-a and set **WiFi Mode Settings** to **MASTER** | | S950 Web UI does not connect with the hostname | **Server Address** may accept only an IP address | Enter the IP fallback for your region from the tabs above | | Connected to the caster, but never **FLOAT** or **FIXED** | An entry other than `AUTO` selected from the mountpoint list | Load the list again and select `AUTO` | | Solution jumps between **FIXED**, **FLOAT** and **SINGLE** | The same credentials run on two connections, for example **Internal Network** still set to connect automatically while you test **Phone Network**, or a second device | Keep one path active, disconnect other devices, or add a data stream, see [Account & Credentials](/get-started/account-and-credentials.md#using-one-subscription-with-several-devices) | | **RTCM1021-1027** chosen as coordinate system parameters type | RTKdata does not send RTCM 1021 to 1027, only 1005 and MSM4 | Choose the coordinate system from **List** instead | | Login rejected, or no corrections | Website login used, mountpoint in lowercase, or a local datum name entered as mountpoint | Use the `rtk` username from *RTK Credentials* and `AUTO` in capitals | | Web UI fields or login do not match these steps | Instructions for another Stonex receiver, whose Web UI differs | Use the Web UI steps on this page only for the S950. Set up the S1000 in Cube-a | | AR stakeout menu not found | Menu described as "Stake out" in short form | Open **Survey** > **Point Stakeout**, select the point, **Stake point**, then **AR** | | Tilted points are off | IMU calibrated with a wrong pole or antenna height | Set the pole to 1.8 m, enter the same height in Cube-a and calibrate again | For connection problems that are not specific to Stonex, see [Common Connection Issues](/support/common-connection-issues.md). ## Frequently asked questions ### Can I set up NTRIP on the Stonex S1000 without Cube-a? Not with documented steps: Stonex has not published an S1000 user manual (September 2026), so RTKdata documents the S1000 NTRIP setup in Cube-a only, with **Internal Network** or **Phone Network**. The S1000 brochure lists a web interface, but its address, login and fields are not documented. Do not use the S950 Web UI values on the S1000. ### Why does the S950 Web UI connect but the rover stays on SINGLE? The RTKdata `AUTO` mountpoint needs the S950 position (GGA) before it sends corrections, and the S950 Web UI has no GGA setting; Stonex does not document whether the receiver sends GGA when it is set up there. Check outside with open sky, then check the APN, the credentials, **Mount Point** `AUTO` and, if the hostname does not connect, the IP fallback. If the rover still stays on **SINGLE**, set it up in Cube-a with **Internal Network** and **GGA Upload Interval(s):** `1`. ### What is the default login of the S950 Web UI? The S950 Web UI login is **User** `admin` and **Password** `admin` (S950 user manual); these are not your RTKdata credentials, which go into **User** and **Password** under **Connection Settings**. Connect to the receiver's Wi-Fi hotspot (named after the serial number) and open `192.168.10.1`. Other Stonex receivers use different standard credentials, so do not carry them over to the S950. ### Why does Cube-a warn that the base coordinates have changed? Cube-a warns because the RTKdata `AUTO` mountpoint can hand you over to a closer reference station as you move, see [NTRIP Server Settings](/get-started/network.md), and Cube-a shows a warning each time the base coordinates change when **Notify when base coordinates change:** is on. With `AUTO` this warning is expected and is not an error. ### Does a smartphone hotspot work while the S950 laser or camera is in use? No. According to a Stonex dealer FAQ, RTKdata corrections cannot come through a smartphone hotspot while the S950 laser or cameras are in use; in this mode Cube-a is connected to the S950 over Wi-Fi. Use a SIM in the S950 (**Internal Network**), or a SIM in the controller (**Phone Network**) with the Android developer option **Mobile data always active** turned on. ## Quick reference 1. Controller with licensed Cube-a 7; for **Internal Network** a Nano SIM without PIN in the receiver, inserted with the receiver off, and your carrier's APN. 2. **Device** > **Communication**: **Stonex GNSS**, **Bluetooth** (Wi-Fi for AR, cameras, laser), **Search**, **Connect**. 3. **Device** > **Working Mode** > **Rover**, **Datalink** **Communication Mode:** **Internal Network** or **Phone Network**. 4. **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`, **CORS Account** from *RTK Credentials*. 5. Load the list (**Get Mountpoint (RTK network)** or **GET ACCESS POINT**), select `AUTO`, GGA interval `1`, Fake and Forced GGA off. 6. Wait outside for at least **SINGLE**, then **Apply** (Phone Network: **Start**, **OK**, **Apply**) and wait for **FIXED**. 7. S950 only, Web UI: hotspot, `192.168.10.1`, `admin` / `admin`, **Working mode**: **Rover**, **Network**, **SIM Card Network** with **APN**, **NTRIP**, **Server Address**, **Server Port** `2101`, **Mount Point** `AUTO`, **Save**. ## 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): the four-point checklist and blocked-port checks * [Coverage Map](/get-started/coverage-map.md): check the station coverage at your site before you go out * [Stonex S999 / S880](/integration-hub/gnss-rovers-and-receivers/stonex-s999-s880.md): the same Cube-a steps, plus the Web UI of the S999 and S880 * [Stonex S599 / S590](/integration-hub/gnss-rovers-and-receivers/stonex-s599-s590.md): Stonex rovers without a modem, with internet from the controller or a hotspot * [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 Web UI * [Stonex X200GO / X120GO](/integration-hub/lidar-scanners-and-mobile-mapping/stonex-x200go-x120go.md): RTK for the Stonex handheld SLAM scanners in GOapp * [GNSS Rovers & Receivers](/integration-hub/gnss-rovers-and-receivers.md): all receiver guides and the universal NTRIP parameters ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) --- # 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-s1000-s950.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.