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?
At this point, there are only a couple of aspects our design is missing. The first is the full integration of the BT for the IMU. This should not be a huge blocker anymore. Seaver was attempting to integrate a BT library on MacOS, but we have decided that Linux may be a better option for integrating BT with the OS. MacOS tends to be a bit less lenient on using some of the low level functionality like Bluetooth.
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?
One design change we had to make was the location of the LiDAR sensor. We had to move it to the center of the course in order for it to get a better view of the course. We also have considered adding other restrictions to the length of the course because the LiDAR resolution is not good enough. CJ has discovered that the sensor can sometimes be unreliable, we will attempt to get a percentage this week of how often we can count on its data. Part of the problem is it sometimes just freaks out and loses the location of the ball at seemingly random times.
Provide an updated schedule if changes have occurred.
We are up-to-date with our current schedule.