Difference between revisions of "F24: Tilt Maze"
From Embedded Systems Learning Academy
Proj user4 (talk | contribs) (Created page with "F24: Tilt Maze Contents 1 Grading Criteria 2 Project Title 3 Abstract 4 Objectives & Introduction 4.1 Team Members & Responsibilities 5 Schedule 6 Parts List & Cost 7 Design &...") |
Proj user4 (talk | contribs) (→Schedule) |
||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | === Grading Criteria === | |
| − | + | <font color="green"> | |
| − | + | * 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> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | == Project Title == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | Project Title | ||
Tilt Maze | Tilt Maze | ||
| − | Abstract | + | == Abstract == |
Tilt Maze is a motion-controlled puzzle game that challenges players to navigate a luminous ball through procedurally generated mazes using device tilting mechanics. Players must reach the exit within time constraints while maneuvering around obstacles and collecting power-ups that provide temporary advantages. The game combines physical device control with strategic gameplay elements, offering high replayability through its randomized level design and emphasizing skills in balance, spatial reasoning, and quick decision-making. | Tilt Maze is a motion-controlled puzzle game that challenges players to navigate a luminous ball through procedurally generated mazes using device tilting mechanics. Players must reach the exit within time constraints while maneuvering around obstacles and collecting power-ups that provide temporary advantages. The game combines physical device control with strategic gameplay elements, offering high replayability through its randomized level design and emphasizing skills in balance, spatial reasoning, and quick decision-making. | ||
| − | Objectives & Introduction | + | == 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. | + | 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 | + | === Team Members & Responsibilities === |
| − | Shreya Belide | + | * Shreya Belide |
| − | Jyoshna Mallineni | + | ** |
| − | Pavan Charith | + | * Jyoshna Mallineni |
| − | + | ** | |
| + | * Pavan Charith | ||
| + | ** | ||
| − | + | == Schedule == | |
| − | + | {| class="wikitable" | |
| + | |- | ||
| + | ! scope="col"| Week# | ||
| + | ! scope="col"| Start Date | ||
| + | ! scope="col"| End Date | ||
| + | ! scope="col"| Task | ||
| + | ! scope="col"| Status | ||
| + | |- | ||
| + | ! scope="row"| 1 | ||
| + | | | ||
| + | * 10/20/2024 | ||
| + | * 10/27/2024 | ||
| + | | | ||
| + | * 10/20/2024 | ||
| + | * 10/27/2024 | ||
| + | | | ||
| + | * Read previous projects, gather information and discuss among the group members. | ||
| + | * Create GitLab repository for project -https://gitlab.com/first892736/tilt-maze-group-2 | ||
| + | | | ||
| + | * <span style="color:green">Completed</span> | ||
| + | * <span style="color:green">Completed</span> | ||
| + | |- | ||
| + | ! scope="row"| 2 | ||
| + | | | ||
| + | *10/27/2024 | ||
| + | | | ||
| + | *11/02/2024 | ||
| + | | | ||
| + | *Order necessary parts - LED Matrix , Speaker , Accelerometer | ||
| + | | | ||
| + | * <span style="color:orange">In progress</span> | ||
| + | |- | ||
| + | ! scope="row"| 3 | ||
| + | | | ||
| + | *11/02/2024 | ||
| + | | | ||
| + | *11/08/2024 | ||
| + | | | ||
| + | *Read and familiarize with LED Matrix Datasheet | ||
| + | | | ||
| + | * <span style="color:orange">In progress</span> | ||
| + | |- | ||
| + | ! scope="row"| 4 | ||
| + | | | ||
| + | * 11/02/2024 | ||
| + | | | ||
| + | * 11/08/2024 | ||
| + | | | ||
| + | * Develop graphics driver for LED matrix and implement initial game objects | ||
| + | | | ||
| + | * <span style="color:red">Not started</span> | ||
| + | |- | ||
| + | ! scope="row"| 5 | ||
| + | | | ||
| + | *11/09/2024 | ||
| + | *11/09/2024 | ||
| + | *11/09/2024 | ||
| + | *11/09/2024 | ||
| + | | | ||
| + | *11/10/2024 | ||
| + | *11/15/2024 | ||
| + | *11/15/2024 | ||
| + | *11/15/2024 | ||
| + | | | ||
| + | * Finalize wiki schedule | ||
| + | * Order circuit boards components and complete the design for printing | ||
| + | * circuit board and component assembly | ||
| + | * Circuit board testing | ||
| + | * Additional accessories if required and finalization of hardware | ||
| + | | | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | |- | ||
| + | ! scope="row"| 6 | ||
| + | | | ||
| + | *11/16/2024 | ||
| + | | | ||
| + | *11/22/2024 | ||
| + | | | ||
| + | * Integration of circuit boards and microcontroller | ||
| + | * Game logic development | ||
| + | * Testing and debugging the game logic | ||
| + | | | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | |- | ||
| + | ! scope="row"| 7 | ||
| + | | | ||
| + | * 11/23/2024 | ||
| + | | | ||
| + | * 11/29/2024 | ||
| + | | | ||
| + | * Integrate game logic code with LED matrix | ||
| + | * Integrate game sounds with game logic | ||
| + | | | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | |- | ||
| + | ! scope="row"| 8 | ||
| + | | | ||
| + | * 11/30/2024 | ||
| + | | | ||
| + | * 12/06/2024 | ||
| + | | | ||
| + | * Integrate subsystem | ||
| + | * Finalizing the video game | ||
| + | * Update the wiki page. | ||
| + | | | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | |- | ||
| + | ! scope="row"| 9 | ||
| + | | | ||
| + | * 12/07/2024 | ||
| + | | | ||
| + | * 12/13/2024 | ||
| + | | | ||
| + | * Address bugs during testing of integrated system | ||
| + | *Test pause/play functionality | ||
| + | | | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | |- | ||
| + | ! scope="row"| 10 | ||
| + | | | ||
| + | *12/14/2024 | ||
| + | *12/14/2024 | ||
| + | *12/14/2024 | ||
| + | *12/14/2024 | ||
| + | | | ||
| + | *12/16/2024 | ||
| + | *12/16/2024 | ||
| + | *12/16/2024 | ||
| + | *12/16/2024 | ||
| + | | | ||
| + | *Final Demo | ||
| + | *Update Gitlab repo with final code. | ||
| + | *Update test video. | ||
| + | *Update the wiki page. | ||
| + | | | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | * <span style="color:red">Not started</span> | ||
| + | |- | ||
| + | |} | ||
| + | <HR> | ||
| + | <BR/> | ||
| − | + | == 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 | + | === 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. | |
| − | Testing & Technical Challenges | + | === Implementation === |
| − | 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. | + | 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: | Include sub-sections that list out a problem and solution, such as: | ||
| − | <Bug/issue name> | + | === <Bug/issue name> === |
Discuss the issue and resolution. | Discuss the issue and resolution. | ||
| − | Conclusion | + | == 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? | + | 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 | + | === Project Video === |
Upload a video of your project and post the link here. | Upload a video of your project and post the link here. | ||
| − | Project Source Code | + | === Project Source Code === |
| − | Sourceforge Source Code Link | + | * [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link] |
| − | References | + | |
| − | Acknowledgement | + | == References == |
| + | === Acknowledgement === | ||
Any acknowledgement that you may wish to provide can be included here. | Any acknowledgement that you may wish to provide can be included here. | ||
| − | References Used | + | === References Used === |
List any references used in project. | List any references used in project. | ||
| − | Appendix | + | === Appendix === |
You can list the references you used. | You can list the references you used. | ||
Latest revision as of 19:13, 5 November 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
Tilt Maze
Abstract
Tilt Maze is a motion-controlled puzzle game that challenges players to navigate a luminous ball through procedurally generated mazes using device tilting mechanics. Players must reach the exit within time constraints while maneuvering around obstacles and collecting power-ups that provide temporary advantages. The game combines physical device control with strategic gameplay elements, offering high replayability through its randomized level design and emphasizing skills in balance, spatial reasoning, and quick decision-making.
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
- Shreya Belide
- Jyoshna Mallineni
- Pavan Charith
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.
