Project
| # | Title | Team Members | TA | Documents | Sponsor |
|---|---|---|---|---|---|
| 37 | Vehicle to Vehicle Communication Device |
Alejandro Gonzalez Harsh Harpalani Tiger Chung |
Christopher Horn | design_document1.pdf final_paper1.pdf photo1.jpg presentation1.pdf proposal1.pdf |
|
| # VEHICLE TO VEHICLE COMMUNICATION DEVICE # Problem Currently, the way smart vehicles work is that they have sensors all over the car to detect nearby objects and information about them. However, these sensors tend to be limited in accuracy past very short distances. And since cars travel at such fast speeds and have to continuously identify changing information in their surroundings, sensors often do not have enough range to identify the necessary information for complicated decisions (crash detection at intersections or highways, avoidance of erratic drivers, traffic maneuvering, etc.). With the rise in popularity of autonomous driving systems, reliably collecting data over long distances is becoming more and more crucial. # SOLUTION OVERVIEW To get over this issue, we propose making a device that would attach to every vehicle on the road. This device would collect information about the vehicle (dimensions, speed, acceleration, position, heading, etc.) and transmit this information to other cars. This device would also collect information about surrounding similarly-equipped vehicles. This way, the guesswork is taken out of smart vehicles trying to figure out what other vehicles are doing around them. Instead, vehicles can directly receive this information from other vehicles on the road and spend more resources monitoring/tracking non-vehicular objects. This data could then be fed into an intelligent system (whether an autonomous car or just a smart system in a modern car) and could be used to make complicated decisions such as those described earlier. # SOLUTION COMPONENTS [Subsystem #1] Transmitter – This subsystem will be responsible for quickly and reliably broadcasting data at a 5.875GHz frequency to a receiver that will be up to 300 meters away. A 5.9 GHz frequency has been allocated by the FCC for use by Intelligent Transportations Systems for vehicle safety but due to resource constraints, we decided to go with a common transceiver that reaches 5.875 GHz, as linked below. https://www.mouser.com/ProductDetail/Maxim-Integrated/MAX2828ETN%2b?qs=Bakm8ERcljqg9szI93ou3Q%3D%3D [Subsystem #2] Receiver – This subsystem will receive and process the data to show up on a display. [Subsystem #3] Sensors (Accelerometer, GPS, Speedometer, Magnetometer) – This subsystem will collect information about the vehicle that the device is attached to. [Subsystem #4] Power supply system (Voltage regulator to drop voltage from car battery voltage to our device) - This subsystem will power all of the components of our device. [Subsystem #5] Data Collected Processing Unit (Raspberry Pi) – This subsystem will act as an interface between the sensors and the transmitter. The subsystem should compile data packets for transmission. The component is subject to change as we need minimal processing power for this subsystem. # CRITERION FOR SUCCESS We strive to demonstrate fast, reliable communication between the transmitter and the receiver. We want to test robustness in communication for distances up to 300 meters between moving vehicles. We also want to provide accurate sensor data so drivers and intelligent systems can make more informed decisions. A successful demo will include a demonstration of the receiver displaying accurate data from transceiver in a classroom setting and a video demonstration of the receiver displaying accurate data of a vehicle from a long distance (up to 300 meters, depending on the strength of signal and interference). A stretch goal of ours is to incorporate data from the OBD-II port of a car instead of solely from the sensors. |
|||||