One real ECU is enough
The tool plays every other node, so bench work starts the day the first ECU arrives.
Keep the ECU in a real vehicle state — without the whole vehicle.
Rest-bus simulation plays every other node from your own network matrix, so one real ECU sees the traffic it expects.
Why Testing Simulation
Traffic from your own matrix
Cyclic traffic is rebuilt from the DBC or ARXML you import, so the ECU never faces a silent bus.
No hardware to evaluate
A virtual CAN channel runs the whole setup with no bus hardware, so an evaluation ships nothing.
Scope
Drives the buses the ECU actually sits on.
- CAN
- CAN-FD
- Automotive Ethernet
- UDS
Capabilities
One bench. Play the rest of the car, replay the drive, drive any frame.
Rest-bus simulation
Every node but the ECU under test sends its cyclic frames from the imported matrix.
Capture and replay
Record CAN to BLF and Ethernet to PCAP; replay at recorded timing, the ECU's own frames left out.
Frame injection
Send a single frame or a cyclic stream on any bus; Ethernet over IPv4, IPv6 or raw layer 2.
Signal override
Push a chosen value onto one declared signal; the cyclic payload updates in place.
NodeScript
JavaScript per simulated node: react to traffic, send frames, run UDS, record a verdict.
Live analysis
Signal plots, a database explorer, a diagnostic console and a trace viewer that decodes captures.
In action
One real ECU, the rest of the car playing along.
Everything but the ECU under test plays from the matrix.
- ECU1DUT · real
- GatewayECUrest-busPLAYING
- BodyECUrest-busPLAYING
Replaydrive_cycle.blf
Interactive generatorSingle frame · Cyclic stream
Testing Studio's Simulation edition.
Testing Simulation is the Simulation edition of Testing Studio. Add it to the Pentest or Fuzz edition, or license it on its own for the bench.
- Testing Simulation
- Rest-bus simulation, replay, injection
- NodeScript, live analysis and the Diagnostic Console
- Testing Studio
- Pentest: the security test catalogue
- Fuzz: signal and frame fuzzing with Test Strategy
- AI Assist in both, available to demo
- UN R155 Annex 5 and GB 44495 profiles and reports
Datasheet
At a glance.
- Simulation
- Node-aware rest-bus simulation from the imported matrix, with one node held as the real ECU under test
- Injection
- Interactive generator for a single frame or a cyclic stream on any bus; Ethernet transmit over IPv4, IPv6 and raw layer 2; live signal override
- Capture and replay
- BLF (CAN) · PCAP (Ethernet); replay at recorded timing with the ECU's own frames excluded; VLAN-aware; offline trace viewer with decode
- Scripting
- NodeScript — JavaScript per simulated node (Jint), with a snippet library and a syntax check
- Live analysis
- Signal plots, database explorer, diagnostic console (UDS by parameter, signal or raw hex)
- Buses
- CAN; CAN-FD up to 64-byte frames with BRS; Automotive Ethernet IPv4/IPv6 with 802.1Q VLAN
- Network ingestion
- CAN DBC · AUTOSAR ARXML
- Channels
- A virtual CAN channel for runs with no hardware; SocketCAN for CAN and CAN-FD; a VLAN-capable NIC for Ethernet
- Safety
- Destructive stimuli — flooding, identity spoofing — stay in dry run until explicitly armed
- Deployment
- Windows client ↔ Linux test server (a WSL2 host is enough for a desk bench); on-premise, air-gap friendly
- Licensing
- Per-machine license key
- What you bring
- A network matrix (DBC or ARXML); for a real bench, one ECU and a CAN or Ethernet interface
Evaluate it
See it run against a real ECU — with no hardware on your side.
Rest-bus simulation around one real ECU. No hardware needed.