Author: apeprah

Angel’s Status Report for 4/30

Angel’s Status Report for 4/30

This week, I mainly worked on the final presentation, and started testing. I was able to test Bluetooth speed and accuracy for the buttons as well. I also started planning out the demo mode that we are going to show during demos. It will not 

Angel’s Status Report for 4/23

Angel’s Status Report for 4/23

This I worked with Vivian to finalize the controller. We went to techspark and drilled in another hole for the breath control sensor, and I also helped to wire the buttons into the PVC pipe. We were able to fit all of the components into 

Angel’s Status Report for 4/16

Angel’s Status Report for 4/16

This week, I added breath control inputs into the program that plays the flute sounds. Previously, it was only depending on the fingerings. This allows me to test playing different octaves of notes, as well as testing duration/start/stopping of playing those notes. I also started looking into how time the latency of the flow of data, specifically the bluetooth portion, as we have metrics for this. I also talked with Judenique about what format she would like the data in the text file to be in for easier reading from the web application, and changed that in my code as well.

Next week, I plan to help Vivian cut out a portion of the PVC to fit the breath controller, and also work with her for calibrating the different ranges needed on the breath sensor to denote blowing soft, hard, or not hard enough to produce a note. I also plan to continue looking into how to time the bluetooth latency. I started looking into it this week but was not able to find any existing methodology to do so. I know the baud rate that the devices are communicating through, but don’t think that is enough for testing metrics. I also plan to start writing in text needed for the site to flesh it out.

Team Status Report for 4/10

Team Status Report for 4/10

This week, we integrated all three parts of the project so that putting in a correct fingering on the flute controller would display on the webapp after going through the flow of data. We were able to show this functionality in our interim demo, as 

Angel’s Status Report for 4/10

Angel’s Status Report for 4/10

This week I worked with Vivian and Judenique to establish the data flow between the flute controller to the webapp by writing the data sent over Bluetooth to a text file that the web application then reads and displays. I also added gyroscope and breath 

Team Status Report for 4/2

Team Status Report for 4/2

This week, we started integrating Angel’s and Vivian’s portions of the project, and were able to successfully send button data  from the flute controller (that Angel and Vivian created in Techspark this week) and play the corresponding note off of the RPi. The flute controller currently has all 9 buttons on it(which fit snugly).

We did not make any overarching design changes, as we have made progress with the current design.

The most significant risks that we are dealing with is related to integration with the webapp, as we have not been able to do much with it yet and would like to showcase it at our demo on Monday. However, since we have a plan to communicate with the application(writing and reading to a text file), and are meeting tomorrow, we feel confident we can get this portion working in some capacity very soon.

Our schedule is unchanged, we started integration this week and will continue to do so while fixing up our respective systems.

Angel’s Status Report for 4/2

Angel’s Status Report for 4/2

I was able to accomplish a lot this week. First, I updated the python code to decode the bit mapping sent from the Arduino Nano and print of the played the note (C, C#,etc). Secondly, I was able to write code in Sonic Pi to 

Angel’s Status Report for 3/26

Angel’s Status Report for 3/26

This week I worked on sending dummy data and then sending fingerings from buttons over Bluetooth from the Arduino Nano BLE to the Raspberry Pi. I was able to write code on the Nano to create characteristics for the fingering, and then update the value 

Angel’s Status Report for 3/19

Angel’s Status Report for 3/19

Before spring break, I spent most of my time working on the design report. I also ordered an Arduino Nano BLE 33 since I found out that the Bluetooth HM10 Module that I ordered did not work like I thought it did. After spring break, I was able to pick up the Arduino and start working with it. Luckily, I was able to establish a connection between the Arduino using its BLE library and the bluepy library on the Raspberry Pi. On the first day I got it, I was able to read and write between the two devices, and create a new characteristic whose value turned on an LED connected to the Arduino.

Later on in the week, I was able to create more  characteristics and set their values, and read those values from the Pi. I set the values to change every 100 milliseonds, and most values were not dropped when read on the Pi. I plan to look into the Baud Rate of the BLE on the Pi and the Arduino later to see how short I can get the delay to be without dropping significant amounts of data. For next week though, I plan on wiring a small amount of buttons to the Nano to simulate human input that is generally slower than a program to see how that behaves, and start writing code on the Pi to decode the fingering data. The schedule has been pushed back a little (we still have slack to accomodate this), but I feel a lot more confident of hitting our latency goals for wireless communication with the flute controller. Next week,I will also start working with Vivian to construct the flute controller and cut the PVC pipe

Angel’s Status Report for 2/26

Angel’s Status Report for 2/26

This week very frustrating when it came to working on my specific part of the project: Communication between the Arduino Nano and the Raspberry Pi. After working with the HC05 Bluetooth module more, and being unable to get to it to connect to the Pi,