Error counters describe communication problems observed by a controller. They do not provide a complete map of the underlying wiring or component fault.

Interpreting the evidence

If several modules report communication trouble, build a timeline using their supplies, network state and recorded symptoms. Ask which measurements show the fault starting, rather than assuming the module with the largest displayed count caused it. Keep the network topology with the report.

Keep this evidence

Record the counter source, test duration and any connection changes made during measurement.

A count without test conditions is difficult to compare. Repair decisions need the physical and operational evidence behind the number.

Speak to AXION

For CAN-bus and vehicle-network diagnostics, send your vehicle details and fault report. Workshop assessment is in Didcot, Oxfordshire. Suitable postal or remote work is confirmed before booking.

Technical background from Kvaser. The referenced design explains the principle; the vehicle-specific procedure determines the repair.

Related reading — CAN load percentage and a slow scan-tool response. Browse all vehicle-electronics diagnostic notes or return to the repair library.