Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 195 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

UCC28180: Current wave form distortion

SENATLA IN
Prodigy 140 points
Part Number: UCC28180

Hello TI,

Greeting...of the day!

We found current wave form distortion in ucc28180 one of our desiged charger but when replace with new one wave form appropriate. please go through below attacehd wave form and let me konw the reason.

Regards,

PR.

Distortion waveform_Blue-Input current, Pink-Input Vac

Normal waveform_Blue-Input current

  • 0
    TI__Mastermind 32500 points

    Hello PR, 

    Thank you for your question on the UCC28180 PFC controller. 

    I cannot tell from the distorted current waveform what function of the controller was not working correctly.  Of the few pins available, possibly ICOMP or ISENSE experienced a problem.

    I suggest that if you can re-install the "bad" controller into the same board and the same distortion happens under the same test conditions, then there may be something wrong with that specific device.  In that case I suggest that you return the bad controller through your component source and request a failure analysis on the device.
    The process is described here: https://www.ti.com/support-quality/additional-information/failure-analysis.html?keyMatch=FAILURE%20ANALYSIS 

    On the other hand if, after re-installing the "bad" controller, the current waveform is normal, then I suggest that the original problem was probably due to some poor soldering or other bad-connection issue and replacing the device "fixed" the problem.   

    Regards,
    Ulrich