Earlier in the week, our team worked together to plan our slides for the final presentation.
This included adding in some more test metrics that related back to our design and use case requirements, filming demos of subcomponents working together, and explaining what we had accomplished so far and what we still need to work on by the final demo. As a team, we will be spending the rest of the week on integration, final poster, final demo preparation/video, and the final report as well as further testing of the full pipeline as we keep integrating components.
One of the biggest risks we are facing is the delivery of our PCBs. The PCBs have been designed in a way that allows us to mount all of our circuit components, our sensors, our display, and our battery pack into a finished product, and if these PCBs do not come in time, we will need to find another way to accomplish this goal. Our current backup plan is to utilize the larger protoboards that Quinn has ordered for us as our method of printing the PCBs at Techspark led to some issues when it actually came to soldering the components on.
While our unit tests had to do with testing the pathfinding algorithms and, the testing for our other components like fire detection would result in a success if the temperature and smoke sensor hit their threshold markers which were successful. For our LEDs/Display testing, we wanted to ensure that based on commands and paths given as an output from the pathfinding, we can correctly display the directions for all of the unit tests as well as highlight the correct path on the display for all of the unit tests. For the battery circuit, we have tested at the correct voltage necessary to ensure the batteries are recharging to use for our circuit which we got to be 7V. For our communication testing, we tested to see the range in which packets were able to be successfully sent between two ESP32s. We found that there were 0 dropped packets within a 200 ft hallway. With these testing results, we haven’t had to make any major design changes to our project as a lot of our design choices came from previous preliminary testing of designs that led to our designs. Currently, our design is fixed and we are just focusing on integrating the components for the full pipeline.
In the upcoming week, we will all be busy on integration as well as the final deliverables (demo, video, report, poster). We hope to be able to use our PCBs after going through multiple designs for correctness but we want to be prepared with a backup plan. In terms of our Gantt chart, we are behind in terms of the PCBs which we have moved to this week. Other than that, tasks on the schedule for the week are aligned with the final deliverables that we will be working on as well as building our small scale demo and having our demo correspond to this at a smaller scale and doing an entire test in a regular building.