Confirm the driver and channel, match the nominal bitrate and CAN mode, verify frame format and identifiers, use correct termination, start with a controlled Dry run, and observe the first live traffic independently. Save the exact adapter and bus settings with the scenario.
1. Record the adapter path
- Adapter make, model, serial number, and firmware when available.
- Windows version, driver version, and application interface.
- Physical channel and any serial or COM mapping.
- Nominal bitrate, CAN FD setting, and data bitrate when applicable.
This record matters because a working rate trim or driver setting may be specific to one complete path.
2. Check the physical bus
Use an isolated, approved bench. Confirm CAN High, CAN Low, and reference ground where required. Check that termination matches the intended topology and that the adapter is not being asked to power a bus it was not designed to power.
Do not connect to a live vehicle or safety-relevant network for an exploratory first run.
3. Validate identifiers and packing
Confirm 11-bit versus 29-bit identifiers, classic CAN versus CAN FD, DLC, byte order, signedness, scaling, offset, and bounds. A receiver can accept a frame electrically and still interpret the payload incorrectly.
4. Start with one visible scenario
Choose one frame and a signal change that is easy to recognize. Run the scenario in Dry run, validate it, and review the encoded frames. Then connect the isolated hardware and transmit at a conservative rate before adding the rest of the scenario.
The free simCAN starter pack provides a 12-second speed profile for this purpose.
5. Observe and preserve evidence
| Evidence | Question answered |
|---|---|
| simCAN console and diagnostics | Did the application schedule the scenario and report adapter results? |
| Independent analyzer or logger | What frames and timing appeared on the bus? |
| Receiver log or output | Did the downstream system process the intended states? |
| Saved scenario and settings | Can another operator repeat the test? |
6. Scale the test deliberately
Add messages, rates, and background load in controlled steps. If timing changes, compare the requested, scheduled, accepted, observed, and received rates before deciding where the constraint lives.
Run a safe first scenario.
Start with the free workbook and DBC, keep Dry run selected, and move to an isolated adapter bench only after the model and settings are reviewed.