Automotive Embedded Systems for Beginners — Episode 14: CAN Bus Communication Protocol Fundamentals (Updated June 2026)

Skoda VW at Shendra (Plot A-1/1) and Bajaj Auto at Waluj (Plot G-137) together employ more than 18,000 engineers in Chhatrapati Sambhajinagar's auto belt. Both facilities have ramped up ECU software teams in 2025–26, and almost every embedded engineer job description in that corridor lists CAN bus protocol experience. CAN (Controller Area Network) is the serial communication backbone that lets ECUs in a vehicle talk to each other — the engine control unit tells the transmission control unit the current torque demand, the ABS controller tells the stability control module wheel speeds, and hundreds more real-time messages flow on the same two-wire bus. Episode 14 explains CAN from the physical layer through frame structure, arbitration and error handling — everything a beginner needs to read CAN job descriptions with confidence.

▶ Watch on YouTube

What Episode 14 Covers and Why CAN Bus Is the Most Important Protocol to Learn First

Before CAN bus, automotive wiring harnesses were point-to-point — every sensor and actuator had its own dedicated wire to the ECU, making harnesses 50kg or heavier. Robert Bosch GmbH developed CAN in 1983, and it became an ISO standard (ISO 11898) in 1993. Today, every vehicle above a basic moped uses CAN. A modern car runs three to five CAN networks: a high-speed powertrain CAN at 500 kbps–1 Mbps, a medium-speed body/comfort CAN at 250 kbps, a low-speed fault-tolerant CAN at 125 kbps, and diagnostic CAN accessed through the OBD-II port. Understanding CAN gives you the foundation for every other automotive protocol — LIN, FlexRay and CAN-FD all build on or extend CAN concepts.

CAN Physical Layer — How the Two-Wire Bus Actually Works

CAN uses a differential signalling pair — CAN-H (high) and CAN-L (low). A dominant bit (logic 0) is transmitted as CAN-H at 3.5V and CAN-L at 1.5V, a differential of 2V. A recessive bit (logic 1) is transmitted as both lines near 2.5V, a differential near 0V. Termination resistors (typically 120 ohm each end) prevent signal reflections. What most beginners do not realise is that the dominant state wins over recessive — this is the physical basis for CAN's non-destructive arbitration. The maximum network length at 1 Mbps is 40 metres; at 125 kbps the network can extend to 500 metres. In practice, vehicle CAN networks are under 10 metres, which allows the full 1 Mbps data rate.

CAN Frame Structure — SOF, Arbitration ID, Data and CRC Explained

A standard CAN frame (11-bit identifier, CAN 2.0A) contains: Start of Frame (1 dominant bit), Arbitration Field (11-bit identifier plus RTR bit), Control Field (IDE bit plus 4-bit DLC specifying 0–8 data bytes), Data Field (0–64 bytes in CAN-FD, 0–8 bytes in classic CAN), CRC Field (15-bit CRC plus delimiter), ACK Field (slot bit acknowledged by receivers) and End of Frame (7 recessive bits). The extended frame format (CAN 2.0B) uses a 29-bit identifier for larger address spaces. In a typical powertrain CAN at Bajaj Waluj, engine speed (RPM) travels in an 11-bit ID frame with 2 bytes of data at a 10ms cycle time. Knowing how to read a CAN database (DBC file) and decode frames is the entry-level skill at every automotive software team.

Non-Destructive Arbitration — How Multiple ECUs Share One Bus Without Collisions

CAN arbitration is the mechanism that prevents message collisions without any central arbitration unit. Every transmitting ECU monitors the bus while transmitting. If an ECU transmits a recessive bit and reads a dominant bit back, it lost arbitration and immediately stops transmitting and waits. The ECU with the lower identifier wins because lower IDs have more dominant bits in the arbitration field. No data is lost, no retransmission is needed — the higher-priority message completes, and the lower-priority ECU retransmits after the bus is free. In practice this means safety-critical messages (ABS, airbag, engine torque limit) are assigned low CAN IDs, so they always win arbitration over lower-priority comfort messages like seat position memory.

CAN Error Handling — Active, Passive and Bus-Off States

CAN defines four error types: Bit Error (transmitted bit differs from monitored bit), Stuff Error (six consecutive identical bits violate bit stuffing), Form Error (fixed-format field has wrong bit) and CRC Error (received CRC does not match). Every CAN node maintains two error counters: Transmit Error Counter (TEC) and Receive Error Counter (REC). When TEC or REC exceeds 127, the node enters Error Passive state and transmits passive error flags. When TEC exceeds 255, the node goes Bus-Off and stops transmitting entirely. Bus-Off recovery requires an application-level reset sequence. Engineers at Endurance Technologies Sambhajinagar (E-92 MIDC) and Continental Pune deal with CAN error diagnostics using oscilloscopes and CAN analysers like Peak PCAN-USB or Vector CANalyzer.

CAN Bus Career Roles at Skoda VW Shendra, Bajaj Waluj, Endurance and Bosch

CAN bus skills appear in 240-plus embedded engineering job postings in Pune and Sambhajinagar as of June 2026 (Naukri.com). Target employers: Skoda VW Shendra plant (Plot A-1/1, AURIC), Bajaj Auto Waluj (Plot G-137, MIDC Waluj), Endurance Technologies (E-92, MIDC Sambhajinagar), Bosch Automotive Pune and Nashik Road, Continental Automotive Pune, KPIT Technologies Pune, Delphi Technologies Nashik and Force Motors Pune. Fresher embedded engineers with CAN bus knowledge earn Rs 4–7 LPA. Engineers with two to three years of CAN network design and diagnostics experience earn Rs 9–15 LPA (AmbitionBox and Glassdoor 2025). Our Industry 4.0 with AI and Industrial Automation workshop at ABC Trainings covers CAN, LIN, RTOS and ECU design fundamentals across our Pune and Sambhajinagar centres. Call 7039169629 or WhatsApp 7774002496.