RTK Troubleshooting Manual | 7 Items to Check First

Table of Contents

• RTK troubleshooting should begin by isolating "what is happening"

• First, isolate the symptoms

• Check the basic condition of the power supply, battery, and equipment

• Check the connection status

• Check the reception status of correction information

• Check the satellite reception environment

• Verify the coordinate system and positioning settings.

• Verify consistency with known points, reference points, and field procedures.

• Operational approach to reducing incidents

• RTK troubleshooting should start by isolating "what is happening"

RTK is a useful technology that, when used properly, can efficiently carry out centimeter-level positioning, surveying, construction management, and as-built verification. On the other hand, it is also true that on-site problems such as "accuracy suddenly degrades," "won't FIX," "it worked yesterday but is off today," "connection drops," and "doesn't match known points" tend to occur.

What’s important here is not to treat RTK troubles as a single, uniform problem. RTK malfunctions can be caused by multiple factors — satellite reception problems, correction-data issues, communication problems, device/terminal configuration errors, coordinate system problems, operational procedure issues, and so on — and it is not uncommon for several of these causes to overlap. Simply hastily rebooting equipment on site may seem to fix the issue temporarily, but it often leads to recurrence and carries the risk of resuming work without having identified the underlying cause.

For example, even for a single symptom like not obtaining a FIX, the cause can be obstructions around the site, or the mobile connection may have dropped so correction information isn’t being received. Alternatively, even if corrections are being received, the selection of reference station information or mount point may be incorrect, so calculations cannot be performed under the expected conditions. Furthermore, even if the solution is FIX numerically, if the coordinate system settings are misaligned, this will appear in the field as a large positional offset.

Therefore, when troubleshooting RTK, it is essential to separate "how the symptoms appear" from "where the cause is located." If you systematically narrow down where the problem is occurring, the speed of on-site recovery will improve significantly. Conversely, if you continue changing settings without any order, you are likely to create additional configuration mistakes on top of the original cause.

In this article, we organize seven items to check first when RTK troubles occur, from a practical perspective. By verifying not only faults in the positioning equipment itself but also communication, corrections, satellites, coordinate systems, consistency with reference points, and operational procedures, you can reduce the likelihood of overlooking the cause. The content is summarized to be useful not only for personnel who use RTK on a daily basis but also for site managers and construction supervisors who have just implemented RTK and are not yet familiar with troubleshooting.

1. First, isolate the symptoms

The first thing to do when troubleshooting RTK is to clearly put into words what is happening. On site, people tend to say things like "RTK is not working" or "the positions don't match," but that alone is not enough to determine countermeasures. Simply breaking the symptoms down into finer detail can greatly narrow down where you need to look.

The first thing to check is whether the problem lies in the "positioning result" itself or in the "connection" or "communication." For example, if the device or app appears to be operating normally but never attains a FIX, then verifying correction data and satellite reception should be prioritized. On the other hand, if an external device is not visible to the terminal, Bluetooth won't connect, or a cable connection is not recognized, then it is a connection-path issue prior to positioning.

Next, it’s also important to determine whether it is completely unusable or usable but with poor accuracy. If you cannot obtain any positioning at all, basic checks of power, connections, communications, and login status should come first. Conversely, if positioning is possible but does not match known points, or shifts by tens of centimeters (several in) to several meters (several ft) when overlaid on drawings, then checking the coordinate system settings, control point management, and transformation settings becomes important.

Also, whether it occurred suddenly or was present from the start helps pinpoint the cause. If it was working normally until yesterday and is only malfunctioning today, changes in the site environment, changes in communication conditions, device updates, configuration changes, or changes in how the reference station is received become suspect. If it has been mismatching since immediately after deployment, initial setup, misunderstanding of the coordinate system, or differences in the understanding of on-site procedures are more likely causes.

When isolating symptoms, it is also important to check the numeric values and displays on the spot. Is it FIX or FLOAT, how many satellites are there, what are the HDOP and accuracy readouts, is the correction reception stable, is the communication icon normal, and does the difference from known points appear in a consistent direction or does it vary each time? Simply capturing this information can substantially change your diagnosis. If offsets cluster in a consistent direction, you are more likely to suspect the coordinate system or the handling of reference points; if they vary each time, you are more likely to suspect the satellite environment or instability in the correction reception.

