RTK Troubleshooting Manual｜7 Items to Check First

RTK is a convenient system that allows you to quickly handle high-precision positioning information on site, but in practice troubles such as "suddenly won't get a Fix", "coordinates don't match", "can't establish a connection", and "it worked yesterday but is unstable today" are not uncommon. Moreover, RTK failures are not necessarily caused by a single factor — power, communications, settings, satellite reception environment, coordinate system, operational procedures, and so on often combine to cause problems. Therefore, rather than hastily changing settings all over the place, it is important to isolate and check the items to be verified one by one.

What causes problems on site is not the trouble itself but losing time because you don't know what to check first. Especially in time-constrained tasks such as surveying, construction management, as-built verification, layout marking, and site condition assessment, getting bogged down in investigating the cause can bring the entire operation to a halt. That is precisely why, in RTK operations, deciding in advance the "sequence of checks to perform when a malfunction occurs" makes a significant practical difference.

This article organizes seven items to check first when RTK problems occur, and provides detailed, practical explanations of common on-site symptoms, easily overlooked causes, how to proceed with checks, and approaches to prevent recurrence. Because it is organized around seven perspectives—power supply, communications, Fix status, known points, settings, surrounding environment, and operation records—it is easy to use directly as an initial-check manual when RTK is unstable.

Table of Contents

• Introduction

• Check the power supply and its surroundings.

• Check the communication status

• Check the fix status and satellite reception status

• Confirm consistency with known points

• Check the settings

• Confirm the impact of the surrounding environment

• Check operation records

• Summary

Introduction

The most important thing when troubleshooting RTK is not to fiddle with it based on guesswork. On site, you may be tempted to "just restart it," "reset the settings," or "try changing the correction data connection," but getting the order wrong can make the cause unclear and actually delay recovery. For example, if the problem was caused by a communication outage yet you repeatedly change only the settings, a fault that was originally simple can become complicated, and even after recovery it will remain unclear why it was fixed.

RTK is not a standalone positioning device, but a system that operates stably only when several conditions are met simultaneously. Even if the receiver unit itself is functioning normally, if the communication link is weak the correction information will not arrive, and even if the correction information does arrive, if the satellite reception environment is poor it will not obtain a fix. Even when a fix is obtained, if the coordinate system or on-site localization settings differ, the results will not match known control points. In other words, RTK malfunctions often occur not only due to mechanical failures but as mismatches in operational conditions.

Considering these characteristics, troubleshooting requires the perspective of isolating which layer the problem is occurring in. Broadly speaking, there are the power layer, the communication layer, the satellite reception layer, the coordinate alignment layer, the settings layer, the surrounding environment layer, and the human operations and records layer. If you check these in order, even if you cannot fully restore service on the spot, you can narrow down candidate causes and more easily move on to the next countermeasures.

Also, when handling RTK troubleshooting, knowing what “normal” looks like is important. If you routinely know how many minutes it typically takes to get a Fix after startup, which correction server you normally connect to, how much deviation to expect at known points, and which locations are unfavorable for reception, you can more quickly recognize abnormalities as abnormalities. Conversely, if you use the system without a baseline for normal conditions, it becomes difficult to determine what is abnormal, and on-site responses will lag behind.

From here, we will go through, in order, the seven items you should check first when you encounter RTK problems. The important thing is that, whatever the symptom, you should not start by assuming a complex cause; instead, eliminate possibilities one by one beginning with the basic conditions. Although it may seem like a roundabout approach, this sequence ultimately leads to the quickest resolution.

1. Check the power supply

The first thing to check in the initial response to RTK trouble is the power supply. It may seem like a simple item, but in practice it often becomes the entry point for on-site problems and is easy to overlook. This is because, even if the power is not completely off, voltage drops or poor contacts can cause symptoms such as unstable communications, reduced reception sensitivity, repeated reboots, or missing logs.

First, check whether the three components—the main unit, the controller, and the communication terminal—each have sufficient remaining charge. RTK operations involve multiple power systems: not only the receiver main unit but also smartphones or tablets, external communication devices, and, in some cases, external batteries or antenna power supplies. If any one of these is unstable, the whole system will effectively be in an "RTK unavailable" state. In particular, it is common for communication to be interrupted because the device that receives correction information runs out of battery or is set to sleep, even while the receiver unit itself is still operating.

