M5 Wheel / Bala not found in I2C bus?
tuupola last edited by tuupola
How is the M5 Wheel / Balance supposed to work? Do I need to connect it via the Grove interface or are the bottom pogo pins enough? I have attached the wheel to a M5Stack Fire. When scanning the I2C bus only MPU6500 and IP5306 are found.
>>> i2c = I2C(scl=Pin(22), sda=Pin(21), freq=400000) >>> i2c.scan() [104, 117]
If I turn the wheel off the I2C scan times out and triggers the task watchdog. So it seems the wheel is atleast connected to the i2c bus.
>>> i2c.scan() Task watchdog got triggered. The following tasks did not reset the watchdog in time: - mp_task (CPU 1) Tasks currently running: CPU 0: IDLE CPU 1: IDLE
tuupola last edited by
Replying to myself here. Went to eat, came back and 0x56 is found on the bus. Although something weird is going on. Setting motor speed and reading the encoder value works only if also the wheel has USB attached. I guess the unit needs the internal battery to be properly charged to function.
m5-docs last edited by
M5 Wheel of BALA is connected with M5Fire via pogo pin ( gpio21 gpio22 gnd 5v ).
The IIC address of M5 Wheel ( 2-DC-driver module ) is 0x56.