A rover-oriented operational view
The map identifies the rover by account, shows its solution mode, and links it to the active source. Events record authentication, position, rejection, and disconnection.
Historical traces remain useful after a session, but active markers and lines disappear immediately at disconnect. Operators can clear map history without changing server records.
Each simultaneous use of one account appears as a distinct session. Setting the account limit to 1 and assigning one credential per rover keeps the active list directly attributable to one operator or receiver.
Interpreting Fix, Float, and Single
The NMEA quality field can be translated into consistent labels and colors. Fix indicates an integer ambiguity state, Float an unresolved differential state, and Single autonomous positioning.
A short mode change is not enough for diagnosis. History, base distance, mountpoint, and correction age show whether degradation is persistent or widespread.
The label does not certify survey accuracy. Known-point checks, reference frame, antenna setup, and field practice remain essential.
Baselines, distance, and coverage
A clickable base-rover line displays distance in kilometers. It helps detect an unsuitable source and explain Float performance. A configured source radius can reject excessive use.
Nearest-station services select a base from GGA. VRS also uses location but produces session-specific corrections. The control center should identify the service type.
Map updates move markers without automatically panning on every GGA or RTCM position message.
Support and incident handling
Server reason codes are translated into clear messages: invalid account, duplicate account, unknown mountpoint, missing GGA, inactive subscription, or timeout.
A remote close during write becomes one disconnection event. The active marker is removed and a later reconnection creates a new session.
Protected administrative actions can start or stop the caster service, while systemd keeps the production process independent of an SSH terminal.
RTK control center FAQ
Is the control center tied to one receiver brand?
No. Interoperability is based primarily on NTRIP, RTCM, and NMEA support. Actual message availability still depends on the receiver model and firmware.
Can one company see another company’s mountpoints?
No. Tenant resolution, authorization, sourcetable filtering, and direct mountpoint checks are performed server-side so each organization only accesses its own resources.
Does a Fix label guarantee survey accuracy?
No. Fix describes the ambiguity state reported by the rover. Coordinates, reference frame, antenna setup, multipath, field procedures, and independent checks still determine the reliability of a survey.