Author: jyew

This week, our team has been working on the foot device, visualizations, and algorithm for the back device. We are currently on schedule to be finished by next week. As stated in previous reports, our greatest risks involve the devices not working properly. To mitigate these risks, we have made sure to think carefully about the designs and tested the devices.

In terms of testing, our team has tested both the back device, foot device, and web app. For the back device, we did tests to ensure that the data we received was accurate and also did tests to make sure that the data sent to the web app matched the data sent from the Arduino. Initially, the values we had were different, however after looking over the code, we found and fixed the bug. We also created visualizations for each sensor and verified the results by comparing our generated visualization with our observations. Furthermore, to test the foot device, we placed different weights on the sensors and checked their resistance. While testing, we realized the weight threshold was too low, so we had to increase the resistance.

To test the entire system itself, we plan to wear both foot sensors and make sure that when applying equal or differentiating pressure, the read resistance values are equal to each other. In addition, we will continue testing the back devices and algorithm by wearing the back device and standing in different positions and then verifying the results match the feedback we want.

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.

This week, we primarily worked on the website and getting the Arduino to connect. Since we recently decided to create a web app rather than a mobile app, we’ve had to look at different solutions for connecting our website to the device. One of the biggest risks currently is being able to properly receive large amounts of data sent from the Arduino on the web app. To mitigate these risks, we are looking into solutions where we read data in chunks of bytes. We are currently behind schedule because our parts only arrived this week and due to Rachel’s recent procedure, we have not been able to get as much progress done as planned. However, after shifting some tasks around and changing the amount of time for each, we should still be on time to finish our project by the final presentation.