Difference between revisions of "F15: Laser Security System"
Proj 146u4 (talk | contribs) (→Project Source Code) |
Proj 146u4 (talk | contribs) (→Acknowledgement) |
||
| Line 203: | Line 203: | ||
| − | == Acknowledgement == | + | == '''Acknowledgement''' == |
| − | |||
== References Used == | == References Used == | ||
Revision as of 18:23, 16 December 2015
Contents
- 1 Project Title
- 2 Abstract
- 3 Objectives & Introduction
- 4 Team Members & Responsibilities
- 5 Schedule
- 6 Parts List & Cost
- 7 Design & Implementation
- 8 Hardware Design
- 9 Hardware Interface
- 10 Software Design
- 11 Implementation
- 12 Testing & Technical Challenges
- 13 My Issue #1
- 14 Conclusion
- 15 Project Video
- 16 Project Source Code
- 17 References
- 18 Acknowledgement
- 19 References Used
- 20 Appendix
Project Title
Abstract
Objectives & Introduction
Team Members & Responsibilities
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 |
