Caption:
Attaching a clear protective box to secure and organize the robot’s wiring system.

Description:
On Thursday, our team focused on strengthening the physical structure of the robot by attaching a clear protective box onto the dog carrier to contain and organize all of the wiring. As we continued developing the robot and adding more electrical components, the wires became increasingly exposed and unorganized, which created risks such as tangling, disconnection, or interference with the robot’s movement. This made it clear that without a proper system to manage and protect the wiring, the overall reliability of the robot would be limited.

To address this, we carefully positioned the wires inside a clear box and used a melted plastic technique to securely attach the box onto the dog carrier. This method allowed us to firmly seal the box in place so it would not shift during movement, while still keeping the structure lightweight and practical. The transparency of the box was an important decision because it allowed us to visually monitor the wiring at all times without needing to open or disturb the setup, which is especially useful when troubleshooting or making adjustments.

While completing this step, we had to think critically about how the wires were arranged inside the box. We made sure they were not bent too sharply or compressed, since that could affect electrical connections or damage the components over time. We also considered how future modifications might be impacted, ensuring that the layout remained accessible enough for us to continue improving the system without having to completely redo the structure.

This process helped us understand that engineering is not just about making individual parts work, but about creating a system where all components function together in a stable and organized way. Even if the coding and sensors are working correctly, a poorly managed physical structure can lead to failure. By taking the time to properly secure and organize the wiring, we improved both the durability and efficiency of the robot.

PLTW Step:
Create and Test because we designed, attached, and evaluated a protective enclosure for the wiring system, ensuring it improved both functionality and stability.

Outcome:
By enclosing the wiring inside a securely attached clear box, our team significantly improved the robot’s organization, safety, and reliability. This step created a stronger and more controlled foundation for future development, allowing us to continue integrating new features without compromising the system’s stability.

Caption:
Finalizing and integrating the complete obstacle avoidance code by combining previously separate programs into one unified system.

Description:
On Wednesday, our team focused on completing the full coding for the obstacle avoidance system, which required us to combine all of our previously separate code segments into one cohesive program. Earlier in the process, we had developed different parts of the code individually, such as sensor input, distance detection, and motor response, but they were not yet functioning together as a single system. This step was important because a robot cannot operate effectively if its components are only working in isolation, everything needs to be integrated so that inputs and outputs flow smoothly.

As we began merging the code, we quickly realized that combining programs is not as simple as copying and pasting. Each section had to be carefully reviewed to ensure there were no conflicts in variable names, timing issues, or logical inconsistencies. We had to think more deeply about how the sequence of operations would affect the robot’s behavior, especially how quickly it should respond when detecting an obstacle. This pushed us to better understand the structure of our code and how small errors could lead to major issues in performance.

During testing, we encountered problems such as delayed reactions and inconsistent movement, which showed us that even if individual parts work correctly, integration can introduce new challenges. We worked through these issues by debugging step by step, adjusting delays, refining conditional statements, and ensuring that sensor data was being processed accurately before triggering movement. This process helped us see coding as a system of logic that must be carefully balanced, rather than just a set of instructions.

By the end of the session, we successfully created a unified program that allowed the robot to detect obstacles and respond in real time without relying on separate code segments. This made the robot’s behavior more efficient and reliable, and it showed us the importance of integration in both programming and engineering as a whole.

PLTW Step:
Create and Test because we developed and integrated the full obstacle avoidance code while continuously testing and debugging to ensure all components worked together correctly.

Outcome:
By completing and combining our code into one unified program, our team transformed separate functions into a fully working obstacle avoidance system. This not only improved the robot’s overall performance but also deepened our understanding of how complex systems require careful integration, logical flow, and continuous refinement to function effectively.