CAN Protocol DESD @ SUNBEAM INFOTECH

Introduction
 CAN protocol is method of communication between
various electronic devices. If defines set of rules for
communication in a network of devices.
 Original idea initiated Robert Bosch in 1983. However
first release of CAN protocol is done in 1986.
 Protocol is implemented in hardware and software to
communicate between different controllers present in the
CAN Protocol automobiles.
 Nowadays this protocol is used in various industries
including Healthcare (ICUs & Operation Rooms),
Controller Area Network Entertainment (light control, door control in studios,
gambling machines), Science (high energy experiments,
astronomical telescopes).

Automobiles – Prior invention of CAN Drawbacks & Limitations of Wired System

 Number of wires in various subsystem makes the system
complicated and difficult to maintain.
 Passing real time information among subsystems was
tedious implementation (serial protocols used).
 Asynchronous transmitter/receiver do not support multi-
domain communication e.g. communication between air-
conditioning system and door/window system.
 Multiple domains in automobiles includes power
generation (engine), chassis (driving mechanism), body
(climate control/wipers), telemetric (entertainment units)
and passive safety (air bags, etc).

Automobile System – with CAN protocol CAN Architecture

 CAN protocol is implemented with OSI reference model.
 It implements two layers of OSI model and rest are left
for implementation specific to the requirement.
 Data Link Layer
 Logical link control
 Allows filtering of messages based on UID.
 Medium access control
 Prepare message frame and handle arbitration.
 Physical Layer
 Send bits to the CAN two wire bus as per timing
requirements.

NILESH GHULE 1
 CAN Protocol DESD @ SUNBEAM INFOTECH

CAN Architecture CAN Node

 Each electronic device is called as Node.

 Host-controller is MCU responsible for functioning of node.
 CAN controller converts messages of node as per CAN
protocol. Can be a separate chip or embedded in MCU.
 Trans-receiver is to transmit bits on CAN bus.

CAN Bus CAN Frame

 CAN bus is a two twisted wire bus i.e. CANH & CANL.  CAN is a message based protocol (not address based).
 The passive voltage of each line is 2.5 V.  Message contains a pre-defined unique id (rather than
 The active voltages are 3.5 V and 1.5 V. addresses).
 When both lines are 2.5 V, difference is 0 V. It represent logic 1  Messages are accepted or rejected by any node based on this
& called as “recessive bit”. UID. If multiple nodes send messages at same time, node with
 When both lines are pulled to 3.5 V and 1.5V respectively, then highest priority gets bus access.
difference is 2 V. It represent logic 0 & called as “dominant bit”.  CAN message is made up of 10 bytes.
 Note that dominant bit can always overwrite recessive bit.  Each message is coded into meaningful sequence of bits/bytes
 CAN bus is a linear bus terminated with 120 Ω. Also input called as frame.
impedance of each node is 120 Ω.  Framing is done by Medium Access Layer.
 CAN bus is not a master slave bus i.e. Any node can write  There are two types of frames:
the data on the bus in certain format (frame) provided  Standard CAN Frame
bus is available.  Extended CAN Frame

CAN – Standard Frame CAN – Extended Frame

 SOF: Start of Frame – Dominant bit – For Sync.

 UID: Type of message and Arbitration.  SRR: Substitute Remote Request : Recessive bit [like RTR]
 RTR:Type of frame i.e. Data Frame [Dominant] or Remote Transmission  11-bit Id + 18 bit Id = 29 bit Id – Extended Message Id.
Request (RTR) Frame [Recessive].
 RTR frame don’t have data, instead request other node to send data.  R1: Additional reserved bit.
 IDE: UID Extension. Standard (dominant) or Extended (recessive) frame.  Types of Frames:
 R0: Reserved for future use.
 Data Frame
 DLC: 4-bit data length code [0 to 8 bytes – data length]
 DATA: 0 to 8 bytes
 Remote Frame
 CRC:15 bits CRC + 1 bit delimiter (recessive)  Error Frame: When error is detected, transmission aborts and
 ACK:Transmitter sent recessive bit, Rcvr overwrite with dominant. + 1 bit send this frame.
delimiter (recessive)  Overload Frame: Like error frame, sent by node when busy in
 EOF: 7-bits (recessive) to indicate End of Frame. internal processing.
 IFS: 3 recessive bits - Intermission bits – Separation between two frames.

NILESH GHULE 2
 CAN Protocol DESD @ SUNBEAM INFOTECH

CAN – Error and Overload Frames CAN Error Detection & Handling
 There are five methods of error detection.
 Message Level Error Detection.
 CRC check
 ACK slots
 Form error
 Bit Level Error Detection.
 Stuff error
 Bit error
 If node detects an error, following steps occurs:
 Transmits error flag.
 Destroys transmitted frame.
 Transmitting node resends the frame.

CAN – Error Detection CAN – Error Detection

 CRC check:  Bit Stuff Error:
 Calculated and sent by transmitter node.  CAN bus is never IDLE as it follows NRZ method (non-
 Receiver node recalculate CRC and if differs, raise error. returning to zero i.e. 0 & 1 is represented as non-zero values -
differential).
 ACK slots:
 For sake of synchronization one bit of opposite polarity is
 Transmitter send recessive bit & Receiver overwrite dominant added after consecutive 5 bits of same polarity, called as bit-
 If none of the node overwrite dominant bit, error is raised. stuffing.
 FORM (FORMAT) error:  Stuffed data frames are de-stuffed by data link layer of receiver.
 EOF, IFS, ACK delim bits are always recessive.  If error is found in stuffing, error is raised.
 If dominant bit is found, error is raised.  In CAN, 6 consecutive recessive/dominant bits represent error
 BIT error: bits.
 Transmitter always monitor sent bit.  All fields in the frame are stuffed with the exception of the
CRC delimiter, ACK field and end of frame which are a fixed
 If sent bit is not validated error is generated, except in case of
size.
arbitration and acknowledgment bit.

CAN protocol – Advantages

 Low cost: Only two wire serial bus.
 Reliable: Error detection & handling. Immune to noise.
 Flexibility: Nodes can be easily added or deleted.
 High speed: Support data rate of 1 Mbits/sec @ 40m bus.
 Multi-master bus: Any node can access bus.
 Fault confinement: Faulty nodes do not disturb commn.
 Broadcast capability: One to One/Many/All commn.
 Standardization: ISO standardized.
 ISO-DIS 11898 : High speed communication
 ISO-DIS 11519-2 : Low speed communication

NILESH GHULE 3