Difference between revisions of "F12: OBD-II Android Monitor"
(→Schedule) |
(→Schedule) |
||
| Line 15: | Line 15: | ||
== Schedule == | == Schedule == | ||
<table class="wikitable"> | <table class="wikitable"> | ||
| − | <th>Week Number</th> <th>Date</th> <th>Tasks</th> | + | <th>Week Number</th> <th>Date</th> <th>Tasks</th> <th>Tasks Completed</th> |
<tr> | <tr> | ||
| Line 25: | Line 25: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * | + | * Gather and order parts |
| − | * | + | * Install Android SDK and tools |
| − | * | + | * Review component data sheets |
| + | </td> | ||
| + | <td> | ||
| + | * Parts ordered on 10/25 | ||
| + | * Installed SDK on Eclipse | ||
| + | * Obtained pdf of OBD-II datasheet | ||
</td> | </td> | ||
</tr> | </tr> | ||
| Line 39: | Line 44: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * | + | * Gather and test components |
| − | * | + | * Establish Android app requirements |
| − | * | + | * Begin Android app design |
| + | * Write Project Abstract | ||
| + | </td> | ||
| + | <td> | ||
| + | * ____ | ||
| + | * ____ | ||
| + | * ____ | ||
</td> | </td> | ||
</tr> | </tr> | ||
| Line 53: | Line 64: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * | + | * Finalize Android app design |
| − | * | + | * Begin Android app implementation |
| − | * | + | </td> |
| + | <td> | ||
| + | * ____ | ||
| + | * ____ | ||
| + | * ____ | ||
</td> | </td> | ||
</tr> | </tr> | ||
| Line 67: | Line 82: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * | + | * Establish communication link between OBD-II and Android phone |
| − | * | + | * Develop UI design |
| − | * | + | </td> |
| + | <td> | ||
| + | * ____ | ||
| + | * ____ | ||
| + | * ____ | ||
</td> | </td> | ||
</tr> | </tr> | ||
| Line 81: | Line 100: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * | + | * Continue UI design |
| − | * | + | * Prepare system testing |
| − | * | + | </td> |
| + | <td> | ||
| + | * ____ | ||
| + | * ____ | ||
| + | * ____ | ||
</td> | </td> | ||
</tr> | </tr> | ||
| Line 95: | Line 118: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * | + | * Begin system testing |
| − | * | + | * Begin finalizing project report |
| − | * | + | </td> |
| + | <td> | ||
| + | * ____ | ||
| + | * ____ | ||
| + | * ____ | ||
</td> | </td> | ||
</tr> | </tr> | ||
| Line 109: | Line 136: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * | + | * Finish project report |
| − | * | + | * Finish system testing |
| − | * | + | * Demo project |
| + | </td> | ||
| + | <td> | ||
| + | * ____ | ||
| + | * ____ | ||
| + | * ____ | ||
</td> | </td> | ||
</tr> | </tr> | ||
Revision as of 19:46, 29 October 2012
Contents
OBD-II Android Monitor
Abstract
This section should be a couple lines to describe what your project does.
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
- Ryan James Cristobal
- Jonathan Luong
Roles & Responsibilities
Schedule
| Week Number | Date | Tasks | Tasks Completed |
|---|---|---|---|
| 1 |
10/20 - 10/26 |
|
|
| 2 |
10/27 - 11/2 |
|
|
| 3 |
11/3 - 11/9 |
|
|
| 4 |
11/10 - 11/16 |
|
|
| 5 |
11/17 - 11/23 |
|
|
| 6 |
11/24 - 11/30 |
|
|
| 7 |
12/1 - 12/7 |
|
|
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:
Wifi Connection Issues
Many wifi connection issues were encountered. To solve this problem, a dedicated task was created to re-connect to wifi if the connection was ever lost.
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
Send me your zipped source code and I will upload this to SourceForge and link it for you.
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.
