Difference between revisions of "F21: Sons of Ultron"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Objectives & Introduction)
Line 6: Line 6:
 
Clear all the bubbles and get yourself out of trouble !! “Bubble Trouble” is a fun game where each time you hit a big bubble, it will split up into two smaller ones. Avoid the bubbles as they bounce through the level. Race against time, collect all the traps and power-ups you can use to be the best at this game. Do you have what it takes to be the ultimate bubble shooter?. This is all displayed in the LED matrix acting as the screen. Use your spike gun to pop all the bubbles from the largest to the smallest bits. Can you clear each level?.
 
Clear all the bubbles and get yourself out of trouble !! “Bubble Trouble” is a fun game where each time you hit a big bubble, it will split up into two smaller ones. Avoid the bubbles as they bounce through the level. Race against time, collect all the traps and power-ups you can use to be the best at this game. Do you have what it takes to be the ultimate bubble shooter?. This is all displayed in the LED matrix acting as the screen. Use your spike gun to pop all the bubbles from the largest to the smallest bits. Can you clear each level?.
  
== Objectives & Introduction ==
+
== Objectives ==
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.
+
The main objective of this project was to create the “BUBBLE TROUBLE” video game displayed on a 64X64 RGB LED matrix, with one SJ2 board as a graphics processor/matrix controller, and another SJ2 board as a controller. Other objectives are the following:
 +
* Design custom PCBs for both the gamepad and matrix controller SJ2 boards.
 +
* Use the FreeRTOS Real-Time Operating System on both SJ2 boards.
 +
* Establish UART communications through Xbee between the two SJ-Two Microcontrollers.
 +
* Create simple coding logic for displaying required characters and game objects.
 +
* Add background music to the game to enhance the gameplay experience.
 +
 
 +
== Introduction==
 +
* Matrix Controller Board: The matrix controller board is responsible for displaying the graphics of the game, controlling the game logic, playing MP3 tracks based on the current game/menu screen, receiving character movement and button press signals over the Xbee interface.
 +
 
 +
* GamePad Controller Board: The gamepad controller board is responsible for processing input joystick and button press signals, controlling the character controls logic, sending character movement and button press signals over an Xbee interface.
 +
 
 +
HOW TO PLAY BUBBLE TROUBLE:
 +
The main aim of the game is to burst all the balloons and advance to the next level.  
 +
* Using the joystick on the game controller, move the character left or right.
 +
* Shoot arrows using the button on the game controller to burst the balloons into smaller ones.
 +
* The character must avoid getting hit by the balloon.
 +
* If the character gets hit by the balloon it loses one life and the level restarts
 +
* Each level has a time limit to complete it. If all the balloons are not burst in that time limit the player loses one life.
 +
* With each level the number of balloons and the size of balloons increase.  
 +
 
 +
 
  
 
=== Technical Responsibilities ===
 
=== Technical Responsibilities ===

Revision as of 01:06, 30 November 2021

BUBBLE TROUBLE.jpeg

Bubble Trouble

Abstract

Clear all the bubbles and get yourself out of trouble !! “Bubble Trouble” is a fun game where each time you hit a big bubble, it will split up into two smaller ones. Avoid the bubbles as they bounce through the level. Race against time, collect all the traps and power-ups you can use to be the best at this game. Do you have what it takes to be the ultimate bubble shooter?. This is all displayed in the LED matrix acting as the screen. Use your spike gun to pop all the bubbles from the largest to the smallest bits. Can you clear each level?.

Objectives

The main objective of this project was to create the “BUBBLE TROUBLE” video game displayed on a 64X64 RGB LED matrix, with one SJ2 board as a graphics processor/matrix controller, and another SJ2 board as a controller. Other objectives are the following:

  • Design custom PCBs for both the gamepad and matrix controller SJ2 boards.
  • Use the FreeRTOS Real-Time Operating System on both SJ2 boards.
  • Establish UART communications through Xbee between the two SJ-Two Microcontrollers.
  • Create simple coding logic for displaying required characters and game objects.
  • Add background music to the game to enhance the gameplay experience.

Introduction

  • Matrix Controller Board: The matrix controller board is responsible for displaying the graphics of the game, controlling the game logic, playing MP3 tracks based on the current game/menu screen, receiving character movement and button press signals over the Xbee interface.
  • GamePad Controller Board: The gamepad controller board is responsible for processing input joystick and button press signals, controlling the character controls logic, sending character movement and button press signals over an Xbee interface.

