[{"data":1,"prerenderedAt":823},["ShallowReactive",2],{"knowledge-page-en-\u002Ftroubleshooting\u002Fstuck-on-float":3},{"article":4,"posts":452,"relatedPosts":453},{"id":5,"title":6,"author":7,"body":8,"category":438,"cover":439,"description":440,"extension":441,"meta":442,"navigation":443,"path":444,"publishedAt":445,"relatedArticles":446,"seo":448,"stem":449,"updatedAt":450,"__hash__":451},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Fstuck-on-float.md","Why am I stuck on Float and not reaching Fix?","Wilko",{"type":9,"value":10,"toc":426},"minimark",[11,21,26,29,63,67,108,112,147,151,185,189,220,224,259,263,297,301,304,420],[12,13,17],"card",{"additionalstyles":14,"color":15,"title":16},"mt-[60px]","primary","Float is normal for the first 10–60 seconds",[18,19,20],"p",{},"Float is always the step before Fix. In good conditions — open sky, nearby reference station and stable corrections — Float lasts 10–60 seconds. If it lasts longer than 3 minutes without reaching Fix, something specific is preventing ambiguity resolution. This page helps you find what.",[22,23,25],"h2",{"id":24},"two-minute-checklist","Two-minute checklist",[18,27,28],{},"Run through these before diving into the causes. They resolve most cases immediately.",[12,30,33],{"additionalstyles":14,"color":31,"title":32},"green","Quick Float diagnostic",[34,35,36,40,43,51,54,57,60],"ul",{},[37,38,39],"li",{},"Are you outside with a clear sky view? Float indoors or under trees is expected.",[37,41,42],{},"Is the NTRIP connection active with a stable bytes-per-second value above zero?",[37,44,45,46,50],{},"For DJI drones, are you using the MSM5 mountpoint ",[47,48,49],"code",{},"RTCM3_NL_MSM5","?",[37,52,53],{},"Are you seeing at least 15 satellites with good SNR?",[37,55,56],{},"Is PDOP below 4?",[37,58,59],{},"Have you been stationary for at least 60 seconds?",[37,61,62],{},"Are GPS, GLONASS, Galileo and BeiDou all enabled?",[22,64,66],{"id":65},"cause-1-wrong-mountpoint","Cause 1 — Wrong mountpoint",[68,69,74,77,80],"cause-card",{"additionalstyles":14,"frequency":70,"icon":71,"level":72,"title":73},"Very common for DJI users","icons\u002FSatellite.svg","5","MSM4 mountpoint used with a DJI drone",[18,75,76],{},"This is the single most common cause of persistent Float on DJI drones. DJI's RTK processing engine requires Doppler observations to resolve integer ambiguities. Doppler is included in MSM5 and MSM7 but not in MSM4. When a DJI drone connects to an MSM4 mountpoint, corrections flow normally and the connection appears successful — but Fix never arrives because the Doppler data needed for DJI's initialisation is absent.",[18,78,79],{},"The symptom is unmistakable: NTRIP connected, bytes flowing, stable Float for many minutes, never converging to Fix regardless of sky conditions.",[81,82,83,98,101],"ol",{},[37,84,85,86,90,91,94,95,97],{},"In DJI Pilot, go to ",[87,88,89],"strong",{},"RTK Settings → Custom Network RTK",". Change the mountpoint from ",[47,92,93],{},"RTCM3_NL"," to ",[47,96,49],{},".",[37,99,100],{},"Disconnect and reconnect. DJI should reach Fix within 60 seconds in open sky.",[37,102,103,104,107],{},"For long-baseline DJI flights, use ",[47,105,106],{},"RTCM3_NL_VRS"," instead. The short effective baseline improves Fix stability.",[22,109,111],{"id":110},"cause-2-corrections-not-reaching-the-receiver","Cause 2 — Corrections not reaching the receiver",[68,113,118,121],{"additionalstyles":14,"frequency":114,"icon":115,"level":116,"title":117},"Common","icons\u002FData.svg","4","NTRIP stream connected but delivering no useful data",[18,119,120],{},"There are two subtle ways corrections can appear to flow but not actually help the receiver: the stream contains no corrections for the satellites your receiver tracks, or the connection drops and reconnects repeatedly. Every dropout resets the ambiguity-resolution timer to zero.",[81,122,123,129,135,141],{},[37,124,125,128],{},[87,126,127],{},"Verify bytes per second is non-zero and stable."," The counter should show a steady 500–2,000 bytes\u002Fsec. If it repeatedly falls to zero, fix the internet connection first.",[37,130,131,134],{},[87,132,133],{},"Check the RTCM message types."," You need at minimum MSM4 messages such as 1074, 1084, 1094 and 1124, or equivalent. Legacy-only 1004\u002F1012 data may not match the receiver.",[37,136,137,140],{},[87,138,139],{},"Check VRS GGA transmission."," If you use a VRS mountpoint without GGA enabled, the server may stream nothing. Enable GGA and reconnect.",[37,142,143,146],{},[87,144,145],{},"Try a dedicated hotspot."," Phone tethering can be less stable. A dedicated hotspot often resolves Float caused by repeated stream interruptions.",[22,148,150],{"id":149},"cause-3-environment-and-obstructions","Cause 3 — Environment and obstructions",[68,152,156,159],{"additionalstyles":14,"frequency":153,"icon":154,"level":72,"title":155},"Very common","icons\u002FTree.svg","Obstructions or multipath blocking ambiguity resolution",[18,157,158],{},"Ambiguity resolution requires sustained, clean carrier-phase measurements from multiple satellites simultaneously. Trees, buildings, vehicles and terrain can block or reflect signals and interrupt the continuous tracking required for Fix. Even partial canopy can scatter L1\u002FL2 signals enough to keep a receiver in Float.",[81,160,161,167,173,179],{},[37,162,163,166],{},[87,164,165],{},"Move to the most open spot available."," Even five metres can make a significant difference. The antenna needs a clean hemisphere of sky above 10–15°.",[37,168,169,172],{},[87,170,171],{},"Stand still."," Movement during initialisation compounds the problem. Stop walking or driving and wait at least 60 seconds.",[37,174,175,178],{},[87,176,177],{},"Lower the elevation mask to 10°."," Where supported, a lower mask allows useful low-angle satellites to improve geometry.",[37,180,181,184],{},[87,182,183],{},"Move away from metal structures."," Metal roofs, silos, greenhouse frames and vehicles create strong multipath. Keep at least ten metres away.",[22,186,188],{"id":187},"cause-4-baseline-too-long","Cause 4 — Baseline too long",[68,190,195,198],{"additionalstyles":14,"frequency":191,"icon":192,"level":193,"title":194},"Moderate","icons\u002FRuler.svg","3","More than 30 km from the nearest reference station",[18,196,197],{},"At long baselines, ionospheric and tropospheric errors at the reference station and rover diverge. Corrections from the distant station no longer describe the atmosphere at your location accurately enough for the receiver to resolve integer ambiguities with confidence.",[81,199,200,208,214],{},[37,201,202,205,206,97],{},[87,203,204],{},"Switch to the VRS mountpoint."," VRS generates a virtual reference station around 1–2 km from you. Enable GGA and connect to ",[47,207,106],{},[37,209,210,213],{},[87,211,212],{},"Check the sourcetable distance."," If the nearest physical station is more than 25 km away, VRS is normally the better choice.",[37,215,216,219],{},[87,217,218],{},"Use a dual-frequency receiver."," Single-frequency receivers are usually limited to baselines of around 10 km before ionospheric errors prevent Fix.",[22,221,223],{"id":222},"cause-5-ionospheric-disturbance","Cause 5 — Ionospheric disturbance",[68,225,230,233],{"additionalstyles":14,"frequency":226,"icon":227,"level":228,"title":229},"Periodic — peaks during solar maximum","icons\u002FSun.svg","2","High solar activity disrupting carrier-phase signals",[18,231,232],{},"The ionosphere delays satellite signals by an amount that varies with solar activity. During geomagnetic storms and solar maximum periods, these delays can change rapidly. This can stop ambiguity resolution even with short baselines and good sky conditions.",[81,234,235,241,247,253],{},[37,236,237,240],{},[87,238,239],{},"Work early morning or evening."," Ionospheric activity is typically lowest during the first two hours after sunrise and later in the evening.",[37,242,243,246],{},[87,244,245],{},"Switch to VRS."," Network-wide ionospheric modelling partially compensates for elevated ionospheric noise.",[37,248,249,252],{},[87,250,251],{},"Check space weather."," A Kp index above 5 often causes RTK problems. Postponing work until the storm passes may be the only reliable option.",[37,254,255,258],{},[87,256,257],{},"Use a triple-frequency receiver."," L5 signals are more robust to ionospheric noise than L1\u002FL2 and can maintain Fix in more difficult conditions.",[22,260,262],{"id":261},"cause-6-receiver-or-software-settings","Cause 6 — Receiver or software settings",[68,264,268,271],{"additionalstyles":14,"frequency":265,"icon":266,"level":228,"title":267},"Less common but easy to fix","icons\u002FCog.svg","Conservative defaults preventing ambiguity resolution",[18,269,270],{},"Default receiver settings are designed to be safe across a wide range of conditions. In challenging environments, those defaults can be too conservative and prevent Fix even when it would be achievable with a small adjustment.",[81,272,273,279,285,291],{},[37,274,275,278],{},[87,276,277],{},"Switch ambiguity resolution to Fix-and-hold."," In Emlid or RTKLIB, this maintains a resolved integer solution through brief disturbances instead of re-initialising continuously.",[37,280,281,284],{},[87,282,283],{},"Enable all constellations."," GPS, GLONASS, Galileo and BeiDou together provide much more redundancy than GPS alone.",[37,286,287,290],{},[87,288,289],{},"Reduce update rate to 1–5 Hz."," In a weak environment, reducing the rate gives the RTK engine more averaging time per epoch.",[37,292,293,296],{},[87,294,295],{},"Set the minimum elevation mask to 10°."," Higher masks can exclude useful satellites and weaken satellite geometry.",[22,298,300],{"id":299},"device-specific-fixes","Device-specific fixes",[18,302,303],{},"Select your device for targeted advice:",[305,306,309,338,365,390,405],"device-tabs",{"additionalstyles":14,"default-tab":307,"items":308},"Emlid","Emlid|DJI|Trimble|SW Maps|u-blox \u002F DIY",[310,311,312,326,335],"device-tab",{"name":307},[18,313,314,317,318,321,322,325],{},[87,315,316],{},"Most effective fix for Emlid stuck on Float:"," go to ",[87,319,320],{},"Settings → GNSS settings → Ambiguity resolution"," and change from Continuous to ",[87,323,324],{},"Fix-and-hold",". This single setting resolves persistent Float in challenging environments for many Emlid users.",[18,327,328,329,331,332,97],{},"Also verify that all constellations are enabled, the elevation mask is 10–15° and NTRIP bytes\u002Fsec is above zero. For a long baseline, switch to ",[47,330,106],{}," and enable ",[87,333,334],{},"Send GGA to caster",[18,336,337],{},"Firmware updates can reset GNSS settings to their defaults. Re-check constellation and ambiguity settings after every update.",[310,339,341,353,356,362],{"name":340},"DJI",[18,342,343,346,347,349,350,352],{},[87,344,345],{},"DJI stuck on Float is almost always MSM4 instead of MSM5."," Change the mountpoint to ",[47,348,49],{}," in DJI Pilot under ",[87,351,89],{},", then disconnect and reconnect.",[18,354,355],{},"If you already use MSM5, make sure the drone is outdoors with GPS lock before connecting. DJI may not send GGA indoors, which can prevent the server from streaming corrections.",[18,357,358,359,361],{},"For long-baseline flights beyond 30 km, try ",[47,360,106],{},". DJI handles VRS well and the shorter effective baseline improves Fix stability.",[18,363,364],{},"On the DJI M300 and Matrice 350, also check that the RTK antenna is firmly seated and its cable is undamaged.",[310,366,368,378,384,387],{"name":367},"Trimble",[18,369,370,373,374,377],{},[87,371,372],{},"For Trimble stuck on Float",", first verify that the data link is active under ",[87,375,376],{},"Instrument → Receiver Status → Data Link",". The bytes counter must be incrementing.",[18,379,380,381,383],{},"For long-baseline work, switch to ",[47,382,106],{},". Trimble Access sends GGA automatically when NTRIP is active.",[18,385,386],{},"If Float persists in good conditions, check PDOP in the receiver status. Trimble's default PDOP mask is 6.0; above this value, Fix is suppressed by design.",[18,388,389],{},"The Trimble R10 works correctly with MSM4. If an R10 remains on Float, investigate the environment or baseline rather than the mountpoint format.",[310,391,393,399,402],{"name":392},"SW Maps",[18,394,395,398],{},[87,396,397],{},"SW Maps stuck on Float usually means the external receiver is the bottleneck."," SW Maps displays the solution supplied by the connected receiver.",[18,400,401],{},"Check the receiver's status in its own app. If the receiver shows Fix while SW Maps still shows Float, disconnect and reconnect the Bluetooth link to refresh the NMEA solution.",[18,403,404],{},"A smartphone's internal single-frequency GNSS chip rarely reaches Fix. For centimetre accuracy, connect a multi-band external receiver.",[310,406,408,414,417],{"name":407},"u-blox \u002F DIY",[18,409,410,413],{},[87,411,412],{},"A u-blox ZED-F9P normally reaches Fix reliably within a 10–30 km baseline."," Beyond that, ionospheric decorrelation can prevent Fix without VRS.",[18,415,416],{},"In RTKLIB-based software, select Fix-and-hold, enable all constellations and use a 10° elevation mask. In U-Center, verify that RTCM3 input is configured on the correct serial port.",[18,418,419],{},"A common DIY setup error is sending corrections to UART2 while the application expects data on UART1. Verify that the correction port matches the physical cabling.",[12,421,423],{"additionalstyles":14,"color":31,"title":422},"Still on Float after all of the above?",[18,424,425],{},"Describe the exact situation to the AI: your device, mountpoint, satellite count, PDOP, baseline distance, sky conditions and how long you have been waiting. The more specific you are, the more targeted the answer.",{"title":427,"searchDepth":428,"depth":428,"links":429},"",2,[430,431,432,433,434,435,436,437],{"id":24,"depth":428,"text":25},{"id":65,"depth":428,"text":66},{"id":110,"depth":428,"text":111},{"id":149,"depth":428,"text":150},{"id":187,"depth":428,"text":188},{"id":222,"depth":428,"text":223},{"id":261,"depth":428,"text":262},{"id":299,"depth":428,"text":300},"troubleshooting","Troubleshooting\u002FWebP\u002Fwhy-am-i-stuck-on-float-and-not-reaching-fix.webp","Float that never becomes Fix is the most common RTK problem in the field. Most cases are caused by one of seven things — and most of them are resolved in under two minutes once you know which one it is. Work through this guide from the top.","md",{},true,"\u002Fen\u002Ftroubleshooting\u002Fstuck-on-float","2026-07-24",[447],"\u002Fen\u002Flearn\u002Ffloat-vs-fix",{"title":6,"description":440},"en\u002Ftroubleshooting\u002Fstuck-on-float",null,"cZuzVDxMmVc2t9_jfIEzEmwmUVVTUPbWnughCbX8Y_Y",[],[454],{"id":455,"title":456,"author":7,"body":457,"category":814,"cover":815,"description":816,"extension":441,"meta":817,"navigation":443,"path":447,"publishedAt":445,"relatedArticles":818,"seo":820,"stem":821,"updatedAt":450,"__hash__":822},"knowledge_en\u002Fen\u002Flearn\u002Ffloat-vs-fix.md","What is the difference between Float and Fix?",{"type":9,"value":458,"toc":806},[459,463,514,518,521,524,527,563,566,569,573,576,615,619,750,754,757,784,788,791,794,800],[22,460,462],{"id":461},"float-vs-fix-at-a-glance","Float vs Fix at a glance",[464,465,466,491],"cards",{"additionalstyles":14},[12,467,471],{"additionalstyles":468,"color":469,"title":470},"h-full","orange","Float — Accuracy: 10 cm–1 m horizontal",[34,472,473,476,479,482,485,488],{},[37,474,475],{},"Corrections received but not fully resolved",[37,477,478],{},"Ambiguities treated as real numbers, not integers",[37,480,481],{},"Position jumps of 10–50 cm are normal",[37,483,484],{},"Never adequate for precision survey",[37,486,487],{},"Often a stepping stone toward Fix",[37,489,490],{},"Can look like Fix on some displays",[12,492,494],{"additionalstyles":468,"color":31,"title":493},"Fix — Accuracy: 1–3 cm horizontal, 2–5 cm vertical",[34,495,496,499,502,505,508,511],{},[37,497,498],{},"Carrier phase ambiguities fully resolved to integers",[37,500,501],{},"Position is stable and repeatable",[37,503,504],{},"Centimetre accuracy maintained at speed",[37,506,507],{},"Required for precision survey and stakeout",[37,509,510],{},"Takes 10–60 seconds in good conditions",[37,512,513],{},"Shown in green on most field software",[22,515,517],{"id":516},"what-makes-fix-different-ambiguity-resolution","What makes Fix different — ambiguity resolution",[18,519,520],{},"To understand Float and Fix you need to understand one concept: carrier phase ambiguity. It is the reason RTK can achieve centimetre accuracy at all — and the reason Float cannot.",[18,522,523],{},"GNSS receivers measure position in two ways. The simpler method is pseudorange — measuring the travel time of a satellite signal to estimate distance. Pseudorange gives accuracy of 1–3 metres. The more precise method is carrier phase — measuring the phase of the satellite's radio wave at the receiver antenna. The carrier wave has a wavelength of about 19 cm (for GPS L1). By tracking how many whole wavelengths fit between the satellite and the receiver, and precisely measuring the fractional part, the receiver can measure distance to millimetre precision.",[18,525,526],{},"The problem: the receiver knows the fractional part of the carrier phase precisely, but it does not know how many whole wavelengths there are between it and the satellite. This unknown integer number is called the carrier phase ambiguity — or simply the integer ambiguity.",[528,529,533,550],"compare-table",{"additionalstyles":14,"items":530,"label":531,"winner":532},"Float|Fix","Float and Fix ambiguity comparison","Fix",[534,535,537,544],"compare-row",{"title":536},"Carrier phase ambiguity",[538,539,541],"compare-cell",{"status":540},"negative",[18,542,543],{},"The integer cycle count is still unknown and treated as a real-valued estimate.",[538,545,547],{"status":546},"positive",[18,548,549],{},"The integer cycle count has been confirmed as a specific whole number.",[534,551,553,558],{"title":552},"Position accuracy",[538,554,555],{"status":540},[18,556,557],{},"10 cm–1 m. The fractional phase is measured, but the unresolved cycle count limits accuracy.",[538,559,560],{"status":546},[18,561,562],{},"Centimetre precision. The resolved cycle count unlocks the precise fractional measurement.",[18,564,565],{},"Resolving the integer ambiguity is what RTK does. Using corrections from the reference station — which has its own precisely known position — the rover can cross-check its carrier phase measurements against the reference and mathematically determine the correct integer values. When the receiver is confident it has the right integers for all tracked satellites, it declares RTK Fixed.",[18,567,568],{},"Float means the receiver is still working on this. It has an estimate of the integers — good enough to give sub-metre accuracy — but not yet confident enough to fix them to specific integers. Float accuracy depends on how good the estimate is: anywhere from 10 cm to 1 m, with occasional larger jumps.",[22,570,572],{"id":571},"the-full-solution-progression","The full solution progression",[18,574,575],{},"When you connect to an NTRIP service and power up in the field, your receiver moves through several solution types before reaching Fix.",[577,578,579,587,594,601,608],"stepper",{"additionalstyles":14},[580,581,584],"stepper-item",{"marker":582,"title":583},"—","No fix — Accuracy: none",[18,585,586],{},"The receiver has no satellite lock and no valid position. It is still acquiring signals. This usually takes 15–60 seconds after power-on outdoors.",[580,588,591],{"marker":589,"title":590},"S","Single — Accuracy: 2–5 m",[18,592,593],{},"The receiver has satellite lock and a valid position, but no corrections are applied yet. It uses pseudorange only. This is the type of position reported by standard GPS apps on your phone.",[580,595,598],{"marker":596,"title":597},"D","DGPS \u002F SBAS — Accuracy: 0.3–1 m",[18,599,600],{},"Differential corrections are applied, but only to pseudorange measurements. It is better than Single, but not accurate enough for precision work. This can appear briefly when NTRIP corrections first arrive.",[580,602,605],{"marker":603,"title":604},"FL","Float — Accuracy: 10 cm–1 m",[18,606,607],{},"Carrier phase corrections are applied, but integer ambiguities are not yet resolved. The position is significantly better than Single but not precise enough for survey work. Float is often a transitional state lasting 10–60 seconds before Fix.",[580,609,612],{"marker":610,"title":611},"FX","Fixed — Accuracy: 1–3 cm horizontal, 2–5 cm vertical",[18,613,614],{},"Integer ambiguities are resolved and full RTK accuracy is achieved. This is the solution type required for precision survey, stakeout, machine guidance and drone mapping with ground control points.",[22,616,618],{"id":617},"which-solution-is-good-enough-for-what","Which solution is good enough for what",[528,620,623,639,657,672,688,703,719,734],{"additionalstyles":14,"items":621,"label":622,"winner":532},"Single|Float|Fix","Suitable RTK solution per application",[534,624,626,631,635],{"title":625},"Rough navigation — Finding a plot or general location",[538,627,628],{"status":546},[18,629,630],{},"Good enough",[538,632,633],{"status":546},[18,634,630],{},[538,636,637],{"status":546},[18,638,630],{},[534,640,642,647,652],{"title":641},"Drone mapping — Direct georeferencing without GCPs",[538,643,644],{"status":540},[18,645,646],{},"No",[538,648,649],{"status":540},[18,650,651],{},"Marginal",[538,653,654],{"status":546},[18,655,656],{},"Required",[534,658,660,664,668],{"title":659},"GCP collection for drone mapping",[538,661,662],{"status":540},[18,663,646],{},[538,665,666],{"status":540},[18,667,646],{},[538,669,670],{"status":546},[18,671,656],{},[534,673,675,679,683],{"title":674},"Precision agriculture — Auto-steer with 2–5 cm row guidance",[538,676,677],{"status":540},[18,678,646],{},[538,680,681],{"status":540},[18,682,651],{},[538,684,685],{"status":546},[18,686,687],{},"Preferred",[534,689,691,695,699],{"title":690},"Survey — Topographic surface mapping",[538,692,693],{"status":540},[18,694,646],{},[538,696,697],{"status":540},[18,698,646],{},[538,700,701],{"status":546},[18,702,656],{},[534,704,706,710,714],{"title":705},"Survey — Cadastral or legal property boundaries",[538,707,708],{"status":540},[18,709,646],{},[538,711,712],{"status":540},[18,713,646],{},[538,715,716],{"status":546},[18,717,718],{},"Required + verification",[534,720,722,726,730],{"title":721},"Stakeout to 1 cm",[538,723,724],{"status":540},[18,725,646],{},[538,727,728],{"status":540},[18,729,646],{},[538,731,732],{"status":546},[18,733,656],{},[534,735,737,741,746],{"title":736},"Machine control — Earthworks",[538,738,739],{"status":540},[18,740,646],{},[538,742,743],{"status":546},[18,744,745],{},"Sometimes",[538,747,748],{"status":546},[18,749,656],{},[22,751,753],{"id":752},"how-to-get-from-float-to-fix-faster","How to get from Float to Fix faster",[18,755,756],{},"Float is a transitional state. In good conditions it lasts 10–30 seconds. In challenging conditions it can persist indefinitely. These measures help most:",[464,758,759,764,768,772,776,780],{"additionalstyles":14},[760,761],"cards-item",{"text":762,"title":763},"Ambiguity resolution requires a strong, stable signal from many satellites simultaneously. Even partial canopy cover significantly slows initialisation.","Go outside with a clear sky view",[760,765],{"text":766,"title":767},"The RTK engine converges faster when the antenna is stationary. Once Fixed, you can move normally. Collecting data while still in Float can delay Fix.","Stand still during initialisation",[760,769],{"text":770,"title":771},"Shorter effective baselines make ambiguity resolution faster and more reliable. Beyond 20 km from a physical station, switch to VRS and enable GGA.","Use a VRS mountpoint",[760,773],{"text":774,"title":775},"More satellites provide more measurement redundancy. Adding GLONASS, Galileo and BeiDou can halve Float-to-Fix time compared with GPS-only.","Enable all satellite constellations",[760,777],{"text":778,"title":779},"Verify that bytes per second is non-zero. A dropped and reconnected correction stream resets initialisation and can leave the receiver stuck on Float.","Check the NTRIP connection",[760,781],{"text":782,"title":783},"Above 4, satellite geometry is poor and ambiguity resolution may not converge. Wait for the geometry window to improve, typically within 15–30 minutes.","Check PDOP",[22,785,787],{"id":786},"false-fix-the-hidden-danger","False Fix — the hidden danger",[18,789,790],{},"The most dangerous scenario in RTK is a false Fix — the receiver declares Fixed but has resolved the ambiguities to the wrong integers. The position looks centimetre-precise and stable, but it is wrong by one or more carrier wavelengths (19 cm per L1 cycle).",[18,792,793],{},"False Fix produces errors of exactly one or more multiples of the carrier wavelength — 19 cm, 38 cm, 57 cm and so on. It is more common at long baselines, in high multipath environments and during solar storms when ionospheric noise is high.",[12,795,797],{"additionalstyles":14,"color":469,"title":796},"How to detect a false Fix",[18,798,799],{},"Always verify on a known control point at the start of any precision survey. Set up over a point with published coordinates and compare your measured position with the known values. A discrepancy of exactly around 19 cm, 38 cm or 57 cm in any direction strongly indicates a false Fix. Disconnect, move to open sky, reconnect and re-initialise before continuing.",[12,801,803],{"additionalstyles":14,"color":15,"title":802},"Fix quality indicator — ratio",[18,804,805],{},"Many receivers and field software applications report a Fix quality ratio alongside the solution type. A ratio above 3.0 indicates high confidence. A ratio between 1.5 and 3.0 means the Fix is tentative, so verify it on known points. A ratio below 1.5 may indicate that the receiver should not have declared Fix at all.",{"title":427,"searchDepth":428,"depth":428,"links":807},[808,809,810,811,812,813],{"id":461,"depth":428,"text":462},{"id":516,"depth":428,"text":517},{"id":571,"depth":428,"text":572},{"id":617,"depth":428,"text":618},{"id":752,"depth":428,"text":753},{"id":786,"depth":428,"text":787},"learn","learn\u002Ffloat-vs-fix.webp","Float and Fix are the two RTK solution types. They look similar on a status screen — both show a position with corrections applied — but the accuracy difference between them is enormous. Fix is centimetres. Float is decimetres to metres. Never collect survey data at Float.",{},[819],"\u002Fen\u002Flearn\u002Fwhat-is-ntrip",{"title":456,"description":816},"en\u002Flearn\u002Ffloat-vs-fix","rVrcpStYIvAqW_8pcTB5DaAOMLXiCzzea9VNPOocA4Y",1787304715463]