AmbiRSU — the C-V2X Roadside Unit (RSU) development kit, and the stationary node.
AmbiRSU is a Cellular Vehicle-to-Everything (C-V2X) Roadside Unit (RSU) development kit — roadside V2X hardware for infrastructure, vehicle manufacturer (OEM) and research integration work, from Ambimat Electronics, an embedded design and manufacturing house in Ahmedabad, India. It is a mature, production-ready V2X development platform available to order from Ambimat, designed for direct 5.9 GHz LTE C-V2X PC5 communication — radio integration and over-the-air validation are under development — with a global navigation satellite system (GNSS) receiver, a separate 4G LTE backhaul and AmbiSEC support, with AmbiSEC populated when specified in the quoted configuration. It is not certified, homologated or type-approved, and no ingress rating or environmental qualification is claimed for the standard configuration.
A roadside unit is the equipment mounted beside or above the road — on a pole, a gantry or a signal head. It is the stationary participant: fixed position, known location, signing the infrastructure messages a vehicle acts on. The kit is supplied for algorithm development, integration, testing and demonstration, with no programme partner required first, and manufacturable in quantity. Production ready describes that maturity and orderability rather than environmental qualification, and it is not a certified production roadside product. Choose a development setup →
An On-Board Unit talking to a Roadside Unit is Vehicle-to-Infrastructure (V2I) communication — a signal, a work zone or a hazard telling an approaching vehicle something its own sensors cannot see. It is meant to be developed against the On-Board Unit development kit rather than in isolation, because a roadside node with nothing to talk to proves very little.
A roadside unit is permanent outdoor infrastructure carrying real-time road-safety communications, which makes it a rather different engineering problem from traffic equipment that only reports upward. India has effectively no deployed RSUs and no domestic manufacturer.
AmbiRSU is available to order from Ambimat.
AmbiRSU is a mature, production-ready V2X development platform available to order from Ambimat. It is supplied for algorithm development, integration, testing, research and demonstration — a roadside-unit development endpoint, not a bare radio evaluation board. No programme partner and no custom-engineering commission is required first. Environmental qualification of the standard configuration for extreme temperature, high humidity, ingress, vibration, shock or outdoor roadside installation is not claimed unless explicitly stated; homologation and certification for a permanent roadside installation remain specific to the final integrated product, the site and the target programme. Choose a development setup →
A revised AmbiRSU datasheet is in preparation and is not yet published; this page is the current public description of the kit. Request AmbiRSU product specifications.
The roadside counterpart to AmbiOBU, on the same foundation.
AmbiRSU is a configurable roadside V2X development platform built on the same compute, positioning, connectivity and software foundation as AmbiOBU. It is intended for vehicle-to-infrastructure and infrastructure-to-vehicle research and roadside integration work — not presented as a certified production roadside unit.
| Component | Development configuration |
|---|---|
| Product class | Mature, production-ready roadside V2X development platform, available to order from Ambimat. Static endpoint, supplied for algorithm development, integration, testing and demonstration, and manufacturable in quantity. Environmental qualification of the standard configuration for extreme temperature, high humidity, ingress, vibration, shock or outdoor roadside installation is not claimed unless explicitly stated; it is not a certified production roadside unit, not homologated and not type-approved |
| Compute | NVIDIA Jetson Orin Nano Super, 8 GB LPDDR5 — the same compute platform and memory configuration as AmbiOBU. Why both endpoints share it → |
| Operating environment | Ubuntu 22.04 LTS |
| Developer middleware | AmbiV2X and ROS 2 Humble, designed to coexist on the Jetson platform: AmbiV2X, the V2X software stack developed by Ambimat, and ROS 2 Humble as the robotics application environment. ROS 2 integration interfaces are on the platform roadmap, to be developed and validated |
| Software | AmbiV2X Developer Stack — the same application and integration environment as AmbiOBU |
| Direct V2X | 5.9 GHz LTE C-V2X PC5, the same radio direction as AmbiOBU. AmbiRSU is designed for direct PC5 communication with nearby V2X participants, where the local exchange does not go through a mobile network. Radio integration and over-the-air validation are under development, and what a particular roadside evaluation covers is confirmed in the agreed configuration. This is the only radio direction Ambimat develops and supplies for V2X. What LTE C-V2X and PC5 are → |
| GNSS | u-blox MAX-M10S GNSS receiver — standard AmbiRSU hardware. The same u-blox M10 standard-precision, multi-constellation module as AmbiOBU; the u-blox figures and their test conditions are on the AmbiOBU page. Not RTK and not lane-level. AmbiV2X has used live position and time from this receiver model on engineering test hosts; validated GNSS integration on AmbiRSU itself is not claimed. Why a roadside unit still needs GNSS time → |
| Motion sensing | Not fitted to the standard configuration. A 9-axis IMU (accelerometer, gyroscope, magnetometer) can be added as a customer-specific addition, quoted separately at additional cost — for example where a programme wants installation-alignment, pole-movement or vibration data. A static roadside node does not need inertial data to function |
| Environmental sensing | Not fitted to the standard configuration. Ambient temperature, relative humidity and barometric-pressure sensors can be integrated on request as a customer-specific addition, quoted separately at additional cost |
| Cellular | SIMCom A7672-series 4G LTE Cat 1 module for backhaul, telemetry, remote diagnostics, backend and IP services. This cellular connection is separate from the direct C-V2X radio and does not provide PC5. |
| Security | AmbiSEC-capable. AmbiSEC hardware is populated when specified in the quoted configuration; confirm its inclusion in the quotation and bill of materials. Where populated, AmbiSEC provides protected key storage, protected cryptographic operations and device-bound identity for the roadside endpoint. The V2X message-security implementation that uses them is being developed, on the same basis and with the same boundaries as the vehicle-side platform. What is implemented and what is being developed → |
| Protocol development | Roadside messages in AmbiV2X: ETSI SPATEM and MAPEM — signal phase and intersection geometry — originated by AmbiV2X’s roadside service role from demonstration data and verified in host-based software testing; a live traffic-signal controller feed is not yet accepted. For US programmes, SAE J2735-2022 SPaT, MAP and TIM over IEEE 1609.3-2020 (WSMP, WME) with IEEE 1609.2-2016 security are candidate development messages, selected per programme — not implemented or conformance-tested |
| Roadside interfaces | Programme-configurable. Traffic-signal and controller data, externally supplied intersection state, road and environment sensors, backend systems and experimental instrumentation are scoped to the target programme rather than fixed in advance |
| Enclosure and environment | Defined per programme. Enclosure, environmental protection, mounting, power conditioning and site interfaces are specified according to the development or pilot programme. No ingress rating, environmental qualification or roadside homologation is claimed for the development platform |
| Power input | 12–19 V DC input to the unit. The unit handles its own internal voltage conversion and power distribution; internal rail details are not published. Connector, polarity, input-current and input-protection details are not published here. The unit’s own input is DC, not mains, and no Power over Ethernet, automotive 24 V compatibility, direct vehicle-battery connection, or surge, lightning or roadside power-conditioning qualification is claimed. Site power conditioning beyond the supplied components remains scoped to the programme |
| Supplied power components | Included with the kit: a Jetson power supply and the Ambimat AE170 power distribution board. The supplied power supply’s rating, input range and plug type are confirmed in the quotation |
What AmbiRSU is not. It is not part of the optional 1:10-scale movable development platform — that belongs to the on-board unit, which is the moving participant. AmbiRSU is the static endpoint it is developed against. A complete research setup normally contains both: one or more moving AmbiOBUs and a fixed AmbiRSU.
On signal interfaces, external input and output beyond the interfaces listed above remains development-configurable. The compute platform exposes more than the roadside unit necessarily brings out to a connector, and this page does not list an interface as available on AmbiRSU merely because the compute module supports it. Which signals are exposed, and how, is part of the programme design.
The common development platform.
AmbiOBU and AmbiRSU are deliberately built on one architecture. The difference between them is where they sit, not what they run.
| AmbiOBU | AmbiRSU | |
|---|---|---|
| Role | Mobile development endpoint — the moving participant | Static roadside development endpoint — the fixed participant |
| Primary experiments | V2V, V2I, moving-node and relative-motion work | V2I, I2V, roadside application development, infrastructure experiments |
| Inertial and environmental sensing | 9-axis IMU standard; ambient environmental sensors a quoted addition at additional cost | 9-axis IMU and ambient environmental sensors both quoted additions at additional cost |
| Optional moving platform | Can be run on the 1:10-scale movable development platform, a separately quoted accessory at additional cost | Not applicable — AmbiRSU is the static endpoint |
| Enclosure and siting | Vehicle-mounted or platform-mounted development configuration | Roadside enclosure, mounting and power defined per programme |
The point of the shared architecture is practical. A team develops against one operating system, one runtime, one set of application tooling and V2X interfaces and one backhaul path, and moves work between the mobile and roadside sides of an experiment with fewer platform-specific differences to absorb. It is a common application environment rather than a promise of binary-identical deployment: the two endpoints are packaged differently, sited differently and powered differently, and their external interfaces are scoped separately.
ROS 2 on the roadside. AmbiRSU is designed for the same AmbiV2X and ROS 2 Humble coexistence as AmbiOBU. On the roadside, ROS 2 is the natural home for infrastructure-side robotics and sensing work: processing data from roadside sensors a programme adds, running roadside applications, and supporting cooperative-perception and intersection experiments. Standard V2X messages such as signal phase and timing, intersection geometry and, as CPM matures, perceived objects are AmbiV2X's side of that work; over-the-air PC5 operation of AmbiV2X is under development, with target readiness in late November 2026. Roadside sensors are scoped per programme rather than included, and the AmbiV2X–ROS 2 integration is on the platform roadmap, not a delivered or validated bridge. ROS 2 and C-V2X use cases →
A compromised roadside unit is a weapon, not a fault.
An RSU that broadcasts unsigned messages, or whose firmware can be silently replaced, can inject false traffic alerts, spoof emergency-vehicle signals, or disable collision warnings across an entire corridor — continuously, from a fixed and well-chosen position, to every vehicle in range.
It is also a trusted insider in the PKI. Roadside units hold application certificates with service-specific permissions that vehicles do not have: an RSU may sign SPaT, MAP and IVI messages; a vehicle may not. Compromise it and you inherit those permissions. How those permissions are encoded →
Eight requirements, and where AmbiRSU stands on each.
The hardware-backed rows depend on AmbiSEC, which is populated when specified in the quoted configuration. No row is a tested or certified whole-unit implementation. Each row states its own status, so AmbiSEC module-level functions, work being developed, planned capabilities, US-profile requirements and customer-specific engineering are kept apart.
| Requirement | AmbiRSU status |
|---|---|
| PKI certificate management | Where AmbiSEC is populated, it holds the roadside credentials inside its security boundary. Issuance, renewal and revocation over the backhaul are being developed, and the authority they talk to is external to Ambimat |
| Signed messages | With AmbiSEC populated, ECDSA signing and verification inside its boundary are implemented at the module level; the IEEE 1609.2 secured-message path that carries them is being developed. AmbiV2X has signed messages on AmbiSEC test hardware over a laboratory network link, not over PC5 |
| Secure OTA | Firmware authenticated before installation, with rollback protection on a failed update. Planned — not implemented today. Required, and to be implemented and verified, before the AmbiV2X stack is delivered to a customer |
| Hardware-backed credential storage | Where AmbiSEC is populated, roadside identity keys and credentials are held inside its hardware-isolated boundary — implemented at the module level; the V2X credential lifecycle that supplies them is being developed |
| Secure boot | Boot sequence cryptographically verified before the unit becomes operational. Planned — not implemented today. Required, and to be implemented and verified, before the AmbiV2X stack is delivered to a customer. Distinct from the secure element’s own internal protections |
| Tamper detection | Not a standard AmbiRSU feature. Enclosure tamper detection or an anti-tamper mesh can be supplied as separately scoped customer-specific engineering — often needed for unattended roadside deployment. AmbiSEC’s silicon-level tamper resistance protects keys inside the secure element; it does not establish tamper protection of the RSU enclosure |
| Device-bound identity | Where AmbiSEC is integrated, a unique identity key held inside the secure element and non-extractable by hardware design, anchoring identity operations to the individual roadside endpoint — implemented at the module level where AmbiSEC is populated |
| Application permissions | Message permissions scoped in the certificate, so a roadside unit signs only the message types its permissions authorise. PSID-based authorisation is a US-profile development requirement, to be developed and validated with the US security profile; it is not a validated AmbiV2X capability today and not a prerequisite for initial India and Europe delivery. Verifying a signature and authorising a service are different checks |
That last row is worth dwelling on. In the standards, permissions are carried in the certificate itself — as a PSID with its SSP in IEEE 1609.2, the US profile, and as an ITS-AID with its SSP in ETSI TS 103 097 for Europe — so what a device is allowed to say is enforced cryptographically rather than by configuration. Separating credentials by application is therefore a design decision taken once, at architecture time — it is not something that can be added later in software.
What a roadside unit inherits, and what it still has to earn.
AmbiRSU is designed and built by an embedded hardware house, and the disciplines it draws on are the ordinary ones: mixed digital and RF board layout on a single PCB, enclosure and thermal design carried out as part of the electronics design rather than bought in afterwards, and production and test tooling designed alongside the product. Those are capabilities, not qualifications, and it is worth being precise about the difference.
What is not claimed. There is no published environmental, thermal or soak qualification for AmbiRSU, and none is claimed here — no operating-temperature rating, no ingress rating and no burn-in figure. Sealing, ingress rating, solar gain, surge, pole-mount mechanics and the environmental test envelope for a specific site are development work on an AmbiRSU programme, not something the platform already carries.
A fixed position also changes the radio design: unlike a vehicle, a roadside unit knows which approaches matter and can aim its antenna along the carriageway rather than radiating equally in every direction. AmbiRSU is designed to the same security architecture as AmbiOBU, adapted for fixed infrastructure deployment with cellular backhaul. Sensors beyond the standard configuration above are scoped from client-supplied requirements.
An open question in India, and one worth engaging publicly.
Our position: authorisation should be a licence with a security bar, not a procurement footnote.
Plausible operator classes: licensed telecom operators, who already hold spectrum, tower estate, backhaul and 24×7 network operations discipline; cloud and software infrastructure providers, who can run the ITS application layer, edge compute and credential-management back end; and highway, tolling and transit concessionaires, who own the roadside asset, power and access rights on the corridors that matter first and have a commercial reason to maintain the units.
Conditions of authorisation should include certified, MTCTE-tested equipment with a tamper-resistant secure element and secure boot; enrolment as an end entity under an approved Root CA with an audited Certification Practice Statement and no self-signed roadside trust; physical-security and tamper-response obligations at the pole with incident-reporting SLAs; and strict separation of safety-message permissions from commercial-service permissions. Where the Indian position currently stands →
An orderable development platform, and a homologated roadside unit, are two different things.
AmbiRSU is a mature, production-ready V2X development platform available to order from Ambimat, and the design is manufacturable in quantity. It is supplied for algorithm development, integration, testing, research and demonstration. Contact Ambimat for configuration, lead time and pricing; no price, stock position or delivery commitment is published here, because none is fixed in advance of an enquiry.
Production ready is a statement about maturity, manufacturability and orderability — not about environmental qualification. Environmental qualification of the standard configuration for extreme temperature, high humidity, ingress, vibration, shock or outdoor roadside installation is not claimed unless explicitly stated, and no operating-temperature range or ingress rating is published for it. Where a deployment needs one, that is an IDH engagement → Homologation and certification for a permanent roadside installation remain specific to the final integrated product, the site and the target programme: this platform is not in production deployment, not certified, not homologated and not type-approved, and no ingress rating or environmental qualification is claimed for it.
What comes with the platform: mixed digital and RF PCB integration; cellular backhaul design; AmbiSEC support for hardware-held credentials, populated when specified in the quoted configuration; whole-device secure boot and authenticated OTA as planned capabilities, required before the AmbiV2X stack is delivered to a customer; and enclosure tamper detection and provisioning as customer-specific engineering rather than standard features.
Where a programme wants more than the standard platform — a corridor, an intersection set or a campus to design against, traffic-controller and command-centre integration, an outdoor enclosure qualified for a named site, or a defined conformity regime — AmbiRSU can be the engineering baseline for a customer-specific production roadside unit. That is optional Ambimat custom engineering, taken up after you have the platform, and it is not a condition of buying one. The eight integration surfaces →
Work we take on beyond the platform itself.
Commissioned development work around roadside infrastructure — custom RSU hardware to a published specification, sensor payload integration, secure-element and credential-lifecycle integration into an existing RSU design, provisioning-line design, and firmware and OTA work for deployed roadside fleets.
On the software side, AmbiRSU runs the same development environment as the on-board unit, described in the reference configuration above. Roadside interfaces, sensor payload and backend integration are scoped according to the target programme rather than fixed in advance. The AmbiV2X Developer Stack →
If you are building roadside infrastructure, the standard platform is orderable on its own and the engineering above is available on top of it. Commercial arrangements for that engineering — custom development, licensing, contract manufacture, joint pilots — are discussed directly. Reach out →
Need a deployment-specific production design?
The standard AmbiOBU and AmbiRSU are production-ready development platforms, available to order exactly as they are, and manufacturable in quantity. Where a programme instead needs automotive, roadside, outdoor or other environment-specific qualification, Ambimat Technologies Pvt Ltd can act as your IDH — independent design house — partner, and adapt or develop the V2X hardware around that programme's electrical, mechanical, RF, environmental, security and integration requirements.
Requirements are captured first. The qualification scope, and the evidence that closes it, are agreed and validated as part of that programme rather than assumed from the standard configuration or promised in advance. It is a separately scoped engineering engagement, and it is not a prerequisite for buying anything — the standard platforms can be ordered directly, with no IDH engagement, no programme partnership and no custom-engineering commission first.
Where this fits.
V2I
What an RSU broadcasts, and the eight systems it has to touch.
AmbiSEC
The secure element AmbiRSU is designed for, populated when specified in the quoted configuration.
India regulation
Why RSUs are excluded from the OBU licence exemption.
SCMS vs CCMS
How each trust model treats roadside stations and their permissions.
Threats and attacks
RSU compromise as a threat class, with its countermeasures.
AmbiV2X Developer Stack
The V2X development environment this node runs, and how its roadside interfaces are scoped.
AmbiOBU
The vehicle-side counterpart, on the same security architecture.
Scoping a roadside deployment or an RSU development programme?
Bring the site, the controller integration and the conformity regime. We will bring the hardware baseline and the security architecture, developed as part of a V2X development programme — and the OBU development kit to give the roadside node a moving participant to be developed against.
Questions this page answers.
What is a Roadside Unit?
The V2X equipment mounted beside or above the road — on a pole, a gantry or a signal head. It has a fixed, known position and signs the infrastructure messages vehicles act on: signal phase and timing, work zones, hazards. It is the stationary participant.
What is a Roadside Unit development kit?
A roadside-unit development endpoint rather than a bare radio evaluation board, designed for direct 5.9 GHz LTE C-V2X PC5 communication; PC5 radio integration and over-the-air validation are under development. AmbiRSU has the same compute and LTE backhaul as AmbiOBU and a standard u-blox MAX-M10S GNSS receiver, and, like the vehicle-side platform, it is AmbiSEC-capable: hardware-held credentials in AmbiSEC where it is populated when specified in the quoted configuration. Outdoor ingress qualification for a particular site is development work on the programme.
Can I order the AmbiRSU development platform, and how do I request a quotation?
Yes. AmbiRSU is a mature, production-ready V2X development platform available to order from Ambimat, with no programme partner and no custom-engineering commission required first. Email Ambimat with the setup you want, how many nodes and what you intend to develop; enquiries reach Ambimat's business development team directly. Price, lead time and delivery terms are quoted per enquiry and are not published on this site. Choose a development setup.
Can Ambimat customise AmbiRSU for a site's temperature, ingress or power requirements?
Yes, as optional engineering rather than as something the standard platform already carries. Where a programme requires a specific operating-temperature range, ingress rating, vibration profile, power-input condition, enclosure or installation format, Ambimat can provide independent design-house (IDH) engineering — that is, engineering carried out by an independent design house on the customer's behalf — to develop and validate the required configuration. No ingress rating or environmental qualification is claimed for the standard development platform. Where that work sits.
How does it work with the On-Board Unit kit?
Together they form the Vehicle-to-Infrastructure (V2I) development setup: the roadside node originates messages about something the vehicle cannot see, such as signal phase and intersection geometry, and the On-Board Unit development kit in the moving vehicle is the receiving node. Over-the-air PC5 operation of AmbiV2X, and signed messaging over it, are not yet claimed. A roadside node with nothing to talk to proves very little, which is why the two kits are designed to be developed together.
Does AmbiRSU use the same software environment as AmbiOBU?
Yes. Ubuntu 22.04 LTS and the AmbiV2X Developer Stack — the same application and integration environment, with AmbiV2X and ROS 2 Humble designed to coexist on the same Jetson platform. That is the point of the shared architecture: a team develops against one environment and moves work between the mobile and roadside sides of an experiment. It is a common application environment rather than a promise of binary-identical deployment.
Does AmbiRSU use the same compute platform as AmbiOBU?
Yes — an NVIDIA Jetson Orin Nano Super with 8 GB of 128-bit LPDDR5 memory on both endpoints. Note that the compute platform exposes more than the roadside unit necessarily brings out to a connector; which external interfaces AmbiRSU presents is part of the programme design rather than inherited from the module.
Which GNSS does AmbiRSU use?
A u-blox MAX-M10S, fitted as standard — the same u-blox M10 standard-precision receiver as AmbiOBU. A static node still needs GNSS for its position and for the sidelink timing reference. No RTK, no dead reckoning, and no lane-level or centimetre-level claim; a fitted receiver is not evidence of validated GNSS position or timing integration with AmbiV2X.
Does AmbiRSU include LTE?
Yes — a SIMCom A7672-series 4G LTE Cat 1 module for backhaul, telemetry, remote diagnostics and backend or IP services. It is separate from the direct C-V2X radio and does not provide PC5. Direct V2X is designed to use 5.9 GHz LTE C-V2X PC5, where the local exchange does not go through a mobile network; its radio integration is under development.
Does AmbiRSU contain an IMU?
Not in the standard configuration. A 9-axis IMU is a customer-specific addition on AmbiRSU, quoted separately at additional cost, for a programme that wants installation-alignment, pole-movement or vibration data. A static roadside node does not need inertial data to function.
Does AmbiRSU include environmental sensors or enclosure tamper detection?
Not as standard. Ambient temperature, humidity and barometric-pressure sensors, and enclosure tamper detection or an anti-tamper mesh, can each be supplied as customer-specific engineering, quoted separately at additional cost. AmbiSEC's silicon-level tamper resistance protects keys inside the secure element; it does not protect the RSU enclosure.
How is AmbiRSU powered?
AmbiRSU takes a 12–19 V DC input, and the unit handles its own internal voltage conversion and power distribution. A Jetson power supply and the Ambimat AE170 power distribution board are included with the kit; the supplied power supply's rating, input range and plug type, and the input connector, polarity, current and protection, are confirmed in the quotation. The unit's own input is DC, not mains, and no Power over Ethernet, automotive 24 V compatibility, or surge, lightning or roadside power-conditioning qualification is claimed.
Is AmbiRSU part of the moving development platform?
No. The optional 1:10-scale movable development platform applies to AmbiOBU, which is the moving participant. AmbiRSU is the static roadside endpoint in that setup: an orderable development platform intended for direct 5.9 GHz LTE C-V2X PC5 communication, with over-the-air integration and validation under development and targeted for late November 2026. A full research setup normally has both.
Can AmbiSEC be included with AmbiRSU?
Yes. AmbiRSU is AmbiSEC-capable, and AmbiSEC is populated when specified in the quoted configuration; it is not fitted to every unit, so state it in the enquiry and confirm it in the quotation and bill of materials. Where populated it provides secure key storage, hardware-backed cryptographic operations and device-bound identity — a unique identity key held inside the secure element and non-extractable by hardware design, so identity operations are anchored to that individual roadside endpoint. Ambimat does not operate the Root CA and is not a PKI operator.
Is this a production roadside unit?
No, and the two statements sit together without contradicting each other. AmbiRSU is a mature, production-ready V2X development platform available to order from Ambimat, and manufacturable in quantity — and environmental qualification of the standard configuration for extreme temperature, high humidity, ingress, vibration, shock or outdoor roadside installation is not claimed unless explicitly stated. It is not a certified production roadside product, not homologated and not type-approved for permanent roadside installation; that remains specific to the final integrated product, the site and the target programme. Taking a platform to a deployed roadside product is optional development work on top of it.
Why is roadside hardware a different problem from vehicle hardware?
The constraint set inverts. Cost per unit matters less and 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 an update path that cannot brick the device are what decide the design. The trust requirements do not relax.
Last updated 2026-10-22 · Technical reference maintained by Ambimat Electronics, Ahmedabad, India. Corrections: v2x@ambimat.com