Bizzare behaviour from SG/UC3525

Hi, the chip has pulse limiting, a noise pulse generated by the top fet appearing on pin 10 will reset the pwm latch. Try a hard short from pin

Good day to you too Terry.

Ummm... guess what I was thinking of doing next ! It's called desperation !

Yuh . That figures. But a 1~2 cm track - with careful attention to routeing ?

OK.

Interesting.

I omitted to mention - for sake of simplicity- that I briefly decoupled the

That 'helped' the odd 'jitter' on the hi-side drive. I thought I was on the home run - I selected the switch position that stops the 3525 outputs and removed power. A couple of second later the IR2110 went *bang* - well fizzz to be more accurate - ( no IGBTs danaged though ).

What's weird is that it was the low side driver that went short ! About 2 ohms from Vs to Lout after it went bust !

waveforms are fine sans IR2110.

I'm driven bonkers how the pulse width on OutA and OutB is different whern it's in circuit ( one presumes there's a clue here but I haven't yet been able to make any sense of it ). One might assume a load current issue but I have only 33k from DCbus/2 to the switching point !

I admit - I'm tempted to provide a specific Vboot supply anyway - using a 555 for example.

But this ain't the issue

I'll try that !

Cheers, Graham

Going entirely from memory... I thought the SG3525 was a push-pull flyback converter, but you use terms like "high side driver" and "half bridge", which make no sense in that context. I can't tell from your scattered verbal description what you are trying to do, but it sounds fishy. Got a schematic?

In article , Pooh Bear wrote: [snip]

I have no experience of smps supplies, just posting to register an interest in learning along with you.

Hand capacity effects around the Shutdown input? A Shutdown input that is both directly connected to the output OR gates, or is capable of doing an early PWM pulse termination via the S-R flip flop?

Try sticking a 0.1uF from Shutdown to 0v, right at the chip?

Actually I thought 0.1uf was a bit big so I added 10nF there. It had the desired effect you suggest.

It seemed to stop the 'jitter' on the trailing high side edge but then I went and switched the damn thing off and the IR2110 went Fizzzz as the rails decayed ! And it was the the *low* side driver that had gone bad ! It measured 2 ohms form Vs to out after this incident !

My brain is going a bit bonkers.

I'm baffled. Doesn't happen often. Last time I was this perplexed was when I realised that I had a very fast voltage driver stage in an audio amplifier that was causing a reverse bias avalanche breakdown problem in the output devices. And don't even begin to ask how I worked that one out !

Graham

OK - I'll look for that but it's the *input* signls to the IR2110 that are wanky - freaky even ! I keep wondering if I'm probing the correct pin ! It's that bad !

Loads of local decoupling.

Nah - it's not that. Thanks for your interest and input regardless !

Regds, Graham

I don't seem to see complete threads these days, so apologies if this remark is out of date.

Perhaps point your bifocals at the 3525 UVLO, and think about whether it is coming in too late, (on power-down), and is not making the output stages safe before the main supply rails drop to a damaging undervoltage.

Gidday Graham,

try this: lift OUTA and OUTB pins. "swap" them with little dangly wires.

If the OUTA pin suddenly starts working and OUTB goes funny, then its something to do with the external connection(s) to OUTA

then pull the same trick with the IR2110 inputs.

some gatedrive outputs get pissy when output inductance pulls them below

try loading them capacitively (perhaps 10-20pF) sans IR2110, see if the waveforms are still OK.

set the DC bus to 0V, provide a separate high-side power supply and see what happens - with no actual output switching, does the problem occur.

place a series resistor between the 3525 & 2110, perhaps 1k.

Cheers Terry

Pooh Bear wrote: [snip]

perhaps there is a solder short, or noise coupling into that pin. I read the 3525 datasheet, and its not clear from the block diagram how such an event might occur, but without looking at a real diagram theres no way to tell.

there are some Unitrode app notes that talk about this, and IIRC bipolar output stages are most susceptible, FET output stages are pretty much immune. Some Unitrode datasheets even say "no output schottky diodes necessary" but alas I cant recall which ones.

true, along with whatever stray capacitance (FETs, layout etc), which will cause nice fast current spikes and associated LdI/dt voltage spikes. the dV/dt wont change much at light load (and may even get worse), so capacitively coupled noise is still there.

does the magnitude of Vdc affect the crazy pulse?

my SOP is to provide multiple well-isolated linear power supplies for every gatedrive, and use those exclusively, until my power stage can happily drive full load all day. Or at least until I'm happy the gatedrive really works.

doing this allows you to ignore the charge-pump power supply aspects, UVLO etc. and just concentrate on banging the gates around.

bung a lamp in series with the VDC supply, its cheaper than a FET.

Cheers Terry

PS the PDF offer stills tands.

"Pin 10 should not be left floating as noise pickup could conceivably interrupt normal operation." Ground pin 10 and see if it helps.

If the 500ns OUTA pulse is "clean"- no jitter, then you have something triggering/resetting that internal FF drive in the 3525. How does that get there? I haven' looked at the 3525 datasheet, but there are several avenues: RC timing ckt, feedback, CL shutdown, and maybe some others- it may take only a 5ns high frequency blip to feedthrough on the wrong hi-z receptor and off it goes. The high dV/dt's and the proximity suggest some beading, orientation, distance, and/or shielding may be required somewhere, but then you already have everything on a board. You can track this down by probing around for other events while triggering off the negative edge of OUTA.

...

