Team Vision for Problem Definition Phase
- During this phase we planned to communicate with the customer to discover the most ideal outcome from this thirty week endeavor and correlate that to customer requirements, engineering requirements, and constraints.
- We utilized budget information and approximations on time restraints to generate a scope of engineering requirements that is achievable while still satisfying the customer completely.
Project SummaryMechanical player pianos have existed since the late 19th century for entertainment and teaching purposes, with the innovation of the electric player piano debuting in the 20th century. Both, unfortunately, have a distinct ineptitude interacting with a human performer. Some costly programs exist today that allows for the performer to play one of the two clefs but the temp is set and determined by a defined beat per minute value beforehand.
The goals of this project are to retrofit a modern acoustic piano to act as a player piano with the added capability of performing a duet with a human performer who is setting the tempo. Storing songs, transferring data, and an intuitive user interface will also be added challenges to this project. The expected result is a marketable prototype that can be installed in a modern standard piano for the purposes as a teaching aid, entertainment, and to allow handicapped pianist play pieces they once thought impossible.
BenchmarkingDevices on the market that we can compare to our design.
- Piano Disc iQ link $6500-$10000
- Disklavier E3 link ~$27400
- PNOmation link $2400
- Synthesia link Needs keyboard with MIDI input and a computer.
Above products lack duet abilities, require smart devices, don’t control foot pedals, and can’t provide accessibility technology which are all goals for our device.
Project Goals and Key DeliverablesExpected end result of the project, what the customer can expect to receive at the end of the project.
- Working prototype that can play a digitally loaded complex song alone that controls dynamics with a simple user interface.
- Provide a system that can potentially play any song including a duet with a human counterpart who may be disabled.
- Retain original functionality of piano in current form.
Customer Requirements (Needs)
Link to Excel File
Engineering Requirements (Metrics & Specifications)
Link to Excel File
- Initial Budget of $500
- Prototype development - must be able to interface with piano available on-hand.
- System size - must fit within upright piano dimensions and not interfere with other components (dimensions TBD)
- Power - must be able to test system and run final prototype from a single 110V wall outlet.
- Manpower - components must be created and/or ordered by members of team.
- Space - limited to space being reserved in Senior Design Lab (pending approval)
- Tone - must not distort the tonal response of the piano in any way (customer requirement), and allow access for a professional tuner to tune the piano
- Time - initial prototype must be complete by Imagine RIT festival (5/6/2016).
- COTS items - all electromechanical items (actuators, motors, etc) must be COTS and not custom-built.
Link to Excel File
Link to Excel File
House of Quality
Outputs and DestinationProvide input to the risk management process. This table highlights the give and take of certain requirements with others. For example how keeping costs down is at odds with number of keys automated, because the more keys we automate the more the system will cost.
Design Review Materials
Customer Requirements File
Group Plans for next phaseIn 3 weeks time we expect as a team to be able to deliver in our review:
- A functional decomposition of our proposed piano playing device.
- Benchmarking against potential competitors to our devices or devices we can draw inspiration from.
- Concept development, we will have ideas of how to do better than the benchmarks.
- Feasibility, we will have an understanding of the list of features that we can implement in our device with the given constraints, hopefully all of them.
- Morphological Chart and Concept Selection, we will have multiple options to solve some of the problems we face in design and we will ask for input on those options.
- System architecture, we will have a layout of the entire system and subsystems and how they interact.
- Design flowcharts, we will have a graphical depiction of the system in use to help convey the behavior of the device.
- Michael Riola
- CAD Piano: First thing to do ~3 hours
- Help test solenoid: ~2 hours
- Choose solenoid that fits: ~1 hour
- Ensure that it works: ~1 hour
- Work with electrical to see what space they need: ~1 hour
- Tim Doores
- Calculate specs for solenoids - 2 hrs
- Brainstorm design ideas - 1 hr
- Test solenoid specifications - 2 hrs
- Keep track of finances and materials purchased - 1 hr
- Assist EE's in their steps for next phase - 1 hr
- Danny Buonocore
- Research which microprocessor best suits the engineering requirements - 1 hr
- Assist in analyzing the previous team's system - 3 hrs
- Plan and design the IO system - 2 hrs
- Determine best communication protocol for microprocessor and individual controllers - 1 hr
- Samraaj Bath
- Work through customer requirements to determine a draft technical spec for the user interface - 2 hrs
- Assist with testing of solenoids and breakddown of previous team's system - 2-4 hrs
- Discuss and analyze findings of testing with team to determine if solenoids will be used or other actuators explored - 2 hrs
- Research usage of microcontrollers in consideration and determine what will be used - 1 hr
- Research methods by which to display data to the user - 1 hr
- Matt Mack
- Continue to breakdown previous groups solution attempt - Ongoing
- Test existing servos to ensure functionality - 2-4 hrs
- Help finalize an electrical subsystem design. - 5 hrs
- Update risks with more detailed information. - 2 hrs
- Ensure all documentatino is updated as time goes by. - 3 hrs
- Scott Porter
- Determine feasibility of Pulse Width Modulation for Solenoids - 2 days
- Research methods to determine best way to tell if note has been played - 1 day
- Update edge with any potential risks found - 1 hr
- Research best microcontroller(s) to use for striking notes - 1 day
- Determine best way to interface electro-mechanical devices with user interface - 1 day
- Ben Parnas
- Tyler LeGacy
- Assist with breakdown of previous teams system - 2-4 hrs
- Research more methods to electro-mechanically play piano - 1-2 hrs
- Help benchmark options for actuators 2-4 hrs
- Help design functional flowchart of device 1-3 hrs
- Update edge with any potential risks found 1 hr