/public/

Subsystem Build & Test

Table of Contents 1 Team Vision for Subsystem Level Build & Test Phase 2 Updated Files 2.1 Bill of Materials 2.2 Engineering Requirements 2.3 Risk Table 2.4 Imagine RIT Poster First Draft 2.5 Imagine RIT Tentative Plan 3 Test Results Summary 3.1 Solenoid Temperature Testing Results 3.2 Transistor Temperature Testing 4 Outputs & Destination 4.1 Final Solenoid Power Schematic 4.2 Timing Diagram for Solenoid Driving 5 Mechanical Updates 5.1 3D Printed Wire Clip 5.2 3D Print Connecting Rod 5.3 Other Updates 6 Risk and Problem Tracking 7 Functional Demo Materials 7.1 Schedule 8 Development of Software Portion 8.1 User Interface and Interaction Design 8.2 Testing Suite 9 Plans for Week 8 Review 10 Individual Plans for Week 8 Review

Team Vision for Subsystem Level Build & Test Phase

During this phase the team was able to:

• Finalize component choices
• Order all needed parts
• Temperature Testing
• Piano Tuning

Updated Files

Bill of Materials

Engineering Requirements

• The team decided that including the pedal actuation and the button feedback would not be within the limits of our budget.

Risk Table

• We had to mitigate the risk of running out of funds by deciding to not implement the feedback and pedal actuation systems.

Imagine RIT Poster First Draft

• This is the general layout for how we imagine how our poster will look.

Imagine RIT Tentative Plan

• Proposal has been submitted to RIT for a location.

• Requested locations include 1st and 2nd floor in Gleason to minimize piano movement.

• Piano will have several pre-loaded songs ready to play at imagine with and without a player (Tim).

• People will be able to play along with piano if they so desire.

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.

• Measured Temperature Curve:

• Theoretical Temperature Curve

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

• Where R is the other resistor in the voltage divider circuit, and V is the cutoff voltage.

Transistor Temperature Testing

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

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

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

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

Used to prevent the rod from sagging when playing notes.

Other Updates

• Assembled array of 24 solenoids on board and mounted it in the piano

• Finalized secure placement of plunger caps to the plungers using screws

• Updated wheel to be symmetrical and added spacer to limit solenoid movement to correct distance

• Changed the sound dampening style to an O-ring inside the solenoid body to dampen where the plunger contacts the body

Risk and Problem Tracking

• The team created a problem tracker to manage all the problems we encounter.

Functional Demo Materials

Schedule

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:

• Usability
• Platform Responsiveness
• Intuition
• Sleek, Flat Design

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.

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.

• Software end-point mimicking the piano
  • Receives requests in the same fashion the piano will be transmitted information.
  • Gives predictable responses depending on the input, given that the input is formatted properly.
  • Has a simple test to check if the endpoint itself is functional.
  • Validates the structure of an incoming request.
  • Validates the specific structure (including notes, pitches, duration) of a sample test song that hits all edge cases

• Testing Suite
  • Can be run with a standalone command away from the rest of the web app.
  • Execution on a test-by-test basis, validating passes in logical order.
  • Takes the same actions the piano system would take, in a repeatable manner.
  • Uses the same software pieces as the piano itself, to validate the inner workings of the piano system.
  • Displays failures and the resultant failure messages to the test executor.
  • Can be executed on production builds, and can create logs

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

• For the next phase the team plans to:
  • Have completed the Raspberry Pi to MSP Communication Code
  • Have complete system installed into piano
  • Have started full system test and troubleshoot
  • Completed Imagine RIT Presentation Plan
  • Completed 2nd Draft of Poster
  • Complete first draft of Technical Paper

Individual Plans for Week 8 Review

Matt Mack

• Continue code development for MSP
• Assist with Controller integration

Ben Parnas

• Finalized 3D printed structures
• Assist code development

Scott Porter

• Finalize power distribution layout
• Assist with system power integration

Tyler LeGacy

• Maintain testing procedure standards
• Continue Hardware/ Electrical Testing

Mike Riola

• Full system integration into piano structure
• Development of 3D printed hardware

Tim Doores

• Song Development
• Poster draft improvement
• Development of 3D printed hardware

Danny Buonocore

• SPI protocol
• Cyber security (SSH, XSS, injection attacks, etc.)
• More generic MIDI splitting

Software Team

• Development of microcontroller system integration with user interface

---

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