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.
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.