• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Subscribers 83 subscribers
  • Views 405 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.

TMS320F280025C: TIDM-02010 over-current issue

Angela Zou
Intellectual 985 points
Part Number: TMS320F280025C
Other Parts Discussed in Thread: TIDM-02010, SYSCONFIG

Dear expert,

My customer use TIDM-02010 to develop HVAC. They are migrating to their own board and facing an issue. Overcurrent is reported when configuring single-shunt for fan and compressor with sysconfig software. Under low-voltage, as long as the PWM enable is set, overcurrent is reported. Please see the figure below:

The configuration file and the chip pin definitions are attached below, please help to check if there is a problem with the configuration. Thank you so much.

 https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/171/tidm_5F00_02010_5F00_f28002x_5F00_rev3p2_5F00_1sc.syscfg

  • 0
    TI__Mastermind 45046 points

    Hi Angela,

    ModuleOverCurrent gets set when the ePWM modules are tripped by some source. Can they verify if a CMPSS output is causing the ePWM trip? They can check the respective COMPSTS registers.

    It looks like they only have CMPSS2 enabled per the sysconfig. However, they've also configured the PFC PWM to be tripped by CMPSS1 (i.e. ePWMXBAR COMP_nFAULT_CMPSS signal).

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 30 points

    Hi Kevin,

      This project is ours. I just successfully applied ID of E2E.In fact the problem is like that:

          We have modified the reference design  by configuring GPIOs /ADC,and adding protection logic again according to customer's hardware design. we connected the external +5V/+15V/+12V to the board.But when we are enabling PFC/Motor1 in BUILD LEVEL 1 we are experiencing module over current fault in PFC/motor 1/MOTOR2. We have not connected motor but just trying to get the PWM signals. We have following COMPSTS registers(1an 2 are same 0x300,cmpss3reg is 0x303）:

    What can be the reason. The hardware modules are completely working fine without any over current. By the way,is there any detailed configured file as to DC motor drive?

  • 0 in reply to frankye
    TI__Mastermind 45046 points

    Hi Frankye,

    frankye said:
    But when we are enabling PFC/Motor1 in BUILD LEVEL 1 we are experiencing module over current fault in PFC/motor 1/MOTOR2. We have not connected motor but just trying to get the PWM signals. We have following COMPSTS registers(1an 2 are same 0x300,cmpss3reg is 0x303）:

    I would recommend trying to understand and fix each of the three over-current conditions one at a time.

    For example, let's focus on MTR1 case first, which is CMPSS1. COMPSTS = 0x300 meaning the low CMPSS1 has latched. If you check the voltage on the respective CMPSS1 signal (A2/C9 pin) with a multi-meter or oscilloscope, what voltage do you see?

    Note that the MTR1_CMPSS_IDC is configured for bi-directional currents (i.e. positive and negative currents).

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 30 points

    I just close CMPSS ENABLE,but got module protect.The INPUTXBAR has INPUT Source as AIO242(Because of hardware design decision).I doult this source is not correct.Maybe it is one of cause?

  • 0 in reply to frankye
    TI__Mastermind 45046 points

    Hi Frankye,

    Yes, this could be a cause. I think you need to add the AIOs like below:

    Then you should see below in INPUTXBAR config:

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Prodigy 30 points

    Hi,thanks a lot. I try as yours advice but get the following compile err(just this change):

  • 0 in reply to frankye
    TI__Mastermind 45046 points

    Hi Frankye,

    Can you see if there are more details about this error in the console or 'problems' dialog box. I'm not familiar with this error.

    Best,

    Kevin