Why doesn't it become a Fix solution? Differences from a Float solution and 8 improvement points

When using RTK positioning, you may encounter situations where accuracy does not stabilize as expected and it never becomes a Fix solution. Even if the display seems to be positioning, many field operators feel uneasy using the data when the status remains a Float solution.

Especially for tasks that require centimeter-level accuracy—construction management, as-built verification, staking out positions, and current condition surveys—the difference between a Fix solution and a Float solution is not merely a display issue but directly affects work quality. Therefore, it is important to organize and understand “why it doesn’t reach Fix,” “is it acceptable to use it while still Float,” and “how can it be improved.”

This article organizes the differences between Fix and Float solutions from a practical perspective, explains the main reasons a Fix solution may not occur, and breaks down eight improvement points to review on site. It does not merely explain theory; it summarizes common on-site situations and the viewpoints you should check.

Table of contents

• Grasp the difference between Fix and Float solutions first

• Improvement point 1: Secure sky visibility and improve satellite conditions

• Improvement point 2: Check not only the number of satellites but also distribution bias

• Improvement point 3: Review whether correction data is being received stably

• Improvement point 4: Don’t underestimate breaks in the communication environment

• Improvement point 5: Don’t rush initialization—let observation conditions settle

• Improvement point 6: Improve receiver/antenna handling and installation state

• Improvement point 7: Check for discrepancies in coordinate and operation settings

• Improvement point 8: Avoid surrounding reflections and radio interference

• Risks of proceeding while staying in a Float solution

• Practical considerations to stabilize Fix solutions

• Summary

Grasp the difference between Fix and Float solutions first

In one sentence, the difference between a Fix solution and a Float solution is the degree of confidence in the computed position. Both are positioning states that aim for high accuracy using correction data, but a Fix solution is a state in which the integer ambiguities have been stably resolved and the position is determined with higher accuracy. A Float solution, on the other hand, is a state where the solution has not yet sufficiently converged despite receiving corrections, leaving positional uncertainty.

In the field, a Fix solution is easy to use for centimeter-level position confirmation, whereas a Float solution tends to produce larger errors and more variable position readings. Of course, Float does not always mean completely unusable: it can be helpful for approximate location awareness or as a reference value. However, treating Float-derived values as decision material for construction or surveying requires caution.

What often causes confusion in practice is that the difference between Fix and Float is not obvious on the screen because numbers are displayed. If positioning continues, users tend to think, “If it’s connecting, it should be fine,” but Fix and Float have entirely different implications. A Fix solution tends to be treated as a prerequisite for proceeding safely with work, while a Float solution is safer to regard as an intermediate state that needs improvement.

There is also not a single reason why Fix is not achieved. Satellite visibility, communication status, quality of correction information, surrounding environment, how the device is held, and mismatched settings are often intertwined. Therefore, simply rebooting does not always solve the issue; you need to review the field conditions step by step. Understanding this helps you stay calm and isolate causes when Fix is not achieved.

Improvement point 1: Secure sky visibility and improve satellite conditions

The first thing to suspect when a Fix solution is not obtained is poor sky visibility. RTK positioning achieves high accuracy by stably receiving multiple satellite signals; if the sky is not sufficiently open, that premise breaks down. Even where you think the sky is visible—next to a building, under trees, beneath an overpass, along a slope, or near a materials storage area—reception conditions can actually be poor.

One important point is that it is not enough to have only the zenith visible. Satellite signals coming in at low elevation angles are also important, and in enclosed surroundings the number of usable satellites may decrease and the geometric conditions needed for positioning may worsen. As a result, even if correction data is being received, the solution can remain unstable and linger in Float.

A common field case is starting to collect a point beside a building and watching time pass without ever getting a Fix. In such cases, people tend to suspect the device or settings, but simply moving a few meters can often improve the situation. Before insisting on a working position, it is more efficient to first check the status in a spot with a wider view of the sky, then approach the target point.

Also note that satellite geometry changes at morning and evening, and visibility can differ even within the same site depending on location. If one spot yields a Fix but another doesn’t, it is likely due to environmental differences rather than equipment failure. When Fix cannot be obtained, the basic step is to calmly re-evaluate how open the sky is.

Improvement point 2: Check not only the number of satellites but also distribution bias

When Fix is not achieved, many people check only the number of satellites. While satellite count is important, it’s not sufficient by itself. In practice, how satellites are distributed across directions is as important as how many are visible. Even with a high satellite count, if they are clustered in similar directions the positioning geometry deteriorates and the solution becomes harder to stabilize.

This is similar to having biased reference directions when determining a position from multiple baselines: precision drops when references are skewed. In RTK positioning, a balanced distribution across the sky is advantageous. Conversely, if buildings or terrain open the sky in only one direction, the apparent satellite count may be adequate but transition to Fix can be delayed or unstable.

