I think this can be done after I order PCB, right now i need to order asap to have something to play with.it needs to be speeded up / higher gain - until it becomes unstable - then back off a bit
I am sorry, i did not understand question? D3 after startup should see a max of 52micro amps.Why is the switcher driving high current into D3 even in steady state although the nominal output voltage is said to be 12V? There seems to be a problem with voltage feedback operation point.
Will do, right now i think i have complete PCB that should...As already stated, soft start time constant should be much higher, I'd test with 5 or 10 uF C5.
I have tried 13V 3W zener and 15V 1W zener, both died at same voltage levels.what was the previous zener power rating ?
Driver is definitely not ON all the time, if you take a look at first pic here is what is happening.It seems to me the HO driver is on all the time and the PWM is late in getting started until it is too late then you have massive overshoot.
Now second test with those values. Whole dcdc bootloopstry C1 = 22n, R6 = 4k7, R14 = 39k, according to the ckt in post #1
Ah sorry, yellow = outputWE can't tell what is what in the pictures, blue = pwm ? what are the others ? we can't see the graticles or easily derive the volts either
repeatedly turns on and off.What does " boot loops " mean ?
Yes but problem was visible on all voltage ranges, it just so happened that above certain threshold driver or Zener (D5) died. Removing the D5 revealed nature of the problem.this is only at 50V Vin right ?
I may be wrong on this one but i don't think this is the real issue. Or to be precise, why that overshoot was caused.We already knew the problem - too much power overshoot at start up causing zener heating and quite likely inductor saturation.
10V is reached pretty much immediately. I have tested this circuit many many many times. I don't see much happening for first 10-80ms simply because of soft start. Previous version starts immediately. And it was bad, sof start already helps a lot.p.s. the gate drive chip only starts to operate when it gets 10V on its supply - this is why you don't see much happening until this 10V level is reached,
if you had read the data sheet you would have been aware of this.
What heat signature? I specifically marked zener with P0 marker, I hope you don't mean that 1k resistor that is right next to it? Because zener itself doesn't heat up, maybe jumps 1C then gets heated by resistor.Please don't take this the wrong way - but looking at the heat signature in the zener - is about as opposite as you can get to designing a power supply properly
I have been observing FB pin while playing with cap, thing is, calculated values point to value ~22nF -> ~600nF, unfortunately i do not have many values in that range so I had to order more. Which means I will continue to try to dampen it. But 100nF already did good job.The engineering approach is to observe the Vout & error amp output at start up, and adjust the control loop accordingly such that it is fast enough ( and with just enough gain ) to keep the overshoot to a couple of volts max at startup & max Vin - also with the speed-up circuit on the Vsense
That is not what is happening. I can't stress that enough but startup circuit built on depletion fet works marvelously. It delivers enough power for entire circuit for unlimited amount of time (at least until it reaches high temp and die but that would take at least dozens of minutes). If you really want to see it i can disconnect D6 and show you guys.* the internal soft start can´t work properly (I mean it works, but in the time when the driver does not yet work. So it´s useless)
Thank you for that suggestion, this is certainly something i can try! Once i get capacitors I ordered.One of the simplest is to connect a 220uF across R10.
This causes the feedback_VRef to ramp up slowly. Thus the voltage regulation setpoint is not yet at 100% when the driver starts to work
I thought about that but I am kind of running out of space on PCB.* adding power supply monitors that shut down VRef (1) when VCC is not yet completely up
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?