Welcome to the OBD Automotive Code Reader Project Page
1. Project Overview
Standardized On-Board Diagnostics (OBD) can be traced back to legislation from 1966, where the State of California began to control emissions, specifically targeting the Los Angeles Basin. Soon after, the Federal Government picked up on this, extending emissions control nationwide in 1968, later passing the Clean Air Act (1970) and the creation on the Environmental Protection Agency (EPA). This created a need for a standardized plug and protocols for emissions controls and testing. In 1988, the Society of Automotive Engineers (SAE) did just that, releasing a standardized plug and testing protocol, which the EPA then adapted and implemented in 1996 .
The ever increasing use of electronically controlled devices in automobiles has allowed for the acquisition of data to monitor individual components of the vehicle. This information can be used to identify problems with mechanical or electronic systems by an indicator (typically a “Check Engine” lamp) should they become faulty. As of 1996, any new automobile sold in the United States must be capable of providing this type of data via the second generation OBD standard. Before this was made standard, many companies either did not provide any means of outside access to the computer data, or the data had to be read through proprietary standards created specifically by that auto-maker using expensive equipment.
The goal of this project is to take advantage of the OBD standard by making a battery powered device that is able to read error codes (from any OBD compliant vehicle) that have been generated by a vehicle, display real-time data from sensors, as well as include data logging capabilities. What will set this project apart from devices currently on the market will be its ability to log GPS data while reading vehicle data simultaneously. This could be used to track how a vehicle is being driven at any given location. The application for this could be useful in tracking a teen’s driving habits, or for insurance purposes. Another use for this technology would be to log data to be interpreted after making changes to the vehicle’s characteristics to see performance gains.
- Battery powered
- OBD-II compliant (all protocols)
- Consumer focused
- Display real-time OBD data
- GPS & OBD data logging
- Removable memory
- Portable (handheld)
- (profile) Jordan Levy email@example.com
- (profile) Josiah Jessen firstname.lastname@example.org
- (profile) Steven Do email@example.com
Mentor: John Batch
Sponsor: Garmin AT
5.1 Power Supply
5.3 User Interface (Buttons and Switches)
5.7 CPU_0 Code
5.9 CPU_1 Code
5.10 OBD Decoder
5.11 GPS Transceiver
5.12 Real Time Clock
5.13 Removable Memory
 The OBD II Homepage, "OBD-II Background," B&B Electronics. [Online]. Available: http://www.obdii.com/background.html/. [Accessed: Nov. 1, 2009].