Project Reflection

Team Reflection

Working on this project gave our team a clearer understanding of how independent embedded systems can be combined into a single functioning device. At the start, each subsystem felt separate, with its own goals and constraints, but as the project progressed we had to learn how to coordinate hardware, timing, and communication so the rover behaved like one system instead of four disconnected pieces. This required more planning and communication than we expected, especially when defining message formats, debugging wireless communication, and making sure each subsystem responded correctly to commands.

One of the biggest lessons came from testing. Many issues only appeared once the subsystems were connected, and this forced us to rethink parts of our design. We learned the value of having clear debugging tools, consistent message structures, and predictable subsystem behavior. These challenges helped us understand why real engineering projects rely so heavily on documentation, version control, and communication between team members.

Another important takeaway was how much the physical design affects the electronics. Noise from motors, wiring layout, and power distribution all influenced how well the subsystems worked. This pushed us to think beyond just code and sensors and consider the rover as a complete system. It also showed us how important it is to design with reliability and testing in mind from the beginning.

Overall, the project helped us grow as engineers by giving us hands‑on experience with system integration, communication protocols, and collaborative problem‑solving. We finished with a better understanding of how to design embedded systems that are not only functional but also maintainable, testable, and ready for future improvements.