Next, what you should check is not to rely on the battery level indicator alone. Even if a battery appears to have remaining charge, if it is degraded its voltage can drop the moment a load is applied, causing communications and satellite tracking to become unstable. This symptom is more likely to occur in the field under severe temperature conditions, such as in winter or midsummer. If it was working fine in the morning but suddenly becomes unstable a few hours later, you should suspect a combination of temperature and battery degradation rather than simply insufficient charge.

The condition of connectors and cables is also important. When operating with an external power supply, plugs can be only partially inserted, cables can be about to break partway, or waterproof caps may not close tightly so vibration changes the contact. Even if they appear connected, if the voltage drops only when they are lightly touched, the fault can recur during transport or when changing the tripod setup. You should also check whether the area around the connectors is contaminated with mud or dust and whether the terminals are worn.

What matters in practical power checks is not "whether it is on right now" but "whether it can supply power stably." To isolate whether the power supply is the cause, comparisons such as swapping in another fully charged battery, disconnecting external power and testing on internal power alone, or, conversely, testing with a stable external power source if the internal power seems suspect, are effective. Even if a single reboot appears to fix the issue, do not be reassured; you need to verify, even for a short period, that it continues to operate stably under the same conditions.

Also, power-saving settings on the controller or the app are easy to overlook. Screen turn-off or background communication restrictions can stop the reception of correction data or cause the app to disconnect from the receiver. This can easily appear to be a device malfunction, but it is actually an issue with the device-side settings. Devices used in the field should not be brought in with their everyday power-saving settings; they should be configured for work to prioritize maintaining communications.

Furthermore, power troubles need to be considered through to measures that prevent recurrence. Rather than simply ending with “I forgot to charge it today,” design operations to cover the number of replacement batteries, charging cycles, who is responsible for checking remaining charge, top‑up charging during lunch breaks, and whether spare devices are available; this will reduce the likelihood of the same problem recurring. RTK tends to draw attention to accuracy, but the causes of actual stoppages on site are often, surprisingly, the breakdown of these basic conditions.

Checking the power supply is unglamorous, but if you move on to the next stage with it left ambiguous you'll misidentify the real cause of unstable communications or position fixes. In a trouble situation, first isolating the power system as an independent candidate cause is the shortest route to recovery.

2. Check the communication status

The next thing to check with RTK is communication. With network RTK, because it assumes correction information is being received continuously and reliably, unstable communication alone can cause problems such as not achieving a Fix, staying in Float, being unable to maintain a Fix, or a sudden collapse in accuracy. In the field we often receive reports like “the satellites are visible but it won’t Fix,” and in a large proportion of those cases the communication conditions are involved.

First, what you want to check is whether the communication line itself is connected. Even if the device appears to have an Internet connection, there are cases where the signal is weak but only the connection indicator remains, the communication speed is extremely low, or either upload or download is unstable. The fact that a map app or browser can occasionally open does not necessarily mean RTK corrections will be stable. Because correction data requires continuity, maintaining an uninterrupted connection is more important than being connected for a moment.

Next I want to check the connection destination settings. If you are using an NTRIP connection, review whether the mount point, server name, port number, ID, password, and so on are correct. The tricky thing here is that even if only part of the settings is wrong, it can still look as if the connection process is proceeding. It is not uncommon for settings for a different site to remain, information from a previously used correction service to be mixed in, or for typographical errors to occur. In particular, at sites where multiple people share the device, someone may have changed the settings and not reverted them.

When checking communications, the condition of the SIM and tethering is also important. If you are connected via a smartphone, the device may enter power-saving mode, tethering may automatically disconnect, or the connection may weaken if the device is left idle for a certain period of time. Also, carriers have strengths and weaknesses depending on the site, so even within the same area coverage may be fine along roads but suddenly weaken near slopes or at the edge of mountains. The success of high-precision positioning is easily affected by these local communication conditions.

When isolating communication problems, it’s easier to organize if you separate the connection between the receiver and the device, the connection between the device and the Internet, and the connection between the Internet and the correction distribution service. For example, whether the Bluetooth or Wi‑Fi connection between the receiver and the device has dropped, whether the device itself is not connected to the Internet, or whether the correction service’s login credentials are invalid will require completely different remedies. If you lump everything together as “poor connectivity,” you won’t make progress in isolating the cause.