Therefore, if you have enough satellites but cannot get Fix, look at the overall observation conditions rather than just the count. In unstable sites, simply shifting position slightly to change sky exposure can suddenly yield a Fix. Often this is less about seeing more satellites and more about alleviating bias in satellite geometry.

For field operators, the important point is not to be reassured by satellite count alone. Even if the displayed numbers look fine, low solution stability means the observation conditions are not sufficient. If you want a Fix, pay attention to both the number and distribution of visible satellites, initialize in a favorable spot, and create the best possible observation conditions.

Improvement point 3: Review whether correction data is being received stably

Obtaining a Fix solution with RTK requires not only receiving satellite signals but also stably receiving correction data and continuing positioning computations based on that data. If this is unstable, the satellites may be visible yet the solution does not converge and remains Float.

In the field, people often assume that once correction data connects it’s fine, but intermittent delays or dropouts can actually occur. Even if the communication icon appears active, if correction data is not being supplied steadily, maintaining a Fix is difficult. This is especially likely during mobile operations or in weak-signal sites.

Also, if the correction source or connection settings are inappropriate, obtaining a Fix becomes harder. The connection might be established but set up in a way that doesn’t match operational conditions, or the necessary information might not be fully delivered, causing instability. From the user’s perspective this often appears as “it’s connected but somehow won’t Fix,” making the root cause hard to spot.

As a countermeasure, first confirm that correction data is being received continuously, and try re-connecting or improving reception conditions. Focus not simply on whether a connection exists but whether continuous, stable reception is occurring. To aim for Fix, treat correction data quality and continuity as important as satellite conditions.

Improvement point 4: Don’t underestimate breaks in the communication environment

Closely related to receiving correction data is the stability of the communication environment. Many attribute lack of Fix solely to equipment performance or satellite conditions, but transient communication interruptions or reduced throughput are often the cause. Mountainous areas, reclaimed land, near-underground environments, and sites with many structures are particularly prone to unstable communications.

When communication is unstable, correction data may be delayed or cut off, and conditions can collapse before the solution stabilizes. The result is that the positioning never fully reaches Fix and instead fluctuates between Float and Fix. Users often see “it almost Fixes but then reverts,” which can lead to misdiagnosis.

What’s important here is not whether communication is possible but whether it remains stable during the work. Even a brief dropout can mean substantial time is required to reconverge. If you keep working during such instability to save time, you may never reach Fix and only waste time.

To improve this, stabilize the system in an area with good communication before starting work, avoid stubbornly staying at points with poor radio conditions, and try changing location slightly to check the state. Communication is invisible but directly affects Fix success, so include it in your initial checklist at the site.

Improvement point 5: Don’t rush initialization—let observation conditions settle

When Fix does not occur, users can become impatient and keep moving the device, readjusting grip, or changing settings repeatedly. However, initialization and solution convergence require some settled observation conditions. Even if improvement is underway, unstable user behavior can cause reversion to Float.

Especially at the start of operations, the device needs to ingest satellite and correction information and stabilize the solution. If you start using it while moving or wander around, conditions change repeatedly and convergence slows. Although field workers want to shorten time, taking the initial tens of seconds to a few minutes to stabilize will improve overall efficiency.

Repeated restarts or reconnections are not always effective when Fix does not occur. While sometimes necessary for anomalies, repeatedly redoing initialization can actually lengthen time to convergence. It is more reasonable to calm observation conditions in place and monitor the numerical trends before deciding.

In practice, basic actions—where to start positioning, how long to stand still, and how to hold the device steadily—affect how easily a Fix is obtained. Rather than complex theory, the basic rule of staying calm and letting conditions settle often works. When Fix is not achieved, avoid adding operations and instead focus on stabilizing conditions.

Improvement point 6: Improve receiver/antenna handling and installation state

Causes of failure to reach Fix are not limited to the environment or communications. How the receiver and antenna are handled can also affect positioning. Holding the device tilted, blocking part of the sky with your body or structures, or placing it on an unstable support can worsen reception.

In practice, aiming for portability sometimes leads to careless handling. For example, holding the device close to your body, using one hand at an angle, or placing it near metal objects are common. Each of these can negatively affect satellite reception and stabilization. Even small-seeming differences can be the dividing line between gaining a Fix or not.

Also, if the pole or terminal is shaking during positioning, solution stability tends to drop. On windy days or uneven footing, the device may move more than expected. Waiting for Fix in such conditions leaves the computation unstable and makes exiting Float difficult.

The basic improvement is to create a posture and installation that facilitate reception: maximize sky visibility, hold the device steadily, and minimize shielding and vibration. While attention often goes to communications and satellites, simply reviewing how the device is held or placed can often improve the status.

Improvement point 7: Check for discrepancies in coordinate and operation settings

