> 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/singularxyz-e1-pro.md). # SingularXYZ E1 Pro RTK Setup: SingularPad NTRIP Connect the SingularXYZ E1 Pro to RTKdata NTRIP in SingularPad. Data Link setup, mountpoint AUTO, port 2101, GGA output and the geoid model for correct heights. The **SingularXYZ E1 Pro** is a multi-constellation GNSS rover configured through the **SingularPad** Android field app. The same workflow applies to other SingularXYZ receivers running SingularPad, including the **E1** and the **Sfaira One**. {% hint style="warning" %} Menu wording in SingularPad differs slightly between app versions. The paths below reflect the screens seen in recent SingularPad releases. If a label does not match exactly, look for the equivalent entry in the same menu. {% endhint %} ## Requirements * **SingularXYZ E1 Pro** (or another SingularXYZ receiver) powered on with clear sky visibility * **SingularPad** installed on an Android phone, controller or tablet * **Bluetooth pairing** between the receiver and the device running SingularPad * **Internet connection** on the device running SingularPad (mobile data or hotspot) * **RTKdata.com account** with active RTK credentials (username starting with `rtk` and password from your RTK dashboard) * **Geoid model** for your region if you need orthometric heights * **Survey pole** with the correct antenna height noted {% 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 %} ## Step-by-step setup {% stepper %} {% step %} ### Connect SingularPad to the receiver 1. Power on the E1 Pro and pair it to your phone or controller over **Bluetooth**. 2. Open **SingularPad** and go to **Device**, then connect to your receiver. 3. Wait until SingularPad shows satellite bars and a position. If the status line shows **H: NA / V: NA** with 0 satellites, the app is not connected to the receiver yet. {% hint style="info" %} Do this outdoors. The receiver needs its own GNSS position before it can report a location to the caster. {% endhint %} {% endstep %} {% step %} ### Create the project and set the coordinate system 1. Go to **Project** > **Project Manager** and create a project. 2. Open **Project Settings** > **Coordinate System** and assign your horizontal system (for example NAD83 in the US, GDA2020 with the correct MGA zone in Australia). 3. Assign a **geoid model** for your vertical datum in the same area. {% hint style="danger" %} Set the coordinate system **before** the NTRIP connection. Skipping the geoid model is the most common first-time mistake and produces elevations that are off by 10 to 15 m (30 to 50 ft) while the horizontal position looks perfect. {% endhint %} {% hint style="warning" %} The **Ellipsoid Manager** is not the projection screen. It holds the ellipsoid only. If you see ellipsoid parameters but no grid, you are on the wrong screen: go back to the project coordinate system settings. {% endhint %} {% endstep %} {% step %} ### Open Device > Data Link and select NTRIP 1. Go to **Device** > **Data Link**. 2. Set the connection type to **Phone Internet** (the internet connection of the device running SingularPad). 3. Set **Connect Mode** to **NTRIP**. {% endstep %} {% step %} ### Enter the RTKdata.com NTRIP settings Select the tab for your region: {% tabs %} {% tab title="North America" %} * **Server / Host:** `rtk.rtkdata.com` * **IP fallback:** `13.56.117.10` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Europe" %} * **Server / Host:** `eu.rtkdata.com` * **IP fallback:** `3.73.41.96` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% tab title="Australia" %} * **Server / Host:** `aus.rtkdata.com` * **IP fallback:** `54.206.56.130` * **Port:** `2101` * **Username / Password:** From *RTK Credentials* in the internal dashboard (not website login) * **Mountpoint (ALL CAPS):** `AUTO` (recommended), or `AUTO_WGS84`, `AUTO_ITRF2020`, `AUTO_ITRF2014` {% endtab %} {% endtabs %} {% hint style="danger" %} Type `AUTO` manually in all capital letters. The username starts with `rtk` and comes from the **RTK Credentials** section of your dashboard. It is **not** your website login. This is the single most common cause of failed connections. {% endhint %} {% endstep %} {% step %} ### Enable position (GGA) output In the same Data Link or NTRIP screen, enable the option that sends your receiver position to the caster. Depending on the app version this is labeled **Send receiver position**, **GGA output**, or similar wording. {% hint style="danger" %} Without GGA, the connection can look successful while no corrections are ever delivered. RTKdata reads your GGA position to route you to the nearest reference station. Sessions with a **0% fix rate** are almost always caused by GGA not being sent. {% endhint %} {% endstep %} {% step %} ### Verify the fix 1. Apply the settings and watch the solution status: **Single** > **Float** > **Fix**. 2. In open sky, expect **Fix** within roughly 30 to 90 seconds. 3. Before staking out or collecting points, enter the correct **antenna / pole height** in SingularPad. A missing or default pole height goes straight into your height error. {% endstep %} {% endstepper %} ## Vertical reference (heights) {% hint style="info" %} RTKdata delivers **ellipsoidal heights**. To get orthometric heights (mean sea level), load a geoid model in your SingularPad project under **Project Settings** > **Coordinate System**. {% endhint %} SingularPad ships with **EGM96**, which works globally and is adequate for most fieldwork. It does not ship **GEOID18** natively. If you need the US NAVD88 model, download the GEOID18 file from NGS and load it into the project. A US user who did this checked against a known control point and landed within about 3 inches vertically. ## Using RTKdata with a local base If you own two SingularXYZ receivers, you can run one as a local base over UHF radio and one as a rover. In that setup the rover gets corrections from your own base, not from RTKdata, so you would normally use one method or the other rather than both at once. Where RTKdata still helps is **positioning the base**. A base that only averages its own position gives you good relative precision, but the absolute coordinates can be off by a metre or more against deed records, county maps and survey monuments. Connecting the base to RTKdata first ties it to real-world coordinates, and the rover then keeps the short-baseline advantage under marginal sky. ## Troubleshooting | Problem | Cause | Fix | | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ | | "I am getting an authentication error" when connecting | No active plan or expired trial on the account. This is not a device or mountpoint problem. | Check your subscription status in the RTKdata dashboard. Once the plan is active, retry with the same settings and mountpoint `AUTO`. | | Thousands of sessions logged with a **0% fix rate** | The rover is not sending its position (NMEA GGA) to the caster, so no reference station can be assigned. | Enable the send-position option in the Data Link / NTRIP settings, then reconnect outdoors. | | "I see ellipsoid parameters but not grid" | You are in the **Ellipsoid Manager**, which holds only the ellipsoid, not the projected grid. | Leave that screen and set the projection under the project coordinate system settings. | | Coordinate system search returns an empty list when typing `EPSG` | Some app versions index the library by name, not by code. | Search by name (for example the datum or country name) instead of the EPSG code. If nothing matches, define the projection manually. | | "I have found the geoid selection part but it only gives option for egm96" | GEOID18 is not included natively in SingularPad. | Use EGM96 (accurate to a few centimetres for most work), or download the regional geoid file and load it into the project. | | NTRIP connects and the horizontal position is right, but elevation is off by 30 to 50 ft | No geoid model applied. RTKdata delivers ellipsoidal heights. | Load a geoid model under **Project Settings** > **Coordinate System**. | | Status shows **H: NA / V: NA**, 0 satellites and a **Disconnect** button | SingularPad is not connected to the receiver hardware. | Reconnect under **Device**. No correction setting helps until the receiver link is up. | | Average fix rate stays at 8 to 16% although the best session reached 80 to 100% | Intermittent sky obstruction, GGA not sent consistently, or not enough convergence time. | Work with 15 to 20 degrees of clear horizon all round, send GGA at 1 Hz, and allow 30 to 90 seconds after connecting before expecting a Fix. | | Fix rate collapses under tree canopy | Canopy blocks satellite signals. The correction stream is not the limiting factor. | Move to open field, a clearing edge or an elevated spot. Corrections cannot compensate for blocked satellites. | | Calibration residuals appear in red after "calibrate point" | Wrong projection parameters, antenna height missing, or no geoid model in the project. | Confirm the projection parameters, enter the pole height, load the geoid model, and repeat the calibration on a solid Fix with 15+ satellites. | | Computed elevation comes out around 100 m negative after a site calibration | The geoid model is not being applied to the project, or the vertical datum conflicts with the assigned projection. | Verify the projection assigned to the project and re-apply the geoid model. Make sure the known point elevation is orthometric, not ellipsoidal. | | Collected coordinates do not match supplied GDA2020 grid values (Australia) | `AUTO` delivers corrections in GDA2020, but the map projection (MGA zone) is applied on the device side. | Set the output coordinate system in SingularPad to GDA2020 with the correct MGA zone for your area. | | Credentials rejected | Website login used instead of RTK credentials. | Use the username starting with `rtk` and the password from *RTK Credentials* in your dashboard. | | Coordinate system shows as "Local system" | SingularPad is taking a network-defined system from the RTCM stream instead of your configured projection. | Override it with a manually defined coordinate system in the project settings. | ## Related Guides * [CHC i93 / i90 / i76 / i73 / X7](/integration-hub/gnss-rovers-and-receivers/chc-i93-i90.md): comparable Android field app workflow with the same Data Link and GGA decisions * [NTRIP & GGA Essentials](/integration-hub/ntrip-clients-and-field-software/ntrip-and-gga-essentials.md): why the caster needs your GGA position before the `AUTO` mountpoint can route corrections * [Understanding Heights](/get-started/understanding-heights.md): geoid models per region, including the SingularPad steps for loading one * [Coordinate Systems & Datums](/get-started/coordinate-systems-and-datums.md): which datum each mountpoint delivers and how to resolve a mismatch * [GNSS Rovers & Receivers](/integration-hub/gnss-rovers-and-receivers.md): all receiver guides, including universal settings for models without their own page ## Related Industry Solutions * [Surveying](https://rtkdata.com/surveying/) * [Construction](https://rtkdata.com/construction/) * [Agriculture](https://rtkdata.com/agriculture/) --- # 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/gnss-rovers-and-receivers/singularxyz-e1-pro.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.