What it is
CAN in Automation (CiA) is the industry group that publishes specifications for building systems on Controller Area Network. ISO 11898 defines the CAN data link — classical CAN, CAN FD, and CAN XL — and the common high-speed physical layer. It leaves higher-layer behavior and many wiring choices open. CiA specifications fill that gap: communication profiles, device profiles, physical-layer recommendations, and, for CAN XL, the CANsec security protocol.
CANopen (CiA 301) is the best-known profile. CANopen FD (CiA 1301) carries the same model onto CAN FD. Each document is numbered and revised on its own, so you cite a specific part and edition.
Who it applies to
These specifications apply to teams that design, supply, or integrate a CAN, CAN FD, or CAN XL network using a CiA protocol or physical-layer recommendation. ECU makers, protocol-stack vendors, and the network owner all have work to do.
Passenger-car powertrain and body buses usually follow an OEM catalog and an AUTOSAR stack. CiA documents still apply to off-highway and special vehicles, charging equipment, CANopen subsystems, CAN FD wiring design, and CAN XL links that use CiA higher layers or CANsec.
What it covers
The families below are the ones automotive and machine networks actually implement.
| Family | What it adds |
|---|---|
| CANopen (CiA 301) and CANopen FD (CiA 1301) | Object dictionary, process data, service data, and network management |
| Device profiles such as CiA 401 (I/O) and CiA 402 (drives) | Objects a device class must implement so vendors interoperate |
| Physical-layer recommendations | Topology, bit timing, cabling, and transceiver practice on ISO 11898-2 |
| CANopen Safety (CiA 304) | Safety communication for safety-related data on CAN |
| CAN XL higher layers and CANsec | Use of the CAN XL frame above ISO 11898-1, plus authentication and optional confidentiality |
A CANopen node exposes an object dictionary. Cyclic signals use process data objects. Configuration uses service data objects. The device profile freezes that dictionary so one vendor can replace another.
How it fits with other documents
ISO 11898-1 is the data link. ISO 11898-2 is the high-speed physical layer. CiA documents describe how projects apply those standards on a real network.
AUTOSAR is the usual car stack. The CAN driver, the CAN interface, and COM move PDUs from the OEM catalog. CANopen has its own identifiers, dictionary, and network management. A gateway can translate. Running both layers on one bus requires a written mapping.
Diagnostics in cars use UDS (ISO 14229), often over ISO 15765. A CANopen node answers service data. UDS support has to be specified on its own.
CANsec protects CAN XL frames. AUTOSAR Secure Onboard Communication protects AUTOSAR PDUs. Each mechanism belongs to its own communication stack. ISO/SAE 21434 still governs the cybersecurity process, and ISO 26262 still governs functional safety. CiA 304 is only a communication measure you may use inside a safety case.
In practice
Pick the application layer before you assign identifiers. On an AUTOSAR or raw OEM bus, CiA 301 applies only if a node implements CANopen. A CiA wiring recommendation can still govern the harness. On CANopen, the contract is the electronic data sheet and the device profile: which objects exist, which are process data, and which node manages the network.
CAN FD links usually fail on bit timing, sample point, topology, or the transceiver. Agree those with ISO 11898-2 and the CiA recommendation before blaming software.
On CAN XL, read the ISO data link, the CiA higher layer, and CANsec together. Decide authentication versus encryption, and how keys are provisioned, while the controller can still change. For safety-related signals, record in the safety concept whether the channel uses CiA 304 or another named protection.