Project

# Title Team Members TA Documents Sponsor
93 Dynamic Violin Fingerboard Attachment
 Adrian Ignaci
Kamil Waz
Sophia Wilhelm
 Manvi Jha proposal1.pdf
# Dynamic Violin Fingerboard Attachment

Team Members:
- Kamil Waz (kwaz2)
- Sophia Wilhelm (sophia16)
- Adrian Ignaci (aigna3)

# Problem

Most people would like to learn an instrument, however not only are the instruments expensive, but the lessons are just as (if not more) costly. This also assumes lessons are even available where they live. For this reason, many people try to teach themselves how to play, either through experimentation or online resources. However, this path has a distinct lack of feedback that would help correct poor habits or otherwise incorrect playing.

# Solution

Our project seeks to give those self-learning an instrument, specifically a violin, an extra source of feedback with respect to finger placement (creating the notes) as well as the rhythm played. A dynamic LED display laid on top of the fingerboard would allow learners to better understand proper finger placement in addition to its relation to the specific note’s duration.
Furthermore, by using linear/membrane potentiometers we could accurately measure the position of a finger placed along any of the 4 paths (strings) on the fingerboard. This allows us to also to also collect information on how accurate the placement is, rather than a simple yes or no as to whether they play the right note.
To encourage building good habits and continuous practice, we would like to allow users to upload pieces they would like to learn. Thus users will be allowed to upload files (MIDI) that can then be used on the fingerboard along with an adjustable tempo. This, paired with individual settings for full piece playthroughs and learning (only playing the next note after the user plays it) will help encourage good, accurate playing whilst making it fun.

# Solution Components

## Fingerboard overlay

This subsystem is the main source of feedback to and from the user. It will contain an array of individually addressable LEDs (1528-1196-ND) which will display appropriate fingerings at the appropriate moment in a piece and membrane potentiometers (SEN-08680) which will give the processor feedback as to the user’s accuracy.

## Microcontroller
The microcontroller will be responsible for a number of key operations, including:
File uploading and reading
Control of the display
User input validation and data collection
We will use the ESP32 (tentative, as using an RP2040 would be easier, but that would also be bulkier and remove a lot of the designing). Additionally, an LCD display (16x2 most likely, no specific part as they’re all pretty generic) can be controlled to display piece statistics to the user.

## Piece Play Configuration
This component controls the aforementioned various settings regarding what style of playing the user wants. Specifically, this will control not only the tempo the pieces are played, but also when the piece progresses. There will be a setting to simply go through the entire piece while tracking statistics in addition to a setting dedicated to learning the piece, which pauses until each fingering is properly performed.
The most straightforward implementation of this (strictly) would only require a potentiometer (COM-09939) or two buttons (such as TS02-66-70-BK-100-LCR-D) for tempo and a switch (OS102011MS2QN1).

##Power
A pair of standard AA batteries should be sufficient for our needs (would need the 36-2463-ND enclosure to hold them).
However we would like to consider 3.7 V Lithium-Ion Battery Rechargeable (1528-1839-ND) with the associated charger (TI BQ24074) and regulator (TI TPS62840). The rechargeable battery is a potentially dangerous option as it could endanger the instrument itself (it’s a more risky fire hazard than an easily removable AA battery), therefore it will not be implemented unless there has been extensive testing of the rest of the system within the time frame of this project.

##Case/Enclosure
There will be two parts, one for the fingerboard components and one for everything else.
The fingerboard overlay will consist of the components surrounded by a sort of envelope made of ~0.3mm transparent silicon rubber (allowing for clarity for the LEDs without compromising the membrane potentiometers).
The second part will be a plastic enclosure that must fit either under the fingerboard or body (better for weight distribution) of a full size violin without significant weight. It will contain the power supply, microcontroller, and configuration modules.

# Criterion For Success

Unit is easy to attach to a standard violin. The attachment must accurately display and detect note fingerings from a user specified piece at an adjustable tempo. User accuracy will be displayed real-time through use of LEDs on the microcontroller, and an accuracy summary will be displayed at the end of the piece. In addition (though less quantifiable), it must not impede the physical way a user must play the instrument.

Note on expertise: Kamil plays violin and knows a number of other violinists. They will be consulted on the physical design.

Cloud-controlled quadcopter

Anuraag Vankayala, Amrutha Vasili

Cloud-controlled quadcopter

Featured Project

Idea:

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

Design/Build:

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