Practical GNSS and RTK resources for real machines.

RTK gives a position now. PPK uses recorded GNSS observations to build and check the final trajectory, with particular value in weak segments, mobile mapping, and UAV flights.

OSR and SSR change what a GNSS receiver receives. PPP, PPP-AR and PPP-RTK show how correction content affects convergence, coverage and receiver support.

Network RTK turns one physical baseline into a regional service through CORS, multi-station modeling, virtual bases, shared grids, and quality control.

How to assess an RTK GNSS receiver for AgOpenGPS: data path, RTK corrections, motion inputs, vehicle-control boundaries, and field validation.

How to read RTK accuracy tests by comparing datasheet specs, Fixed Rate, RMS, CDF, and scenario statistics before choosing a receiver.

RTK GPS can improve field mapping, but acreage, boundaries, datum, antenna setup, and export metadata decide whether the map still lines up later.

Why host-based RTK moved the software engine off-chip, how that architecture lowered cost, and why the responsibility boundary still matters today.

AG3335 suffixes define GNSS responsibility boundaries, from PVT-first modules to RTK+DR packaging, vehicle dead reckoning, and OPEN compute paths.

Kalmix chose AG3335 as a GNSS platform because real machines need L1/L5 tracking, firmware control, RTK behavior, and deployable module architecture.

A field-level RTCM 3.x reference for frame parsing, CRC-24Q, MSM fields, message types, base-station records, and parser validation.

A field-level NMEA 0183 reference for GGA, RMC, GSA, and GSV: sentence fields, talker IDs, checksums, GNSS codes, and parser-safe version handling.