F18: Catch me if you can

From Embedded Systems Learning Academy
Revision as of 00:41, 21 November 2018 by Proj user11 (talk | contribs) (→‎Parts List & Cost)

Jump to: navigation, search

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

Catch Me If You Can

Abstract

"Catch me if you can" is a fun game where the user must be attentive and agile enough to catch the randomly dropping eggs from above into a basket. This is all displayed in the LED matrix acting as the screen. The user shall gain and accumulate points equivalent to the eggs collected successfully and there shall be a limited score for each level. The system will consist of two SJ boards, the one board will be used as a game console with which user will try to catch the eggs by moving the board in the required orientation. The other board will control the display module that displays the graphics of eggs falling and also the basket movement. The display module shall communicate with the game console via RF Nordic transceiver. There will be various sounds produced by the display module board for various events during the game like an egg catch\miss or an intermediate milestone reached.

Objectives & Introduction

Display Module:LED display Control Module:/* yet to fill*/ Wireless Module:/* yet to fill */

Team Members & Responsibilities

  • Aquib Abduljabbar Mulani
    • Wireless chip driver/application and calibrating accelerometer.
  • Kailash Kumar Chakravarty
    • RGB LED 32x32 matrix driver and game display application code.
  • Nandini Mandya Shankaraiah
    • Audio output driver and game display application code.
  • Rishabh Sheth
    • Managing WiKi, PCB design, and console application code.
  • Swanand Sapre
    • Menu handling via switches and console application code.

Schedule

Week# Date Task Status Actual Completion Date
1 10/8 Product Requirement Analysis & Order Required Parts. Completed 10/25/2018
2 10/26 Software Design and ownership of each module Completed 10/27/2018
3 10/30
  • Calibrating Accelerometer values for actual orientation
  • Developed algorithm for basket movement using accelerometer values
 Completed 11/09/2018
4 11/6
  • Design schematics for consol charging circuit & LED display circuit
  • Finalize parts and components for PCB design and develop footprints library for KiCAD (if not present)
In progress
5 11/6
  • Porting Adafruit LED driver into LPC
  • Basic LED testing by activating individual and group of pixels
  • Develop game specific APIs to draw objects like basket on top of led driver
Completed 10/09/2018
6 11/6
  • Start and Stop switch, which controls the power to the system and displays Welcome and Good Bye screen
  • Pause switch to pause the game,which holds LED display content still.
7 11/6
  • Speaker integration to the display module play some random sound which is stored in the Flash/SD card
  • Design PCB for Console & Display and generate Gerber files, finalize PCB manufacture
8 11/20
  • Order PCB for manufacturing and order missing components
9 11/27 Algorithm development and testing for the Game interactions
10 12/04 Final testing and Bug fixes
11 12/11 Complete Wiki Report and Final Demo

Parts List & Cost

Sl No Parts Quantity Price
1 SJ One Board 2 $160
2 LED Matrix Display 1 $55.6
3 Piezo Buzzer 2 $1.5
4 Accelerometer 1 NA
5 Switches 4 NA
6 Portable Power Supply 1 $5
7 RF Nordic TX 1 NA
8 Miscellaneous

Design & 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=F18:_Catch_me_if_you_can&oldid=49007"