TB6612FNG Motor Driver ICs, Modules and Robot Shields

TB6612FNG motor control: bare IC, dual-H-bridge board or platform-specific shield

Compare TB6612FNG surface-mount driver ICs, compact dual-motor breakout boards, Raspberry Pi motor HATs, WeMos D1 mini shields, Arduino-format motor/servo expansion boards and micro:bit boards. This mixed catalog also includes DRV8833 and L298N alternatives, other selectable chips and bundles with different soldering or quantities. A listing that mentions TB6612FNG is not a promise that every option contains that IC. Check the selected variant, interface and included hardware before buying.

What a TB6612FNG stage does

The TB6612FNG is a dual H-bridge motor driver used to control two suitable brushed-DC motor channels independently, or drive a compatible bipolar stepper by coordinating its two bridges under an appropriate controller. Logic inputs and PWM control direction, standby and output behavior; the driver does not measure position, generate a motion plan or replace a complete microcontroller. 'Four-way' in some board titles can refer to four half-bridge outputs, not four independently controlled DC motors. A module with two motor ports is not equivalent to a four-motor robot controller without additional drive hardware.

For each design, distinguish motor supply (VM), logic supply (VCC), MCU I/O levels and any separate regulator on a larger shield. One compact breakout listing quotes VCC 2.7–5.5V, VM to 15V and output currents of 1.2A average / 3.2A brief peak under its own stated conditions. These figures should not be applied to every board in the collection, or interpreted as guaranteed continuous current with both channels running in a hot enclosure. Consult the exact IC and PCB documentation for thermal dissipation, supply decoupling, startup/stall current and allowable duty cycle. Neither an 'upgrade over L298N' slogan nor a 'better' title substitutes for a measured load and voltage-drop comparison.

Choose the actual level of assembly

• Bare TB6612FNG IC: SSOP/TSSOP-24 chip listings offer five- or ten-piece packs and selected options on broader multi-model pages. A chip needs the proper PCB land pattern, soldering, decoupling and motor/logic connections; it is not a plug-in module or HAT. On a multi-model page 'TB9001FNG', 'TB9061FNG', 'TB6552FNG' and 'TB6608FNG' are separate selected ICs, not alternate labels for TB6612FNG. Another multi-chip listing places TB6612FNG next to TLC5928, SN74LVC4245 and SI4831, and another next to LM3478, AD620 and LM2901; the selected model decides what ships.
• Compact driver breakout: small TB6612 modules appear as one-, two-, three-, five-, ten- or thirty-board selections. 'Welded', 'weld', 'with Soldered PIN' and 'Unwelded' or 'Solderless' describe header-assembly options, not different chip functions. Confirm whether the headers are actually soldered, which side of the board is accessible, the input header orientation, and whether any additional regulator or connector is on the board. A standalone dual-motor module does not include the motor or MCU unless the particular listing says so.
• Raspberry Pi HAT: selected Pi-format boards pair a TB6612FNG motor stage with a PCA9685 PWM controller and I2C interface; one observed listing states a 40-pin Pi header, 3.3V logic, 6–12V VIN and an onboard 5V regulator. These are specifications of that HAT, not of the bare chip or every other shield. Verify Pi model, GPIO/header fit, I2C address selection, controller software, motor supply and whether a particular board can safely power its host. A PCA9685 is a PWM controller, not a high-current H-bridge by itself.
• WeMos D1 mini shield: a selected D1 mini-format motor shield advertises I2C-controlled dual-motor drive. Check shield generation, D1 mini header arrangement and I2C device requirements. It is not automatically pin-compatible with a generic TB6612 breakout or an Arduino UNO shield.
• Arduino-format motor/servo expansion: selected shields pair TB6612FNG motor drive with servo headers, PS2 connector or other board-level hardware. A Keyestudio description cites a TB6612FNG for two motors and two LM2596S-5.0V converter modules for servo-related power distribution. Its motor supply, servo rail and PS2 connector's 5V output must be checked separately; the shield is not a bare TB6612 module and servo headers are not extra H-bridge motor outputs. A 'Shield V2' listing calls out I2C; check its own PCB and controller interface rather than assuming direct STEP/DIR or simple GPIO wiring.
• micro:bit expansion: a Keyestudio breakout board and another PCA9685/TB6612 expansion board are presented for BBC micro:bit projects. These combine the micro:bit's control interface with board-level power distribution and motor outputs. Confirm edge-connector revision, power routing and software against the exact board; a micro:bit expansion board does not necessarily include a micro:bit.

