I am trying to use a SN75441 h-bridge in conjunction with an arduino in order to drive a DC motor forward and backward. Let me describe the setup and then the problem I am encountering.
I have an SN75441. Pins 1 and 16 are connected to the positive rail. (+5V) Pins 4, 5, 12 and 13 are connected to ground. Pin 8 is connected to a +9V power supply. Pins 2 and 7 are connected respectively to two of the arduino logic pins in output mode. They are alternating every few seconds being respectively H,L then L,H, then H,L again, and so on. You get the idea. Pins 3 and 6 are connected to the DC motor.
The +5 V positive rail for the SN75441 is supplied by the arduino. Everybody shares the same ground.
The setup is analogous to the one found here:
http://itp.nyu.edu/physcomp/Labs/DCMotorControl
My expectation for the behavior is that the motor will change direction every few seconds when Pins 2 and 7 reverse.
What actually happens is that the motor switches direction 0-3 times and then remains going in that direction forever. Now, what appears to be happening is that the arduino starts resetting very rapidly which means it keeps resetting to the logical output pins to their initial setting.
My question is two parts:
1) Why would that be happening?
2) How do I fix it?
Best Answer
That's probably happening because the motor's causing a brown out on the Arduino power supply, or causing a lot of noise on the RESET pin of the AVR. Make sure that you've pulled the reset pin to 5V with a smallish resistor (no greater than 10K). Since you're using an Arduino, though, its probably already on the board.
You may be able to confirm this by looking at MCUCSR immediately on reset, ie, right at the beginning of the main() function before you do anything else. You should also be able to see lots of noise on the AVR power supply pins (VCC vs GND), and probably also see the supply level dropping to a much lower voltage than what you'd expect. This is happening because even though you may be using separate supplies, when there's a sudden change the motor's current requirement, it's inductance will draw the power from wherever it can. This means that by the time the current from the separate power supply is available, it'd have dumped a whole lot of noise on the ground, and also pulled power through the IO pin of the atmega which is driving the SN754410, as well as through 5V at the 754410 itself.
The problem is exacerbated by the way in which you're driving the motors and what you're doing to them. By tying the 1,2EN input (pin 1) to 5V, you've ensured that the driver is continuously driving the motor. Each time the motor switches direction, it experiences the worst case condition possible, where it has to go from one extreme to the other extreme. The sudden change in direction of driving and the time the motor will take to respond causes a period during which its going to pump reverse EMF back into the driver and subsequently cause contamination at the ground. Additionally, since the situation is actually worse than a stall, the current consumed is something like 5 times higher than the steady state current required by the motor normally.
In order to fix the problem, there are a few things you can try.
Add diodes on the motor lines to prevent the reverse EMF from reaching the 754410. It'll cause some contamination to the 9V supply and the Ground, but that can be localized to near the motor and not let the AVR see it as much. You should have these in any case. For an example for how this can be done (from the datasheet of the L293, a similar IC), see :
(source: datasheetdir.com)
Add heavy decoupling on both the supply lines. Separately decouple the 5V for the AVR and the 5V for the SN754410. Use something like 10uF electrolytic/tantalum with 100nF ceramic in parallel with each, at least. Decouple the 9V supply with something much higher, say 100uF. Try to reduce the contact resistance of the wires bringing in the 9V supply.