01 / 06
ARXML to runnable model
Discovers services, events, operations, deployment IDs, data types, ECU ownership and CAN topology with explicit diagnostics.
ARXML-driven vehicle simulation
Make the rest of the vehicle available now.
Turn AUTOSAR ARXML into a portable rest-of-vehicle simulation around any compatible ECU or application under test—including HPC, IVI, cluster and ADAS targets—before every dependency or shared bench is ready.
Local by default One product container No AI key required
Live validation topology
Customer ARXMLInterfaces · deployment · types
validate + resolve
SDV Labs simulator
Typed mocksVehicle stateAutomationEvidence
SOME/IPSD · methods · events
CAN / CAN FDVirtual or physical
live application traffic
Any system under testHPC · IVI · cluster · ADAS · any ECU
LIVEAUTOSAR ARXMLSOME/IPCAN / CAN FDPCAPNGASC / BLFDocker / OCI
From contract to execution
Your ARXML becomes an executable integration environment.
The platform resolves what the files actually define, fails loudly on ambiguity, and exposes safe mock behavior through production-relevant transports.
See the technical architecture02 / 06
Typed SOME/IP
Includes COVESA vSomeIP, its Python binding, Classic AUTOSAR payload serialization and selected E2E P01/P04/P05 protection.
03 / 06
Live CAN & CAN FD
Uses Linux SocketCAN with physical-value encoding, cyclic/event scheduling, inbound decode and safe HMI-selectable connection profiles.
04 / 06
Any ECU as the SUT
Place an HPC, IVI, cluster, ADAS controller, gateway or other compatible ECU/application under test while the simulator provides its surrounding interfaces.
05 / 06
Requirement visualization
Turn requirement preconditions into named vehicle states, live bus traffic and observable target reactions that teams can review together.
06 / 06
Engineering evidence
Provides bounded SOME/IP/CAN wire monitoring, explicit drops, replay diagnostics, assertions and atomic run reports.
Three workflows. One model.
Explore, automate and reproduce.
Start with interface-safe defaults. Add customer-owned profiles, scenarios and recordings as fidelity grows.
01
Manual exploration
Drive ignition, doors, gear, speed, HVAC, ADAS and customer-defined states from a browser HMI while the target application reacts live.
02
Repeatable automation
Run deterministic seeded conditions or versioned scenarios, then reproduce the same sequence on a workstation, in CI or on a shared bench.
03
Field-derived replay
Normalize supported PCAPNG, ASC, BLF, CSV and JSONL evidence into semantic replay while establishing a fresh protocol session.
A continuously available shift-left validation layer
Earlier than SIL. Everywhere HIL cannot be.
SDV Labs complements commercial SIL, network-analysis ecosystems, HIL and vehicle testing. It lets requirement, architecture and ECU teams visualize conditions and validate interface behavior on everyday engineering infrastructure.
DefinitionRequirements · architecture · ARXML
SDV LabsDeveloper · CI · test · architecture
Commercial SILHigher-fidelity models and analysis
HIL & vehiclePhysical and release validation
Requirements
Experience intended vehicle conditions and target reactions before hardware is available.
Developer & CI
A local, deterministic rest-of-vehicle environment beside every approved build.
Test
One HMI for exploratory, scenario-based and field-derived validation.
Architecture
A reviewable view of interfaces, deployment and unresolved contracts.
Customer-controlled by design
Your engineering IP stays in your boundary.
Local processing
No external AI provider or SDV Labs cloud is required.
Controlled delivery
Evaluation customers receive an audited image—not the private source repository.
Approved networks
Deploy inside a customer-managed engineering boundary.
Explicit evidence
Diagnostics and reports support repeatable technical review.
Founding evaluation
Bring your ARXML. Leave with a runnable validation environment.
A 30-day, non-production evaluation can be scoped around your interfaces, target application and acceptance evidence.