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.

UCC28950: Irregular C, D drive output

Part Number: UCC28950
Other Parts Discussed in Thread: UCC2895, , UCC28951, UCC3895, UCC1895

Hi Team,

I used to query in the following thread, but since it was already closed, I created a new thread. Please tell me about this issue again.

UCC28950: (UCC28951)Irregular C, D drive output - Power management forum - Power management - TI E2E support forums

There is a problem that the pulse width of OUTC and OUTD becomes long irregularly.

As instructed, I checked the waveforms of the CS pin and COMP pin, but it seems that there is no abnormal waveform at the timing when the problem occurs.

CH1:OUTC, CH2:Transformer Current, CH3:OUTB, CH4:OUTD

CH1:COMPCH2:Transformer CurrentCH3:OUTB, CH4:OUTD

CH1:CS, CH2:Transformer Current, CH3:OUTB, CH4:OUTC

As additional information, when the pulse width of OUTC and OUTD becomes long, it seems that it is turned off at a value close to the maximum Duty.

CH1:OUTCCH2:Transformer CurrentCH3:OUTBCH4:OUTD

Please explain the mechanism of the above operation.

Best regards.

  • Hello,

    I found these threads on the e2e explaining what you are seeing and what is causing it.  The information in these threads should help you understand the operation that you are seeing in your design.

    https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/817030/ucc28950-asymmetric-duty-cycle-operation

    https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/274735/ucc28950-mismatched-c-d-outputs

    Regards,

  • Hi Mike,

    I've checked each thread, but is it okay to understand that the 3895 bug doesn't occur on the 28950?

    If my understanding is correct, your answer is not the answer to my question.

    Below, we will add information about the malfunction.

    This problem seems to occur when the PFC INV OFF timing and the transformer current inversion timing are close to each other.

    It is thought that the PFC switching noise is affecting the malfunction after switching the lead phase. What kind of malfunction is possible?

    CH1:CS, CH2:Transformer Current, CH3:PFCINV_Vgs, CH4:OUTD

    Best regards.

  • Hello,

    The UCC2895 issue seemed to be due to light load startup and not having enough PWM signal.  However, the controller in that situation was trying to demand 0% duty cycle.  To resolve this issue they recommend adding a ramp to the CS signal per application note slua275.  The following link will bring this to an application note describing the issue and how to resolve it.  https://www.ti.com/lit/an/slua275/slua275.pdf

    The UCC28950 will sync out A and B to the master clock and phase shift out C and D to control the duty cycle.  When the controller demands 0% duty cycle it will phase shift out C and D 180 degrees.  This will make OUT C and D's pulses look twice as large as they should be.  This is normal and is what this waveform that you took is showing.

    In your waveform what looks like occurred is duty cycle jumped form 60% to 100%.  The converter then demanded 0% duty cycle and recovered slowly.  It is almost as if over current protection kicked in and discharged the soft start capacitor.  You can confirm this by looking at SS and comp when this occurs.

    The UCC28950 when operating over 90% duty cycle can trigger over current protection earlier than it should.  This was corrected in the UCC28951 and is recommended in designs that require duty cycles of greater than 90%.  The following link will bring you to an application note that explains that behavior.  https://www.ti.com/lit/pdf/slua853

    If your design requires greater than 90% duty cycle you should be using the UCC28951 instead of the UCC28950.

    Regards,

  • Hi

    First of all, regarding slua275,

    You said that UCC3895 and UCC28950 have completely different internal circuits, and we set Tmin (RTmin=100kΩ), so I don't think they are related.

    Then I have a question about your answer.

    Please answer below.

    1.

    It is said that the OCP may have been detected because the duty jumped from 60% to 100%, but I don't know why the duty jumped in the first place. Why do duty jumps occur? Like the waveform attached earlier, the comp voltage does not rise at the timing when Duty jumps.

    Also, there is no discharge of the SS capacitor, and it seems that there is no 0% duty due to overcurrent protection.

    Please check the waveform.

    CH1:COMP, CH2:Transformer Current, CH3:SS, CH4:OUTD

    2.

    You answered "The UCC28950 when operating over 90% duty cycle can trigger over current protection earlier than it should." Does this mean that the overcurrent protection threshold is lowered? Please tell me specifically what happens when operating over 90% duty cycle.

    3.

    I believe the cause of the problem is the noise when the transformer current is near 0A and the CS voltage is small.

    Doesn't noise to the CS pin cause it to malfunction?

    Could you please check if there is any malfunction due to noise on the CS pin?

     

    Best regards.

  • Additional information.

    1. In the above waveform, the comp voltage increased because the output voltage dropped.

    CH2:Transformer Current, CH3:Vout

    2. I changed it to UCC28951 and confirmed it, but the problem did not disappear.

  • Hello,

    You had asked if the UCC2895 had the same issue as the UCC28950.  So the following information describes the UCC2895 issue and the UCC28950 full load behavior that you are observing.

    "The UCC2895 issue seemed to be due to light load startup and not having enough PWM signal.  However, the controller in that situation was trying to demand 0% duty cycle.  To resolve this issue they recommend adding a ramp to the CS signal per application note slua275.  The following link will bring this to an application note describing the issue and how to resolve it.  https://www.ti.com/lit/an/slua275/slua275.pdf

    The UCC28950 will sync out A and B to the master clock and phase shift out C and D to control the duty cycle.  When the controller demands 0% duty cycle it will phase shift out C and D 180 degrees.  This will make OUT C and D's pulses look twice as large as they should be.  This is normal and is what this waveform that you took is showing.

    In your waveform what looks like occurred is duty cycle jumped form 60% to 100%.  The converter then demanded 0% duty cycle and recovered slowly.  It is almost as if over current protection kicked in and discharged the soft start capacitor.  You can confirm this by looking at SS and comp when this occurs.

    The UCC28950 when operating over 90% duty cycle can trigger over current protection earlier than it should.  This was corrected in the UCC28951 and is recommended in designs that require duty cycles of greater than 90%.  The following link will bring you to an application note that explains that behavior.  https://www.ti.com/lit/pdf/slua853"

    The over current protection is triggered when the slope compensation ramp + the CS signal reaches 2 V.  This can be seen in the block diagram of the data sheet.

    1. You can change the trip point by adjust the current sense resistor and/or adjusting the slope compensation.

    It appears that you are using the UCC28950 over 90% duty cycle.  It is recommend per application note slua853 that you use the UCC28951 in applications where over 90% duty is required in your design.

    Regards,

  • Hi.

    Which is 2895 or 3895? I'm asking because you posted threads about 3950 and 28950. This is not my first question.

    Moving on to the main topic, please answer my previous three questions.

    As I have written many times, this problem has been confirmed to occur in UCC28951 as well.

    We need to resolve this issue urgently.

    Best regards.

  • Hello,

    1a. The UCC3895, UCC2895, UCC1895 are the same device with different thermal characteristic, see the ratings below.

    1b.  The UCC28950 is one device rated for one teampature range please see below.

    Please note this waveform you provided the CS signal does not seem present (CH3) it just looks like noise. 

    If you are using the UCC28950 I would have thought it was due to the OCP condition.  However, you verified it in the UCC28951.  So it is not that.

    I looked up the issue and was a glitch circled below.  

    When the slope compensation + the CS and slope compensation is greater than 2 V it will start to discharge SS and demand zero duty cycle.  It will cause both C and D to phase shift and the period will look twice as long.  This will occur in both the UCC28950 and UCC28951.  The only difference is the glitch circled above in the UCC28950.

    What you are seeing is normal behavior for the UCC28950 demanding zero duty cycle.  This waveform you took below shows the converter is demanding max duty cycle and then shifts C and D to demand 0% duty cycle.  It looks like the design may have hit an OCP condition and discharged SS demanding 0% duty cycle and then started recharging soft start.

    Original I thought it was the glitch issue because you were using the UCC28950.  However, that was not observed in your waveforms.  

    It just seems that you are seeing normal behavior when the UCC28950 or UCC28951 behavior.  The devices are doing what they were design to do.

    Regards,

  • Hi,

    Thank you for your answer.

    CH3 in this image is SS, not CS signal.

    CH1:COMP, CH2:Transformer Current, CH3:SS,  CH4:OUTD

    The CS signal is as below.

    CH1:CS, CH2:Transformer Current, CH3:OUTB,  CH4:OUTC

    SS should be pulled out during overcurrent, but since the SS voltage has not changed, I believe that there is no overcurrent.

    Another reason to think that it is not OCP is that the CS peak value after the glitch is higher than the CS peak value when the glitch occurs.

    Please answer the following questions.

    1.Is it possible to operate at 0% duty even if SS is not pulled out?

    2.When the glitch you told me about occurs, does it always turn off for a short period of time?

    3.How does the 28951 deal with glitches?

    Best regards.

  • Hello,

    Please see below.

    1.Is it possible to operate at 0% duty even if SS is not pulled out?

    >Yes this would be demanded by the voltage amplifier.

    >In your scope plots for SS and COMP you have them set for AC, you might want to retake these with these channels set on DC.  You will not see gradual changes in DC voltage with an AC setting.

    2.When the glitch you told me about occurs, does it always turn off for a short period of time?

    >If it occurs that is correct.

    >I am not seeing the glitch on your plots.

    3. How does the 28951 deal with glitches?

    >This was changed with a metal mask change to remove the condition in the IC.  The details are proprietary. 

    You had mentioned that CH3 is SS in the following image.  The scope is set on AC for CH3 so you may not see the SS discharge..  Could you reset CH3 to DC and retake the plot.

    Regards,

  • Hello,

    1.I changed to DC setting and measured. Please see the waveform below.

    It looks like there is no variation in SS and COMP.

    CH1:COMP, CH2:Transformer Current, CH3:SS,  CH4:OUTD

    CH1 has an offset of 2.5V and CH3 has an offset of 3.5V.

    2.How many seconds is the short OFF period when the glitch occurs?

    Best regards.

  • Hello,

    Your waveform looks to be steady state at 3.7V.  After soft start this should have charged up to 4.65V.   Is there something in your design preventing SS from reaching 4.75V? 

    Maybe your SS voltage be clamped at 3.7V is causing the issue.  Please allow the SS to charge to 4.65V to see if the issue goes away.

    Your comp is at 2.4V demanding maximum duty cycle and controlling the peak current to 1V.  Then the peak current jumps to 1.25V.  If Comp did not change then the device should demand 0% duty cycle when this occurs.  Because it is above the control voltage.  The below waveforms looks like this is what the device is doing.

     .

    If the comp was steady when the below waveform was taken the UCC28950 should not have asked for more duty cycle.  Did this waveform look the same for the UCC28951.  I am just curious?

    The behavior reported for over 100% duty cycle for the UCC28950 glitch may cause the current to jump.  However, I did not see the glitch in your above waveform.  However it is demanding more than 90% duty cycle and this is a known issue in the UCC28950 if the duty cycle is over 100%.  You may not just be seeing it because you scope is bandwidth limited. You may want to reevaluate without bandwidth limiting.

    Regards,

  • Hello,

    1.Regarding the SS voltage clamped to 3.7V, after startup, it is set to 4.65V, but after the problem occurred, it has stabilized at about 3.7V.

    Please see below.

    CH1:COMP, CH2:Transformer Current, CH3:SS,  CH4:OUTD

    Is it correct to assume that the SS pin is pulled out while the OCP is being detected, and that it is not pulled out when the CS peak voltage is lower than the OCP threshold? Looking at the waveform above, I don't think the OCP is continuing because the transformer current doesn't change before and after SS is clamped to 3.7V. I wonder why the SS voltage has not returned to 4.65V. 

    This is unintended behavior, but since the problem also occurs when the SS is running at 4.65V, the initial cause of the problem is likely elsewhere.

    2. I don't think it's turned on twice by requiring 0% and 100% duty for control. Even if 0% is requested as you say, I don't know what caused the previous mode not to turn off.

    One of the reasons why I don't think it's due to duty control is that there are cases where the On continues longer than twice as shown in the waveform below. If it continues to be ON, it will operate like a 0% duty, so the output will drop and it is requested to increase the duty.

    3. I've checked without any bandwidth restrictions to see if there are any glitches. Glitch could not be detected even if the capacitor for noise elimination of OUTC and D was additionally removed.

    4. We have confirmed that adding resistors in series to OUTC and D or reducing the switching noise of the PFC circuit reduces the frequency of occurrence of this problem. I believe the problem is caused by noise. Please let me know which pin the noise can cause this problem.

    Best regards.

  • Hello,

    Please see my comments below.

    1.Regarding the SS voltage clamped to 3.7V, after startup, it is set to 4.65V, but after the problem occurred, it has stabilized at about 3.7V.

    >This should stay at 4.65V unless an over current condition has occurred.

    >Can you share a schematic?

    >Can you separate these three plots with better resolution.  I can't see them clarely. 

    Please see below.

    CH1:COMP, CH2:Transformer Current, CH3:SS,  CH4:OUTD

    Is it correct to assume that the SS pin is pulled out while the OCP is being detected, and that it is not pulled out when the CS peak voltage is lower than the OCP threshold? Looking at the waveform above, I don't think the OCP is continuing because the transformer current doesn't change before and after SS is clamped to 3.7V. I wonder why the SS voltage has not returned to 4.65V. 

    >According to the block diagram the OCP threshold is the sum of the CS signal and slope compensation.

    >What is your slope + CS signal?

    This is unintended behavior, but since the problem also occurs when the SS is running at 4.65V, the initial cause of the problem is likely elsewhere.

    >The SS being discharged to 3.7 V indicates that OCP is being detected or is being loaded down by an external source.

    >I am curious do you have a resistor tied from VREF or any other external source to the SS pin preventing it from discharging?

     

    2. I don't think it's turned on twice by requiring 0% and 100% duty for control. Even if 0% is requested as you say, I don't know what caused the previous mode not to turn off.

    >You claimed that COMP and SS are stable and the devices peak current goes larger than it should.  The controller should demand 0% duty cycle when this occurs.

    One of the reasons why I don't think it's due to duty control is that there are cases where the On continues longer than twice as shown in the waveform below. If it continues to be ON, it will operate like a 0% duty, so the output will drop and it is requested to increase the duty.

    >In this waveform you can see the peak currents are control to a different voltage than the Comp demands.  The first time it occurs it looks like it is demanding 0% duty cycle and misses a switching cycle.  The next switching cycle the CS signal is even higher and the transformer looks slightly saturated and the next pulse is missed.  Once again 0% duty cycle is being demanded.

    >Your controller appears to be operating greater than 90% duty cycle and in OCP.  This will cause a glitch and extended off time in the UCC28950, which was supposed to be resolved in the UCC28951.  You should be using the UCC28951 in your design.  I know that you claim it had not resolved your issue, but you should still be using it.  You also need to figure out why the SS pin being discharged to 3.7V.  Could you please share your schematic for review?

    3. I've checked without any bandwidth restrictions to see if there are any glitches. Glitch could not be detected even if the capacitor for noise elimination of OUTC and D was additionally removed.

    >Thankyou for doing this and I can see the glitch is not observed.

    >You can see the CS signal in the transformer has increased before this occurred.  It should not if the COMP and SS is stable.  It should try to control it to the same level.  Is there a shift in the output load when this occurs?

    >This does appear to be asking for 0% duty cycle.  The C and D are shifted 180 degrees and the waveform will look like this when it occurs.  The other e2e links previously shared discuss similar behaviors to this.

     

    4. We have confirmed that adding resistors in series to OUTC and D or reducing the switching noise of the PFC circuit reduces the frequency of occurrence of this problem. I believe the problem is caused by noise. Please let me know which pin the noise can cause this problem

    >Noise could be contributing to the issue.  Adding resistors as you have done will dampen ringing.

    >Using filtering capacitors on critical pins such as CS will help.

    >If you are using the device in slave mode please make sure you have an 825 k ohm resistor tied between SS and ground.  This is mentioned in the data sheet.  If this is not done the device could also misbehave.

    Regards,

  • Hello,

    Please see my comments in blue below.

    1.

    >This should stay at 4.65V unless an over current condition has occurred.

    >Can you share a schematic?

    >Can you separate these three plots with better resolution.  I can't see them clarely. 

    Schematics cannot be shared.

    The problem occurs even when the SS pin is connected only with an 800kΩ pull-down to GND and a capacitance of 0.32uF.

    I have separated the three plots. Please check below.

    CH1:COMP, CH2:Transformer Current, CH3:SS,  CH4:OUTD

    >According to the block diagram the OCP threshold is the sum of the CS signal and slope compensation.

    >What is your slope + CS signal?

    Rsum (75kΩ) is pulled up from VREF. The slope is calculated to be 0.067V/us. 

    Since the ON time is 5us, the maximum amount of slope correction is about 0.34V.

    The OCP threshold is about 1.66V and 1.22V should not be OCP.  Please see the waveform below.

    CH1:CS, CH2:Transformer Current, CH3:OUTB,  CH4:OUTC

    >The SS being discharged to 3.7 V indicates that OCP is being detected or is being loaded down by an external source.

    >I am curious do you have a resistor tied from VREF or any other external source to the SS pin preventing it from discharging?

    OCP is detected because the transformer has been biased due to a problem.

    Our initial design pulls SS up from VREF, but even with this pull-up removed, SS remains stable at 3.7V when the problem occurs.

    2.

    >You claimed that COMP and SS are stable and the devices peak current goes larger than it should.  The controller should demand 0% duty cycle when this occurs.

    It seems we don't understand each other.

    It seems that the reason why the peak current increases is that there is a problem with the control, and it cannot be turned off at the timing that should be turned off. Therefore, I don't think the gate waveform looks stretched because 0% duty is requested. First of all, there must be a problem that the gate cannot be turned off, and I would like to know the cause of this problem.

    >Your controller appears to be operating greater than 90% duty cycle and in OCP.  This will cause a glitch and extended off time in the UCC28950, which was supposed to be resolved in the UCC28951.  You should be using the UCC28951 in your design.  I know that you claim it had not resolved your issue, but you should still be using it.  You also need to figure out why the SS pin being discharged to 3.7V.  Could you please share your schematic for review?

    It is difficult to change because the delivery of UCC28951 will not meet our schedule.

    3.

    >Thankyou for doing this and I can see the glitch is not observed.

    >You can see the CS signal in the transformer has increased before this occurred.  It should not if the COMP and SS is stable.  It should try to control it to the same level.  Is there a shift in the output load when this occurs?

    >This does appear to be asking for 0% duty cycle.  The C and D are shifted 180 degrees and the waveform will look like this when it occurs.  The other e2e links previously shared discuss similar behaviors to this.

    As previously mentioned, the output drops after the problem occurs. The COMP voltage is rising by control against this drop.

    As I wrote above, the problem starts when the gate OFF timing is extended even though neither COMP nor SS fluctuates.

     CH2:Transformer Current, CH3:Output Voltage

    4.

    >Noise could be contributing to the issue.  Adding resistors as you have done will dampen ringing.

    Does it mean that it malfunctions when noise ringing enters OUTC or D?

    Could you please elaborate on the possible malfunction modes in that case?

    >Using filtering capacitors on critical pins such as CS will help.

    Filters on CS and SYNC had no effect. Are there any pins other than CS and SYNC that should be considered for filtering?

    >If you are using the device in slave mode please make sure you have an 825 k ohm resistor tied between SS and ground.  This is mentioned in the data sheet.  If this is not done the device could also misbehave.

    Our original design had 800kohm resistance on the SS pin, but changing it to 827kohm had no effect.

    What is the acceptable resistance value for 825kohm? What is the minimum value that does not malfunction? Also, what kind of malfunctions can occur?

    Best regards.

  • Hello,

    You mention that if your design does not have a 825 k ohm resistor from SS pulled to ground that you do not see the issue.  Please note that the 825 k ohm resistor from the SS pin to ground is only required if you are using the device in slave mode.  If you are using it as a master controller this resistance is not required.

    Regards,

  • Hello,

    I didn't say that. where is it written?

    Why are you ignoring the question? Please answer the above questions properly.

    By the way, we are using it as a slave by inputting a signal to the SYNC pin.

    Regards,

  • Hello,

    The commend about the 825 k resistor from SS to ground only being needed in slave mode is written on page 18 of the data sheet.

    A copy of the page is below.

    Your questions are related to the C and D gate drive's known behavior.  It is not a device malfunction. The C and D will phase shift to produce 0% duty cycle.  This behavior has been documented on the e2e. Your questions were related to this behavior and were previously discussed in this thread.  However, I have found this thread that discussed this issue as well.  You may find it helpful in understanding the C and D behavior.

    https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/817030/ucc28950-asymmetric-duty-cycle-operation

    If you are using the UCC28950 in slave mode you will require the 825 k ohm resistor from the SS pin to ground.  There is most likely something in your design that is preventing SS from being charged to 4.65V.  I know it is not possible to share your schematic.  However, the following link will bring you to an application note that you can use to check your schematic.  https://www.ti.com/lit/pdf/slua560

    Regards,

  • Hello,

    You say this is known behavior, is that true? Please see below.

    I don't think this is the correct control waveform.

    Please answer the question.

    Q1.I don't think it's possible for the waveform to just operate at 0% duty, but can you explain it?

    Q2.It is clear that noise is the culprit. I've heard this many times, but please tell me which pins can cause this behavior when noise enters and why.

    Q3.Is 800kohm acceptable for the SS pin resistance? What problems, if any, can occur?

    Best regards.

  • Hello,

    Please see below.

    Q1.I don't think it's possible for the waveform to just operate at 0% duty, but can you explain it?

    You say this is known behavior, is that true? Please see below.

    >This is correct.

    >Think of pulse demanding a 100% duty cycle and the next cycle demanding 0%.

    1.) 100% duty cycle A and D on, C and B off

    2.) 0%  B and D on, A and C off, This make it look like the C and D pulse has twice the period.  What happen is phase C and D shifted 180 degrees.

    >This is  what you are seeing here.  You were in a 100% duty cycle.  The current is higher then the comp voltage demands.  The next duty cycle should be zero %.  This is what the controller is doing.

     

    Q2.It is clear that noise is the culprit. I've heard this many times, but please tell me which pins can cause this behavior when noise enters and why.

    >You are correct noise can cause the controller to misbehave. 

    a.) If you have this issue you should be able to remove it with filtering.

    >Any pin being pulled below ground could cause the circuit to misbehave as well. 

    b.) If you have this issue, you should be able to resolve it with Schottky diodes.

    Q3.Is 800kohm acceptable for the SS pin resistance? What problems, if any, can occur?

    > The 825 k ohm resistor was supposed to be used to keep the device from entering an IC design test mode, when the device is being used as a slave device.   Using a lower value should just steel slightly more soft start current.  I would not think it would be an issue by using 800 k ohms of resistance.

    Iss = 25 uA - 3.7V/825k = 20.52 uA

    Iss =  25uA - 3.7V/800k = 20.37 uA

    You might run into problems if you used a resistor that was so small that it stole all of the SS current.

    Regards,

  • Hello,

    I can understand that the mode you described would give a waveform like this.

    However, what I am concerned about is that D is turned off earlier than B is turned off at the timing shown below.

    Since A does not turn on while B is on, it is strange that D turn off while B is on. D should turn OFF after A turn ON.

    Q1.Is this OFF timing correct?

    Q2.If 0% duty is required after 100% duty as you say, why is the first 100% duty required? As previously discussed, neither COMP nor SS changed. Is it possible for these to request 100% duty without changing?

    Best regards.

  • Hello,

    I have added comments directly to your waveform to help explain what is happening.  Your peak current becomes higher than what the voltage amplifier is demanding and then the converter phase shifts C and D 180 degrees to demand 0 duty cycle. 

    To help with out this works.  I have edited the C and D waveforms to show you what a 178 degree phase shift in the C and D pulses would like.

    Q1. I believe the timing for C and D is correct for the peak current that is being seen on the transformer.  The peak current for some reason went higher than the control voltage and the controller is trying to demand 0% duty cycle.

    Q2.  I have seen your plots showing that SS and Comp voltage has not changed.  So why is the current climbing when it should not.  Why for that one switching cycle does the controller demand 100% duty cycle and increase the current beyond the controlled current? 

    Why were you asking about the 800 k ohm resistor on the SS pin?  Did this remove your issue?

    Regards,

  • Hello,

    I understand that 0% duty is requested after 100% duty and the phase is shifted by 180 degrees.

    However, what I want to know is, even if the phase is shifted by 180 degrees, is it possible for control to turn D off before A turns on?

    From what is described in the datasheet, it looks like an impossible control. Please see below.

    Why 100% duty is required is the question I am asking you, and it is strange that you ask. If this can't be explained, I don't think it's being controlled correctly.

    By the way, changing the 800kohm resistor on the SS pin did not solve the problem.

    Best regards.

  • Hello,

    You are correct that A will not turn on if B is on.

    The device is capable of 100% duty cycle.  So you are not correct about the D operation if zero duty cycle is demanded after 100% duty cycle.  If the duty cycle is less than 100% you are correct.

    If A and D are on they demand a 100 % duty cycle.  If at the very begging of C and B cycle.  If Zero duty cycle is demanded, which is what you are seeing.  It will force B low and D high.  In your case since the device went to 100% duty with A and D.  When B went high D also went high to demand zero duty cycle based on what the CS signal is seeing.

    I know you cannot share your schematic.  I looked at your CS signal from previous posts and it looks it quite noisy.   Maybe it is the noise on the CS signal that is causing the design to go to 100% duty cycle.  Have you tried filtering the CS pin.  1 k ohm and 22 pf of the CS resistor will generally due the trick.

    Your current sense signal also shows noise going more than 500 mV below ground.  If this noise is truly on the CS pin it will cause the device to misbehave.  This is because negative voltage breaks down the isolation of the silicon.  All pins should not gore more than 300 mV below ground to prevent this from happening.  Filtering should help with this and adding a Shottky diode across CS and Gnd would help here as well.

    If you are using the SR FETs I would recommend turning them off before critical conduction so there is not reverse current in the FETs.  This can be done with a voltage divider off a VREF to the DCM pin.  If this is not done the FETs could be damaged at turnoff and the CS signal could be affected by this reverse current.

    When it comes to the CS transformer it needs to be before the H-Bridge and not in series with the transformer.   Some customer's have made the mistake of putting the CS transformer in series with the transformer.  If the current sense transformer is in series with transformer the DC information could be lost.

    I would also check your current sense transformer to make sure it is being reset correctly.   If it is saturating it will also cause issues.

    The following link will bring you to an application note that discuss how to set up the current sense transformer and how to turn off the SR FETs before critical conduction.  You may find this information helpful.

    https://www.ti.com/lit/pdf/slua560

    Regards,