F15: Car Report
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Project Title
Car Project: OBD-II
Abstract
For our project, we will be building an OBD II device that will interface with a vehicle through CAN Bus protocol. OBD II stands for On-Board Diagnostic II, which is used to track and monitor a vehicle's status and functions. A DB-9 connector to OBD-II cable was used to connect our device to the car in order to record real-time information of the vehicle like the temperature, engine check, and MPH. After gathering all required information, you can diagnose any faults in the vehicle that may appear.
Objectives & Introduction
//Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.
A device like OBD-II was introduced to the automobile industry in the late 1970's and it is still widely used today as a diagnostic tool for a vehicle from engine control to parts records. OBD-II is used by mechanics, car owners, agencies, and car manufactures to ensure vehicle is within the EPA emission standards. As California has become one of the leading states for the car industry, we decided building an OBD-II will lead to a better understanding of CAN Bus interface that is widely used in the car industry.
To design a OBD-II, we used a voltage regulator, DB-9 connector, a microcontroller on the SJSU one board, and a LCD screen to display the vehicle's information. We used CAN interface to transmit and receive information regarding the vehicle and UART interface to display the information on the LCD display. The objective of an OBD-II is to establish strong and reliable connection to a vehicle in order to gather valid information like MPH, RPM, engine check, temperature, car performance, and ay faults.
Team Members & Responsibilities
- Yasmine Jamjoum
- Hardware Design and Software Implementation of CAN and UART interface
- Khang Doan
- Hardware Design and Software Implementation of CAN and UART interface
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Week# | Date | Planned Task | Actual |
|---|---|---|---|
| 1 | 10/12-10/18 |
• Purchase all required parts • Download and install programs and data sheets for CAN Bus interface and OBD-II connection |
• Parts ordered on 10/16 • All required programs and data sheets were downloaded and installed |
| 2 | 10/19-10/25 |
• Gather all parts • Test all components separately • Plan and design hardware design diagrams |
• Testing components separately was successful • Waiting on a few components • Diagrams for hardware design were complete |
| 3 | 10/26-11/1 |
• Begin hardware design • Test the hardware design along the way |
• Started hardware design • Started project report |
| 4 | 11/2-11/8 |
• Complete the hardware design • Test the hardware as a whole |
• Realized we needed a transceiver • Waiting on the transceiver before we can continue with the hardware design completion |
| 5 | 11/9-11/15 |
• Complete the hardware design • Test the complete hardware interface • Research about the software interface for OBD-II: CAN Bus protocol • Research about the software interface for LCD Display: UART protocol |
• Received the transceiver • Completed the hardware design • Updated all hardware diagrams • Tested and Debugged the whole system |
| 6 | 11/16-11/22 |
• Begin the software interface for OBD-II: CAN Bus protocol • Begin the software interface for LCD display: UART protocol |
• Began research on CAN Bus • Obtained additional data sheets for CAN Bus and OBD-II connection |
| 7 | 11/23-11/29 |
• Begin the software interface for OBD-II: CAN Bus protocol • Begin the software interface for LCD display: UART protocol |
• Started software programming for CAN bus and UART interfaces |
| 8 | 11/30-12/6 |
• Complete the software interfaces for CAN Bus and UART protocol • Begin Debugging |
• Completed the software interfaces for CAN Bus and UART protocol • Started Testing and Debugging
|
| 9 | 12/7-12/13 |
• Finish Debugging • Interface the hardware with software • Test system design |
• Completed the debugging phase • Started interfacing the hardware with the software • Tested the device on an actual vehicle • Continued the project report |
| 10 | 12/14-12/17 |
• Complete system testing • Complete the project report • Demo the project |
• Completed system testing • Created video for presentation • Completed the project report • Presented the project on Thursday, December 17, 2015 |
Parts List & Cost
//Give a simple list of the cost of your project broken down by components. Do not write long stories here.
Hardware
• OBD-II to DB-9 Cable [$9.95]
• Prototype board [$12.99]
• DB-9 Male Connector, Switch, LED, resistor, LM7805 voltage regulator [$10.99]
• LCD Display [$34.99]
• Vehicle: 2004 Acura TL [$8,100]
Software
• Windows Vista/7 (32 or 64-bit)
• Eclipse IDE
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
My Issue #1
Discuss the issue and resolution.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here. We would like the thank the following people for their contributions during this project: Preet Kang
References Used
List any references used in project.
Appendix
You can list the references you used.
