top of page

Turning Half Bridge Switch into a full bridge Switch 

Whenever I get a message or an email or a comment regarding unsuccessful bridge circuits, it’s usually along the lines of no output being observed, the MOSFETs getting hot, or everything just getting damaged or blowing up. When I was in the preliminary stages of bridge design, I also had repeated failures. I had circuits blowing up. I had circuits just not working, no matter what. I’ve written on my blog about one such experience of mine. You can read it here:


In this article, I’ll talk about the first things you should do if your attempts at designing a bridge circuit have gone up in smoke or if you’re designing a bridge circuit and want to ensure everything has been done properly.


Another thing I should mention is that, in almost all cases of people asking for help, the bridge driver (the high-low side driver) has been the IR2110 (or similar, such as IR2112, IR2113, etc). Remember that most bootstrap-based high-low side drivers function in pretty much the same way. So, I’ll talk about the driver in general here. I had, however, written a tutorial regarding the IR2110. So, if you're interested regarding that check out:

Using the high-low side driver IR2110 - explanation and plenty of example circuits 

Document hard copy back up of this 


The first thing to do is to check everything over and over again. I know it's cliched and it's probably the most repeated thing you’ve heard, but it's also the least appreciated or followed. One missing connection (or an extra one too, eg a short) could be the cause of all the mayhem.


1) Firstly, check the connection of the bridge itself. Ensure that all the MOSFETs are connected correctly.


2) Check the power connections to the drivers. Make sure that the supply voltage is within acceptable bounds. Ensure that you have small decoupling/bypass capacitors (0.1µF ceramic capacitors) along with larger filter capacitors (for example, 10µF electrolytic capacitors). Use the 0.1µF capacitors across all power lines.


3) Check the connections to the drivers, ie the driving signals coming from the PWM controller, microcontroller, etc. Make sure that the signals for the high-side MOSFET and the low-side MOSFET of one leg of the bridge don’t overlap. If, in any way, both the high-side and low-side MOSFET turn on simultaneously, this will be a dead short-circuit. Expect some ka-boom and smoke. Use an oscilloscope to ensure that the signals don’t overlap.


4) Check the bootstrap circuitry. Make sure you’re using the proper diodes – ultrafast diodes when required. Make sure your bootstrap capacitor is large enough, but not too large. As I had previously mentioned, there is a simple guideline I follow. For low frequencies and high on-times, use large capacitors. 47µF to 68µF could be used for 50Hz/60Hz, for example. For higher frequencies, eg 30kHz, use smaller capacitances, eg 10µF.


5) Check the connections from the drivers to the bridge MOSFETs. Ensure that you’ve placed a series gate resistor between each driver output and MOSFET gate. Ensure that you’ve connected the virtual ground (obtained using the bootstrap capacitor; for example, this is the pin 5 – VS – of the IR2110) to the corresponding high-side MOSFET source. Check that you’ve connected the high-side output of the driver to the high-side MOSFET gate and that you’ve connected the low-side output of the driver to the low-side MOSFET gate.


6) Check that you have placed a gate to source resistor between the gate and source of each MOSFET. I always use a 1kΩ resistor. If you have a number of MOSFETs in parallel, have a gate to source resistor for each MOSFET. Choose the resistance such that the combined resistance is about 1kΩ. For example, if you have three MOSFETs in parallel, for each MOSFET use a 3.3kΩ resistor. This will give a combined resistance of 1.1kΩ (you can use 3kΩ resistors to get a combined resistance of 1kΩ).

Read here about one of my experiences where I damaged loads of drivers and MOSFETs all due to the lack of gate-to-source resistors:


7) Ensure that you have used the same ground for the drivers and the controller generating the drive signals (microcontroller, PWM controller, etc) and the bridge. Most (all that I’ve used) bootstrap-based high-low side drivers are non-isolated drivers. The input and output stage are not isolated from each other. Hence, the driver must share the same ground with both the input stage (which is the microcontroller, PWM controller, etc) and the output stage (which is the bridge that is being driven).


