Posted on

Team Status Report 4/12/2025

We anticipate there being some friction with integrating the video recording, processing, and bluetooth reading all simultaneously, which may or may not be out of scope depending on the progress of the sensor assembly. Additionally, we have a risk of not being able to save the calibration status of the sensor, which would result in the user having to calibrate the sensor before each lift. However, since the sensor should easily remain on long enough for a whole workout, this wouldn’t be the worst setback since calibrating is quick and easy.

We have not changed our design or schedule.

Posted on

Meadow’s Status Report for 4/12/2025

Since the last status report I’ve worked extensively trying to get calibration to save on the sensor, but due to the lack of documentation it has been difficult to make work. I’ve found a couple resources of claims to have done so, but even running these examples explicitly doesn’t result in a saved calibration. But I will continue to try methods in the coming week in case I can fix the issue. Aside from that, I’ve discussed the physical build of the hardware portion with Jason and we’ve come to a general consensus on it. We’re currently waiting for a key part for that, but after arrival we should be able to go to TechSpark and assemble holdings for the parts on our barbell clip. Finally I started exploring how to transmit our hardware data to the user in a presentable and easy to understand manner. Although we’re using Jamshed’s app for this, I wanted to be able to test ways to display things like balance before integrating it into the app. We were never going to use a full Arduino for the final build and our new ESP32 models arrived (what we will be using), so I got started on the setup between the new ESP32 and the BNO055 sensor using our existing Arduino script in the IDE. In short, I added the ESP32 as a board in Arduino so we can run our script in the same way, just with the right components. There’s an Arduino IO site that I also began setting up so I can try experimenting with sending the data that comes from my script into visual feedback, similarly to how it should be in our app. I think I’m a bit behind on having the sensor features working well enough to be sent directly to the app, but hopefully I can close some of those gaps in the coming week and a half before the final presentation. So, next week I hope to figure out the best way to display balance to users and make sure that Jamshed is able to read the values output by the BNO into his app in the same way we see them printed from my IDE.

Posted on

Jamshed’s Status Report for 4/12/2025

Implemented a Bluetooth Manager with Swift’s CoreBluetooth to send start/stop commands and read dummy data from ESP32. Wrote boilerplate multithreaded firmware for the ESP32 to allow our sensor device to listen for commands from the host iOS device and transmit data simultaneously. Used above firmware and bluetooth manager to create a testbench app using the Charts API to plot dummy data values from ESP32, transmitted over BLE in JSON format.

Wrote a short Python script to experiment with different methods of calculating Mean Concentric Velocity, which will be translated to Swift and run in the iOS app.

Created startup page and home page UI for the iOS app.

My progress is on schedule. Once I ensure that the BLE communication between the sensor and iPhone is robust (which I think it almost is), I plan to integrate it into the RiseVBT main app. I will also try to polish the object tracking feature and integrate it as well, as a separate feature for now.

Posted on

Jason’s Status Report for 4/12/25

This week I spent some time researching how we would like to attach the actual hardware component to the barbell (clips). Although this did not take much time I find it important enough to update that we decided on industrial velcro as a strong enough adhesive to attach our hardware component to the barbell and will use this method unless it appears unfit after further testing. Apart from that, I worked with Jamshed this week for the rest of my time spent on the hardware components this week to properly integrate the data from the IMU with the software iOS platform that Jamshed has been working on. We discussed some protocol that I updated the arduino script based off of and am also working on updating the python script to further support this protocol in which the sensor will wait for a start signal from the software platform to begin transmitting data. Furthermore, Jamshed also mentioned that he wanted me to implement some sort of method of diserning the concentric from the eccentric motion for the plots to be grouped individually based on the sorted data (movement). I will pursue implementing this by monitoring the z-axis and its data from user motion. I hope to have this done by midweek so that Jamshed and I can test these new updates and hope to be further along the integration process. Nonetheless, I think we are on track for the final demo in three weeks or so.