What you see: the app connects, but no corrections arrive, or it shows a long list of mount points. A mount point is the name of one correction stream on the CasterThe internet server that hands out correction streams. Your rover logs in to it, like tuning into a radio station.Full definition: a single base, or a network stream like VRSVirtual reference station. The network blends nearby stations to create a pretend base right next to you, which keeps the baseline short.Full definition.
Why it happens
In NTRIPThe standard way RTK corrections are sent over the internet. Think of it as internet radio for correction data.Full definition version 1, when you ask for a mount point that doesn't exist, the caster sends back its source table (the full list of mount points) instead of corrections. BKG's NTRIP documentation describes this. Some casters do the same when your login is missing. So a list where you expected data almost always means the name is wrong or your login didn't go through.
Fix it
- Pick from the list, don't type. Most apps can download the mount point list. Choose from it.
- Match capital letters exactly. Mount point names are case-sensitive, so "vrs_rtcm3" is not "VRS_RTCM3".
- Pick the right format. Choose a mount point that sends RTCMThe common format RTK corrections are written in, so different brands can understand each other.Full definition unless your receiver needs CMR or CMRxTrimble's own compact correction format. Some networks offer it for Trimble gear and machine control.Full definition. In one Emlid forum case, switching to the RTCM 3 mount point fixed the problem.
- Pick the right type. "VRS", "nearest" or "auto" streams need your location (GGAA short message your rover sends with its rough location. VRS and nearest-station streams need it to know where you are.Full definition): see VRS sends nothing. A single-base stream needs you to be close to that base (baseline length).