At the site, it is important not to leave checks of the communications environment to guesswork. Recording details such as where connections tend to drop, around what times instability is likely, how other carriers perform, and whether the presence of an external antenna makes a difference will be useful if the problem recurs. In mountainous areas, reclaimed land, near underground structures, at sites with many steel frames, and around tunnel portals, issues can appear not simply as dead zones but as localized quality degradation.

Also, you should understand how the device behaves when communication is temporarily interrupted. With some devices, the Fix is lost immediately after correction is lost, while others hold the Fix for a while before the accuracy degrades. If operators do not understand these differences, they may mistakenly proceed with measurements thinking "it's fine because it still shows Fix." Make it a habit to check not only the display but also the time of the last correction reception, the connection status, and whether updates have been received.

As a communication measure, adopting an approach that does not rely on a single connection is also effective. At critical sites, prepare spare SIMs or devices from other carriers, check communication status in advance, and set up a system to view correction-service outage information; preparations beyond the equipment itself affect operational quality. RTK is a positioning technology, but in operational settings the ability to manage the communications infrastructure has a major impact on stability.

3. Check the Fix status and satellite reception status

The status that tends to draw the most attention in RTK troubles is the Fix state. However, simply looking at whether it has a "Fix" or not is insufficient. In practice, you need to understand the meanings of status indicators such as Fix, Float, and standalone positioning, and consider the process leading to those states and the surrounding information together. Whether it fails to obtain a Fix or it obtains a Fix but cannot maintain it, it is important to first check this in conjunction with the satellite reception status.

If a Fix is not obtained, the first thing to consider is whether correction information is not being received, whether satellite observation conditions are insufficient, or whether it is both. Even if communications are normal and correction information is being received, the Fix will be unstable in environments where the number of satellites is insufficient, certain directions are obstructed, or multipath reflections are strong. Conversely, even if many satellites are being received, if correction information is not being delivered, you will not get a high-precision fixed solution. In other words, the Fix status is the result of multiple conditions and does not, by itself, indicate the cause.

When evaluating satellite reception, it is important not to look only at the number of satellites but to assess the quality of the reception. Even if the sky appears open, nearby high-voltage power lines, cranes, towers, large vehicles, building facades, water surfaces, or wire mesh can cause reception quality to deteriorate due to reflected signals. Even when many satellites are displayed, the stability of the Fix will decrease if observation conditions are poor. In particular, if instability occurs only at the edges of the site or close to structures, you should suspect an uneven reception environment rather than the satellite count.

Also, it's important not to place too much trust in values immediately after achieving a Fix. Just after startup or immediately after reconnection, the display may show Fix even though stability is not yet sufficient. Depending on the characteristics of each device, it is safer to wait until the condition has settled for a while after the display switches to Fix or to check at a known point before starting the actual measurement. The more hurried the site, the more likely people are to begin work the moment a Fix appears, but if you skimp on those tens of seconds to minutes here, subsequent re-measurements or rework can become significant.

If the Fix is easily lost, you should also review your positioning posture and how you hold the receiver. Small things—such as a tilted pole, covering the top of the receiver with your hand, being too close to a vehicle or machine, or blocking one direction with your body—can affect stability. In tasks that continuously acquire measurements by walking, measurements can be stable when you stop but become unstable while moving; in that case you need to review not only the positioning mode but also the workflow.

What’s important when checking the Fix status is not just the “current display” but also reading “why that display is shown.” For example, if a Float persists for a long time, corrections are being received but observation conditions may be insufficient. If it remains in standalone positioning, corrections may not be reaching the receiver or the connection settings may be incorrect. If Fix and Float alternate frequently, intermittent communications, surrounding obstructions, or a reflective environment may be the cause. This perspective of linking symptoms to causes speeds up on-site decision-making.

Furthermore, in practice it is important to standardize the interpretation of the Fix status among operators. Because display colors and abbreviations vary by device, one person may decide “it’s green so it’s fine,” while another may decide “it’s dangerous because the correction time is old.” If the way displays are read is inconsistent, quality will not be uniform even when using the same device. On site, you need to share in advance not only the conditions for a Fix indication but also what criteria will allow measurement to begin.

In RTK troubleshooting, the Fix status is a sign of the outcome. Rather than overreacting to it alone, understanding it in conjunction with the satellite reception environment, correction updates, observation time, and equipment attitude will lead to correct identification of the cause.

4. Confirm consistency with known points

