F16: OBD2 Reader
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
Abstract
The OBD2 reader is an on board diagnostic device that will translate the diagnostic code from the vehicle's ecu to an understandable and readable data for the user. This device will use several protocols learned in 146 lab as well as other techniques featured in the Socialledge Wiki in order to implement the design. The cars onboard ECU takes all the sensory data from several sensors and units and translates this into hexadecimal number and outputs it through its OBD2 port. Our OBD2 ready device will link with the car’s ECU and takes this information and compares it to the database codes that will indicate the problem with the vehicle. Once the codes from the ECU to our board match they will display the result on the additional LCD device. The LCD device will be implemented on top of our board using the I2C protocol. This device will display the error with the vehicle with diagnostic suggestions and methods of approach.
Objectives & Introduction
This project aims to design an OBD2 reader using the SJOne LPC 1758 board. The reader will display a vehicle's Engine Control Unit information via an LCD screen.
Objectives:
- Interface the SJOne board with the OBD2 reader
- Store and read external memory module through SJOne board
- Interfacing SJOne to external LCD or OLED display
Sensors and Peripherals Used:
- LCD or OLED display
Team Members & Responsibilities
- Rob Nikfar
- Samira Oliva
- Samuel Palomino
- Eric Sanchez
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# | Start Date | End Date | Task | Status | Notes |
|---|---|---|---|---|---|
| 1 | 10/30/16 | 11/05/16 |
|
Completed |
|
| 2 | 11/06/16 | 11/12/16 |
|
In Progress | TBA |
| 3 | 11/13/16 | 11/19/16 |
|
Incomplete | TBA |
| 4 | 11/20/16 | 11/26/16 |
|
Incomplete | TBA |
| 5 | 11/27/16 | 12/03/16 |
|
Incomplete | TBA |
| 6 | 12/04/16 | 12/10/16 |
|
Incomplete | TBA |
| 7 | 12/11/16 | 12/17/16 |
|
Incomplete | TBA |
| 8 | 12/18/16 | 12/20/16 |
|
Incomplete | TBA |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Item | Qty. | Price (Total) | Description |
|---|---|---|---|
| SJOne Board | 1 | $80.00 | SJOne Board |
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.
- communication Protcols
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.
References Used
List any references used in project.
Appendix
You can list the references you used.
