F21: MARIO - Revision history

Proj user13: /* Schedule */

2021-11-03T03:23:29Z

‎Schedule

Proj user13: /* Schedule */

2021-11-03T03:20:55Z

‎Schedule

Proj user13: /* Schedule */

2021-11-03T02:55:38Z

‎Schedule

Proj user13: /* Project Title */

2021-10-16T21:31:51Z

‎Project Title

Proj user13: /* Schedule */

2021-10-16T21:27:55Z

‎Schedule

Proj user13: /* Schedule */

2021-10-16T21:14:32Z

‎Schedule

Proj user13: /* Project Title */

2021-10-16T20:54:53Z

‎Project Title

Proj user13: /* Abstract */

2021-10-16T20:50:13Z

‎Abstract

Proj user13: /* Team Members & Responsibilities */

2021-10-13T23:20:40Z

‎Team Members & Responsibilities

Proj user13: Created page with "=== Grading Criteria === * How well is Software & Hardware Design described? * How well can this report be used to reproduce this project? * Code Quali..."

2021-10-13T23:19:00Z

Created page with "=== Grading Criteria === * How well is Software & Hardware Design described? * How well can this report be used to reproduce this project? * Code Quali..."

New page

=== 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 ==
Parking Frenzy

== 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 along side 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.

== 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 ===
* Scott LoCascio
**
* Naeem Mannan
**
* Rahul Ghadge
**

== Schedule ==

{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Start Date
! scope="col"| End Date
! scope="col"| Task
! scope="col"| Status
|-
! scope="row"| 1
|
* 10/12/2020
* 10/13/2020
|
* 10/18/2020
* 10/13/2020
|
* Read previous projects, gather information and discuss among the group members.
* Create GitLab repository for project
|
* Completed
* In progress
|-
! scope="row"| 2
|
*10/19/2020
|
*10/20/2020
|

*Order necessary parts
|
* In progress
|-
! scope="row"| 3
|
*10/26/2020
|
*11/01/2020
|
*Read and familiarize with LED Matrix Datasheet
|
* Not started

|-
! scope="row"| 4
|
* 11/02/2020
|
* 11/08/2020
|
* Develop graphics driver for LED matrix and implement initial game objects
|
* Not started
|-
! scope="row"| 5
|
*11/09/2020
*11/09/2020
*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
|
* Not started
* Not started
* Not started
* Not started
* Not started
|-
! scope="row"| 6
|
*11/16/2020
|
*11/22/2020
|
*Integration of circuit boards and microcontroller
* Game logic development
* Testing and debugging the game logic
|
* Not started
* Not started
* Not started
|-
! scope="row"| 7
|
* 11/23/2020

|
* 11/29/2020
|
* Integrate game logic code with LED matrix
* Integrate game sounds with game logic
|
* Not started
* Not started
|-
! scope="row"| 8
|
* 11/30/2020
|
* 12/06/2020
|

* Integrate subsystem
* Finalizing the video game
* Update the wiki page.
|
* Not started
* Not started
* Not started
|-
! scope="row"| 9
|
* 12/07/2020
|
* 12/13/2020
|
* Address bugs during testing of integrated system
* Test pause/play functionality
|
* Not started
* Not started
* Not started
|-
! scope="row"| 10
|
*12/16/2020
*12/14/2020
*12/14/2020
*12/14/2020
|
*12/16/2020
*12/16/2020
*12/16/2020
*12/16/2020
|

*Final Demo
*Update Gitlab repo with final code.
*Update test video.
*Update the wiki page.
|
* Not started
* Not started
* Not started
* Not started
|-
|}

<HR>
 

== 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 ===
* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]

== 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.

@@ Line 41: / Line 41: @@
+|
 * 10/15/2021
 * 10/25/2021
+|

@@ Line 40: / Line 40: @@
 ! scope="row"| 1
+|
-* 10/12/2020
+* 10/15/2021
-* 10/13/2020
+* 10/25/2021
+|
 * Read previous projects, gather information and discuss among the group members.
@@ Line 66: / Line 63: @@
 ! scope="row"| 2
+|
-*10/19/2020
+*10/25/2021
+|
-*10/20/2020
+*11/03/2021
+|
 *Choose game based on Preet's Project Proposal feedback
@@ Line 77: / Line 74: @@
 *Brainstorm gameplay, rules, and level design on paper
+|
-* <span style="color:orange">In progress</span>
+* <span style="color:green">Completed</span>
 |-
 ! scope="row"| 3
+|
-*10/26/2020
+*11/04/2021
+|
-*11/01/2020
+*11/09/2021
+|
 *Read and familiarize with LED Matrix Datasheet
@@ Line 110: / Line 112: @@
 ! scope="row"| 5
+|
-*11/09/2020
+*11/09/2021
-*11/09/2020
+*11/09/2021
-*11/09/2020
+*11/09/2021
-*11/09/2020
+*11/09/2021
+|
-*11/10/2020
+*11/10/2021
-*11/15/2020
+*11/15/2021
-*11/15/2020
+*11/15/2021
-*11/15/2020
+*11/15/2021
+|
 * Finalize wiki schedule
 * circuit board and component assembly
 * Circuit board testing
@@ Line 131: / Line 132: @@
 *Bluetooth modules can send controls data back and forth between game pad board and master board
 *Controls data can be accessed using "get" and "set" API
