Difference between revisions of "F22: Space Warriors"
(→Project Source Code) |
(→Schedule) |
||
| Line 49: | Line 49: | ||
* Discuss and source parts for project. Start ordering parts. | * Discuss and source parts for project. Start ordering parts. | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
|- | |- | ||
! scope="row"| 2 | ! scope="row"| 2 | ||
| Line 62: | Line 62: | ||
* Familiarize with relevant hardware datasheets | * Familiarize with relevant hardware datasheets | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
|- | |- | ||
! scope="row"| 3 | ! scope="row"| 3 | ||
| Line 72: | Line 72: | ||
* Order any missing parts we may need | * Order any missing parts we may need | ||
* Develop drivers for hardware required in the project | * Develop drivers for hardware required in the project | ||
| − | * Develop driver for LED display | + | * Develop driver for LED display. |
| | | | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
| Line 84: | Line 84: | ||
* 11/12/2022 | * 11/12/2022 | ||
| | | | ||
| − | * Continue developing drivers | + | * Continue developing drivers. |
| + | * Search and finalize game sounds. | ||
* Start testing drivers on hardware | * Start testing drivers on hardware | ||
* Discuss and plan game logic | * Discuss and plan game logic | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
|- | |- | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
| Line 96: | Line 97: | ||
*11/19/2022 | *11/19/2022 | ||
| | | | ||
| − | * Finalize wiki schedule | + | * Finalize wiki schedule. |
* Order circuit boards components and complete the design for printing | * Order circuit boards components and complete the design for printing | ||
| − | * | + | * Complete drivers for MP3 decoder. |
| − | * Circuit board testing | + | * Circuit board testing. |
* Additional accessories if required and finalization of hardware | * Additional accessories if required and finalization of hardware | ||
* Start developing game logic | * Start developing game logic | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| Line 115: | Line 112: | ||
*11/23/2022 | *11/23/2022 | ||
| | | | ||
| − | *Integration of circuit boards and microcontroller | + | * Integration of circuit boards, different components, and microcontroller |
* Continue game logic development | * Continue game logic development | ||
* Testing and debugging the game logic | * Testing and debugging the game logic | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
| − | + | ||
| − | |||
|- | |- | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
| Line 133: | Line 129: | ||
* Integrate game sounds with game logic | * Integrate game sounds with game logic | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:green">Completed</span> |
| − | * <span style="color: | + | * <span style="color:orange"> in Progress </span> |
|- | |- | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| Line 143: | Line 139: | ||
| | | | ||
| − | * Integrate subsystem | + | * Integrate subsystem. |
| − | * Finalizing the video game | + | * Finalizing the video game. |
* Update the wiki page. | * Update the wiki page. | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:orange"> in Progress </span> |
| − | + | ||
| − | |||
|- | |- | ||
! scope="row"| 9 | ! scope="row"| 9 | ||
| Line 160: | Line 155: | ||
* Test pause/play functionality | * Test pause/play functionality | ||
| | | | ||
| − | * <span style="color: | + | * <span style="color:orange"> in Progress</span> |
| − | |||
| − | |||
|- | |- | ||
! scope="row"| 10 | ! scope="row"| 10 | ||
Revision as of 00:31, 7 December 2022
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
Lumberjack
Abstract
Lumberjack is a reaction-based game with the objective of chopping down a tree while avoiding the incoming branches. The project will be a re-creation of a mobile game called Timber Guy, using an LED matrix array and capacitive touch buttons to interface with the game. Players will continuously cut down a tree by tapping on the capacitive touch sensors to make the character chop the tree. Meanwhile, they must also dodge the descending branches of the tree. By touching the respective capacitive sensors on the left or right sides of the LED display, players will move the character to avoid getting hit. Moreover, the players must continuously cut down the tree, which restores the countdown gauge, faster than it is depleted. If the player collides with a branch or the countdown is depleted, the game will be considered over.
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
- Dhanush Babu
- Nick Tran
- Rajveer Singh Kaushal
Schedule
| Week# | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 |
|
|
|
|
| 2 |
|
|
|
|
| 3 |
|
|
|
|
| 4 |
|
|
|
|
| 5 |
|
|
|
|
| 6 |
|
|
|
|
| 7 |
|
|
|
|
| 8 |
|
|
|
|
| 9 |
|
|
|
|
| 10 |
|
|
|
|
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:
<Bug/issue name>
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.
