wire / wire-format / can-frame

CAN (Controller Area Network) frame

A CAN 2.0 frame: 11-bit (or 29-bit extended) identifier, RTR bit, IDE bit, DLC (data length code, 0-8), then 0-8 bytes of data, CRC-15, ACK, EOF. CAN FD extends DLC to 0-64 bytes with a different CRC. CAN is used in automotive, industrial, and aerospace systems.

wire-format kind wire-format status standard verification verified tier B wire-format@1

aka: CAN (Controller Area Network) frame

wire format

spec: ISO 11898-1 (CAN)

A CAN 2.0 frame: 11-bit (or 29-bit extended) identifier, RTR bit, IDE bit, DLC (data length code, 0-8), then 0-8 bytes of data, CRC-15, ACK, EOF. CAN FD extends DLC to 0-64 bytes with a different CRC. CAN is used in automotive, industrial, and aerospace systems.

fieldsizemeaning
SOF1 bitStart of Frame (dominant).
Identifier11 bits (standard) or 29 bits (extended)Message identifier (also determines priority; lower = higher priority).
RTR1 bitRemote Transmission Request (1 = request data from a node with this ID).
IDE1 bitIdentifier Extension (0 = standard 11-bit, 1 = extended 29-bit).
r01 bitReserved (must be dominant/0).
DLC4 bitsData Length Code: 0-8 bytes (CAN 2.0), or 0-15 (CAN FD: 0-8, 12, 16, 20, 24, 32, 48, 64).
Data0-8 bytes (CAN 2.0) or 0-64 bytes (CAN FD)Payload (up to 8 bytes for CAN 2.0, up to 64 for CAN FD).
CRC15 bits (CAN 2.0) or 17/21 bits (CAN FD)Cyclic redundancy check.
ACK2 bitsACK slot (dominant = at least one receiver accepted) + ACK delimiter (recessive).
EOF7 bitsEnd of Frame (all recessive).
IFS3 bitsInter-Frame Space (all recessive).

example:

00 00 00 00 00 00 00 00 00 00 00 00 00 00

CAN 2.0 standard frame (simplified bit-level; shown as byte-aligned for illustration)


provenance

agent: curl -H 'accept: application/json' wire.phall.io/wire-format/can-frame or /wire-format/can-frame.json