CAN bus debugging checklist

Dervo Global team · 18 September 2026 · 1 min read

A simple order of checks when a CAN network does not behave.

A simple order of checks when a CAN network does not behave.

Good practice

Check the basics first: bit rate, wiring, common ground and 120 ohm termination at both ends of the bus.
Check the DBC file: IDs, byte order, scaling and cycle times must match what the ECU really sends.
Look for error frames and rising bus load before looking at software.
Compare timestamps to see whether message cycle times are stable or delayed.
Isolate the problem by disconnecting nodes one at a time to find a disturbing node.
Log everything, including the trace before the failure, so it can be replayed later.

Need help putting this into practice? Talk to us about your project.

Dervo Global supports automotive programs with testing and engineering, and growing businesses with simple CRM and HR & Payroll tools.

How a CAN bit is built from time quanta, why every node needs the same sample point, and how to pick settings that work with your clock.

Two platforms, two ways of building ECU software. Here is what each one means for the way you plan, build and run tests.

When features arrive as software updates, testing changes from a phase at the end into a continuous activity. Here is how to prepare.

One is about making the product safe, the other is about how mature your processes are. What each asks for, and where they overlap.