No. An RTK integer-fixed status means that the positioning engine has accepted an integer ambiguity solution under its documented criteria. It does not independently verify the reference coordinates, coordinate transformation, antenna-height correction or final position against truth. A correctly fixed relative solution can still be delivered in the wrong place. Conversely, accepting the wrong integers is a different failure from applying the right baseline to incorrect reference information.
For an integration or acceptance test, distinguish three questions: what the status field actually means, whether the positioning configuration is correct, and whether the delivered coordinates agree with suitable independent evidence. A green “Fixed” indicator answers only the first question within the receiver's specified meaning.
Decode the field before interpreting the fix
Carrier observations contain initially unknown cycle offsets. Integer ambiguity resolution estimates and accepts integer-valued parameters in an appropriate measurement model; it is not a check of a surveyed control point. The pseudorange and carrier-phase guide explains the measurement background.
Field names are not interchangeable. In NovAtel OEM7 BESTPOS documentation, NARROW_INT identifies a multi-frequency RTK solution with narrow-lane integer ambiguities resolved. FIXEDPOS instead means that the position was fixed through a position command or averaging. It is not another spelling of an RTK integer fix. BESTPOS also separates solution status from position type. These are NovAtel definitions, not ResiNav output fields or universal labels.
Record the actual message, firmware, solution type, validity state and epoch. If a display combines several underlying states into “Fixed,” obtain its documented mapping. A status copied from a different solution or an earlier epoch cannot validate the position being evaluated now.
Separate wrong integers from wrong coordinate delivery
An incorrect integer fix occurs when the accepted ambiguity values differ from the appropriate true integer values for that model and observation arc. Possible ambiguity errors do not imply a position offset equal to one wavelength: several observations, geometry, constraints and other estimated states determine the coordinate effect. Neither an offset's size nor its resemblance to a wavelength multiple identifies the cause.
Reference and setup errors are separate. NOAA NGS's single-base real-time positioning guidelines describe forming rover coordinates from a baseline and base coordinates, with antenna-reference and height handling. The absolute coordinate result therefore needs correct reference information as well as a useful relative estimate. The document concerns classical single-base surveying; its numerical field procedures are not universal limits for every network or moving platform.
For a hypothetical coordinate-assembly example, hold an estimated baseline vector fixed and express both positions in the same local east–north–up Cartesian frame:
rover position = base position + estimated baseline.
If the supplied base coordinate has an assumed error of (+0.30, −0.40, +0.20) m, that assembly transfers the same vector to the rover. Its horizontal magnitude is 0.50 m and its three-dimensional magnitude is about 0.539 m. Repeating the same baseline calculation does not remove the reference offset. This isolates coordinate assembly; it is not a complete reprocessing model of incorrect base metadata or receiver performance.
Height has another reference point. In a second hypothetical vertical calculation, an antenna reference point is correctly positioned at 100.00 m above the chosen vertical reference. The mark is 2.00 m below it. Subtracting an incorrectly entered 1.80 m gives 98.20 m rather than 98.00 m. The resulting +0.20 m mark-height error does not require a wrong integer solution.
A height-reference mismatch is a separate delivery issue: see how ellipsoidal height, orthometric height and geoid separation relate before applying a vertical conversion to a receiver output.
Trimble's Siteworks calibration guidance separately identifies calibration, antenna type and height, and base location as setup issues. It also warns that a calibration can have small residuals while its control arrangement creates problems elsewhere. Its software workflow is a vendor example, not a configuration attributed to ResiNav.
Why agreement is useful but not sufficient
Two occupations agreeing closely show repeatability under the conditions shared by those occupations. If both use the same incorrect reference coordinate, transformation or antenna height, their agreement can coexist with the same absolute error. Likewise, evaluating a calibration only on the points used to fit it is weaker than checking separate control that was not used in that fit.
Small measurement residuals show consistency with the fitted model, not independent coordinate truth. A low standard deviation is also conditional on the estimator's assumptions and accepted solution. The separate measurement-residual guide explains why errors can be absorbed into estimated states. Do not count these three indicators—repeatability, residuals and reported uncertainty—as three independent truth checks merely because they appear in different display panels.
Ambiguity acceptance statistics have their own definitions. Teunissen and Verhagen's original ratio-test analysis explains limitations of a single fixed critical value across different models. A ratio is not a universal probability that this position is correct. Use the receiver's documented statistic and validation method; there is no threshold supplied here for all receivers or environments.
Choose checks that challenge different assumptions
| Check | What it can examine | What can remain shared or untested |
|---|---|---|
| Measure an independently established control point in the required frame | End-to-end coordinates, including relevant transformation and reference-point handling | Control uncertainty, identification errors, and performance away from that place and time |
| Repeat after a documented new initialization | Whether a separately formed solution agrees with the earlier result | The same base, atmosphere, reflections, calibration and height errors can persist |
| Compare with a suitable separate reference method | Errors not exposed by internal status or repeatability alone | Shared GNSS corrections, common control, reference uncertainty, time alignment and lever-arm errors can compromise independence |
Trimble Access's versioned RTK initialization guidance recommends periodically remeasuring previously measured points with a new initialization. This is a useful repeat check, not a statement that any reset creates statistically independent evidence. Its reset options are implementation-specific and are not operating instructions for another receiver.
A surveyed control point must have known provenance, a compatible frame and epoch, and uncertainty suitable for the test. A point created by the same unverified setup is not automatically independent control. Where a local transformation is fitted, include checks not used to determine that transformation and consider their spatial distribution.
For a moving platform, compare the same physical reference point at matched epochs. A second receiver sharing the same correction source and environment may reveal a disagreement, but agreement can still conceal common error. A reference method needs an uncertainty and alignment budget; “independent” describes which errors it avoids sharing, not simply a second instrument's brand.
Use failed checks to narrow the investigation
If separate initializations disagree, retain both results and their status, epochs, correction source and setup. The disagreement warrants investigation; it does not by itself prove which run had wrong integers. Changes in environment, mounting, reference configuration or correction delivery can also matter.
If repeat results agree but independent control shows a stable offset, audit the coordinate frame and epoch, base coordinates, transformation, vertical reference, antenna reference point and height application. That pattern makes shared setup errors worth testing; it does not rule out other causes or prove that every ambiguity is correct. Check horizontal and vertical components separately before applying an empirical correction.
For an acceptance decision, define the required coordinate frame, reference point, operating conditions, permissible errors and how unavailable or non-fixed intervals will be reported. Compare the coordinate errors against the chosen reference, not just the percentage of time displaying Fixed. A test limited to fixed epochs answers a conditional question and should retain its excluded intervals separately.
Buy the missing evidence or function
For procurement, distinguish an RTK-capable configuration from a demonstrated acceptance result. Ask for documented status meanings and test evidence appropriate to the delivered coordinate output. A setup investigation may require control, calibration work or a better reference method rather than replacement hardware. A correction-delivery problem may require a service or interface change. A verified reception-interference problem is a separate reason to evaluate RF protection.
The RTK and anti-jamming purchasing guide keeps those functions separate, while the receiver evaluation guide provides the broader acceptance context. This article assigns no RTK status, ambiguity-validation algorithm or diagnostic output to a ResiNav product. Its practical conclusion is specific: Fixed is a solution-state observation; position correctness needs reference and configuration evidence as well.
NEXT STEP
Turn available platform information into an engineering review.
Use the Technology centre to frame the discussion, review relevant application scenarios, then send the available platform and receiver details for confirmation.