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.

TMDSCNCD28379D: Bus imbalance and overcurrent trips

Part Number: TMDSCNCD28379D
Other Parts Discussed in Thread: TIDM-1000,

Hello, 

We currently have a TIDM-1000 Vienna circuit evaluation module that we have been able to run up to its rated 2400W in all 4 builds. Our project consists of ramping up the power of this Vienna circuit to 32KW. We have been working on this for a little over a year and can get 2500W out before we begin to suffer bus imbalance and over-current trips on our custom circuit. 

Essentially we duplicated the low-power components and translated the signal levels of the evaluation board while replacing the high power components with much higher power components and heat sinking ie. mosfets, capacitors, inductors, etc. 

The 3mH (eval) inductors were replaced with 0.6mH 16KVA inductors. You can see them at the top of the picture. Our bus capacitors are film went from 180uF (eval) to 580uF. We went to the MSC40SM120JCU3 FET and higher rated SiC diodes. All devices should run 50Khz easily. calculation.xlsx shows these values to be ok. 

One other thing we had to update were the hall effect sensors. We needed more range so we are using the L03S100D15. We are compensating for the hall effect offset to generate identical signals as the Eval board. 

For the most part all of the low power components are identical to the ones used on the eval board. 

We are running by slowly ramping up the input voltage, we don't get very far until we suffer bus imbalances and overcurrent trips. 

What we would like is if TI had any kid of on-site services that we could contrac tto come out for a day or so and review our setup and help us out a bit. There seems to be too much going on here to solve on a forum such a this. 

That being said, I can answer any questions you may have about our setup, even providing schematics if applicable. We have been trying to get this circuit to work for some time. 

Sometimes too much information is a bad thing so I will end this here for now. 

Let me know your thoughts. I look forward to hearing them. 

-Chris Yeckel 

Chief Engineer Stangenes Industries

  • Hi Chris,

    I will get back to you tomorrow.

    Regards,

    Chen

  • Hi Chris,

    Unfortunately we are not able to do the onsite support. This is actually a scaling problem. Usually we only support the questions related to the reference design based on the original spec. 

    It is hard to give suggestions based on the info you gave. Other than the power level change, what else have been changed in terms of spec?  for example, AC input freq? ISR freq? 

    Regards,

    Chen

  • That is all you need to know? AC input frequency? The input frequency is 60hz and switching frequency is 50Khz. We have not changed this. I was told i would be contacted by a specialist? Are you that specialist? I tried to ask simple questions on this forum several months ago, got incorrect answers. I am trying yet again, as this is the only avenue available to me to ask questions on TI products. The simple question I asked several months ago is... "what diagnostic, or input to the TMDSCNCD28379D generates the "overcurrent trip" in the software. Currently we are running build 1, which does not try to regulate, just runs the mosfets at 50% duty, and we have disconnected all diagnostics (shunt resistors, hall effect sensors, VBUS voltage sensors) and we still get overcurrent trips in the software? What can possibly cause this? There is nothing in the documentation describing this, so can this forum answer?  

  • Hi Chris,

    "what diagnostic, or input to the TMDSCNCD28379D generates the "overcurrent trip" in the software. Currently we are running build 1, which does not try to regulate, just runs the mosfets at 50% duty, and we have disconnected all diagnostics (shunt resistors, hall effect sensors, VBUS voltage sensors) and we still get overcurrent trips in the software? What can possibly cause this? There is nothing in the documentation describing this, so can this forum answer?  

    This should not be very hard to find the route cause. I will suggest to check the signal chain of the overcurrent trip.

    Usually it starts from the IO pin to CMPSS module(usually for current protection) to EPWM trip zone. If you still see the trips happen. it can be any issue along this signal chain. 

    Regards,

    Chen

  • Chen, 

    I have attached our schematic, it is very close to the TI schematic, but updated for higher powers and a different hall effect sensor. 

    I think you need to break what you stated above down a bit for me.

    We have shorted our shunt resistors that feed the AMC1305M25DW.

    We have shorted the input to the AMC1301DWV which is the Vbus monitor

    We have shorted the hall effect sensor input that feeds the OPA4350Ua. 

    We are running only in build 1. Which should not be looking at most of the feedback in any case. 

    When we start at low voltage and slowly bring up the input volltage we trip off at around 3KW, no reason for the trip is displayed in the software, we used to get overcurrent trips or voltage imbalance trips, now we get no indication of what trips us off. 

    Assuming it is noise getting into the MCU... which pins should I be filtering on the MCU that could be causing the trip off? 

    Besides the sensor inputs to the MCU (the SD_datas... IL_FDBKs, V_BUS_FDBK), what else can trip us off? 

    Above you state "Usually it starts from the IO pin to CMPSS module(usually for current protection) to EPWM trip zone. If you still see the trips happen. it can be any issue along this signal chain" what does this mean? what specific pins are you describing? What is the signal chain? 

    Thank you for your help, 

    -Chris 

    910-29020-01Rev.1 APS_MOSFET_5.pdf

     991-29020-02_rev4_5_YEX.pdf

  • Hi Chris,

    I am sorry for the late reply. 

    Above you state "Usually it starts from the IO pin to CMPSS module(usually for current protection) to EPWM trip zone. If you still see the trips happen. it can be any issue along this signal chain" what does this mean? what specific pins are you describing? What is the signal chain? 

    Since you mentioned the issue is due to the false triggering of the protection. I was thinking the debug should start with the protection signal chain. Usually we utilize CMPSS and PWM module to achieve quickest protection. The external sensing signal will feed into CMPSS module and then goes into trip zone submodule inside PWM module. My suggestion is to check the output of CMPSS module and flag register in EPWM trip zone submodule to identify where does the issue come from. If the signal comes from the CMPSS, then you can consider using digital filter or others inside CMPSS to remove potential false triggering of CMPSS if it is noise.

    Regards,

    Chen