ERROR_DRV_FAULT Motor cannot start

Owen · April 20, 2018, 3:46am

I still don’t have a successful starter motor. It’s really discouraging for me! When I set my_odrive.axisN.config.enable_control and my_odrive.axisN.config.do_calibration parameters according to the operator’s manual the output is displayed without this parameter.Then I checked the low_level.c file and found that “.enable_control” and “.do_calibration” were blocked. When I followed the instructions and entered my_odrive.motor0.encoder.pll_pos and my_odrive.motor0.pos_setpoint = 10000, the motor did not move, I can turn the motor by hand.
start

Then when I enter my_odrive.motor0.error and my_odrive.motor1.error both show error 20 (ERROR_DRV_FAULT). When I run python demo.py.
py2

But the motor has not moved. In fact, I did not insert the motor and encoder on M1. The board is v3.4 ，the ARM chip is hotter than the DRV8301, but it can flash normally. I don’t know where the problem is.

madcowswe · April 20, 2018, 4:54am

Hi, I’m sorry getting started is being frustrating for you. Just to help me understand, when you say:

I’m not sure what you mean.

Actually that’s not a problem, this is actually because these parameters moved to axis.h/cpp. However it is true that until firmware v0.4.0 we can’t actually disable/enable the axis at runtime, it has to be through the config and then reboot. Though both are enabled by default, so you shouldn’t need to change it.

It seems your actual issue is that you are getting error 20: DRV_FAULT. To help you with that, can I ask you: What is your ODrive version v3.4 24V, or v3.4 48V? What voltage is your power supply? What are your motors?

Cheers

Owen · April 20, 2018, 5:24am

Hi, I’m sorry I didn’t say it clearly; my ODrive version is v3.4 48V, but I use 24V and I use the mos tube is NTMFS4935NT1G. The motor is a hub motor with a maximum operating current of approximately 10A

madcowswe · April 20, 2018, 5:28am

Sorry that doesn’t make sense to me: the 48V versions of ODrive have NTMFS5C628NLT, and the 24V version has NTMFS4935NT. Or did you make your own?

Owen · April 20, 2018, 5:59am

Yes, I did it myself; I saw it before, it seems that the 48V and 24V versions only differ in the mos tube. So I configure CONFIG_BOARD_VERSION=v3.4-24V. use NTMFS4935NT

madcowswe · April 20, 2018, 6:03am

Which commit did you base the design on? What values do you get for:

my_odrive.motor0.gate_driver.drv_fault
my_odrive.motor1.gate_driver.drv_fault

Owen · April 20, 2018, 6:07am

I want to make a mobile chassis for my robot, and then add navigation.The output is 0

madcowswe · April 20, 2018, 6:15am

What I mean is which commit did you base it on?

Okay, in that case I can suggest these mods.

Owen · April 20, 2018, 6:43am

Oh, sorry,forgive me poor English,it should be January 26. I have already done this but still have this error.

madcowswe · April 20, 2018, 6:50am

In that case I would recommend that you invest in a ODrive v3.5, we have confirmed no DRV_FAULT in our testing up to simultaneous 80A on both axis.

Owen · April 26, 2018, 6:31am

Hi,madcowswe! Thank you for your help, I will consider your opinion. Before that, I still wanted to find out why this kind of error occurred. Is it related to the chip itself?

madcowswe · April 26, 2018, 6:34am

The reason is because there is unstable voltages on the board and the DRV chip has problems.

Owen · April 26, 2018, 8:10am

Hi, madcowswe! good news. I just replaced the DRV chip and the FAULT error disappeared. the motor turns after power up.

itisieric · July 14, 2020, 7:19am

How do I reset this error?
I have a 56v 3.6