The Controller Area Network (CAN) protocol, like many sophisticated networking protocols, is structured into distinct abstraction layers, each responsible for specific functions. This layered approach
allows for a modular and organized design, facilitating development and troubleshooting. Understanding these layers—the application, object, and transfer layers—is crucial to grasping how CAN bus efficiently manages communication between electronic control units (ECUs). While the application layer handles application-specific logic and the object layer manages message filtering and status, the transfer layer is where much of the CAN standard's complexity and functionality reside, acting as the bridge between the physical transmission and higher-level processing.
The Transfer Layer: The Heart of CAN Protocol
The transfer layer is arguably the most critical component of the CAN protocol, encompassing the majority of the standard's specifications. Its primary role is to receive messages from the physical layer and transmit them to the object layer, ensuring reliable and ordered data flow. This layer is burdened with a multitude of responsibilities, including bit timing and synchronization, which are essential for coordinating data transmission across multiple devices. It also handles message framing, which defines the structure of the data packets, and arbitration, the mechanism that resolves conflicts when multiple devices attempt to transmit simultaneously.
Furthermore, the transfer layer is responsible for acknowledgment, confirming successful message reception, and robust error detection and signaling, which are vital for maintaining data integrity. Finally, it manages fault confinement, a process that isolates faulty nodes to prevent them from disrupting the entire network. These functions collectively ensure that the CAN bus operates with high reliability and efficiency, making it suitable for safety-critical applications like those found in automobiles.
The Physical Layer: Electrical Standards and Mechanical Challenges
The physical layer of the CAN bus, as initially specified by ISO 11898-1:2003, provided only abstract requirements, emphasizing the use of a medium that supports multiple-access at the bit level through dominant and recessive states. The concrete electrical aspects, such as voltage levels, current characteristics, and the number of conductors, were later detailed in ISO 11898-2:2003, which has become the widely accepted standard. This electrical specification defines how signals are physically transmitted and received over the bus.
However, a significant challenge arose from the lack of formal specification for the mechanical aspects of the physical layer. Details like connector types, pin-outs, and cable colors were left undefined. This omission led to a situation where automotive ECUs often featured custom connectors and various cable configurations, with only two lines consistently dedicated to the CAN bus. While this freedom allowed for flexibility, it also introduced interoperability issues due to mechanical incompatibilities between different implementations. To address this, de facto standards, such as the 9-pin D-sub connector with specific pin assignments, have emerged to improve consistency.
Ensuring Interoperability and Noise Immunity
To enhance interoperability, many vehicle manufacturers have developed their own specifications, outlining approved CAN transceivers and requirements for parasitic capacitance on the line, including those related to ESD protection. This is particularly important given the varying voltage requirements in 12V and 24V systems, where line maximum voltages can reach 24V during jump starts in light vehicles and up to 36V in truck systems. New solutions are continuously being developed to allow components to be used across different CAN variants, including CAN FD.
Noise immunity, a critical feature for automotive environments, is achieved in ISO 11898-2:2003 by maintaining a low differential impedance on the bus, typically with 120-ohm termination resistors at each end. This design, while effective for noise reduction, means that a dormant CAN bus draws more current than other voltage-based signaling buses. The standard also incorporates a 0 V rail running along the bus to maintain a high degree of voltage association between nodes, providing immunity to common mode voltage. Best practices recommend using twisted pair wires within a shielded cable for CAN bus signals to minimize RF emissions and reduce susceptibility to interference, further bolstering its reliability in noisy environments.
