1 Electrical and Computer Engineering Team Pishro-Nik and Ni Chris Comack - Simon Tang - Joseph Tochka - Madison Wang Car-to-Car Communication for Accident Avoidance March 5, 2009 Professor Pishro-Nik Advisor, Assistant Professor, ECE Professor Ni Advisor, Assistant Professor, CEE

2 Electrical and Computer Engineering Background  Automobile accidents are both dangerous and costly Over 42,000 fatalities in the United States every year. More than 2.9 Million injuries from 6.4 Million car accidents annually. Combined cost of 230+ Billion dollars per year. Responsible for 5% of preventable deaths each year (JAMA).  Goal: To provide a system to reduce these rates by warning drivers before a collision happens. How? Use GPS to track position and vehicle’s OBD-II port to monitor speed and acceleration of vehicles. Communicate this information among cars on the road via Dedicated Short Range Communication in the 5.9GHz spectrum. Source: Mokdad AH, Marks JS, et al. (March 2004). "Actual causes of death in the United States, 2000". JAMA 291 (10): 1238–45.Actual causes of death in the United States, 2000

3 Electrical and Computer Engineering Scenario

4 Electrical and Computer Engineering Scenario

5 Electrical and Computer Engineering Review of Situations

6 Electrical and Computer Engineering Proposed Solution Use of Car to Car Communication Cars 2 & 3 emit audio warning indicating Car 1 is decelerating rapidly. The cars operators now have more time to respond to this dangerous situation, decreasing the risk of collision.

7 Electrical and Computer Engineering Collision Detection Algorithm

8 Electrical and Computer Engineering Design & Requirements  System must be scalable  Track car’s location with GPS receiver  Use OBD-II (on-board diagnostic connection) to monitor speed, acceleration, and other information from car’s computer Standard on all cars made after 1996 – includes 150 million+ cars on the road in the U.S. today.  Communicate between vehicles using DSRC (Dedicated Short Range Communication) Transceiver

9 Electrical and Computer Engineering Block Level Diagram

10 Electrical and Computer Engineering GPS – Progress

11 Electrical and Computer Engineering GPS – Problem  No GPS Coordinate in Response Message

12 Electrical and Computer Engineering GPS – Progress  Process Response Correctly if there are GPS Coordinates

13 Electrical and Computer Engineering GPS Statistics  Measure Latitude/Longitude in One Location  Refreshes Coordinates

14 Electrical and Computer Engineering Inputs & Outputs  Inputs: SPST Power Switch, two momentary push-buttons.  Outputs: Green LED indicator, red LED warning light, Piezoelectric element for audible warning.

15 Electrical and Computer Engineering Data Collection  GPS coordinates updated at rate of 1 Hz.  Time-stamp acquired from GPS at same rate.  Heading, or compass direction, calculated from comparing GPS location to previous coordinates.  Speed information from Engine Control Unit polled at approximately 10 Hz.  Acceleration calculated from current and previous velocity values.  Control signal to monitor transceiver buffer; above five data points received from other units at max. frequency possible.

16 Electrical and Computer Engineering Data Transmission  Total processing time is minimized by performing heading and acceleration calculations before transmitting.  Minimal packet size allows frequent transmission of single packet containing all pertinent information.  Data transmitted after each update to prevent stale data. “Dead reckoning” also implemented to fill in the blanks between each GPS update.

17 Electrical and Computer Engineering Software Flowchart

18 Electrical and Computer Engineering Transceiver updates  Goals from last time Confirm Range (at least 150 m) Tested at 160 m Implement/confirm receiving functionality  To do Integrate with GPS, OBD-II Receive/send from multiple sources

19 Electrical and Computer Engineering Ethernet Packet Structure  Header 33 bytes SRC/DST MAC addresses SRC/DST IP addresses Length  Other data and payload Transceiver info Channel/power to send, etc. Payload, padding, checksum Payload will include position, speed, timestamp, acceleration, and heading ~13 bytes

20 Electrical and Computer Engineering PCB Progress  Currently only the layout for transceiver portion is done  Things to come GPS interface (serial port) OBD-II interface layout Inputs & Outputs Ship out design for manufacturing

21 Electrical and Computer Engineering Price of individual PCB Number Manufacturer Part NumberSupplierPackageDescription Quantit yPriceTotalTotal PCB Price 1LT1086DigikeyTO V fixed regulator LM340DigikeyTO-2205V fixed regulator ATMEGA128DigikeyTQFP-64Microcontroller115 4ENC28J60-HSparkfun10-dip Ethernet Controller header135 5Jtag connector0 6ELM327 Elm Electronics28-SOIC OBD to RS232 interpreter TCA1A226M8RDigikey uF cap Magellan A12MagellanGPS Denso TransceiverDensoTransceiver00 10ECJ-2VB1E104KDigikey uF cap FMMT597TADigikeysot-23PNP BJT MMBTA06-7Digikeysot-23NPN BJT ERJ-6GEYJ472VDigikey8054.7k resistor ERJ-6GEYJ473VDigikey80547k resistor ERJ-6GEYJ471VDigikey resistor ERJ-6GEYJ103VDigikey80510k resistor ERJ-6GEYJ223VDigikey80522k resistor

22 Electrical and Computer Engineering PCB Progress