← Related research
Automate CAN-based ECU testing without losing the engineer in the loop
A CAN or ECU test procedure is never just "send a frame."

It is acquire the interface, send only the approved message, watch the gateway or ECU response, capture evidence, and release the bus cleanly. Every one of those steps is usually done by hand, on a laptop, by whoever is free that day.
Release-gate CAN capture
An example run.
Release-gate CAN captureExample run
- Commanded pressure
- 38.2 bar
- Measured pressure
- 37.9 bar
- Gateway dropouts
- 0
- Decision
- release evidence ready
The workflow today
- Attach the adapter and bring the bus up manually before every run
- Hand-craft or replay raw frames from a DBC, one test at a time
- Watch signals in a scope tool and decide pass/fail by eye
- Write up what happened afterward, from memory or screenshots
With Plotune Nexus
- Acquire the CAN interface as a bounded operation, released when the run ends
- Encode and send only the approved message from your DBC, at the required cycle time
- Gate the next step on a decoded signal condition instead of a fixed wait
- Package the run as one reviewable artifact: trace, decoded signals, and verdict together
Works with.
Supported integrations for this workflow.
- Classic CAN
- CAN FD (SocketCAN)
- DBC decode / encode
- XCP-on-CAN
- UDS over CAN / DoIP
More Nexus workflows.
Nexus
ROS 2 / DDS testing
Run unattended hardware tests and judge requirements on live telemetry, without ROS tooling on your side.
See the workflow →Nexus
Test automation
Let agents run, watch and re-run sequences, so an engineer is not needed in the loop for every build.
See the workflow →Nexus
AI hardware-in-the-loop
Give AI agents access to real hardware while you keep control of the boundary.
See the workflow →See this mapped to your bench.
Plotune Nexus is one product. This is how it runs against CAN / ECU Testing.





