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. The engagement usually starts with a development setup and runs through to a product, which is why the offering is described in terms of platforms to develop on rather than a catalogue to buy from.
The mobile side: a sensing and V2X on-board unit for the vehicle itself. Offered as a development kit open to collaboration rather than as an off-the-shelf purchase.
The fixed side: a V2X roadside sensing unit, the infrastructure half of the same conversation. Also a development kit open to collaboration.
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.
Stacks and SDKs, the standards a programme has to hold to, tooling, and test and certification — the parts of a V2X project that decide whether the hardware ever ships.
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.
Over-the-air update is part of how the software lifecycle is engineered on a V2X programme, though it is not currently offered as a standalone development setup.
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.