Difference between revisions of "F24: Bounce Tales"
Proj user8 (talk | contribs) (→Parts List & Cost) |
Proj user8 (talk | contribs) (→Parts List & Cost) |
||
| Line 214: | Line 214: | ||
64x64 RGB LED Matrix | 64x64 RGB LED Matrix | ||
| | | | ||
| − | + | Amazon | |
| | | | ||
1 | 1 | ||
| Line 234: | Line 234: | ||
Two-axis Joystick | Two-axis Joystick | ||
| | | | ||
| − | + | Amazon | |
| | | | ||
1 | 1 | ||
| Line 244: | Line 244: | ||
MP3 Decoder | MP3 Decoder | ||
| | | | ||
| − | + | Amazon | |
| | | | ||
1 | 1 | ||
| Line 254: | Line 254: | ||
Power Supply | Power Supply | ||
| | | | ||
| − | + | Amazon | |
| | | | ||
1 | 1 | ||
Revision as of 19:16, 19 December 2024
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
Bounce Tales
Abstract
Bounce Tales is a classic mobile game reminiscent of the Nokia era, featuring a bouncing character navigating through levels filled with obstacles. This project aims to recreate the game experience using the SJ-2 board and an LED matrix display. Players will control the character’s movement using buttons or a joystick, while the game will include levels, obstacles, and scoring. The implementation will focus on real-time movement, collision detection, and level progression.
Objectives & Introduction
The idea is to build the bounce tales game on a 64x64 RGB LED Screen. The game is played using a joystick. The ball keeps on collecting the point avoiding the obstacles and its direction can be controlled using left and right control of the joystick, which can also be used in forward direction jump to avoid the obstacles. MP3 decoder is used for different sound effects in the background of game.
Team Members & Responsibilities
- Vaidehi
- LED driver
- Game Logic
- PCB design verification
- WiKi page handling
- Shashank
- MP3 decoder driver
- Game Logic
- PCB Schematic and Board Design
- WiKi page handling
- Manvendra
- Joystick driver
- Game Logic
- PCB design verification
- WiKi page handling
Schedule
| Week# | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 |
|
|
|
|
| 2 |
|
|
|
|
| 3 |
|
|
|
|
| 4 |
|
|
|
|
| 5 |
|
|
|
|
| 6 |
|
|
|
|
| 7 |
|
|
|
|
| 8 |
|
|
|
|
| 9 |
|
|
|
|
| 10 |
|
|
|
|
Parts List & Cost
| Item# | Part Name | Part Supplier | Quantity | Cost |
|---|---|---|---|---|
| 1 |
64x64 RGB LED Matrix |
Amazon |
1 |
$ 87.4 |
| 2 |
Sjtwo board |
Amazon |
1 |
$ 50 |
| 3 |
Two-axis Joystick |
Amazon |
1 |
$ 4.25 |
| 4 |
MP3 Decoder |
Amazon |
1 |
$ 8.05 |
| 5 |
Power Supply |
Amazon |
1 |
$ 7.99 |
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.
