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.

TMS320F280049: What's the difference of TZB and DCAEVT1/2 or DCBEVT1/2 in trip zone

Part Number: TMS320F280049

Hi Expert,

There's a confusion about TZB and DCAEVT1 function in TZCTL register.

For example, if there's a DCAEVT1.force event, and force EPWM to a low state. What's the difference between the below two line codes?

When using DCAEVT1 to force ePWMx to low state, Does that mean, 

  1. if only force EPWMxA to low state, just using EPWM_TZ_ACTION_EVENT_DCAEVT1?
  2. if force both EPWMxA and EPWMxB to low state, it should use EPWM_TZ_ACTION_EVENT_TZB?

EPWM_setTripZoneAction(EPWM1_BASE, EPWM_TZ_ACTION_EVENT_TZB, EPWM_TZ_ACTION_LOW);

EPWM_setTripZoneAction(EPWM1_BASE, EPWM_TZ_ACTION_EVENT_DCAEVT1, EPWM_TZ_ACTION_LOW);

Thanks!

Best Regards

Rayna

  • Hi Experts,

    Assuming "TZ1 - TZ6   do not exist",  I thought

     

    1.

    EPWM_setTripZoneAction(EPWM8_BASE, EPWM_TZ_ACTION_EVENT_TZBEPWM_TZ_ACTION_DISABLE);

     

    And

       

    2.

    EPWM_setTripZoneAction(EPWM8_BASE, EPWM_TZ_ACTION_EVENT_DCBEVT1, EPWM_TZ_ACTION_DISABLE);

    EPWM_setTripZoneAction(EPWM8_BASE, EPWM_TZ_ACTION_EVENT_DCBEVT2, EPWM_TZ_ACTION_DISABLE);

    (2 lines).

     

    have the same functionality, but they ended up generating different waveforms in my code …

    Does anybody know the difference between the above (1) and (2)?

    ===================================

    epwm.h has the following lines:

    " EPWM_TZ_ACTION_EVENT_TZB = 2,     //!< TZ1 - TZ6, DCBEVT2, DCBEVT1

    EPWM_TZ_ACTION_EVENT_DCAEVT1 = 4, //!< DCAEVT1 (Digital Compare A event 1) "

    • Does EPWM_TZ_ACTION_EVENT_DCAEVT1 Mean DCAEVT1 occurred?
    • Does EPWM_TZ_ACTION_EVENT_TZA Mean  TZ1 - TZ6, Or DCAEVT2, Or  DCAEVT1 occurred?

  • XIAOQUAN FU said:
    Does anybody know the difference between the above (1) and (2)?

    1=OSHT events, 2=CBC events circuit paths are triggered.

    You have to read x49c technical resource manual (TRM) to understand several possible ePWM xBAR MUX configurations.

  • Hi,

    I am looking into this issue and will get back shortly.

    Thanks

    Vasudha

  • Hi,

    The TRM mentions about the ability of DCAEVT1 & DCBEVT1 events to either directly trip the PWM or provide a one-shot trip event to the module.

    Similarily, DCAEVT2 and DCBEVT2 events can also be configured to either directly trip an EPWM module or provide a cycle by cycle trip event to the EPWM module.

    TRM also mentions the priority of conflicting actions in TZA/ DCAEVT1/DCAEVT2 as shown below:

    I think the TZA/TZB related configuraton would be used in case of direct PWM trip. I will confirm this once with the design team and get back.

    Thanks
    Vasudha

  • Hi Vasudha,

    Thanks for your reply. Hope you could update after check. Thanks!

    Best Regards

    Rayna

  • Hi Vasudha, Rayna, is this closed?

  • Hi Vasudha,

    Is there any update information? Thanks!

    Regards/Rayna

  • Hi Vasudha,

     

    Thanks a lot for your explanations!

     

    What is the difference between “directly trip PWM” and “one-shot trip”? Could you elaborate?

  • Hi,

    If you refer to the TZCTL register, you can see that DCxEVT1/2 have separate trip action configuration,

    You can use that with DCxEVT to cause a trip action directly or configure the DCxEVT as One-shot trip and in that case TZA/TZB trip action will take effect.