Verification of known points is critically important when ultimately determining whether RTK is usable. Even if communication is established and a "Fix" indication appears, if it does not agree with known points, the positioning results cannot be used for operational purposes. On site, achieving a Fix is sometimes treated as the goal in itself, but what truly matters is whether the results are consistent with the required coordinate system and accuracy.

The role of checking known points is not simply to measure errors. It serves as a benchmark for early detection of various problems that commonly occur with RTK, such as coordinate system mix-ups, site localization errors, mixing of geodetic datums, shifts in elevation reference, antenna height input mistakes, and inconsistencies in installation procedures. In other words, checking known points is like a health checkup for RTK operations.

A common oversight on site is skipping the check of known points with the thought, "It was fine yesterday, so it should be fine today." However, even with the same equipment and the same location, conditions can change due to setting changes, switching the correction connection, terminal updates, or personnel changes. In particular, when operating across multiple sites, there is a risk that the settings from the previous site remain and measurements are taken in a different coordinate system. Such mistakes can be noticed relatively early if known points are checked first.

When verifying known points, what's important is not just seeing whether a single measurement was close, but also confirming reproducibility. Even if you get a close value by chance once, if a repeat measurement shifts, the Fix may be unstable or the setup may not be consistent. By checking multiple times over a short period and observing the error trends, it becomes easier to distinguish between a coincidental match and a stable agreement.

Also, you need to adopt a perspective that questions the accuracy of the known points themselves. When old markers or temporary markings are used as known points, the original coordinate values may not conform to current operational standards. Physical locations may have shifted due to pavement renewal or nearby construction, recorded values may differ from on-site indications, or the interpretation of the vertical datum may be ambiguous. If you only suspect the RTK side, you will overlook problems on the reference side.

When measurements don't match known points, it's useful to look at the pattern of the offsets. If both horizontal and vertical are shifted significantly across the board, suspect a problem with the coordinate system or localization. If only the elevation shows a noticeable offset, you should review the elevation datum or the antenna height input. If the offset is consistently the same amount in roughly the same direction each time, a configuration/settings issue is likely; if there is large variability, consider instability in the Fix or the installation conditions. In this way, you can infer the likely layer of cause from the nature of the offsets.

To make confirmation of known points part of on-site culture, it is also important to keep the verification procedure simple. If complex forms have to be filled out every time, they tend to be skipped. For example, doing one check at the start of the shift, rechecking after midday as needed, and only rechecking necessary locations at the end creates a workflow that is easier to sustain while keeping the burden low and ensuring quality.

At RTK trouble sites, attention tends to go to whether the equipment is operating, but what ultimately guarantees correctness is consistency with known points. Rather than whether a Fix indication appears, adopting the practice of checking how well positions can be reproduced against known points is the foundation of positioning quality.

5. Confirm the settings

One of the most deep-rooted problems in RTK troubleshooting is configuration errors. Unlike issues that are easy to see, such as power or communications, settings can appear to be functioning normally while only the results are wrong. Moreover, configuration-related faults are often slow to be detected because the operator believes they "did it the usual way."

First, check the positioning mode and correction method settings. Devices and apps offer multiple operating modes, such as standalone positioning, DGPS, RTK, and modes intended for post-processing. If you use them without clarifying which mode is active, you will not achieve the expected accuracy. Also, even if you are receiving correction information, results can be unstable if that information does not match the method assumed on site. This mix-up is common at sites that switch between multiple services or multiple devices.

Next, the coordinate system settings are crucial. The plane rectangular coordinate system's zone number, how latitude and longitude are handled, the type of geodetic datum, and whether a geoid is applied can cause not just centimeter-level but much larger discrepancies. On site, we receive inquiries such as "the coordinates are shifted overall" or "only the elevation is strange," and behind these issues there can be mismatches in coordinate system settings. In particular, if the reference standards are not unified among client-provided data, design drawings, known point reports, and equipment settings, the field team can end up using shifted values without realizing it.

Site localization and transformation settings are also points to watch. On construction sites, drawing coordinates, arbitrary coordinates, or local origins may be used, and their transformation parameters may be stored on equipment or terminals. If these settings come from a different site, even if the fix itself is correct, the coordinates produced will be unusable. Moreover, because the values can look plausible numerically, if verification of known points is omitted, detection will be delayed.

Entries for antenna height and equipment height also frequently cause problems in practice. Typical mistakes include changing the pole height without correcting the value, confusing the slope distance with the vertical height, using different units, or leaving an input field set to the previous value. These errors tend to appear especially as vertical-direction discrepancies and can be critical for as-built verification and height management. Moreover, on-site attention is often focused on horizontal accuracy, and height checks tend to be postponed.

