Persistent CURRENT_LIMIT_VIOLATION Error

Hi,

We are getting a persistent error which we can’t get to the bottom of.

Our setup:

  1. 3 micros with FW V0.6.12-1 being controlled by an MCU over CAN.
  2. The motors are 80W each with hall sensors.
  3. We have got them setup and calibrated OK.
  4. We have robust comms getting feedback data.
  5. We are running them in velocity mode and getting the motors running up to max RPM with the tune we initially got from running through the GUI. Although we do need velocity gain scheduling in order to keep the response sharp and reach all desired RPM.
  6. For this test we have set the soft current limit to 20A to gives us a lot of headroom.
  7. We have used various power supplies but the error still occurs with the overkill supply: 24V, 67A.
  8. All 3 motors are attached to a gearbox, one of the 3 is then driving a track belt.
  9. In initial testing using a USB, the ramp rate could be set to 100turn/s2 with the track belt with only occasional errors. When testing using the GUI, the minimum stable RPM is ~1100RPM. For testing we have automated a ramp up and down, the CAN controller FW is set to use a minimum RPM of 1300RPM, at a rate of 100RPM every 100ms.

Our issue:

  1. We are seeing a consistent current limit violation error (0x1000) from all 3 motors when reading the disarm_reason error. This doesn’t seem to be happening at a particular point in the motors ramp up or down and sometimes occurs when the motor is stationary and the commanded RPM is 0, we have a test log if that is helpful. When this error occurs, the MCU attempts to recover the drives by commanding them into closed loop mode but that doesn’t work more often than it does. When I manually command the MCU to put the drives into closed loop it works everytime unless in the state outlined in the point below.
  2. Less frequently the drives are ending up in, what I think is, idle with a blue LED but could be uninitialised state with a teal LED. This happens after error 0x1000 but not everytime, it does not produce an error after the 0x1000 has been cleared. When trying to put the driver into closed loop it does not read back an error and once attempted to put it into closed loop there is an error with a red LED, it fails to enter closed loop and then immediately after produces a velocity limit violation error (0x8000), which I can clear but that does not allow it to enter closed loop. I have tried to reboot the drives with Odrive.reset(ODriveCAN::ResetAction::Reboot) and that still does not allow to enter closed loop but not convinced I am actually rebooting. The only way to clear the error is with a power cycle.
  3. This seems harmless but might provide information. 1 of the drives produces the spurious error 0x24001954 frequently but doesn’t seem to affect the drive - does not put it into idle and continues to function as normal.

My understanding is that the current limit violation error should occur when the hard current limit is exceeded, the inverter limit is exceeded or the current control bandwidth causes it to be unstable. Having set the soft current limit to 20A, I believe that is never being exceeded even when derated because of a input voltage droop. The inverter limit is hard set at 7.9A and should never be exceeded under these conditions as should not exceed more than 3A pk/phase. The control bandwidth is set during calibration and requires no further config.

Has anyone else seen something like this with Micro drives? Could any one of the above parameters be violated if the tune is not quite right? I was thinking it would not as it would fail quickly and sometime the motors can ramp for minutes without throwing the error. Also it would not occur when the motor is at rest and not being commanded to change velocity.

Any info or things to try would be appreciated.

Patrick