CarTalk - UCI-EECS113-Spring17/Scurvy GitHub Wiki
##comments: narrow down the problem. what type of viechle you want to use. what class of information you want to gather. Also define the limitaitons of the bus access. mention if they are secuirity measures or verifications needed.
Description
The United States mandates that all vehicles manufactured from 2008 on be outfitted with an OBD-II connector and implement the CAN (Controller Area Network) Bus. The CAN Bus provides a networking protocol to tie in all components of a vehicle (eg. ECU, Transmission, A/C Unit, ABS) and access through a port found on the drivers side known as the OBD-II port.
Typically a tool like the one above is used to access information provided by the vehicle and set variables that are available. These tools are typically used for purely diagnostic purposes or to notify the vehicle of aftermarket modifications. Alternatively, a bluetooth device as seen below can be used to interface with smartphones and provide the same functionality as typical scan tools.
This project aims to implement the CAN protocol in order to expand upon functionality provided by typical diagnostic tools to incorporate typical Internet of Things functionality. The added functions will provide an interface to communicate and access data from the vehicle via web services such as Facebook Messenger, Google Assistant, Telegram etc. Some potential actions include querying the amount of gas remaining, logging fuel:oxygen ratio, average speed, current speed, control power windows, etc.
Features
- Pull vehicle data through the CAN Bus
- Generate statistics based on vehicle data
- Synchronize stored vehicle data to cloud services
- Access vehicle data through various web services
- Control vehicle functionality through various web services
- On device joystick and LCD to access diagnostics similar to a typical scan tool