Team Vision for Problem Definition Phase
- Our plan first consisted of examining the existing system and, after speaking with the customer, determining the feasibility of continuing with their existing system.
- In addition to the above, the team wanted to get a more complete and solidly formed list of customer requirements for our iteration.
- From these customer requirements, the team wanted to get a solid draft of preliminary engineering requirements as well.
What did your team actually accomplish during this phase?
- We checked out what the previous team had built and had a meeting with Ron Dufort, our customer, and learned a considerable amount about our goals and clarified customer expectations and requirements.
- We created a good draft of engineering and customer requirements in addition to a preliminary version of a house of quality.
- We assessed our risks and determined actions we would take in order to combat any technical, resource, safety, and social risks.
- We discussed similar products to our projects and created a benchmarking table to compare each product.
- We wrote down a list of tasks for throughout the semester and created a project plan with assigned dates and duration times.
Project SummaryMost piano music requires a performer to use two hands to play a piece, which is an obstacle for amputees or players with physical impairments. Furthermore, duet pieces written for two players are impossible for a single pianist to practice on their own. A previous Senior Design Project implemented a system to assist these players by automatically playing notes on a piano that the pianist cannot play themselves. The system allowed the user to select a MIDI formatted song to play automatically at the same time the pianist was performing. There are no restrictions with playing the piano normally when desired. The previous version has limitations since the device can only play keys in a two-octave range, which severely limits the complexity of songs that can be played. It also lacks the ability to play notes at different volumes, and does not provide feedback about the notes that are played by the human player.
The aim of this project is to expand the device's playing range to all of the piano’s keys and pedals, add support for control of tempo and volume levels, and give the player more control over song playback. Additionally, the project aims to be developed in such a way that it could be expanded later on and have additional features added to it.
Project Goals and Key Deliverables
- Improve upon the previous design and deliver a better prototype that can play upon more of the piano keys in addition to having a better user interface.
- Further the accessibility options of the prototype and potentially improve upon the user interface in regards to providing an easy method for amputees to use the system.
- Retain original functionality of piano in current form.
Customer Requirements (CR)
Engineering Requirements (ER)
Usability Requirements (UR)
Click here to download the requirements document: Requirements Document
- Initial Budget of $500.
- Prototype development - must utilize the current piano and extend to all keys; team's choice to utilize the existing system. There must be no effect on the ability to play the piano as a normal piano. There must be no permanent modification to the piano.
- System size - must fit within upright piano dimensions and not interfere with other components.
- Power - must be able to test system and run final prototype from a single 110V wall outlet.
- 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 - Modified and extended prototype must be complete by Imagine RIT festival in the spring.
House of QualityRequirements Document
Benchmarking TableBenchmarking Document
Project PlanGantt Chart
Group Plans for next phaseIn 3 weeks time we expect to be able to deliver the following:
- Knowledge on piano anatomy and striking mechanism
- Research in solenoids to see if we can add volume changes
- More suitable electronic designs that won't overheat
- Modifications to current mechanical design
- Extended previous CAD designs to include all keys
- Research in sound sensing implementation
- Review requirements with client
- Jared Loewenthal
- Refine power requirements
- Determine possible power supply options to meet power requirements
- Define control interface with microcontroller
- Determine electrical component sizes with ME team members
- Tuyen Nguyen
- Research past team's schematics, and PCB design
- Analyze problems with current electrical design
- Determine how an extension of the current system for actuating all piano keys might be implemented
- Research possible components to use for actuating piano pedals
- Kevin Davison
- Research options for dynamic listening to audio currently playing
- Learn the source code that the previous team had and look for improvements particularly in the UI space
- Work with EEs to learn the electrical system and microcontroller
- Assist MEs if any CE knowledge is necessary
- David Custer
- Investigate whether we have access to the previous teams files for the previous design and base piano in CAD(Solidworks or creo).
- Coordinate with Krisi to design a pedal activation system that can be easily activated using an electrical controls system.
- Coordinate with EE and CE team members to discuss which path for the mechanical design would be best for them.
- Start a CAD design for the keys and pedals(continuing the previous design if we can obtain it).
- Help estimate cost of controls and mechanical design.
- Discuss with team possibilities for additional funding.
- Kristina Hinova
- Learn piano anatomy and striking mechanism
- Brainstorm and design striking mechanism modifications
- Extend CAD designs to include all keys
- Brainstorm and design pedal activation system
- Edward Maskelony
- Study specifics of previous team's system design
- Operate the player piano in its current state
- Research MIDI protocol and software libraries
- Search for inexpensive microcontroller options