A common occurrence on site is that multiple people each give different explanations. One person says, "the correction hasn't arrived," another says, "it's FIX," and yet another says, "only the known points don't match." In such situations, you need to align who is looking at which screen and what they are basing their statements on. The starting point for troubleshooting is defining the symptoms, not relying on intuition.

Not limited to RTK, in troubleshooting the less thorough the initial isolation is, the longer recovery will take. Confirming reproducibility on-site and quickly establishing under which conditions the malfunction occurs is the most effective first step. Rather than hastily changing settings across the board, organizing the symptoms first allows subsequent checks to proceed efficiently and without wasted effort.

2. Check the power, battery, and basic condition of the equipment

Many RTK problems can be resolved simply by reviewing basic conditions, without knowledge of advanced positioning theory or correction information. Particularly easy to overlook are the power supply, the battery, and the condition of the device itself. On site, conditions such as high and low temperatures, rain, dust, vibration, and repeated movement often coincide, so equipment that was stable in the office can easily develop faults.

First, check that the RTK receiver, smartphone or tablet, communication terminal, and all peripheral accessories have sufficient power. Even if the battery level is not zero, some devices become unstable in communications or Bluetooth when the remaining charge is low. Especially during long periods of outdoor use, high screen brightness, continuous mobile data usage, location processing, and connections to external devices can coincide and cause power consumption to increase faster than expected.

Also, when using a mobile battery or a power cable, be aware that even if you think it’s supplying power, it may not actually be charging. Cable breakage, poor terminal contact, dirt around the waterproof cap, or incompatibility with a conversion adapter can make it appear connected while not providing stable power. If the connection is lost with only a slight touch on site, it is likely a physical connection issue rather than a problem with the positioning system.

Furthermore, if restarting the device temporarily restores functionality, you should also suspect the device’s firmware/software or resource shortages on the terminal. If many apps are left running or background communication processes become heavy, the RTK app’s operation can become unstable. This is especially likely in smartphone-linked deployments, and you should include the terminal’s health status as well as the receiver when checking.

High-temperature environments should not be overlooked. Under direct sunlight in midsummer, terminals and RTK equipment can become hot, enter protective mode, and suffer degraded performance. Symptoms such as a dimming screen, more frequent disconnections, app crashes, and longer reconnection times may be related to heat. In such cases, simply reviewing positioning conditions will not improve things; operational measures are required, such as heat shielding, temporary cooling in the shade, cooling/insulation measures, and staggering operating times.

With respect to the condition of the device itself, you should also check for damage or dirt on the antenna section, deformation of the connector area, and deterioration of waterproofing materials. If it becomes unstable after a drop or impact, even if external damage appears minor, there may be internal effects. The problem, especially on-site, is that because it can somehow still be used, early-stage faults are easily overlooked. Small changes—such as taking longer than before to achieve a FIX, or the satellite count not increasing even at the same location—are easier to assess if recorded early.

When it comes to RTK troubles, people tend to focus on corrections and coordinates. However, checking the power supply and equipment status is the fastest and most reliable way to isolate the issue. If you proceed to the next checks while this remains unclear, you may end up suspecting more complex causes and taking a roundabout path. The more urgently you rush to restore operation on site, the more important it is to first reliably verify the basic state.

3. Check the connection status

In RTK operations, multiple connection paths are involved — the receiver, smartphones and tablets, the network, and, in some cases, external radios or SIM-based communications. Therefore, what appears to be a positioning accuracy problem is often actually caused by a connection fault. Verifying the connection status is a central part of RTK troubleshooting.

First, what you should check is how the receiver is connected to the device. Whether it's a Bluetooth connection, a wired connection, via a dedicated app, or using the OS's native location services, the way problems manifest will differ. With Bluetooth, even if pairing information remains, the actual communication session may not be functioning properly. The device may show as connected, yet the app may not be receiving data. In such cases, instead of simply toggling power, removing the pairing and registering it again can sometimes resolve the issue.

