Week 7: Automating The Code & Moving the Car
Anshul B -
Hello and welcome back to my blog! My name is Anshul, and this week has been about automation in our code and making our car move. We’ve implemented a system to ensure our code is updated on the Raspberry Pi, and we’ve begun writing the control script to interact with the car’s movement.
Creating a CI/CD Pipeline
This week, one of the major developments was setting up a Continuous Integration/Continuous Deployment (CI/CD) pipeline. This system ensures that any changes pushed to our GitHub repository are automatically deployed to the Raspberry Pi without the need for manual updates. With this setup, we can work on debugging our code and testing it in real time. Also, I have included a picture of us creating our CI/CD pipeline on the Raspberry Pi monitor.
Starting the Control Code
We’ve also begun writing a Bash script to control and move the car. The script listens for inputs from a Bluetooth-connected mouse, interpreting specific button presses as movement commands. For example, scrolling up on the mouse could mean turning right, and scrolling down would mean turning left. These commands are sent to the Raspberry Pi, which then communicates with the motor drivers. Then, the motor drivers control the voltage being sent to each motor, effectively moving our car.
Project Progress
This week, my research on the Depth-from-Defocus (DFD) method is coming to an end, meaning we will soon be able to integrate it into our GitHub repository (I have already added the CNN that I built onto our repository). Finally, getting the car to move is a huge milestone for ICON, as it means we can now begin implementing and testing our code. Thank you for reading this week’s blog, and stay tuned for next week’s updates as we continue working on ICON!
Comments:
All viewpoints are welcome but profane, threatening, disrespectful, or harassing comments will not be tolerated and are subject to moderation up to, and including, full deletion.