Difference between revisions of "F21: Flame Over"

Revision as of 20:05, 16 December 2021

Abstract

Flame Over is a single-player mode game where the player moves a fire fighter to destroy the fire flames that come shooting at the player using a water gun. The player is granted four lives at the start of the game at each level. The Player’s lives will decrease by one for every three flames that touch the fire fighter. The player transits to the next level when enough flames are destroyed at each level. The speed of the flames approaching the fire fighter varies between levels.

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.

Objectives

• Write driver module to display game characters and update the display continuously at an optimum refresh rate
• Implement game algorithm for movement of player and flames in real-time, generate water splash bullets.
• Implement player lives count, player health and collision algorithms.
• Write driver module to receive directions from the input device (joystick) via zigbee.
• Fetch Joystick data over ADC and transmit the joystick signals wirelessly via Zigbee with the help of UART drivers.
• Write driver module to play game sounds via MP3 encoder
• Use FreeRTOS tasks and understand task priority and synchronization.

Team Members & Responsibilities

• Naveena Sura
  • Game logic and design
  • Game implementation
  • Built game characters on LED matrix display
  • Game Animation Screens
  • Bug fixes and optimizations
• Suganya Nandakumar
  • GPIO Driver for LED matrix display
  • Built game characters on LED matrix display
  • PCB Schematic and Board Design
  • Soldering all components on PCB
• Vaidehi Deshpande
  • Joystick Interfacing - ADC driver
  • Speaker and MP3 Decoder interfacing
  • Zigbee interfacing with UART driver for transmission and reception
  • Built game characters on LED matrix display

Schedule

Parts List & Cost

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.

Pin Configuration

LED Matrix

A 64x64 RGB LED Matrix Panel is used as a display. It has 64 rows and 64 columns. It is divided into two 32x64 sections. A LED or pixel (which we use in subsequent sections) can be accessed and controlled individually. A decoder is used to access individual row. One row can be selected at a time using A,B,C,D and E pins. This enables us to select one row in each of the 32X64 sections. Columns are controlled using shift registers, every bit in the shift register controls the corresponding column. On every falling edge of the clock pulse, the values at R1, B1, G1, R2, B2, and G2 pins are stored into the shift register and the register shifts the data by one bit. After this, the data on the shift register is passed onto the individual LED's when both OE and LE pins are set to high.

LED Matrix front View

LED Matrix rear View

LED matrix pins: S.NO RGB LED pins SJone GPIO pins 1 R1 P2.5 2 G1 P0.1 3 B1 P0.18 4 R2 P0.15 5 G2 P2.9 6 B2 P2.7 7 A P2.4 8 B P0.0 9 C P0.22 10 D P0.17 11 CLK P0.16 12 OE P2.8 13 LAT P2.6 14 VCC 3.3V 15 GND GND

LED Matrix Organisation

Hardware Design

Software Design and Implementation

Game Start screen:

At the start of the game, a welcome screen is continously displayed until the player is ready and presses the start key. Only on start key press, the freertos game logic tasks are scheduled.

Game Design and tasks:

We used six freertos tasks of different priorities to control the course of the game:

• Game display Task
  • Refreshes the screen ie., it clears and updates the screen every 3 milliseconds.
  • Draws all the game characters ie., fireman, flames and fireman lives periodically every 3 milliseconds.
  • Implements logic to check for level ups, game win or lose status.
  • Checks if the fireman was able to successfully put the flames off or if the flames hit the fireman and updates the count of fireman lives based on this.

• Fireman Task:
  • Keeps track of the direction control data transmitted wirelessly from the joystick device from the other board and accordingly updates Fireman position.
  • Also has a logic to update water splash trigger flag when the joystick key press signal is received.

• Water Splash Task
  • Reads the water splash trigger flag that has been updated in ‘Fireman Task’ and controls the movement of water splash bullets.
  • Plays a water bullet sound track every time water splash bullets are released.

• Flame1 Task and Flame2 Task
  • Generates Flames on two horizontal tracks from the left and move them towards the right end unless striked by a water bullet, in which case, the flames burst and are put off.
  • Generates random starting row positions for each of these flames.
  • Controls the speed of movement of these flames based on the game level.
  • Decrements the fireman health every time the fireman is hit by a flame.

Collision detection:

• Bullet to Enemy Collision
  • The movement of bullet and enemy spaceship is stopped and both are cleared from the screen. Kill count is incremented for level up and respective flags are set. Burst animation is played at the collision spot.

• Spaceship to Enemy Collision
  • The movement of enemy spaceship is stopped and it is cleared from the screen. Respective flags are set and burst animation is played at the collision spot.

Printed Circuit Board

Layout & Design

We have designed our Printed Circuit Board using AUTODESK EAGLE software, version 9.6.2. As we did not have any prior hands-on experience in designing a PCB, initially we did not have a clear idea on where to begin. The lecture on Eagle PCB provided by Professor Preet provided a good insight about using this software and building a PCB. As suggested during the lecture, we followed Sparkfun Eagle tutorials and libraries while working on the PCB. These resources served as a good source of information for us and made our work easy.

For PCB fabrication, we