Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

ArduSimple simpleRTK2B NTRIP Setup: F9P RTK

Connect ArduSimple simpleRTK2B (u-blox ZED-F9P) and simpleRTK3B (Unicore, Septentrio) boards to RTKdata NTRIP via phone app, PC tool or WiFi NTRIP Master.

The ArduSimple simpleRTK2B is a low-cost RTK board built around the u-blox ZED-F9P multi-band GNSS module. It tracks GPS, GLONASS, Galileo, and BeiDou on L1/L2 frequencies and delivers centimeter-level accuracy with RTK corrections. The simpleRTK3B boards use Unicore or Septentrio modules instead, and the u-blox ZED-F9R with IMU is on the simpleRTK2B Fusion. Check which module your board carries in the table below, because the steps to connect it to RTKdata depend on it. ArduSimple's RTK Handheld 2 Mapping Kit and RTK Calibrated Surveyor Kit contain a pre-configured ZED-F9P receiver, so Method A applies to them. On iOS, ArduSimple supports only the SW Maps app with these kits. This guide covers three ways to connect the boards to RTKdata NTRIP corrections: Bluetooth to a phone (fieldwork), USB to a PC tool (bench testing and configuration) and the WiFi NTRIP Master in the XBee socket (no phone or PC, for example on a robot).

Requirements

  • ArduSimple simpleRTK2B or simpleRTK3B board with GNSS antenna and clear sky view

  • Method A: Android phone with Bluetooth and the Lefebure NTRIP Client or SW Maps app, plus the ArduSimple Bluetooth module in the XBee socket. The Bluetooth module does not work with iOS devices.

  • Method B: PC with a USB cable and the tool for your module: u-center (u-blox, Windows), UPrecise (Unicore, Windows 7/8/10 64-bit according to ArduSimple) or a web browser (Septentrio)

  • Method C: ArduSimple WiFi NTRIP Master in the XBee socket and a 2.4 GHz WiFi network or phone hotspot with internet access

  • RTKdata.com account with active RTK credentials (username starting with rtk)

Don't have an RTKdata.com account yet? Start 30-day Free Trial or View Pricing

Which module is on your ArduSimple board?

Board
GNSS module
Tool for Method B

simpleRTK2B Budget

u-blox ZED-F9P

u-center

simpleRTK2B Fusion

u-blox ZED-F9R with IMU

u-center

simpleRTK3B Budget

Unicore UM980

UPrecise

simpleRTK3B Compass

Unicore UM982, dual-antenna heading

UPrecise

simpleRTK3B Fusion

Unicore UM981 with INS

UPrecise

simpleRTK3B Heading

Septentrio mosaic-H

Web interface

simpleRTK3B Pro

Septentrio mosaic-X5

Web interface

The XBee socket is wired to UART2 of the ZED-F9P on the simpleRTK2B Budget and to COM2 on the simpleRTK3B boards. The Bluetooth module and the WiFi NTRIP Master both use this port.

RTKdata streams carry L5, E5a and B2a where the base station tracks them; some older base stations send L1 and L2 only. RTCM 1230 (GLONASS code-phase biases) comes from the base station, and most RTKdata base stations do not send it. Without it, a receiver from another manufacturer than the base station cannot fully resolve the GLONASS ambiguities, so GLONASS does not contribute to the RTK fix. GPS, Galileo and BeiDou are not affected.

Method A: Bluetooth to Phone (Lefebure or SW Maps)

This is the recommended method for field use. Your phone runs the NTRIP client, logs in to RTKdata and forwards the RTCM corrections to the receiver over Bluetooth.

1

