Description: The TB6612FNG motor driver can control up to two DC motors at a constant current of 1.2A (3.2A peak). Two input signals (IN1 and IN2) can be used to control the motor in one of four function modes - CW, CCW, short-brake, and stop. The two motor outputs (A and B) can be separately controlled, the speed of each motor is controlled via a PWM input signal with a frequency up to 100kHz. The STBY pin should be pulled high to take the motor out of standby mode.
Logic supply voltage (VCC) can be in the range of 2.7-5.5VDC, while the motor supply (VM) is limited to a maximum voltage of 15VDC. The output current is rated up to 1.2A per channel (or up to 3.2A for a short, single pulse).
Board comes with all components installed as shown. Decoupling capacitors are included on both supply lines. All pins of the TB6612FNG are broken out to two 0.1" pitch headers; the pins are arranged such that input pins are on one side and output pins are on the other.
Based on 13 ratings:
1 of 1 found this helpful:
Since all of our students have iPads, we use the Light Blue Bean Arduino compatible microcontroller in our Physical computing class. This means that we need a motor driver that operates at a 3v logical voltage to get a signal from the bean.
This chip seemed to be the best fit for us.
I do wish there was a way to get the chip in a style that could be easily put into a breadboard without having to solder headers on.
Seems like the price could be a little lower.
Also, the standby pin is not necessary for our needs, but in order for the chip to work, you have to wire Standby to 3v, adding a little bit of complexity for novice students.
Ideally, what I would like is a version of the L293D chip that will operate at 3v logic, but this will meet our needs for now.
2 of 2 found this helpful:
I used the TB6612FNG motor driver as part of a 24 motor life test stand. The motors are switching direction every 100ms causing a current spike of > 2 amps. The test has been running continuously for a week with out any issues. Each of the TB6612FNG motor drivers worked right out of the box saving me a lot of time.
5 of 5 found this helpful:
I’ve owned two of these motor drivers. I’ve used them to drive a self-balancing robot and the rover 5 chassis. I’ve never ran into any problems with it. For the rover 5, I keep each treads' two motors in sync by simply hooking them up together from one motor output. Perhaps this limits the bot’s speed, but it’s good enough for me.
I’ve controlled the driver with an assortment of microcontrollers: Arduino Uno, Arduino Mega 2560, bare atmega328, bare attiny84. I’ve also powered the driver with rechargable AAs, regular AAs, and a 7.4V Li-Poly battery (sold here @ sparkfun). All of which work as expected.
Works just as expected.
I was doing a little DYI RC car and I needed something to control the motors with. The motors were salvaged from something else and way underpowered but the driver did exactly what it was advertised to do. I’ll be getting some better motors and trying again soon. The only thing that was a little tricky was soldering the headers on since it was so small, but that’s more my inexperience than anything.
The built-in 200K resistors make this just plain fun to use. No need to worry about hooking it up directly to your micro controller pins. However, I did notice one thing that seemed weird to me.
I used the same power source for both the motor and the logic side and I used a function generator to supply the PWM. When I switched off the power supply the motor kept turning very slowly and I realized that the PWM supply was running it. I checked it out and when the power supply was on the current running through the PWM line was 0.02mA. When I switched off the power supply the current jumped to 9.0mA.
I’m using this and an Arduino Pro Mini to control the drive motors of a Hexbug “Battle Spider”. Using the linked bildr tutorial it was easy to get everything wired up.
One problem with the bildr tutorial though: their provided move and stop functions don’t reset the PWM outputs. I was running a motor test to discover which direction the motors ran. After running motor A both ways and stopping I couldn’t run motor B without A running as well.
All that is needed is to analogWrite 0 to both PWM pins in the stop function.
This is a very easy to use motor driver. Using the bildr.org tutorial linked from the product page, it took me only minutes to get two motors running off of it using Python on a Raspberry Pi 2.
so nice to not have to worry about flyback diodes, smart control bits are great, worked like a charm and these are things that fall in the category of “should have one in my bin all the time”