Why Isn't RTK Getting a Fix? 8 Causes to Check On Site

When using RTK in the field, you may encounter issues such as never achieving a Fix no matter how long you wait, reverting to Float soon after obtaining a position, or instability that differs by day even at the same location. RTK is a method that can achieve high-precision positioning, but it will not necessarily become stable simply by turning on the receiver. Only when multiple conditions are met—satellite reception conditions, transfer of correction information, observation environment, configuration settings, operational procedures, and so on—can a stable Fix be achieved.

In practice, if you assume there is only one cause for not getting a fix, it will take longer to recover. For example, even if you think communications are the cause, the real culprit may be poor sky visibility, or satellites may be visible but the format of the correction data or the handling of coordinate systems may not match. Conversely, what looks like an environmental problem is often actually caused by the base station’s operating conditions or the rover’s initialization procedures.

Therefore, in this article we organize eight causes you should prioritize checking on-site when RTK fails to achieve a Fix, and explain from a practical perspective how to isolate them and the directions for countermeasures. Rather than merely explaining terminology, we cover where to start checking on-site, why those checks are necessary, and what should be standardized to prevent recurrence. Troubleshooting RTK becomes significantly faster when causes are viewed systematically. To ensure you can respond calmly when you cannot obtain a Fix, we will organize the key checks to run here.

Table of Contents

• First understand the mechanism by which RTK obtains a Fix

• Cause 1 Sky visibility is poor and satellite conditions are insufficient

• Cause 2: The observed values are being disturbed by the effects of surrounding reflections.

• Cause 3 Correction information has not been received, or is interrupted

• Cause 4: The distance to the reference station and operating conditions are not appropriate

• Cause 5 Operational procedures immediately after initialization are not stable

• Cause 6 Reception settings and correction conditions do not align

• Cause 7 Problems with antenna installation or mounting/retention methods

• Cause 8 Equipment, power, and communication-related conditions are unstable

• Order of checks and measures to prevent recurrence at sites where RTK does not obtain a fix

• Summary

First, grasp how RTK obtains a Fix

To correctly understand why RTK does not achieve a Fix, you must first be clear about what condition constitutes a Fix. RTK uses signals received from satellites to determine position, but it is not simply calculating the current location as in standalone positioning. It compares observations from a reference station with a known position to the observations of the rover whose position you want to measure, and uses the differences to cancel out errors and thereby improve accuracy.

What becomes important at this point is that satellite-signal tracking is stable, that correction information is being delivered appropriately, and that the integer ambiguities of the carrier can be resolved stably. The state in which these integer-value solutions are stably and definitively resolved is generally called a Fix. Conversely, when the solution has not yet been sufficiently fixed it is called a Float, and under even worse conditions it approaches standalone positioning.

In other words, an RTK fix is not achieved by merely receiving satellite signals. It’s not simply a matter of having many satellites; an RTK fix is only attained when reception quality, geometric conditions, correction information, communication status, the surrounding environment, and consistency of settings all come together. Therefore, when a fix is not obtained, you must not look only at the receiver itself but check the entire observation system.

A common misconception on site is to assume there’s no problem because the satellite numbers look reasonably good. In reality, the number of satellites in view does not always correspond to the likelihood of getting a Fix. If most satellites are at low elevation angles, observation quality tends to degrade, and in locations with a lot of reflections the signal quality worsens. Also, if correction data is even slightly delayed or missing, a Fix will not be stable even when satellites are being received.

As such, the problem of RTK not obtaining a Fix cannot be judged by looking at just a single display item. That is why it is important to break down and check the possible causes. From here, we will go through the eight causes that are particularly likely to occur in the field, one by one.

Cause 1 Poor sky visibility and insufficient satellite conditions

The first thing to suspect is, as expected, the observation environment. Because RTK computes positions from satellite signals, it becomes difficult to obtain a fix when the sky is not sufficiently open. Near buildings, beneath slopes, in mountainous areas, in heavily wooded locations, or in places surrounded by structures, the number and geometry of available satellites tend to be skewed.

What matters here is not simply whether a small patch of sky is visible, but whether you have a consistently clear line of sight over a wide angle. Even if it is open directly overhead, if the surroundings are enclosed it becomes difficult to acquire satellites at low elevation angles, and the geometry deteriorates. In RTK, because multiple satellites must be stably tracked simultaneously to obtain a high-precision solution, insufficient visibility is a major cause of delayed Fixes or failure to achieve a Fix.

In practice, the point you want to measure is sometimes right next to a structure, making it impossible to get a Fix on the spot. In that case, the important thing is not to force completion of initialization at that point. First, obtain a stable Fix in a nearby open area, then move to the observation point quickly, or combine auxiliary operations; you need to devise an appropriate procedure. If it consistently takes a long time to get a Fix at the same location, you should suspect environmental factors specific to that point.

