Unicore UM980 / UM982
These steps connect an Unicore UM980 / UM982 to the Premium Positioning correction network over NTRIP, using SW Maps (Bluetooth) or UPrecise / host. 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 on the customer portal.
SW Maps (Bluetooth) or UPrecise / host.
A working internet connection on the controller or phone.
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
What you'll need: Your UM980/UM982 board powered and tracking satellites, reachable over Bluetooth or USB/serial. A way to feed corrections: Android + SW Maps over Bluetooth (common field path), a PC running Unicore UPrecise over the board's serial/COM port, or your own host microcontroller. Plus the NTRIP username and password from your Premium Positioning welcome email - enter your own.
How RTK works on this board: The UM980/UM982 is an OEM engine - it doesn't connect to the internet itself. A client (SW Maps, UPrecise, or your host) logs in to the caster, pulls the RTCM stream, and pushes those bytes into the board's serial input. The board auto-detects the RTCM type, so you don't specify a format.
Decide your path: Path A - SW Maps on Android over Bluetooth (handheld/field). Path B - UPrecise on a PC over USB/serial (bench/config). Path C - your own host forwarding NTRIP/RTCM to the board UART. Steps 4 - 7 cover SW Maps; steps 8 - 9 cover UPrecise. Labels vary by app/firmware - match by function.
Path A - connect the board in SW Maps: Pair the UM980/UM982 in Android Bluetooth first. In SW Maps tap the Bluetooth/GNSS icon (or Menu > Bluetooth GNSS), Scan, and select your receiver. Set Instrument Model (or a generic RTK option) and your antenna/pole height. Confirm live position and satellites before adding corrections.
Path A - open the NTRIP Client: In SW Maps open the NTRIP Client (menu or corrections settings) and add a new profile (+ / Add New Profile).
Path A - enter the caster settings: Caster Host / Address: rtkpremium.xyz; Port: 2101; Mountpoint: COMMON; Protocol: NTRIP. For Username/Password enter YOUR OWN from your welcome email. Enable 'Send NMEA GGA to NTRIP Caster'. Save the profile.
Path A - start corrections: Connect/start the profile. SW Maps logs in to rtkpremium.xyz:2101 on COMMON and relays RTCM to the board over Bluetooth. A data/bytes indicator shows corrections flowing. Skip to the final verification step.
Path B - connect the board in UPrecise: Install UPrecise, connect the board by USB/serial, open the port dialog, select the COM port and baud, and connect. Confirm live position and Fix Type readouts before adding corrections.
Path B - configure the NTRIP Client: In UPrecise click the toolbox icon > RTCM > Input > Ntrip Client. Enter Host rtkpremium.xyz, Port 2101, Mount point COMMON, Protocol NTRIP, and YOUR ID/Password. If prompted, set GGA Location reporting to 1 (CurrentSerialGGA). Click Ok, then Output > Serial Port > your receiver's COM port. The Input/Output indicators turn green when RTCM flows.
Path C - host microcontroller: If integrating directly, run an NTRIP client on your host (ESP32, Raspberry Pi, etc.) connecting to rtkpremium.xyz:2101, mountpoint COMMON, NTRIP, with your username/password. Forward every received RTCM byte unmodified into the board's UART RX. Optionally send periodic NMEA GGA back. The board auto-detects the RTCM.
Give it sky view and a moment to converge: Antenna must have a clear, open view of the sky. With valid RTCM arriving, the solution moves Single → RTK Float → RTK Fixed within a few minutes.
Confirm RTK Fixed: In UPrecise watch the Fix Type field; in SW Maps watch the fix-quality indicator. It should reach RTK Fixed (cm-level). If it stalls at Float or stays Single, recheck the caster Host/Port/Mountpoint, your credentials, that RTCM is actually reaching the board's input, and improve sky view.
If the fix will not hold
The UM980/UM982 never connects to the internet itself - a client (SW Maps, UPrecise, or your host) pulls the NTRIP/RTCM stream and feeds it into the board's serial input. Field labels differ slightly (Caster Host vs Address, Mount point vs Mountpoint, ID vs User) - match by function.
For more, see RTK corrections troubleshooting and Fix inconsistent RTK accuracy on site.
Need help
Support is available 24/7. Include your receiver model, the mountpoint, the solution status, and the correction age when you get in touch.
Last updated
Was this helpful?