NTRIP Corrections Settings
The NTRIP Corrections settings screen manages the built-in NTRIP client that streams RTCM corrections from a caster over the internet and forwards them to your GNSS receiver. This is where you create, edit, test, and connect NTRIP configurations. For the full walkthrough on how RTK works and how to verify a Fixed solution, see Mapit NTRIP Client.
The NTRIP client requires a Mapit Pro Plus subscription. See Mapit Pro Plus for details.
- Android
- iOS
Go to Settings - NTRIP Corrections to access this screen.
Configuration list
The screen opens on a list of saved NTRIP configurations. You can keep multiple configurations - one per caster or mountpoint - and switch between them without retyping credentials.
- Tap the + button to add a new configuration
- Tap a configuration row to connect
- Tap the overflow (⋮) to edit, delete, or test a configuration
- If no configurations exist yet, the list shows No NTRIP configurations yet. Tap + to add one.
When a configuration is active, a status bar at the top of the screen shows the connection state (Connecting..., Connected, Reconnecting...), the active mountpoint, and the live data rate in KB/s.
Add / Edit Configuration dialog
| Field | Description |
|---|---|
| Configuration Name | A friendly name so you can recognise the entry in the list (e.g. SmartNet UK, Local Base). |
| Caster Host | Hostname or IP address of the NTRIP caster (e.g. rtk2go.com). |
| Port | TCP port of the caster (commonly 2101). |
| Username | Your caster account username. |
| Password | Your caster account password. Stored securely on the device. |
| Mountpoint | The specific stream to subscribe to. Tap Select Mountpoint to load the caster source table and pick from a list of mountpoints reported by the caster. |
| Receiver Target | Where to forward RTCM once it arrives. Options: Test (discard - useful to verify the caster connection), Bluetooth (classic SPP), TCP, USB, BLE. The receiver target must match the External GNSS connection you actually use. |
Mountpoint selection
Tap Select Mountpoint inside the dialog to fetch the caster's source table. The app connects, lists every mountpoint with its identifier, format, and approximate location, and lets you pick one by tapping. If the source table is empty or fails to load, you will see Loading source table... followed by an error - double-check host, port, and credentials.
Auto-connect
| Setting | Default | Description |
|---|---|---|
| Auto-connect | Off | When enabled, NTRIP automatically connects as soon as your external GNSS receiver connects. When disabled, you must tap Connect manually each session. |
Auto-connect is convenient for daily RTK workflows; disable it if you only occasionally need corrections or if you swap between configurations frequently.
Send NMEA GGA
| Setting | Default | Description |
|---|---|---|
| Send NMEA GGA | Off | Send your current position to the caster as a GGA sentence. Required by VRS (Virtual Reference Station) networks that compute per-rover corrections based on your location. |
| GGA Send Interval | - | How often to transmit your position (in seconds) when Send NMEA GGA is enabled. |
Enable Send NMEA GGA when your caster requires it - most national correction services do. For a single physical base, a non-VRS caster, or the Test receiver target, you can leave it off.
Connection status and errors
The connection status bar may report:
| Status | Meaning |
|---|---|
| Disconnected | No NTRIP session active. |
| Connecting... | TCP connect and HTTP handshake in progress. |
| Connected | RTCM is streaming - the data rate shows live throughput. |
| Reconnecting... | Network dropped. The client is retrying; existing configuration is preserved. |
Typical error messages:
| Error | Cause |
|---|---|
| Connection to NTRIP caster failed | Host unreachable, wrong port, or caster is down. |
| Authentication failed. Check username and password. | Wrong credentials. |
| Mountpoint not found on caster | The mountpoint in your configuration no longer exists on the caster. |
| No data received from caster | Caster accepted the connection but is not sending RTCM (often a VRS needing GGA). |
| NTRIP stream closed unexpectedly | Caster closed the stream. Re-connect and check your subscription. |
Read next:
- Mapit NTRIP Client - full walkthrough including how RTK works, caster selection, RTCM forwarding, and troubleshooting
- External GNSS Settings - the receiver connection must be set up before NTRIP can forward corrections
- RTK and Fix Types - how to verify RTK Float and RTK Fixed status after NTRIP connects
Go to Settings - NTRIP Corrections to access this screen.
On iOS, the NTRIP client forwards RTCM to whichever external receiver is currently active as the GPS source (see External GNSS Settings on iOS):
- Bluetooth BLE - RTCM is written to the Nordic UART Service RX characteristic.
- Bluetooth Classic - RTCM is written to the MFi-certified accessory's output stream. Currently whitelisted for the Eos Arrow series only; other manufacturers are pending Apple MFi approval.
- TCP/IP NMEA - RTCM is not forwarded over outbound TCP (this transport is receive-only).
All other configuration fields - host, port, mountpoint, credentials, GGA, auto-connect - behave the same as on Android.
See Mapit NTRIP Client for the iOS walkthrough.
The NTRIP client requires a Mapit Pro Plus subscription. See Mapit Pro Plus for details.