What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?
- The code to process the IMU data includes a filter to smooth out noise (VQF filter). This filter was first planned to be on the smartphone as part of the rest of the pre-processing, but after discussions with Iqui and Dr. Melissa Orta-Martinez from CMU’s Haptics Lab, we realized we may need to move the filtering code onto the wearable device, to increase fidelity.
- The MCU onboard the device is currently single core, and from Iqui’s experience the current VQF library does not work on a single core MCU. We have a dual core one to switch in that still fits within our size constraints as backup.
- We can also sidestep the signal fidelity problem and keep the filter on the smartphone if we are able to send IMU data at a rate above 30 Hz. We will be testing the max rate of information sent through the Bluetooth module on our current MCU as specified in its datasheet.
Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?
Other than moving the filtering code onto the MCU, no other changes have been made.
Provide an updated schedule if changes have occurred.
N/A
This is also the place to put some photos of your progress or to brag about a component you got working.