For wired connections, differences in cable standards, the quality of any adapter, the USB settings on the device, and the order of connection can all have an impact. It is not uncommon to be using a cable that can charge but cannot perform data communication. Because this is hard to judge from appearance, having a spare cable of the same type on site is important. When you suspect a connection fault, you need to check not only the settings screen but also whether position data is actually flowing and whether the device is recognized as an external device.

Next, network connectivity is also important in RTK operations. In network-based RTK, continuous mobile communication is a prerequisite for receiving correction information stably. Just seeing the antenna icon is not enough; you need to check whether the actual communication quality is stable. At sites with weak signal strength, even when it appears connected, reception of correction data can be interrupted, causing the system to switch back and forth between FIX and FLOAT.

Also, power-saving settings or background restrictions on the device can prevent the app from maintaining communication. Especially during long periods on site, the OS may automatically lower communication priority or restrict operation when the screen is off, which can cause reception of corrections or the connection to the receiver to become unstable. In such cases, even if there is no problem with the RTK receiver itself, you need to review the device's settings.

In sites where multiple connections are used simultaneously, it is important to separately check which connection has been severed. For example, if the Bluetooth link between the receiver and the terminal is alive but the terminal’s connection to the correction distribution service is down, the receiver will be visible yet will not achieve a FIX. Conversely, even if mobile data is functioning normally, if the link with the receiver is broken the positioning process cannot proceed before receiving corrections. On the surface both appear as “RTK not usable,” but the places you need to check are completely different.

When dealing with connection troubles, the order of reboots is also important. If you restart the receiver, the device, the app, and the network settings in a disorderly way, you won't be able to tell where the improvement came. The basic approach is to check the symptoms and disconnect and reconnect each connection target one by one. On site, it's surprisingly common for the devices to be too far apart, for other Bluetooth devices to cause interference, or for a device with the same name to be connected by mistake.

To consistently reduce RTK issues, simplifying connection paths as much as possible is effective. Operations such as swapping devices for each site, reusing cables, or running multiple apps simultaneously are flexible, but they also increase potential causes of trouble. The more frequently a site is used, the more fixing a standard configuration and unifying connection procedures will help shorten recovery times.

4. Check the reception status of correction information

For RTK to function as RTK, it is essential that correction information is being received properly. Therefore, when symptoms such as not achieving a FIX, unstable accuracy, or a sudden deterioration in positioning occur, you should prioritize checking the reception status of correction information. This is one of the aspects of RTK troubleshooting that tends to show site-to-site variation.

When using network RTK, the first thing to check is whether the correction distribution service is properly connected. If there is a problem with the login credentials, connection destination, mount point, or communication path, corrections will not be received even if the terminal or receiver is operating. In particular, when duplicating settings on site, settings for another project may remain, or the connection destination may be set to a different region. Because the settings themselves look familiar, they are easy to overlook, and this tends to delay identifying the cause.

Next, what you should check is not only whether corrections are being received but whether they are being received continuously. Even if a correction arrives momentarily, intermittent communication will not produce a stable position solution. You should not be reassured just because the display shows FIX; you need to confirm that it remains stable for several minutes and that it can be maintained while moving. At sites with weak communication, near tunnels, below slopes, in mountainous areas, or around structures, interruptions in correction reception are more likely to manifest as reduced accuracy.

When operating a reference station in-house, there are additional items to check. These include whether the reference station is correctly recognizing its coordinates, whether the transmission settings are as expected, whether the data format matches the receiver, and whether the power supply and antenna installation conditions are acceptable. Because monitoring only the mobile station will not resolve issues, having a system that can verify the status of the reference station via a separate route speeds up troubleshooting.

When there are issues with correction data, there are cases where the data appears to be received but does not meet the expected accuracy requirements. This is especially true when the receiver displays multiple statuses such as FIX, FLOAT, DGPS, or standalone positioning. Even if the person in charge concludes, "The position is being output, so there’s no problem," the measurements may in fact not achieve the inherent accuracy of RTK. Because the required accuracy level varies depending on the task, you should always check not only that coordinates are being output but also which status they are being output in.

