Support
No RTK FIX? Troubleshooting NTRIP connections
No RTK FIX or can’t connect? The most common symptoms (401, timeout, stuck in FLOAT, no GGA) and what to check, in order – with a fix for each one.
6 min read
| Symptom | Likely cause | Solution |
|---|---|---|
| Error 401 / Unauthorized | Wrong username or password, or the subscription has expired | Check your credentials (case-sensitive); check the status and expiry date in the panel. |
| Cannot connect / timeout | No internet, wrong host or port | Host rtk.ba (without http://), port 2101; check the mobile signal and the modem's APN. |
| Empty mountpoint list | The device is not downloading the sourcetable | Enter the AUTO mountpoint manually. |
| Connected to AUTO, but stays FLOAT or gets a random base and the connection drops after ~2 min | The receiver is not sending GGA | Enable "Send GGA" / "NMEA upload"; wait until the receiver has an autonomous position. |
| Stuck in FLOAT | Obstructed sky, multipath, far from the base, outdated RTCM format | Move to open sky; check that the receiver supports RTCM 3 MSM; check the distance to the base station on the map. |
| FIX keeps dropping in and out | Mobile internet dropouts (age of corrections increases) | External antenna for the modem, a different operator or a roaming SIM. |
| Position "shifted" relative to old lines | Different correction source / coordinate system | Use the same source as when the lines were recorded, or record them again. |
If none of the above helps, open a ticket in the panel or write to us at info@rtk.ba – on our side we can see your connection, base station and data flow, so we can pinpoint the problem quickly.
Related: Also double-check the basic settings in connecting via NTRIP, the distance to the base on the coverage map and the factors in RTK accuracy.