Difference between revisions of "F20: Son of a Gun"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Abstract)
(Abstract)
Line 17: Line 17:
  
  
[[File:Block_Diagram_SOG.jpg|800px|thumb|center|Block Diagram of Son Of a Gun]]
+
[[File:Block_Diagram_SOG.jpg|800px|thumb|center|Block Diagram of Game Son Of a Gun]]
  
 
== Objectives & Introduction ==
 
== Objectives & Introduction ==

Revision as of 01:08, 24 October 2020

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.

Son of a Gun

Abstract

Son Of A Gun is a shooting game inspired by the evergreen classics Duck Hunt and Virtua Cop 2. There will be enemy and friend objects on the LED matrix. The player will use a gun(having IR/color sensor or gyroscope) to aim and shoot the objects on the LED matrix. Killing the friend object will lead to 'Game Over'.


Block Diagram of Game Son Of a Gun

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

  • Tejas Pidkalwar
  • Tirth Pandya
  • Nimit Patel

Schedule

Week# Date Task Actual Status
1

09/23 - 09/29

  • Review previous projects
  • Brainstorm on games and proposals
  • Frame the project proposals
  • 09/24
  • 09/25
  • 09/27
  • Completed
  • Completed
  • Completed
2

09/30 - 10/06

  • Components search and analysis
  • Discuss probable gameplays and challenges
  • 10/03
  • 10/04
  • Completed
  • Completed
3

10/07 - 10/13

  • Set up git repository
  • Set up JIRA for project management
  • 10/18
  • 10/10
  • Completed
  • Completed
4

10/14 - 10/20

  • Set up wikipage
  • Prepare initial wiki schedule
  • Order finalized components
  • Study data-sheets of the components
  • Create a high-level flowchart of the project
  • 10/15
  • 10/19
  • 10/18
  • 10/20
  • 10/20
  • Completed
  • Completed
  • Completed
  • Completed
  • Completed
5

10/21 - 10/27

  • Distribute major roles among team members
  • Test the acquired parts and components
  • Develop basic drivers for LED matrix and sensors
  • Finalize gameplay objects - v1.0

Incomplete

6

10/28 - 11/03

  • Test and integrate the basic drivers
  • Add functionalities for gameplay[v1.0]
    • Aim cursor and object mobility with shoot detection

Incomplete

7

11/04 - 11/10

  • Develop and design UI and console casing
  • Develop and integrate sound effects
  • Improve the gameplay - v2.0
    • Improved objects and graphics with sound effects and UI

Incomplete

8

11/11 - 11/17

  • Test and fix the gameplay[v2.0]
  • Discuss and design advance levels in the gameplay
  • Develop wireless functionalities for the game
  • Finalize the full gameplay - v3.0

Incomplete

9

11/18 - 11/24

  • Design and order PCB
  • Integrate and test all the functionalities for gameplay[v3.0]
  • Design casing for the power supply and other modules

Incomplete

10

11/25 - 12/01

  • Integrate the designed PCB
  • Enclose the modules with the gun and the LED matrix
  • Fine tunings and adjustments
  • Complete the documentation

Incomplete

11

12/02 - 12/07

  • Final testing and fixes
  • Upload game video and other details
  • Prepare for Final Demo

Incomplete

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.