P17363: Player Piano
/public/

Subsystem Build & Test

Table of Contents

Team Vision for Subsystem Level Build & Test Phase

During this phase the team was able to:

Updated Files

Bill of Materials

public/MSD2 Documents/BOM.JPG

Engineering Requirements

public/MSD2 Documents/Eng Requirements.JPG

Risk Table

public/MSD2 Documents/Risk Table.JPG

Imagine RIT Poster First Draft

public/MSD2 Documents/Poster Draft.JPG

Imagine RIT Tentative Plan

Test Results Summary

Solenoid Temperature Testing Results

The team compared the expected and the actual results of measuring the temperature curve of the thermistor when attached to the solenoid.

public/MSD2 Documents/TempDataMeas.JPG

public/MSD2 Documents/TheoreticalTemp.JPG

With this data the team now knows that the formula for the temperature cutoff is found with this equation:

public/MSD2 Documents/Therm Voltage Eq.JPG

Transistor Temperature Testing

public/MSD2 Documents/Transistor Temp Profiles.JPG
The transistors being used in the final design were evaluated to establish how long a note could be played continuously before it overheated. With this testing the team knows that the longest note the piano can play is 24 seconds. This means we will be able to play any long note we come across.

Outputs & Destination

  1. Test Results
  2. System integration

Final Solenoid Power Schematic

public/MSD2 Documents/Final Solenoid Schematic.JPG

This schematic eliminates the buzz from the PWM signal going into the solenoid. This completely mitigates one of the biggest risks of the design.

Timing Diagram for Solenoid Driving

public/MSD2 Documents/Timing.JPG

This is how the timing works for the PWM. The value that controls when the output changes, TACCRx is modified to fit the loudness of the note for a stronger solenoid pull. The duty cycle of the pulses is found by using the formula:

(TACCR0-TACCRx)/(TACCR0)= 100*duty cycle

Mechanical Updates

3D Printed Wire Clip

public/MSD2 Documents/WireClip.JPG

This clip is what connects the beading wire to the key stud removing the need to tie the wire directly to the piano, reducing install time.

3D Print Connecting Rod

public/MSD2 Documents/ConnectingRod.JPG
Used to prevent the rod from sagging when playing notes.

Other Updates

Risk and Problem Tracking

public/MSD2 Documents/Problem Tracker.JPG

Functional Demo Materials

Schedule

public/MSD2 Documents/Week8Plan.JPG pdf

Development of Software Portion

The team has made a lot of progress on the software portion of the piano project, namely with the UI and with the development of an effective testing suite.

User Interface and Interaction Design

A modular user-interface was designed for the player piano, mainly focusing on:

After a cycle of bench-marking similar controller-centric designs, it was decided that a very minimalist flat design would be used, with big text and as little instruction as possible. This abides by a lot of the design best practices, and allows users to take actions with the path of true least resistance.

One of the major benefits of the application is the fact that the tablet and touch-input friend design allows for both toddlers and elders with deteriorating eyesight to take actions easily. This is accomplished without jeopardizing either the software integrity of the design and while keeping it easily usable and non-constricting for adults.

public/MSD2 Documents/UI capture.PNG

The UI design colors are still up to be changed easily, but right now these colors are present to be welcoming and friendly to toddlers who may come to the booth at imagine RIT.

Testing Suite

On top of the UI design that was worked on, the software developers focused on developing a strong testing suite so that future actions are easily validated. This was completed by developing two main pieces to the tests, the end-point and the test listing itself.

All the facets of the suite are not done yet, but the structure and basics to the system are already in place. The tests themselves have not been run (with real data) yet, due to the fact the communication protocol has not been set. It does not make sense to write tests that will be subject to change soon.

Plans for Week 8 Review

Individual Plans for Week 8 Review

Matt Mack

Ben Parnas

Scott Porter

Tyler LeGacy

Mike Riola

Tim Doores

Danny Buonocore

Software Team


Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Integrated System Build & Test with Customer Demo | Customer Handoff & Final Project Documentation