The Automotive CAN Bus, short for Controller Area Network, is a communication protocol that has become the backbone of vehicle communication systems. Originally developed by Robert Bosch GmbH in the 1980s, this standard has evolved to address the growing complexity of in-vehicle electronic systems. The Automotive CAN Bus allows various electronic control units (ECUs) in a vehicle to communicate with each other, enabling seamless integration and coordination of different functionalities. In this article, let us explore the applications of CAN and the higher-level protocols used in automotive systems.
CAN Standard specifies the Physical Layer and Data Link layer of the standard OSI model. Running on 2 wires with necessary line-termination resistors, CAN uses differential signaling for robust performance. CAN specifies detailed bit timing in terms of smaller time units called quanta. It also employs bit stuffing as an NRZ (Non-Return-to-Zero) encoding mechanism.
The CAN communication is organized as frames with 2 different variants — Standard Frame Format and Extended Frame Format. CRC checks are used along with an acknowledgement mechanism to provide reliable communication.
The Automotive CAN Bus finds extensive applications in modern vehicles. One of its primary uses is in the transmission of sensor data. Sensors located throughout the vehicle measure parameters such as engine speed, temperature, brake status, and tire pressure. The Automotive CAN Bus facilitates the transmission of this data to the relevant ECUs, ensuring effective monitoring and control of vehicle performance.
Each ECU in the system is assigned a unique node address and the ID is used to identify the originating party of the CAN frame.
In addition to sensor data, the Automotive CAN Bus also enables communication between various ECUs responsible for different systems in the vehicle. For example, the engine control unit can communicate with the transmission control unit to optimize gear shifts, resulting in improved fuel efficiency and smoother driving. The Automotive CAN Bus also allows communication between safety systems, such as the anti-lock braking system (ABS) and the electronic stability control (ESC), enhancing vehicle safety.
While the CAN standard specifies only the lower layers, higher-level protocols are often utilized on the CAN vehicle communication network to enable application-specific functionalities. The most used protocol is the In-Vehicle Networking protocol where the ECUs communicate values as Signals organized as Messages. The OBD-II (On-Board Diagnostics) protocol provides standardized access to diagnostic information in vehicles. It allows service technicians to retrieve fault codes, monitor vehicle performance, and perform emissions testing, aiding in vehicle maintenance and repair.
The Unified Diagnostics Services protocol is used for running vehicle diagnostics, end-of-line configuration, and servicing. Another higher-level protocol commonly used for CAN vehicle communication is the J1939 protocol, primarily employed in heavy-duty vehicles and off-road equipment. The J1939 protocol defines a set of standard parameter groups and messages, facilitating communication between different vehicle systems.
The Automotive CAN Bus has established itself as the dominant communication protocol in the automotive industry. Its widespread adoption can be attributed to its reliability, scalability, and cost-effectiveness. According to a report by Precedence Research, the global automotive communication technology market size was valued at USD 7.63 billion in 2020, with a majority dominated by CAN. It is expected to grow with a compound annual growth rate of 6.9%.
The breadth of Automotive CAN bus stack development tools, silicon support, and engineering expertise is unmatched among in-vehicle protocols. Automotive CAN bus stack development spans the physical layer transceiver, the CAN driver, the protocol stack (CAN TP, UDS, OBD-II), and the DBC-based signal layer — making it a full-stack engineering discipline. Engineers pursuing Automotive CAN bus stack development benefit from a mature toolchain including Vector CANoe, PEAK Hardware, and open-source SocketCAN libraries. The strong market share of the Automotive CAN Bus can be attributed to its ability to handle real-time data transmission, robust error detection and correction mechanisms, and low implementation cost.
The CAN protocol offers several advantages in vehicle communication. Firstly, its low latency and high reliability make it suitable for real-time applications, such as engine control and active safety systems. The distributed nature of the protocol ensures that even if one ECU fails, the remaining ECUs can continue to communicate, maintaining overall system functionality.
Secondly, the CAN vehicle communication is highly scalable. It supports a hierarchical architecture, allowing for the addition of new ECUs without significant changes to the existing network. This flexibility enables the integration of new functionalities as vehicles evolve, without the need for extensive rewiring.
Lastly, the CAN protocol has a low implementation cost compared to other communication protocols. Its simplicity and wide availability of compatible components make it a cost-effective choice for automotive manufacturers.
While the CAN protocol has many advantages, it also has some limitations. One of the primary drawbacks is its limited bandwidth. The original CAN protocol supports data rates up to 1 Mbps, which may not be sufficient for applications requiring high-speed data transmission, such as high-definition video streaming or large software updates.
Another disadvantage is the lack of built-in security features. The CAN protocol does not include encryption or authentication mechanisms, making it susceptible to unauthorized access and potential security breaches. However, various solutions and best practices have been developed to address these security concerns, such as secure gateways and intrusion detection systems.
The CAN standard is continuously evolving to meet growing automotive market needs, with variants introduced on top of classic CAN 2.0. One such variant is CAN-FD (Flexible Data Rate), which allows for increased data transmission rates, making it suitable for applications requiring high bandwidth, such as advanced driver assistance systems (ADAS). The CAN XL (eXtra Long) aims to address further increasing bandwidth requirements by supporting data rates up to 20 Mbps.
Furthermore, the integration of the Automotive CAN Bus with other emerging technologies, such as Ethernet and wireless communication, is expected to further expand its capabilities. The combination of different communication protocols enables seamless integration of various systems, paving the way for advanced functionalities like autonomous driving and vehicle-to-vehicle communication.
CAN protocol implementation in automotive design requires careful attention to bit timing parameters, bus termination, error frame handling, and multi-frame transport protocols such as ISO 15765-2. From hardware transceiver selection and PCB layout to AUTOSAR COM stack configuration and DBC-based signal mapping, CAN protocol implementation in automotive design spans the complete embedded stack. Our software-defined vehicles services leverage Automotive CAN Bus expertise to enable seamless ECU integration, helping OEMs transition from hardware-defined to software-defined vehicle architectures.
Data throughput in CAN bus has evolved from the original 1 Mbps ceiling of classic CAN 2.0 to 8 Mbps in CAN-FD and up to 20 Mbps in CAN XL. Understanding data throughput in CAN bus is critical for automotive network designers who must balance bus load, message latency, and priority-based arbitration. Embien's digital transformation services include automotive network load analysis, CAN-to-CAN-FD migration planning, and DBC optimization — helping OEMs maximize data throughput in CAN bus across all vehicle segments.
The Automotive CAN Bus has revolutionized vehicle communication, providing a robust and cost-effective solution for integrating various electronic systems in vehicles. Its wide adoption and dominance in the automotive industry can be attributed to its reliability, scalability, and low implementation cost. While the CAN protocol has its limitations, ongoing advancements are addressing these shortcomings and ensuring its relevance in future automotive bus systems.
As vehicles become more connected and autonomous, the importance of efficient and secure communication protocols like CAN will only increase. With further advancements on the horizon, the future of CAN vehicle communication looks promising. Contact us to utilize Embien's vast experience in Automotive CAN Bus design and Automotive CAN bus stack development.
Embien's edge computing services support Automotive CAN Bus development — from CAN vehicle communication stack integration and ECU firmware development to CAN-FD migration and protocol validation.
Embien's electronics product development services cover Automotive CAN Bus hardware design — including CAN transceiver selection, PCB layout, Automotive CAN bus stack development, and EMC testing.
A case study on developing a wireless Automotive CAN Bus bridge using eStorm-B1 EVK — demonstrating Embien's expertise in CAN vehicle communication, Automotive CAN bus stack development, and wireless connectivity integration.