S
Stretto
Guest
"Robert Roland" wrote in message
news:ei9qt6p235hr6orqnrkt3j2mp37d83u6uu@4ax.com...
On Wed, 25 May 2011 05:58:30 -0600, "Stretto" <Stretto@nowhere.com>
wrote:
by the commutation somehow getting stuck. The windings in the motor
are very low resistance, so it would have a very similar effect.
normally are just barely warm to the touch after a flight, and they
were not submerged in water. The water must have seeped slowly in
under the heatshrink.
troubleshooting. I was curious to see if anyone could explain why
these controllers seem to fail so reliably in contact with water. This
is the third one I have seen in a short time.
designs seem to be the most popular. In general, they all employ a
microcontroller (almost exclusively an Atmel) and a bank of MOSFETs
and a few passives to glue it together.
around so that I have at least one on each rail on each phase. The
controller now runs properly on a low-power motor (hard disk spindle
motor), so only MOSFETs were broken. There is also a bipolar
transistor (gate drive for the high-side P-channels) that is seriously
scorched, but, amazingly, it seems to work.
but since there are many of them in parallel, it is tricky to find the
bad ones by measuring. I first removed all that had a short from gate
to either D or S. After that, there were only a few left, so it got
much easier.
placed under the shrink hose, it does not contact all the MOSFETs, and
it does not get particularly hot. If overloaded (usually due to a too
large propeller), though, they get really hot.
original resolution, so they're about 2MB each.
Here's the power side, with the seven surviving MOSFETs:
http://home.c2i.net/w-479147/temp/top.jpg
Here's the logic side:
http://home.c2i.net/w-479147/temp/bottom.jpg
Notice the 6-pin dual transistor in the upper right corner. It looks
completely mangled, but it still seems to work.
The two 7806s are not really part of the controller. They are used to
supply the radio gear from the motor battery, so that no dedicated
receiver battery is needed. It is called a "BEC", a Battery Eliminator
Circuit.
The SO-8 at the bottom, covered in glue, is the 5V regulator for the
CPU.
-------------------------------------------
What maybe happening is there is not enough gate drive to drive all the
mosfets. This can cause cross conduction due to the mosfets not turning off
and on fast enough(you get times when they are both on on the same side).
This would be a controller issue and not the problem with the mosfets. Since
you say it has happened several times that is most likely the problem if the
drive circuitry is sub-par.
I can't tell what exactly the circuit is doing but it looks like the uC is
directly driving the mosfets(considering all those resistors). Mosfets are
not as ideal as one wishes and the biggest problem with paralleling them is
the increased gate capacitance. Basically you can think of a gate of a
mosfet as having a capacitor across it and it takes time to charge the
capacitor. As it charges the mosfet transitions from open to closed or vice
versa. The transition acts a resistor varying from R_ds(on)(for your mosfets
it is 7.5mOhms) to some very large value. As current is flowing through the
mosfet the resistance causes significant thermal dissipation. The goal is to
have very quick transition so there is less time for the mosfet to heat up.
Fast transitions require low gate capacitance. When you parallel mosfets you
increase the effective gate capacitance(as seen by the driver) which slows
all the transitions down for each mosfet.
The design parallels 5 mosfets per leg. Each mosfet has 7.5mOhms so the
total resistance is 1.5mOhms but the gate charge is 105*5(*2) = 525nC. These
are best case. If the drive voltage is lower than 10V that 7.5mOhms will
increase which increases heat dissipation(but you said it wasn't getting too
hot to the touch so the drive voltage maybe ok all the incidences happen
when you are losing power).
You could possibly use 1 mosfet per leg instead of 5 by finding a better
mofset.
http://www.fairchildsemi.com/ds/FD%2FFDMS7650.pdf
While the wrong package it has about the same ratings or better(from what
I've checked).
http://www.vishay.com/docs/69063/si7137dp.pdf
For pch it's not as good but may work(if you use better nch's(lower R_ds(on)
then you can use worse pch if necessary).
The main thing you need to work out is if the controller really is failing
because it gets wet or if it's coincidence. There is only 1 way a mosfet is
going to fail in the way you are using it and it's overheating(I'm sure you
know there are other ways to ruin them such as ESD but these effects
shouldn't occur in SOC). For an h-bridge this will happen only due to cross
conduction issues(assuming it was properly designed for the rated load and
for a motor it generally is not meant run stalled).
Cross-conduction either occurs because the controller itself is
malfunctioning and not synchronizing the switching properly or because it is
not properly able to drive the mosfets.
Possible reasons: Stalled motor(draws more current), low power(increases
cross conduction and R_ds(on)), malfunctioning controller(sync issues =>
more cross conduction). Water(not sure but this is not part of the SOC).
Note that significant cross conduction should only occur when changing
polarity/reversing the motor. But if the controller or power is failing that
it will more likely occur. If you are drastically changing the polarity of
the motor(or the controller thinks you are) then it may be trying to reverse
the polarity very often which will increase power. So in that case it could
be an issue with the input to the controller(the controller should be able
to prevent this quite easily).
Hopefully I've given enough information that you might be able to figure out
what happened.
PS. That dual transistor you mentioned may be a clue to the cause. I see 2
others that look identical(I guess thatâs a diode above each one). I don't
know what they are doing but possibly the transistor is going back causing
the mosfets to subsequently fail. You did say it's working but maybe not as
well as it should be.
BTW, normally these motor controllers are designed by using a driver with
high-side capabilities. p-ch mosfets generally have a much larger R_ds(on)
than similar n-ch and so it is better to use n-ch's instead of p-ch's for
the high side. This requires special driving circuitry though but generally
is better. (basically you have to generate a voltage larger than your supply
voltage to drive the high-side n-ch mosfets. There are dedicated IC's to do
this that cost a few dollars and some have significant driving capabilities
for paralleling(much more so than that uC).
news:ei9qt6p235hr6orqnrkt3j2mp37d83u6uu@4ax.com...
On Wed, 25 May 2011 05:58:30 -0600, "Stretto" <Stretto@nowhere.com>
wrote:
Since the motor got very hot, it is more likely the problem was causedIf the mosfets themselves burned up then it was most likely due to cross
conduction where the high and low side mosfets were both turned on at the
same time and no safety protection prevented it(you can current sense on
the
mosfets to make sure no cross conduction occurs).
by the commutation somehow getting stuck. The windings in the motor
are very low resistance, so it would have a very similar effect.
Certainly. But I do not think that is what happened here. The MOSFETsIf the mosfets are hot and you throw some water on them they probably won't
like it.
normally are just barely warm to the touch after a flight, and they
were not submerged in water. The water must have seeped slowly in
under the heatshrink.
I understand that, and I was not really seeking help with the specificIt's difficult to say what the problem is when there is no real information
given.
troubleshooting. I was curious to see if anyone could explain why
these controllers seem to fail so reliably in contact with water. This
is the third one I have seen in a short time.
Indeed. But for R/C hobbyists, cost is important, so the simplestDC motor controllers can come in a wide variety of designs with some
more prone to catastrophes than others.
designs seem to be the most popular. In general, they all employ a
microcontroller (almost exclusively an Atmel) and a bank of MOSFETs
and a few passives to glue it together.
I have now removed all MOSFETs that are bad, and shuffled the restCan you determine if it is the mosfets themselves or the controller that is
the problem? Is it obvious what is broke or does it just not work?
around so that I have at least one on each rail on each phase. The
controller now runs properly on a low-power motor (hard disk spindle
motor), so only MOSFETs were broken. There is also a bipolar
transistor (gate drive for the high-side P-channels) that is seriously
scorched, but, amazingly, it seems to work.
The voltage from the multimeter is actually enough to turn them on,You can also check the mosfets to see if they are working or not by
applying
a gate voltage(possibly not a good idea in circuit unless you are careful)
and checking their conductivity.
but since there are many of them in parallel, it is tricky to find the
bad ones by measuring. I first removed all that had a short from gate
to either D or S. After that, there were only a few left, so it got
much easier.
There is a small heat sink, but I think it's mostly cosmetic. It isFor "water tight" boards you can apply an epoxy. If the components are
getting very hot and not designed for rapid cooling there is not much you
can do as it is a mechanical problem with the stresses of rapid cooling on
the cases. If it is just the mosfets then possibly a heat sink will help if
one doesn't exist.
placed under the shrink hose, it does not contact all the MOSFETs, and
it does not get particularly hot. If overloaded (usually due to a too
large propeller), though, they get really hot.
If you're interested, no problem. I have left the pictures at theirTake a pic of the board and post it?
original resolution, so they're about 2MB each.
Here's the power side, with the seven surviving MOSFETs:
http://home.c2i.net/w-479147/temp/top.jpg
Here's the logic side:
http://home.c2i.net/w-479147/temp/bottom.jpg
Notice the 6-pin dual transistor in the upper right corner. It looks
completely mangled, but it still seems to work.
The two 7806s are not really part of the controller. They are used to
supply the radio gear from the motor battery, so that no dedicated
receiver battery is needed. It is called a "BEC", a Battery Eliminator
Circuit.
The SO-8 at the bottom, covered in glue, is the 5V regulator for the
CPU.
-------------------------------------------
What maybe happening is there is not enough gate drive to drive all the
mosfets. This can cause cross conduction due to the mosfets not turning off
and on fast enough(you get times when they are both on on the same side).
This would be a controller issue and not the problem with the mosfets. Since
you say it has happened several times that is most likely the problem if the
drive circuitry is sub-par.
I can't tell what exactly the circuit is doing but it looks like the uC is
directly driving the mosfets(considering all those resistors). Mosfets are
not as ideal as one wishes and the biggest problem with paralleling them is
the increased gate capacitance. Basically you can think of a gate of a
mosfet as having a capacitor across it and it takes time to charge the
capacitor. As it charges the mosfet transitions from open to closed or vice
versa. The transition acts a resistor varying from R_ds(on)(for your mosfets
it is 7.5mOhms) to some very large value. As current is flowing through the
mosfet the resistance causes significant thermal dissipation. The goal is to
have very quick transition so there is less time for the mosfet to heat up.
Fast transitions require low gate capacitance. When you parallel mosfets you
increase the effective gate capacitance(as seen by the driver) which slows
all the transitions down for each mosfet.
The design parallels 5 mosfets per leg. Each mosfet has 7.5mOhms so the
total resistance is 1.5mOhms but the gate charge is 105*5(*2) = 525nC. These
are best case. If the drive voltage is lower than 10V that 7.5mOhms will
increase which increases heat dissipation(but you said it wasn't getting too
hot to the touch so the drive voltage maybe ok all the incidences happen
when you are losing power).
You could possibly use 1 mosfet per leg instead of 5 by finding a better
mofset.
http://www.fairchildsemi.com/ds/FD%2FFDMS7650.pdf
While the wrong package it has about the same ratings or better(from what
I've checked).
http://www.vishay.com/docs/69063/si7137dp.pdf
For pch it's not as good but may work(if you use better nch's(lower R_ds(on)
then you can use worse pch if necessary).
The main thing you need to work out is if the controller really is failing
because it gets wet or if it's coincidence. There is only 1 way a mosfet is
going to fail in the way you are using it and it's overheating(I'm sure you
know there are other ways to ruin them such as ESD but these effects
shouldn't occur in SOC). For an h-bridge this will happen only due to cross
conduction issues(assuming it was properly designed for the rated load and
for a motor it generally is not meant run stalled).
Cross-conduction either occurs because the controller itself is
malfunctioning and not synchronizing the switching properly or because it is
not properly able to drive the mosfets.
Possible reasons: Stalled motor(draws more current), low power(increases
cross conduction and R_ds(on)), malfunctioning controller(sync issues =>
more cross conduction). Water(not sure but this is not part of the SOC).
Note that significant cross conduction should only occur when changing
polarity/reversing the motor. But if the controller or power is failing that
it will more likely occur. If you are drastically changing the polarity of
the motor(or the controller thinks you are) then it may be trying to reverse
the polarity very often which will increase power. So in that case it could
be an issue with the input to the controller(the controller should be able
to prevent this quite easily).
Hopefully I've given enough information that you might be able to figure out
what happened.
PS. That dual transistor you mentioned may be a clue to the cause. I see 2
others that look identical(I guess thatâs a diode above each one). I don't
know what they are doing but possibly the transistor is going back causing
the mosfets to subsequently fail. You did say it's working but maybe not as
well as it should be.
BTW, normally these motor controllers are designed by using a driver with
high-side capabilities. p-ch mosfets generally have a much larger R_ds(on)
than similar n-ch and so it is better to use n-ch's instead of p-ch's for
the high side. This requires special driving circuitry though but generally
is better. (basically you have to generate a voltage larger than your supply
voltage to drive the high-side n-ch mosfets. There are dedicated IC's to do
this that cost a few dollars and some have significant driving capabilities
for paralleling(much more so than that uC).