F18: Hit the Balloon

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

• Aaron Lee
• Rahul Kadam
• Vijay Vanapalli

Schedule

Week#	Date	Task	Actual
1	10/29	Finalize Wiki Scheudle Complete purchase of LED matrix Divide tasks between group members	Wiki scheudle completed LED matrix board purcahase completed
2	11/5	LED matrix display - Power on and display 'Hello World!' Set 4 LEDs to represent bow/arrow on left side of display that can move up and down using two switches Implement single LED that rises from bottom to the top of display (rising balloon)	Power on LED Matrix Display
3	11/12	Implement shooting arrow Randomly generate rising balloons Design PCB Begin implementing hit detection for arrows and balloon
4	11/19	Have a simple working game working with hit detection, arrows, and rising balloons Begin implementation of motion controller Finalize PCB
5	11/26	Finalize implementation of motion controller Integrate Start/End Screen
6	12/3	Add music if time permits Daisy Chain 3 LED Matrix Displays Fix bugs and optimize code Complete 75% of report
7	12/10	Final testing and debugging of system/game using motion controller Complete report and prepare for demo

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

• Sourceforge Source Code Link

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.