Difference between revisions of "F18: 1v1 Penalty Shootout"
Proj user17 (talk | contribs) (→Team Members & Responsibilities) |
Proj user17 (talk | contribs) (→Schedule) |
||
| Line 46: | Line 46: | ||
== Schedule == | == Schedule == | ||
| − | + | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 53: | Line 53: | ||
! scope="col"| Date | ! scope="col"| Date | ||
! scope="col"| Task | ! scope="col"| Task | ||
| − | ! scope="col"| | + | ! scope="col"| Status |
|- | |- | ||
! scope="row"| 1 | ! scope="row"| 1 | ||
| − | | | + | | 09/25 |
| + | | | ||
| + | * Discuss project ideas to implement gaming projects with group members | ||
| + | * To come up with new ideas for applications specific to FreeRTOS | ||
| + | * Submitted the abstract for the Car Racing Game and 1v1 Penalty Shootout for project approval. | ||
| | | | ||
| − | * | + | * Submitted project proposals and waiting for approval from the professor. |
| − | |||
|- | |- | ||
! scope="row"| 2 | ! scope="row"| 2 | ||
| − | | 10/ | + | | 10/02 |
| | | | ||
| − | * Research on project | + | * Research on components required for the approved project. |
| − | |||
| − | |||
| | | | ||
| + | * 1v1 Penalty Shootout Project got approved by the professor | ||
|- | |- | ||
! scope="row"| 3 | ! scope="row"| 3 | ||
| − | | 10/ | + | | 10/9 |
| − | | | + | | |
| − | * | + | * Discuss project requirements and implementation logic with group members. |
| − | + | * Divide the project into different modules. | |
| − | + | * Assign responsibilities to each group member. | |
| + | * Decide deadlines and deliverables for each module. | ||
| | | | ||
| + | * Divided the workload among each and every group members. | ||
| + | * Finalized the project implementation logic and developed the basic idea. | ||
|- | |- | ||
! scope="row"| 4 | ! scope="row"| 4 | ||
| − | | | + | | 10/23 |
| | | | ||
| − | * | + | * To verify power requirements for LED Matrix |
| − | * | + | * Ordered 64x64 LED Matrix from Sparkfun. |
| + | * Ordered power supply for LED Matrix from Amazon. | ||
| | | | ||
| + | * Confirmed the voltage and current rating and placed an order for the power adapter. | ||
|- | |- | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
| − | | | + | | 10/30 |
| − | | | + | | |
| − | * | + | * Started working on Accelerometer available on SJOne board for player movement. |
| − | * | + | * Understand the high-level APIs for the Wireless nordic communication. |
| − | + | * Understand 64x64 LED Matrix connections from Sparkfun datasheets. | |
| + | * Brush up on transistor basics and understand how data flows in a given LED Matrix. | ||
| + | * Get accustomed to Eagle software for PCB design and get used to basic functionality. | ||
| | | | ||
| + | * Implemented few basic PCB designs | ||
| + | * Verified pin connections, power requirements for 64x64 RGB LED Matrix. | ||
| + | * Installed Eagle software and made a simple circuit to get acquainted with the software. | ||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| − | | 11/ | + | | 11/06 |
| − | | | + | | |
| − | + | * To develop game visuals such as goalpost, ball and ball movement animation. | |
| − | * | + | * To develop a good understanding of wireless communication between two SJone boards. |
| − | * | + | * To control individual LED's on a 64x64 LED Matrix. |
| − | + | * Understand output latch and output enable addressing modes on a LED Matrix. | |
| | | | ||
| + | * Successfully able to display game visuals. | ||
| + | * Got a basic idea of addressing specific LEDs on LED Matrix using 5-address lines. | ||
| + | * Understood the functionality of latch, output enable and clock pins of LED Matrix. | ||
|- | |- | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
| − | | 11/ | + | | 11/13 |
| | | | ||
| − | + | * To write LED Matrix driver to derive game visuals along with various colors. | |
| − | * | + | * To finish with the PCB design for our application |
| − | * | + | * To map different orientation values with respect to X, Y and Z axis respectively. |
| − | + | * To develop start screen, score screen and end result screen for the in-game module. | |
| | | | ||
| + | * Successfully able to achieve game visuals on LED Matrix such as ball movement, goalpost location | ||
| + | * Completed start screen, score screen and end result screen for the in-game module. | ||
| + | * Completed PCB design | ||
|- | |- | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
Revision as of 01:51, 18 November 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
1v1 Penalty Shootout
Abstract
This section should be a couple lines to describe what your project does.
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
- Aniket Phatak
- Bhargav Shashidhara Pandit
- Goalkeeper
- 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 |
|
|
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.
