Adasens
Adaptive sensor intelligence
Middleware Compatibility Reference / Rev. 2025.03
The matrix below enumerates every ROS 2 distribution and AUTOSAR version verified against in-house reference hardware in Boulder, Colorado and Stuttgart, Germany. Signed compatibility reports ship with every production kit.
§ 02 / Supported middleware versions
Every row below is verified against in-house reference hardware in Boulder and Stuttgart and ships with a signed compatibility report on request. Badges indicate in-house test coverage at the noted revision.
§ 03 / Integration philosophy
Every Adasens sensor kit ships as a complete working artifact tree: reference sensor driver packages, deterministic launch files, calibrated URDFs, and signed firmware images keyed to the host ECU's secure boot chain. You drop the package into your existing workspace, point your middleware at the message-passing shim, and the perception pipeline starts publishing.
There is no proprietary bus, no replacement scheduler, no fork of the ROS 2 or AUTOSAR kernel. Latency budgets are documented per modality — currently 4.1 ms p99 for LiDAR, 2.7 ms p99 for mmWave, 5.8 ms p99 for ToF — and verified on each commit against the Boulder and Stuttgart reference racks before a signed firmware image is cut. Firmware artifacts carry an Ed25519 signature anchored to Adasens' public root, so your secure boot loader can refuse tampered images at boot.
§ 04 / Next step
Book a 30-minute technical consultation with an Adasens solutions engineer. Bring your ROS 2 / AUTOSAR version, your ECU's power envelope, and your target perception latency — we'll return a signed compatibility report and a proposed sensor configuration, on the call, for your specific stack.