Also, because satellite geometry changes with weather and time of day, you may find that obtaining a fix was no problem yesterday but is difficult today. These fluctuations cannot be completely avoided, but they have a greater effect at sites with poor sky visibility. Therefore, before observation, check how unobstructed the sky is at the site and determine in advance where initialization will be easiest and from which positions continuous observation will be easiest to maintain.

When investigating why it won't fix, you may be tempted to start with communication settings or equipment failures, but in reality the most fundamental and easily overlooked factor is the view of the sky. If you're unsure on site, first move a few meters to a few tens of meters (a few ft to a few tens of ft) and simply check whether the condition improves in a more open location — just that can help narrow it down. If it stabilizes simply by changing location, you can consider the reception environment to be the primary cause.

Cause 2 Observed values are being distorted by surrounding reflections

If you still don't get a Fix even with a relatively open sky, the next thing to suspect is reflections from the surroundings. Signals arriving from satellites are very weak and can be affected by reflections from metal surfaces, glass, water surfaces, exterior walls, vehicles, heavy machinery, fences, and similar objects. When such reflected waves mix in, observations of the true arrival time and phase are disturbed, and integer ambiguity resolution becomes unstable.

This effect is troublesome because it is hard to judge by sight in the field. Even if you think it’s fine because the sky is open, reception quality can drop significantly if a large vehicle is parked right next to you or if metal handrails or steel materials are lined up. The reason RTK tends to be unstable on narrow urban roads and around structures is not just simple obstruction but the compounding of these reflection effects.

The frightening thing about reflections is that anomalies are difficult to detect from satellite count alone. Even if many satellites are visible, a Fix won't be stable unless the observations are clean. Furthermore, even after achieving a Fix, the reception environment can change during observation as nearby vehicles or heavy machinery move, causing it to revert to Float. In other words, reflections not only prevent getting a Fix, they can also make maintaining a Fix impossible.

As a countermeasure, the basic approach is to physically increase the distance from reflective sources. Avoid placing metal objects near the antenna, do not initialize near a vehicle roof or against a wall, and avoid locations immediately adjacent to material storage yards; even slightly changing the installation position can lead to improvements. Especially during initialization, observation stability is important, so rather than forcing a fix in poor conditions, it is more efficient overall to obtain a reliable solution in a position with fewer reflections.

There are also situations where the operator’s own body or the way they hold the device can affect reception. If the receiving unit is brought too close to the body, tilted, or the operator partially blocks the overhead space, the condition can subtly worsen. This is especially true for handheld operation, where environmental factors and holding conditions can combine to increase instability, so maintaining consistency in placement is important.

Reflections are invisible, so relying solely on experience makes judgments inconsistent. At each site, recording where it takes longer to get a Fix and which orientations or layouts cause instability will help prevent recurrence in the future. Developing the habit of checking not only the sky view but also surrounding reflection sources is the first step to improving RTK operation accuracy.

Cause 3 Correction information has not been received, or is interrupted

In RTK, simply having the rover receive satellites does not achieve high-precision positioning. It is necessary to properly receive the correction information sent from the base station and use it to correct errors. Therefore, if correction information has not arrived, is arriving but intermittent, delayed, or in an incompatible format, it is natural that a fix will not be obtained.

On site, this cause is seen quite frequently. Because the satellites are being received, it may at first glance look as if positioning itself is working, but if the flow of correction information is unstable the solution can remain at Float or take a very long time to reach Fix. In cases where the communication link’s radio conditions are poor, the connection to the base station is lost, the correction stream’s authentication or selection settings are incorrect, or the received data arrives only intermittently, it will not stabilize no matter how long you wait.

A problem that is particularly easy to overlook is not a complete loss but an intermittently interrupted state. Even if corrections arrive for short periods, poor continuity means the conditions necessary to establish and maintain a Fix are not met. From the operator’s perspective the connection may appear to be active, making the cause hard to notice, but in reality the quality of the correction information may be insufficient.

During this troubleshooting, it is important to check the reception status of correction information, the update interval, the duration of continuous connection, and the stability of communications. At sites with poor communication environments, you should not only check for the presence of a signal but also verify whether correction reception remains stable when you move the work location slightly. Also, in operations where communication conditions change while moving, communication can become disrupted just before a fix is obtained, so initialization should, as a rule, be performed at as stable a location as possible.

Furthermore, if the type of correction information or the receiver-side settings are not appropriate, the data itself may be received but cannot be used effectively. This point is also related to later configuration factors, but in the field this area is easily confused between communication and configuration. It is easier to sort things out by first checking whether the corrections are being received stably, and then whether their contents are being handled correctly.

