> For the complete documentation index, see [llms.txt](https://docs.premium-positioning.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premium-positioning.com/guides/oem-boards-and-integration/ardusimple-simplertk2b-u-blox-zed-f9p.md). # ArduSimple simpleRTK2B (u-blox ZED-F9P) Connect an ArduSimple simpleRTK2B (u-blox ZED-F9P) to RTK Premium corrections over NTRIP using SW Maps, Lefebure or u-center: caster settings and the steps to a fixed solution. These steps connect an ArduSimple simpleRTK2B (u-blox ZED-F9P) to the Premium Positioning correction network over NTRIP, using SW Maps or Lefebure NTRIP Client (Android), or u-center (PC). They assume you already have your NTRIP credentials. ### Before you start * Your NTRIP username and password, from your Premium Positioning welcome email or your account in the XYZ Platform. * No account yet? Start a [14-day free trial](https://www.premium-positioning.com/start-14-day-free-trial?utm_source=docs\&utm_medium=referral\&utm_campaign=docs\&utm_content=ardusimple-simplertk2b-u-blox-zed-f9p) to get your credentials. * SW Maps or Lefebure NTRIP Client (Android), or u-center (PC). * A working internet connection on the controller or phone. * No phone or hotspot in the field? If your controller or receiver takes a SIM, Premium Positioning [IoT SIMs](https://www.premium-positioning.com/products?utm_source=docs\&utm_medium=referral\&utm_campaign=docs\&utm_content=ardusimple-simplertk2b-u-blox-zed-f9p#iot-sims) give it its own data connection. * A clear view of the sky at the point you are measuring. ### Network settings These are the same for every Premium Positioning customer. Only your username and password are unique to you. * Server or host: rtkpremium.xyz * Port: 2101 * Mountpoint: COMMON * Protocol: NTRIP ### Steps 1. Power the receiver: Power your simpleRTK2B / ZED-F9P board over USB from a power bank or adapter. Connect the GNSS antenna and place it outdoors with a clear, open view of the sky - RTK won't fix indoors or under heavy tree cover. 2. Pair over Bluetooth: On Android open Settings > Bluetooth and pair with the receiver. On ArduSimple Bluetooth/BLE bridges the device first appears as a MAC address then renames to e.g. 'BT+BLE\_Bridge\_XXXX' (older firmware: 'RTK\_GNSS\_\*\*\*' or 'simpleRTK2B'). Default PIN, if asked, is 1234. The exact name depends on firmware. 3. Install and open SW Maps: Install 'SW Maps' (free) from Google Play and open it. Grant Location and nearby-devices/Bluetooth permissions - without them it can't connect or compute a position. (Lefebure NTRIP Client and u-center on a PC are valid alternatives; this guide follows SW Maps.) 4. Connect SW Maps to the receiver: Open the connection screen - the antenna/Bluetooth icon in the toolbar, or the side Menu > 'Bluetooth GNSS'. Choose the mode (classic Bluetooth, or 'Bluetooth LE' for the ArduSimple BLE bridge) and select your paired receiver. Wording varies by version. 5. Set the instrument model and height: Set 'Instrument Model' to a u-blox / generic RTK option (e.g. 'Generic NMEA' or 'u-blox') if your board isn't listed. Enter 'Instrument Height' (pole/tripod to the antenna). Tap 'Connect' - you should see a live position and satellite count. 6. Open the NTRIP Client settings: Open the SW Maps Menu and tap 'NTRIP Client'. Tap 'Add New Profile' (or '+') and name it (e.g. 'Premium Positioning'). 7. Enter the caster address and port: Address / Host = rtkpremium.xyz, Port = 2101, Protocol = NTRIP. These are the same for every customer. 8. Enter YOUR NTRIP credentials: Enter the Username and Password from YOUR welcome email - unique to your account; don't use anyone else's. If you can't find them, contact support first. 9. Select the mountpoint: For Mountpoint, enter or select COMMON (type it in capitals if it's a free-text field; otherwise tap the source-table/list button and pick COMMON). 10. Enable Send NMEA GGA: Turn ON 'Send NMEA GGA to NTRIP Caster' - this sends your approximate position so the network returns corrections for your area; without it the receiver can stall on Float. 11. Connect to the caster: Tap 'Connect' in the NTRIP Client screen. The NTRIP icon shows active (no red X) and correction data starts flowing - fed over Bluetooth into the ZED-F9P automatically; you don't configure anything on the board. 12. Watch the solution status climb: Watch the fix indicator: Autonomous (single) → DGPS → RTK Float → RTK Fixed, typically 10 - 60 s outdoors with \~10+ satellites. 'Age of corrections' should stay under \~5 s. 13. Confirm RTK Fixed: Done when the solution reads 'RTK Fix' / 'FIX' (not Float/Autonomous) and horizontal accuracy drops to \~0.01 - 0.02 m. If it stays Float, confirm 'Send NMEA GGA' is ON, credentials and COMMON are correct, and the antenna has clear sky. ### If the fix will not hold The simpleRTK2B receives corrections through the ZED-F9P's serial/USB input; SW Maps forwards the NTRIP stream over Bluetooth automatically, so no settings change on the board. Caster host/port/mountpoint are common to all customers; only your username/password are personal. SW Maps labels vary by version and by Bluetooth vs BLE bridge - match by meaning. Lefebure NTRIP Client and u-center work the same way with the same caster details. For more, see [RTK corrections troubleshooting](/troubleshooting/rtk-corrections-troubleshooting.md) and [Inconsistent RTK accuracy on site](/troubleshooting/inconsistent-rtk-accuracy-on-site.md). ### FAQ Do I need to configure the ZED-F9P board to receive corrections? You do not. SW Maps forwards the NTRIP stream over Bluetooth into the board's input automatically, so no setting changes on the board. Which apps work with the simpleRTK2B? SW Maps and Lefebure NTRIP Client work on Android, and u-center works on a PC. All three use the same caster details. What are the NTRIP settings for a simpleRTK2B on RTK Premium? Use host rtkpremium.xyz, port 2101, mountpoint COMMON and protocol NTRIP, with the username and password from your welcome email. Why does my simpleRTK2B stay on RTK Float? Most often Send NMEA GGA is off. Check that it is on, that the credentials and the COMMON mountpoint are correct, and that the antenna has a clear view of the sky. How long does an RTK fix take? A fix typically takes 10 to 60 seconds outdoors with 10 or more satellites in view. ### Need help Support runs on business days from 09:00 CET to 17:00 ET. Contact us at or +31 85 0606 338, and include your receiver model, the mountpoint, the solution status, and the correction age. Last updated: 10 October 2026