...
🇨🇳 Meet SonnePower at bauma CHINA 2026   |   Nov. 24–27, 2026   |   Shanghai New International Expo Centre (SNIEC)   |   BOOTH N1.576 🇨🇳 Meet SonnePower at bauma CHINA 2026   |   Nov. 24–27, 2026   |   Shanghai New International Expo Centre (SNIEC)   |   BOOTH N1.576

What Causes CAN Bus Off Error?

Table of Contents

Short Answer

A CAN bus-off error occurs when a node’s Transmit Error Counter (TEC) exceeds the protocol-defined limit due to repeated communication failures. These failures are commonly caused by wiring or termination issues, electromagnetic interference, baud rate or bit timing mismatches, or improper CAN controller configuration.

In CAN-based control systems, few issues are as disruptive—and as frustrating—as a CAN bus-off error. When a node enters the bus-off state, it is forcibly disconnected from the network, often causing machines to stop operating entirely.

What makes bus-off especially challenging is that it is not a single fault, but the final result of accumulated communication errors. In complex, multi-node systems, the root cause is often hidden beneath layers of physical, protocol, and configuration issues.

This article explains what causes a CAN bus-off error, how it develops at the protocol level, and how engineers can recover and prevent it in real-world applications.

Understanding the CAN Bus-Off State

What Is a CAN Bus-Off State?

The bus-off state is a self-protection mechanism defined by the CAN protocol. Its purpose is to prevent a faulty node from continuously disrupting communication on the network.

When a node enters bus-off:

  • It immediately stops transmitting CAN frames

  • It no longer participates in arbitration or acknowledgment

  • Communication can only resume after a defined recovery process

Bus-off is not a random failure. It is the end stage of escalating CAN errors.

CAN bus off error illustrated in an industrial CAN network with one ECU disconnected

CAN Error States Overview

CAN defines three error states that describe how a node behaves as errors accumulate:

  • Error-Active
    The node operates normally and participates fully in communication.

  • Error-Passive
    The node has detected frequent errors and becomes less disruptive, limiting how it signals errors.

  • Bus-Off
    The node is completely disconnected from the CAN network.

A node always transitions through these states in sequence. It cannot jump directly from normal operation into bus-off.

How Error Counters Trigger Bus-Off

Transmit Error Counter (TEC) vs Receive Error Counter (REC)

Every CAN controller maintains two internal counters:

  • Transmit Error Counter (TEC) – increases when transmission errors occur

  • Receive Error Counter (REC) – increases when reception errors occur

While both counters matter, bus-off is almost always triggered by the TEC. Failed transmissions—especially those without acknowledgment—cause the TEC to rise quickly.

Bus-Off Threshold Explained

According to the CAN specification, when the transmit error counter exceeds the bus-off threshold (commonly 255), the controller must enter the bus-off state.

This design ensures that:

  • A malfunctioning node cannot dominate the bus

  • Healthy nodes can continue communicating

  • Overall network stability is preserved

Protocol-Level Errors That Cause Bus-Off

Bit Errors

A bit error occurs when a node transmits a dominant or recessive bit but reads back a different value from the bus.

Common causes include:

  • Electrical noise

  • Faulty transceivers

  • Signal reflections due to poor termination

Repeated bit errors rapidly increase the TEC.

CRC Errors

Each CAN frame includes a cyclic redundancy check (CRC) to ensure data integrity. If the calculated CRC does not match the received value, the frame is rejected.

CRC errors are often linked to:

  • Signal distortion

  • Grounding problems

  • Electromagnetic interference

Acknowledge (ACK) Errors

Every CAN frame must be acknowledged by at least one other node. If no acknowledgment is detected, the transmitter assumes the frame failed.

ACK errors commonly occur when:

  • Only one node is active on the bus

  • Other nodes are powered down

  • Baud rate or bit timing is mismatched

Physical Layer Problems Behind Bus-Off Errors

Termination Resistance Issues

Proper CAN termination is essential for signal integrity. A typical CAN bus requires two 120-ohm termination resistors, one at each end of the network.

Bus-off can occur when:

  • Termination resistors are missing

  • Too many terminators are installed

  • Incorrect resistor values are used

Improper termination causes reflections and unstable voltage levels on the bus.

CAN_H / CAN_L Wiring Faults

Wiring issues are among the most common real-world causes of bus-off:

  • CAN_H and CAN_L swapped

  • Broken wires or loose connectors

  • Shorts to ground or power

These faults lead to continuous transmission errors and rapidly increasing TEC values.

Electromagnetic Interference (EMI)

In environments such as electric mining trucks or large construction machinery, CAN networks are exposed to:

  • High-current switching devices

  • Motors and inverters

  • Long cable runs

In these conditions, standard CAN transceivers may accumulate transmission errors quickly, pushing the TEC toward the bus-off limit.
SonnePower vehicle controllers integrate automotive-grade isolated CAN transceivers, improving noise immunity and helping maintain stable communication even in high-interference environments.

Configuration and Firmware Causes

Baud Rate and Bit Timing Mismatch

Even small mismatches in baud rate or bit timing parameters can cause persistent CAN errors.

Typical configuration mistakes include:

  • Incorrect sample point settings

  • Wrong propagation or phase segment values

  • Using timing parameters copied from systems with different clock frequencies

These issues often resemble physical faults but originate entirely in software configuration.

Missing or Incomplete Bus-Off Recovery Logic

Some systems remain permanently offline after entering bus-off—not because of hardware damage, but because recovery logic was never implemented.

Common firmware issues include:

  • Automatic bus-off recovery disabled

  • No software reset of the CAN controller

  • Improper handling of controller error flags

How to Recover from a CAN Bus-Off Error

Automatic vs Manual Recovery

Bus-off recovery behavior depends on the CAN controller:

  • Some controllers recover automatically after an idle period

  • Others require explicit software intervention

  • Some require a full reset or power cycle

Always verify recovery behavior in the controller documentation.

Practical Recovery Steps

  1. Stop CAN transmission immediately

  2. Reset or reinitialize the CAN controller

  3. Verify termination, wiring, and grounding

  4. Confirm baud rate and bit timing on all nodes

  5. Resume communication while monitoring error counters

If bus-off reoccurs, the underlying cause has not been resolved.

Practical CAN Bus-Off Troubleshooting Checklist

Use this checklist when diagnosing a bus-off error in the field:

  1. Measure resistance between CAN_H and CAN_L

  2. Inspect wiring and connectors

  3. Verify baud rate and timing consistency

  4. Isolate nodes to identify faulty devices

  5. Monitor transmit error counter behavior

Final Thoughts

A CAN bus-off error is not a mysterious failure—it is a clear signal that persistent communication problems exist. In most systems, the root cause lies in physical layer integrity, configuration mismatches, or insufficient noise immunity.

By understanding how error counters, protocol rules, and real-world conditions interact, engineers can resolve bus-off issues faster—and design CAN networks that remain stable under the harshest operating conditions.