Why host-based RTK moved the software engine off-chip, how that architecture lowered cost, and why the responsibility boundary still matters today.
Deep Dives
Deep Dives
Kalmix Deep Dives document the engineering judgment behind Kalmix hardware: why a particular GNSS chipset or platform was chosen, the industry context around that decision, and how it shapes product architecture and performance. These are the most technical, opinionated articles in the library.
3 articles
Engineering series
GNSS / RTK resources
Overview
Kalmix Deep Dives is an engineering series explaining the hardware decisions behind Kalmix GNSS products, including why Kalmix standardized on the MediaTek/Airoha AG3335 GNSS platform and how it compares to alternatives such as u-blox ZED-F9P.
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.