Difference between revisions of "F18: Zero Zero UFO"
Proj user12 (talk | contribs) (→Parts List & Cost) |
Proj user12 (talk | contribs) (→Parts List & Cost) |
||
| Line 107: | Line 107: | ||
| $2.95 | | $2.95 | ||
|- | |- | ||
| + | |||
| + | |} | ||
== Design & Implementation == | == Design & Implementation == | ||
Revision as of 01:23, 7 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
Abstract
Bringing a classic game back to life using Embedded Processors and FreeRTOS will help bring a new take to the basic handheld game. We decided to develop the UFO survival game. The objective is to keep the UFO flying for as long as you can whilst avoiding randomly generated obstacles and the other players ufo. The players will control their respective UFOs with the help of the "Accelerometer" sensor present on the SJone board. The ufo can move in either of these directions; Upward, Downward, Forward, Backward , to avoid crashing. The obstacles will move from Right to Left but the Players' UFOs will stay in the field of vision, i.e. they will always be on the screen. The obstacles will have random spacing and random size, testing the users focus. Player who survives longer wins the Game.
Objectives & Introduction
Team Members & Responsibilities
- Neel Patel
- Aman Chandan
- Oliver Zhu
- Himanshu Gunjal
- Pooja Baviskar
Schedule
| Week# | Date | Task | Actual |
|---|---|---|---|
| 1 | 10/16 | Order Components | We will finish ordering all the components required for this. |
| 2 | 10/23 | Interface LCD Display | Finish Displaying the UFO + Start screen. |
| 3 | 10/30 | Move UFO and Wireless Comms | Move UFO in z-axis and beta test Wireless communications (Send a message wirelessly between boards). |
| 4 | 11/6 | Wireless Communication Estd | Send accelerometer coordinates wirelessly. |
| 5 | 11/13 | PCB schematics and Obstacle generation. | Finish PCB schematics and moving randomly generated obstacles from right to left. |
| 6 | 11/20 | Collision Detection and Layout Complete | Finish collision detection algorithm and PCBs should be ordered. |
| 7 | 11/27 | Adding Second Player | Add second player to the screen. |
| 8 | 12/4 | Cosmetic Detailing | Use Cardboards and Stuff to finish the project and make it look like a product.
|
Parts List & Cost
| Sr No# | Part | Price |
|---|---|---|
| 1 | SJOne Board | $80 |
| 2 | 64x64 LED Matrix | $74.95 |
| 3 | Level Shifters | $2.95 |
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.
