Introduction
This week’s assignment was focused on networks and communication: design, build, and connect wired or wireless nodes, each with an address (through a network or bus protocol), and paired with at least one local input and/or output device. The goal is to go beyond standalone boards and start creating systems that actually communicate.
At the same time, next week’s assignment is to write an application that interfaces a user with an input or output device that I have made - adding a software layer that lets a human interact with the hardware.
Since I’ve been sick these past days, and because I’ve been working a lot on my final project (with many updates coming on that front), I decided to approach this week and next week as a bundle. Instead of two separate assignments, I’m building one joint project that satisfies both the networking/communication requirements and the user-application component.
Understanding the Next Steps
For my final project, I’m building a combat robot. To make it competition-ready, I originally relied on specialized combat robotics parts-motors, ESCs, a commercial receiver-all purchased from dedicated robotics websites. I wired and soldered everything so the bot could move and spin its weapon.
However, since I was sick, missed last week’s class, and-let’s be honest-I’m not an engineer, I didn’t really know how to tackle this week’s assignment. So on Friday afternoon, I set up a Zoom call with Anthony, explained where I currently was in the project, and asked for guidance.
As he looked at the requirements for this week and next, he immediately saw an opportunity to do something integrated. Instead of continuing to rely on the commercial receiver, he suggested that I design my own PCB that can act as the robot’s receiver. This would replace the store-bought unit and become the perfect bridge between both assignments: a communication-focused board for this week and a user-interfacing component for next week.
We ended the Friday call aligned that on Monday we would go deeper and outline a concrete path forward.
On Monday, I met with Anthony again. He was, once again, extremely helpful (another big shout-out). He walked me through how the receiver communication system works-especially the PWM signaling the commercial receiver currently sends to the ESCs.
He then recommended designing a new PCB around the ESP32-S3 microcontroller, which offers strong wireless communication capabilities and can generate the PWM outputs needed for the left motor, right motor, and weapon motor.
Here the next steps:
- Test the existing components to confirm everything still works
- Start the PCB design, considering physical layout constraints
- Review the design before manufacturing
- Fabricate the board
- Solder, program, and test the final version
Final Project
Please note that the final project includes a detailed walkthrough of how the combat robot was connected to a PS5 controller. The robot creates its own Wi-Fi network, which the computer connects to. At the same time, the computer pairs with the PS5 controller via Bluetooth. Controller inputs are then read on the computer using Python and transmitted to the robot, where Arduino code converts them into motor commands. The full setup, code, and communication flow are documented step by step on the final project page.