Currently in the motor ESP32 firmware, there's a lot of duplication of everthing to keep the 3 motors split out from each other - things like the motor control and parameters structs. The way we've set things up though, all I2C communication in and out of this is doing all three motors at once anyway, and so the ability to reference them individually is never used. It's currently just adding overhead by turning what could be 1 function call or queue interaction into 3.
Currently in the motor ESP32 firmware, there's a lot of duplication of everthing to keep the 3 motors split out from each other - things like the motor control and parameters structs. The way we've set things up though, all I2C communication in and out of this is doing all three motors at once anyway, and so the ability to reference them individually is never used. It's currently just adding overhead by turning what could be 1 function call or queue interaction into 3.
Currently in the motor ESP32 firmware, there's a lot of duplication of everthing to keep the 3 motors split out from each other - things like the motor control and parameters structs. The way we've set things up though, all I2C communication in and out of this is doing all three motors at once anyway, and so the ability to reference them individually is never used. It's currently just adding overhead by turning what could be 1 function call or queue interaction into 3.
Tried this out, and it actually just made this less consistent and more messy. Reverted.