A lack of understanding about the types of correction information and how to receive them also leads to problems. In RTK, high accuracy is achieved by combining not only signals from satellites but also correction information originating from a reference station. Therefore, even if the number of satellites is sufficient, without corrections you will not reach the expected accuracy. Conversely, even if you are receiving only corrections, if satellite reception conditions are poor you will not obtain a stable FIX. Corrections and satellites must be considered together as a set.

On-site, contracts for correction-data distribution and the management of connection endpoints tend to become practical blind spots. When the service period expires, authentication credentials change, or configuration inconsistencies occur across multiple devices, symptoms that appear to be equipment failures can arise. In such cases, no amount of rebooting the equipment will resolve the problem. Those responsible for deployment should formalize operational rules that cover not only management of RTK equipment but also the usage conditions for correction information and the management of configuration settings.

Checking correction information is an item that tends to be deferred the less familiar someone is with RTK. However, many problems where a FIX is not achieved can be diagnosed by carefully examining the reception status of the correction information, which will give you a sense of the likely cause. The accuracy of RTK is not supported solely by the performance of the receiver itself. Only when you include how to reliably receive correction information does RTK operation become practical for real-world use.

5. Check the satellite reception environment

To achieve high accuracy with RTK, you need not only correction information but also an environment in which satellite signals can be received stably. Therefore, when it is difficult to obtain a FIX, the solution is unstable, or accuracy deteriorates when moving, it is essential to check the satellite reception environment. This is obvious from the principles of RTK, but on-site attention often focuses only on equipment settings and the effects of the surrounding environment can be overlooked.

The first thing to be aware of is how open the sky is. An RTK receiver performs positioning calculations using signals from multiple satellites, but if the sky above is blocked by buildings, trees, bridges, slopes, heavy equipment, temporary structures, etc., the number of usable satellites can decrease and reception can become biased toward certain directions. Even if a certain number of satellites is available, poor geometric distribution can make accuracy unstable. It is important not to judge solely by the number.

Another thing to watch out for is multipath. This is the phenomenon where satellite signals reflect off building exteriors, vehicles, metal surfaces, water surfaces, and the like, causing direct and reflected waves to mix upon reception. Even in locations with a clear line of sight, surrounding conditions can make positioning unstable and the reported values may continue to fluctuate slightly. Extra caution is needed on narrow urban streets, material storage yards, sites with a lot of steel, and near guardrails.

When checking satellite reception conditions, it is useful to see whether moving the equipment just a few meters improves the situation. If FIX stabilizes simply by shifting the location slightly without changing settings, it becomes easier to determine that the surrounding environment has a strong influence. Conversely, if it does not stabilize even in an open area, it is more likely that other factors such as correction information or connection settings are involved.

Also, immediately after starting positioning, it may take a short time for reception conditions to stabilize. If you begin recording values as soon as you arrive on site, the system may not yet be stable. Especially when you are in a hurry, you tend to neglect the first few minutes. However, in RTK operations, simply allowing this initial stabilization time can reduce unnecessary re-measurements.

In satellite reception, the antenna's mounting orientation and how it is held also affect performance. If the pole is tilted, the receiver is loosely mounted, your body or the vehicle is blocking some directions, or the device is held close to your chest or at your side, reception conditions can deteriorate. This is not a problem that can be solved simply by using higher-performance equipment; careful handling directly translates into accuracy.

Surrounding environmental conditions often affect RTK more than the weather itself, but rain, wet ground surfaces, temporary sheets, and wet structures can also indirectly affect reflection conditions. Also, the amount of foliage on trees changes with the seasons, so reception conditions at the same location can differ. When a place that worked yesterday doesn’t work today, you should consider environmental changes as well as configuration errors.

When responding to RTK troubles, it's important not to conclude checks of the satellite reception environment by simply blaming "the site." What matters is determining where on that site the system can be used and which tasks can be carried out. In locations with restricted sky visibility, many countermeasures can be implemented in operational design, such as changing how observation points are selected, increasing auxiliary known points, or combining with other surveying methods. To operate RTK stably, reading the site environment is as important as equipment knowledge.

6. Check the coordinate system and positioning settings