When RTK fails to obtain a fix, focusing only on satellite conditions can cause you to overlook problems with the correction information. In practice, it is safer to assume you are only at the starting line when both satellite reception and correction reception are in place. It is important to verify not just that corrections are being received, but that they are arriving stably, continuously, and in a valid form.

Cause 4: The distance to the reference station and operational conditions are not appropriate

Because RTK uses the observation differences between a base station and a rover, if the conditions of the two differ too much the effectiveness of the corrections tends to decrease. In general, the farther apart the base station and the rover are, the less likely the effects of the ionosphere and troposphere, satellite-specific error patterns, and local environmental differences will match, and the Fix may become unstable.

This problem in the field does not occur only when you enter a location far from the reference station during wide-area work. It can also occur when, in operations that switch among multiple correction sources, a correction that is not optimal for the field conditions is selected, or when the installation environment at the reference station itself is unstable. If the reference station’s setup point is shaking, signals are obstructed, the power supply is unstable, or communications are interrupted, adjusting only the rover side will not provide a fundamental solution.

Also, even if a reference station considers itself stable, differences in installation height and the surrounding environment can introduce biases in observation conditions. Because a reference station has the role of continuously sending corrections stably over long periods, its installation conditions must be more stringent than those for a rover. If this is ambiguous, it tends to appear on rovers as unexplained non‑Fix.

In practice, because troubleshooting is often carried out with only the rover, checks on the base station tend to be postponed. However, if multiple rovers at the same site simultaneously have difficulty obtaining a Fix, or if the system as a whole is unstable only on certain days, you should suspect the base station or the conditions under which corrections are provided. Conversely, if only a single rover is unstable, it is more efficient to prioritize verifying that rover’s specific settings and the condition of its equipment.

To address this cause, it is useful to organize in advance the concept of distance and operational rules. Standardizing which correction conditions are used for which operational ranges, what to check when installing the base station, and how to compare and verify during anomalies prevents inconsistent decisions in the field. Since RTK problems are not confined to the rover alone, it is important to consider the entire system, including the base station.

Cause 5 Operational procedures immediately after initialization are not stable

The initialization process of RTK until it achieves a Fix is extremely important. If reception conditions are not stable at this stage, there may not be enough observations, causing it to take a long time to reach Fix or to remain in Float indefinitely. However, in actual field work there are surprisingly many actions that destabilize initialization, such as starting to walk immediately after powering on, moving to the observation point before checking reception status, or repeatedly changing how the receiver is held during initialization.

The receiver gradually acquires satellites and stabilizes observation conditions immediately after startup. Therefore, how you use the first few minutes will affect how easy it is to obtain a Fix afterward. If you move into a poor environment or pass through an area with weak communications during initialization, the conditions that were beginning to stabilize can be disrupted. As a result, operators may be left with nothing more than the impression that, for some reason, it is difficult to get a Fix today.

Even after a Fix has been achieved, if initialization is insufficient and unstable observations continue, it can easily revert to Float with slight environmental changes. This means that what matters is not merely whether a Fix was displayed once, but whether the system has been sufficiently prepared to maintain a stable state. Rather than starting work immediately based only on the numeric display, operational procedures should wait a short time and confirm that the state is stable.

On sites with less-experienced crews, there's a tendency to cut initialization time because people want to start working immediately after startup. However, with RTK, skipping a few minutes of checks can result in losing many times that amount of time later to re-surveys and troubleshooting. If you want to improve operational efficiency, performing initialization carefully will ultimately be faster.

As countermeasures, after powering on first stabilize reception in an open area; confirm correction reception and satellite acquisition before moving; avoid sudden movements or large attitude changes during initialization; and even if a Fix indication appears, do not make an immediate judgment—confirm that the fix remains stable. These basic procedures must be rigorously followed. Consistency in basic operations has a much greater impact on Fix rate than complex techniques.

Cause 6 Receiving settings and correction conditions do not match

A surprisingly common issue in the field is failing to obtain a fix because of mismatched settings. If satellites are visible, corrections are being received, and the environment is not that poor, but you still don’t get a fix, you should suspect inconsistencies in the receiver settings or the correction conditions. For example, if the configured satellite systems, the handling of correction data, the observation mode, coordinate-system–related settings, or initialization thresholds are not aligned with field conditions, the solution can be difficult to stabilize.

Configuration issues are characterized by being difficult to judge from appearance alone. Because numeric values are displayed on the receiver screen, it may appear to be operating, but internally the necessary conditions may not be met. Also, settings left unchanged from a previous job at a different site may not match the current operating conditions. At sites with multiple operators, changes made to settings are sometimes not shared, so the state can change without anyone realizing it.

Another thing to watch out for is that even if settings are not completely wrong, subtle mismatches can create instability. For example, if the priority order of reception targets or observation conditions does not match the field, the time to Fix will be no