F19: Smacman
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.
SMACMAN
Abstract
Our team is planning on creating a unique 2 player game involving a central screen and two auxiliary controllers. The two opponents will face one another and will have a paddle on their side much like the game pong. A ball will travel between players which they have to deflect away. Additionally, each player will have a “monster” that will continuously move towards the ball. If a monster collides with the ball, that opponent of the owner of the monster will lose. Therefore, it is beneficial for a player to try to place the ball closer to their monster and further away from the opponent’s monster. Additionally, if the ball contacts the side of the screen behind the player’s paddle, they will also lose. As the game progresses, the speed of the ball will increase and eventually additional balls will be added. There are also possibilities “powerups” being implemented that invoke actions such as temporary invincibility from the opponent’s monster. The controllers will be wireless and communicate with the master board which runs the game and drives the 64x64 LED matrix.
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
- Nick Schiffer
- XBEE, Controller Functionality, Communication Architecture, MP3, Game Logic Development, Enclosures
- Mohit Ingale
- LED Driver, Game Logic Development, Enclosures, PCB Designing
- Ayesha Siddiqua
- Graphic Driver, Game Logic Development
- Shreya Patankar
- Graphic Driver, Game Logic Development
Schedule
View our current progress here: Github Project
| Week# | Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|
| 1 | 10/1/2019 |
|
|
|
| 2 | 10/15/2019 |
|
|
|
| 3 | 10/22/2019 |
|
|
|
| 4 | 10/29/2019 |
|
|
|
| 5 | 11/5/2019 |
|
|
|
| 6 | 11/12/2019 |
|
|
|
| 7 | 11/19/2019 |
|
|
|
| 8 | 11/26/2019 |
|
|
|
| 9 | 12/3/2019 |
|
|
|
| 10 | 12/10/2019 |
|
|
|
| 11 | 12/17/2019 |
|
|
|
Parts List & Cost
| Item# | Part Desciption | Vendor | Qty | Cost |
|---|---|---|---|---|
| 1 | SJTwo Boards | From Preet | 3 | $150.00 |
| 2 | 64x64 RGB LED Matrix | Adafruit | 1 | $92.00 |
| 3 | Wiring Components and Cable | Amazon | 1 | $20 |
| 4 | x1-x2 3D printer filament spool(s) | For 3D printed enclosures [1] | 1 | $20 |
| 5 | 3x XBEE Modules | From Preet and Adafruit | 4 | $27 |
| 6 | Batteries | Adafruit | TBD | TBA |
Design & Implementation
View our current progress here (this will be added to the wiki when completed): Github Wiki
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
1)There are two players in the game. These are 2 xbee nodes and they are connected to one main node and thus the topology for broadcast is set. 2)MP3 player for game sound effects
Hardware Interface
1) Xbee interfaces using UART Bus.
2)MP3 player interface using SPI Bus.
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.