One common troublesome issue with RTK is that the position doesn't match even though it shows as "FIX". In such cases, because power, connections, corrections, and the satellite environment all appear to be fine, identifying the cause often takes longer. In many cases the root cause is a mismatch in the coordinate system or positioning settings.

In RTK, it's not enough to simply measure your current position; it is also critically important which coordinate system those values are handled in. If the reference used for site drawings, known points, design data, and as-built management data does not match the settings on the RTK equipment or app, discrepancies ranging from tens of centimeters (several in) to several meters (several ft) or more can occur. Moreover, because the equipment will appear to be operating normally in such cases, the person in charge may not notice.

For example, confusion between latitude/longitude and plane rectangular coordinates, mixing up the global geodetic system with a site-specific coordinate system, misinterpreting geoid height versus ellipsoidal height, and omitting transformation parameters are typical causes. The settings you should suspect also vary depending on whether the discrepancy is in elevation or in planar position. If only elevation is anomalously offset, you should review the definition of elevation and the handling of the geoid model. If the planar position is consistently shifted in one direction, it is natural to suspect the coordinate system or the way the origin is handled.

Furthermore, with some apps and receivers it can be difficult to determine the type of coordinates being displayed and the internal calculation settings. Even if the screen appears correct at first glance, the output settings may be set separately, or previous settings may persist for each project. When multiple projects are handled on the same device, this kind of mix-up is likely to occur.

When a site uses its own local coordinate system, extra caution is required. In civil construction, land development, and equipment installation, work is often carried out using a local coordinate system to make tasks easier. In such cases, coordinates obtained from RTK cannot necessarily be used as-is. If you handle the numbers without understanding the transformation procedure and the relationship to the site reference points, you may find that, even though the equipment is operating correctly, the deliverables are unusable.

Coordinate system troubles can also arise from mismatched understandings among personnel. If the surveying team explains things using a global coordinate reference, the construction team interprets them based on site drawings, and the app configuration team continues operating with settings from past projects, a situation can occur where no one senses a device malfunction yet the positions simply don't match. Precisely because RTK is highly accurate, discrepancies in settings become clearly apparent.

A useful way to perform this check is to compare measurements at known or validation points. Rather than judging solely by how the current location looks, place the device at points with clearly defined coordinates and compare; this makes it easier to see error trends. If you can determine whether the errors are scattered, consistently offset by a fixed amount, differ only in height, or are offset with a directional component, it becomes easier to identify problems originating from the coordinate system or from settings.

When troubleshooting RTK, it is important not to over-rely on the FIX indication. FIX only represents the status of the positioning solution and does not guarantee that it is correctly tied to the coordinates you intend to use on site. Achieving precision and being correct as a deliverable are separate matters. To use RTK safely in practice, do not treat the coordinate system and positioning settings as a one-time initial setup; make it a habit to verify them for each project.

7. Confirm consistency with known points, reference points, and on-site procedures

Many RTK problems arise not from equipment or settings but from a lack of alignment with on-site procedures. This is especially common when surveying staff, construction management, subcontractors, and multiple crews are working on the same site. To use RTK correctly, not only the instrument readings but also the way site reference points are established and maintained and the work procedures must be aligned.

First, what I want to check is the reliability of the known points and reference points. It's not uncommon for a point that was thought to be a known point to have been relocated on site, for temporary stakes to have moved, for different crews to interpret markers differently, or for people to be referencing the control used in a previous construction phase. Even if measurements are made with high accuracy using RTK, if the reference points used for comparison are uncertain, the result can be mistaken as "RTK is off."

Next, an important issue is input errors in pole height and equipment height. This is simple but a very common problem. When a vertical difference appears as a constant amount, it may be due to differences in the input values rather than positioning theory. Because the values can change whenever equipment is swapped on site, extension parts are added, or fixtures are replaced, the issue is likely to recur unless operational rules are fixed.

Also, the timing and procedures of observations affect the results. Operations such as recording data before FIX is confirmed, observing immediately after moving before values have stabilized, omitting verification points, or skipping the initial checks at the start of work can become hotbeds for problems even when the equipment is functioning normally. Because RTK yields results in a short time, if efficiency is over‑prioritized the verification process tends to be cut short.

