Work down the list for the status you see. Most problems are a typo, no internet, or a blocked sky.
Stuck on SINGLE (no corrections coming in)
- Is the controller or RoverThe receiver that moves around the job, like a survey pole or a drone. It uses the base's corrections to find its exact spot.More really online? Try opening a web page, or check that the hotspot has data.
- Check the host, PortA number that tells your device which "door" on the caster server to use. For NTRIP it's often 2101.More, username, password and Mount pointOne specific correction stream on a caster, like one channel on a radio. Each one comes from a certain station or network setup.More again. Capital letters matter.
- Is your account still active? Many state networks make you renew every year.
- Using a VRSVirtual reference station. The network blends nearby stations to create a pretend base right next to you, which keeps the baseline short.More or "nearest" mount point? Make sure GGAA short message your rover sends with its rough location. VRS and nearest-station streams need it to know where you are.More (your rough location) is being sent. See NTRIP explained.
Stuck on FLOAT
- Move to open sky, away from buildings, trees and trucks (what affects a fix).
- Check how far you are from the nearest station with the Nearest base station tool. Past about 20 km, expect slower fixes that drop more often (why).
- Make sure the mount point sends a format and satellite systems your receiver can use.
- Watch the Age of correctionsHow old the latest correction message is, in seconds. If it keeps climbing, your internet link is struggling.More. If it keeps going up, your cell link is the problem.
- Check for space weather on NOAANational Oceanic and Atmospheric Administration. The US agency that includes NGS and runs the CORS network.More's Space Weather Prediction Center.
Fixed, but in the wrong place
- The DatumThe starting point and ruler that coordinates are measured from. The same spot has different numbers in different datums.More or GeoidA lumpy, imaginary "sea level" surface around the whole Earth. Elevations are measured from it.More doesn't match, or the geoid got applied twice (datums).
- Your own base is using a rough, uncorrected position. Set it properly with OPUS.
- The Antenna heightThe straight-up distance from the ground mark to the antenna's reference point. Getting it wrong shifts every height you measure.More or antenna type is wrong.
Still no luck? Try another option for your state from the state map, or switch to PPK with NOAA CORS.
Sources (checked Oct 16, 2026):NGS User Guidelines for Single Base Real Time GNSS Positioning v2.1Emlid Reach RS3 docs: RTK quickstartDJI Matrice 350 RTK User Manual v1.2Diagrams are FixFinder illustrations. Always follow your equipment's current manual.