Contents

CAN XL

The third CAN generation: up to 2,048-byte payloads and data rates of about 10–20 Mbit/s, designed to carry IP and Ethernet frames and bridge CAN and Ethernet worlds.

Why it exists

Zonal architectures need more bandwidth at the edge than CAN FD offers, but full Ethernet for every node is costly. CAN XL extends CAN once more so that a CAN network can carry large payloads and even Ethernet frames.

What it is

  • CAN-style arbitration with a fast data phase of roughly 10–20 Mbit/s.
  • Payloads up to 2,048 bytes, enough for an Ethernet frame.
  • Fields that identify the content type (e.g. a tunnelled Ethernet frame) and a virtual network ID.
  • CANsec provides link-layer authentication and encryption.
Simplified CAN XL frame
Priority ID11 bitsBus arbitration priority
SDT · SEC8 + 1 bitsContent type and extended-content flag
DLC11 bitsEncodes payload length
PCRC13 bitsPreface CRC
VCID8 bitsVirtual CAN network
Acceptance field32 bitsAddressing or content information
Data1–2048 bytesVariable-length payload
FCRC32 bitsFrame CRC

Selected fields in transmission order; payload length varies, and other control bits, stuff bits, switching sequences and frame-ending fields are omitted.

How it is used

Typical scenarios are backbone-like CAN segments with high data rates, and tunnelling IP traffic between a zone controller and edge ECUs. It competes with and complements 10BASE-T1S; the choice depends on existing ecosystem, cost and tooling.

When to consider it

On platforms with deep CAN expertise and tooling that need more edge bandwidth or IP connectivity without a full Ethernet migration.

Best practices

  • Evaluate silicon availability and toolchain maturity early — the ecosystem is young.
  • Compare total cost against 10BASE-T1S for the same edge function.

Common pitfalls

  • Assuming CAN FD tooling and test equipment support CAN XL out of the box.

What it means for your discipline

  • Networks & communication Core

    Evaluates CAN XL against 10BASE-T1S for zonal edge networks; plans tunnelling of Ethernet frames over CAN XL.

  • Hardware & silicon Core

    Needs CAN XL controllers and SIC XL transceivers; first production transceivers appeared in 2026.

  • Base software Partial

    Requires new driver and stack support; AUTOSAR includes CAN XL.

  • Cybersecurity Partial

    CAN XL defines CANsec, a link-layer security protocol, giving authentication and optional encryption on the bus.

  • E/E architecture Partial

    Offers a migration path for CAN-heavy platforms that need more bandwidth without moving everything to Ethernet.

No direct stake: Functional safety · HPC & application software · Diagnostics & lifecycle · Software update & OTA

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)

Not directly involved on this node type.

MCU-based ECU · AUTOSAR Classic
  • Communication — Routes CAN XL payloads and requires stack support for larger frames, tunnelling and configured security handling.
  • ECU abstraction — Abstracts CAN XL hardware through interface and transceiver support compatible with the new frame format.
  • Microcontroller abstraction (MCAL) — Configures CAN XL controllers and handles frame transmission, reception and arbitration and data-phase timing.
  • Microcontroller · HSM — Requires a CAN XL-capable controller and sufficient memory for payloads up to 2,048 bytes.