To prevent configuration problems, an operational practice that allows tracking change history is effective. If records show who changed which setting and when, isolating faults becomes faster when anomalies occur. Conversely, if multiple people can freely modify settings, it’s easy to end up in a situation where “someone changed it yesterday evening but no one remembers,” which delays recovery. Frequently used on-site settings should be templated and loaded at the start of operations to reduce input errors and leftover settings.

Also, behavior can change after app or firmware updates. Because not only screen layouts and setting names may change but default values can also be altered, you should always verify with a known point after an update. Leaving updates to automatic installation can result in settings having changed on the day of fieldwork, which is a situation you want to avoid. For business devices, it is desirable to manage the timing of updates and to complete post-update verification before putting them into production use.

Checking settings is something that people who are more experienced are especially likely to let their guard down about. Everyone pays attention to power and communications, but settings are easy to assume are "the same as always." When RTK is unavailable, or when it appears to be working yet the results don't agree, it's essential to verify the consistency of the settings one by one.

6. Confirm the effects of the surrounding environment

Because RTK is often used outdoors, it is strongly affected by the surrounding environment. Even if the equipment, communications, and settings are correct, poor environmental conditions can cause problems such as being unable to get a fix, unstable positioning, or position offsets that occur only in certain locations. Therefore, when troubleshooting, you need to calmly observe the on‑site environment before suspecting the equipment.

The first thing to check is sky visibility. Because RTK requires stable reception of multiple satellites, having a wide, clear view of the sky is a basic requirement. In gaps between buildings, densely vegetated locations, near cuttings and slopes, under bridges, and in mountainous areas, the view in certain directions is easily obstructed, and a skewed satellite geometry can make the Fix unstable. Even where it appears to be outdoors, many locations do not have an adequate open view of the sky, and in places where vegetation conditions change between winter and summer, conditions also vary by season.

Another thing to watch out for is reflective environments. Facades of high-rise buildings, metal fences, guardrails, heavy machinery, vehicles, temporary structures, steel frames, puddles, and the like can cause satellite signal reflections and degrade reception quality. These effects are trickier than simple obstruction, and even if a sufficient number of satellites are available, positioning can become unstable. Symptoms such as readings fluctuating only when standing in a particular spot, or stabilizing when you change orientation, are clues that point to a reflective environment.

The communication environment is also part of the surrounding environment. Behind embankments on developed land, along hillsides, in areas close to underground structures, and in zones with dense equipment, communication quality can deteriorate locally. With RTK, stability requires both satellite reception and communication, so an open sky alone is insufficient. There are places where the sky is open but correction signals are weak, and conversely places where communication is good but reception is poor. On site, you should understand that locations suitable for positioning and those suitable for receiving corrections do not necessarily coincide.

When checking the surrounding environment, the important thing is to consider the problem as location-dependent. To distinguish whether the receiver is faulty or whether this particular spot on site is the issue, it's useful to move a few meters to a few tens of meters (a few ft to a few dozen ft) and see if the situation changes. Even with the same device, if it doesn't get a fix next to a building but stabilizes when moved a short distance away, the cause is more likely environmental than the device. Tweaking settings on the spot without making this comparison will not provide a fundamental solution.

Also, the effects of the time of day cannot be overlooked. The positions of work vehicles, crane operation, surrounding traffic volume, and changes in the layout of on-site equipment can cause reception conditions to differ between morning and afternoon. There are also cases where reception becomes more difficult than before due to an increase in temporary structures. In other words, even at the same site, the environment is not fixed and must be treated as something that changes according to the work schedule.

In sites with poor conditions, it is important to decide not to force completion using only RTK on-site. Establish a reference at a location with better reception, and, as needed, combine it with other methods, change the measurement positions or order, or add supplementary observations — flexibility to switch to procedures tailored to the site is required. Because RTK is not infallible, in areas with severe environmental conditions you need to rethink how you use it.

Checking the surrounding environment is an important step before suspecting equipment malfunction. Many problems that occur on site are influenced more by the conditions in which the machine is placed than by the machine itself. For that reason, observing factors such as the degree of openness of the surrounding space, reflective objects, communication status, work position, and changes over the course of the day is the quickest route to stable operation.

7. Review operational records

