What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).
- Fixed Bluetooth processing code to include timestamp for synchronization when processing acceleration and gyroscope data
- Fixed IMU sampling code to resample at 100 Hz for consistency rather than its max (~180 Hz)
- Ported IMU-data-sending code from designated foot wearable MCU to secondary MCU for further development
- Updated documentation to ensure smoother code portability (needed to add the external change for making Bluetooth packets 24 bytes instead of the default 22), reformatted as README in Github
- Added code to connect to both MCUs at the same time (kept code in for receiving data from foot wearable MCU, now can connect to shank wearable IMU to send vibration commands)
- During group meeting with PhD students: Discussed with Vu the details of testing “convergence”, or the number of steps needed to calibrate the FPA algorithm’s step detection mechanism. Currently, we have the number of steps at 8, but I tested in a small room where I would be turning often. Turning introduces error into the FPA algorithm, so we must now test the calibration while walking in a straight line via treadmill.
Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?
Progress is on schedule according to updated Gantt chart for demo.
What deliverables do you hope to complete in the next week?
- Isolate mocap FPA analysis code for mocap testing use
- Create script to port results into CSV for analysis during mocap testing
- Determine calibration time length during mocap testing
- Write scaled vibration command code (that is actually reactive to calculated FPA angle rather than hardcoded)