Difference between revisions of "F19: Road Max Fury"

Revision as of 03:17, 18 October 2019

Project Title

Road Max Fury- Game using FreeRTOS

Abstract

Road Max Fury is a game based on a classic car racing arcade game developed in 1984 by Konami named Road Fighter. We planned to reproduce this game as a part of our CMPE 244 project. The goal is to reach the finish line without running out of time, avoiding other cars on the road or running out of fuel .The fuel is refilled by hitting petrol pump which the player can encounter at random location during the course of the game. The player also needs to prevent car from hitting the edge of the road to prevent the collision.

Example Link: https://www.youtube.com/watch?v=1FzumH75whY

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

Namdev Prabhugaonkar
Rutuja Shah
Saumil Shah

Schedule

Week#	Date	Deliverables	Status
1	09/29	Road Max Fury project approved by instructor	Completed
Week#	Date	Deliverables	Status
2	10/12	Create project Wiki page Create a Bill of Materials Select and order Parts	Completed Completed Completed
Week#	Date	Deliverables	Status
3	10/16	Create and establish Github repository Create and setup Slack Channel Look through previous years projects and study it Distribute major roles among team members UI and initial game design	Completed Completed Completed Completed Completed
Week#	Date	Deliverables	Status
4	10/23	Make Repo on Github for all modules - Follow Naming Convention Learn about PCB layouts and PCB building Learn about on board accelerometer and get values on terminal Understand the LED matrix data sheet	TO DO TO DO TO DO TO DO
Week#	Date	Deliverables	Status
5	10/30	Develop patterns on LED matrix Game algorithm design Understand the accelerometer values and develop a filter to obtain required values	TO DO TO DO TO DO
Week#	Date	Deliverables	Status
6	11/06	Interface LED matrix display Interface and test accelerometer	TO DO TO DO
Week#	Date	Deliverables	Status
7	11/13	Car creation and movement Implement random obstacle creation algorithm	TO DO TO DO
Week#	Date	Deliverables	Status
8	11/20	Interface accelerometer with car movement Understand and implement SD-card read Render SD-card data to MP3 decoder	TO DO TO DO TO DO
Week#	Date	Deliverables	Status
9	11/27	Implement car collision detection Perform unit testing Start intergrating modules	TO DO TO DO TO DO
Week#	Date	Deliverables	Status
10	12/10	Integration testing Bug fixes Wiki report completion	TO DO TO DO TO DO
Week#	Date	Deliverables	Status
11	12/18	Complete final implementation of Road Max Fury Complete debugging of all game components Demo	TO DO TO DO TO DO

Parts List & Cost

Part	#	Cost	Source
SJ2 Board	2	$110.00	Preet
Azerone 32 x 64 LED Matrix	1	$31.99	https://www.amazon.com/gp/product/B07F2JW8D3/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
HiLetgo MP3 Decoder	1	$6.99	https://www.amazon.com/gp/product/B0725RHR4D/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

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.

@@ Line 80: / Line 80: @@
 * Learn about PCB layouts and PCB building
 * Learn about on board accelerometer and get values on terminal
+* Understand the LED matrix data sheet
 |
+* TO DO
 * TO DO
 * TO DO
@@ Line 93: / Line 95: @@
 | 10/30
 |
-* Understand the LED matrix data sheet
+* Develop patterns on LED matrix
 * Game algorithm design
-* Understand accelerometer datasheet
+* Understand the accelerometer values and develop a filter to obtain required values
 |
 * TO DO