problem of burning the hell out of mosfets!!!!help

Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.
i tried some of the design posted in this forum but aint make no good.....ended up with burning a huge stock of mosfets with no succes....signals are shown on the gate point before connecting mosfets and they disppear after connecting them.....and if worked then it would be for a while....can any one suggest in a simple manner why the hell this happens...
warm regards
 
Disabled Account
Joined 2012
they tend to oscillate easily. You need to keep very short lead lengths. Have decoupling cap at the fet - not at the power supply. And a gate resistor of a few hundrd Ohms close to the gate lead. These are the typical things to do to prevent oscillations which destroy the fet. if you have a 100Mhz scope, you could see possible oscillation at full power happen.

Other common problem is misidentifying the leads - which is gate, drain and source. double - triple check.
 
they tend to oscillate easily. You need to keep very short lead lengths. Have decoupling cap at the fet - not at the power supply. And a gate resistor of a few hundrd Ohms close to the gate lead. These are the typical things to do to prevent oscillations which destroy the fet. if you have a 100Mhz scope, you could see possible oscillation at full power happen.

Other common problem is misidentifying the leads - which is gate, drain and source. double - triple check.


how exactly do u say to place those resistor and capacitors
 
An interesting point when playing fet's, is NEVER, NEVER, NEVER let the gate pin floating:mad:. Always define a level for it. As it is capacitively coupled with the main current channel, though this capacitance, the gate left open circuit may capture some charge from main channel, opening it randomly, and creating a DC path trough it. As the FET has both current and voltage from drain to source, is becomes class A (linear region) biased, and may be destroyed if this point is outside the SOA of the unit. This can happen in few milliseconds. For avoid this situation, use a 100K resistor between gate and source, when there exist possibility to the gate bias to be removed:scratch:.

This sometime happens in SMPS manipulated by unexperienced people.

Good luck!.
 
it would be easier to everyone to help with your problem if you could attach as much pictures as possible. pictures of your pcb, pictures of your mosfet, ir2110, soldering and the signal trace at some important point.

the best post that i've came across explaining how to troubleshoot a class d design is as below:

If I were you, I will not connect the feedback loop before you find everything is okay, especially with a new design. I will first disconnect the MOSFET, drive an AC signal (using computer sound card playing sine wave) into the comparator. Even without a scope but a DMM, you can still check whether there is AC output from comparator, then check level shifter, then logic input to IR2110. Short Vs of IR2110 to COM. Check both low side and high side output of IR2110. If everything okay, I will then disconnect VS and COM and connect the MOSFET. Try drive the AC signal frequency as high as possible, otherwise the bootstrap power supply for the high side may not work. Measure the current drawn by the MOSFET and temperature to guess whether there is shoot through. Check MOSFET output and inductor for AC. If everything is okay, I will then close the feedback loop.

With a scope and a siggen, it will be a lot easier.
people are building the irs900d problem free. so the pcb works. you then decide to start your class d journey with a new, unconfirmed pcb that nobody have given any feedback for. it's better to start with a simpler design and work from there.
 
Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.