Difference between revisions of "F18: 1v1 Penalty Shootout"
Proj user17 (talk | contribs) (→Schedule) |
Proj user17 (talk | contribs) (→Schedule) |
||
| Line 51: | Line 51: | ||
* Order components | * Order components | ||
* Research on project requirements. | * Research on project requirements. | ||
| − | | | + | | |
|- | |- | ||
! scope="row"| 3 | ! scope="row"| 3 | ||
| Line 58: | Line 58: | ||
* Basic LED display driver to control individual pixels. | * Basic LED display driver to control individual pixels. | ||
* Developing logic for hand gesture control using accelerometer sensor. | * Developing logic for hand gesture control using accelerometer sensor. | ||
| − | | | + | | |
|- | |- | ||
! scope="row"| 4 | ! scope="row"| 4 | ||
| Line 64: | Line 64: | ||
| | | | ||
* Establishing basic wireless communication between two SJ-One boards. | * Establishing basic wireless communication between two SJ-One boards. | ||
| − | | | + | | |
|- | |- | ||
! scope="row"| 5 | ! scope="row"| 5 | ||
| Line 70: | Line 70: | ||
| | | | ||
* Develop game specific API to display on the LED driver. This includes objects such as Goalkeeper and ball. | * Develop game specific API to display on the LED driver. This includes objects such as Goalkeeper and ball. | ||
| − | | | + | | |
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| Line 76: | Line 76: | ||
| | | | ||
* PCB layout design and finalizing the schematic. | * PCB layout design and finalizing the schematic. | ||
| − | | | + | | |
|- | |- | ||
! scope="row"| 7 | ! scope="row"| 7 | ||
| Line 83: | Line 83: | ||
* Developing logic for ball movement and translating hand gesture control into player movements. | * Developing logic for ball movement and translating hand gesture control into player movements. | ||
* Project update report on Wiki. | * Project update report on Wiki. | ||
| − | | | + | | |
|- | |- | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| Line 90: | Line 90: | ||
* Synchronize ball movement and player movement logic into the LED matrix. | * Synchronize ball movement and player movement logic into the LED matrix. | ||
* Soldering components and Hardware testing on PCB. | * Soldering components and Hardware testing on PCB. | ||
| − | | | + | | |
|- | |- | ||
! scope="row"| 8 | ! scope="row"| 8 | ||
| Line 96: | Line 96: | ||
| | | | ||
* Final Testing and bug fixes | * Final Testing and bug fixes | ||
| − | | | + | | |
|} | |} | ||
Revision as of 02:13, 12 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
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.
Team Members & Responsibilities
- Satya Sai Deepak. Naidu
- Aniket Phatak
- Bhargav Shashidhara Pandit
- Harmeen Joshi
- Tahir Rawn
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Week# | Date | Task | Actual |
|---|---|---|---|
| 1 | 10/9 |
|
Completed! |
| 2 | 10/16 |
|
|
| 3 | 10/23 |
|
|
| 4 | 10/30 |
|
|
| 5 | 11/6 |
|
|
| 6 | 11/13 |
|
|
| 7 | 11/20 |
|
|
| 8 | 11/27 |
|
|
| 8 | 12/4 |
|
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.
