V2X developer resources — what to read, what to run, what to buy.
Most V2X documentation is either a standards catalogue or a product brochure. This section is what an engineer actually needs to go from nothing to a signed CAM on a real radio, with the free things flagged as free and the expensive things flagged as expensive.
From nothing to a signed CAM on a real radio.
Standards
What to read, in what order, and which cost money.
Stacks and SDKs
Commercial V2X software stacks and development hardware.
Open source
Vanetza, ms-van3t, V2X-Hub, Artery, VASP and the simulation toolchain.
Test and certification
OmniAir, ETSI Plugtests, C-Roads, test equipment.
PKI test environments
Where you can actually enrol a device.
Tools
Browser-based parsers and reference databases that send nothing anywhere.
If you are starting from zero this week.
- Read ETSI EN 302 665 and then TS 102 941. Both free. That is the architecture and the PKI protocol.
- Pull the ASN.1 modules from ETSI's GitLab and compile them. Where they are →
- Build against Vanetza rather than writing a stack. It is the reference implementation and it is LGPLv3.
- Stand up a local enrolment authority and get the message nesting and the HMAC key-tag computation right before you touch a radio.
- Simulate before you buy hardware. ms-van3t on ns-3 supports LTE-V2X Mode 4 and NR-V2X Mode 2.
- Then buy an evaluation kit, and plan the certification path before the hardware is frozen, not after.
Doing it in the other order costs months, and the security layer is where the months go.
Adjacent material.
V2X PKI
The ETSI enrolment and authorisation exchange, message by message.
Message sets
Every message you will implement, with its ID, rate and standard.
AmbiSecure reference databases
Structured field-by-field references for IEEE 1609.2, TS 103 097, TS 102 941 and ISO 21177.
Development kits
Once the reading is done, the next constraint is hardware to run it on: On-Board Unit and Roadside Unit development setups.
Last updated 2026-08-19 · Technical reference maintained by Ambimat Electronics, Ahmedabad, India. Corrections: v2x@ambimat.com