[{"data":1,"prerenderedAt":1343},["ShallowReactive",2],{"knowledge-page-en-\u002Ftroubleshooting\u002Fntrip-connection-failed":3},{"article":4,"posts":501,"relatedPosts":502},{"id":5,"title":6,"author":7,"body":8,"category":486,"cover":487,"description":488,"extension":489,"meta":490,"navigation":491,"path":492,"publishedAt":493,"relatedArticles":494,"seo":497,"stem":498,"updatedAt":499,"__hash__":500},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Fntrip-connection-failed.md","Cannot connect to NTRIP caster — what now?","Yuri",{"type":9,"value":10,"toc":475},"minimark",[11,16,20,70,74,98,102,144,158,162,224,229,233,268,272,275,354,358,469],[12,13,15],"h2",{"id":14},"quick-diagnostic-checklist","Quick diagnostic checklist",[17,18,19],"p",{},"Before diving into causes, run through these five checks. They resolve the majority of NTRIP connection failures.",[21,22,26],"card",{"additionalstyles":23,"color":24,"title":25},"mt-[60px]","green","Quick NTRIP diagnostic",[27,28,29,37,52,58,64],"ol",{},[30,31,32,36],"li",{},[33,34,35],"strong",{},"Internet working?"," Open a browser and load any website. If it fails, fix your connection first.",[30,38,39,42,43,47,48,51],{},[33,40,41],{},"Correct host and port?"," Port must be ",[44,45,46],"code",{},"2101",". Host must match exactly — no typos and no ",[44,49,50],{},"http:\u002F\u002F"," prefix.",[30,53,54,57],{},[33,55,56],{},"Credentials correct?"," Username and password are case-sensitive. Copy-paste rather than typing.",[30,59,60,63],{},[33,61,62],{},"Mountpoint exists?"," Load the sourcetable from the server to confirm the mountpoint name.",[30,65,66,69],{},[33,67,68],{},"GGA enabled?"," Required for VRS mountpoints. It must be enabled in your NTRIP client.",[12,71,73],{"id":72},"cause-1-no-internet-connection","Cause 1 — No internet connection",[75,76,81,84],"cause-card",{"additionalstyles":23,"frequency":77,"icon":78,"level":79,"title":80},"Most common cause on first setup","icons\u002FData.svg","5","Device has no data connection",[17,82,83],{},"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.",[27,85,86,89,92,95],{},[30,87,88],{},"Open a browser on the same device and navigate to any website. If it does not load, resolve the connectivity issue before proceeding.",[30,90,91],{},"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.",[30,93,94],{},"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.",[30,96,97],{},"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.",[12,99,101],{"id":100},"cause-2-port-2101-is-blocked","Cause 2 — Port 2101 is blocked",[75,103,108,114],{"additionalstyles":23,"frequency":104,"icon":105,"level":106,"title":107},"Common on corporate networks and some mobile carriers","icons\u002FLock.svg","4","Firewall or carrier blocking TCP port 2101",[17,109,110,111,113],{},"NTRIP uses TCP port ",[44,112,46],{},". 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.",[27,115,116,122,128,134],{},[30,117,118,121],{},[33,119,120],{},"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.",[30,123,124,127],{},[33,125,126],{},"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.",[30,129,130,133],{},[33,131,132],{},"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.",[30,135,136,139,140,143],{},[33,137,138],{},"Test the port directly."," On a computer, open a terminal and run ",[44,141,142],{},"telnet ntrip.rtksub.com 2101",". If the connection opens, the port is accessible. If it times out, the port is blocked.",[21,145,148],{"additionalstyles":23,"color":146,"title":147},"primary","Quick port test on Android",[17,149,150,151,154,155,157],{},"Install the free app ",[33,152,153],{},"Port Authority"," on Android. Enter the NTRIP host and port ",[44,156,46],{},", then tap Scan. A green result means the port is reachable. A red result means it is blocked on your current network.",[12,159,161],{"id":160},"cause-3-wrong-credentials-or-mountpoint","Cause 3 — Wrong credentials or mountpoint",[75,163,167,178],{"additionalstyles":23,"frequency":164,"icon":165,"level":106,"title":166},"Connection reaches the server but is rejected","icons\u002FKey.svg","Authentication failure or unknown mountpoint",[17,168,169,170,173,174,177],{},"If the server is reachable but your client receives an error like ",[44,171,172],{},"401 Unauthorized"," or ",[44,175,176],{},"404 Not Found",", the problem is the credentials or mountpoint name.",[27,179,180,186,199,205],{},[30,181,182,185],{},[33,183,184],{},"Check for typos."," Username and password are case-sensitive. Copy and paste from your service confirmation email rather than typing manually.",[30,187,188,191,192,173,195,198],{},[33,189,190],{},"Load the sourcetable."," Most NTRIP clients have a ",[33,193,194],{},"Get Mountpoints",[33,196,197],{},"Source Table"," button. Use it to fetch the current list of available mountpoints from the server — do not type the mountpoint name manually.",[30,200,201,204],{},[33,202,203],{},"Check your subscription status."," If your trial or subscription has expired, the server will reject your credentials even though they look correct.",[30,206,207,210,211,173,213,216,217,220,221,223],{},[33,208,209],{},"Verify the host address."," Do not include ",[44,212,50],{},[44,214,215],{},"https:\u002F\u002F"," before the hostname. Enter the hostname only — for example ",[44,218,219],{},"ntrip.rtksub.com"," — and set the port separately to ",[44,222,46],{},".",[225,226],"terminal-box",{"additionalstyles":227,"items":228},"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",[12,230,232],{"id":231},"cause-4-gga-not-being-sent","Cause 4 — GGA not being sent",[75,234,239,242],{"additionalstyles":23,"frequency":235,"icon":236,"level":237,"title":238},"Affects VRS mountpoints — connection appears successful but no data flows","icons\u002FMarker.svg","3","No GGA position being transmitted to server",[17,240,241],{},"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.",[27,243,244,258,261],{},[30,245,246,247,250,251,173,254,257],{},"In your NTRIP client settings, look for ",[33,248,249],{},"Send GGA to caster",", ",[33,252,253],{},"Transmit NMEA GGA",[33,255,256],{},"Send position to server",". Enable it.",[30,259,260],{},"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.",[30,262,263,264,267],{},"If you are not using VRS but still see 0 bytes, try switching to a non-VRS mountpoint such as ",[44,265,266],{},"RTCM3_NL",". Standard mountpoints do not require GGA.",[12,269,271],{"id":270},"device-specific-fixes","Device-specific fixes",[17,273,274],{},"Select your device for tailored instructions:",[276,277,280,306,324,338,344],"device-tabs",{"additionalstyles":23,"default-tab":278,"items":279},"Emlid","Emlid|DJI|SW Maps|Trimble \u002F Leica|Lefebure",[281,282,283,300,303],"device-tab",{"name":278},[17,284,285,288,289,292,293,296,297,299],{},[33,286,287],{},"Emlid Flow (Reach RS2+, RS3, RS4, RX2):"," Go to ",[33,290,291],{},"Correction input → NTRIP",". Tap ",[33,294,295],{},"Add profile"," and fill in the credentials. Enable ",[33,298,249],{}," if you use a VRS mountpoint. Make sure the receiver has satellite lock (Single or better) before connecting.",[17,301,302],{},"If the connection fails with correct credentials, toggle airplane mode on and off to refresh the data connection, then reconnect.",[17,304,305],{},"For Emlid on Windows with FieldGenius: configure NTRIP inside Emlid Flow via the receiver's IP, not inside FieldGenius.",[281,307,309],{"name":308},"DJI",[17,310,311,312,315,316,319,320,323],{},"In DJI Pilot 2, go to ",[33,313,314],{},"RTK Settings → Custom Network RTK"," and check the host, port and credentials. Use ",[44,317,318],{},"RTCM3_NL_MSM5"," for DJI drones, or ",[44,321,322],{},"RTCM3_NL_VRS"," for long baselines. Make sure the controller has internet access before connecting.",[281,325,327],{"name":326},"SW Maps",[17,328,329,330,333,334,337],{},"Open ",[33,331,332],{},"NTRIP Client"," only after connecting the external receiver. The option does not appear without an active Bluetooth GNSS or USB Serial GNSS connection. Enable ",[33,335,336],{},"Send NMEA GGA to NTRIP Caster"," for VRS.",[281,339,341],{"name":340},"Trimble \u002F Leica",[17,342,343],{},"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.",[281,345,347],{"name":346},"Lefebure",[17,348,349,350,353],{},"In Lefebure NTRIP Client, add a new profile and use the ",[33,351,352],{},"Get Source Table"," button. Allow the app to use mobile data, and enable GGA when the selected mountpoint is VRS.",[12,355,357],{"id":356},"common-error-messages","Common error messages",[359,360,361,377],"table",{},[362,363,364],"thead",{},[365,366,367,371,374],"tr",{},[368,369,370],"th",{},"Error message",[368,372,373],{},"Meaning",[368,375,376],{},"Fix",[378,379,380,393,405,418,431,442,456],"tbody",{},[365,381,382,387,390],{},[383,384,385],"td",{},[44,386,172],{},[383,388,389],{},"Wrong username or password",[383,391,392],{},"Check credentials. Copy-paste from your account dashboard.",[365,394,395,399,402],{},[383,396,397],{},[44,398,176],{},[383,400,401],{},"Mountpoint does not exist",[383,403,404],{},"Load the sourcetable and select a mountpoint from the list.",[365,406,407,412,415],{},[383,408,409],{},[44,410,411],{},"Connection refused",[383,413,414],{},"Port 2101 blocked or server unreachable",[383,416,417],{},"Switch to mobile data. Test the port with telnet or Port Authority.",[365,419,420,425,428],{},[383,421,422],{},[44,423,424],{},"Connection timeout",[383,426,427],{},"No route to server — network or firewall issue",[383,429,430],{},"Check the internet connection. Try a different network.",[365,432,433,436,439],{},[383,434,435],{},"Connected, 0 bytes\u002Fsec",[383,437,438],{},"GGA not sent for VRS, or wrong mountpoint",[383,440,441],{},"Enable GGA. Switch to a non-VRS mountpoint as a test.",[365,443,444,450,453],{},[383,445,446,449],{},[44,447,448],{},"ICY 200 OK"," then drops",[383,451,452],{},"Successful connection but stream interrupted",[383,454,455],{},"Unstable internet. Use a hotspot and enable auto-reconnect.",[365,457,458,463,466],{},[383,459,460],{},[44,461,462],{},"Sourcetable empty",[383,464,465],{},"Server reachable but no mountpoints returned",[383,467,468],{},"Your subscription may be inactive. Contact your correction service.",[21,470,472],{"additionalstyles":23,"color":24,"title":471},"Still stuck?",[17,473,474],{},"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":476,"searchDepth":477,"depth":477,"links":478},"",2,[479,480,481,482,483,484,485],{"id":14,"depth":477,"text":15},{"id":72,"depth":477,"text":73},{"id":100,"depth":477,"text":101},{"id":160,"depth":477,"text":161},{"id":231,"depth":477,"text":232},{"id":270,"depth":477,"text":271},{"id":356,"depth":477,"text":357},"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",[495,496],"\u002Fen\u002Ftroubleshooting\u002Fstuck-on-float","\u002Fen\u002Flearn\u002Fwhat-is-gga",{"title":6,"description":488},"en\u002Ftroubleshooting\u002Fntrip-connection-failed",null,"6dPLfUP248llqwHU3VZpKE8iJ50c-nLalv8qxJwJOAw",[],[503,915],{"id":504,"title":505,"author":506,"body":507,"category":486,"cover":906,"description":907,"extension":489,"meta":908,"navigation":491,"path":495,"publishedAt":909,"relatedArticles":910,"seo":912,"stem":913,"updatedAt":499,"__hash__":914},"knowledge_en\u002Fen\u002Ftroubleshooting\u002Fstuck-on-float.md","Why am I stuck on Float and not reaching Fix?","Wilko",{"type":9,"value":508,"toc":896},[509,515,519,522,552,556,589,593,626,630,664,668,698,702,737,741,775,777,780,890],[21,510,512],{"additionalstyles":23,"color":146,"title":511},"Float is normal for the first 10–60 seconds",[17,513,514],{},"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.",[12,516,518],{"id":517},"two-minute-checklist","Two-minute checklist",[17,520,521],{},"Run through these before diving into the causes. They resolve most cases immediately.",[21,523,525],{"additionalstyles":23,"color":24,"title":524},"Quick Float diagnostic",[526,527,528,531,534,540,543,546,549],"ul",{},[30,529,530],{},"Are you outside with a clear sky view? Float indoors or under trees is expected.",[30,532,533],{},"Is the NTRIP connection active with a stable bytes-per-second value above zero?",[30,535,536,537,539],{},"For DJI drones, are you using the MSM5 mountpoint ",[44,538,318],{},"?",[30,541,542],{},"Are you seeing at least 15 satellites with good SNR?",[30,544,545],{},"Is PDOP below 4?",[30,547,548],{},"Have you been stationary for at least 60 seconds?",[30,550,551],{},"Are GPS, GLONASS, Galileo and BeiDou all enabled?",[12,553,555],{"id":554},"cause-1-wrong-mountpoint","Cause 1 — Wrong mountpoint",[75,557,561,564,567],{"additionalstyles":23,"frequency":558,"icon":559,"level":79,"title":560},"Very common for DJI users","icons\u002FSatellite.svg","MSM4 mountpoint used with a DJI drone",[17,562,563],{},"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.",[17,565,566],{},"The symptom is unmistakable: NTRIP connected, bytes flowing, stable Float for many minutes, never converging to Fix regardless of sky conditions.",[27,568,569,580,583],{},[30,570,571,572,574,575,577,578,223],{},"In DJI Pilot, go to ",[33,573,314],{},". Change the mountpoint from ",[44,576,266],{}," to ",[44,579,318],{},[30,581,582],{},"Disconnect and reconnect. DJI should reach Fix within 60 seconds in open sky.",[30,584,585,586,588],{},"For long-baseline DJI flights, use ",[44,587,322],{}," instead. The short effective baseline improves Fix stability.",[12,590,592],{"id":591},"cause-2-corrections-not-reaching-the-receiver","Cause 2 — Corrections not reaching the receiver",[75,594,597,600],{"additionalstyles":23,"frequency":595,"icon":78,"level":106,"title":596},"Common","NTRIP stream connected but delivering no useful data",[17,598,599],{},"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.",[27,601,602,608,614,620],{},[30,603,604,607],{},[33,605,606],{},"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.",[30,609,610,613],{},[33,611,612],{},"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.",[30,615,616,619],{},[33,617,618],{},"Check VRS GGA transmission."," If you use a VRS mountpoint without GGA enabled, the server may stream nothing. Enable GGA and reconnect.",[30,621,622,625],{},[33,623,624],{},"Try a dedicated hotspot."," Phone tethering can be less stable. A dedicated hotspot often resolves Float caused by repeated stream interruptions.",[12,627,629],{"id":628},"cause-3-environment-and-obstructions","Cause 3 — Environment and obstructions",[75,631,635,638],{"additionalstyles":23,"frequency":632,"icon":633,"level":79,"title":634},"Very common","icons\u002FTree.svg","Obstructions or multipath blocking ambiguity resolution",[17,636,637],{},"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.",[27,639,640,646,652,658],{},[30,641,642,645],{},[33,643,644],{},"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°.",[30,647,648,651],{},[33,649,650],{},"Stand still."," Movement during initialisation compounds the problem. Stop walking or driving and wait at least 60 seconds.",[30,653,654,657],{},[33,655,656],{},"Lower the elevation mask to 10°."," Where supported, a lower mask allows useful low-angle satellites to improve geometry.",[30,659,660,663],{},[33,661,662],{},"Move away from metal structures."," Metal roofs, silos, greenhouse frames and vehicles create strong multipath. Keep at least ten metres away.",[12,665,667],{"id":666},"cause-4-baseline-too-long","Cause 4 — Baseline too long",[75,669,673,676],{"additionalstyles":23,"frequency":670,"icon":671,"level":237,"title":672},"Moderate","icons\u002FRuler.svg","More than 30 km from the nearest reference station",[17,674,675],{},"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.",[27,677,678,686,692],{},[30,679,680,683,684,223],{},[33,681,682],{},"Switch to the VRS mountpoint."," VRS generates a virtual reference station around 1–2 km from you. Enable GGA and connect to ",[44,685,322],{},[30,687,688,691],{},[33,689,690],{},"Check the sourcetable distance."," If the nearest physical station is more than 25 km away, VRS is normally the better choice.",[30,693,694,697],{},[33,695,696],{},"Use a dual-frequency receiver."," Single-frequency receivers are usually limited to baselines of around 10 km before ionospheric errors prevent Fix.",[12,699,701],{"id":700},"cause-5-ionospheric-disturbance","Cause 5 — Ionospheric disturbance",[75,703,708,711],{"additionalstyles":23,"frequency":704,"icon":705,"level":706,"title":707},"Periodic — peaks during solar maximum","icons\u002FSun.svg","2","High solar activity disrupting carrier-phase signals",[17,709,710],{},"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.",[27,712,713,719,725,731],{},[30,714,715,718],{},[33,716,717],{},"Work early morning or evening."," Ionospheric activity is typically lowest during the first two hours after sunrise and later in the evening.",[30,720,721,724],{},[33,722,723],{},"Switch to VRS."," Network-wide ionospheric modelling partially compensates for elevated ionospheric noise.",[30,726,727,730],{},[33,728,729],{},"Check space weather."," A Kp index above 5 often causes RTK problems. Postponing work until the storm passes may be the only reliable option.",[30,732,733,736],{},[33,734,735],{},"Use a triple-frequency receiver."," L5 signals are more robust to ionospheric noise than L1\u002FL2 and can maintain Fix in more difficult conditions.",[12,738,740],{"id":739},"cause-6-receiver-or-software-settings","Cause 6 — Receiver or software settings",[75,742,746,749],{"additionalstyles":23,"frequency":743,"icon":744,"level":706,"title":745},"Less common but easy to fix","icons\u002FCog.svg","Conservative defaults preventing ambiguity resolution",[17,747,748],{},"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.",[27,750,751,757,763,769],{},[30,752,753,756],{},[33,754,755],{},"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.",[30,758,759,762],{},[33,760,761],{},"Enable all constellations."," GPS, GLONASS, Galileo and BeiDou together provide much more redundancy than GPS alone.",[30,764,765,768],{},[33,766,767],{},"Reduce update rate to 1–5 Hz."," In a weak environment, reducing the rate gives the RTK engine more averaging time per epoch.",[30,770,771,774],{},[33,772,773],{},"Set the minimum elevation mask to 10°."," Higher masks can exclude useful satellites and weaken satellite geometry.",[12,776,271],{"id":270},[17,778,779],{},"Select your device for targeted advice:",[276,781,783,810,836,861,875],{"additionalstyles":23,"default-tab":278,"items":782},"Emlid|DJI|Trimble|SW Maps|u-blox \u002F DIY",[281,784,785,799,807],{"name":278},[17,786,787,790,791,794,795,798],{},[33,788,789],{},"Most effective fix for Emlid stuck on Float:"," go to ",[33,792,793],{},"Settings → GNSS settings → Ambiguity resolution"," and change from Continuous to ",[33,796,797],{},"Fix-and-hold",". This single setting resolves persistent Float in challenging environments for many Emlid users.",[17,800,801,802,804,805,223],{},"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 ",[44,803,322],{}," and enable ",[33,806,249],{},[17,808,809],{},"Firmware updates can reset GNSS settings to their defaults. Re-check constellation and ambiguity settings after every update.",[281,811,812,824,827,833],{"name":308},[17,813,814,817,818,820,821,823],{},[33,815,816],{},"DJI stuck on Float is almost always MSM4 instead of MSM5."," Change the mountpoint to ",[44,819,318],{}," in DJI Pilot under ",[33,822,314],{},", then disconnect and reconnect.",[17,825,826],{},"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.",[17,828,829,830,832],{},"For long-baseline flights beyond 30 km, try ",[44,831,322],{},". DJI handles VRS well and the shorter effective baseline improves Fix stability.",[17,834,835],{},"On the DJI M300 and Matrice 350, also check that the RTK antenna is firmly seated and its cable is undamaged.",[281,837,839,849,855,858],{"name":838},"Trimble",[17,840,841,844,845,848],{},[33,842,843],{},"For Trimble stuck on Float",", first verify that the data link is active under ",[33,846,847],{},"Instrument → Receiver Status → Data Link",". The bytes counter must be incrementing.",[17,850,851,852,854],{},"For long-baseline work, switch to ",[44,853,322],{},". Trimble Access sends GGA automatically when NTRIP is active.",[17,856,857],{},"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.",[17,859,860],{},"The Trimble R10 works correctly with MSM4. If an R10 remains on Float, investigate the environment or baseline rather than the mountpoint format.",[281,862,863,869,872],{"name":326},[17,864,865,868],{},[33,866,867],{},"SW Maps stuck on Float usually means the external receiver is the bottleneck."," SW Maps displays the solution supplied by the connected receiver.",[17,870,871],{},"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.",[17,873,874],{},"A smartphone's internal single-frequency GNSS chip rarely reaches Fix. For centimetre accuracy, connect a multi-band external receiver.",[281,876,878,884,887],{"name":877},"u-blox \u002F DIY",[17,879,880,883],{},[33,881,882],{},"A u-blox ZED-F9P normally reaches Fix reliably within a 10–30 km baseline."," Beyond that, ionospheric decorrelation can prevent Fix without VRS.",[17,885,886],{},"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.",[17,888,889],{},"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.",[21,891,893],{"additionalstyles":23,"color":24,"title":892},"Still on Float after all of the above?",[17,894,895],{},"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":476,"searchDepth":477,"depth":477,"links":897},[898,899,900,901,902,903,904,905],{"id":517,"depth":477,"text":518},{"id":554,"depth":477,"text":555},{"id":591,"depth":477,"text":592},{"id":628,"depth":477,"text":629},{"id":666,"depth":477,"text":667},{"id":700,"depth":477,"text":701},{"id":739,"depth":477,"text":740},{"id":270,"depth":477,"text":271},"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.",{},"2026-07-24",[911],"\u002Fen\u002Flearn\u002Ffloat-vs-fix",{"title":505,"description":907},"en\u002Ftroubleshooting\u002Fstuck-on-float","cZuzVDxMmVc2t9_jfIEzEmwmUVVTUPbWnughCbX8Y_Y",{"id":916,"title":917,"author":7,"body":918,"category":1333,"cover":1334,"description":1335,"extension":489,"meta":1336,"navigation":491,"path":496,"publishedAt":493,"relatedArticles":1337,"seo":1340,"stem":1341,"updatedAt":499,"__hash__":1342},"knowledge_en\u002Fen\u002Flearn\u002Fwhat-is-gga.md","What is GGA and why do I need to enable it?",{"type":9,"value":919,"toc":1322},[920,924,931,939,942,946,949,952,1034,1039,1042,1153,1159,1163,1197,1201,1221,1225,1228,1300,1304],[12,921,923],{"id":922},"what-gga-is","What GGA is",[17,925,926,927,930],{},"GGA stands for ",[33,928,929],{},"Global Positioning System Fix Data",". It is one of several standardised NMEA 0183 sentences — short text strings that GPS and GNSS receivers use to report position and status information. You have probably seen NMEA sentences if you have ever looked at raw receiver output: they begin with a dollar sign and are comma-separated.",[17,932,933,934,938],{},"In the context of NTRIP, GGA has a specific role: it is the sentence your device sends ",[935,936,937],"em",{},"to the server"," — in the opposite direction from the correction data — to tell the server where you are. This is unusual because most NTRIP communication is one-way (server to rover), but VRS requires this two-way exchange.",[17,940,941],{},"GGA does not need to be accurate to centimetre level for NTRIP to work correctly. A Single or Float solution position — accurate to a few metres — is more than sufficient. The server only needs to know which part of the network you are in, not your exact position.",[12,943,945],{"id":944},"what-a-gga-sentence-contains","What a GGA sentence contains",[17,947,948],{},"A typical GGA sentence looks like this. Each comma-separated field carries a specific piece of information:",[225,950],{"additionalstyles":227,"items":951},"Example GGA sentence|$GPGGA,123519,5230.000,N,00452.000,E,4,09,0.9,25.4,M,46.9,M,,*47",[359,953,954,963],{},[362,955,956],{},[365,957,958,961],{},[368,959,960],{},"Field",[368,962,373],{},[378,964,965,975,985,995,1004,1014,1024],{},[365,966,967,972],{},[383,968,969],{},[44,970,971],{},"123519",[383,973,974],{},"UTC time — 12:35:19",[365,976,977,982],{},[383,978,979],{},[44,980,981],{},"5230.000,N",[383,983,984],{},"Latitude — 52° 30.000' North (Netherlands)",[365,986,987,992],{},[383,988,989],{},[44,990,991],{},"00452.000,E",[383,993,994],{},"Longitude — 4° 52.000' East",[365,996,997,1001],{},[383,998,999],{},[44,1000,106],{},[383,1002,1003],{},"Fix quality — 4 = RTK Fixed (see table below)",[365,1005,1006,1011],{},[383,1007,1008],{},[44,1009,1010],{},"09",[383,1012,1013],{},"Number of satellites in use",[365,1015,1016,1021],{},[383,1017,1018],{},[44,1019,1020],{},"0.9",[383,1022,1023],{},"HDOP — horizontal dilution of precision",[365,1025,1026,1031],{},[383,1027,1028],{},[44,1029,1030],{},"25.4,M",[383,1032,1033],{},"Altitude above mean sea level in metres",[1035,1036,1038],"h3",{"id":1037},"fix-quality-values","Fix quality values",[17,1040,1041],{},"The fix quality field in GGA tells the NTRIP server — and any other system reading the output — what kind of position solution your receiver currently has:",[359,1043,1044,1059],{},[362,1045,1046],{},[365,1047,1048,1051,1053,1056],{},[368,1049,1050],{},"Value",[368,1052,373],{},[368,1054,1055],{},"Typical accuracy",[368,1057,1058],{},"Suitable for VRS?",[378,1060,1061,1077,1093,1108,1123,1137],{},[365,1062,1063,1068,1071,1074],{},[383,1064,1065],{},[44,1066,1067],{},"0",[383,1069,1070],{},"No fix",[383,1072,1073],{},"—",[383,1075,1076],{},"No — position is invalid",[365,1078,1079,1084,1087,1090],{},[383,1080,1081],{},[44,1082,1083],{},"1",[383,1085,1086],{},"GPS fix (Single)",[383,1088,1089],{},"2–5 m",[383,1091,1092],{},"Yes — good enough to locate in network",[365,1094,1095,1099,1102,1105],{},[383,1096,1097],{},[44,1098,706],{},[383,1100,1101],{},"DGPS fix",[383,1103,1104],{},"0.5–2 m",[383,1106,1107],{},"Yes",[365,1109,1110,1114,1117,1120],{},[383,1111,1112],{},[44,1113,106],{},[383,1115,1116],{},"RTK Fixed",[383,1118,1119],{},"1–3 cm",[383,1121,1122],{},"Yes — best quality GGA",[365,1124,1125,1129,1132,1135],{},[383,1126,1127],{},[44,1128,79],{},[383,1130,1131],{},"RTK Float",[383,1133,1134],{},"0.1–1 m",[383,1136,1107],{},[365,1138,1139,1144,1147,1150],{},[383,1140,1141],{},[44,1142,1143],{},"6",[383,1145,1146],{},"Dead reckoning",[383,1148,1149],{},"Variable",[383,1151,1152],{},"Depends on accuracy",[21,1154,1156],{"additionalstyles":23,"color":146,"title":1155},"You do not need Fix before sending GGA",[17,1157,1158],{},"A common misunderstanding is that GGA only works when you already have RTK Fix. In fact, a Single solution (quality 1) is perfectly sufficient. Send GGA as soon as your receiver has any valid position — this allows VRS to start generating corrections, which then helps you get Fix.",[12,1160,1162],{"id":1161},"how-gga-enables-vrs","How GGA enables VRS",[1164,1165,1166,1173,1179,1185,1191],"stepper",{"additionalstyles":23},[1167,1168,1170],"stepper-item",{"marker":1083,"title":1169},"Your receiver gets a rough position",[17,1171,1172],{},"Within 30–60 seconds of powering on outdoors, your receiver acquires satellite signals and computes a Single solution — typically accurate to 2–5 metres. This is enough.",[1167,1174,1176],{"marker":706,"title":1175},"Your NTRIP client sends GGA to the server",[17,1177,1178],{},"Your client connects to the VRS mountpoint and immediately sends the GGA sentence containing your rough position. Most clients send GGA once on connection and then again every 10–60 seconds to account for movement.",[1167,1180,1182],{"marker":237,"title":1181},"The server identifies your location in the network",[17,1183,1184],{},"The VRS server reads the latitude and longitude from your GGA sentence and determines which surrounding physical reference stations apply to your area. This computation takes less than a second.",[1167,1186,1188],{"marker":106,"title":1187},"A virtual station is generated near you",[17,1189,1190],{},"The server synthesises an RTCM3 correction stream as if a base station existed 1–2 km from your position. It starts streaming this data back to your client immediately.",[1167,1192,1194],{"marker":79,"title":1193},"Your receiver achieves RTK Fixed",[17,1195,1196],{},"With local-quality corrections flowing, your receiver resolves carrier phase ambiguities and reaches Fixed — typically within 10–60 seconds in good sky conditions.",[12,1198,1200],{"id":1199},"when-gga-is-required-vs-optional","When GGA is required vs optional",[1202,1203,1204,1209,1213,1217],"cards",{"additionalstyles":23},[1205,1206],"cards-item",{"text":1207,"title":1208},"Any mountpoint labelled VRS, MAC or a similar network correction type. The server cannot generate a virtual station without your position.","GGA required — VRS mountpoints",[1205,1210],{"text":1211,"title":1212},"Some NTRIP services select the closest physical station automatically based on your GGA position, rather than requiring you to choose a mountpoint manually.","GGA required — nearest-station auto-selection",[1205,1214],{"text":1215,"title":1216},"When connecting to a fixed mountpoint like RTCM3_NL, the server streams corrections regardless of whether GGA is sent. You can enable GGA for logging purposes but it is not used.","GGA optional — standard single-station mountpoints",[1205,1218],{"text":1219,"title":1220},"When using your own base-rover configuration without NTRIP, GGA is not involved in the correction exchange at all.","GGA optional — own base station setups",[12,1222,1224],{"id":1223},"how-to-enable-gga-on-your-device","How to enable GGA on your device",[17,1226,1227],{},"The setting name varies between NTRIP clients, but the function is the same on all of them.",[276,1229,1231,1243,1256,1265,1275,1284,1294],{"additionalstyles":23,"items":1230},"Emlid Flow|SW Maps|FieldGenius|Trimble Access|DJI Pilot 2|Lefebure NTRIP|Leica Captivate",[281,1232,1234],{"name":1233},"Emlid Flow",[17,1235,1236,1237,1239,1240,1242],{},"In ",[33,1238,291],{},", select your VRS mountpoint and enable ",[33,1241,249],{},". Connect after the receiver has a valid Single solution.",[281,1244,1245],{"name":326},[17,1246,1247,1248,1251,1252,1255],{},"Go to ",[33,1249,1250],{},"Settings → NTRIP Client",", select the VRS mountpoint and enable ",[33,1253,1254],{},"Transmit GGA"," before connecting.",[281,1257,1259],{"name":1258},"FieldGenius",[17,1260,1247,1261,1264],{},[33,1262,1263],{},"Set Up Corrections → RTK via Internet",". Select the VRS source and enable GGA transmission in the data-link settings.",[281,1266,1268],{"name":1267},"Trimble Access",[17,1269,1270,1271,1274],{},"Enter the VRS mountpoint in ",[33,1272,1273],{},"Survey Style → Rover radio",". Trimble Access sends GGA automatically while NTRIP is active.",[281,1276,1278],{"name":1277},"DJI Pilot 2",[17,1279,1280,1281,1283],{},"Enter the VRS mountpoint under ",[33,1282,314],{},". DJI sends GGA automatically after it has GPS lock, so configure it outdoors.",[281,1285,1287],{"name":1286},"Lefebure NTRIP",[17,1288,1289,1290,1293],{},"Enter the caster host, port and VRS mountpoint. Enable ",[33,1291,1292],{},"Send GGA"," and select the receiver or internal GPS as the GGA source.",[281,1295,1297],{"name":1296},"Leica Captivate",[17,1298,1299],{},"In the internet connection or rover settings, select the VRS mountpoint and enable NMEA GGA output to the NTRIP caster.",[12,1301,1303],{"id":1302},"gga-troubleshooting","GGA troubleshooting",[1202,1305,1306,1310,1314,1318],{"additionalstyles":23},[1205,1307],{"text":1308,"title":1309},"The connection is established but no corrections are flowing. This almost always means GGA is not being sent — or is being sent with quality 0 (no fix). Enable GGA, ensure the receiver has at least a Single solution, then reconnect.","Connected to VRS but 0 bytes per second",[1205,1311],{"text":1312,"title":1313},"If corrections are flowing but Fix takes many minutes, the GGA position may have had low quality at connection time. Disconnect, wait for a better Single solution outdoors, then reconnect.","GGA sent but Fix is very slow",[1205,1315],{"text":1316,"title":1317},"Most NTRIP clients send GGA periodically — every 5–60 seconds. The server receives updated positions and adjusts the virtual station to follow you. You do not need to reconnect when moving around the network coverage area.","Moving between areas — does GGA update?",[1205,1319],{"text":1320,"title":1321},"GGA contains only your approximate position, altitude, satellite count and fix quality. It contains no personal identifiers; the NTRIP server uses it only to route corrections.","Privacy note",{"title":476,"searchDepth":477,"depth":477,"links":1323},[1324,1325,1329,1330,1331,1332],{"id":922,"depth":477,"text":923},{"id":944,"depth":477,"text":945,"children":1326},[1327],{"id":1037,"depth":1328,"text":1038},3,{"id":1161,"depth":477,"text":1162},{"id":1199,"depth":477,"text":1200},{"id":1223,"depth":477,"text":1224},{"id":1302,"depth":477,"text":1303},"learn","learn\u002Fwhat-is-gga.webp","GGA is a short position message your device sends to the NTRIP server. For standard mountpoints it is optional. For VRS mountpoints it is mandatory — without it the server cannot generate corrections and streams nothing back. This is the single most common reason VRS appears to connect but delivers no Fix.",{},[1338,1339],"\u002Fen\u002Flearn\u002Fwhat-is-vrs","\u002Fen\u002Flearn\u002Fwhat-is-ntrip",{"title":917,"description":1335},"en\u002Flearn\u002Fwhat-is-gga","HFG0RJGp9bO8FHQR5HkzNRVEiSqOCSmiRVEfH3EUQ58",1787304715420]