The last thing to check is the operational records. The power supply, communications, Fix status, known points, settings, and surrounding environment we’ve looked at so far are all items that can be checked on site. However, past records are indispensable for reproducing troubles and identifying their root causes. If you end the visit with “it was just acting up today,” the same problems will be repeated.

For operational records, it is useful to note items such as start time, equipment used, terminal used, battery replacement time, correction connection destination, known-point verification results, site location, any concerning symptoms, whether a reboot occurred, and any configuration changes. You do not need to write down every detail, but you should record enough to be able to tell later what happened and when. Simply having records can greatly speed up troubleshooting when the issue recurs.

For example, if the Fix becomes unstable every afternoon, suspect rising temperatures, network congestion, battery degradation, and the like. If the connection drops only on days when a particular device is used, it may be a device setting or a Bluetooth compatibility issue. If a known-point offset appears only when using a certain correction source, that should prompt a review of the settings and transmission conditions. In this way, records are not merely reporting materials but are inputs for root-cause analysis.

Also, operational records also serve to prevent knowledge from becoming person-dependent. In RTK operations, things may be manageable while an experienced operator handles issues by feel, but once that person is absent, work on site can quickly grind to a halt. If know-how such as "at this location I always move once to the north before initializing" or "communication at this site is more stable in the morning" is not recorded, the next person will repeat the same mistakes. Records are the means of turning an individual's experience into shared on-site knowledge.

If the device can produce log files, it is useful not only to keep notes on the app screen but also to save device logs and connection logs. Being able to review intermittent reception of corrections, the status of transition to Fix, satellite status, and the history of error messages can reveal problems that were not visible on site. In particular, for issues with low reproducibility or cases where the system temporarily recovered on site but the cause is unknown, the presence or absence of logs can determine how effectively you can respond next time.

To make operational records useful, it's necessary not only to keep them but also to review them regularly. Even once a month, organizing what kinds of problems were common, which sites tend to experience which issues, and whether there are differences between devices makes it easier to implement preventive measures. For example, this can lead to improvements such as realizing there are not enough spare batteries, that a different-carrier device should be used at a particular site, or that known-point checks should be scheduled in both the morning and the afternoon.

Furthermore, standardizing the format for recording incidents stabilizes the quality of reports. Even having common fields for "Symptoms", "Time of occurrence", "Location", "Actions taken", and "Whether it improved" makes it easier to compare causes. Conversely, if reports are only verbal, they become vague impressions, leaving only information such as "probably a communication issue" or "seems unstable", which does not lead to improvements.

RTK issues aren't just about being fixed on the spot. True troubleshooting means ensuring that when the same thing happens again you can respond faster and more reliably. To do that, it's essential to create a cycle of keeping operational records, reviewing them, and reflecting them in on-site procedures.

Summary

In RTK troubleshooting, above all it is important not to assume a single cause and to check the basic conditions in order. When you panic on site you tend to suspect complicated settings or equipment failure, but in fact the cause is often found among basic items such as power, communications, Fix status, known points, settings, the surrounding environment, and operation records.

First, check the power: the starting point is to isolate whether the equipment, terminals, and external power supply are operating stably. Next, examine communications and organize the terminal connections, line quality, and the connection conditions for correction services. Then confirm the Fix status and satellite reception conditions, and while correctly interpreting what the displays mean, be sure to assess the quality of reception, not just the status indicators.

And in practice, the most important thing is consistency with known points. Even if you have a fix, if it does not match the known points, the results cannot be used. Furthermore, you should review settings such as the coordinate system, correction method, and antenna height, and maintain a mindset that suspects configuration issues that can distort results even when everything appears normal. In addition, observe the effects of the surrounding environment—such as sky visibility, reflections, and communication conditions—and do not forget the possibility that the cause lies in the location rather than the equipment.

Finally, to prevent troubleshooting from being a one-off, operational records are indispensable. If you record what happened, how you responded, and what improvements were made, the next response will certainly be faster. RTK is a high-precision technology, but what supports stable operation is the steady accumulation of such careful checks and records.

When RTK becomes unstable, first try isolating the issue by following the seven items introduced here. Simply deciding on an order and checking them will reduce unnecessary reconfiguration and roundabout steps caused by assumptions, and greatly improve on-site recovery capability. To reliably apply high-precision positioning to your operations, not only choosing high-performance equipment but also having an operations manual that allows you to calmly verify things during trouble is a major strength.