HOW TO PLAY BUBBLE TROUBLE: The main aim of the game is to burst all the balloons and advance to the next level.

  • Using the joystick on the game controller, move the character left or right.
  • Shoot arrows using the button on the game controller to burst the balloons into smaller ones.
  • The character must avoid getting hit by the balloon.
  • If the character gets hit by the balloon it loses one life and the level restarts
  • Each level has a time limit to complete it. If all the balloons are not burst in that time limit the player loses one life.
  • With each level the number of balloons and the size of balloons increase.


Technical Responsibilities

Administrative Roles
  • Game Logic Development
Rishabh Gupta & Vilas Dhuri & Saharsh Shivhare
  • PCB Design
Vilas Dhuri
  • LED Display Driver
Rishabh Gupta
  • Graphics Driver
Rishabh Gupta & Vilas Dhuri & Saharsh Shivhare
  • Splash Screen Graphics Driver
Vilas Dhuri & Saharsh Shivhare
  • MP3 Decoder
Saharsh Shivhare
  • Hardware Integration
Vilas Dhuri & Saharsh Shivhare


Administrative Responsibilities

Administrative Roles
  • Team Leader
Rishabh Gupta
  • Git Repository Managers
Rishabh Gupta
  • Code Reviewers
Rishabh Gupta & Vilas Dhuri & Saharsh Shivhare
  • Wiki Report Manager
Vilas Dhuri
  • Bill of Materials Manager
Saharsh Shivhare


Schedule

Week# Start Date End Date Task Status
1
  • 10/11/2021
  • 10/17/2021
  • Read previous projects, gather information, and discuss among the group members.
  • Create a GitLab repository for the project.
  • Completed
  • Completed
2
  • 10/18/2021
  • 10/24/2021
  • Order necessary parts
  • Distributing project tasks among group members
  • Completed
  • Completed
3
  • 10/25/2021
  • 10/31/2021
  • Read and familiarize with LED Matrix Datasheet.
  • Read and familiarize with MP3 Decoder Datasheet.
  • Completed
  • Completed
4
  • 11/01/2021
  • 11/7/2021
  • Finalize wiki schedule
  • Developing graphics driver for LED matrix and implementing initial game objects
  • Designing Game Start-up Screen and Game Over screen
  • Designing PCB and Circuit Simulation in Eagle Tool
  • Completed
  • Completed
  • Completed
  • Completed
5
  • 11/8/2021
  • 11/14/2021
  • Joystick integration and Button for shooting
  • Implementing Character Movement through Joystick using UART
  • Implementing Arrow shooting logic
  • Designing and Implementing Ball Trajectory and bounce logic
  • Completed
  • Completed
  • Completed
  • Completed
6
  • 11/15/2021
  • 11/21/2021
  • Implementing Ball Splitting logic
  • Developing Screen Transition from game screen to level
  • Game logic development
  • Testing and debugging the game logic
  • Completed
  • Completed
  • In Progress
  • In Progress
7
  • 11/22/2021
  • 11/28/2021
  • Configuring Xbee Modules
  • Integrating Xbee for wireless remote control and character Movement
  • LED Matrix Score and Lives Bar
  • Implementing Game timer
  • Implementing game logic for the ball hitting the character
  • Finalize PCB design in software and order PCB
  • Integrating MP3 decoder into the game
  • Integrating game sounds with game logic
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
  • In Progress
  • In Progress
8
  • 11/30/2021
  • 12/06/2021
  • Integrate subsystem
  • Finalizing the video game
  • Update the wiki page.
  • Not started
  • Not started
  • Not started
9
  • 12/07/2021
  • 12/13/2021
  • Address bugs during testing of integrated system
  • Test pause/play functionality
  • Not started
  • Not started
  • Not started
10
  • 12/16/2021
  • 12/14/2021
  • 12/14/2021
  • 12/14/2021
  • 12/16/2021
  • 12/16/2021
  • 12/16/2021
  • 12/16/2021
  • Final Demo
  • Update Gitlab repo with final code.
  • Update test video.
  • Update the wiki page.
  • Not started
  • Not started
  • Not started
  • Not started


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.