In multi-person operations, variations in procedures manifest as variations in accuracy. One operator checks known points every morning, while another carries over the previous day’s settings and uses them as-is. One team watches the FIX status for tens of seconds before recording, while another measures the moment the display switches. Such differences lead the site as a whole to conclude that “RTK is unstable.” In reality, differences in operating rules, rather than the equipment, are sometimes the problem.

What works well here is to have a simple manual for each site. Deciding in advance which known point to use for the start-of-work check, how many centimeters of deviation should trigger rechecking, where to restart if communication is lost, and to what extent FIX should be verified will make judgments less likely to waver during trouble. RTK is an advanced technology, but to operate it stably on site, it is essential to translate it into procedures that people can follow.

Furthermore, it is necessary to adopt a perspective that varies the level of verification according to the intended use of the deliverables. Tasks that only require a rough check and those that directly affect as-built form or quantities demand different levels of certainty. Treating everything with the same mindset can either waste time unnecessarily or, conversely, lead to insufficient checks and rework. Dealing with RTK troubles is not just about restoring the system; it is also about judging how much the resulting data can be trusted.

Checking consistency with known control points and procedures is directly linked not only to dealing with problems when they occur but also to ensuring quality during normal operations. A site that can judge by the same standards even when equipment is changed or personnel are replaced is strong. In sites using RTK, operational design makes more of a difference than the technology itself. What supports the correctness of the numbers is not only the equipment but also the shared understanding on site.

Operational Approach to Reducing Incidents

There are limits to dealing with RTK problems only after they occur. To use it reliably in the field, it is important to create conditions in everyday operations that make problems less likely to arise. The seven items we have reviewed so far are not merely recovery procedures; they also directly contribute to improving routine operations.

First and foremost, it is important to establish standard procedures at the site. By defining basic operations—such as checking known points at the start of the day, verifying the connection between the controller and the receiver, confirming reception of correction data, beginning observations once a FIX solution has stabilized, rechecking after the lunch break, and checking logs at the end of the workday—you can reduce variability between operators. RTK malfunctions are often not due to faulty equipment but to using the equipment differently each time.

Next, it is also useful to keep records when problems occur. If you leave even a brief record of which site, which time of day, what symptoms appeared, and what actions improved the situation, you will be able to respond more quickly if it recurs. Locations with weak communications, places where satellite reception is difficult, and sites that require attention when aligning with known points are all worth accumulating as site-specific knowledge.

Standardizing equipment configurations also contributes to stable operation. If devices, receivers, cables, communication methods, and app settings change each time, it becomes difficult to isolate the cause. Even when operating multiple units, aligning the standard configuration and unifying how settings are managed makes troubleshooting easier. Those responsible for deployment should take a view that not only compares device performance but also prepares configurations that are easy to reproduce on site.

Furthermore, it is important not to try to solve everything with RTK alone. In areas with limited sky visibility, unstable communications, or projects involving complex coordinate transformations, it can be more reliable to combine other positioning methods and checks of known points. RTK is a powerful tool, but it is not a cure-all. Distinguishing between tasks suited to RTK and tasks that require careful handling will, as a result, enable both quality and efficiency.

In recent years, smartphone-linked RTK operations have become more widespread, and there are an increasing number of products that are easy to handle in the field. For example, configurations like LRTK that pair with an iPhone to make high-precision positioning easy lower the barrier to adoption, while at the same time increasing the importance of device operation and connection management. In other words, choosing user-friendly equipment and preparing troubleshooting check procedures in advance both determine practical usability on site.

The seven items to check first when troubleshooting RTK are: isolating the symptom, power and equipment status, connections, correction information, satellite environment, coordinate system settings, and consistency between known points and procedures. If you check them in this order, you can narrow down the likely cause of many on-site problems. The important thing is not to keep frantically changing settings, but to examine sequentially which layer the problem is occurring in.

RTK is a technology that, when used correctly, can significantly boost on-site productivity and accuracy. However, if the checkpoints for troubleshooting are vague, its benefits cannot be fully realized. To ensure stable continued use on-site, it is important to share these seven items as daily operational standards and to establish a system that allows anyone to perform checks to the same standard.