Free · no signup required

CAN Scenario Test Checklist

Use these 22 checks before playing a CAN signal scenario. Confirm the DBC, profiles, adapter, bus, playback plan, and result logging directly in your browser—or print or save the checklist as a PDF.

Try simCAN Free for 7 Days

Project or bench Date Operator

01 | Safety and scope

Know exactly what the bench is allowed to do.

The test is on an isolated, approved bench, not an uncontrolled vehicle network. Expected arbitration IDs, frame formats, rates, and value ranges are documented. Power, termination, grounds, and emergency stop or disconnect are confirmed. A named person owns the go/no-go decision for live transmit.

02 | DBC and signal profiles

Make every intended message and transition unambiguous.

The DBC revision matches the target ECU or device revision. Standard versus extended ID and classic CAN versus CAN FD are correct for every active frame. Signal scale, offset, signedness, start bit, length, units, and min/max have been reviewed. The scenario plot has the intended start state, transitions, duration, and loop behavior. Estimated bus load leaves enough margin for timing accuracy and other required traffic.

03 | Adapter and bus

Confirm the complete path from simCAN to the test network.

Interface, channel, nominal bitrate, CAN FD setting, and data bitrate are correct. The adapter is detected and the required Windows driver/backend is installed. A connection check has opened the real bus and sent a controlled test frame. If timing matters to the test, transmission diagnostics have been run at the planned workload. Any saved adapter timing adjustment belongs to this exact hardware path and is still appropriate.

04 | Scenario playback

Confirm the scenario behaves like the system being simulated.

The scenario begins with known, safe signal values before any transitions occur. Observed frame IDs, update rates, values, and transitions match the intended profile. The receiving software, controller, or data pipeline responds as expected. An external analyzer or logger is connected when independent wire-level evidence is required.

Timing is a supporting check: simCAN diagnostics help identify scheduling or adapter limitations. Use an external analyzer when the test requires independent proof of traffic on the wire.

05 | Results and replay

Save enough evidence to reproduce the result.

Scenario workbook, DBC, app version, adapter model, driver/backend, and any timing adjustments are recorded. A timestamped CAN log or analyzer capture is saved with the test result. Pass/fail criteria and any deviations are written down before the next run. The final scenario can be replayed without relying on undocumented manual steps.

Want to build, play, record, and replay CAN signal scenarios in one app?

Try simCAN on the Windows machine and CAN adapter you plan to use. The full-featured trial does not require a credit card.

Start the 7-Day Trial See What $499 Includes