Prepare the board

  1. Insert the ArduSimple Bluetooth module into the XBee socket.

  2. Connect your GNSS antenna to the board and place it with a clear sky view.

  3. Power the board via USB or battery. The POWER LED (blue) lights up.

  4. Make the XBee port output NMEA at the baud rate of the Bluetooth module (115200 for the current module, 38400 for the first version):

    • simpleRTK2B (ZED-F9P): u-blox ships UART2 with NMEA output off. In u-center, load ArduSimple's configuration file Rover 1Hz + send NMEA messages to Bluetooth, BLE, or radio plugin for your firmware (1.51 or 1.13) under Tools > Receiver Configuration... (generation u-blox Generation 9, then Transfer file > GNSS) and store it with Receiver > Action > Save Config. The file sets UART2 to 115200. With the first-version Bluetooth module (38400), set UART2 back to 38400 afterwards: in View > Messages View > UBX-CFG-PRT, set the target to UART2, change the baud rate, click Send and save again with Receiver > Action > Save Config.

    • simpleRTK3B Budget, Compass, Fusion (Unicore): NMEA is off by default. In UPrecise, open the Data Stream window and type these commands one by one, each followed by Enter: gngga com2 1, gpgst com2 1, gngsv com2 1, gngsa com2 1, gnrmc com2 1 and gnvtg com2 1, then saveconfig. On the Compass (UM982), do not paste ArduSimple's complete command block: it starts with config signalgroup 2, while ArduSimple gives CONFIG SIGNALGROUP 3 6 for the UM982.

    • simpleRTK3B Pro, Heading (Septentrio): in the web interface, go to Communication > Serial Port, set the Baud rate of COM2 to 115200, press Ok and save the configuration. Then go to NMEA/SBF Out, choose +New NMEA stream > Serial port > COM2, set Interval to 1 sec, select GGA, GSA, GSV, RMC and VTG, press Finish, then Ok and save the configuration.

If the app shows no position from the board, the XBee port is not sending NMEA. On the simpleRTK2B, RTCM3 input on UART2 is on by default, NMEA output is not.

2

Pair Bluetooth on your phone

  1. On your Android phone, go to Settings > Bluetooth and scan for devices.

  2. Pair with RTK_GNSS_*** (default name, PIN 1234). For iOS devices, ArduSimple offers the BT+BLE Bridge instead of this module.

  3. Note the paired device name for the next step.

3

Configure the NTRIP client app

Open Lefebure NTRIP Client or SW Maps and create an NTRIP profile with these settings:

  • Host (domain): rtk.rtkdata.com

  • Host (IP fallback): 13.56.117.10

  • Port: 2101

  • Username / Password: From RTK Credentials in your account dashboard, not your website login

  • Mountpoint (ALL CAPS): AUTO (recommended), or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

  • Host (domain): eu.rtkdata.com

  • Host (IP fallback): 3.73.41.96

  • Port: 2101

  • Username / Password: From RTK Credentials in your account dashboard, not your website login

  • Mountpoint (ALL CAPS): AUTO (recommended), or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

  • Host (domain): aus.rtkdata.com

  • Host (IP fallback): 54.206.56.130

  • Port: 2101

  • Username / Password: From RTK Credentials in your account dashboard, not your website login

  • Mountpoint (ALL CAPS): AUTO (recommended), or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014

  • Send GGA: turn on the option that sends the NMEA GGA position to the caster (see the SW Maps and Lefebure NTRIP Client guides). Without your position the AUTO mountpoint cannot assign a base station: the login succeeds, but no corrections arrive.

  • Receiver connection: Select your paired ArduSimple Bluetooth device.

4

Connect and verify RTK Fix

  1. Tap Connect in the NTRIP client. The app streams RTCM corrections over Bluetooth to the receiver.

  2. Monitor the solution status: 3D Fix > DGPS > Float > Fix.

  3. Once the board achieves RTK Fix, accuracy drops to 1-2 cm.

  4. The NORTK LED on the board turns off when Fix is achieved.

Method B: USB to PC (u-center, UPrecise or web interface)

This method is ideal for bench testing and initial board configuration. The steps below use u-center for the u-blox boards (simpleRTK2B Budget and Fusion). For the simpleRTK3B boards, use UPrecise or the web interface as described after the steps.

1

Connect the board to your PC

  1. Connect the USB port labelled POWER+GPS to your PC. On the simpleRTK2B this is the ZED-F9P's own USB port, and Windows 10 needs no extra driver.

  2. Open u-center and select the correct COM port under Receiver > Connection.

  3. Confirm you see satellite data in the satellite view panel.

2

Enable the u-center NTRIP client

  1. Go to Receiver > NTRIP Client.... The dialog NTRIP client settings opens.

  2. Enter Address, Port, Username and Password for your region, click Update source table and select AUTO under NTRIP mount point:

  • Address: rtk.rtkdata.com

  • Port: 2101

  • Username / Password: Your RTK credentials

  • NTRIP mount point: AUTO, selected from the list after Update source table

  • Address: eu.rtkdata.com

  • Port: 2101

  • Username / Password: Your RTK credentials

  • NTRIP mount point: AUTO, selected from the list after Update source table

  • Address: aus.rtkdata.com

  • Port: 2101

  • Username / Password: Your RTK credentials

  • NTRIP mount point: AUTO, selected from the list after Update source table

  1. Leave Use manual position unchecked. u-center then takes the position from the receiver and sends it to the caster. Wait for a 3D fix before you continue.

  2. Click OK to connect.

