U-blox Broadens Automotive Gnss Line For Safer Adas And Autonomy
U-blox has added two new automotive GNSS modules aimed at different parts of the vehicle stack, and the split is pretty clear. One targets high-volume Advanced driver-assistance system use with lane-level positioning, while the other is built for programs that need functional safety aligned with ISO 26262 and more advanced autonomy goals.
Two Modules Built Around Different Vehicle Needs
The new arrivals are the ZED-X20K and ZED-A20K. Together they extend the company’s satellite navigation portfolio in a way that lets engineering teams choose either a cost-focused path for mainstream deployment or a safety-oriented design for more demanding architectures.
| Module Name | Target Application | Key Features | Functional Safety | Availability |
|---|---|---|---|---|
| ZED-X20K | Mainstream ADAS, TCU and IVI | Lane-level positioning and native Galileo HAS | No dedicated ISO 26262 claim in this announcement | Engineering samples and evaluation kit available |
| ZED-A20K | Safety-oriented ADAS and higher autonomy programs | GNSS RAW data and QM positioning output | ISO 26262 ASIL-B(D)-compliant design | Samples scheduled from August |
Both modules share pin-to-pin compatibility with each other, which gives automakers and suppliers a cleaner upgrade path across model cycles. The announcement does not say that this interface carries across the wider u-blox automotive portfolio, so for now it reads as a pairing specific to these 2 parts. U-blox also includes jamming and spoofing detection, though the company has not detailed the detection method or said whether it is standard across every automotive module.
ZED-X20K Focuses on Global Lane-Level Positioning
The ZED-X20K is intended for mass-market ADAS Level 3 programs, along with TCU and IVI uses.
- Lane-level accuracy with all-band GNSS support
- Native Galileo HAS access with less reliance on paid correction services
That detail matters because it reduces dependence on paid correction services and avoids extra backend infrastructure. It also removes some service management overhead, which can help shorten development time while keeping navigation performance consistent across regions. From what I have seen in positioning projects, fewer external dependencies usually make validation less messy.
ZED-A20K Brings a Different Safety Architecture
For vehicle designs that require a defined functional safety concept around GNSS sensing, the ZED-A20K takes a different route.
- ISO 26262 ASIL-B(D)-compliant design with GNSS RAW data output
- High-performance QM positioning in a single module
That opens the door for OEMs to move away from older dual-hardware GNSS layouts and consolidate the job into a single module. The likely payoff is lower system complexity and reduced cost, with a cleaner engineering path for safety-sensitive navigation technology.
For automotive GNSS selection, the real split here is between an easier upgrade path and a deeper safety concept.
For automotive GNSS selection, the real split here is between an easier upgrade path and a deeper safety concept.
More Flexibility for SDV Architectures
U-blox says the A20 concept is designed to work with externally hosted positioning engines, which is especially relevant for ADAS Level 3 and above. In software-defined vehicle architecture, that kind of separation can improve how positioning functions are synchronized with the broader compute environment.
The matching form factor between the ZED-X20K and ZED-A20K also gives manufacturers more freedom at the platform level. A vehicle line can support versions with functional safety requirements and versions without them, while still using the same physical interface. I read that a bit like a map layer swap, where the base coordinates stay fixed and the capability overlay changes.
Automotive Range and Positioning Choices
Beyond ZED-X20K and ZED-A20K, u-blox has fielded other automotive-relevant GNSS modules over time, including NEO-M8L and ZED-F9K. In broad terms, the older M8 generation has been used where dead reckoning support and proven integration matter, while the F9 line is associated with higher-precision work and RTK-capable positioning in related deployments.
That split also helps explain single-band versus dual-band design choices. Single-band receivers are usually simpler and fit cost-sensitive navigation jobs, while dual-band designs improve accuracy and resilience in harder signal conditions. I tend to think of it like comparing a rough route trace with a cleaner GPS lock.
ADR modules work by blending GNSS with vehicle-motion sensors so positioning can stay usable through tunnels or urban blockage. In practice, dead reckoning leans on sensor fusion and carries the route estimate until clean satellite signals return.
Typical applications stretch from ADAS and autonomous driving to telematics or fleet tracking, with dead reckoning especially useful when satellite visibility drops. For adjacent segments such as robotics or UAV development, higher-precision modules in the F9 family are usually the more obvious fit.
Availability and Evaluation Timing
The ZED-X20K has reached the engineering sample stage, and an evaluation kit is already available. U-blox says samples of the ZED-A20K are scheduled to begin shipping in August.
That timing gives developers a near-term path to evaluation and early integration work, especially for teams balancing safety targets with internet of things connectivity or in-vehicle navigation functions.
