[{"data":1,"prerenderedAt":1759},["ShallowReactive",2],{"knowledge-page-en-\u002Ftroubleshooting":3},{"article":4,"posts":5,"relatedPosts":1758},null,[6,502,916,1358],{"id":7,"title":8,"author":9,"body":10,"category":488,"cover":489,"description":490,"extension":491,"meta":492,"navigation":493,"path":494,"publishedAt":495,"relatedArticles":496,"seo":499,"stem":500,"updatedAt":4,"__hash__":501},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Fntrip-connection-failed.md","Cannot connect to NTRIP caster — what now?","Yuri",{"type":11,"value":12,"toc":477},"minimark",[13,18,22,72,76,100,104,146,160,164,226,231,235,270,274,277,356,360,471],[14,15,17],"h2",{"id":16},"quick-diagnostic-checklist","Quick diagnostic checklist",[19,20,21],"p",{},"Before diving into causes, run through these five checks. They resolve the majority of NTRIP connection failures.",[23,24,28],"card",{"additionalstyles":25,"color":26,"title":27},"mt-[60px]","green","Quick NTRIP diagnostic",[29,30,31,39,54,60,66],"ol",{},[32,33,34,38],"li",{},[35,36,37],"strong",{},"Internet working?"," Open a browser and load any website. If it fails, fix your connection first.",[32,40,41,44,45,49,50,53],{},[35,42,43],{},"Correct host and port?"," Port must be ",[46,47,48],"code",{},"2101",". Host must match exactly — no typos and no ",[46,51,52],{},"http:\u002F\u002F"," prefix.",[32,55,56,59],{},[35,57,58],{},"Credentials correct?"," Username and password are case-sensitive. Copy-paste rather than typing.",[32,61,62,65],{},[35,63,64],{},"Mountpoint exists?"," Load the sourcetable from the server to confirm the mountpoint name.",[32,67,68,71],{},[35,69,70],{},"GGA enabled?"," Required for VRS mountpoints. It must be enabled in your NTRIP client.",[14,73,75],{"id":74},"cause-1-no-internet-connection","Cause 1 — No internet connection",[77,78,83,86],"cause-card",{"additionalstyles":25,"frequency":79,"icon":80,"level":81,"title":82},"Most common cause on first setup","icons\u002FData.svg","5","Device has no data connection",[19,84,85],{},"NTRIP corrections travel over a standard internet connection. If your device cannot reach the internet, it cannot reach the NTRIP server — regardless of how correctly everything else is configured.",[29,87,88,91,94,97],{},[32,89,90],{},"Open a browser on the same device and navigate to any website. If it does not load, resolve the connectivity issue before proceeding.",[32,92,93],{},"If you use a receiver with a built-in SIM card (Emlid RS3, RS4 or some Trimble units), verify the SIM has an active data plan and signal bars are showing.",[32,95,96],{},"If you use a phone hotspot, check that the device connecting to the hotspot actually has internet access through it — not just a Wi-Fi connection to the hotspot.",[32,98,99],{},"In areas with weak cellular signal, switch between 4G and 3G modes. A stable 3G connection is better than an unstable 4G one for NTRIP streaming.",[14,101,103],{"id":102},"cause-2-port-2101-is-blocked","Cause 2 — Port 2101 is blocked",[77,105,110,116],{"additionalstyles":25,"frequency":106,"icon":107,"level":108,"title":109},"Common on corporate networks and some mobile carriers","icons\u002FLock.svg","4","Firewall or carrier blocking TCP port 2101",[19,111,112,113,115],{},"NTRIP uses TCP port ",[46,114,48],{},". Some corporate Wi-Fi networks and mobile carriers block outbound connections on non-standard ports. If you have general internet access but cannot reach the NTRIP server, port blocking is likely.",[29,117,118,124,130,136],{},[32,119,120,123],{},[35,121,122],{},"Switch networks."," If you are on corporate Wi-Fi, switch to mobile data. If you are on mobile data, try a different carrier's SIM or a Wi-Fi network at home.",[32,125,126,129],{},[35,127,128],{},"Use a personal hotspot."," Create a hotspot from your phone's mobile data connection and connect your field device to it. This bypasses most corporate network restrictions.",[32,131,132,135],{},[35,133,134],{},"Ask IT to open the port."," On a corporate network, request that TCP port 2101 outbound is opened for your device. This is a standard NTRIP requirement.",[32,137,138,141,142,145],{},[35,139,140],{},"Test the port directly."," On a computer, open a terminal and run ",[46,143,144],{},"telnet ntrip.rtksub.com 2101",". If the connection opens, the port is accessible. If it times out, the port is blocked.",[23,147,150],{"additionalstyles":25,"color":148,"title":149},"primary","Quick port test on Android",[19,151,152,153,156,157,159],{},"Install the free app ",[35,154,155],{},"Port Authority"," on Android. Enter the NTRIP host and port ",[46,158,48],{},", then tap Scan. A green result means the port is reachable. A red result means it is blocked on your current network.",[14,161,163],{"id":162},"cause-3-wrong-credentials-or-mountpoint","Cause 3 — Wrong credentials or mountpoint",[77,165,169,180],{"additionalstyles":25,"frequency":166,"icon":167,"level":108,"title":168},"Connection reaches the server but is rejected","icons\u002FKey.svg","Authentication failure or unknown mountpoint",[19,170,171,172,175,176,179],{},"If the server is reachable but your client receives an error like ",[46,173,174],{},"401 Unauthorized"," or ",[46,177,178],{},"404 Not Found",", the problem is the credentials or mountpoint name.",[29,181,182,188,201,207],{},[32,183,184,187],{},[35,185,186],{},"Check for typos."," Username and password are case-sensitive. Copy and paste from your service confirmation email rather than typing manually.",[32,189,190,193,194,175,197,200],{},[35,191,192],{},"Load the sourcetable."," Most NTRIP clients have a ",[35,195,196],{},"Get Mountpoints",[35,198,199],{},"Source Table"," button. Use it to fetch the current list of available mountpoints from the server — do not type the mountpoint name manually.",[32,202,203,206],{},[35,204,205],{},"Check your subscription status."," If your trial or subscription has expired, the server will reject your credentials even though they look correct.",[32,208,209,212,213,175,215,218,219,222,223,225],{},[35,210,211],{},"Verify the host address."," Do not include ",[46,214,52],{},[46,216,217],{},"https:\u002F\u002F"," before the hostname. Enter the hostname only — for example ",[46,220,221],{},"ntrip.rtksub.com"," — and set the port separately to ",[46,224,48],{},".",[227,228],"terminal-box",{"additionalstyles":229,"items":230},"mt-[30px]","Host|ntrip.rtksub.com||Port|2101||Mountpoint — standard|RTCM3_NL||Mountpoint — DJI drones|RTCM3_NL_MSM5||Mountpoint — VRS (>30 km)|RTCM3_NL_VRS||Mountpoint — high-end|RTCM3_NL_MSM7",[14,232,234],{"id":233},"cause-4-gga-not-being-sent","Cause 4 — GGA not being sent",[77,236,241,244],{"additionalstyles":25,"frequency":237,"icon":238,"level":239,"title":240},"Affects VRS mountpoints — connection appears successful but no data flows","icons\u002FMarker.svg","3","No GGA position being transmitted to server",[19,242,243],{},"VRS (Virtual Reference Station) mountpoints require your rover to send its approximate position to the NTRIP server. The server uses this to generate a virtual correction point near you. If GGA is not sent, the server streams nothing — you are connected but receive 0 bytes per second.",[29,245,246,260,263],{},[32,247,248,249,252,253,175,256,259],{},"In your NTRIP client settings, look for ",[35,250,251],{},"Send GGA to caster",", ",[35,254,255],{},"Transmit NMEA GGA",[35,257,258],{},"Send position to server",". Enable it.",[32,261,262],{},"Make sure your receiver has at least a Single solution before connecting. GGA requires a valid position — even a rough one. If GGA contains all zeros, the server cannot generate corrections.",[32,264,265,266,269],{},"If you are not using VRS but still see 0 bytes, try switching to a non-VRS mountpoint such as ",[46,267,268],{},"RTCM3_NL",". Standard mountpoints do not require GGA.",[14,271,273],{"id":272},"device-specific-fixes","Device-specific fixes",[19,275,276],{},"Select your device for tailored instructions:",[278,279,282,308,326,340,346],"device-tabs",{"additionalstyles":25,"default-tab":280,"items":281},"Emlid","Emlid|DJI|SW Maps|Trimble \u002F Leica|Lefebure",[283,284,285,302,305],"device-tab",{"name":280},[19,286,287,290,291,294,295,298,299,301],{},[35,288,289],{},"Emlid Flow (Reach RS2+, RS3, RS4, RX2):"," Go to ",[35,292,293],{},"Correction input → NTRIP",". Tap ",[35,296,297],{},"Add profile"," and fill in the credentials. Enable ",[35,300,251],{}," if you use a VRS mountpoint. Make sure the receiver has satellite lock (Single or better) before connecting.",[19,303,304],{},"If the connection fails with correct credentials, toggle airplane mode on and off to refresh the data connection, then reconnect.",[19,306,307],{},"For Emlid on Windows with FieldGenius: configure NTRIP inside Emlid Flow via the receiver's IP, not inside FieldGenius.",[283,309,311],{"name":310},"DJI",[19,312,313,314,317,318,321,322,325],{},"In DJI Pilot 2, go to ",[35,315,316],{},"RTK Settings → Custom Network RTK"," and check the host, port and credentials. Use ",[46,319,320],{},"RTCM3_NL_MSM5"," for DJI drones, or ",[46,323,324],{},"RTCM3_NL_VRS"," for long baselines. Make sure the controller has internet access before connecting.",[283,327,329],{"name":328},"SW Maps",[19,330,331,332,335,336,339],{},"Open ",[35,333,334],{},"NTRIP Client"," only after connecting the external receiver. The option does not appear without an active Bluetooth GNSS or USB Serial GNSS connection. Enable ",[35,337,338],{},"Send NMEA GGA to NTRIP Caster"," for VRS.",[283,341,343],{"name":342},"Trimble \u002F Leica",[19,344,345],{},"Confirm the controller has an active internet data link, then reload the sourcetable rather than entering a mountpoint manually. In Trimble Access, check the received-byte counter under the receiver's Data Link status.",[283,347,349],{"name":348},"Lefebure",[19,350,351,352,355],{},"In Lefebure NTRIP Client, add a new profile and use the ",[35,353,354],{},"Get Source Table"," button. Allow the app to use mobile data, and enable GGA when the selected mountpoint is VRS.",[14,357,359],{"id":358},"common-error-messages","Common error messages",[361,362,363,379],"table",{},[364,365,366],"thead",{},[367,368,369,373,376],"tr",{},[370,371,372],"th",{},"Error message",[370,374,375],{},"Meaning",[370,377,378],{},"Fix",[380,381,382,395,407,420,433,444,458],"tbody",{},[367,383,384,389,392],{},[385,386,387],"td",{},[46,388,174],{},[385,390,391],{},"Wrong username or password",[385,393,394],{},"Check credentials. Copy-paste from your account dashboard.",[367,396,397,401,404],{},[385,398,399],{},[46,400,178],{},[385,402,403],{},"Mountpoint does not exist",[385,405,406],{},"Load the sourcetable and select a mountpoint from the list.",[367,408,409,414,417],{},[385,410,411],{},[46,412,413],{},"Connection refused",[385,415,416],{},"Port 2101 blocked or server unreachable",[385,418,419],{},"Switch to mobile data. Test the port with telnet or Port Authority.",[367,421,422,427,430],{},[385,423,424],{},[46,425,426],{},"Connection timeout",[385,428,429],{},"No route to server — network or firewall issue",[385,431,432],{},"Check the internet connection. Try a different network.",[367,434,435,438,441],{},[385,436,437],{},"Connected, 0 bytes\u002Fsec",[385,439,440],{},"GGA not sent for VRS, or wrong mountpoint",[385,442,443],{},"Enable GGA. Switch to a non-VRS mountpoint as a test.",[367,445,446,452,455],{},[385,447,448,451],{},[46,449,450],{},"ICY 200 OK"," then drops",[385,453,454],{},"Successful connection but stream interrupted",[385,456,457],{},"Unstable internet. Use a hotspot and enable auto-reconnect.",[367,459,460,465,468],{},[385,461,462],{},[46,463,464],{},"Sourcetable empty",[385,466,467],{},"Server reachable but no mountpoints returned",[385,469,470],{},"Your subscription may be inactive. Contact your correction service.",[23,472,474],{"additionalstyles":25,"color":26,"title":473},"Still stuck?",[19,475,476],{},"If none of the above resolves the issue, the problem may be specific to your receiver model or network environment. Describe your exact error message, device and current network setup to the AI for a targeted answer.",{"title":478,"searchDepth":479,"depth":479,"links":480},"",2,[481,482,483,484,485,486,487],{"id":16,"depth":479,"text":17},{"id":74,"depth":479,"text":75},{"id":102,"depth":479,"text":103},{"id":162,"depth":479,"text":163},{"id":233,"depth":479,"text":234},{"id":272,"depth":479,"text":273},{"id":358,"depth":479,"text":359},"troubleshooting","Troubleshooting\u002FWebP\u002Fcannot-connect-to-ntrip-caster-what-now.webp","NTRIP connection failures have a small number of root causes. Work through this guide from the top — most problems are solved within the first three checks.","md",{},true,"\u002Fen\u002Ftroubleshooting\u002Fntrip-connection-failed","2026-07-25",[497,498],"\u002Fen\u002Ftroubleshooting\u002Fstuck-on-float","\u002Fen\u002Flearn\u002Fwhat-is-gga",{"title":8,"description":490},"en\u002Ftroubleshooting\u002Fntrip-connection-failed","6dPLfUP248llqwHU3VZpKE8iJ50c-nLalv8qxJwJOAw",{"id":503,"title":504,"author":9,"body":505,"category":488,"cover":908,"description":909,"extension":491,"meta":910,"navigation":493,"path":911,"publishedAt":495,"relatedArticles":912,"seo":913,"stem":914,"updatedAt":4,"__hash__":915},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Fwrong-coordinates-rtk-fix.md","My coordinates are wrong — but I have RTK Fix",{"type":11,"value":506,"toc":899},[507,521,525,528,549,553,584,588,624,631,635,654,658,692,696,719,723,726,887,893],[23,508,510],{"additionalstyles":25,"color":148,"title":509},"The key distinction: precision vs accuracy",[19,511,512,513,516,517,520],{},"RTK Fix gives you high ",[35,514,515],{},"precision"," — your positions are repeatable and internally consistent to centimetres. ",[35,518,519],{},"Accuracy"," — how well those positions match real-world coordinates — depends on the datum, coordinate system and geoid model applied on top. Fix without the right transformation applied can be precise but inaccurate.",[14,522,524],{"id":523},"diagnose-by-offset-size","Diagnose by offset size",[19,526,527],{},"The size and direction of the coordinate error is the fastest clue to the cause. Select the pattern that matches your situation:",[529,530,532,537,541,545],"cards",{"additionalstyles":531},"mt-[40px]",[533,534],"cards-item",{"text":535,"title":536},"Consistent shift in one direction. Horizontal only — height looks fine.","0.5 – 2 m",[533,538],{"text":539,"title":540},"Height only — plan position is fine. Ellipsoidal vs orthometric height confusion.","0.3 – 1 m",[533,542],{"text":543,"title":544},"Large offset, possibly inconsistent. Completely wrong coordinate system selected.","10 m – 100 m+",[533,546],{"text":547,"title":548},"Height only and consistent across all points. Wrong antenna height entered.","2 cm – 50 cm",[14,550,552],{"id":551},"cause-1-datum-mismatch","Cause 1 — Datum mismatch",[77,554,558,561,564],{"additionalstyles":25,"frequency":555,"icon":556,"level":81,"title":557},"Typical offset: 0.5 – 2 m horizontal","icons\u002FWorld.svg","WGS84 \u002F ETRS89 corrections applied without local datum transformation",[19,559,560],{},"All NTRIP correction services — including GEODNET-based services — deliver corrections in WGS84 or ETRS89. These are global reference frames used by satellites. Most countries work in a local national datum — RD New in the Netherlands, OSGB36 in the UK, GDA2020 in Australia — which does not perfectly align with WGS84.",[19,562,563],{},"The difference between WGS84 and a national datum is small but significant for precision work: typically 0.5 – 1.5 m in the Netherlands, and similar magnitudes in other countries. If your field software is not applying the correct datum transformation, every point you collect will be shifted by this amount.",[29,565,566,569,575,581],{},[32,567,568],{},"Check your job's coordinate system settings. Verify that both the horizontal datum and transformation method are set correctly for your country.",[32,570,571,574],{},[35,572,573],{},"For the Netherlands:"," the job must use RD New (EPSG:28992) with the RDNAPTRANS™ 2018 transformation. Without it, positions will be off by roughly 0.6 – 0.9 m.",[32,576,577,580],{},[35,578,579],{},"For the UK:"," use OSGB36 (British National Grid, EPSG:27700) with the OSTN15 transformation and OSGM15 geoid. Without OSTN15, horizontal positions are off by up to 1.5 m and heights by several metres.",[32,582,583],{},"Verify by occupying a known national control point. If the offset is consistent in direction and magnitude across all points, it is a datum transformation problem.",[14,585,587],{"id":586},"cause-2-missing-or-wrong-geoid-model","Cause 2 — Missing or wrong geoid model",[77,589,593,596,599,602],{"additionalstyles":25,"frequency":590,"icon":591,"level":81,"title":592},"Typical offset: 0.3 – 50+ m in height only","icons\u002FRuler.svg","Ellipsoidal height reported instead of orthometric (above sea level) height",[19,594,595],{},"GNSS receivers measure height relative to the WGS84 ellipsoid — a mathematical model of Earth's shape. This ellipsoidal height is not the same as the height above sea level (orthometric height) that appears on maps and is used in engineering.",[19,597,598],{},"In the Netherlands, the difference between ellipsoidal height and NAP (Normaal Amsterdams Peil, the Dutch vertical datum) varies between approximately 38 m and 44 m across the country. If your receiver outputs ellipsoidal height and your project uses NAP heights, every elevation you collect will be wrong by this amount.",[19,600,601],{},"The correction between ellipsoidal and orthometric height is called the geoid undulation. Applying the correct geoid model converts one to the other.",[29,603,604,611,616,621],{},[32,605,606,607,610],{},"Check whether your field software applies a geoid model. In Emlid Flow, go to ",[35,608,609],{},"Job settings → Coordinate system"," and verify that a geoid file is selected.",[32,612,613,615],{},[35,614,573],{}," use the NLGEO2018 geoid, included in RDNAPTRANS™ 2018. This converts ellipsoidal heights to NAP. Without it, heights are out by 38 – 44 m.",[32,617,618,620],{},[35,619,579],{}," use OSGM15. For Germany use GCG2016, Belgium BG03 and France RAF18. See the country table below for a full reference.",[32,622,623],{},"If the geoid file is not available in your software, download it from the national geodetic authority and import it into the coordinate library.",[23,625,628],{"additionalstyles":25,"color":626,"title":627},"orange","A 40-metre height error is not RTK failure",[19,629,630],{},"A common support question is: “My heights are completely wrong — off by 40 metres.” This is almost never a receiver problem. It is the difference between WGS84 ellipsoidal height and NAP, or another national vertical datum. The RTK Fix is working perfectly — the geoid model has simply not been applied.",[14,632,634],{"id":633},"cause-3-wrong-coordinate-system-in-your-job","Cause 3 — Wrong coordinate system in your job",[77,636,640,643],{"additionalstyles":25,"frequency":637,"icon":638,"level":108,"title":639},"Typical offset: 10 m to hundreds of metres","icons\u002FMap.svg","Job configured with the wrong projection or EPSG code",[19,641,642],{},"If your positions are off by tens or hundreds of metres, or if the offset varies across your site rather than being a consistent shift, the most likely cause is a completely wrong coordinate system. This happens when the job is created with the default coordinate system — often WGS84 geographic or a UTM zone — instead of the project's required system.",[29,644,645,648,651],{},[32,646,647],{},"Check the EPSG code of your job's coordinate system and compare it with what your project requires. Netherlands: EPSG:28992 (RD New). Germany: EPSG:25832 (ETRS89 \u002F UTM zone 32N) or state-specific systems. Belgium: EPSG:31370 (Belgian Lambert 72).",[32,649,650],{},"If the wrong system was used for existing data, re-process the raw observations in the correct coordinate system rather than applying a post-collection offset. Projection errors are not uniform across large areas.",[32,652,653],{},"Create a template job with the correct coordinate system and transformation before fieldwork begins. Share it with the whole team so everyone uses the same settings.",[14,655,657],{"id":656},"cause-4-antenna-height-error","Cause 4 — Antenna height error",[77,659,663,666],{"additionalstyles":25,"frequency":660,"icon":661,"level":239,"title":662},"Typical offset: 2 cm – 50 cm in height, consistent across all points","icons\u002FSatellite.svg","Incorrect antenna height or measurement reference entered",[19,664,665],{},"The antenna height you enter in your field software is subtracted from the measured position to compute the ground point. An error here shifts every height measurement by exactly the same amount. This is a systematic error, which makes it identifiable.",[29,667,668,674,680,686],{},[32,669,670,673],{},[35,671,672],{},"Verify what the height is measured to."," Different manufacturers measure to different reference points. Emlid heights are measured to the bottom of the receiver. Trimble heights are typically measured to the antenna reference point (ARP). Entering the wrong reference adds or subtracts the antenna offset on top of your field measurement.",[32,675,676,679],{},[35,677,678],{},"Check the vertical offset in the antenna profile."," Most field software stores a vertical offset for each receiver model. Verify this value matches the published receiver specifications.",[32,681,682,685],{},[35,683,684],{},"For tilted pole work:"," ensure the pole bubble is calibrated. A 2° tilt on a 2-metre pole introduces a 7 cm horizontal error.",[32,687,688,691],{},[35,689,690],{},"Test on a known benchmark."," If the height error equals your measured antenna height exactly, you have entered it in the wrong direction.",[14,693,695],{"id":694},"cause-5-antenna-phase-centre-offset","Cause 5 — Antenna phase centre offset",[77,697,702,705,708],{"additionalstyles":25,"frequency":698,"icon":699,"level":700,"title":701},"Typical offset: 2 – 10 cm, height only","icons\u002FCog.svg","2","Receiver antenna profile missing or incorrect in field software",[19,703,704],{},"GNSS receivers do not measure position at the physical base of the antenna. They measure at the antenna phase centre — a point inside the antenna that varies by satellite elevation angle. Field software corrects for this using antenna calibration data.",[19,706,707],{},"If your receiver model is not in the software's antenna database, or the wrong model is selected, the phase centre correction is not applied and height measurements are off by a few centimetres. This is less common than datum and geoid errors but matters for the highest-accuracy applications.",[29,709,710,713,716],{},[32,711,712],{},"In your field software, check that the antenna model matches your physical receiver exactly — including variant, such as RS2 versus RS2+.",[32,714,715],{},"For Emlid receivers used with third-party software, download the IGS antenna calibration file in ANTEX format and import it into the antenna database.",[32,717,718],{},"If the offset is consistent and small — 2 to 5 cm in height — it is worth investigating. If it is larger, revisit antenna height entry or the geoid model first.",[14,720,722],{"id":721},"correct-settings-by-country","Correct settings by country",[19,724,725],{},"Use this table to verify the coordinate system, datum transformation and geoid model for your working country. All of these must be configured correctly in your field software at the same time.",[361,727,728,744],{},[364,729,730],{},[367,731,732,735,738,741],{},[370,733,734],{},"Country",[370,736,737],{},"Horizontal CRS",[370,739,740],{},"Datum transformation",[370,742,743],{},"Vertical \u002F geoid",[380,745,746,762,778,794,810,826,840,855,871],{},[367,747,748,753,756,759],{},[385,749,750],{},[35,751,752],{},"Netherlands",[385,754,755],{},"RD New — EPSG:28992",[385,757,758],{},"RDNAPTRANS™ 2018",[385,760,761],{},"NAP via NLGEO2018",[367,763,764,769,772,775],{},[385,765,766],{},[35,767,768],{},"United Kingdom",[385,770,771],{},"British National Grid — EPSG:27700",[385,773,774],{},"OSTN15",[385,776,777],{},"ODN via OSGM15",[367,779,780,785,788,791],{},[385,781,782],{},[35,783,784],{},"Germany",[385,786,787],{},"ETRS89 \u002F UTM zone 32N — EPSG:25832",[385,789,790],{},"ETRS89 → DHDN BeTA2007",[385,792,793],{},"DHHN2016 via GCG2016",[367,795,796,801,804,807],{},[385,797,798],{},[35,799,800],{},"Belgium",[385,802,803],{},"Belgian Lambert 72 — EPSG:31370",[385,805,806],{},"BD72 transformation",[385,808,809],{},"TAW via BG03",[367,811,812,817,820,823],{},[385,813,814],{},[35,815,816],{},"France",[385,818,819],{},"RGF93 v2 \u002F Lambert-93 — EPSG:2154",[385,821,822],{},"Direct ETRS89 alignment",[385,824,825],{},"NGF-IGN69 via RAF18",[367,827,828,833,835,837],{},[385,829,830],{},[35,831,832],{},"Denmark",[385,834,787],{},[385,836,822],{},[385,838,839],{},"DVR90 via DK-GM2022",[367,841,842,847,850,852],{},[385,843,844],{},[35,845,846],{},"Sweden",[385,848,849],{},"SWEREF99 TM — EPSG:3006",[385,851,822],{},[385,853,854],{},"RH2000 via SWEN17",[367,856,857,862,865,868],{},[385,858,859],{},[35,860,861],{},"Australia",[385,863,864],{},"GDA2020 \u002F MGA — zone-specific",[385,866,867],{},"GDA94 → GDA2020 transformation grid",[385,869,870],{},"AHD via AUSGeoid2020",[367,872,873,878,881,884],{},[385,874,875],{},[35,876,877],{},"United States",[385,879,880],{},"State Plane or UTM (NAD83)",[385,882,883],{},"NAD83 (2011) — use epoch-matched",[385,885,886],{},"NAVD88 via GEOID18",[23,888,890],{"additionalstyles":25,"color":26,"title":889},"Always verify on a known control point",[19,891,892],{},"Before collecting data on any project, occupy a published national control point with known coordinates in the project datum. Compare your measured coordinates against the published values. A discrepancy of more than 3 cm horizontally or 5 cm vertically indicates a datum, geoid or antenna-height problem that must be resolved before fieldwork begins.",[23,894,896],{"additionalstyles":229,"color":148,"title":895},"Not sure which settings your software is using?",[19,897,898],{},"Describe your device, field software and the coordinate error you are seeing to the AI. Include the offset size, direction and whether it affects horizontal position, height or both for a specific diagnosis.",{"title":478,"searchDepth":479,"depth":479,"links":900},[901,902,903,904,905,906,907],{"id":523,"depth":479,"text":524},{"id":551,"depth":479,"text":552},{"id":586,"depth":479,"text":587},{"id":633,"depth":479,"text":634},{"id":656,"depth":479,"text":657},{"id":694,"depth":479,"text":695},{"id":721,"depth":479,"text":722},"Troubleshooting\u002FWebP\u002Fmy-coordinates-are-wrong-but-i-have-rtk-fix.webp","RTK Fix means centimetre-level precision relative to the reference frame. It does not guarantee your coordinates match what you expect on a map or in a national coordinate system. When Fix is solid but coordinates are off, the cause is almost always a datum or coordinate system mismatch — not the RTK itself.",{},"\u002Fen\u002Ftroubleshooting\u002Fwrong-coordinates-rtk-fix",[494,498],{"title":504,"description":909},"en\u002Ftroubleshooting\u002Fwrong-coordinates-rtk-fix","bt1ZB70v_ZMJpavlRxYatogsGLmX87nqkgkPGXJZTcY",{"id":917,"title":918,"author":919,"body":920,"category":488,"cover":1348,"description":1349,"extension":491,"meta":1350,"navigation":493,"path":1351,"publishedAt":1352,"relatedArticles":1353,"seo":1355,"stem":1356,"updatedAt":4,"__hash__":1357},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Frtk-fix-dropping.md","RTK Fix keeps dropping — how to fix it","Wilko",{"type":11,"value":921,"toc":1338},[922,926,929,955,959,999,1003,1046,1050,1094,1100,1104,1131,1135,1167,1171,1207,1211,1332],[14,923,925],{"id":924},"identify-your-pattern-first","Identify your pattern first",[19,927,928],{},"How Fix drops tells you a lot about the cause. Match your situation to one of these patterns before diving into fixes.",[529,930,931,935,939,943,947,951],{"additionalstyles":25},[533,932],{"text":933,"title":934},"Fix is stable when standing still but drops every time you walk or drive. Especially when passing trees, buildings or under a canopy. → Obstruction or multipath","Drops when moving",[533,936],{"text":937,"title":938},"Fix holds for 2–5 minutes then drops to Float, then recovers. Repeating cycle even in open sky. → Unstable internet or NTRIP reconnects","Drops every few minutes",[533,940],{"text":941,"title":942},"Fix is fine on part of the site but consistently drops in certain zones — near a building, fence line or crop. → Local obstruction or multipath","Drops in specific areas",[533,944],{"text":945,"title":946},"Fix initialises and drops almost immediately, regardless of location. Float most of the time. → Long baseline, wrong mountpoint or receiver settings","Never holds longer than 30 sec",[533,948],{"text":949,"title":950},"Fix is stable in clear conditions but unstable on overcast days or after rain. May correlate with season. → Ionospheric activity or increased multipath from wet surfaces","Drops during cloudy or wet weather",[533,952],{"text":953,"title":954},"Fix is stable morning and evening but unstable around midday or at a predictable time. → Poor satellite geometry (PDOP window) or peak ionospheric activity","Drops at specific times of day",[14,956,958],{"id":957},"cause-1-physical-obstruction","Cause 1 — Physical obstruction",[77,960,964,967],{"additionalstyles":25,"frequency":961,"icon":962,"level":81,"title":963},"Very common","icons\u002FTree.svg","Trees, buildings or terrain blocking satellite signals",[19,965,966],{},"When an obstruction passes between your antenna and satellites, signals drop. If enough satellites disappear simultaneously, carrier phase ambiguities can no longer be maintained and Fix drops to Float. This is the most common cause of Fix instability in field conditions.",[29,968,969,975,981,987,993],{},[32,970,971,974],{},[35,972,973],{},"Walk with the antenna as high as possible."," A taller pole — 2.0 m instead of 1.5 m — improves line of sight above crops, fences and people.",[32,976,977,980],{},[35,978,979],{},"Hold the pole vertical."," Even a small tilt blocks part of the opposite sky. Use the bubble level or your receiver's tilt sensor.",[32,982,983,986],{},[35,984,985],{},"Reduce the elevation mask to 10°."," This admits more low-angle satellites. Do not go below 5°, because very low satellites add more noise than useful geometry.",[32,988,989,992],{},[35,990,991],{},"Enable all constellations."," GPS, GLONASS, Galileo and BeiDou together give the receiver more alternatives when one part of the sky is blocked.",[32,994,995,998],{},[35,996,997],{},"Move the measurement position 2–3 metres."," If the point allows it, a small move can clear a local obstruction completely.",[14,1000,1002],{"id":1001},"cause-2-multipath-interference","Cause 2 — Multipath interference",[77,1004,1008,1011,1014],{"additionalstyles":25,"frequency":1005,"icon":1006,"level":108,"title":1007},"Common","icons\u002FBuilding.svg","Reflected signals from buildings, vehicles or water",[19,1009,1010],{},"Multipath occurs when satellite signals bounce off surfaces before reaching your antenna. The reflected signal arrives slightly later than the direct signal. Your receiver receives both, and the mixture corrupts the carrier phase measurement — causing Fix to degrade or drop.",[19,1012,1013],{},"Multipath is worst near large metal structures such as construction sites, silos and greenhouses, glass buildings, still water and wet horizontal surfaces after rain.",[29,1015,1016,1022,1028,1034,1040],{},[32,1017,1018,1021],{},[35,1019,1020],{},"Move 5–10 metres away from reflective surfaces."," Distance is the most effective multipath fix.",[32,1023,1024,1027],{},[35,1025,1026],{},"Raise the elevation mask to 15° or 20° near buildings."," This removes low-angle signals that are most likely to reflect.",[32,1029,1030,1033],{},[35,1031,1032],{},"Use a receiver with multipath mitigation."," Trimble Maxwell, NovAtel STROBE and Septentrio AIM+ are designed to reject reflected signals.",[32,1035,1036,1039],{},[35,1037,1038],{},"Avoid measuring immediately after rain."," Wet roads, roofs and fields reflect more strongly. Wait 30–60 minutes when possible.",[32,1041,1042,1045],{},[35,1043,1044],{},"Wait for cranes or vehicles to leave the reflection zone."," Moving metal objects cause rapidly changing multipath that is particularly difficult to filter.",[14,1047,1049],{"id":1048},"cause-3-unstable-internet-connection","Cause 3 — Unstable internet connection",[77,1051,1053,1056],{"additionalstyles":25,"frequency":1005,"icon":80,"level":108,"title":1052},"NTRIP stream interrupted by data connection drops",[19,1054,1055],{},"When the NTRIP correction stream is interrupted — even for a few seconds — your receiver loses the reference data it needs to maintain carrier phase lock. If the gap is long enough, Fix drops to Float and the receiver must re-initialise. This is especially common in areas with variable mobile data coverage.",[29,1057,1058,1064,1070,1076,1082,1088],{},[32,1059,1060,1063],{},[35,1061,1062],{},"Check signal strength."," Watch whether the mobile connection changes from 4G to 3G or Edge at the moment Fix drops.",[32,1065,1066,1069],{},[35,1067,1068],{},"Switch to a dedicated hotspot."," A separate hotspot often maintains a more stable connection than phone tethering.",[32,1071,1072,1075],{},[35,1073,1074],{},"Switch carrier."," Coverage varies significantly between networks, especially in rural areas.",[32,1077,1078,1081],{},[35,1079,1080],{},"Force 4G only."," Prevent the modem from repeatedly switching between network types.",[32,1083,1084,1087],{},[35,1085,1086],{},"Enable auto-reconnect."," Make sure the NTRIP client reconnects automatically after a brief interruption.",[32,1089,1090,1093],{},[35,1091,1092],{},"Check bytes per second."," A healthy stream is usually a steady 500–2,000 bytes\u002Fsec. Drops to zero confirm an internet or NTRIP interruption.",[23,1095,1097],{"additionalstyles":25,"color":148,"title":1096},"How long does reconnection take?",[19,1098,1099],{},"When NTRIP disconnects and reconnects, most receivers re-achieve Fix within 10–30 seconds if the satellite geometry is good and the baseline is short. A brief interruption is recoverable. If your receiver takes 2–5 minutes to get Fix again after every drop, the baseline or environment is also a contributing factor.",[14,1101,1103],{"id":1102},"cause-4-long-baseline","Cause 4 — Long baseline",[77,1105,1108,1111],{"additionalstyles":25,"frequency":1106,"icon":591,"level":239,"title":1107},"Moderate","Too far from the nearest reference station",[19,1109,1110],{},"At longer baselines the ionosphere and troposphere introduce differential errors that make carrier phase ambiguity resolution harder to maintain. Fix is more fragile — small signal disturbances that would not matter at a 5 km baseline cause Fix to drop at 40 km.",[29,1112,1113,1119,1125],{},[32,1114,1115,1118],{},[35,1116,1117],{},"Switch to a VRS mountpoint."," A virtual reference station gives an effective baseline of only 1–2 km. This is the most effective fix.",[32,1120,1121,1124],{},[35,1122,1123],{},"Check the physical station distance."," If the nearest station is 50 km or more away and VRS is available, switch to VRS.",[32,1126,1127,1130],{},[35,1128,1129],{},"Enable multiple constellations."," More satellites give the RTK engine enough redundancy to maintain Fix over a longer baseline.",[14,1132,1134],{"id":1133},"cause-5-high-pdop-or-poor-satellite-geometry","Cause 5 — High PDOP or poor satellite geometry",[77,1136,1139,1142],{"additionalstyles":25,"frequency":1106,"icon":1137,"level":239,"title":1138},"icons\u002FSpace_satellite.svg","Satellites clustered in one part of the sky",[19,1140,1141],{},"Even with a good NTRIP connection and short baseline, Fix can drop if the satellite geometry is poor — PDOP above 4–5. Satellite geometry changes continuously throughout the day. A 20-minute window of poor geometry can cause Fix to drop repeatedly even though everything else is fine.",[29,1143,1144,1150,1155,1161],{},[32,1145,1146,1149],{},[35,1147,1148],{},"Check PDOP in your field software."," Look for the satellite quality or PDOP display. If PDOP is above 4, consider waiting for the geometry window to pass — typically 15–30 minutes.",[32,1151,1152,1154],{},[35,1153,991],{}," Adding GLONASS, Galileo and BeiDou distributes satellites across more sky positions, dramatically improving PDOP.",[32,1156,1157,1160],{},[35,1158,1159],{},"Use a satellite prediction app."," Apps such as GNSS View or Geo++ RINEX Logger show predicted PDOP values for your location throughout the day. Plan work sessions around the best geometry windows.",[32,1162,1163,1166],{},[35,1164,1165],{},"Lower the elevation mask slightly."," Allowing 10° satellites instead of 15° adds more satellites at varied positions, often improving PDOP by 0.5–1.0 in open sky.",[14,1168,1170],{"id":1169},"cause-6-receiver-settings","Cause 6 — Receiver settings",[77,1172,1175,1178],{"additionalstyles":25,"frequency":1173,"icon":699,"level":700,"title":1174},"Less common but impactful","Suboptimal GNSS or RTK configuration",[19,1176,1177],{},"Default receiver settings are conservative. In challenging environments — near buildings, under trees or with long baselines — tweaking specific settings can dramatically improve Fix stability.",[29,1179,1180,1189,1195,1201],{},[32,1181,1182,1185,1186,225],{},[35,1183,1184],{},"Switch from continuous to fix-and-hold ambiguity mode."," Continuous re-initialisation mode drops Fix at the slightest ambiguity uncertainty. Fix-and-hold maintains Fix through brief disturbances. In Emlid Flow: ",[35,1187,1188],{},"Settings → GNSS → Ambiguity resolution → Fix-and-hold",[32,1190,1191,1194],{},[35,1192,1193],{},"Enable all satellite constellations."," GPS alone gives 8–12 satellites. Adding GLONASS, Galileo and BeiDou gives 30–50 or more. More satellites means more redundancy and a more stable Fix.",[32,1196,1197,1200],{},[35,1198,1199],{},"Reduce the update rate."," Running at 10 Hz or 20 Hz in a challenging environment processes more data but also amplifies noise. Dropping to 5 Hz or 1 Hz gives the RTK engine more time per epoch and can improve stability.",[32,1202,1203,1206],{},[35,1204,1205],{},"Check the minimum satellite count."," Some field software rejects Fix if fewer than five satellites are tracked. In challenging environments, lowering this threshold to four prevents unnecessary drops when one satellite briefly disappears.",[14,1208,1210],{"id":1209},"recommended-settings-for-fix-stability","Recommended settings for Fix stability",[361,1212,1213,1226],{},[364,1214,1215],{},[367,1216,1217,1220,1223],{},[370,1218,1219],{},"Setting",[370,1221,1222],{},"Recommended value",[370,1224,1225],{},"Why",[380,1227,1228,1241,1254,1267,1280,1293,1306,1319],{},[367,1229,1230,1235,1238],{},[385,1231,1232],{},[35,1233,1234],{},"Constellations",[385,1236,1237],{},"GPS + GLONASS + Galileo + BeiDou",[385,1239,1240],{},"Maximum satellite count, best geometry",[367,1242,1243,1248,1251],{},[385,1244,1245],{},[35,1246,1247],{},"Elevation mask",[385,1249,1250],{},"10–15°",[385,1252,1253],{},"10° in open sky, 15° near buildings",[367,1255,1256,1261,1264],{},[385,1257,1258],{},[35,1259,1260],{},"Ambiguity resolution",[385,1262,1263],{},"Fix-and-hold (Emlid \u002F RTKLIB)",[385,1265,1266],{},"Maintains Fix through brief disturbances",[367,1268,1269,1274,1277],{},[385,1270,1271],{},[35,1272,1273],{},"Update rate",[385,1275,1276],{},"1–5 Hz for survey, 10 Hz for machine guidance",[385,1278,1279],{},"Lower rate = more stable Fix in challenging areas",[367,1281,1282,1287,1290],{},[385,1283,1284],{},[35,1285,1286],{},"PDOP mask",[385,1288,1289],{},"6.0 (do not lower below 4.0)",[385,1291,1292],{},"Reject poor geometry but allow marginal conditions",[367,1294,1295,1300,1303],{},[385,1296,1297],{},[35,1298,1299],{},"SNR mask",[385,1301,1302],{},"35 dBHz",[385,1304,1305],{},"Filter very noisy signals without losing too many satellites",[367,1307,1308,1313,1316],{},[385,1309,1310],{},[35,1311,1312],{},"NTRIP auto-reconnect",[385,1314,1315],{},"Enabled",[385,1317,1318],{},"Recover from brief internet drops automatically",[367,1320,1321,1326,1329],{},[385,1322,1323],{},[35,1324,1325],{},"Mountpoint",[385,1327,1328],{},"VRS if available",[385,1330,1331],{},"Eliminate baseline as a Fix stability factor",[23,1333,1335],{"additionalstyles":25,"color":26,"title":1334},"Still dropping after trying all of the above?",[19,1336,1337],{},"Describe your exact situation to the AI at the top of this page — your device, the drop pattern, your environment and what you have already tried. Specific symptoms point to specific causes that this general guide cannot cover.",{"title":478,"searchDepth":479,"depth":479,"links":1339},[1340,1341,1342,1343,1344,1345,1346,1347],{"id":924,"depth":479,"text":925},{"id":957,"depth":479,"text":958},{"id":1001,"depth":479,"text":1002},{"id":1048,"depth":479,"text":1049},{"id":1102,"depth":479,"text":1103},{"id":1133,"depth":479,"text":1134},{"id":1169,"depth":479,"text":1170},{"id":1209,"depth":479,"text":1210},"Troubleshooting\u002FWebP\u002Frtk-fix-keeps-dropping-how-to-fix-it.webp","Dropping from Fix to Float and back repeatedly is one of the most disruptive RTK problems in the field. The cause is almost always one of six things — and each has a specific fix. Work through this guide to find yours.",{},"\u002Fen\u002Ftroubleshooting\u002Frtk-fix-dropping","2026-07-24",[497,1354],"\u002Fen\u002Flearn\u002Ffloat-vs-fix",{"title":918,"description":1349},"en\u002Ftroubleshooting\u002Frtk-fix-dropping","hA7kZSikz5lpN-MYfKa0BX_BQNafwztmpgGfiRgbzAU",{"id":1359,"title":1360,"author":919,"body":1361,"category":488,"cover":1751,"description":1752,"extension":491,"meta":1753,"navigation":493,"path":497,"publishedAt":1352,"relatedArticles":1754,"seo":1755,"stem":1756,"updatedAt":4,"__hash__":1757},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Fstuck-on-float.md","Why am I stuck on Float and not reaching Fix?",{"type":11,"value":1362,"toc":1741},[1363,1369,1373,1376,1406,1410,1442,1446,1478,1482,1514,1518,1546,1550,1584,1588,1620,1622,1625,1735],[23,1364,1366],{"additionalstyles":25,"color":148,"title":1365},"Float is normal for the first 10–60 seconds",[19,1367,1368],{},"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.",[14,1370,1372],{"id":1371},"two-minute-checklist","Two-minute checklist",[19,1374,1375],{},"Run through these before diving into the causes. They resolve most cases immediately.",[23,1377,1379],{"additionalstyles":25,"color":26,"title":1378},"Quick Float diagnostic",[1380,1381,1382,1385,1388,1394,1397,1400,1403],"ul",{},[32,1383,1384],{},"Are you outside with a clear sky view? Float indoors or under trees is expected.",[32,1386,1387],{},"Is the NTRIP connection active with a stable bytes-per-second value above zero?",[32,1389,1390,1391,1393],{},"For DJI drones, are you using the MSM5 mountpoint ",[46,1392,320],{},"?",[32,1395,1396],{},"Are you seeing at least 15 satellites with good SNR?",[32,1398,1399],{},"Is PDOP below 4?",[32,1401,1402],{},"Have you been stationary for at least 60 seconds?",[32,1404,1405],{},"Are GPS, GLONASS, Galileo and BeiDou all enabled?",[14,1407,1409],{"id":1408},"cause-1-wrong-mountpoint","Cause 1 — Wrong mountpoint",[77,1411,1414,1417,1420],{"additionalstyles":25,"frequency":1412,"icon":661,"level":81,"title":1413},"Very common for DJI users","MSM4 mountpoint used with a DJI drone",[19,1415,1416],{},"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.",[19,1418,1419],{},"The symptom is unmistakable: NTRIP connected, bytes flowing, stable Float for many minutes, never converging to Fix regardless of sky conditions.",[29,1421,1422,1433,1436],{},[32,1423,1424,1425,1427,1428,1430,1431,225],{},"In DJI Pilot, go to ",[35,1426,316],{},". Change the mountpoint from ",[46,1429,268],{}," to ",[46,1432,320],{},[32,1434,1435],{},"Disconnect and reconnect. DJI should reach Fix within 60 seconds in open sky.",[32,1437,1438,1439,1441],{},"For long-baseline DJI flights, use ",[46,1440,324],{}," instead. The short effective baseline improves Fix stability.",[14,1443,1445],{"id":1444},"cause-2-corrections-not-reaching-the-receiver","Cause 2 — Corrections not reaching the receiver",[77,1447,1449,1452],{"additionalstyles":25,"frequency":1005,"icon":80,"level":108,"title":1448},"NTRIP stream connected but delivering no useful data",[19,1450,1451],{},"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.",[29,1453,1454,1460,1466,1472],{},[32,1455,1456,1459],{},[35,1457,1458],{},"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.",[32,1461,1462,1465],{},[35,1463,1464],{},"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.",[32,1467,1468,1471],{},[35,1469,1470],{},"Check VRS GGA transmission."," If you use a VRS mountpoint without GGA enabled, the server may stream nothing. Enable GGA and reconnect.",[32,1473,1474,1477],{},[35,1475,1476],{},"Try a dedicated hotspot."," Phone tethering can be less stable. A dedicated hotspot often resolves Float caused by repeated stream interruptions.",[14,1479,1481],{"id":1480},"cause-3-environment-and-obstructions","Cause 3 — Environment and obstructions",[77,1483,1485,1488],{"additionalstyles":25,"frequency":961,"icon":962,"level":81,"title":1484},"Obstructions or multipath blocking ambiguity resolution",[19,1486,1487],{},"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.",[29,1489,1490,1496,1502,1508],{},[32,1491,1492,1495],{},[35,1493,1494],{},"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°.",[32,1497,1498,1501],{},[35,1499,1500],{},"Stand still."," Movement during initialisation compounds the problem. Stop walking or driving and wait at least 60 seconds.",[32,1503,1504,1507],{},[35,1505,1506],{},"Lower the elevation mask to 10°."," Where supported, a lower mask allows useful low-angle satellites to improve geometry.",[32,1509,1510,1513],{},[35,1511,1512],{},"Move away from metal structures."," Metal roofs, silos, greenhouse frames and vehicles create strong multipath. Keep at least ten metres away.",[14,1515,1517],{"id":1516},"cause-4-baseline-too-long","Cause 4 — Baseline too long",[77,1519,1521,1524],{"additionalstyles":25,"frequency":1106,"icon":591,"level":239,"title":1520},"More than 30 km from the nearest reference station",[19,1522,1523],{},"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.",[29,1525,1526,1534,1540],{},[32,1527,1528,1531,1532,225],{},[35,1529,1530],{},"Switch to the VRS mountpoint."," VRS generates a virtual reference station around 1–2 km from you. Enable GGA and connect to ",[46,1533,324],{},[32,1535,1536,1539],{},[35,1537,1538],{},"Check the sourcetable distance."," If the nearest physical station is more than 25 km away, VRS is normally the better choice.",[32,1541,1542,1545],{},[35,1543,1544],{},"Use a dual-frequency receiver."," Single-frequency receivers are usually limited to baselines of around 10 km before ionospheric errors prevent Fix.",[14,1547,1549],{"id":1548},"cause-5-ionospheric-disturbance","Cause 5 — Ionospheric disturbance",[77,1551,1555,1558],{"additionalstyles":25,"frequency":1552,"icon":1553,"level":700,"title":1554},"Periodic — peaks during solar maximum","icons\u002FSun.svg","High solar activity disrupting carrier-phase signals",[19,1556,1557],{},"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.",[29,1559,1560,1566,1572,1578],{},[32,1561,1562,1565],{},[35,1563,1564],{},"Work early morning or evening."," Ionospheric activity is typically lowest during the first two hours after sunrise and later in the evening.",[32,1567,1568,1571],{},[35,1569,1570],{},"Switch to VRS."," Network-wide ionospheric modelling partially compensates for elevated ionospheric noise.",[32,1573,1574,1577],{},[35,1575,1576],{},"Check space weather."," A Kp index above 5 often causes RTK problems. Postponing work until the storm passes may be the only reliable option.",[32,1579,1580,1583],{},[35,1581,1582],{},"Use a triple-frequency receiver."," L5 signals are more robust to ionospheric noise than L1\u002FL2 and can maintain Fix in more difficult conditions.",[14,1585,1587],{"id":1586},"cause-6-receiver-or-software-settings","Cause 6 — Receiver or software settings",[77,1589,1592,1595],{"additionalstyles":25,"frequency":1590,"icon":699,"level":700,"title":1591},"Less common but easy to fix","Conservative defaults preventing ambiguity resolution",[19,1593,1594],{},"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.",[29,1596,1597,1603,1608,1614],{},[32,1598,1599,1602],{},[35,1600,1601],{},"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.",[32,1604,1605,1607],{},[35,1606,991],{}," GPS, GLONASS, Galileo and BeiDou together provide much more redundancy than GPS alone.",[32,1609,1610,1613],{},[35,1611,1612],{},"Reduce update rate to 1–5 Hz."," In a weak environment, reducing the rate gives the RTK engine more averaging time per epoch.",[32,1615,1616,1619],{},[35,1617,1618],{},"Set the minimum elevation mask to 10°."," Higher masks can exclude useful satellites and weaken satellite geometry.",[14,1621,273],{"id":272},[19,1623,1624],{},"Select your device for targeted advice:",[278,1626,1628,1655,1681,1706,1720],{"additionalstyles":25,"default-tab":280,"items":1627},"Emlid|DJI|Trimble|SW Maps|u-blox \u002F DIY",[283,1629,1630,1644,1652],{"name":280},[19,1631,1632,1635,1636,1639,1640,1643],{},[35,1633,1634],{},"Most effective fix for Emlid stuck on Float:"," go to ",[35,1637,1638],{},"Settings → GNSS settings → Ambiguity resolution"," and change from Continuous to ",[35,1641,1642],{},"Fix-and-hold",". This single setting resolves persistent Float in challenging environments for many Emlid users.",[19,1645,1646,1647,1649,1650,225],{},"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 ",[46,1648,324],{}," and enable ",[35,1651,251],{},[19,1653,1654],{},"Firmware updates can reset GNSS settings to their defaults. Re-check constellation and ambiguity settings after every update.",[283,1656,1657,1669,1672,1678],{"name":310},[19,1658,1659,1662,1663,1665,1666,1668],{},[35,1660,1661],{},"DJI stuck on Float is almost always MSM4 instead of MSM5."," Change the mountpoint to ",[46,1664,320],{}," in DJI Pilot under ",[35,1667,316],{},", then disconnect and reconnect.",[19,1670,1671],{},"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.",[19,1673,1674,1675,1677],{},"For long-baseline flights beyond 30 km, try ",[46,1676,324],{},". DJI handles VRS well and the shorter effective baseline improves Fix stability.",[19,1679,1680],{},"On the DJI M300 and Matrice 350, also check that the RTK antenna is firmly seated and its cable is undamaged.",[283,1682,1684,1694,1700,1703],{"name":1683},"Trimble",[19,1685,1686,1689,1690,1693],{},[35,1687,1688],{},"For Trimble stuck on Float",", first verify that the data link is active under ",[35,1691,1692],{},"Instrument → Receiver Status → Data Link",". The bytes counter must be incrementing.",[19,1695,1696,1697,1699],{},"For long-baseline work, switch to ",[46,1698,324],{},". Trimble Access sends GGA automatically when NTRIP is active.",[19,1701,1702],{},"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.",[19,1704,1705],{},"The Trimble R10 works correctly with MSM4. If an R10 remains on Float, investigate the environment or baseline rather than the mountpoint format.",[283,1707,1708,1714,1717],{"name":328},[19,1709,1710,1713],{},[35,1711,1712],{},"SW Maps stuck on Float usually means the external receiver is the bottleneck."," SW Maps displays the solution supplied by the connected receiver.",[19,1715,1716],{},"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.",[19,1718,1719],{},"A smartphone's internal single-frequency GNSS chip rarely reaches Fix. For centimetre accuracy, connect a multi-band external receiver.",[283,1721,1723,1729,1732],{"name":1722},"u-blox \u002F DIY",[19,1724,1725,1728],{},[35,1726,1727],{},"A u-blox ZED-F9P normally reaches Fix reliably within a 10–30 km baseline."," Beyond that, ionospheric decorrelation can prevent Fix without VRS.",[19,1730,1731],{},"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.",[19,1733,1734],{},"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.",[23,1736,1738],{"additionalstyles":25,"color":26,"title":1737},"Still on Float after all of the above?",[19,1739,1740],{},"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":478,"searchDepth":479,"depth":479,"links":1742},[1743,1744,1745,1746,1747,1748,1749,1750],{"id":1371,"depth":479,"text":1372},{"id":1408,"depth":479,"text":1409},{"id":1444,"depth":479,"text":1445},{"id":1480,"depth":479,"text":1481},{"id":1516,"depth":479,"text":1517},{"id":1548,"depth":479,"text":1549},{"id":1586,"depth":479,"text":1587},{"id":272,"depth":479,"text":273},"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.",{},[1354],{"title":1360,"description":1752},"en\u002Ftroubleshooting\u002Fstuck-on-float","cZuzVDxMmVc2t9_jfIEzEmwmUVVTUPbWnughCbX8Y_Y",[],1787304715007]