Does the firmware version 0.5.5 require both axes to respond on SPI before booting? if so can you point me in the right direction of disabling this? Please help. I made a board with the reference design of the Odrive but only with a single axis.
This issue was fixed by rectifying the hardware. It turns out the Power ground and digital ground were isolated which led to the DRV8301 chip not having enough power or any power to turn on.
Once the Power Ground plane and digital ground plane were shorted, the DRV started communicating appropriately.
I have exactly this problem, but with an Official ODRIVE V3.6
In [9]: dump_errors(odrv0)
system: no error
axis0
axis: Error(s):
AxisError.MOTOR_FAILED
motor: Error(s):
MotorError.DRV_FAULT
DRV fault: metadata not loaded
sensorless_estimator: no error
encoder: no error
controller: no error
axis1
axis: Error(s):
AxisError.MOTOR_FAILED
motor: Error(s):
MotorError.DRV_FAULT
DRV fault: metadata not loaded
sensorless_estimator: no error
encoder: no error
controller: no error
It seemed to occur when I was testing out using CAN to communicate between an arduino and the odrive v3.6. I connected the ground of the odrive to the ground of the arduino. Everything seemed to be working fine (i.e. messages going back and forth), then all of a sudden the odrive turned off, and now I only see these errors.