# Emlid Reach RX / RX2 NTRIP Setup: RTK Corrections

The Emlid Reach RX and RX2 are compact, lightweight multi-band GNSS receivers built for GIS data collection and mapping. Unlike the RS2+ which has a built-in antenna, the RX series is a small receiver module that pairs with an external antenna or attaches to a survey pole. It connects to your phone or tablet **exclusively via Bluetooth**, and the phone handles the internet connection for NTRIP corrections. The RX tracks GPS, GLONASS, Galileo, and BeiDou. The RX2 adds QZSS and L5 support for faster convergence.

## Requirements

* **Emlid Reach RX or RX2** with a compatible GNSS antenna
* **Emlid Flow app** installed on your phone or tablet (iOS or Android)
* **Internet connection** on your phone (cellular data)
* **RTKdata.com account** with active RTK credentials
* **Survey pole or mounting bracket** for the antenna
* **Note for iOS users:** You need the MFi-certified revision of the RX/RX2 for iOS Bluetooth compatibility. Check your device packaging or Emlid support if unsure.

{% 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 %}

#### Power on and pair via Bluetooth

1. Press the power button on the RX/RX2. The LED will begin blinking.
2. Open the **Emlid Flow** app.
3. Tap **+ Add new device**. The app scans for nearby Emlid devices via Bluetooth.
4. Select your **Reach RX** or **Reach RX2** from the list.
5. If prompted, confirm the Bluetooth pairing on your phone.
6. Once connected, the device dashboard appears showing satellite tracking status.
   {% endstep %}

{% step %}

#### Configure correction input

1. Tap **Correction input** in the left-side menu.
2. Toggle correction input **On** if it is not already enabled.
3. Select **NTRIP** as the correction type.
4. Tap **Add new NTRIP profile**.
   {% endstep %}

{% step %}

#### Enter RTKdata.com NTRIP settings

Fill in the fields. Select the tab for your region:

{% tabs %}
{% tab title="North America" %}

* **Host (domain):** `rtk.rtkdata.com`
* **Host (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" %}

* **Host (domain):** `eu.rtkdata.com`
* **Host (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" %}

* **Host (domain):** `aus.rtkdata.com`
* **Host (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 %}

Also configure:

* **Send receiver position to the correction service:** **Enabled**

Tap **Save**.

{% hint style="warning" %}
Only these four mountpoints are valid. Always use **ALL CAPS**.
{% endhint %}
{% endstep %}

{% step %}

#### Connect and verify

1. Tap **Connect** on your saved profile.
2. The correction input status changes to **Connected**.
3. Monitor the solution: **Single** → **Float** → **Fix**.
   {% endstep %}

{% step %}

#### Set up mock location (Android)

The RX/RX2 outputs corrected positions to your field app via mock location on Android. This makes every app on your phone use the centimeter-level position from the RX instead of the phone's built-in GPS.

1. On your Android phone, go to **Settings → About phone** and tap **Build number** 7 times to enable Developer Options.
2. Go to **Settings → Developer Options → Mock location app**.
3. Select **Emlid Flow** as the mock location provider.
4. Open your field app (ArcGIS Field Maps, Mergin Maps, QField, SW Maps, etc.). It will now receive the corrected RTK position automatically.

**On iOS**, mock location is not available. Instead, select the RX/RX2 as an external Bluetooth GNSS source directly in your field app's location settings.
{% endstep %}
{% endstepper %}

## What to expect

* **LED indicators:** Solid green = powered on and tracking. Blinking blue = Bluetooth connected. The LED does not directly indicate Fix status — check the app.
* **Convergence time:** Typically 15–60 seconds to Float, then 30–90 seconds to Fix with good sky visibility.
* **Accuracy at Fix:** 1–2 cm horizontal, 2–4 cm vertical.
* **Battery life:** Approximately 8–10 hours (RX) or 10–12 hours (RX2) with Bluetooth and NTRIP active.

## Vertical reference (heights)

{% hint style="info" %}
Heights from RTKdata.com are **ellipsoidal**, not orthometric (mean sea level). If your project requires MSL heights, apply a geoid model in your GIS software or use Emlid Flow's geoid settings.
{% endhint %}

## Troubleshooting

| Problem                                    | Cause                                        | Fix                                                                                                                             |
| ------------------------------------------ | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| RX not appearing in Emlid Flow             | Bluetooth not enabled or device out of range | Ensure Bluetooth is on. Keep the RX within 10 meters. Restart Bluetooth on your phone if needed.                                |
| NTRIP connects but solution stays Single   | GGA not being sent                           | Verify **Send receiver position** is toggled on in the NTRIP profile.                                                           |
| Float but no Fix after several minutes     | Obstructed sky or multipath                  | Move away from buildings, metal structures, and dense tree cover.                                                               |
| Field app not receiving corrected position | Mock location not configured                 | On Android, enable Developer Options → Mock location app → Emlid Flow. On iOS, use the Bluetooth GNSS method in your field app. |
| "Authentication failed" error              | Wrong credentials                            | Use the username and password from your RTK dashboard, not your RTKdata.com website login.                                      |

## Tips and tricks

* **The RX2 converges faster than the RX** due to additional L5 tracking. If you frequently work in challenging environments, the RX2 is worth the upgrade.
* **Bluetooth range is about 10 meters.** Keep your phone in a pocket or chest mount rather than leaving it in your vehicle.
* **Antenna matters.** The RX/RX2 accuracy depends heavily on the external antenna quality. Use the Emlid-recommended survey antenna for best results.
* **Save multiple NTRIP profiles** if you work across regions — one for EU, one for NA, etc. Switch between them with a single tap.
* **Enable logging** for PPK backup. If corrections drop, you can post-process the raw data against RTKdata RINEX files.


---

# Agent Instructions: 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:

```
GET https://docs.rtkdata.com/integration-hub/gnss-rovers-and-receivers/emlid-reach-rx-rx2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.