Every project starts with a simple question. For me, it was: how can I build something that moves, thinks, and responds to its environment without constant human control?
This question became the foundation of my thesis — the development of an automated rover powered by microcontrollers, sensors, and real-time decision-making.
As a Computer Engineering student, I wanted a project that would challenge both my hardware and software skills. The idea of creating a rover was exciting, but also unpredictable. It meant dealing with physical components, sensor accuracy, and system integration — things that don't always behave the way code does.
The Build Phase
The rover was designed using Arduino as its core controller, combined with multiple sensors to detect obstacles and navigate its surroundings. I worked on integrating both hardware and software, making sure each component communicated properly with the system.
At this stage, I focused on:
- Sensor integration and calibration
- Motor control and movement logic
- Writing and refining the control algorithms
It wasn't just about making it move - it was about making it move correctly.
Challenges and Debugging
This is where the real learning happened.
The rover didn't work perfectly on the first try - far from it. There were issues with inconsistent sensor readings, delayed responses, and unexpected behavior during navigation.
Instead of seeing these as failures, I treated them as testing opportunities. I:
- Identified bugs through repeated testing
- Adjusted sensor thresholds and logic conditions
- Improved system stability through iteration
This process strengthened my problem-solving skills and gave me hands-on experience in debugging both hardware and software systems.
Results and Outcome
After continuous testing and improvements, the rover was able to:
- Detect obstacles and adjust its path
- Navigate autonomously within its environment
- Maintain stable and responsive behavior
The project became more than just a requirement - it was proof of my ability to build, test, and refine a complete system.
What I Learned
This journey taught me that building a system is not just about writing code or assembling components - it's about understanding how everything works together.
It also reinforced skills that are highly relevant to my career path, especially in quality assurance:
- Systematic testing and validation
- Debugging and issue tracking
- Attention to detail in system behavior
Final Thoughts
Creating this automated rover was one of the most challenging and rewarding experiences in my academic journey. It pushed me beyond theory and into real-world problem solving.
More importantly, it showed me the value of persistence - because in engineering, things rarely work perfectly the first time, and that's where real growth begins.