Mock Design Review

Description

The Mock Design Review (MDR) is intended to aid your team as it prepares its design document. The MDR focuses narrowly upon providing feedback on the preparation of historically problematic design document elements. If these elements fall short during your Design Review the following week, precious time is lost…. to your detriment.

The MDR provides feedback on your preparation of important design review document elements including, but not limited to:

During the MDR, your team will have approximately 5 minutes to present an example of each of these elements. Expect to share the 30-minute MDR session with 4 to 5 other design teams… and come prepared to learn from their work… both the good and bad.

Your task is to prepare and present an “elevator pitch” of your project (i.e. high-level project description in 2 minutes). Your pitch is your MDR submission and should include samples of each element listed above extracted from your design document draft. During the MDR, speak to your MDR submission, which will be projected for all to see.

This is not a presentation of your design document, which will be substantially longer than the 4 to 6 pages of your MDR submission. Organize your submission in accordance with the design review document guidance and the example design review document. (Your submission should look like a report prepared in MS Word rather than a PowerPoint presentation). During the MDR, make your pitch directly from your submission.

The course staff will focus on providing feedback on the form of the sample MDR elements you present – the very limited available time will not afford detailed feedback on your design.

Requirements and Grading

We are looking for a high-level understanding of your design efforts – substantially via the sample elements (listed above) extracted from your in-progress design document. Upload your MDR submission to your project page on PACE (i.e. ECE 445 web board) before arriving at MDR:

As in your future design document, number pages after the title page in your MDR submission.

Any material obtained from websites, books, journal articles, or other sources not originally generated by the project team must be appropriately attributed with properly cited sources in a standardized style such as IEEE, ACM, APA, or MLA.

The course staff at the MDR will assign individual grades to each student based upon:

Submission and Deadlines

Sign-up for the Mock Design Review on to the ECE 445 course website – specifically at the Sign up for Team Presentation item on the PACE tab. Sign-up will open the Monday one week prior to the MDRs.

Upload your MDR submission (.pdf format) to the ECE 445 course website before your MDR session – specifically at the My Project item on the PACE tab.

While you will not complete peer reviews during the MDR, you are expected to actively contribute to the discussion.

Automatic Piano Tuner

Joseph Babbo, Colin Wallace, Riley Woodson

Automatic Piano Tuner

Featured Project

# Automatic Piano Tuner

Team Members:

- Colin Wallace (colinpw2)

- Riley Woodson (rileycw2)

- Joseph Babbo (jbabbo2)

# Problem

Piano tuning is a time-consuming and expensive process. An average piano tuning will cost in the $100 - $200 range and a piano will have to be retuned multiple times to maintain the correct pitch. Due to the strength required to alter the piano pegs it is also something that is difficult for the less physically able to accomplish.

# Solution

We hope to bring piano tuning to the masses by creating an easy to use product which will be able to automatically tune a piano by giving the key as input alongside playing the key to get the pitch differential and automatically turning the piano pegs until they reach the correct note.

# Solution Components

## Subsystem 1 - Motor Assembly

A standard tuning pin requires 8-14 nm of torque to successfully tune. We will thus need to create a motor assembly that is able to produce enough torque to rotate standard tuning pins.

## Subsystem 2 - Frequency Detector/Tuner

The device will use a microphone to gather audio measurements. Then a microprocessor processes the audio data to detect the pitch and determine the difference from the desired frequency. This can then generate instructions for the motor; direction to turn pegs and amount to turn it by.

## Subsystem 3 - User Interface/Display Panel

A small but intuitive display and button configuration can be used for this device. It will be required for the user to set the key being played using buttons on the device and reading the output of the display. As the device will tune by itself after hearing the tone, all that is required to display is the current key and octave. A couple of buttons will suffice to be able to cycle up and down keys and octaves.

## Subsystem 4 - Replaceable Battery/Power Supply

Every commercial product should use standard replaceable batteries, or provide a way for easy charging. As we want to develop a handheld device, so that the device doesn’t have to drag power wires into the piano, we will need a rechargeable battery pack.

# Criterion For Success

The aim of the Automatic Piano Tuner is to allow the user to automatically tune piano strings based on a key input alongside playing a note. We have several goals to help us meet this aim:

- Measure pitch accurately, test against known good pitches

- Motor generates enough torque to turn the pegs on a piano

- Tuner turns correctly depending on pitch

- Easy tuning of a piano by a single untrained person

Project Videos