# Title Team Members TA Documents Sponsor
45 Assistive Digital Piano
Anna Shewell
Jae Young Kwak
Shruti Chanumolu
Zipeng Wang appendix
PROBLEM: Learning to play piano over a longer duration can be tedious, boring (for some) and above all very expensive . The average cost of piano lessons is between $15 and $40 for a 30-minute lesson in the United States. However not taking lesson has potential drawbacks as well. For instance wrong fingering, playing too fast or to too slow, no performance evaluation metrics or evaluators to rate your improvement in piano playing, improper key tapping and pressure exerted on keys( affecting and changing the melody of the music) and not practicing enough. In addition it has been commonly found among young children losing motivation to play piano due to either differences with their piano teachers or just not fun to practice piano regularly.

PROPOSAL: With our project, the assistive digital piano, we aim to reduce the requirement for professional guidance in piano learning, at least at the beginner level, and aim to develop methods to make piano practicing more fun for younger kids.

INNOVATIONS: Many learning tools exist as toys for kids to play around with. What will set our project apart is that the keyboard will light up with the correct key to press in the sequence of the song in a specific color, and the player will wear gloves with color coordinated fingers that correspond to the key that is supposed to be played. Otherwise, the sound from the key will not play. Another feature that will make our keyboard unique is that we will use the note, dynamic, and rhythm data of the played song to save the player's performance and create computer visualizations to see whether the player is playing too soft, too loud, or off rhythm (when played alongside a built-in metronome).

SENSORS: --Color Sensor Info(,, ) In addition to the color sensor, we will have shock impact sensors measuring key dynamics. Digital pianos often use velocity measurements to find the speed at which the key is pressed to determine the volume. We will attempt to use both methods.

HARDWARE: To put this piano together, we will have to be cognizant of 1. How each individual key will act as a pressure sensitive switch that produces a signal for the speaker, 2. How each key will use a color sensor to detect which finger is pressing the key, 3. How the circuit will determine, from a file input, which key should be played next by which finger and prevent any other sounds from being played by keys and the song from moving on until those keys have been pressed, and 4. How the data will be recorded.

software part: from the data collected from the hardware part we will design a software to measure the rhythmic accuracy(will use a metronome to determine the speed and beat accuracy) ,errors in key and finger placements and evaluate the learners performance.

Since building a full 88 key digital piano is an extreme endeavor, we will focus on a proof of concept build that consists of just a few fully constructed keys.

Cloud-controlled quadcopter

Anuraag Vankayala, Amrutha Vasili

Cloud-controlled quadcopter

Featured Project


To build a GPS-assisted, cloud-controlled quadcopter, for consumer-friendly aerial photography.


We will be building a quad from the frame up. The four motors will each have electronic speed controllers,to balance and handle control inputs received from an 8-bit microcontroller(AP),required for its flight. The firmware will be tweaked slightly to allow flight modes that our project specifically requires. A companion computer such as the Erle Brain will be connected to the AP and to the cloud(EC2). We will build a codebase for the flight controller to navigate the quad. This would involve sending messages as per the MAVLink spec for sUAS between the companion computer and the AP to poll sensor data , voltage information , etc. The companion computer will also talk to the cloud via a UDP port to receive requests and process them via our code. Users make requests for media capture via a phone app that talks to the cloud via an internet connection.

Why is it worth doing:

There is currently no consumer-friendly solution that provides or lets anyone capture aerial photographs of them/their family/a nearby event via a simple tap on a phone. In fact, present day off-the-shelf alternatives offer relatively expensive solutions that require owning and carrying bulky equipment such as the quads/remotes. Our idea allows for safe and responsible use of drones as our proposed solution is autonomous, has several safety features, is context aware(terrain information , no fly zones , NOTAMs , etc.) and integrates with the federal airspace seamlessly.

End Product:

Quads that are ready for the connected world and are capable to fly autonomously, from the user standpoint, and can perform maneuvers safely with a very simplistic UI for the common user. Specifically, quads which are deployed on user's demand, without the hassle of ownership.

Similar products and comparison:

Current solutions include RTF (ready to fly) quads such as the DJI Phantom and the Kickstarter project, Lily,that are heavily user-dependent or user-centric.The Phantom requires you to carry a bulky remote with multiple antennas. Moreover,the flight radius could be reduced by interference from nearby conditions.Lily requires the user to carry a tracking device on them. You can not have Lily shoot a subject that is not you. Lily can have a maximum altitude of 15 m above you and that is below the tree line,prone to crashes.

Our solution differs in several ways.Our solution intends to be location and/or event-centric. We propose that the users need not own quads and user can capture a moment with a phone.As long as any of the users are in the service area and the weather conditions are permissible, safety and knowledge of controlling the quad are all abstracted. The only question left to the user is what should be in the picture at a given time.

Project Videos