Understand alternatives rather than assuming pin compatibility

Many product pages offer a choice of 'TB6612FNG' or 'DRV8833' on a similarly sized motor module. These are different IC families with their own pin maps, standby/sleep behavior, logic requirements, motor-supply ranges, current limits and thermal characteristics. A selected 'DRV8833 Red', 'DRV8833 Black' or 'DRV8833 Version / 10PCS' is not a TB6612FNG item. One listing titled 'TB6612 DRV8833 ...' has only DRV8833 Red/Black options, so its title alone cannot prove a TB6612 option is available there. A different multi-choice listing also offers L298N, MINI L298N, '2.5A driver module' and a larger L298 board. L298N's bipolar driver architecture, voltage drop and board form factor differ; those selections are not simply a color revision of TB6612FNG.

Descriptions claiming '1A', '1.2A' or a high peak current may refer to a different IC, test condition, per-channel metric or transient interval. The motor's stall current, supply voltage and thermal operating point determine suitability, not a family nickname. A green/red module color, 'original chip' claim or a generic 16-pin header reference cannot verify manufacturer origin or detailed specification. For a repaired PCB, compare exact part marking, footprint and pin functions rather than substituting based on a broad 'better than L298N' headline.

Motor and control-system selection checklist

1. Specify the load: identify whether the project needs one or two brushed-DC motors, a bipolar stepper or servo-control signal outputs. A PWM servo header does not directly supply the current of a DC motor.
2. Check actual variant: TB6612FNG versus DRV8833 or L298N; bare IC versus populated board; soldered versus unsoldered header; one board versus a 5/10/30-pack. 'TB6612 Package 1–8' labels require the individual package list to establish what is included.
3. Check electrical domains: compare motor supply, logic supply, MCU output levels, PWM/standby signals and any onboard regulator separately. A Pi HAT's 6–12V VIN statement is not a voltage specification for every TB6612FNG module.
4. Estimate real motor current: use starting/stall current as well as normal draw, channel count and duty cycle. Verify continuous dissipation on the selected PCB, board copper, airflow and power connector, not just the IC's brief peak figure.
5. Map the control interface: direct input/PWM breakout, I2C/PCA9685 HAT, WeMos shield or Arduino/micro:bit expansion may need different software and address/pin mapping. 'For Arduino' and 'for Raspberry Pi' are not universal plug-and-play guarantees.
6. Review physical integration: examine chip footprint, header orientation, HAT clearance, motor connector polarity, cable requirements and installed versus loose headers. Inspect selected product photos and documentation for the exact revision rather than assuming interchangeability between boards.
7. Plan safe transients and heat: braking, reversing and motor startup can stress driver and supply. Follow device-specific protection and power-routing guidance; this overview deliberately does not prescribe a universal wiring circuit for every motor or board.

Example buying paths

For a small MCU robot with two brushed-DC motors, start with a TB6612FNG dual-channel breakout and confirm motor stall current, logic interface, header finish and supply. For a Raspberry Pi smart car, pick an explicitly Pi-format PCA9685/TB6612 HAT and check its I2C/software and regulator arrangement. For a classroom D1 mini build, choose the platform's shield rather than assuming a bare breakout stacks onto the board. For PCB manufacturing, select the exact TB6612FNG IC variant and verify the package drawing. If the product offers DRV8833 or L298N instead, evaluate that architecture on its own merits. In all cases the selected option and its manufacturer-specific documentation, not this collection title, define the delivered item and electrical limits.