Difference between revisions of "F18: 1v1 Penalty Shootout"
Proj user17 (talk | contribs) (→Schedule) |
Proj user17 (talk | contribs) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
== Project Title == | == Project Title == | ||
− | ==== | + | ==== Goals of Glory ==== |
== Abstract == | == Abstract == | ||
Line 68: | Line 68: | ||
| | | | ||
* Research on components required for the approved project. | * Research on components required for the approved project. | ||
+ | * Discuss project requirements and implementation logic with group members. | ||
| | | | ||
* 1v1 Penalty Shootout Project got approved by the professor | * 1v1 Penalty Shootout Project got approved by the professor | ||
Line 74: | Line 75: | ||
| 10/9 | | 10/9 | ||
| | | | ||
− | |||
* Divide the project into different modules. | * Divide the project into different modules. | ||
* Assign responsibilities to each group member. | * Assign responsibilities to each group member. | ||
Line 204: | Line 204: | ||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
− | | | + | | WiFi Antenna |
− | | | + | | |
| 3 | | 3 | ||
− | | | + | | |
|} | |} |
Latest revision as of 20:11, 7 December 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
Goals of Glory
Abstract
The game works like a classic penalty shootout where 2 players will be able to play wirelessly, and the corresponding game visuals will be displayed on the LED Matrix. The logic is based on the output from a group of gesture sensors. The sensors detect the motion of player leg movements to kick and hand movements of the goalkeeper to stop the ball and the corresponding game visuals are displayed on the LED matrix in real time. The LED matrix is interfaced to the SJone board in such a way that it receives commands wirelessly from hand and leg movements of each player using sensor nodes. Three display modes will be used for the game UI- Start mode, Game mode and display result mode. Thus, the user can experience a mini version of games using motion sensing.
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.
Objectives
Team Members & Responsibilities
- Player Movements
- Aniket Phatak
- Bhargav Shashidhara Pandit
- Goalkeeper Movements
- Tahir Rawn
- Harmeen Joshi
- Display (RGB LED Matrix)
- Harmeen Joshi
- Tahir Rawn
- Satya Sai Deepak. Naidu
- Wireless (Nordic)
- Aniket Phatak
- Bhargav Shashidhara Pandit
- PCB Design
- Satya Sai Deepak. Naidu
Schedule
Week# | Date | Task | Status |
---|---|---|---|
1 | 09/25 |
|
|
2 | 10/02 |
|
|
3 | 10/9 |
|
|
4 | 10/23 |
|
|
5 | 10/30 |
|
|
6 | 11/06 |
|
|
7 | 11/13 |
|
|
8 | 11/20 |
|
|
9 | 11/27 |
|
|
10 | 12/4 |
|
|
11 | 12/11 |
|
|
Parts List & Cost
Item# | Part Desciption | Vendor | Qty | Cost |
---|---|---|---|---|
1 | SJOne Boards | Preet | 3 | $240.00 |
2 | 64x64 RGB LED Matrix | Sparkfun | 1 | $75.00 |
3 | Power Adaptor Cable | Amazon | 1 | $9 |
4 | PCB | PCBWay [1] | 5 | $30 |
5 | MPU 6050 | Amazon | 2 | $11 |
6 | WiFi Antenna | 3 |
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.