My work this past week consisted of helping with the proposal presentation and drafting a prototype + its CAD model. I was responsible for the hardware requirements, specifications, and solutions in the proposal, and helped with edits to the entire presentation in the time leading up to presentation day.
The CAD model is a few days behind schedule according to the roadmap. This is mainly due to me wanting to render the functioning linear actuator/lead screw, rotation motor, and microcontroller. I am still working on this model and have additional free time this week to catch up. The current prototype will be built out of 1-inch T-slot aluminum extrusions (CADing done with parts from 80/20), using an ESP32 dev board capable of operating a motor driver and at least one stepper or servo motor. I am still weighing the pros and cons of a linear actuator vs a manual lead screw, as well as a stepper motor vs a servo motor. The circuit will likely need an external power supply to power any of these motors, since the traces on an ESP32 won’t handle the power necessary to keep the motor powered over an extended period. This should all be resolved and the parts can be ordered by the end of next week. Though this places the hardware behind schedule, I am not worried. Assembly will be simple and can be done the day the parts arrive, and all should be back on track after that; the characterization task that comes after assembly should really only take a day or two, and the programming itself will be simple motor control. There is plenty of slack time in these first few hardware tasks that allow for this setback.
I’ve started on a basic arduino program for controlling the ESP32 and testing the stepper motor system’s accuracy. One of the first things we’ll be testing once we have the ESP32 is our ability to send it commands from our project’s software. If the arduino IDE/language doesn’t work, MicroPython is the next most likely route of hardware programming.