• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 399 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LAUNCHXL-F280049C: with boostxl-drv8320RS -> moduleOvercurrent fault in Lab 02

jgerhardy
Intellectual 485 points
Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: C2000WARE,

Hello,

I am working through the motor control labs in C2000ware motor control SDK using the launchxl-F280049C with the Booslxl-drv8320RS.

The values I see in the ADC registers are double (max value) of what is expected in the lab description and
setting the motorVars.flagEnableSys bit results in an moduleOverCurrent fault.

The demo boards are straight out of the bag with the default jumper settings. The lab suggests
checking for hardware faults in the current and/or voltage sampling circuits, or PWM drive circuit of the inverter.

It is difficult to imagine that brand new demo boards have a HW fault, but I tried with a second set of boards and
have the same result. I have gone through the documents for the  boards and everything seems right.
Have I maybe missed something? Any hints are much appreciated.

Regards,
John

  • 0
    TI__Guru** 114280 points

    You can find a hardware guide about the kits in the folder of motorControlSDK, please follow the guide to make some settings.

    \ti\c2000\C2000Ware_MotorControl_SDK_3_03_00_00\solutions\common\sensorless_foc\docs

    Try to run the lab again without connecting a motor to see what happens, and check if there are PWM outputs on the related pins, and check the voltage  to the ADC on the related pins as well.

  • 0 in reply to Yanming Luo
    Intellectual 485 points

    Hello Yanming,

    Thank you for your suggestions. Reviewing the documents, everything seemed right. However, your suggestion to check the PWM output helped me out. The PWM signals from the mircocontroller were there, but nothing at the gates of the MoSFETs, because the enable signal was missing. This led me to take a closer look at switch S6. After changing the position of S6, things started working.

    Checking the settings for the boostxl in user.h, the defines are like this:

    #define BOOSTX_to_J1_J2     0
    #define BOOSTX_to_J5_J6     1

    #define BOOST_to_LPD        BOOSTX_to_J1_J2
    //#define BOOST_to_LPD        BOOSTX_to_J5_J6

    This is confusing. Why two defines for the same thing? But it seems
    to me that this would be better for the boostxl on site 2:

    #define BOOSTX_to_J1_J2     0
    #define BOOSTX_to_J5_J6     1

    //#define BOOST_to_LPD        BOOSTX_to_J1_J2
    #define BOOST_to_LPD        BOOSTX_to_J5_J6

    Is this the right setting?

    Greetings,

    John

  • +1 in reply to jgerhardy
    TI__Guru** 114280 points
    jgerhardy said:
    Why two defines for the same thing?

    There are two sites for connection the BoosterPak to LaunchXL-F280049C. Using site 1 is the default setting.

    jgerhardy said:
    Is this the right setting?

    Right. It's for installing the BoosterPak on site 2 of LaunchXL-F280049C.

  • 0 in reply to Yanming Luo
    Intellectual 485 points

    Hello Yanming,

    Thank you for the confirmation and your support!

    Best Regards,

    John