If no position reaches the caster, the login succeeds but no corrections arrive (0 kB/s) and Fix Mode stays at 3D. Wait for a 3D fix and select AUTO from the updated source table.

3

Verify RTK Fix in u-center

  1. Open View > Docking Windows > Data. The Fix Mode field shows the current solution.

  2. Watch the progression: 3D > DGNSS > FLOAT > FIXED.

  3. At FIXED, 2D Acc. and 3D Acc. drop to the centimeter level, and the NTRIP client icon at the bottom of u-center is green.

  4. The u-center map view will show your position converging to a stable point.

Unicore boards in UPrecise (simpleRTK3B Budget, Compass, Fusion)

  1. Install UPrecise (Windows 7/8/10, 64-bit according to ArduSimple). It starts in Chinese; ArduSimple's guide shows how to switch it to English.

  2. Connect the POWER+GPS port, select the COM port, choose 115200 or AUTO as baud rate and press Connect.

  3. NMEA output is off by default. Open Receiver Configuration, enable GGA (ArduSimple recommends GGA, GSA, GSV, GST and RMC) for the port UPrecise is connected to and press Enter. Then type saveconfig in the Data Stream window and press Enter; the reply is Command, SAVECONFIG, response: OK.

  4. Click the toolbox icon and select RTCM. In the RTCM Monitor, click Input, choose Ntrip Client and fill in Ntrip Caster Host (the host for your region), Port 2101, Mount point AUTO, User ID and Password from RTK Credentials.

  5. Tick GGA Location reporting, enter 1, select CurrentSerialGGA and click OK. RTKdata needs this setting: without GGA the AUTO mountpoint sends nothing.

  6. Click OutPut, select Serial Port and the COM port of your receiver.

  7. Click Connect in the RTCM Monitor. Input and OutPut turn green, and with Hex ticked you see the incoming RTCM data. The Fix Type changes to RTK Float, then RTK Fixed.

Septentrio boards in the web interface (simpleRTK3B Pro, Heading)

  1. Connect the POWER+GPS port. The first time, the PC shows only a new drive: install the Septentrio driver from it, then reconnect the board.

  2. Open http://192.168.3.1 and log in with the factory user given in ArduSimple's Septentrio configuration guide.

  3. Give the receiver internet access: share your PC's connection over USB (ArduSimple shows this in a video; the receiver's IP address changes after a restart) or use the Shield for Septentrio Native Ethernet: move the switch on the board towards 5V = OUTPUT, plug in the shield, connect it to your Ethernet hub with an RJ45 cable, then go to Communication > Ethernet, set Ethernet Interface Mode Power on, select DHCP and press Ok.

  4. Check that the receiver runs as a rover: GNSS > Position, Mode Rover with all position modes checked, Ok, save.

  5. Go to Corrections > NTRIP > +New NTRIP client. Set Mode to Client and fill in Caster (the host for your region), Port 2101, User name, Password and Mount point AUTO.

  6. Set Send GGA to caster to auto and click Ok.

  7. Save the configuration in the pop-up at the lower right of the browser, otherwise it is lost after a power cycle.

  8. RTCM starts to arrive, and the position mode changes to RTK Float, then RTK Fixed.

Method C: WiFi NTRIP Master (no phone or PC)

The ArduSimple WiFi NTRIP Master is an XBee plugin with an ESP32 that runs its own NTRIP client (open-source firmware ESP32-XBee). It joins a 2.4 GHz WiFi network, logs in to RTKdata, writes the corrections to the receiver through the XBee socket and sends the latest GGA position it reads from the receiver to the caster. Use it when the board works without a phone or PC, for example on a robot or mower.

