• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 82 subscribers
  • Views 357 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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-F28379D: Overcurrent trip weird behavior using dual axis motor using FCL reference software

Arun Kumar
Expert 1030 points
Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE, BOOSTXL-3PHGANINV

Hello,

In the dual axis motor using FCL reference software which comes with C2000WARE motor control SDK,Could you please explain the overcurrent setup..

I have disconnected the inverter PCB(BOOSTXL-3PhGaNInv) and manually given some values at the relevant pins to simulate a stable condition(motorVars[1].tripFlagDMC is 0)

  1. I have for now manually given a little over 1.65v to each of the ADC inputs responsible for the current feedback
  2. Around 2v on the ADC input responsible for the VDC bus.
  3. GPIO14 , i.e the OT pin in the inverter schematic to pulled to VCC,3v3.

In the HAL_setupMotorFaultProtection() function I see that for MTR_2,  I see that xbar input is setup with GPIO14 and the various pwm trip zones are set w.r.t to this pin

Now when I disconnect one of the current feedback inputs to the ADC , the system immediately trips (motorVars[1].tripFlagDMC = 1)

Also when I disconnect the VDC bus feedback going to the ADC, it trips with motorVars[1].tripFlagDMC = 2

But when I Ground the GPIO pin(i.e GPIO14 = 0) nothing seems to happen???, isn't the system supposed to trip with motorVars[1].tripFlagDMC = 1?

The error logic is in "runMotorControl(MOTOR_Vars_t *pMotor, HAL_MTR_Handle mtrHandle)".

Could you kindly help with the above.

Thanks

Arun

  • 0
    TI__Guru** 116090 points

    Which build level are you using? Why don't you connect the inverter board for test? 

    GPIO14 is for BOOSTXL-3PhGaNInv on site J5~J8. You should connect the GPIO24 to 3.3V/GND with a 1~2k(OHM) resistor for test.

  • 0 in reply to Yanming Luo
    Expert 1030 points

    Build level 4 (Speed Control)

    As per the pin configuration and the launchpad schematics, We should connect to GPIO24 for the first Motor(MTR_1) and GPIO14 for the second motor(MTR_2) ? Correct me if i am wrong here..

    Currently we are trying this experiment on MTR_2, that is why we were toggling GPIO14..

    if we connect the inverter board (i.e BOOSTXL-3PhGaNInv) to the launchpad we wont be able to set any value to GPIO14/24 as this is given by the inverter.

    We are in the process of developing a high power motor driver using the current launchpad PCB and the same dual axis firmware as a base for the initial development. So we need to check the logic of this particular GPIO to replicate the same functionality.

    By our understanding GPIO14/24 is an active low pin (3v3 = Error, GND = Error), But grounding this pin had no effect...!

  • 0 in reply to Arun Kumar
    TI__Guru** 116090 points

    You are right. GPIO24 for BOOSTXL-3PhGaNInv on site 1, GPIO14 for BOOSTXL-3PhGaNInv on site 2.

    Please take a look at the user's guide of this lab, you need to remove the R20 on both BOOSTXL-3PhGaNInv boards, or disconnect J3-30 and J7-70 pins
    to both BOOSTXL-3PhGaNInv boards.

    Yes. You should pull up these two pins to 3.3V.

  • 0 in reply to Yanming Luo
    Expert 1030 points

    Thanks for the reply Yanming.

    One more thing we noticed today, in build4/build3((Speed and Torque control)) with the original hardware setup using the Launchpad and BOOSTXL-3PhGaNInv , the motor for a very brief moment rotates in the opposite direction before it starts spinning in the intended direction.

    The same behavior is observed after calibration as well. Any suggestion on how to remedy this?   

  • 0 in reply to Arun Kumar
    TI__Guru** 116090 points

    It's normal for using sensorless-FOC or sensored-FOC with incremental encoder. The motor will be forced to the zero angle position with forward or reverse direction for encoder offset calibration every startup since incremental encoder can't provide the rotor initial position.

    You have to do the calibration to run the motor in first time when power on the controller, but you can skip the calibration state when re-start the motor.