Contents
StandardISO

ISO 11898

Road vehicles — Controller area network (CAN)

ISO 11898 defines how CAN controllers and transceivers exchange messages reliably on vehicle networks using Classical CAN, CAN FD and CAN XL.

What it is

ISO 11898 is the standards family behind Controller Area Network (CAN), a communication technology widely used between vehicle electronic control units. It defines the rules for exchanging CAN frames and the behavior of the interfaces that connect controllers to the bus.

The family covers Classical CAN, CAN FD and CAN XL. These are related communication formats with different capabilities; choosing CAN hardware requires more precision than simply asking whether it supports “CAN.” The normative documents are paid standards.

Who it applies to

It matters to engineers developing CAN controllers, transceivers, ECUs, gateways and vehicle networks. Network engineers use it to specify compatible communication behavior, while hardware engineers use the relevant physical-layer requirements when selecting and integrating transceivers.

ECU software teams also need working knowledge of the standard because controller configuration, error recovery and transceiver operating modes affect communication. Vehicle manufacturers and suppliers typically identify applicable parts and editions in project requirements. ISO 11898 is a technical standard, rather than a vehicle approval regulation by itself.

What it covers

Two parts provide the main starting points:

Part Main subject Practical question
ISO 11898-1 Data link layer and physical coding sublayer How does the controller construct, transmit and check CAN frames?
ISO 11898-2 High-speed physical medium attachment How does the transceiver send and receive signals and support applicable low-power functions?

Part 1 includes Classical CAN, CAN FD and CAN XL frame formats. Support depends on the controller implementation; implementing one format does not imply support for every format. ISO part 1 scope

Part 2 addresses high-speed transceiver behavior, including options for low-power operation, selective wake-up and signal improvement. The 2024 edition includes CAN SIC XL physical-layer support. ISO now lists a 2026 edition replacing it, so projects referencing the 2024 edition should review the applicable edition explicitly. ISO part 2 scope and editions

How it fits with other documents

ISO 11898 provides the communication foundation. It does not define the application meaning of a vehicle signal, diagnostic service behavior or a complete vehicle network-management strategy.

ISO 15765-2 provides transport and network-layer services used for diagnostics over CAN, while ISO 14229 defines UDS diagnostic services. AUTOSAR specifications describe software modules that configure and use CAN communication. OEM requirements add project-specific rules for timing, topology, wiring, termination and validation.

CAN error detection also does not establish functional safety or cybersecurity compliance. Those require system-level analysis and, where appropriate, additional communication protection.

In practice

Start a network specification by recording the required CAN format, controller capabilities, transceiver type, timing configuration and applicable standard editions. Treat these as separate choices: a controller supporting CAN XL does not by itself establish a suitable physical connection.

For an existing network, verify every connected node before enabling a different frame format. Validate timing and signal quality on representative hardware and harnesses, including gateway behavior and recovery from communication faults.

For partial networking, check selective wake-up support across the transceiver, its configuration and the software power-management sequence. A transceiver recognizing a wake-up condition is only one step in bringing the required ECU functions back into operation.

What it means for your discipline

  • Networks & communicationCore

    Owns CAN network configuration, timing and compatibility decisions. Uses the relevant parts to assess arbitration, error handling and communication behavior.

  • Hardware & siliconCore

    Selects CAN transceivers and designs their electrical integration. Checks physical-layer capabilities, signal quality and sleep or wake-up behavior.

  • Base softwarePartial

    Configures CAN controller drivers, transceiver control and communication recovery. Must match software settings to the controller, transceiver and network capabilities.

  • E/E architecturePartial

    Chooses where each CAN variant fits in the vehicle architecture. Allocates gateways and network segments with compatible performance and power-management requirements.

  • Functional safetyPartial

    Assesses how CAN communication failures affect safety functions. Treats CAN error detection as one input to the safety design and specifies additional protection where required.

  • Diagnostics & lifecyclePartial

    Checks that diagnostic communication uses compatible CAN interfaces and network settings. Relies on separate transport and diagnostic specifications for diagnostic message behavior.

No direct stake: Cybersecurity · HPC & application software · Software update & OTA