Make the receiver output GGA on the XBee socket

  • simpleRTK2B (ZED-F9P): in u-center, load ArduSimple's configuration file Rover 1Hz + send GGA messages to 4G NTRIP plugin for your firmware (1.51 or 1.13) under Tools > Receiver Configuration... and store it with Receiver > Action > Save Config. It sets UART2 to 115200 and turns on GGA output. The version for firmware 1.13 also switches BeiDou off.

  • simpleRTK3B Budget, Compass, Fusion (Unicore): in the UPrecise Data Stream window, type gngga com2 1 and then saveconfig, each followed by Enter.

  • simpleRTK3B Pro, Heading (Septentrio): set COM2 to 115200 as in Method A. Then add an NMEA stream on COM2 with GGA at 1 sec as in Method A, or load ArduSimple's configuration file Send 1Hz GGA to Plugin: in the main menu Admin, under Receiver Configurations, press the upload arrow of Current configuration, select the file, press Proceed and then OK. Save the configuration in the pop-up at the lower right of the browser.

Open the configuration page

  1. Plug the WiFi NTRIP Master into the XBee socket in the right orientation and power the board.

  2. With a phone or laptop, join the WiFi network ESP_XBee_xxxxxx (the last characters are unique to your device) and open http://192.168.4.1/. The page ESP32 XBee Config shows the firmware version next to its title.

  3. This network has no internet. If the page does not load, keep the phone or laptop connected to it (turn off mobile data), or try another browser or a private window.

Connect the NTRIP Master to WiFi

  1. In the WiFi card, type the SSID and Password of a 2.4 GHz network with internet access. A phone hotspot works. Type both by hand instead of using Scan or a saved password.

  2. Leave IP config on DHCP.

  3. Use WPA2 on the router or hotspot: the firmware has no WPA3 support, and networks that ask for a username and password (WPA2 Enterprise) do not work. On an iPhone 12 or later, turn on Maximize Compatibility under Settings > Personal Hotspot.

  4. Keep the board close to the WiFi access point, because the WiFi antenna is on the plugin. ArduSimple offers a variant with a uFL connector for an external antenna on request.

The UART (main communication) card is set to UART 0 and 115200 baud from the factory, which matches the receiver settings above. Leave it unchanged: UART controller refers to the ESP32, not to UART2 of the receiver.

Enter the RTKdata settings

  1. Switch on NTRIP client.

  2. Host and port: the host for your region in the left field, without http:// and without :2101, and 2101 in the right field: rtk.rtkdata.com (North America, IP fallback 13.56.117.10), eu.rtkdata.com (Europe, 3.73.41.96) or aus.rtkdata.com (Australia, 54.206.56.130).

  3. Mountpoint: AUTO (or AUTO_WGS84, AUTO_ITRF2020, AUTO_ITRF2014).

  4. Username and Password: from RTK Credentials, not your website login.

  5. Leave NTRIP server, NTRIP caster and the socket functions off. The firmware documentation advises against enabling all protocols at once.

  6. Optional: under WiFi hotspot, set Security to WPA/2-PSK (recommended) with a password of at least 8 characters. The hotspot is open by default. A shorter password stops the hotspot from starting. If holding BOOT on the NTRIP Master for more than 5 seconds does not bring it back, use ERASE in the ESP32 DownloadTool and flash the firmware again as in ArduSimple's firmware update guide.

  7. Click the submit button above the NTRIP client card (labelled Submit in an English browser). The device restarts and shows Waiting for restart....

Check the connection

  1. Next to NTRIP client, the counter shows bytes in (corrections) and out (GGA). In rises continuously, out rises by one GGA sentence every 15 seconds.

  2. http://192.168.4.1/log.html shows Successfully connected to followed by your host, 2101 and AUTO.

  3. Once the caster accepts the login, the LED fades in and out in the colour set next to NTRIP client. A blinking LED or no LED in that colour means it is still trying.

  4. On the board, NORTK turns off at RTK Fix.

Firmware v0.5.4 sends only the GGA sentence to the caster. Older versions (v0.5.2, v0.5.3) forward everything the receiver sends on the XBee port, so keep that output short as in the receiver step above. If you update the NTRIP Master with ArduSimple's firmware update guide, it has you switch off the receiver's UART outputs first: switch GGA output back on afterwards.

Vertical reference (heights)

Heights from RTKdata.com are ellipsoidal, not orthometric (mean sea level). Apply a geoid model in your GIS or surveying software if MSL heights are required.

Troubleshooting

Problem
Cause
Fix

Connected, but no corrections: the XBEE>GPS LED does not blink and NORTK stays on

GGA does not reach the caster: the GGA option is off in the app or tool, or the XBee port outputs no NMEA

Turn on GGA in the app, and set up the XBee port output (Method A step 1, Method C first step)

Wrong COM port in u-center

Multiple USB devices connected

