SkyTraq PX1122R / NavSpark
These steps connect a SkyTraq PX1122R / NavSpark to the Premium Positioning correction network over NTRIP, using GNSS Viewer (PC) or SW Maps (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.
GNSS Viewer (PC) or SW Maps (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
Before you start: what you need: A SkyTraq PX1122R / NavSpark RTK module (typically on a PX1122R-EVB or your own carrier) with an ACTIVE multi-band antenna on RF_IN, placed with a clear, open view of the sky (the PX1122R needs an active antenna with 3.3V bias). Plus either a Windows PC running SkyTraq's GNSS Viewer (USB) or an Android phone running SW Maps over Bluetooth/serial. Have your NTRIP username and password from your welcome email ready.
Confirm the module is in rover mode: The PX1122R works as an RTK rover out of the box: it accepts RTCM 3.x from a network base/VRS and computes a cm-level position. If it was previously set up as a base, switch it back to rover (normal) mode in GNSS Viewer first. Wording varies by GNSS Viewer version - look for the RTK / mode setting.
Connect the module and confirm it's alive: PC: connect by USB, open GNSS Viewer, select the module's COM port, set baud 115200 (8-N-1) and connect. Android: power the module, pair it over Bluetooth (SPP/serial), then select it inside SW Maps later. Either way you should see live NMEA (GGA, GSV) and tracked satellites once the antenna has sky view.
Get a basic (autonomous) position fix first: With the antenna outdoors and open to the sky, wait until the module reports a normal 3D fix (GGA quality 1, or 2 for DGPS) tracking plenty of satellites. RTK won't engage until there's a stable standalone fix, so don't skip this - allow up to a minute on a cold start.
Choose how corrections reach the module: The module needs an RTCM3 stream piped into its serial (UART) input at 115200 baud. Two common ways: (A) GNSS Viewer's built-in NTRIP client on the PC pulls corrections and sends them down the USB/serial link; or (B) SW Maps on your phone acts as the NTRIP client, pulls corrections over mobile data, and relays them over the Bluetooth/serial bridge. If you instead feed the input from a separate radio/modem, the same caster values apply.
Option A - GNSS Viewer NTRIP client (PC): Recent GNSS Viewer versions (~2.1.050+) include an internal NTRIP client for single-UART operation. Open the NTRIP client window/dialog (label varies by version - look for 'NTRIP'). If your build has no NTRIP option, use the SW Maps path, or feed corrections from a third-party NTRIP client into the module's serial port.
Option B - SW Maps Bluetooth GNSS + NTRIP client (Android): In SW Maps, open the menu and choose Bluetooth GNSS (connect instrument). Select your paired PX1122R / NavSpark and set the instrument/antenna model so SW Maps reads its NMEA. Once connected and showing a position, open the NTRIP / corrections setting (commonly under the same Bluetooth GNSS menu) and enable the NTRIP client. Labels differ slightly between SW Maps versions.
Enter the Premium Positioning caster details: In whichever NTRIP client you use, enter EXACTLY: Host/Server rtkpremium.xyz, Port 2101, Mountpoint COMMON, Protocol NTRIP - the same for every customer.
Enter YOUR OWN NTRIP username and password: Type the NTRIP username and password from your welcome email - unique to you; do not use anyone else's. An authentication error here almost always means a mistyped username/password or mountpoint.
Connect to the caster and send your position (NMEA GGA): Start/connect the NTRIP client. NTRIP casters require the client to send your approximate position as an NMEA GGA so the network supplies the right corrections - GNSS Viewer and SW Maps do this automatically once the module has a position. If the mountpoint list loads and the connection shows incoming bytes, corrections are flowing.
Confirm RTCM corrections are reaching the module: Watch the data counters: the NTRIP client should show received bytes climbing, and the module should be receiving RTCM3 on its serial input (decodes standard RTCM 3.x MSM plus base messages like 1005/1006). If bytes arrive at the client but the module never moves toward RTK, check that corrections are actually wired/relayed into the module's input at 115200 baud, and that you have clear sky.
Verify RTK Fixed (NMEA GGA quality 4): The solution should climb 3D/DGPS → RTK Float → RTK Fixed. You're set up correctly when the NMEA GGA fix-quality field (6th field in $GxGGA) reads 4 = RTK Fixed (5 = RTK Float, not fully converged) - cm-level horizontal accuracy. If it sits on 5/Float, improve sky view, keep the antenna still, and confirm the correction stream is uninterrupted.
If the fix will not hold
The PX1122R needs three things at once: an active multi-band antenna with open sky, the module in rover mode, and a live RTCM3 stream into its serial input at 115200 8-N-1. GNSS Viewer is the easiest PC verification tool (newer versions can act as the NTRIP client); SW Maps is the simplest field option over Bluetooth. Labels differ between GNSS Viewer and SW Maps versions - match the closest. Success = NMEA GGA quality 4 (RTK Fixed).
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?