Zhichun’s Status Report for Apr.8

This week I focused on building the circuit on the feet, and I think my progress is on track. This circuit is supposed to be able to detect pressure. Our team chose to accomplish this by building a pressure sensor, and I built a voltage divider with the sensor and a resistor. With the different amounts of pressure, the resistance of the pressure sensor will be changed, and by measuring the voltage in between the pressure sensor and the resistor, I will be able to get the amount of force applied to the pressure sensor.

My contribution to this project is the physical part of the vest and the circuit of the lower pressure system, I will analysts and evaluate them by seeing if they are functional.

For the next week, I plan to implement the code for the pressure sensor with Arduino, and I found an article online explaining a similar subject to this.

https://srituhobby.com/how-the-voltage-sensor-module-works-with-arduino/

Team Status Report for April 1

As stated in the previous status reports, our biggest risks are our algorithm not working correctly and our Bluetooth not communicating correct data. To mitigate these risks, we’ve been doing lots of testing to ensure the data read from our sensors is correct and researching quaternion libraries to help with our algorithms. There have been no changes to our design currently, however, some members seemed to encounter enormous difficulties when completing their tasks, so we are currently behind schedule. In order to account for this, we’ve decided to shorten the number of days allocated for testing, without reducing the total time spent and also re-assign some tasks. By doing this, we hope to still finish on time before the final presentations.

Our updated schedule

Jasmine Yew’s Report for April 1

This week, I primarily researched quaternion libraries and how to use the generated quaternions to generate feedback. I’ve decided to use an external Javascript library called three.js and to generate feedback, I plan to use Three.js to generate the vectors to display on the feedback page. Since it seemed like no progress had been made on the tracking page, I also created an interim tracking page with a basic HTML layout where users choose the exercise they want to perform, then get directed to a new page where they can begin tracking their set or stop tracking their set. I am slightly behind schedule right now because my parts of the project rely on parts that my teammates are still working on and have yet to complete. In order to keep on track, I’ve been using fake data and plan to keep using fake data to test the quaternion generation. By next week, I hope to have the quaternions generated, hopefully using the data received from the sensors.

Sydney’s Status Report for April 1

This week I mainly worked on optimizing our libraries so we could both use the onboard DMP processing to get quaternions as well as the arduino BLE library. This was a real problem as our program as previously written was using 120% of the program memory space. Unfortunately due to problems around that we have yet to fully test the bluetooth integration(but this will hopefully happen tomorrow before the interim demo). But after spending a couple hours better understanding the libraries and removing functionality unused by our application I was able to get our program memory usage down to 99%. This progress is visible on our github. I also worked with Rachel a bit to decide on how to sew the devices together and make sure it matches our vision. We are just barely behind as we were hoping to have the data read to the web server by now, but I think after tomorrow that will be done, and then next week I will dive into working on the foot sensors and assisting Jasmine as needed on getting the detection algorithms working.

Zhichun Zhao’s Weekly Status Reports for Apr.1

This week I focused on the physical level of the project. I designed and built a wearable system with expandable straps and buckles that fit the accelerometers, the Arduino, and the power banks. I used the sewing machine along with the straps that I ordered at the beginning of the semester, but since the machine stopped working after the first 20 minutes of use, I had to sew the sensors on to the bands manually. This made the process more time-consuming and took longer than I expected. Fortunately, I completed the wearable part by the end of the week.

For the next week, I will start focusing on the tracking page as well as the demo with my teammates.