This week, I mounted the LEDs onto the enclosure and I focused on integrating the motors yet again. Our breadboard had been damaged due to drawing too much current while powering 6 motors, so following a TA’s recommendation, I began soldering 3 of the 6 motor drivers onto protoboards. I started with 1 reference protoboard, tested it to ensure it worked, and then continued with the rest. Ashira and I collaborated to test each motor driver as she helped solder the remaining 3. We carefully measured each driver’s Vref and confirmed that the motors rotated as expected with the code before soldering the voltage regulator. However, once we soldered a protoboard with 2 motor drivers and connected the necessary grounds and voltage lines onto rails on the voltage regulator, the motors stopped working and our RPi would no longer power on.
Unfortunately, these setbacks have caused my progress to fall behind. I’ve requested a replacement RPi so we can restart our work, but in the meantime, we’ll be borrowing one from Professor Benson, so we can continue testing and hopefully get at least a couple of motors running. At this point, we’re scaling back from attempting to run all 6 motors simultaneously, since every attempt to do so seems to result in some form of failure—either to our components or to our power delivery setup.
Next week, my goals are to complete the final presentation and get our hardware environment stable again. It’s been frustrating to hit so many hardware roadblocks, but I’m hoping we can make meaningful progress before the final demo.
As you’ve designed, implemented and debugged your project, what new tools or new knowledge did you find it necessary to learn to be able to accomplish these tasks? What learning strategies did you use to acquire this new knowledge?
One of the most valuable learning tools for me was video tutorials and community discussion forums, especially the Raspberry Pi Forum. These resources sometimes provided the insight I needed or helped me move our project one step closer to working. In addition, documentation for various components (such as the A4988 motor driver) became a critical resource once I knew how to interpret it properly.
The most important learning strategy I used was refining my research skills. Being able to narrow down what I was looking for—whether it was understanding a motor driver’s pinout or resolving an issue with GPIO behavior—made my problem-solving much more efficient. I also mainly learned by doing: experimenting with the hardware, testing individual components, and learning from trial and error helped solidify the new concepts.