Vehicle-to-Everything hardware and product development — from requirement to a manufacturable unit.
India has proposed a national V2X fitment requirement and has no domestic on-board unit manufacturer. That gap is a hardware problem, and hardware is the older half of this company.
Ambimat Electronics has designed and built embedded products since 1982, concept to box-packaged product, with one organisation accountable across the design-to-manufacture boundary and PCB fabrication through a qualified partner ecosystem. This page is what that means for a C-V2X on-board or roadside unit.
India writes V2X rules for hardware it does not yet build.
As of the TRAI consultation in April 2026, India had not deployed a single V2X roadside unit and had no domestic on-board or roadside unit manufacturer. All such hardware was imported. Since then the Ministry of Road Transport and Highways has published a draft notification proposing AIS-230-compliant C-V2X on-board units on newly manufactured L, M and N category vehicles, with proposed dates of 1 October 2027 and 1 October 2028. What is draft and what is enacted →
That combination — a proposed fitment requirement at national scale, a cost target set by two-wheelers, and no domestic supply base — is a hardware problem. It is also the reason the AmbiOBU and AmbiRSU programmes exist.
One organisation across the design-to-manufacture boundary.
Ambimat Electronics is an OEM and ODM design and manufacturing house established 1982 — 44 years — working from concept to box-packaged product. PCB fabrication runs through a qualified global partner ecosystem, as the parent company states itself; what sits in one place is the accountability for the whole unit, not the fab. The dated engineering record →
For a V2X unit this matters more than it does for most products, because the decisions that break an OBU programme sit across the boundary between design and manufacture: the antenna placement that survives the enclosure, the thermal budget that survives the dashboard, the secure element that has to be personalised on a line rather than at a desk, and the bill of materials that has to close at a price a two-wheeler buyer will pay.
| Discipline | What it covers for a V2X unit |
|---|---|
| Embedded hardware design | PCB, microcontroller and power architecture |
| Antenna and RF integration | Placement, ground plane, feed loss and coexistence between the V2X, GNSS and cellular antennas in one enclosure. What decides real-world range → |
| Cellular radio design | 4G / LTE integration for the Uu path that carries certificate batches and firmware |
| GNSS integration | Positioning and timing, including the time synchronisation the PC5 sidelink depends on |
| Multi-sensor integration | Inertial, environmental and positioning sensors integrated on one board, as on the published AmbiLogistics platform. Integration with a vehicle data bus is programme-specific work, not part of the existing baseline |
| Enclosure and mechanical design | Machined and fabricated housings with thermal and vibration design done alongside the electronics — the practice published under AmbiSpace. Outdoor ingress qualification is programme work, not existing heritage |
| Secure element integration | Common Criteria EAL6+ compliant secure element for message signing and key custody |
| Secure bootloader and firmware | Verified boot and signed application firmware |
| OTA update pipeline | Signed, delta-packaged field update with on-device verification |
| Device-bound identity | A unique identity key held inside the secure element, non-extractable by hardware design |
| Certification support | Preparation and submission support for FCC, CE and MTCTE |
Existing government and research clients include ISRO, BARC and the Indian Army, all three named on the parent company's published client list. Three of the disciplines above have dated public outcomes behind them rather than only a capability statement: antenna control units supplied in 1993 and designed again in 2020, FCC certification obtained on a wireless device in 2014, and a development kit built for NXP's secure element in 2016. The record, with sources → · Which capability feeds which product →
The hard parts of an Indian OBU are not the V2X modem.
The C-V2X modem is a purchasable part, and the chipset landscape is well documented. The parts available, and what each one does →
What decides whether an on-board unit works in Indian service is a different list, and it is a list Ambimat has shipped hardware against:
- Thermal behaviour in a 48 °C ambient — a sealed unit on a two-wheeler in May is a thermal design problem before it is an electronics problem.
- Vibration on Indian road surfaces — mechanical survival and solder-joint life, not simulated but observed.
- GNSS performance under dense urban multipath — position and, critically, the timing reference the PC5 sidelink needs.
- Cellular behaviour on Indian networks — real coverage patterns, not lab conditions.
- Manufacturing at a cost point that works on a two-wheeler — the constraint that decides whether a national fitment requirement is met or contested.
The starting point is not a blank sheet. AmbiOBU evolves AmbiLogistics, Ambimat's existing field-deployed vehicle-tracking platform, by adding V2X sensing and integrating the AmbiSEC secure element for PKI-signed message broadcasting. That platform's specification is published: a 72-channel u-blox M8 receiver with GAGAN augmentation and built-in spoofing detection, 2.5 m CEP, −25 °C to +70 °C operating range, and IEC 60945 waterproofing. Those are the tracking platform's published figures; AmbiOBU's own V2X development configuration uses a u-blox MAX-M10S multi-constellation GNSS receiver. The published rows, separated from the development configuration →
An RSU is an outdoor computer that must not be touched for a decade.
Roadside units invert the OBU constraint set. Cost per unit matters less; access cost dominates. A unit on a gantry is expensive to reach, so enclosure sealing, thermal management without moving parts, surge and power resilience, and a field-update path that cannot brick the device are what decide the design.
The trust requirements do not relax. An RSU signs infrastructure messages that vehicles will act on, so it needs the same key custody, the same credential lifecycle and the same update integrity as a vehicle unit — with the added consideration that it is physically accessible to anyone with a ladder. AmbiRSU starts from that electronics and validation practice and the same secure element — noting, as the platform page does, that outdoor ingress qualification for a given site is programme work rather than existing heritage.
X.509 remains appropriate for RSU-to-platform backhaul over TLS, which is a separate credential path from the ITS certificates the unit broadcasts under. Both have to be provisioned, and both have to be renewable in the field. How the two hierarchies relate →
Where the two platforms actually are.
Stated the same way here as on the product pages, because the distinction is commercially material to you.
| Platform | Status |
|---|---|
| AmbiSEC | In production, and available as the security development setup — IoT and V2X security co-processor module |
| AmbiOTA | Secure over-the-air update architecture. Technology reference — not currently offered as a development setup |
| AmbiOBU | Development platform, open to collaboration. The AIS-230-aligned specification is pending; the published table is hardware lineage, not a product datasheet |
| AmbiRSU | Development platform, open to collaboration |
What the two development platforms need in order to become finished products is a partner with a deployment: an OEM with a fitment deadline, a tier-1 with an integration programme, a road authority with a site, or a research consortium with a pilot. The design, the manufacturing and the security layer are what we bring to that. The full product line and its status →
The path from a working board to a manufacturable product.
Most V2X hardware efforts produce a demonstrator. The distance between a demonstrator and a unit that can be built ten thousand times, personalised securely and certified for sale is where programmes stall.
| Stage | Output |
|---|---|
| Architecture | Block diagram, part selection, radio and antenna plan, trust boundary, power and thermal budget |
| Prototype | A working unit for demonstration and testing — the proof-of-concept engagement, 90 to 180 days |
| Design for manufacture | PCB layout for assembly, test-point strategy, enclosure tooling, bill-of-materials consolidation |
| Identity and records | Device-bound identity in the secure element, per-unit identity records, failure disposal |
| Validation | Extended-soak and environmental burn-in against the target envelope, plus pre-compliance testing before anything is submitted. Ambimat's published practice on space instrumentation is 168-hour burn-in before delivery; the equivalent envelope for a V2X unit is set per programme |
| Regulatory preparation | Documentation and submission support for FCC, CE and MTCTE. Type approval and certification remain with the authorised body |
| Production | Assembly, functional test and box-packaged output |
What this engagement is not.
- We do not supply a certified production V2X protocol stack. Where a programme needs a conformance-certified facilities, networking and security-services implementation, that comes from a stack vendor and we integrate it onto hardware we design. What we do provide is the AmbiV2X Developer Stack — an open ROS 2 application and development environment for AmbiOBU and AmbiRSU with V2X protocol integration against a programme-selected profile. The commercial stacks available →
- We are not an accredited test laboratory. We prepare hardware and documentation for certification and support the submission. The testing and the approval sit with the accredited body. How V2X testing and certification actually work →
- We do not deliver corridor-scale systems integration. We build the units and the security layer that go into a deployment somebody else is integrating.
- AmbiOBU and AmbiRSU are development platforms. They are not orderable products, they are not certified, and they are not homologated.
The technical material behind this page.
Chipsets and hardware
The V2X silicon landscape: modems, security parts and what each one is actually for.
AmbiOBU
The on-board unit programme, its AmbiLogistics lineage and its indicative specification.
AmbiRSU
The roadside unit programme, and what the published engineering record does and does not establish underneath it.
V2X security integration
The secure element, provisioning and credential-lifecycle side of the same unit.
India regulation
AIS-230, the MoRTH draft notification and the spectrum position, with draft and enacted kept apart.
About Ambimat
The design and manufacturing house behind this: established 1982, Ahmedabad.
Send us the binding constraint.
The cost ceiling, the fitment date, the thermal envelope, the enclosure, the certification route or the volume you have to reach. Email goes to an engineer, not a form.
Questions this page answers.
Can Ambimat design a C-V2X on-board unit?
Yes — hardware architecture, RF and antenna planning, GNSS and cellular integration, sensing, power and thermal, enclosure, design for manufacture and the provisioning line. A conformance-certified C-V2X protocol stack comes from a stack vendor and is integrated onto the hardware; Ambimat does not supply a certified production stack. It does supply the open ROS 2 application and development environment for AmbiOBU and AmbiRSU and the V2X protocol integration around it. The AmbiV2X Developer Stack. The silicon a design selects from.
What is hard about an on-board unit for Indian conditions?
Not the modem, which is a purchasable part. Thermal behaviour in a 48 °C ambient, vibration on Indian road surfaces, GNSS performance under dense urban multipath, cellular behaviour on Indian networks, and manufacturing at a cost point that works on a two-wheeler. Ambimat has shipped hardware against all five, on the AmbiLogistics vehicle-tracking platform that AmbiOBU evolves from.
Are AmbiOBU and AmbiRSU available to buy?
No. Both are development platforms, open to collaboration. The hardware baselines exist — a field-deployed and publicly specified vehicle-tracking platform on one side, the AmbiSpace electronics, mechanical and burn-in validation practice on the other, and the same secure element in both — but they are not orderable products, not certified and not homologated. What they need to become finished products is a partner with a deployment. Programme status for all four products.
Does Ambimat manufacture, or only design?
Both, with one organisation accountable for the whole unit: architecture, prototype, design for manufacture, assembly, functional test and box-packaged output. PCB fabrication runs through a qualified global partner ecosystem rather than an in-house fab, which the parent company states in its own company overview. Existing government and research clients include ISRO, BARC and the Indian Army, all named on the published client list.
Does Ambimat handle regulatory certification?
It prepares hardware and documentation and supports the submission for FCC, CE and MTCTE. It is not an accredited test laboratory, and type approval remains with the authorised body — for Indian V2X on-board units, ARAI or the appropriate authority. How testing and certification work.
What is different about roadside unit hardware?
The constraint set inverts. Cost per unit matters less and access cost dominates, so enclosure sealing, thermal management without moving parts, surge and power resilience, and an update path that cannot brick a device on a gantry are what decide the design. The trust requirements do not relax — an RSU signs messages vehicles act on, and it is physically reachable by anyone with a ladder.
Last updated 2026-08-20 · Technical reference maintained by Ambimat Electronics, Ahmedabad, India. Corrections: neel.shah@ambimat.com