|
|
| Line 1: |
Line 1: |
| − | === Grading Criteria ===
| + | From Preet: |
| − | <font color="green">
| + | This is not the correct page to write your report. |
| − | * 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.
| |
| − | </font>
| |
| − | | |
| − | = Anti-Crash Car =
| |
| − | | |
| − | == Abstract ==
| |
| − | The project involves a GPS controlled car that drives to a user determined destination and automatically stops or slows down when an obstacle is in its way in order to prevent itself from crashing. Any command that can potentially damage the car is disabled (e.g. moving forward when the obstacle is in front).
| |
| − | | |
| − | == 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 ===
| |
| − | * Geff Lozano
| |
| − | ** ...
| |
| − | * Koko Maung
| |
| − | ** ...
| |
| − | * Matthew Pham
| |
| − | ** ...
| |
| − | | |
| − | == 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.
| |
| − | | |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | ! scope="col"| Week#
| |
| − | ! scope="col"| Date
| |
| − | ! scope="col"| Task
| |
| − | ! scope="col"| Actual
| |
| − | |-
| |
| − | ! scope="row"| 1
| |
| − | | 10/8
| |
| − | | Task list
| |
| − | | Completed? Problems Encountered?
| |
| − | |}
| |
| − | | |
| − | == Parts List & Cost ==
| |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | ! scope="col"| Qty
| |
| − | ! scope="col"| Part
| |
| − | ! scope="col"| Price
| |
| − | |-
| |
| − | ! scope="row"| 1
| |
| − | | RC Rock Crawler
| |
| − | | $200.86
| |
| − | |-
| |
| − | ! scope="row"| 1
| |
| − | | [http://www.robotshop.com/en/devantech-ultrasonic-range-finder-srf08.html SRF08 Ultrasonic Range Finder]
| |
| − | | $54.30
| |
| − | |-
| |
| − | ! scope="row"| 4
| |
| − | | Sensor Housing MPSH-01
| |
| − | | $4.95
| |
| − | |-
| |
| − | ! scope="row"| 3
| |
| − | | [http://www.robotshop.com/en/sharp-gp2y0a21yk0f-ir-range-sensor.html?___SID=U GP2Y0A21YK0F IR Sensor - 10cm to 80cm]
| |
| − | | $9.95
| |
| − | |-
| |
| − | ! scope="row"| 3
| |
| − | | SIRC-01 Sensor Cable
| |
| − | | $1.95
| |
| − | |-
| |
| − | ! scope="row"| 1
| |
| − | | [http://www.robotshop.com/en/3dr-gps-module-ublox-lea-6-compass.html?___SID=U 3DR GPS Module w/ Compass]
| |
| − | | $89.99
| |
| − | |-
| |
| − | ! scope="row"| 1
| |
| − | | Battery
| |
| − | | $25.00
| |
| − | |-
| |
| − | ! scope="row"| 2
| |
| − | | Shipping
| |
| − | | $10.22
| |
| − | |}
| |
| − | | |
| − | == 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 ===
| |
| − | ==== Design Flow ====
| |
| − | [[File:Cmpe146_S14_ACCAR_SwDesignFlow.png]]
| |
| − | | |
| − | === 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 ===
| |
| − | 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.
| |
