GURUNANAK INSTITUTIONS TECHNICAL CAMPUS (AUTONOMOUS)

(Accredited by NAACA+, Affiliated to JNTUH HYDERABAD)

DEPARTMENT OF ELECTRICAL AND ELECTRONICS ENGINEERING
REVIEW OF INTERNSHIP PRESENTATION
ON
CONTROL AREA NETWORK (CAN)(Topic Name)
By
M.Saikumar-18WJ1A0272

Internal Guide. Head of the department

B.Sravan kumar K.shanti
Associate professor Professor &HOD
EEE, GNITC EEE, GNITC
Contents:
• Abstract
• Introduction
• History of CAN
• Working Principle
• Types of CAN
• Advantages & Dis advabtages
• Applications
• Conclusion
Abstract
• Desynchronizing streams of frames through the means of offsets has today
become common practice in automotive CAN networks. This is because this
traffic shaping strategy is very beneficial in terms of reducing response times
especially at high load levels. However, to the best of our knowledge, there is no
result available in the literature that allows the response times of frames with
offsets to be calculated for CAN. In this paper, we address this shortcoming of
existing CAN schedulability analysis, and propose an extendible framework built
upon the trans action model to derive worst-case response times (WCRT) on
CAN. As will be shown in the experiments performed on realistic automotive
networks, explicitly integrating offsets in the analysis permits a much tighter
WCRT evalu ation than with the classical synchronous analysis, which ultimately
enables the designer to reduce resource over provisioning.
INTRODUCTION

• CAN bus is a vehicle bus standard designed to allow microcontroller and devices
to communicate with each other in vehicle

• It is a message based protocol.

• It is a multi-master serial bus

History of CAN:
• It was created in mid-1980s for automotive applications by Robert Bosch.

• Design goal was to make automobiles morereliable, safer, and more fuel efficient.

• The latest CAN specification is the version 2.0 made in 1991.

Working Principle:
•Every CAN mechanism consists of a CAN device. This CAN device sends data
across CAN network in the form of packets and these packets are called CAN
frame. Every CAN frame consists of arbitration ID, a data field, a remote frame,
an over load frame and an error frame.
Types of CAN :
• Data Frame:
Used to transmit data
• Remote Frame:
Used to request data transmission
• Error Frame:
Sent by a node that detects an error
• Overload Frame :
Sent by a node to request a delay in transmission
Data Frame:

1. A data frame consists of seven fields: start-offrame, arbitration, control, data,

CRC, ACK,and end-of-frame.
 Remote Frame:
•Used by a node to request other nodes tosend certain type of messages
• Has six fields as shown in Figure . These fields are identical to those of a data
frame with the exception that the RTR bit in the , field is recessive in the remote
frame.
 Error Frame:
• This frame consists of two fields.-
- The first field is given by the superposition of error flags contributed from different
nodes.
-The second field is the error delimiter.
• Error flag can be either active-error flag or passive-error flag.
-Active error flag consists of six consecutive dominant bits.
- Passive error flag consists of six consecutive recessive bits.
• The error delimiter consists of eight recessive bits.
Error Frame:
 Advantages:
• It support multi master and multicast features.
• The CAN bus has maximum length of 40meters.
• The CAN provides the ability to work in differentelectrical environment.
• It has maximum length of 40 meters.
• The controller area network (CAN) reduces.
• It has standard bus in distributed network.
• It cost is low and lightweight network.
• It has automatic retransmission for message that lost attribution.
Dis-Advantages :
• It has high software expenditure.
• Undesirable interaction more probable.
Applications:
•The controller area network (CAN) is used for transmission airbags, antilock
braking,electric power steering etc.
•It is used in audio video systems.
•The controller area network (CAN) is used in lifts and escalators.
•It is used in sport cameras.
Conclusion:
• CAN is ideally suited in applications requiring a large number of short messages
with high reliability in rugged operating environments. Because CAN is message
based and not address based, it is especially well suited when data is needed by
more than one location and system wide data consistency is mandatory.
Reference:
• https://youtu.be/kS0d4GfCuVk
• https://youtu.be/FqLDpHsxvf8
Thank you