S16: Pinball
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.
Pinball
Abstract
For our project, we wanted to design a pinball machine. We wanted to incorporate bumpers, a 7 segment LED display driven by a UART interface for the total points earned, a sound system that would go off after each bumper was hit, and LED's surrounding the machine. In addition, we wanted the user to be able to interact with the machine by turning it on and off with a power button, as well as control the flippers with push buttons that are placed on the sides of the pinball machine.
Objectives & Introduction
Below is a high level list of the minimum functionality features our project will include.
- Launching Pin ball (mechanical)
- Play sound/music when sensors are triggered
- Flipper Controls (mechanical)
- Ball detection sensor
- Score Incrementation as sensors are hit
- Display score on 7-segment display
- Game Over announcement
Team Members & Responsibilities
- Yvonne Jacinto
- Physical Component Design: Building the Pinball Machine container and Designing the layout for the playing field
- Megumi Page
- Power Accountant: Designing power circuit for power supply and tracking watt consumption
- Jo-Anna Marie Reyes
- 7-Segment Display Programmer: Developing the code to display outputs as the State Machine executes
- BJ Wahhab
- Flipper Control/Polling MicroSwitch, State Machine and Software Flow
Schedule
| Week# | Start Date | End Date | Task | Status | Outcome |
|---|---|---|---|---|---|
| 1 | 3/28 | 4/03 | Project Proposal | Submitted | Approved |
| 2 | 4/04 | 4/10 | 1. Component research and initial pinball design 2. Begin component purchasing |
In-progress | |
| 3 | 4/11 | 4/17 | 1. Start of the architectural design 2. Program lights, sounds, and buffers 3. Start mechanical aspects |
||
| 4 | 4/18 | 4/24 | 1. Incorporate bumpers and LED display 2. Make connections and test if certain parts are working |
||
| 5 | 4/25 | 5/01 | 1. Incorporate all components into the designed pinball skeleton 2. Begin component/unit testing 3. Troubleshoot/Debug as needed |
||
| 6 | 5/02 | 5/08 | Product testing and final adjustments | ||
| 7 | 5/09 | 5/15 | Final Product Testing |
Parts List & Cost
| Part | Part Name | Quantity | Cost | Details |
|---|---|---|---|---|
| 1 | SJ One Board | 1 | 80 | |
| 2 | Audio Controller | 1 | 50 | |
| 3 | Power Supply | 1 | 0 | |
| 4 | Pinballs | ~9 | 0 | |
| 5 | Pinball Ball Shooter | 1 | 20 | |
| 6 | Mutli-Colored LEDs | ~20 | 0 | |
| 7 | LED Mixed Pack | ~20 | 0 | |
| 8 | 7-Segment Serial Display (COM-09230) | 3 | 0 | |
| 9 | 3-D Printed Flippers | 2 | 0 | |
| 10 | Jumper Cables | 50+ | 0 | |
| 11 | Speakers | 1 Set | 0 | |
| 12 | Servos | 2 | 0 | |
| 12 | Push Buttons | 2 | 0 | |
| 13 | Wood | 0 |
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.
The hardware design included a battery supply, 3 7-segment serial displays, multiple LEDs, and an audio controller.
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.
Hardware Constraints
- Power Supply: 24V / 2.1A
- Pinball size: 0.5 inch diameter / 8.4-8.5 grams each
- Pinball frame width: 1.5 feet
- Pinball frame length: 2 feet
- Pinball frame height: TBD
- Angle: ~5 degrees inclined
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:
My Issue #1
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.
