The most significant risk is the integration of hardware, mechanical, and software. We weren’t able to fully integrate it all in time for interim demo, focusing instead of finishing critical individual parts. Though it still fits in our timeline, this means that we need to stay extremely on pace till the final presentation. We will first remedy the missing parts we discovered during the implementation process, taking time over carnival to do so, and then we will move forward into the integration and testing process.
For testing, we will be first testing individual processes, running trials on each component (ie. schedule signal generation from software app, sensor detection integrity/accuracy from the circuit’s end, and door opening accuracy for mechanical, etc.). We will be putting all of our individual testing results into a google spreadsheet and calculating the average accuracy. As of right now, the idea is to organize our results into quartiles so we know which aspect to focus debugging/improving first.
Changes made are that we are currently working with a web app for software for now, stepper motor is no longer being used as it is not compatible with the ESP32, additional power sources were needed as the servos drew way too much power for one breadboard supply to handle, and we require more acrylic due to the newer design being larger than expected. These costs are being mitigated by being more cautious with our calculations before implementing them to conserve material (nothing should break).
Our schedule is around the same.