-*Plan PCB design on paper
+*Plan PCB design on paper.
 *Game pad controller can read joystick and accelerometer values and detect switch presses
 *Decide how to handle each collision detection case (character/enemy, bullet/enemy, etc.)
 *Finish enclosure design in AutoCAD software and start printing
 *Finalize PCB design on paper and design in PCB software
 *LED matrix displays character orientation correctly depending on current movement direction
 *Controller input (joystick or accelerometer) option is implemented on game pad controller
 *Bullet moves on LED matrix when button is pressed
 *Finalize PCB design in software and order PCB
@@ Line 156: / Line 150: @@
 ! scope="row"| 6
+|
-*11/16/2020
+*11/16/2021
+|
-*11/22/2020
+*11/22/2021
+|
 *LED matrix menu screens and game over/victory screens are implemented on matrix
@@ Line 168: / Line 162: @@
 *Finalize MP3 track selection for each screen and during gameplay
 *Collision detection logic is fully functional and displays correctly on LED matrix
 * Testing and debugging the game logic
+|
@@ Line 178: / Line 170: @@
 ! scope="row"| 7
+|
-* 11/23/2020
+* 11/23/2021
+|
-* 11/29/2020
+* 11/29/2021
+|
 * Integrate game logic code with LED matrix
 * Integrate game sounds with game logic
-*Finish rough draft of project report
+* Finish rough draft of project report
-*Write gameplay logic code on master controller. Gameplay logic should update the score and status bar items correctly
+* Write gameplay logic code on master controller. Gameplay logic should update the score and status bar items correctly
-*LED matrix graphics design for all levels is complete
+* LED matrix graphics design for all levels is complete
-*MP3 decoder plays correct song/track during gameplay and for each menu/game over screen
+* MP3 decoder plays correct song/track during gameplay and for each menu/game over screen
-*Gameplay state machine switches to next state based on user button presses and gameplay progression
+* Gameplay state machine switches to next state based on user button presses and gameplay progression
+|
 * <span style="color:red">Not started</span>
@@ Line 196: / Line 188: @@
 ! scope="row"| 8
+|
-* 11/30/2020
+* 11/30/2021
+|
-* 12/06/2020
+* 12/06/2021
+|
@@ Line 211: / Line 203: @@
 ! scope="row"| 9
+|
-* 12/07/2020
+* 12/07/2021
+|
-* 12/13/2020
+* 12/13/2021
+|
 * Address bugs during testing of integrated system
@@ Line 224: / Line 216: @@
 ! scope="row"| 10
+|
-*12/16/2020
+*12/16/2021
-*12/14/2020
+*12/14/2021
-*12/14/2020
+*12/14/2021
-*12/14/2020
+*12/14/2021
+|
 *12/16/2020

@@ Line 51: / Line 51: @@
 * Finalize parts list
 * Setup splitwise account for cost sharing
 * Create GitLab repository for project
 * Decide on day/time for weekly meetings
+|
 * <span style="color:green">Completed</span>
-* <span style="color:orange">In progress</span>
+* <span style="color:green">Completed</span>
 |-
 ! scope="row"| 2

@@ Line 12: / Line 12: @@
 == Project Title ==
-Ace Mario
+Hotshot Mario
 == Abstract ==

@@ Line 47: / Line 47: @@
+|
 * Read previous projects, gather information and discuss among the group members.
-* Decide on day/time for weekly meetings
+* Decide on 2 game ideas and submit Project Proposal assignment
-* Decide on 2 game ideas
+* Discussion on using wireless or wired controllers,3D printing options,PCB softwares and manufacturer.
 * Finalize parts list
 * Setup splitwise account for cost sharing
 * Setup team GitLab repo with master and working master branches
 * Create GitLab repository for project
+* Decide on day/time for weekly meetings
+|
 * <span style="color:green">Completed</span>
@@ Line 68: / Line 63: @@
+|
 *10/20/2020
-−
+|
 *Choose game based on Preet's Project Proposal feedback
 *Finish schedule rough draft and upload to Wiki report
 *Order project parts
-*Submit Wiki schedule assignment
+*Break project up into tasks and assign project tasks to team members
 *Obtain datasheets for all parts and upload to team Google Drive folder
 *Brainstorm gameplay, rules, and level design on paper
@@ Line 105: / Line 94: @@
 * 11/08/2020
+|
 *Develop graphics driver for LED matrix and implement initial game objects
 *Begin developing MP3 decoder board driver
 *Begin developing bluetooth board driver
-Finalize CAD enclosure design on paper and begin designing in AutoCAD software
+*Finalize CAD enclosure design on paper and begin designing in AutoCAD software
+|
 * <span style="color:red">Not started</span>
@@ Line 242: / Line 230: @@
 *Final Demo
 *Update Gitlab repo with final code.
-*Update test video.
+*Film demo video
 *Update the wiki page.
-*Film demo video and upload. Create link on Wiki report
+*Finalize project report and submit
+|
 * <span style="color:red">Not started</span>

@@ Line 15: / Line 15: @@
 == 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 along side 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.
+Super Mario is one of the best-selling games of all time, with more than 50 million copies sold worldwide. Our goal will be to produce a similar version of it where the player controls Mario. Mario has to race through the Mushroom Kingdom and save Princess.
 == Objectives & Introduction ==

@@ Line 21: / Line 21: @@
 === Team Members & Responsibilities ===
-*  Scott LoCascio
+*  Vivek Tapkir
 **
-*  Naeem Mannan
+*  Shreevats Gadhikar
 **
-*  Rahul Ghadge
+*  Daya Modekar
 **
 == Schedule ==