> 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/ntrip-clients-and-field-software/trimble-unity.md). # Trimble Unity NTRIP Setup: Source Field & TMM Set up RTKdata NTRIP corrections in Trimble Unity. Enter host, port 2101 and type the AUTO source manually, or route corrections via Trimble Mobile Manager. **Trimble Unity** is Trimble's asset lifecycle management platform for utilities, municipalities, and public infrastructure operators. Office teams use the Unity web app to manage assets, work orders, and GIS data, while field crews use the Unity mobile apps (Unity Field, Unity Mobile) to inspect assets, capture locations, and close out work orders offline. Because Unity captures asset positions that end up in a GIS of record, centimeter accuracy matters. Unity takes its position from a connected GNSS receiver, and that receiver needs an RTK correction stream. This guide shows how to point Unity at RTKdata.com. ## Requirements * **Trimble Unity account with admin rights.** The GPS configuration is created in the Unity web app and requires admin credentials. * **GNSS receiver** supported by your Unity deployment (for example a Trimble R-series receiver, or a Catalyst DA2). * **Mobile device** running the Unity mobile app, with the receiver paired. * **Internet access** on the field device (cellular data or hotspot). * **Active RTKdata.com account** with RTK credentials (username starts with `rtk`, taken from *RTK Credentials* in the internal dashboard, not your website login). {% 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 %} {% hint style="warning" %} Unity ships in several modules (Work Management, Field, Maintain, AMS) and the positioning screens differ slightly between them and between releases. Labels below follow Trimble's published GPS configuration documentation. If your build words a field differently, match it by function: an address field, a port field, a source or mountpoint field, and a credentials pair. {% endhint %} ## Step-by-step setup {% stepper %} {% step %} ### Create a positioning configuration in the Unity web app 1. Log in to the **Trimble Unity** web app with **admin** credentials. 2. Open the menu and click **GPS Config**. 3. Click **Create Config** (top right). 4. Enter a name in **Positioning Configuration Name**, for example `RTKdata`. 5. Choose your receiver in the **Connection Type** dropdown (external receivers appear as entries such as `External: R2`). 6. Under **Antenna Settings**, set **Pole Height(Meters)** if you work off a survey pole. {% endstep %} {% step %} ### Select NTRIP as the correction source Under **Real Time Correction**, select **NTRIP** in the **Primary Correction** dropdown. {% hint style="danger" %} **Prefix the address with `http://`.** Trimble's own documentation states: "If you are using NTRIP correction source, make sure you prefix the server URL or IP address with `http://`." Unity will not resolve a bare hostname. Enter `http://rtk.rtkdata.com`, not `rtk.rtkdata.com`. {% endhint %} {% endstep %} {% step %} ### Enter the RTKdata connection details Select your region and enter the matching values: {% tabs %} {% tab title="North America" %} * **Server / caster address:** `http://rtk.rtkdata.com` * **IP fallback:** `http://13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Source / Mountpoint (ALL CAPS):** `AUTO` (recommended). Alternatives: `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Europe" %} * **Server / caster address:** `http://eu.rtkdata.com` * **IP fallback:** `http://3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Source / Mountpoint (ALL CAPS):** `AUTO` (recommended). Alternatives: `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Australia" %} * **Server / caster address:** `http://aus.rtkdata.com` * **IP fallback:** `http://54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Source / Mountpoint (ALL CAPS):** `AUTO` (recommended). Alternatives: `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} RTKdata streams standard **RTCM 3.2** corrections over NTRIP, so no proprietary Trimble format (VRS, iMAX, CMRx) is involved. {% endstep %} {% step %} ### Type `AUTO` into the Source field Type **`AUTO`** into the **Source** field in ALL CAPS and leave it there. You can also press **Get Source** and select it from the list. Do not clear the field if it turns red. See [The Source field and the short mountpoint list](#the-source-field-and-the-short-mountpoint-list) below. Click **Save** (top right). {% endstep %} {% step %} ### Connect on the mobile device and verify Fix 1. Open the Unity mobile app and log in. 2. Tap the **Settings** icon, then **GPS**. 3. Tap **Positioning Configuration** and select the profile you created. 4. Tap **Pole Height** and adjust if needed. 5. Tap **GPS Receiver**, then **Connect**. 6. Go **outdoors with a clear view of the sky** and tap **Location Status** to watch the solution. | Status | Meaning | | ----------------------- | ----------------------------------------------- | | **SINGLE / Autonomous** | Basic GNSS position, no corrections applied yet | | **FLOAT** | Corrections arriving, solution converging | | **FIX** | Centimeter-level accuracy active | Convergence typically takes 5 to 60 seconds in open sky. {% hint style="danger" %} **The receiver must be outdoors before corrections can work.** RTKdata selects the best base station from the position your receiver reports (GGA). Indoors, the receiver has no position to report, so no corrections are sent and you stay on SINGLE. Unity does not expose a separate "send GGA" toggle, the receiver handles this once it has a satellite position. See [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md). {% endhint %} {% endstep %} {% endstepper %} ## The Source field and the short mountpoint list When you press **Get Source**, Unity downloads the caster's source table and validates whatever is in the **Source** field against it before saving. RTKdata publishes a source table, and it is deliberately short. `AUTO` is the entry to type, in ALL CAPS, with the reference-frame variants available when a project is tied to a specific frame. A coordinate system name is never a valid Source. What you will not find in the table is a list of individual base stations, because you are not meant to pick a station at all: * **RTKdata picks the best station for you.** The `AUTO` mountpoint is resolved server-side from the position your receiver reports, and the caster assigns the best available base station for where you are standing. * **No guesswork from a dropdown.** On networks that publish hundreds of stations, the operator has to guess which one is nearest, healthiest and on the right reference frame. Nothing in such a list tells you which station is having a bad day. * **It follows the crew.** Move to the next job and the assignment updates automatically. There is no stale mountpoint in a saved profile that quietly keeps pulling from a base 80 km away. If the list comes back **empty**, the caster address is the first thing to check: Trimble requires the `http://` prefix on NTRIP sources, so enter `http://rtk.rtkdata.com` rather than the bare hostname. Typing `AUTO` manually into the **Source** field in ALL CAPS is always valid, whether or not the list populated. {% hint style="info" %} If your Unity build hard-blocks **Save** while the Source field is flagged, use the Trimble Mobile Manager route below. That is Trimble's documented path for external receivers anyway, and it takes the correction setup out of Unity entirely. {% endhint %} ## Alternative: route corrections through Trimble Mobile Manager For external GNSS receivers, Trimble documents the correction setup as living **outside** the Unity app: "This connection is configured outside of the Trimble Unity Field app using Trimble Mobile Manager (TMM)." Unity then simply consumes the corrected position that TMM provides. This is the most reliable route with RTKdata, because TMM accepts a manually typed mountpoint. 1. Install **Trimble Mobile Manager** on the same device and connect your receiver. 2. In TMM, open **Configuration** and set the **GNSS correction source** to **Custom local**. 3. Set **Protocol** to **NTRIP**. 4. Enter the RTKdata **URL** and **Port** (`2101`) for your region from the tabs above. 5. Set the corrections service **username and password** from your RTKdata RTK credentials. 6. Enter the mountpoint **`AUTO`** in ALL CAPS instead of picking from the mount point table. 7. For the **GNSS source reference frame**, select the frame matching the `AUTO` variant you chose, or **Auto** if unsure. 8. In Unity, go to **Settings > GPS** and turn on the **Trimble Mobile Manager** toggle ("Turn on to enable Trimble Mobile Manager's positioning configuration"). {% hint style="info" %} With the TMM toggle enabled, Unity's own **Antenna Height** field becomes unavailable, because pole height and antenna settings are then managed in TMM. Set them there instead. {% endhint %} {% hint style="warning" %} **Catalyst Free will not accept a third-party caster.** If you use a Trimble DA2 with a Catalyst Free subscription, configuration changes in TMM are not applied and RTKdata corrections will not reach the receiver. You need at least a Catalyst Basic subscription. See [Trimble Receivers with RTKdata](/integration-hub/gnss-rovers-and-receivers/trimble-receivers.md). {% endhint %} ## Vertical reference (heights) {% hint style="info" %} Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). If your Unity workflow records elevations against a vertical datum, apply the appropriate geoid model. In Trimble Mobile Manager this is set under **Configuration > Geoid**. {% endhint %} ## Troubleshooting | Problem | Cause | Fix | | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "Unable to populate source" / Source list is empty after **Get Source** | Caster address entered without the `http://` prefix, so Unity never reaches the source table | Enter `http://rtk.rtkdata.com` (or your regional host) and press **Get Source** again. Typing `AUTO` in ALL CAPS directly into the **Source** field also works. | | **Source** field highlights red on **Save** | Unity validated the Source against a source table it did not receive | Check the `http://` prefix and the port (`2101`), then retry. The value `AUTO` itself is correct. If Unity still hard-blocks the save, configure corrections in Trimble Mobile Manager instead. | | "Source is not valid", save rejected | Same as above | Retry with the prefix, or use the Trimble Mobile Manager route, where the mountpoint is typed manually. | | Cannot find a "send GGA" or "send position" option | Unity does not expose a GGA toggle, the receiver sends position once it has a satellite fix | Take the receiver outdoors with clear sky. No manual toggle is required. | | Connects but stays on SINGLE or FLOAT | Receiver indoors or under canopy, so no position is reported to the caster | Move to open sky. Confirm the receiver has satellite lock in **Location Status**. | | Cannot reach the caster at all | Address entered without the `http://` prefix | Enter `http://rtk.rtkdata.com` (or your regional host). Trimble requires the prefix for NTRIP sources. | | Authentication fails | Website login used instead of RTK credentials | Use the *RTK Credentials* from the internal dashboard. The username starts with `rtk` and is case-sensitive. | | Corrections never apply on a DA2 | Catalyst Free subscription blocks third-party correction sources | Upgrade to at least Catalyst Basic, or use a receiver that accepts external NTRIP directly. | | Field crew works but office profile does not | Positioning configuration not assigned or not selected on the device | On the device, check **Settings > GPS > Positioning Configuration** and select the RTKdata profile explicitly. | ## Tips for best results * **Roll out one profile.** Create a single `RTKdata` positioning configuration with `AUTO` and assign it to the whole crew. Because `AUTO` is position-resolved, the same profile is correct everywhere in the region. * **Never browse for mountpoints.** Typing `AUTO` in ALL CAPS is the supported path on every Trimble product, not a workaround. * **Remember the `http://` prefix.** It is the single most common reason a Unity NTRIP source silently fails to connect. * **Test the profile on one device outdoors** before pushing it to the full crew, so you validate credentials and sky view separately from the configuration itself. * **If Unity fights you, use TMM.** Trimble itself documents Trimble Mobile Manager as the configuration point for external GNSS receivers with Unity Field. ## Related Guides * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why RTKdata needs your position and how the AUTO mountpoint resolves to a base station * [Trimble Receivers with RTKdata](/integration-hub/gnss-rovers-and-receivers/trimble-receivers.md): Trimble Access, Earthworks, and Catalyst licensing notes that also apply to Unity deployments * [Trimble R12i / R10 / R750](/integration-hub/gnss-rovers-and-receivers/trimble-r12i.md): receiver-side setup for the R-series units commonly paired with Unity * [MyUtiliGuard (Subsite UtiliGuard 2 RTK)](/integration-hub/ntrip-clients-and-field-software/myutiliguard.md): another utility field app where the mountpoint is typed rather than browsed * [NTRIP Clients & Field Software](/integration-hub/ntrip-clients-and-field-software.md): full list of apps and field software with RTKdata setup guides ## 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.rtkdata.com/integration-hub/ntrip-clients-and-field-software/trimble-unity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.