Difference between revisions of "F24: Rival Rush"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Created page with "=== Grading Criteria === <font color="green"> * How well is Software & Hardware Design described? * How well can this report be used to reproduce this project? * Code Quali...")
 
(→‎Team Members & Responsibilities)
 
(9 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 ==
−
Parking Frenzy
+
Rival Rush
  
 
== Abstract ==
 
== Abstract ==
−
Parking Frenzy is car parking video game. The player will be able to move the car in right or left direction, the road itself will be descending towards the car and will also consist of obstacles such as other vehicles. The road will have lanes through which the car must navigate to ultimately be able to slot itself into the right parking spot alongside the road. The parking spots will be randomly generated along the edge of the LED matrix and the player must navigate the car into the spot at the right time or else it will result in a crash. The difficulty of the game will increase as the player reaches a certain amount of points. The difficulty will increase in terms of the speed of the car and the number of obstacles. The final score of the player will be displayed at the end of every game. a speaker attached to the board will generate the game sounds.
+
This is a 2 player game that would be implemented on a 64*64 RGB LED. Each player has to move against the oncoming traffic without being hit by any of the vehicles. The players can move left or right horizontally across the highway by tilting the player consoles (SJ2 boards). The movement across the road by tilting is sensed by an accelerometer. The players will have 3 lives each of which is deducted per hit. The players can also collect coins on the road which add to their score. The number and speed of the approaching traffic will increase over time. The player with a greater score at the end of 60 seconds will win the game. The LED will display the players’ scores, number of lives left and the racing track on either side.
  
 
== Objectives & Introduction ==
 
== Objectives & Introduction ==
Line 21: Line 9:
  
 
=== Team Members & Responsibilities ===
 
=== Team Members & Responsibilities ===
−
*  Scott LoCascio
+
*  Alshama Mony Sheena
−
** 
+
*  Harshwardhan Ashish Bhangale
−
*  Naeem Mannan
+
*  Gautam Santhanu Thampy
−
** 
 
−
*  Rahul Ghadge
 
−
** 
 
  
 +
== Schedule ==
  
−
== Schedule ==
 
  
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
 
! scope="col"| Week#
 
! scope="col"| Week#
−
! scope="col"| Start Date
+
! scope="col"| Date
−
! scope="col"| End Date
 
 
! scope="col"| Task
 
! scope="col"| Task
 
! scope="col"| Status
 
! scope="col"| Status
 
|-
 
|-
 
! scope="row"| 1
 
! scope="row"| 1
−
|  
+
| 10/14
−
* 10/12/2020
 
−
* 10/13/2020
 
 
|
 
|
−
* 10/18/2020
+
* To go through previous projects and discuss with the team members.
−
* 10/13/2020
+
* To come up with new ideas for applications specific to FreeRTOS.
−
|
 
−
* Read previous projects, gather information and discuss among the group members.
 
−
* Create GitLab repository for project
 
 
|  
 
|  
−
* <span style="color:green">Completed</span>
+
* Had a brainstorming session with the team and decided to do gaming projects using FreeRTOS.
−
* <span style="color:orange">In progress</span>
+
* Prepared the abstract for the project proposal.
 
|-
 
|-
 
! scope="row"| 2
 
! scope="row"| 2
 +
| 10/21
 
|  
 
|  
−
*10/19/2020 
+
* To decide the structure of the team and divide the project into different modules.
 +
* To assign roles and responsibilities to each team member.
 +
* To finalize the deadlines and deliverables for the project.
 
|  
 
|  
−
*10/20/2020
+
* Assigned roles and responsibilities to each member.
−
|
+
* Created a test plan with tasks, deadlines and deliverables assigned to it.
−
 
 
−
*Order necessary parts
 
−
|
 
−
* <span style="color:orange">In progress</span>
 
 
|-
 
|-
 
! scope="row"| 3
 
! scope="row"| 3
−
|
+
| 10/28
−
*10/26/2020
+
|  
−
|
+
* To start designing the Master module which will take inputs from different players, take a decision and sends it to LED Matrix display.
−
*11/01/2020
+
|  
−
|
+
* Divided the project into different modules like Master, Player, Wireless, LED Display, PCB, and Testing.
−
*Read and familiarize with LED Matrix Datasheet
+
* Started designing the Master module to take inputs from Players.
−
|
 
−
* <span style="color:red">Not started</span>
 
−
 
 
−
 
 
 
|-
 
|-
 
! scope="row"| 4
 
! scope="row"| 4
−
|
+
| 11/04
−
* 11/02/2020
+
|  
−
|
+
* To understand the high-level APIs for the Wireless nordic node.
−
* 11/08/2020
+
* To understand the connections, read the datasheet for RGB LED Matrix.
−
|
+
|  
−
* Develop graphics driver for LED matrix and implement initial game objects
+
* Made a basic layout, pin connections, power requirements for 64x64 RGB LED Matrix.
−
|
+
* Understood the Wireless APIs available and wrote a basic code to send-receive data using Nordic.
−
* <span style="color:red">Not started</span>
 
 
|-
 
|-
 
! scope="row"| 5
 
! scope="row"| 5
−
|
+
| 11/11
−
*11/09/2020
+
|  
−
*11/09/2020
+
* To install Eagle software for PCB design and get accustomed to the basic functions.
−
*11/09/2020
+
|  
−
*11/09/2020
+
 
−
|
 
−
*11/10/2020
 
−
*11/15/2020
 
−
*11/15/2020
 
−
*11/15/2020
 
−
|
 
−
* 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
 
! scope="row"| 6
 +
| 11/18
 
|
 
|
−
*11/16/2020
+
* To test the Player and Master modules.
 +
* To understand addressing mode, latching, and clock functionality for RGB LED Matrix.
 
|  
 
|  
−
*11/22/2020
+
 
−
|
 
−
*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
 
! scope="row"| 7
−
|  
+
| 11/25
−
* 11/23/2020
+
|
  
−
|
 
−
* 11/29/2020
 
−
|
 
−
* 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
 
! scope="row"| 8
 +
| 12/02
 
|  
 
|  
−
* 11/30/2020
+
* To send and receive data between Player and Master using Wireless protocol.
−
|
+
* To write the logic to glow a particular LED on the display matrix.
−
* 12/06/2020
+
* To design and finalize the PCB circuit.
 
|
 
|
  
−
* 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
 
! scope="row"| 9
 +
| 12/09
 
|  
 
|  
−
* 12/07/2020
+
* To implement RGB LED Matrix tasks and APIs for the Master module.
−
|
+
* To integrate the layout of the application (UI, border, car design, obstacle design) to Master Module.
−
* 12/13/2020
+
* To generate random obstacles, score logic and implement other game functionalities (eg: game over scenario).
 +
* To display the cars, border area, screen division for 2 cars and enable obstacle and car movement as per the input from the master module.
 +
* Finalize the PCB design, get it reviewed by the team and send it for fabrication.
 
|
 
|
−
* 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
 
! scope="row"| 10
 +
| 12/16
 
|  
 
|  
−
*12/16/2020
+
* To keep moving the display down continuously for the car race track.
−
*12/14/2020
+
* To move the car horizontally pixel by pixel for every change in data from the player module.
−
*12/14/2020
+
* To test the overall functionality of the project using PCB.
−
*12/14/2020
+
|
 +
 
 +
|-
 +
! scope="row"| 11
 +
| 05/13
 
|  
 
|  
−
*12/16/2020
+
* To Integration of all modules and end to end testing.
−
*12/16/2020
+
* To fix bugs and optimize the code.
−
*12/16/2020
 
−
*12/16/2020
 
 
|
 
|
  
−
*Final Demo
+
|-
−
*Update Gitlab repo with final code.
+
|-
−
*Update test video.
+
! scope="row"| 12
−
*Update the wiki page.
+
| 05/20
 +
|
 +
* Adding extra functionalities and extra features for the project.
 +
* Test the extra features with overall project requirement.
 
|
 
|
−
* <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 ==
 
== Parts List & Cost ==

Latest revision as of 20:34, 4 November 2024

Project Title

Rival Rush

Abstract

This is a 2 player game that would be implemented on a 64*64 RGB LED. Each player has to move against the oncoming traffic without being hit by any of the vehicles. The players can move left or right horizontally across the highway by tilting the player consoles (SJ2 boards). The movement across the road by tilting is sensed by an accelerometer. The players will have 3 lives each of which is deducted per hit. The players can also collect coins on the road which add to their score. The number and speed of the approaching traffic will increase over time. The player with a greater score at the end of 60 seconds will win the game. The LED will display the players’ scores, number of lives left and the racing track on either side.

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

  • Alshama Mony Sheena
  • Harshwardhan Ashish Bhangale
  • Gautam Santhanu Thampy

Schedule

Week# Date Task Status
1 10/14
  • To go through previous projects and discuss with the team members.
  • To come up with new ideas for applications specific to FreeRTOS.
  • Had a brainstorming session with the team and decided to do gaming projects using FreeRTOS.
  • Prepared the abstract for the project proposal.
2 10/21
  • To decide the structure of the team and divide the project into different modules.
  • To assign roles and responsibilities to each team member.
  • To finalize the deadlines and deliverables for the project.
  • Assigned roles and responsibilities to each member.
  • Created a test plan with tasks, deadlines and deliverables assigned to it.
3 10/28
  • To start designing the Master module which will take inputs from different players, take a decision and sends it to LED Matrix display.
  • Divided the project into different modules like Master, Player, Wireless, LED Display, PCB, and Testing.
  • Started designing the Master module to take inputs from Players.
4 11/04
  • To understand the high-level APIs for the Wireless nordic node.
  • To understand the connections, read the datasheet for RGB LED Matrix.
  • Made a basic layout, pin connections, power requirements for 64x64 RGB LED Matrix.
  • Understood the Wireless APIs available and wrote a basic code to send-receive data using Nordic.
5 11/11
  • To install Eagle software for PCB design and get accustomed to the basic functions.
6 11/18
  • To test the Player and Master modules.
  • To understand addressing mode, latching, and clock functionality for RGB LED Matrix.
7 11/25
8 12/02
  • To send and receive data between Player and Master using Wireless protocol.
  • To write the logic to glow a particular LED on the display matrix.
  • To design and finalize the PCB circuit.
9 12/09
  • To implement RGB LED Matrix tasks and APIs for the Master module.
  • To integrate the layout of the application (UI, border, car design, obstacle design) to Master Module.
  • To generate random obstacles, score logic and implement other game functionalities (eg: game over scenario).
  • To display the cars, border area, screen division for 2 cars and enable obstacle and car movement as per the input from the master module.
  • Finalize the PCB design, get it reviewed by the team and send it for fabrication.
10 12/16
  • To keep moving the display down continuously for the car race track.
  • To move the car horizontally pixel by pixel for every change in data from the player module.
  • To test the overall functionality of the project using PCB.
11 05/13
  • To Integration of all modules and end to end testing.
  • To fix bugs and optimize the code.
12 05/20
  • Adding extra functionalities and extra features for the project.
  • Test the extra features with overall project requirement.

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.

Retrieved from "http://socialledge.com/sjsu/index.php?title=F24:_Rival_Rush&oldid=72558"