PRESENTED BY :
BHUPESH JOSHI
ANIL DABAS
NAVIN DALAL

---

[attachment=13378]
ABSTRACT
The extensive use of electronics in modern vehicles is well known. Electronics and software provide possibilities for substantial improvements in functional content, performance and other product properties. At the same time this field of engineering has been uncharted territory in the automotive industry. Today's vehicles contain hundreds of circuits, sensors, and many other electrical components. Communication is needed among the many circuits and functions of the vehicle. For example, when the driver presses the headlights switch on the dashboard, the headlights react. For this to occur, communication is needed between the dashboard switch and the front of the vehicle. In current vehicle systems this type of communication is handled via a dedicated wire through point-to-point connections. If all possible combinations of switches, sensors, motors, and other electrical devices in fully featured vehicles are accumulated, the resulting number of connections and dedicated wiring is enormous.
The Controller Area Network (CAN) is a serial bus communications protocol developed by Bosch in the early 1980s. It defines a standard for efficient and reliable communication between sensor, actuator, controller, and other nodes in real-time applications.
We have implemented CAN protocol on ARM platform as our project and implemented only some features of CAN because it is not possible to implement all of them .Our system will implement can bus with the help of arm processor ,cans (2.0A) and sensors where data sensed by sensors will be displayed through output devices.
INTRODUCTION
1.1 Controller -Area Network (CAN)
CAN (Controller Area Network) is a serial bus system, which was originally developed for automotive applications in the early 1980's. The CAN protocol is internationally standardized in ISO 11898-1 and comprises the data page link layer of the 7-layer ISO/OSI reference model. CAN, which is by now available from more than 50 semiconductor manufacturers in hardware, provides two communication services: the sending of a message (data frame transmission) and the requesting of a message (remote transmission request, RTR).
The CAN protocol specifies also an automatic retransmission of faulty messages after transmitting an error frame. Error frames may be send by transmitting or receiving nodes. The CAN protocol specifies sophisticated fault detection mechanism not a fault confinement.
Bosch originally developed the Controller Area Network (CAN) in 1985 for in-vehicle networks. In the past, automotive manufacturers connected electronic devices in vehicles using point-to-point wiring systems. Manufacturers began using more and more electronics in vehicles, which resulted in bulky wire harnesses that were very heavy and expensive. They then replaced dedicated wiring with in-vehicle networks, which reduce wiring cost, complexity, and weight. CAN, a high-integrity serial bus system for networking intelligent devices, emerged as the standard in-vehicle network. The automotive industry quickly adopted CAN and, in 1993, it became the international standard known as ISO 11898. Since 1994, several higher-level protocols have been standardized on CAN, such as CAN open and Device Net. Other markets have widely adopted these additional protocols, which are now standards for industrial communications. We focuses on CAN as an in-vehicle network have widely adopted these additional protocols, which are now standards for industrial communications. We focus on CAN as an in-vehicle network.[10].
1.2Technology:
CAN is a multi-master broadcast serial bus standard for connecting electronic control units (ECUs).
Each node is able to send and receive messages, but not simultaneously: a message (consisting primarily of an ID — usually chosen to identify the message-type/sender — and up to eight message bytes) is transmitted serially onto the bus, one bit after another — this signal-pattern codes the message (in NRZ) and is sensed by all nodes.
The devices that are connected by a CAN network are typically sensors, actuators and control devices. A CAN message never reaches these devices directly, but instead a host-processor and a CAN Controller is needed between these devices and the bus.
If the bus is free, any node may begin to transmit. If two or more nodes begin sending messages at the same time, the message with the more dominant ID (which has more dominant bits i.e. bit 0) will overwrite other nodes' less dominant IDs, so that eventually (after this arbitration on the ID) only the dominant message remains and is received by all nodes.[3]
1.3 IMPLIMENTATION
The Implementation part of the project is to configure and enable the CAN interface present in the ARM boards for supporting CAN protocol and connecting them to form a network which is perfectly suited for embedded automotive system. We have connected different sensors at different parts of vehicle, these sensors will continuously sent data to arm controller through its I/O ports .This data is given to CAN1 and CAN1 gives this data to CAN2 through can bus which then sends them to display.
We have implemented CAN protocol on ARM platform as our project and implemented only some features of CAN because it is not possible to implement all of them .Our system will implement can bus with the help of arm processor ,cans (2.0A)and sensors where data sensed by sensors will be displayed through output devices.