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

Quectel LG69T / LC29H

These steps connect a Quectel LG69T / LC29H to the Premium Positioning correction network over NTRIP, using Host app / SW Maps (via a Bluetooth/serial bridge). 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.

  • Host app / SW Maps (via a Bluetooth/serial bridge).

  • 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

  1. Confirm you have an RTK-capable variant: Corrections only work on Quectel modules with an RTK engine: LG69T (AM)/(AS), and LC29H variants such as LC29HD/HE/DA (NOT the basic LC29HA, which can't accept corrections). If a serial console prints "This version is not licensed, please contact FAE", the RTK feature needs activating with Quectel first. The module does the RTK maths internally - you just deliver our RTCM3 stream to its serial input.

  2. Wire up / power the module and note the UART: On an evaluation board (EVK) just connect USB. On a bare module, connect the main UART (commonly UART1) to your host PC/microcontroller or a Bluetooth bridge. Default serial is 115200 baud, 8N1. TX/RX cross over (module TX → adapter RX). Exact pin/port names vary by module/breakout - check the datasheet.

  3. Verify the module is outputting position first: Open a serial terminal or Quectel's QGNSS tool at 115200. You should see NMEA ($GxGGA, $GxRMC). Confirm an autonomous fix outdoors before adding corrections.

  4. (Optional) Confirm rover mode and message rates: The module is a rover by default. To be explicit, RTK-capable LC29H firmware accepts proprietary commands like $PQTMCFGRCVRMODE (rover vs base) and $PQTM/$PAIR rate commands, saved with $PQTMSAVEPAR. Exact command names differ by firmware/variant - follow the command list in YOUR module's application note.

  5. Choose how you'll deliver corrections: Path A - Android + SW Maps over a Bluetooth-Classic-to-serial bridge (HC-05/06/JDY-31 wired to the module UART). Path B - a host PC/microcontroller running an NTRIP client (QGNSS, STRSVR, Lefebure, or your own ESP32/Pi code) writing raw RTCM3 to the UART RX.

  6. PATH A - Pair the Bluetooth bridge: Use a genuine Bluetooth Classic (SPP) bridge, not BLE-only. Set the bridge baud to match the module (115200). Pair the phone to the bridge in Android Bluetooth settings (PIN often 1234 or 0000).

  7. PATH A - Connect the module in SW Maps: SW Maps menu > 'Bluetooth GNSS' > 'Connect Instrument'. Select your bridge device and a generic NMEA instrument model. Confirm live position and satellite count before adding corrections.

  8. PATH A - Configure the SW Maps NTRIP client: In SW Maps NTRIP Client / Caster settings enter Host/Address rtkpremium.xyz, Port 2101, Mountpoint COMMON, Protocol NTRIP. Enter YOUR OWN username/password from your welcome email.

  9. PATH A - Start corrections: Tap Connect. SW Maps connects to the caster, sends your phone's GGA to request COMMON, then forwards the returned RTCM3 over Bluetooth into the module UART. The correction/data-received indicator becomes active.

  10. PATH B - Configure your NTRIP client: In QGNSS use Tools > NTRIP; in STRSVR/Lefebure/your own code set the same values: Host rtkpremium.xyz, Port 2101, Mountpoint COMMON, NTRIP, plus YOUR username/password. The client must send periodic NMEA GGA upstream.

  11. PATH B - Pipe RTCM3 into the module UART: Route the raw RTCM3 bytes straight to the module's serial input (RX). In QGNSS the built-in NTRIP client does this; with STRSVR set input = NTRIP client, output = the module's serial COM port at 115200 8N1; on an ESP32/Pi write the bytes to the UART. Don't re-frame the bytes - standard RTCM3 is expected.

  12. Watch the fix converge: Float then Fixed: With corrections flowing, the internal RTK engine uses them automatically. The NMEA GGA quality field moves from 1 (autonomous) to 5 (RTK Float) to 4 (RTK Fixed). Convergence outdoors with a good antenna takes seconds to a couple of minutes.

  13. Confirm RTK Fixed: You have a valid RTK solution when GGA quality reads 4 (RTK Fixed) - SW Maps shows a Fix/RTK Fixed status and cm-level position. If you only reach Float (5) or stay at 1, recheck: caster values and YOUR credentials, RTCM3 reaching the UART RX, matching baud rates, an RTK-capable/licensed variant, and a clear sky view.

If the fix will not hold

The Quectel module computes RTK on-board - your job is to deliver standard RTCM3 to its serial input; SW Maps (over a Bluetooth-Classic serial bridge) or any NTRIP client on a PC/MCU both work. RTK only works on correction-capable variants (LG69T-AM/AS, LC29HD/HE/DA), not the basic LC29HA. Default serial is 115200 8N1. Proprietary $PAIR/$PQTM command names and UART pins differ by variant/firmware - check the specific Quectel application note. RTK Fixed = NMEA GGA quality 4 (RTK Float = 5).

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.

PreviousQField
NextRaven RS1 / Viper 4+

Last updated

Was this helpful?