Difference between revisions of "F18: Catch me if you can"
Proj user11 (talk | contribs) (→Parts List & Cost) |
Proj user11 (talk | contribs) (→Parts List & Cost) |
||
| Line 132: | Line 132: | ||
| 1 | | 1 | ||
| NA | | NA | ||
| + | |- | ||
| + | ! scope="row"| 8 | ||
| + | | Miscellaneous | ||
| + | | | ||
| + | | | ||
|} | |} | ||
Revision as of 02:12, 27 October 2018
Contents
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 console board for various events during the game like when an egg is missed or an intermediate milestone is reached.
Objectives & Introduction
Display Module:LED display Control Module:/* yet to fill*/ Wireless Module:/* yet to fill */
Team Members & Responsibilities
- Rishabh Sheth
- Managing WiKi, PCB design, and console application code.
- Kailash Kumar Chakravarty
- LED 32x32 matrix driver and Game display application code.
- Nandini Mandya Shankaraiah
- Audio output driver and Game display application code.
- Aquib Abduljabbar Mulani
- Wireless chip driver/application and calibrating accelerometer.
- Swanand Sapre
- Menu Handling via switches and console application code.
Schedule
| Week# | Date | Task | Actual |
|---|---|---|---|
| 1 | 10/23 | Product Requirement Document preparation & Order Required parts. | |
| 2 | 10/30 | Software Design Document / Toplevel design of Game display | ? |
| 3 | 11/6 | Software Design Document / Toplevel design of Game Console | ? |
| 4 | 11/13 | Driver & testing of individual module 32x32 LED display, wireless communication and Audio output | ? |
| 5 | 11/20 | Intigration and testing of all module i.e basic funcationalty like wirelessly controlling basket on display | ? |
| 6 | 11/27 | First PCB layout design and final release of Catch me if you can driver code | ? |
| 7 | 12/4 | Physical PCB on hand, UI improvement and test case preparation. | ? |
| 8 | 12/11 | Testing and final release of source code & hardware | ? |
Parts List & Cost
| Sl No | Parts | Quantity | Price |
|---|---|---|---|
| 1 | SJ One Board | 2 | 160 |
| 2 | LED Matrix Display | 1 | $55.6 |
| 3 | Speaker | 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
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.
