Why do my P-channel MOSFETs keep dying in this H-bridge?

Question

So this is my H-bridge: Every time I start using it in one direction the P-channel MOSFET and the NPN BJT which belong to the used direction die in seconds. The killed MOSFET and the BJT developing a short circuit so I can use the other direction no more. They die without noticeable heat or smoke!
The controller is an arduino uno, and only the N-channel MOSFETs are driven with PWM signal, the P-channels are connected to simple digital output pins. PWM frequency is the default 490Hz for digital pins 9 and 10 (each PWM output is individual). I've already killed 4-5 P-channel MOSFET + BJT pair, it could happen on both side. (It depends which direction I use first.) The motor is a 12V car windshield wiper DC motor, the power supply is 12V 5A. 12V and 5V power supply grounds are connected.

There are two things which may be true, but I am not 100% sure as I did not test it thoroughly:

• in the former version I was using 1k resistors for R7 and R8, and I did not have any problems. I will try it again but I am running low on P-channel MOSFETs now..
• when I cut out the fried MOSFET + BJT pair, I can use the other direction without killing the remaining MOSFET + BJT pair.

Please help me, what is happening here :)

• Should I use a resistor between the NPN BJT and the P-channel MOSFET?
• Should I use a 2n7000 MOSFET instead of the 2N2222 BJT?

UPDATE: I've just tested the H-bridge with a 12V 55W light bulb instead of the wiper motor. The P-FET and NPN were killed during the test. The N-channel side was driven with a 40% PWM signal. Without a load it did not have any problem.

UPDATE2: I changed back R7 and R8 to 1k from 150R. Now the bridge is working again without any components failing. (I didn't run it for days, but with the 150R resistors the reproducing of the fault only took a few seconds.) I will add some decoupling capacitors on the bridge between the GND and +12V anyway as Brian suggested. Thanks for the answers to everyone!

Answer 1

How are you decoupling the 12V supply?

One possible failure mode is that inductive spikes from switching off the motor current (i.e. at the PWM rate) are dumped into the 12V supply via the flyback diodes. Yes, that's supposed to happen, but...

If the 12V supply is not decoupled, and is sourced from a PSU not a rechargeable battery, or is sourced via a long (inductive) cable, it is not actually a 12V supply, but momentarily driven up to that inductive spike voltage. Which could be well above the MOSFET ratings...

Monitor the 12V supply with a fast oscilloscope. If it shows signs of over-voltage spikes, increase its decoupling until it doesn't. (That should include 0.1uF ceramic capacitors for low HF impedance as well as an electrolytic reservoir capacitor. And possibly a 16V or 25V zener diode just in case...).

I don't know that this is your actual problem, but it is one base you MUST cover.

Answer 2

R1 R2 are far too big for all but the smallest nonexistant mosfets.This means that they are turning of much slower than they are turning on .This means that even if you think that you have included some sensible deadtime you will still get shoot through and eat fets.I use a extra transistor to do a fast turn off ,its worth it .

Answer 3

One of the top P channel MOSFETs is active - this determines direction. When you apply PWM to both N channel MOSFETs (as implied in your circuit), you get shoot-thru on one half of the H bridge.

You must NOT apply PWM to both N channels devices - only apply it to the bottom right when the top left P channel device is activated OR only apply it to the bottom left when the top right P channel device is activated.

EDIT - also, your P channel MOSFETs are upside down.

Answer 4

One thing that stands out to me is the lack of flyback diodes across your FETs. As your motor is an inductive load, it can very easily generate high voltages across your FETs when there is a change in current (V = L dI/dT in an inductor). These voltages can easily exceed the breakdown rating of the source-drain junction in your FETs.

To solve this, a diode is normally put in parallel with the junction to keep the voltage in check like so:

(Image from: http://www.modularcircuits.com/blog/articles/h-bridge-secrets/mosfets-and-catch-diodes/)

This "clamps" the voltage across the FET.

Answer 5

@Autistic is right about R1 and R2 - this arrangement will lead to very slow switching times on the P fets. You may consider using a dedicated P Fet driver charge pump instead of the BJT+Pullup.

Some sanity checks

Can you check the driving signals? It is very important which FET is turned on or off.

forward: 
p1 on    p2 off 
n1 off   n2 on

backwards: 
p1 off    p2 on 
n1 on     n2 off

brake: 
p1 off    p2 off
n1 on     n2 on

Try the followings:

• stop any PWM
• disconnect any load
• drive from your code as: p1 on n1 off, wait 500ms, p1 off n1 off 100ms (dead time), p1 off n1 on 500ms, p1 off n1 off 100 ms (dead time) and repeat. This produces a test signal which is easy to debug.
• now the p1 n1 output of the h-bridge shall switch from GND to 12V nicely. Use a scope to test it, or you can use a small light bulb as well. Connect the bulb between GND and the p1 n1 output - it shall blink so p1 is good. Connect it to 12V and p1 n1 output - it shall blink so n1 is good.
• if you have a scope, verify if p1 and n1 is not cross-conducting. Checking this signal you shall not see any other value than clean GND, clean 12V, and some floating GND in the 100ms dead time.
• if you have no scope, you can set a quite big dead time, e.g. 500ms - it can not hurt :) but can save your P fet.
• now connect your motor instead of the light bulb, it shall run and slow/stop like the bulb. This verifies that the fets are ok.

The problem

• Be very cautious about the PWM arrangement above. You can very easily fry your fets. You can turn on the P side while you're switching the N side, therefore you make shorts (smaller or bigger - it may survive with 20% PWM depending on the quality of your power source).

Normally, microcontrollers have a dedicated 4 output PWM driver with deadband control. The 4 PWM signals can drive the 4 fets, and these signals are synchronized and inverted, plus the dead time is taken into account. See the PIC microcontrollers' PWM for more. http://www.ermicro.com/blog/wp-content/uploads/2009/01/picpwm_03.jpg

Since the Arduino is not built for that purpose, you may wish to use some basic logic to produce the right PWM signals. The goal is to ensure that n1 and p1 are always driven complementary, as well as n2 and p2. You can get it by using some more BJTs: http://letsmakerobots.com/files/YG_H-Bridge1.jpg Then you have the two pins which you can PWM drive.

You might rather use some logic gates, like this: https://e2e.ti.com/blogs_/b/motordrivecontrol/archive/2012/03/26/so-which-pwm-technique-is-best-part-2 and then you have a clean forward/reverse, plus one PWM pin which drives the speed.

This article may worth of checking: http://www.modularcircuits.com/blog/articles/h-bridge-secrets/h-bridge_drivers/

Answer 6

Are you sure that you are switching on the top left P-FET when you are apply PWM to the bottom right N-FET?

You should double check your P-FET orientation. It seems like the P-FET is backwards and you are getting excessive power dissipation when the P-FET body diode conducts. Measure the voltage across the P-FET under your fault conditions. If you see around 0.6 V across the FET when the 2N2222 is on, then the P-FET is reversed. Also check the P-FET gate voltage during the fault condition to ensure it is seeing less than 0.2 V.

Do you still see the fault current if you remove your motor from the circuit ?