> 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/troubleshooting/rtk-corrections-troubleshooting.md). # RTK corrections troubleshooting Most RTK problems fall into a handful of patterns: the receiver will not connect, it connects but will not reach a fixed solution, or the fix keeps dropping. This page works through each symptom and what to check, from the most common cause down. Work top to bottom within each section. The first cause listed is the one to rule out first. ### The receiver will not connect to the caster * Check the address and port. They must read rtkpremium.xyz and 2101 exactly, with no stray spaces. * Check the internet connection. The receiver needs working data, whether through its own SIM, a paired phone or controller, or Wi-Fi or Ethernet. Confirm the link is up before looking further. * Check the mountpoint. If the source table loads but you see no fix, make sure a mountpoint is selected. COMMON suits most receivers. ### Authentication failed * Re-enter the username and password. They are case sensitive, so mind the capitals. Type them by hand rather than pasting if a paste might add a space. * Use the credentials from your account email, not an example or an old set. * Confirm the subscription is active. An expired trial or lapsed subscription will be refused at sign-in. If in doubt, contact support. ### Connected but stuck on float, no fix A float solution means the receiver is receiving corrections but has not yet resolved the integer ambiguities that give centimetre accuracy. * Check position sending. For a network mountpoint, the GGA heartbeat must be on, or the network cannot generate a correction matched to your location. See [Mountpoint selection and the GGA heartbeat](https://claude.ai/chat/b419af49-7d48-49a1-832b-42d52fe66419#). * Move to open sky. Buildings, trees, and vehicles block and reflect signals. Step into the clear and give the receiver a minute. * Check the correction age. It should stay within a few seconds. A climbing age points to a dropping data link. * Give it time. On a fresh connection the receiver needs a short while to converge. If it will not fix after several minutes in open sky, disconnect and reconnect. ### The fix keeps dropping out * Watch for obstructions. Passing a building, a tree line, or under cover will drop the fix to float until the receiver re-initialises. Plan routes through open ground where you can. * Maintain lock. Keep the antenna as upright and as still as the job allows while moving between points. * Re-initialise cleanly. After a drop, return to open sky, let the receiver re-fix, and re-measure the last good point to confirm the new fix agrees before trusting it. * Check the geometry. A poor satellite spread weakens the solution. If your receiver reports a high DOP, wait a few minutes for the constellation to change. ### The accuracy looks wrong or inconsistent If the receiver reports a fix but positions do not match where they should be, the cause is usually setup rather than the correction stream. The dedicated guide [Fix inconsistent RTK accuracy on site](https://claude.ai/chat/b419af49-7d48-49a1-832b-42d52fe66419#) works through antenna height, the wrong point being measured, datum mismatches, and similar. As a first pass: * Confirm the antenna height is entered correctly and measured to the right reference. * Confirm the receiver and your software are working in the same coordinate system. * Re-measure a known point and compare against its published coordinates. ### When to contact support Support is available 24/7. If you have worked through the relevant section above and the problem holds, get in touch and include your receiver make and model, the mountpoint you are using, the solution status the receiver reports, and the correction age. Those four details let support reach the cause quickly. ### FAQ My receiver connects but stays on float. Why? It is receiving corrections but has not fixed the ambiguities. Most often the GGA heartbeat is off, the sky view is blocked, or it simply needs more time in the open. What correction age is normal? A few seconds. A rising age usually means the data link is struggling. The fix drops every time I pass a building. Is that a fault? No. Obstructions break the satellite lock. Return to open sky to re-initialise, then re-check your last point. I get a fix but the coordinates are off. What now? Check antenna height and your coordinate system first, then see [inconsistent RTK accuracy on site](/troubleshooting/inconsistent-rtk-accuracy-on-site.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.premium-positioning.com/troubleshooting/rtk-corrections-troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.