It could be beneficial to split the robot firmware into an interface/planner and a controller. This would give the user a choice for selecting hardware for budgeting etc.
The interface controller could be an esp32(cam), raspberry pi or jetson nano. It purpose would be taking input and planning trajectories.
The controller could be an esp32, teensy 4.0, stm32 or other. The main purpose would be collection sensor data (uss, button, imu, adc etc), calculate inverse kinematics and updating hardware (servos, led, oled)
It could be beneficial to split the robot firmware into an interface/planner and a controller. This would give the user a choice for selecting hardware for budgeting etc.
The interface controller could be an esp32(cam), raspberry pi or jetson nano. It purpose would be taking input and planning trajectories.
The controller could be an esp32, teensy 4.0, stm32 or other. The main purpose would be collection sensor data (uss, button, imu, adc etc), calculate inverse kinematics and updating hardware (servos, led, oled)