SDV Labs ARXML Vehicle Simulator
A portable interface twin around any ECU under test.
Resolve customer-owned AUTOSAR definitions into reviewable mock services, vehicle states and protocol traffic around an HPC, IVI, cluster, ADAS controller or other compatible target. Visualize requirement conditions early, then use the same baseline from a developer workstation to CI and the integration bench.
System architecture
One image. External inputs. Customer-controlled outputs.
Read-only inputs
ARXML · YAML · scenarios · recordings
Product container
Parser · model · runtime · HMI · API
Generated evidence
Catalog · diagnostics · reports · exports
Browser operator
Manual · auto · scenario · replay
Bench network
SOME/IP over Ethernet · CAN via SocketCAN
Local boundary
No mandatory outbound data path
Shift-left requirement validation
Make a requirement observable before the vehicle exists.
Use the HMI or automation API to establish requirement preconditions, publish the corresponding SOME/IP and CAN traffic, and observe how the selected ECU or application reacts. The same flow supports reviews, development, CI and later bench correlation.
1. Define intent
Select requirement conditions, interfaces and expected reactions.
2. Experience the state
Visualize live vehicle state and production-relevant protocol traffic.
3. Capture evidence
Record target reactions, diagnostics and repeatable run reports.
Current platform
What is included
- Mixed Classic and Adaptive ARXML ingestion with cross-file diagnostics
- Typed Classic AUTOSAR SOME/IP serialization and deserialization
- COVESA vSomeIP service discovery, methods and event offering
- AUTOSAR E2E send protection for selected P01, P04 and P05 paths
- Live Classic CAN and CAN FD through Linux SocketCAN
- Manual HMI, seeded auto, authored scenarios and field-derived replay
- Any compatible HPC, IVI, cluster, ADAS, gateway or other ECU/application as the system under test
- Requirement visualization through named states, protocol traffic and observed reactions
- SOME/IP and CAN application-telemetry wire monitoring
- Containerized local runtime with no mandatory cloud or AI dependency
Honest engineering boundaries
We make the interface layer portable and observable. We do not blur it with capabilities that belong to higher-fidelity environments.
- ARXML defines communication contracts—not customer business behavior.
- The product is not a deterministic real-time plant model or HIL replacement.
- ISO-TP/UDS, LIN transport and bus-level fault injection are not in the current release.
- Customer-wire acceptance requires actual ARXML, endpoints and independent golden payloads.
- Evaluation software is not certified for production, homologation or safety decisions.
Evaluation path
Prove the fit against your own interfaces.
Define success around discovery, payload vectors, target reactions, replay evidence and the engineering work that can move off constrained shared assets.