[{"data":1,"prerenderedAt":1241},["ShallowReactive",2],{"knowledge-page-en-\u002Fsetup\u002Femlid-rs2-plus-ntrip":3},{"article":4,"posts":491,"relatedPosts":492},{"id":5,"title":6,"author":7,"body":8,"category":476,"cover":477,"description":478,"extension":479,"meta":480,"navigation":481,"path":482,"publishedAt":483,"relatedArticles":484,"seo":487,"stem":488,"updatedAt":489,"__hash__":490},"knowledge_en\u002Fen\u002Fsetup\u002Femlid-rs2-plus-ntrip.md","How to set up Emlid Reach RS2+ with NTRIP corrections","Wilko",{"type":9,"value":10,"toc":464},"minimark",[11,16,47,56,60,97,109,113,133,137,161,165,202,206,262,266,269,309,313,458],[12,13,15],"h2",{"id":14},"before-you-start","Before you start",[17,18,20,27,32,37,42],"requirements",{"additionalstyles":19},"mt-[30px]",[21,22,23],"requirement-item",{},[24,25,26],"p",{},"Emlid Reach RS2+ fully charged (or connected to power via USB-C)",[21,28,29],{},[24,30,31],{},"Emlid Flow app installed on your phone — Android or iOS, latest version",[21,33,34],{},[24,35,36],{},"NTRIP credentials: host address, port number, mountpoint name, username and password",[21,38,39],{},[24,40,41],{},"Mobile data on your phone, or a Wi-Fi connection with internet access",[21,43,44],{},[24,45,46],{},"Clear sky view — go outside before connecting",[48,49,53],"card",{"additionalstyles":50,"color":51,"title":52},"mt-[60px]","primary","RS2+ vs RS3 vs RS4",[24,54,55],{},"The steps in this guide apply to the entire Emlid Reach RS family — RS2+, RS3 and RS4 all use the same Emlid Flow app and the same NTRIP setup process. The only difference is that the RS3 and RS4 support additional constellations and frequencies. Select your exact model when prompted in Emlid Flow for the correct antenna calibration.",[12,57,59],{"id":58},"step-1-power-on-and-connect-in-emlid-flow","Step 1 — Power on and connect in Emlid Flow",[61,62,63,71,90],"stepper",{"additionalstyles":50},[64,65,68],"stepper-item",{"marker":66,"title":67},"1","Power on the RS2+",[24,69,70],{},"Press and hold the power button until the LED indicator turns on. The RS2+ boots in approximately 20 seconds. During boot the LED pulses white, then settles into a steady or slow-pulsing blue — indicating it is broadcasting a Wi-Fi hotspot.",[64,72,75,87],{"marker":73,"title":74},"2","Connect your phone to the RS2+ hotspot",[24,76,77,78,82,83,86],{},"Go to your phone's Wi-Fi settings and connect to the RS2+ hotspot — named something like ",[79,80,81],"code",{},"reach:xx:xx",". The default password is ",[79,84,85],{},"emlidreach",".",[24,88,89],{},"Alternatively, if you have already paired the RS2+ to your phone's hotspot in a previous session, turn on your phone's hotspot first and the RS2+ will connect to it automatically. This is the preferred setup for field use because the phone retains its mobile data connection.",[64,91,94],{"marker":92,"title":93},"3","Open Emlid Flow and connect to the receiver",[24,95,96],{},"Open Emlid Flow. The app automatically discovers RS2+ units on the same network. Tap your receiver in the device list to connect. The main screen shows satellite count, solution status and battery level.",[48,98,101],{"additionalstyles":50,"color":99,"title":100},"green","Use phone hotspot for field work",[24,102,103,104,108],{},"Connect the RS2+ to your phone's hotspot rather than using the RS2+ as the hotspot. This way the phone keeps its mobile data connection and the RS2+ uses it for NTRIP — one connection handles everything. In Emlid Flow, go to ",[105,106,107],"strong",{},"Settings → Wi-Fi"," on the receiver to add your phone hotspot as a known network.",[12,110,112],{"id":111},"step-2-configure-correction-input","Step 2 — Configure correction input",[61,114,115],{"additionalstyles":50},[64,116,119,126],{"marker":117,"title":118},"4","Open Correction input",[24,120,121,122,125],{},"In Emlid Flow, tap the ",[105,123,124],{},"Correction input"," tab (the antenna icon at the bottom of the screen, or in the receiver settings). This is where you configure how the RS2+ receives RTK corrections.",[24,127,128,129,132],{},"Set the source to ",[105,130,131],{},"NTRIP",". Other options — LoRa radio and Bluetooth — are used for base-rover setups and are not relevant for NTRIP.",[12,134,136],{"id":135},"step-3-enter-ntrip-credentials","Step 3 — Enter NTRIP credentials",[61,138,139],{"additionalstyles":50},[64,140,143,150,155],{"marker":141,"title":142},"5","Add a new NTRIP profile",[24,144,145,146,149],{},"Tap ",[105,147,148],{},"Add profile"," (or edit an existing one). Fill in the connection details from your correction service. For RTKsub:",[151,152],"terminal-box",{"additionalstyles":153,"items":154},"mt-[24px]","Host|ntrip.rtksub.com||Port|2101||Username|your username||Password|your password",[24,156,145,157,160],{},[105,158,159],{},"Request mountpoints",". Emlid Flow connects to the server and retrieves the list of available mountpoints.",[12,162,164],{"id":163},"step-4-select-mountpoint","Step 4 — Select mountpoint",[61,166,167,184],{"additionalstyles":50},[64,168,171,174,177],{"marker":169,"title":170},"6","Choose the right mountpoint for your RS2+",[24,172,173],{},"From the sourcetable, select the mountpoint that matches your situation:",[151,175],{"additionalstyles":153,"items":176},"Standard (\u003C30 km)|RTCM3_NL||Long baseline (>30 km)|RTCM3_NL_VRS||High-end survey|RTCM3_NL_MSM7 (works, but MSM4 is sufficient)",[24,178,179,180,183],{},"The RS2+ processes MSM4 and MSM7 equally well. Start with ",[105,181,182],{},"RTCM3_NL"," (MSM4). Only switch to VRS if your working area is more than 30 km from the nearest physical reference station.",[64,185,188,199],{"marker":186,"title":187},"7","Enable GGA if using VRS",[24,189,190,191,194,195,198],{},"If you selected ",[105,192,193],{},"RTCM3_NL_VRS",", enable the ",[105,196,197],{},"Send GGA to caster"," toggle. This sends your approximate position to the server so it can generate a virtual station near you. Without it, VRS returns zero data.",[24,200,201],{},"For standard mountpoints like RTCM3_NL, GGA is optional — leave the toggle off.",[12,203,205],{"id":204},"step-5-connect-and-verify-rtk-fix","Step 5 — Connect and verify RTK Fix",[61,207,208,221],{"additionalstyles":50},[64,209,212,218],{"marker":210,"title":211},"8","Tap Connect and go outside",[24,213,145,214,217],{},[105,215,216],{},"Connect",". Emlid Flow connects to the NTRIP server and begins streaming corrections to the RS2+. The correction counter (bytes per second) in the Correction input tab should start incrementing — confirming data is flowing.",[24,219,220],{},"Make sure you are outside with a clear sky view. The RS2+ cannot achieve RTK Fix indoors or under heavy canopy.",[64,222,225,228,259],{"marker":223,"title":224},"9","Watch the solution status",[24,226,227],{},"The solution status progresses through three stages:",[229,230,231,256],"solution-status-showcase",{"additionalstyles":153},[232,233,234,242,249],"solution-statuses",{},[235,236,239],"solution-status",{"status":237,"title":238},"single","Single",[24,240,241],{},"Satellite lock, no corrections yet. Accuracy 2–5 m.",[235,243,246],{"status":244,"title":245},"float","Float",[24,247,248],{},"Corrections received, ambiguities not yet resolved. Accuracy 0.1–1 m.",[235,250,253],{"status":251,"title":252},"fixed","Fixed",[24,254,255],{},"Full RTK Fix. Centimetre accuracy. Ready to work.",[257,258],"emlid-flow-status",{},[24,260,261],{},"In good sky conditions with a nearby reference station, Fix typically arrives within 10–60 seconds. If it takes longer, see the troubleshooting section below.",[12,263,265],{"id":264},"step-6-use-with-field-software","Step 6 — Use with field software",[24,267,268],{},"Once the RS2+ has RTK Fix, connect it to your survey or mapping software to collect and stake out points.",[270,271,273,291,297,303],"device-tabs",{"additionalstyles":50,"items":272},"Emlid Flow survey|FieldGenius|SW Maps|QField",[274,275,277,284],"device-tab",{"name":276},"Emlid Flow survey",[24,278,279,280,283],{},"Emlid Flow includes a built-in survey module. Once Fix is achieved, tap ",[105,281,282],{},"Survey"," at the bottom of the screen to start collecting points, lines and areas. Set the antenna height (to the bottom of the receiver), configure your coordinate system and begin.",[24,285,286,287,290],{},"For stakeout, tap ",[105,288,289],{},"Stakeout"," and import your design points from a CSV or DXF file. Emlid Flow guides you to each point with a real-time directional indicator.",[274,292,294],{"name":293},"FieldGenius",[24,295,296],{},"Connect the RS2+ to your controller over Wi-Fi or Bluetooth, then configure it as the active GNSS receiver in the instrument settings. The RS2+ supplies the RTK position once it has Fixed.",[274,298,300],{"name":299},"SW Maps",[24,301,302],{},"Connect the RS2+ as a Bluetooth GNSS receiver in SW Maps. Keep NTRIP configured in Emlid Flow, then use the Fixed solution from the receiver in the mapping app.",[274,304,306],{"name":305},"QField",[24,307,308],{},"Configure the RS2+ as the external GNSS receiver and select the correct coordinate reference system for the project. Verify that QField reports RTK Fixed before collecting data.",[12,310,312],{"id":311},"troubleshooting","Troubleshooting",[314,315,316,332],"table",{},[317,318,319],"thead",{},[320,321,322,326,329],"tr",{},[323,324,325],"th",{},"Problem",[323,327,328],{},"Likely cause",[323,330,331],{},"Fix",[333,334,335,361,374,390,406,419,432,445],"tbody",{},[320,336,337,343,346],{},[338,339,340],"td",{},[105,341,342],{},"Cannot request mountpoints",[338,344,345],{},"No internet on RS2+, wrong host or port",[338,347,348,349,352,353,356,357,360],{},"Ensure RS2+ is connected to a network with internet (your phone hotspot). Verify host is ",[79,350,351],{},"ntrip.rtksub.com",", port ",[79,354,355],{},"2101",". No ",[79,358,359],{},"http:\u002F\u002F"," prefix.",[320,362,363,368,371],{},[338,364,365],{},[105,366,367],{},"Credentials rejected",[338,369,370],{},"Wrong username or password",[338,372,373],{},"Copy-paste credentials from your RTKsub account dashboard. Check for leading or trailing spaces.",[320,375,376,381,384],{},[338,377,378],{},[105,379,380],{},"Connected but 0 bytes\u002Fsec",[338,382,383],{},"VRS mountpoint with no GGA sent",[338,385,386,387,389],{},"Enable ",[105,388,197],{}," in the NTRIP profile. Wait for a Single solution before connecting.",[320,391,392,397,400],{},[338,393,394],{},[105,395,396],{},"Stuck on Float for more than 3 minutes",[338,398,399],{},"Long baseline, obstructions or high PDOP",[338,401,402,403,405],{},"Switch to ",[79,404,193],{}," with GGA enabled. Move to open sky. Check satellite count — it should be 20+.",[320,407,408,413,416],{},[338,409,410],{},[105,411,412],{},"Fix drops when moving",[338,414,415],{},"Obstructions or multipath",[338,417,418],{},"Hold pole vertical. Move away from trees and buildings. Lower elevation mask to 10° in Emlid Flow GNSS settings.",[320,420,421,426,429],{},[338,422,423],{},[105,424,425],{},"Coordinates offset by 0.5–2 m",[338,427,428],{},"Datum transformation not applied",[338,430,431],{},"For Netherlands: verify RDNAPTRANS™ 2018 is applied in your job's coordinate system.",[320,433,434,439,442],{},[338,435,436],{},[105,437,438],{},"Heights wrong by ~40 m",[338,440,441],{},"Ellipsoidal height, no geoid model",[338,443,444],{},"Apply NLGEO2018 in the coordinate system settings. Ellipsoidal height differs from NAP by 38–44 m.",[320,446,447,452,455],{},[338,448,449],{},[105,450,451],{},"RS2+ not found in Emlid Flow",[338,453,454],{},"Not on the same network",[338,456,457],{},"Connect your phone to the RS2+ hotspot, or ensure both are on the same Wi-Fi network. Restart Emlid Flow.",[48,459,461],{"additionalstyles":50,"color":99,"title":460},"Save the profile for next time",[24,462,463],{},"Once your NTRIP profile is configured and working, Emlid Flow saves it automatically. On your next job, simply tap the profile, tap Connect, and you are ready. The entire process takes under 30 seconds from power-on to Fix in good conditions.",{"title":465,"searchDepth":466,"depth":466,"links":467},"",2,[468,469,470,471,472,473,474,475],{"id":14,"depth":466,"text":15},{"id":58,"depth":466,"text":59},{"id":111,"depth":466,"text":112},{"id":135,"depth":466,"text":136},{"id":163,"depth":466,"text":164},{"id":204,"depth":466,"text":205},{"id":264,"depth":466,"text":265},{"id":311,"depth":466,"text":312},"setup","Setup\u002FWebP\u002Fhow-to-set-up-emlid-reach-rs2-with-ntrip_corrections.webp","The Emlid Reach RS2+ connects to any NTRIP correction service in under two minutes using Emlid Flow. This guide walks you through every step — from first power-on to RTK Fixed — and covers the most common pitfalls along the way.","md",{},true,"\u002Fen\u002Fsetup\u002Femlid-rs2-plus-ntrip","2026-07-25",[485,486],"\u002Fen\u002Flearn\u002Fwhich-mountpoint","\u002Fen\u002Flearn\u002Fwhat-is-gga",{"title":6,"description":478},"en\u002Fsetup\u002Femlid-rs2-plus-ntrip",null,"BEnKdnEqnm26SzakMq9eM0jRXyyHkvSt5H0soTm3ORM",[],[493,820],{"id":494,"title":495,"author":496,"body":497,"category":810,"cover":811,"description":812,"extension":479,"meta":813,"navigation":481,"path":485,"publishedAt":483,"relatedArticles":814,"seo":817,"stem":818,"updatedAt":489,"__hash__":819},"knowledge_en\u002Fen\u002Flearn\u002Fwhich-mountpoint.md","Which NTRIP mountpoint should I choose?","Yuri",{"type":9,"value":498,"toc":803},[499,503,506,526,530,533,551,555,658,666,670,673,752,761,765,776,787,797],[12,500,502],{"id":501},"quick-mountpoint-finder","Quick mountpoint finder",[24,504,505],{},"Choose by device first, then use VRS whenever the nearest reference station is more than 30 km away or Fix is unstable.",[507,508,509,514,518,522],"cards",{"additionalstyles":50},[510,511],"cards-item",{"text":512,"title":513},"Use MSM4 for Emlid Reach RS \u002F RX, u-blox ZED-F9P, SW Maps, FieldGenius and most generic NTRIP clients.","Most devices within 30 km → RTCM3_NL",[510,515],{"text":516,"title":517},"DJI requires MSM5 Doppler observations to initialise Fix. Do not use the MSM4 default mountpoint for DJI.","Any DJI RTK drone → RTCM3_NL_MSM5",[510,519],{"text":520,"title":521},"MSM7 supplies extended-precision observations that high-end survey receivers can use.","Trimble, Leica or high-end survey → RTCM3_NL_MSM7",[510,523],{"text":524,"title":525},"VRS shortens the effective baseline to 1–2 km. Enable GGA transmission before connecting.","Any device beyond 30 km → RTCM3_NL_VRS",[12,527,529],{"id":528},"all-mountpoints-explained","All mountpoints explained",[24,531,532],{},"RTKsub exposes four mountpoints. Each is optimised for a different combination of device type and working distance.",[507,534,535,539,543,547],{"additionalstyles":50},[510,536],{"text":537,"title":538},"The standard mountpoint. Delivers RTCM3 corrections in MSM4 format — compact, efficient and compatible with virtually every modern RTK receiver. Includes GPS, GLONASS, Galileo and BeiDou on all frequencies. Use it within 30 km when your device is not a DJI drone or a high-end survey receiver.","RTCM3_NL — MSM4",[510,540],{"text":541,"title":542},"MSM5 adds Doppler observations to the standard MSM4 data. DJI's RTK implementation specifically requires Doppler to initialise correctly. Outside DJI, MSM5 is rarely needed because standard devices perform identically on MSM4 and MSM5.","RTCM3_NL_MSM5 — MSM5",[510,544],{"text":545,"title":546},"MSM7 provides the same observations as MSM4 but at full extended precision. Trimble, Leica, Septentrio and NovAtel receivers can use this extra precision, particularly in challenging baselines and environments. It uses roughly twice the bandwidth of MSM4.","RTCM3_NL_MSM7 — MSM7",[510,548],{"text":549,"title":550},"VRS generates a virtual reference station 1–2 km from your rover using data from multiple surrounding physical stations. Fix initialisation is faster and Fix stability is higher. Send GGA to the caster or the stream returns zero bytes.","RTCM3_NL_VRS — VRS MSM4",[12,552,554],{"id":553},"side-by-side-comparison","Side-by-side comparison",[314,556,557,579],{},[317,558,559],{},[320,560,561,564,567,570,573,576],{},[323,562,563],{},"Mountpoint",[323,565,566],{},"MSM level",[323,568,569],{},"GGA required",[323,571,572],{},"DJI works",[323,574,575],{},"Trimble \u002F Leica best",[323,577,578],{},"Use when",[333,580,581,600,620,639],{},[320,582,583,587,590,593,595,597],{},[338,584,585],{},[79,586,182],{},[338,588,589],{},"MSM4",[338,591,592],{},"No",[338,594,592],{},[338,596,592],{},[338,598,599],{},"Default for most devices, baseline \u003C30 km",[320,601,602,607,610,612,615,617],{},[338,603,604],{},[79,605,606],{},"RTCM3_NL_MSM5",[338,608,609],{},"MSM5",[338,611,592],{},[338,613,614],{},"Yes",[338,616,592],{},[338,618,619],{},"DJI drones only",[320,621,622,627,630,632,634,636],{},[338,623,624],{},[79,625,626],{},"RTCM3_NL_MSM7",[338,628,629],{},"MSM7",[338,631,592],{},[338,633,592],{},[338,635,614],{},[338,637,638],{},"Trimble, Leica, high-end survey",[320,640,641,645,648,650,653,655],{},[338,642,643],{},[79,644,193],{},[338,646,647],{},"MSM4 + VRS",[338,649,614],{},[338,651,652],{},"Yes*",[338,654,614],{},[338,656,657],{},"Baseline >30 km or Fix instability",[24,659,660,661,663,664,86],{},"*DJI on VRS: use ",[79,662,193],{}," for long-baseline DJI work. For short baselines, use ",[79,665,606],{},[12,667,669],{"id":668},"what-happens-with-the-wrong-mountpoint","What happens with the wrong mountpoint",[24,671,672],{},"The consequences of the wrong mountpoint depend on which way you get it wrong. None of them produce an obvious error message — which is why choosing correctly matters.",[314,674,675,688],{},[317,676,677],{},[320,678,679,682,685],{},[323,680,681],{},"Situation",[323,683,684],{},"Symptom",[323,686,687],{},"What is actually happening",[333,689,690,704,715,728,741],{},[320,691,692,698,701],{},[338,693,694,695,697],{},"DJI drone on ",[79,696,182],{}," (MSM4)",[338,699,700],{},"Stuck on Float indefinitely",[338,702,703],{},"DJI needs Doppler data (MSM5 minimum). MSM4 corrections flow but Fix never initialises.",[320,705,706,709,712],{},[338,707,708],{},"Any device on VRS without GGA",[338,710,711],{},"Connected, 0 bytes\u002Fsec",[338,713,714],{},"Server cannot generate a virtual station. The connection appears active but the stream is empty.",[320,716,717,722,725],{},[338,718,719,720],{},"Emlid on ",[79,721,626],{},[338,723,724],{},"Works fine — no problem",[338,726,727],{},"Emlid ignores the extra precision in MSM7. Slightly higher bandwidth, otherwise identical result.",[320,729,730,735,738],{},[338,731,732,733,697],{},"Trimble on ",[79,734,182],{},[338,736,737],{},"Fix achieved, slightly lower accuracy",[338,739,740],{},"Works correctly. Missing the extended precision that MSM7 provides — a marginal difference in most conditions.",[320,742,743,746,749],{},[338,744,745],{},"Any device, wrong region mountpoint",[338,747,748],{},"No corrections or very poor Fix",[338,750,751],{},"Corrections come from distant stations, so the baseline is huge.",[48,753,756],{"additionalstyles":50,"color":754,"title":755},"orange","The DJI mistake is the most common",[24,757,758,759,86],{},"The most frequent support question about mountpoints is: “My DJI drone connects fine but never reaches Fix.” The answer is almost always MSM4 instead of MSM5. If you fly DJI, always use ",[79,760,606],{},[12,762,764],{"id":763},"finding-mountpoints-in-the-sourcetable","Finding mountpoints in the sourcetable",[24,766,767,768,771,772,775],{},"Every NTRIP server publishes a sourcetable — a list of all available correction streams with metadata. Your NTRIP client usually has a ",[105,769,770],{},"Get Mountpoints"," or ",[105,773,774],{},"Download Source Table"," button that fetches and displays this list.",[24,777,778,779,782,783,786],{},"If you need to read the raw sourcetable, you can request it from any NTRIP server by connecting to the host address in a browser or with a tool like ",[79,780,781],{},"curl",". Each line starting with ",[79,784,785],{},"STR;"," is a mountpoint. The fields are semicolon-separated and include the mountpoint name, format, message types and coordinates of the reference station.",[48,788,790],{"additionalstyles":50,"color":51,"title":789},"Sort by distance in Trimble Access",[24,791,792,793,796],{},"When the sourcetable loads in Trimble Access, tap the sort button and choose ",[105,794,795],{},"Distance",". The nearest physical station appears at the top. If the nearest station is more than 30 km away, switch to the VRS mountpoint rather than the top result.",[48,798,800],{"additionalstyles":19,"color":99,"title":799},"Still unsure? Ask the AI.",[24,801,802],{},"If you have an unusual device or a situation not covered here, describe your device model, NTRIP client and intended work. You can then get a specific recommendation.",{"title":465,"searchDepth":466,"depth":466,"links":804},[805,806,807,808,809],{"id":501,"depth":466,"text":502},{"id":528,"depth":466,"text":529},{"id":553,"depth":466,"text":554},{"id":668,"depth":466,"text":669},{"id":763,"depth":466,"text":764},"learn","learn\u002Fwhich-ntrip-mountpoint-should-i-choose.webp","The right mountpoint depends on two things your device and your baseline. Choose the wrong one and you may get Float instead of Fix, or Fix without the accuracy your receiver is capable of.",{},[815,816],"\u002Fen\u002Flearn\u002Fwhat-is-rtcm","\u002Fen\u002Flearn\u002Fwhat-is-vrs",{"title":495,"description":812},"en\u002Flearn\u002Fwhich-mountpoint","2oy9yd-U6YpNzoth9z555eT4WEjXlUdxBk5m0gbX-Kc",{"id":821,"title":822,"author":496,"body":823,"category":810,"cover":1233,"description":1234,"extension":479,"meta":1235,"navigation":481,"path":486,"publishedAt":483,"relatedArticles":1236,"seo":1238,"stem":1239,"updatedAt":489,"__hash__":1240},"knowledge_en\u002Fen\u002Flearn\u002Fwhat-is-gga.md","What is GGA and why do I need to enable it?",{"type":9,"value":824,"toc":1222},[825,829,836,844,847,851,854,857,940,945,948,1056,1062,1066,1098,1102,1120,1124,1127,1200,1204],[12,826,828],{"id":827},"what-gga-is","What GGA is",[24,830,831,832,835],{},"GGA stands for ",[105,833,834],{},"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.",[24,837,838,839,843],{},"In the context of NTRIP, GGA has a specific role: it is the sentence your device sends ",[840,841,842],"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.",[24,845,846],{},"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,848,850],{"id":849},"what-a-gga-sentence-contains","What a GGA sentence contains",[24,852,853],{},"A typical GGA sentence looks like this. Each comma-separated field carries a specific piece of information:",[151,855],{"additionalstyles":19,"items":856},"Example GGA sentence|$GPGGA,123519,5230.000,N,00452.000,E,4,09,0.9,25.4,M,46.9,M,,*47",[314,858,859,869],{},[317,860,861],{},[320,862,863,866],{},[323,864,865],{},"Field",[323,867,868],{},"Meaning",[333,870,871,881,891,901,910,920,930],{},[320,872,873,878],{},[338,874,875],{},[79,876,877],{},"123519",[338,879,880],{},"UTC time — 12:35:19",[320,882,883,888],{},[338,884,885],{},[79,886,887],{},"5230.000,N",[338,889,890],{},"Latitude — 52° 30.000' North (Netherlands)",[320,892,893,898],{},[338,894,895],{},[79,896,897],{},"00452.000,E",[338,899,900],{},"Longitude — 4° 52.000' East",[320,902,903,907],{},[338,904,905],{},[79,906,117],{},[338,908,909],{},"Fix quality — 4 = RTK Fixed (see table below)",[320,911,912,917],{},[338,913,914],{},[79,915,916],{},"09",[338,918,919],{},"Number of satellites in use",[320,921,922,927],{},[338,923,924],{},[79,925,926],{},"0.9",[338,928,929],{},"HDOP — horizontal dilution of precision",[320,931,932,937],{},[338,933,934],{},[79,935,936],{},"25.4,M",[338,938,939],{},"Altitude above mean sea level in metres",[941,942,944],"h3",{"id":943},"fix-quality-values","Fix quality values",[24,946,947],{},"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:",[314,949,950,965],{},[317,951,952],{},[320,953,954,957,959,962],{},[323,955,956],{},"Value",[323,958,868],{},[323,960,961],{},"Typical accuracy",[323,963,964],{},"Suitable for VRS?",[333,966,967,983,998,1012,1027,1041],{},[320,968,969,974,977,980],{},[338,970,971],{},[79,972,973],{},"0",[338,975,976],{},"No fix",[338,978,979],{},"—",[338,981,982],{},"No — position is invalid",[320,984,985,989,992,995],{},[338,986,987],{},[79,988,66],{},[338,990,991],{},"GPS fix (Single)",[338,993,994],{},"2–5 m",[338,996,997],{},"Yes — good enough to locate in network",[320,999,1000,1004,1007,1010],{},[338,1001,1002],{},[79,1003,73],{},[338,1005,1006],{},"DGPS fix",[338,1008,1009],{},"0.5–2 m",[338,1011,614],{},[320,1013,1014,1018,1021,1024],{},[338,1015,1016],{},[79,1017,117],{},[338,1019,1020],{},"RTK Fixed",[338,1022,1023],{},"1–3 cm",[338,1025,1026],{},"Yes — best quality GGA",[320,1028,1029,1033,1036,1039],{},[338,1030,1031],{},[79,1032,141],{},[338,1034,1035],{},"RTK Float",[338,1037,1038],{},"0.1–1 m",[338,1040,614],{},[320,1042,1043,1047,1050,1053],{},[338,1044,1045],{},[79,1046,169],{},[338,1048,1049],{},"Dead reckoning",[338,1051,1052],{},"Variable",[338,1054,1055],{},"Depends on accuracy",[48,1057,1059],{"additionalstyles":50,"color":51,"title":1058},"You do not need Fix before sending GGA",[24,1060,1061],{},"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,1063,1065],{"id":1064},"how-gga-enables-vrs","How GGA enables VRS",[61,1067,1068,1074,1080,1086,1092],{"additionalstyles":50},[64,1069,1071],{"marker":66,"title":1070},"Your receiver gets a rough position",[24,1072,1073],{},"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.",[64,1075,1077],{"marker":73,"title":1076},"Your NTRIP client sends GGA to the server",[24,1078,1079],{},"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.",[64,1081,1083],{"marker":92,"title":1082},"The server identifies your location in the network",[24,1084,1085],{},"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.",[64,1087,1089],{"marker":117,"title":1088},"A virtual station is generated near you",[24,1090,1091],{},"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.",[64,1093,1095],{"marker":141,"title":1094},"Your receiver achieves RTK Fixed",[24,1096,1097],{},"With local-quality corrections flowing, your receiver resolves carrier phase ambiguities and reaches Fixed — typically within 10–60 seconds in good sky conditions.",[12,1099,1101],{"id":1100},"when-gga-is-required-vs-optional","When GGA is required vs optional",[507,1103,1104,1108,1112,1116],{"additionalstyles":50},[510,1105],{"text":1106,"title":1107},"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",[510,1109],{"text":1110,"title":1111},"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",[510,1113],{"text":1114,"title":1115},"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",[510,1117],{"text":1118,"title":1119},"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,1121,1123],{"id":1122},"how-to-enable-gga-on-your-device","How to enable GGA on your device",[24,1125,1126],{},"The setting name varies between NTRIP clients, but the function is the same on all of them.",[270,1128,1130,1143,1156,1164,1174,1184,1194],{"additionalstyles":50,"items":1129},"Emlid Flow|SW Maps|FieldGenius|Trimble Access|DJI Pilot 2|Lefebure NTRIP|Leica Captivate",[274,1131,1133],{"name":1132},"Emlid Flow",[24,1134,1135,1136,1139,1140,1142],{},"In ",[105,1137,1138],{},"Correction input → NTRIP",", select your VRS mountpoint and enable ",[105,1141,197],{},". Connect after the receiver has a valid Single solution.",[274,1144,1145],{"name":299},[24,1146,1147,1148,1151,1152,1155],{},"Go to ",[105,1149,1150],{},"Settings → NTRIP Client",", select the VRS mountpoint and enable ",[105,1153,1154],{},"Transmit GGA"," before connecting.",[274,1157,1158],{"name":293},[24,1159,1147,1160,1163],{},[105,1161,1162],{},"Set Up Corrections → RTK via Internet",". Select the VRS source and enable GGA transmission in the data-link settings.",[274,1165,1167],{"name":1166},"Trimble Access",[24,1168,1169,1170,1173],{},"Enter the VRS mountpoint in ",[105,1171,1172],{},"Survey Style → Rover radio",". Trimble Access sends GGA automatically while NTRIP is active.",[274,1175,1177],{"name":1176},"DJI Pilot 2",[24,1178,1179,1180,1183],{},"Enter the VRS mountpoint under ",[105,1181,1182],{},"RTK Settings → Custom Network RTK",". DJI sends GGA automatically after it has GPS lock, so configure it outdoors.",[274,1185,1187],{"name":1186},"Lefebure NTRIP",[24,1188,1189,1190,1193],{},"Enter the caster host, port and VRS mountpoint. Enable ",[105,1191,1192],{},"Send GGA"," and select the receiver or internal GPS as the GGA source.",[274,1195,1197],{"name":1196},"Leica Captivate",[24,1198,1199],{},"In the internet connection or rover settings, select the VRS mountpoint and enable NMEA GGA output to the NTRIP caster.",[12,1201,1203],{"id":1202},"gga-troubleshooting","GGA troubleshooting",[507,1205,1206,1210,1214,1218],{"additionalstyles":50},[510,1207],{"text":1208,"title":1209},"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",[510,1211],{"text":1212,"title":1213},"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",[510,1215],{"text":1216,"title":1217},"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?",[510,1219],{"text":1220,"title":1221},"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":465,"searchDepth":466,"depth":466,"links":1223},[1224,1225,1229,1230,1231,1232],{"id":827,"depth":466,"text":828},{"id":849,"depth":466,"text":850,"children":1226},[1227],{"id":943,"depth":1228,"text":944},3,{"id":1064,"depth":466,"text":1065},{"id":1100,"depth":466,"text":1101},{"id":1122,"depth":466,"text":1123},{"id":1202,"depth":466,"text":1203},"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.",{},[816,1237],"\u002Fen\u002Flearn\u002Fwhat-is-ntrip",{"title":822,"description":1234},"en\u002Flearn\u002Fwhat-is-gga","HFG0RJGp9bO8FHQR5HkzNRVEiSqOCSmiRVEfH3EUQ58",1787304715266]