CAN Bus Physical Layer, Arbitration, And Fault Confinement
Canonical definition: A CAN network combines a protocol controller, compatible physical-layer transceiver, topology and termination system, bit timing, frame format, arbitration, error detection, fault confinement, and vehicle-specific application messages.
Controller Is Not Transceiver
application software
→ CAN controller: frames, arbitration, CRC, errors, counters
→ transceiver: logic-level TX/RX to differential bus signaling
→ twisted-pair network: topology, termination, stubs, connectors
→ other nodes and gateway
The ESP32-S3 includes one TWAI controller compatible with Classical CAN frame formats. It requires an external physical-layer transceiver. Its TWAI peripheral is not CAN FD-compatible, so it must not be attached to an FD network under the assumption that it will simply ignore the faster data phase.
Arbitration And Identifiers
CAN uses dominant and recessive bus states. Nodes compare the bus while transmitting; a node that sends recessive but observes dominant stops transmitting without corrupting the winning frame. The identifier participates in arbitration, but its application meaning is assigned by the vehicle or higher-layer protocol.
- 11-bit and 29-bit identifiers are frame formats, not universal signal dictionaries.
- Lower numerical identifiers win arbitration when frames begin together.
- Counters, checksums, multiplexing, state, and gateway translation may be part of the application data.
Classical CAN And CAN FD
| Feature | Classical CAN | CAN FD |
|---|---|---|
| payload | up to 8 data bytes | up to 64 data bytes |
| bit timing | one nominal bit-rate region | nominal arbitration phase plus optional faster data phase |
| controller requirement | Classical CAN controller | CAN FD-capable controller |
| application meaning | still vehicle- and protocol-specific | |
Physical-layer variants, transceiver capabilities, bit timing, sample point, propagation delay, and network topology must match the actual bus.
Error States
CAN nodes track transmit and receive errors. Fault confinement moves a repeatedly failing node through error-active, error-passive, and bus-off behavior. Bus-off is evidence of a fault or incompatible setup; it is not something to bypass until the wiring, timing, transceiver, and software are understood.
Safe Observation Workflow
- Identify the exact bus and gateway side from service information.
- Confirm Classical CAN versus CAN FD and the physical-layer variant.
- Use a correct transceiver, high-impedance instrumentation, and transmit-disable or listen-only safeguards.
- Verify termination and resistance only in the correct power and service state.
- Record bit rate, sample point, frame formats, bus load, errors, wake traffic, and vehicle state.
- Do not assign meaning to identifiers without supported vehicle-specific evidence.
Develop arbitration, filters, transmit behavior, and bus-off recovery on an isolated bench network. Do not transmit into unknown propulsion, chassis, restraint, security, or driver-assistance networks.