If Fix is not achieved, or even when Fix is achieved the values feel unreliable, check for discrepancies in settings. Even if positioning itself is progressing, if operational settings don’t match field conditions the outcome may be different from expected. Setting issues are easy to overlook and hard for users to notice, prolonging trouble.

Examples include reference settings not matching assumptions, inappropriate work modes, required correction conditions not being applied, or saved coordinate handling differing from intent. These may not appear related to Fix success at first glance, but in practice they are strongly linked. If settings feel off, users distrust the positioning even if a Fix is obtained, and decision-making becomes difficult.

On sites where multiple people share equipment, prior users’ settings may remain. Even if you think you’re using standard conditions, another setting might be active and prevent stabilization. In busy sites, such basic checks are often skipped.

Therefore, when Fix is not obtained, stop and confirm setting consistency as well as environment and communications. If the system was stable previously but suddenly became unstable, setting changes or different operational procedures may be involved. To isolate the cause quickly, include settings in your checklist.

Improvement point 8: Avoid surrounding reflections and radio interference

Nearby reflections and interference are also non-negligible causes of failure to reach Fix. Satellite signals are very weak and susceptible to metal, glass, water surfaces, large vehicles, temporary fencing, heavy machinery, and materials. Not only direct signals but delayed reflected signals can mix in and produce errors in position computation, making the solution hard to stabilize.

In the field people may assume that open sky equals good conditions, but influences from the immediate surroundings can be significant. For example, even in a wide area, nearby large metal installations or vehicles can disturb reception. Temporary structures or fences may seem harmless but can create reflection issues.

In such environments, you may not see major problems in satellite count or communication, yet Fix may not occur or may be unstable. Because causes are hard to see, users tend to suspect operation or settings, but changing location is often the most effective remedy.

In practice, prioritize stabilizing in a location with favorable conditions rather than standing exactly at the target point. Moving slightly to avoid reflecting surfaces and then stabilizing can dramatically shorten time to Fix. Because these factors are hard to notice, make it a habit to consciously avoid them on site.

Risks of proceeding while staying in a Float solution

When numbers are displayed despite not being in Fix, there is a temptation to continue working. Under time pressure, one might judge “today the conditions are just bad” and collect points in Float. However, that decision can lead to significant rework later.

Even if a Float solution looks stable, positional fluctuation remains. Therefore, for tasks reliant on accuracy—staking out positions, as-built checks, boundary checks, overlaying with drawings—errors cannot be ignored. A value that seems fine on the day may not match when rechecked later or may be inconsistent with other points or drawings.

What is more troublesome is that data collected in Float may not appear abnormal at the time. Large outliers are obvious, but shifts of a few to a dozen centimeters are easy to miss. Yet such differences can be unacceptable for construction, as-built measurements, earthwork volumes, or layout verification.

Thus, understanding the difference between Fix and Float is not just knowledge but a matter of quality control. When Fix cannot be obtained, it is safer and more efficient to stop and investigate why the status won’t improve and to correct it before proceeding.

Practical considerations to stabilize Fix solutions

To obtain Fix solutions stably, it’s important not only to know individual causes but also to have reproducible on-site procedures. If you rely on intuition each time, results will vary by operator. Conversely, having a set order of checks lets you calmly isolate causes when Fix is not achieved.

For example: first check status in an open sky area, then verify continuity of communication and correction reception, next review surrounding reflections and mounting/holding state, and finally check settings. Even holding this simple flow makes field responses much more stable. By eliminating causes one by one, you reduce unnecessary reboots and ad-hoc operations.

Also, before starting work, take the perspective of “are there conditions today that make obtaining Fix difficult?” If there are many trees, nearby structures, weak communication, rough footing, or strong wind, then plan to allocate extra time for stabilization from the start. Anticipating problems is more effective than reacting after they occur.

A Fix solution will not simply be produced automatically by the device. Satellites, communications, corrections, environment, settings, and operations must come together for stability. Put another way, if Fix is not achieved, some condition is missing. Being able to calmly see that raises the quality of on-site decisions.

Summary

The reasons Fix is not achieved are not solely equipment-related. A lack of sky visibility, biased satellite geometry, unstable correction data, communication dropouts, movement during initialization, device handling, mismatched settings, and surrounding reflections or interference can combine to keep a solution in Float.

The difference between Fix and Float is not a display artifact but whether the accuracy is usable on site. In practice, proceeding with Float often causes misalignments and rechecks later, so the ability to judge why Fix is not achieved on the spot is essential.

If you want to better distinguish Fix and Float on site and operate high-precision positioning in an easier-to-handle way, using an iPhone-mounted GNSS high-precision positioning device like LRTK can be effective. For operators who want clearer on-site position checks and measurement workflows, the ease of understanding Fix status and operational handling is a major advantage. If you want to further incorporate high-precision positioning into practice, consider also examining simplified surveying methods using LRTK to help balance site decisions and work efficiency at a high level.