• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 84 subscribers
  • Views 997 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.

TMS320F28069F: Lab11e for TMS32F28069F PWM stop after fault

Joshua Pauls
Prodigy 10 points
Part Number: TMS320F28069F
Other Parts Discussed in Thread: CONTROLSUITE

Hello,

Regarding Lab11e for TMS32F28069F.

Description:

Currently Lab9a is being used. The most significant change implemented was related to error handling.
If the bridge driver DRVxxxx shows a fault, we configure the Trip Zone to single shot -> if the DRVxxxx shows an error, Trip Zone disables the PWM signals to the bridge and the motor stands still.

File "hal.c" Function "HAL_setupFaults" and here line "PWM_enableTripZoneSrc(obj->pwmHandle[cnt],PWM_TripZoneSrc_OneShot_TZ3_NOT)"

Now Lab11e is being used. The same change to single shot is done, but now when the software runs in "HALLBLDC",  the error in the Trip Zone is immediately cleared and the HALLBLDC algorithm will drive the motor current again, so the motor begins to spinning.

Question 1) How can I stop the PWM immediately in such an error case?

Question 2) Why is the program construction changed from Lab 9a to 11e and when is lab 11e as fpu32 available?

Thank for your support.

  • 0
    TI__Guru** 119450 points

    2) there are several threads on this topic, here is one that was still on the first page

    Essentially for proj_lab11+ we made the software simpler by in-lining all the control functions instead of having them obfuscated in CTRL.  This makes it more obvious exactly what is occurring. Customers familiar with our controlSUITE style of projects prefer this method. The downside is that you lose some functionality (motor ID, state machines, etc.).

    It is up to you to decide which software makes the most sense for your application. Most customers seem to build off of proj_lab05 or 10 though.

    For 1) I'll let Yanming or Sean answer.

  • 0 in reply to ChrisClearman
    TI__Guru** 115420 points
    For Q-1), You can keep this one shot fault trip of TZx from DRVx. HALLBLDC used the trip-zone force register to set pwm output which didn't block other h/w TZ inputs to implement fault protection, there is no conflict with h/w fault protection from other TZx.