Ambimat’s V2X practice builds the systems that let a moving vehicle exchange safety messages with other vehicles and with roadside infrastructure — and, just as importantly, the development kits that let an OEM or a technology company start working on that without building the hardware first.
The customers are vehicle OEMs and technology companies. AmbiOBU and AmbiRSU are mature, production-ready V2X development platforms available to order from Ambimat; no programme partner or custom-engineering commission is required first. Production ready describes that maturity and orderability, not environmental qualification or certification.
What the V2X practice covers
AmbiOBU — on-board unit
The mobile side: a sensing and V2X on-board unit for the vehicle itself. A production-ready V2X development platform, available to order.
AmbiRSU — roadside unit
The fixed side: a V2X roadside sensing unit, the infrastructure half of the same conversation. Also a production-ready V2X development platform, available to order.
AmbiSEC — security co-processor
An IoT and V2X security co-processor module, currently in production and available as the security development setup. Where the hardware root of trust for a V2X programme actually lives.
Developer and integration capability
AmbiV2X is a V2X software stack developed by Ambimat, based on existing ETSI ITS standards and India’s draft AIS-230 framework. Integration documentation, permitted access, licensing and software delivery scope are agreed individually for each customer engagement.
Where it fits
- Vehicle OEMs building connected-mobility capability into a platform
- Technology companies developing V2X applications who need hardware to develop against
- Roadside and infrastructure programmes on the fixed side of the link
- Programmes that have to satisfy a specific regulatory regime — India, the European Union, the United States, China or wider Asia-Pacific
How Ambimat contributes
V2X is where several of Ambimat’s existing capabilities meet: RF and antenna work, embedded firmware, secure element and credential handling from AmbiSecure, and the hardware design and manufacturing discipline needed to take a development kit to a product. The security architecture in particular is not bolted on — a vehicle broadcasting safety messages is only useful if the receiver can tell a genuine message from a fabricated one.
Authenticated over-the-air update is planned and is required before AmbiV2X stack delivery to a customer; it is not implemented today and is not offered as a standalone development setup.
Explore V2X
Product platforms and their current programme status, the developer stack, security architecture, regulation by region and the technical glossary are all on the dedicated V2X property.