Open Device Manager and confirm which COM port is assigned to the u-blox or FTDI device.

UART2 not receiving corrections

RTCM3 input switched off on UART2 (on by default)

In u-center, check UBX-CFG-PRT > UART2: Protocol In must include RTCM3

Mountpoint error

Typed in lowercase

Enter AUTO in ALL CAPS, or select AUTO from the source table.

Bluetooth pairs but no data flows

Baud rate mismatch, or UART2 sends no NMEA

Match UART2 to the Bluetooth module (115200 for the current module, 38400 for the first version) and turn on NMEA output (Method A step 1).

Slow convergence or no Fix after a firmware update

Firmware and configuration file do not match

Keep the firmware your board shipped with. If you update, load the ArduSimple configuration file for the new firmware (1.51 or 1.13) and save it.

Septentrio: corrections arrive but no Float or Fix

Receiver not configured as a rover

GNSS > Position, Mode Rover with all position modes checked, Ok, save

UPrecise: Input and OutPut set, but no data

Connect not clicked, or GGA output off on the connected port

Click Connect in the RTCM Monitor; enable GGA under Receiver Configuration

NTRIP Master log: Could not connect to host

Host typed with http:// or :2101, no internet on the WiFi network, or outbound TCP port 2101 blocked

Enter only the host name, check internet access, allow port 2101 or use the IP fallback

NTRIP Master log: Could not connect to mountpoint: Mountpoint not found

Username or password empty

Enter your RTK credentials

NTRIP Master log: Could not connect to mountpoint: HTTP/1.1 401 Unauthorized

Wrong username or password

Re-type the RTK credentials by hand

NTRIP Master: nothing happens for minutes after you correct the settings, or after a coverage gap

After repeated failed attempts the client waits longer before it tries again, up to one hour

Click submit (the device restarts), press XBEE RESET on the board or power-cycle it

NTRIP Master hotspot disappeared after setting a hotspot password

Password shorter than 8 characters

Hold BOOT on the NTRIP Master for more than 5 seconds. If the hotspot does not return, use ERASE in the ESP32 DownloadTool, flash the firmware again (ArduSimple firmware update guide) and then use at least 8 characters

Configuration page does not load or reports that header fields are too long

Browser issue

Use another browser or a private window, or close and reopen the tab

Two devices keep disconnecting each other

The same credentials run on the NTRIP Master and on a phone app or PC tool at the same time

Use one client per data stream, see Account & Credentials

Login fails although the credentials are correct

The tool does not accept a character of your password

Contact support@rtkdata.com

Tips and tricks

  • Keep the factory firmware unless you need a feature. ArduSimple recommends not changing the configuration or firmware of a new board. If you update, choose 1.13 (up to 10 Hz) or 1.51 (up to 8 Hz) and load the matching ArduSimple configuration file.

  • Method A is best for fieldwork, Method B for configuration and bench testing, and Method C for machines that run without a phone or PC.

  • Match UART2 to the plugin. ArduSimple's configuration files set 115200, which fits the current Bluetooth module and the WiFi NTRIP Master.

  • The simpleRTK2B Fusion (ZED-F9R) adds dead reckoning via its built-in IMU; the u-center NTRIP client steps of Method B apply to it as well. ArduSimple's configuration files in this guide start from a default ZED-F9P configuration, and ArduSimple notes that sensor fusion configuration might not be plug and play. The simpleRTK3B Fusion uses a Unicore UM981 with INS and is set up in UPrecise like the other Unicore boards.

  • The RTK Calibrated Surveyor Kit is pre-configured to send NMEA over Bluetooth/BLE and USB at 1 Hz. Skip the UART2 configuration step.

  • Log raw data for PPK post-processing as a fallback when NTRIP connectivity is intermittent. The simpleRTK3B Pro and Heading have a built-in microSD datalogger.

Related Guides

  • u-center (u-blox F9): the full NTRIP client configuration for the ZED-F9P used in Method B

  • Lefebure NTRIP Client: the Android app from Method A, with its GGA and Bluetooth output settings explained

  • SW Maps: the free Android alternative to Lefebure that also records points while streaming corrections

  • SparkFun RTK Facet: another ZED-F9P receiver with a very similar NTRIP workflow

  • NTRIP & GGA Essentials: why the AUTO mountpoint needs your GGA position before corrections start

Related Industry Solutions

PreviousLeica GS11 I / GS11 T
NextBad Elf Flex

Last updated

Was this helpful?