At the end of part three, we had built our robot from a kit, tested the motors and looked at A a number of sensors. We intentionally kept the choices vague, remembering that robotics is a personal project. You are bringing life to a project that can navigate the world around it. It has a personality created in code, but with a mind of its own at times.
For this part of the build, we are going to have a little fun with our robot. No sensors are required – all we need is an old Android phone or tablet (even some Chromebooks will work) and a little space. We are going to use a free Android app to bring remote control to our robot. Thanks to the newer Raspberry Pi’s Bluetooth capabilities, we can remotely connect and control our robot. In a world where sensors can help a robot navigate its environment, it is informative (and fun) to get hands-on and learn how effective our custom Python robot library is. After this project, you will undoubtedly want to tweak the values stored in your robot.py library, as you will now have a better understanding of what speeds are necessary for different terrains.
The most important thing is that you have some fun with this part!
Blue Dot
Sometimes we need to get handson with a robot. Just like controlling an RC car, we need to get our hands on the controls and take the robot for a spin. So, how
