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.

UCC28730: UCC28730 WEB BENCH DESIGN REPORT

Part Number: UCC28730
Other Parts Discussed in Thread: UCC28600, LM5023, UCC24650

Hello:

We have several highly compact designs using UCC287xx family.

One of them currently being tested is UCC28730. We used the Web Bench & the Excel Spreadsheet.

Pl see the attached pdf of the report Web Bench produced.

There is a strange entry for Vout actual which is 18.257 apparently  based upon the values used in the divider at VS pin

But Vout itself everywhere else reported is 6.2V.

  Web Bench calculates 4*(1+Rfbt/Rfbb) which is 18.257V

This is a bit confusing. Vout is determined by this ratio divided by Na/Ns, in which case it makes sense.

Is this the correct interpretation?

Another thing: Lpm can swing wildly clearly based upon Iout.

What should be then used for setting this inductance? 

In our case, we have imposed  Iout=300mA which gives Lpm as approx 4mH

An achievable value with gap on the core suggested ( our core has a slightly higher cross-section). But if the real load is 50 mA?

Web Bench will give 23 mH, an impossible value to achieve in this core unless you quadruple turns with Rcs =28 Ohms. Also sounds weird but clearly consistent with Vcs

So shall we set Iout=300mA knowing that we would hardly ever have ICs connected to it will draw that amount of current? ..because the Lpri is achievable with 60T:5T:14T?

Any clarification will be highly appreciated.

WBDesign24_28730_6v2300mA.pdf

  • Hello Robin,

    Thank you for your interest in the UCC28730 flyback controller.

    On review of the Webench report, I believe that the listing of "Vout actual" is erroneously named.
    I'm not sure what it should be called, "Vaux_pos" or something, but it is not the actual Vout, rather the reflection of Vout + Vf of the output diode through the turns-ratio. 
    I'll notify the Webench group about the misnaming.

    As for the high inductances, unfortunately for such low-power, low-current designs with high input voltage, the calculated inductances are real.
    Lm is forced to be so high, to meet the simultaneous criteria of energy per cycle throughput AND the constant current regulation duty cycle at max load.

    Your true load of 50mA is about 300mW, but the Lm is so high that you propose a fake max load of 300mA (~1.8W) to bring Lm down. 
    The 300mW will then be a light-load operating condition.  But the current limit will still be up at 300mA+. 
    This a limitation of the constant-current limit function with its fixed Kcc factor in the UCC28730 and other PSR controller in this family.

    You may obtain some relief on Lm with a different off-line flyback controller such as LM5023 or UCC28600 that does not limit the duty cycle this way.
    But they do require opto-coupled feedback which adds cost and complication.   

    I would suggest a "cap-drop" approach for such low power, but I presume you require isolation from the line.

    Regards,
    Ulrich

  • Thnx Ulrich.

    Yes, "Vout actual" should be renamed as " calculated VDD" ...one suggestion.

    As to the output power, we can load up the output(s!) for about 2W. As this will be bais for TPS24 xxx, TMS320F28379 , opamps, drivers etc.

    We would rather stick with UCC287 series. We have 700/710 designs as well....along with 780/782 etc

  • Hello Ulrich 100

    Me back again regarding UCC28730 circuit performance. We have exact same values we obtained from the Web-Bench design tool for 6.2V output with 300mA load. While line regulation is excellent, we see no load regulation at all. Any ideas on how to obtain load regulation? Surprising thing is that output never reaches 6.2 but stays around 4.7V with approx 200 Ohm ...Trying to get it up by adjusting VS upper diver resistor value. But doubt if that will fix bring any load regulation. ...and BTW: we do not see the characteristic flyback high shoot back with ringing at all...perhaps due to low Ipeak & low leakage inductance( 8 uH)...?

    Any expert review will be highly appreciated.

  • Hello Robin,

    That is curious behavior, but if it stays stuck at 4.7V, this seems to be like constant current (CC) regulation (Iout = fixed while Vout sags).

    4.7V / 200R = 23.5mA, so this doesn't look like an external overload.  However, the schematic may look perfect but the pcb may have an error.  There may be an "internal" overload where you can't see the current going.
    Please check the usual stuff like diodes and caps in correct polarity and that transformer turns-ratios and winding polarities check out.
    Also check the pcb layout files to verify there are no unwanted via-to-track or via-to-copper short circuits.

    Also check the input power to verify that it matches the output power plus some reasonable loss. 110mW out at say 75% to be conservative = 150mW input.  If you measure much higher than 150mW input, then the primary side may be operating at its CC limit and you have an internal current sink somewhere, probably on the secondary side. This would match the scenario you describe where there is no characteristic DCM ringing after the flyback demagnetization interval. CC would look like transition mode (boundary mode, critical conduction mode) operation.

    Also, remove the UCC24650 wake-up chip, at least until the regulation issue is debugged. It will be one less variable to worry about. 

    Good luck.  Please let me know what you find.
    Ulrich

  • Ulrich: Sorry: if the posts look repeated... the new format is causing a lot of confusion here..

    In any event, found out the reason for the absence of characteristic ringing on the drain on our circuit. This was caused by the RCD snubber carried forward from the 28710d circuit of some vintage. Removing that kicked off the ringing and now the controller can sense the secondary current state correctly & hopefully get back the load regulation.

    I will post new results asap.

    fyi

    robin

  • Ulrich:

    All clear!

    Will send full data asap.

    thnx much and greatly appreciate the time you took to review our debug report that led to fix the design.

    r

  • Hello Robin,

    I'm glad to hear of your success. I appreciate you keeping me informed, and wish you more success to come.  
    By our policy, I need to close this thread to keep our support tracking straight.

    Good luck!
    Ulrich