If you have a faulty bridge design and are making changes to it, replacing some components to try again, I suggest you get rid of everything and construct the circuit again using no parts from the old circuit. A faulty MOSFET can damage the driver and vice versa. A faulty driver may damage other parts and so there may be other damaged parts on your circuit that you don’t even know are damaged.


If you follow these tips/hints, you should be able to successfully design bridge drive circuits with no problem. Following these tips/hints will also help you solve problems in any existing bridge drive circuit.

Dead Time Setting

after reading ur tutorials i have some questions on deadtime mechanism of Mosfet driving for full bridge or half bridge SMPS circuit.
How can one ensure the dead time by programming a micro-controller??
Is there any hardware available which ensures the dead time automatically for me????

It will be very helpful if u make a tutorial about dead time mechanism and how to create dead time using mcu programming.


  • You can ensure dead-time in the code by using small delays between the driving signals.

    There are some drivers available that have programmable dead-time settings. For example, take a look at IR2183 (fixed 500ns deadtime) and IR21834 (adjustable between 0.4us and 5us).


MAGIC of knowledge

I turned the switch on and BOOM! That noise, the tiny puff of smoke and the accompanying smell had become far too familiar.

I looked on in confusion at all the failed electronics components in front of me. I needed answers. Why did the H-bridge circuit not work as “claimed”? Books showed numerous such circuits. The Internet was not short of designs either. They were all similar though. I had done my research. I thought I understood the principles and modalities of operation. Then, where did the fault lie? Frustration was creeping in. But I just had to find the fault and fix it.

I wanted to make the SMPS based inverter because I could learn so much in a field completely new to me and then use the inverter at home during power cuts. In that one night of experimentation, I had failed repeatedly, damaging 24 IR2110’s and a lot more components. I had applied all I had learned thus far. Success, however, eluded me.

After repeated failures, I posted my problem on online electronics forums. Numerous members from around the world, engineers and non-engineers alike, joined in to contribute. I learnt and questioned. Heated discussions, arguments and counter-arguments took place. And I absorbed all I could. I did not get a direct solution to my problem but I felt I had become richer and perhaps, through discussion, helped make others richer.

 I spent hours reading documents and application notes, analyzing existing designs and testing the different concepts experimentally. However, the result was the same.

One day I stumbled upon a circuit on the internet, which had a different type of MOSFET gate protection, which employed a resistor between “gate” and “source”. Theoretically this resistor was not required. I redesigned the entire circuit with these resistors connected.

MAGIC! I got the required AC output. No BOOM, no smoke, no smell! 4 resistors (one between gate and source of each MOSFET) that, in total, cost less than $0.25, had been the difference! This was the magic of knowledge – the power of knowledge people refer to.

I then resorted to books and the Internet and learnt why the gate-to-source resistor stopped the MOSFET, and in turn the driver IR2110, from “blowing”.

After completing my inverter, I regularly posted on online electronics forums, especially – in the time I found between school, sports, electronics endeavors and other activities – to help others and to learn.

Many people later posted on regarding problems where the MOSFET and driver “blew”. I had been the one to suggest the use of the “gate-to-source” resistor and this had been the solution to most such problems.

My repeated failures had frustrated me, but also pushed me beyond the boundary of books to learn, acquire and share knowledge, to believe in the power of knowledge but most importantly to believe in myself and my capabilities. This belief and these teachings helped me in later endeavors to overcome obstacles in my way and achieve success.

Importance of the gate-to-source resistor:

It prevents accidental turn on of the MOSFET by external noise usually at startup when the gate is floating. The MOSFET may sometimes turn on with a floating gate because of the internal drain to gate "Miller" capacitance. A gate to source resistor acts as a pull-down to ensure a low level for the MOSFET. I have had MOSFETs blowing up in high voltage circuits, without the resistor in place. In most of the commercial power supplies / inverters I have seen, there is a 1k resistor used.

A similar experience is narrated in Sanajaya Maniktala's "Switching Power Supplies A to Z". This is also talked of in Raymond Mack's "Switching Power Supplies Demystified".

bottom of page