This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Help debugging a misbehaving DRV8301-HC-EMV board

Hi! I've been working with a DRV8301-HC-EMV with a F28069 Control Card for a few weeks and managed to get my application running after some grief, but now when i try to run it it behaves erratically, out of nowhere. I tried running the original Lab02b example project and it misbehaves too so I conclude something must be wrong with the board. I'd appreciate any help in debugging the problem, I'll write down the symptoms and what i already tried:

When I tried the Lab02b example, it'd start identifying the motor, but in the ES_State_Ls it'll start spinning out of control (it didn't use to do this before). When i try my project (based on the lab12b example) It does the Rs measurement, but when it does it consumes a tremendous amount of current and makes scary noises.


What i tried:

Checked all connections and they are fine, measured the resistance of the motor coils and they are all correct, there's no leakage to the case. Power supply is stable and well connected.

I reseated the control card in the socket, no dice.

  • hard to remotely debug.

    you can attach your user.h file that is being used in the compile project to see if there is an issue.

    also check that your compiler is NOT 6.2.0-6.2.2 (it will not be if you are on CCS v6)
  • Thanks for the reply, here's my config. Please note that the code used to work fine with this config, so it might be a hardware issue, which i don't know where to start diagnosing apart from the connection and voltage checks i already made.

    6518.user.h

  • you are running the interrupt too fast. you have 30 KHz PWM with all TICKS set to (1) meaning the interrupt, controller, and estimator all run at 20 KHz. That is filling up the interrupt of 90 MHz processor.

    try changing this
    #define USER_NUM_PWM_TICKS_PER_ISR_TICK (2)

    nothing else seems out of the ordinary, so if you are still having issues I would suspect HW, especially around the current sense.