S17: MyAutoHealth
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
Real-time vehicle diagnostics.
Abstract
Wear and tear or aging of parts of an automobile may cause a malfunction which may lead to accidents, loss of life and property. Being able to pinpoint the issue in the automobile could be harder than actually fixing one. Most modern vehicles, just like a computer, have a central processing unit called the Engine Control Unit (ECU) which oversees all operations. This project aims to use an external OBD 2 module to communicate with the ECU using UART and display the status of all critical vehicle parameters to the user. This will enable the user to monitor the engine’s internal functioning. The module will suggest measures to improve driving efficiency and avoid damage. The module will also be used to analyze the driving habits of people, especially school bus drivers or those taking a driving test.
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.
Team Members & Responsibilities
- Manan Mehta
1. Interface Accelerometer and use appropriate algorithms to measure vibrations
- Pushpender Singh & Sameer Saran
1. Soldering and connecting OBD II Uart components - 4/17.
2. Interfacing the serial port - 2/21.
3. Acquiring OBD reading from the vehicle - 2/21.
4. Translating received data to Graphs/meters.
- Sanman Pradhan
1. Design a PCB to accommodate the various hardware components.
2. Schematic is being designed using EaglePCB.
3. The power supply circuit, designed to be the main power source, peripherals such as the LCD will be housed on the PCB.
4. Assist with interfacing and programming of the temperature sensor.
- Shashank Iyer
A temperature sensor will be placed under the hood of the car near the engine. This will be used to access the amount of heat emanating from the engine. It will complement the coolant temperature sensor's reading.
The development of the system and its integration with SJ1 will as follows: 1. Acquiring a temperature sensor that can operate in the full range of temperature swing that an average engine fluctuates between.
2. Using a sturdy standoff to ensure it is able to read values accurately from the air around the engine.
3. Supplying power to the sensor from the SJ1 board.
4. Processing sensor outputs through the onboard ADC to make them processor readable. 5. Creating a task that polls the value from the sensor at intervals of 10 ms and pushes it to a queue.
6. Creating a second task that waits for the queue data and displays it.
7. If the temperature exceeds safe limits, a software interrupt is triggered and decides whether to alert the driver or cut the ignition.
Schedule
| Week# | Date | Task | Action |
|---|---|---|---|
| 1 | 03/21 | Research Project design and Finalize concept | Completed |
| 2 | 03/28 | Purchasing BOM and Assign Tasks | Completed |
| 3 | 04/04 | Developing C code to read Accelerometer readings | Completed |
| 4 | 04/11 | Interfacing OBD II sensor and Temperature sensor | In-progress |
| 5 | 04/18 | Developing C code to retrieve data from Vehicle and PCB design | |
| 6 | 04/25 | Integrating OBD and Sensor code into tasks and PCB design | |
| 7 | 05/02 | Testing and debugging | |
| 8 | 05/09 | PCB Assembly and Testing | |
| 9 | 05/16 | Ready for Demo |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
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.
References Used
List any references used in project.
Appendix
You can list the references you used.