It sounds like this is for your employment. Therefore my first recommendation is that you might consider using an off the shelf powersupply or working with a company that specializes in designing and manufacturing SMPS designs specially for people such as yourself. You could spend all day (weeks/months/perhaps even years) banging your head against the wall in frustration. In the end you might end up with a product that seems reliable and meets your requirements to your satisfaction only to find in your horror that once deployed in the field it experiences all sorts of unanticipated failures. It is very easy to overlook things in an SMPS even when it seems to be operating well. If you are a generalist doctor (or even a podiatrist) you probably have no business performing heart transplants when there are plenty of heart surgeons available.

Nevertheless for your own edutainment it would still be very valuable to pursue the causes of your current SMPS ailments on your own time.

By the sounds of it your design has multiple weaknesses/problems which may or may not be directly related to each other.

In particular the IR2110 seems to have attracted your intense scrutiny, however I would venture to guess it is probably only an innocent victim. As for the OutA/OutB jitter/unequal pulse width problems (as well as the human hand near the design and it changes performance), this can probably be explained by either your implementation of or your understanding of 3525 pins 1, 2, 8, 9, and 10 (for dual inline package). These are all extremely important pins which are normally driven by relatively high impedance signals. They are quite sensitive and are quite integral to the control loop and the general proper functioning of your device.

In particular the shutdown pin is not "slow acting" like you have theorized. It would appear from the block diagram that even a very momentary high signal on this pin will instantly turn off the output NOR gates, as well as set the PWM latch thus keeping the outputs off until at the very least the next cycle of the oscillator. How fast the outputs turn back on depends on what happened to the soft start capacitor.

As for your IR2110 fizzling... It seems to me that if the output IGBTs haven't failed, then clearly something is very wrong. I guess that is obvious since the IR2110 failed... Without a schematic it is very hard to say exactly what you are doing and how turning off the 3525 might have effected the IR2110. What is the nature of your powersupply source for the

Whatever the cause of this problem, it sounds like it has a relatively low chance of being directly related to your other pulse width/jitter problems. I would not look directly at the IR2110 for the source of your problem as much the circuitry surrounding and hooked up to the IR2110 for the root cause.

Aside from these considerations... Current limiting? You are using it right? Right?? Without it you are liable to get some kind of STD or something. Any high power SMPS which has any hope of being remotely reliable must implement some kind of highly effectual current limiting. The soft start and shutdown pins of the 3525 may play some role in a given current limiting implementation, but it is up to you to decide exactly how best to do it in your application. I personally like implementations that have two levels of safety. One level instantly shuts off the output as fast as possible (IE:

This is a good point, however it appears the designer of the IR2110 envisioned this scenario and took care of it. Presumably the IR2110 inputs have both schmitt triggers and internal pull downs.

A 0.1uF capacitor on the shutdown pin is a step in the right direction, but this pin should still not be left floating. It mentions this in TI's UC3525A datasheet under the section: Principles of Operation and Typical Characteristic Shutdown Options. Datasheet I'm looking at can be found:

So, a pull down resistor (or hardwiring to ground) should be used unless it is actively being driven by something.

Yes, I looked at that area. I'm unhappy it's adequate so I'm intending to add my own over-riding UVLO that monitors all the rails.

In the instance I mention however I had already asserted the shutdown function on the 3525 before allowing the rails to decay - i.e. OutA and B were both inactive. Then the IR2110 expired as the volts dropped !

Graham

Cheers Kristian. Did that quote come from the data sheet ?

Ok just found it.

Graham

The 3525 is simply being used to generate the timing waveforms. The 3525 outputs drive an IR2110 half bridge arrangement.

It's a configuration very similar to one used by one of the major pro-audio amplifier companies in a mildly different incarnation which has proven reliability. The differences are modest and I've added some further protective features in fact.

Not that I can post right now sadly.

Graham

Indeed.

Quite !

After others' comments I'm going to concentate on pin 10 - the shutdown pin. Despite the fact that the block diagram of the chip's internals shows no obvious route for this to cause the effect, I've been pointed to a caution on the data sheet regarding it.

Cheers, Graham

Lol ! The data sheet application schematic shows the pin hi-Z in normal use ! Time to see the truth I guess ?

Graham

It usually takes quite a bit of power to make a component audibly fizzle. While not totally inconceivable, a 14V bias supply (which was just turned off before the failure, is that what you are suggesting?) isn't too likely to be able to deliver this much juice. So that leaves the question, if it didn't come from the IR2110 supply rail, where did the power come from?

Perhaps the power came from the main input capacitor(s) charged to what,

After the failure, did you check to see if the bootstrap diode (which is used by the IR2110 to charge the bootstrap capacitor Cboot) was still good? What is the part number you are using for this bootstrap diode? If this part failed it could conceivably cause the symptoms described. The temptation when selecting this part would be to use a low voltage schottky diode, however this would not be a good choice since the part must be able to block the full high voltage supply voltage plus around 15V plus margin. During turn off of the IR2110 Vcc supply it is conceivable this diode would experience slightly higher voltage stress than during normal operation. If improperly selected, this might help explain why it failed at power off. This may not be your problem, but it is a theory at least.

What does your power stage look like? Do your half bridge IGBTs have antiparallel diodes on them?

This is probably unrelated, but 14V is rather too low by conventional standards for driving normal IGBTs. Normal IGBTs expect about 15V of gate drive for good performance, and since the high side IGBT will only receive at the most one diode drop less than the IR2110 bias supply voltage, this is a bit lower than what is conventionally considered optimum.