Need Help? +44 (0) 123 4567
You can add your content here.

DC Controllers

Filters
Featured
Popularity
Date
Set Ascending Direction
View as Grid List
Items 1-24 of 34
24
36
48
60

A dc motor driver module category covers several control styles, from dual H-bridge boards for reversing to one-way MOSFET switches and standalone PWM speed controllers. H-bridge drivers handle reversing motors, while one-direction loads can use a single MOSFET switch instead. Small battery robots usually fit TB6612FNG or DRV8833-class drivers, while higher-power 12–24 V builds often step up to BTS7960-class hardware. L298N remains common in tutorials, but its inherent voltage drop makes it a weaker fit for low-voltage battery projects.

Page
24
36
48
60

How to choose the right DC motor controller in 3 decisions

Stall current, not running current, is the number that kills undersized drivers. If you do not have a measured figure, plan around startup or stall current being roughly 5–10× the motor’s rated current.

Need / load type Reverse needed? Best controller type Product examples on this page Not the right choice when
Fan, pump, heater, or other one-way brushed DC load No Single MOSFET switch module IRF520 MOSFET motor driver module Not the right choice if you need forward/reverse, or if you are using 3.3 V logic and expecting the IRF520 to switch fully
Small 2WD or 4WD robot with two brushed DC motors Yes Dual H-bridge motor driver TB6612FNG dual motor driver, DRV8833 dual motor driver board, MX1508 compact dual motor driver Not the right choice if motor stall current exceeds the board’s real continuous range
Older Arduino tutorial build or wall-powered classroom project Yes Legacy dual channel dc motor controller L298N dual-channel motor driver, L293D Arduino motor shield Not the right choice for low-voltage battery robots where voltage drop matters
Tiny low-power motion control with limited pins Usually yes I2C motor driver MiniMoto DRV8830 I2C motor driver Not the right choice for general robot drive loads; it is a low-voltage 2.75V–6.8V board with 9 selectable addresses for small loads
High-current brushed motor that still needs reversing Yes High-current H-bridge motor controller BTS7960 high-power motor driver, VNH2SP30 Monster Motor Shield Not the right choice for brushless motors, and not the right choice if you only need one-way manual speed control
No-code speed control for a brushed DC motor No reverse built in Standalone PWM controller 10A PWM motor speed controller Not the right choice if you need MCU control, reversing, or a brushless motor; this 12V–40V controller adjusts duty cycle from 10% to 100%
Stepper motor Different category A4988/DRV8825-class stepper driver — Do not buy L298N, TB6612FNG, or similar brushed DC drivers for stepper projects
Brushless motor Different category ESC or BLDC controller — Do not buy a brushed DC H-bridge for BLDC loads

If you need forward/reverse control, you need an H-bridge driver. If you only need one-direction speed control for a fan, pump, heater, or similar load, a single MOSFET switch is simpler and cheaper than an H-bridge. For shoppers leaning toward a modern small-motor board, see how a modern dual H-bridge is wired and controlled from Arduino.

Small robot drivers: L298N vs TB6612FNG vs DRV8833 vs L293D

Driver family Product example Motor supply range Current class Voltage-drop / efficiency takeaway Control-interface takeaway Best fit
L293D L293D motor shield for Arduino — 0.6A per channel Legacy bipolar driver, so efficiency is not its strength Shield-first format for Uno or Mega builds Very small motors and quick shield-based prototypes
L298N L298N motor driver module 5–35V input Listed up to 2A per channel, but about ~1 A continuous is the realistic planning number with the module heatsink Community consensus is to skip the l298n motor driver module for most low-voltage battery builds because its BJT design drops about 2–5 V and runs hot ENA/ENB enable pins are familiar in older tutorials Older tutorials, higher-voltage wall-powered builds, and simple legacy projects
TB6612FNG TB6612FNG dual motor driver Up to 15V motor supply 1.2A average, 3.2A peak MOSFET-based, so losses are typically around 0.2–0.5 V instead of the much larger L298N drop IN1/IN2 plus a dedicated PWM pin per motor Small robots that want easy code porting, high PWM frequency, and up to 100kHz PWM
DRV8833 DRV8833 dual DC motor driver 2.7V–10.8V 1.5A RMS per channel, 4A peak Also MOSFET-based, with roughly 0.2–0.5 V loss and better low-voltage behavior than L298N Modulates the two IN pins and needs 2 PWM-capable pins per motor; adds short brake and sleep Low-voltage battery robots needing protection features and sleep mode
MX1508 MX1508 1.5A dual motor driver 2.8V to 10V 1.5A class Compact low-voltage option for space-constrained builds Simple small-module format Tight layouts where the 24.7 x 21.5 mm footprint matters

TB6612FNG and DRV8833 are the usual modern replacements for L298N because MOSFET-based drivers waste far less voltage. The split between them comes down mainly to supply range and pin budget. TB6612FNG is the better fit when you want up to 15V motor supply, 1 PWM pin per motor, and very high PWM frequency, while DRV8833 fits 2.7V–10.8V systems that benefit from short brake and sleep. They are not drop-in interchangeable despite marketplace claims.

For many ESP32 robot builds, TB6612FNG and DRV8833 are the safer 3.3 V logic-friendly choices. L298N still makes sense mainly when you are following older tutorials or using a higher-voltage wall-powered build where the drop matters less. It becomes a weaker choice once motor stall current goes above about 1.5 A or the project depends on getting nearly full battery voltage to 5–6 V motors. If you choose DRV8833, these DRV8833 wiring and control examples are the right next step.

High-current and no-code control: BTS7960, VNH2SP30, or a standalone PWM box

Option Reverse control? Voltage range Current reality takeaway Best for Main caution
BTS7960 Yes Listed 5V to 27V; safer planning range is 6–27 V “43A” is not a realistic continuous-use figure; buyers commonly plan around about ~10–20 A continuous with heatsinking and airflow High-current brushed motors that still need reversing Needs careful wiring, cooling, and realistic current expectations
VNH2SP30 shield Yes 5.5V–16V Rated 30A peak and 14A continuous, but real-world discussion often treats it closer to 5–10 A per channel Arduino-based high-current motion builds that want shield format and current sensing Legacy path, clone half-bridge failures appear in reports
10A PWM controller No 12V–40V Rated 400W max, 8A continuous, 10A peak; cheap PWM boxes are often criticized for inflated amp labels Manual speed control with no code Not for brushless motors, not reverse-polarity protected, and vulnerable to inductive stall surges

If the load is one-direction only and manual control is fine, the PWM box is simpler than an H-bridge. If forward/reverse is required, choose BTS7960 or VNH2SP30-class hardware instead.

The BTS7960 high-power motor driver is the right call when you need a 12v dc motor driver board for a larger brushed motor and direction control still matters. It is listed for 5V to 27V operation with PWM up to 25 kHz, but 6–27 V is the safer planning range. The VNH2SP30 Monster Motor Shield covers the same general use case in shield form, with current sensing proportional to motor current, 30A peak, 14A continuous, and a 5.5V–16V range. For no-code control, the 10A DC motor PWM speed controller is the straightforward option for 12V–40V brushed motors with 10%–100% duty-cycle adjustment, but it is not the right tool for brushless motors or high-inrush trolling-motor-style loads. If your project needs an MCU in the loop, these Arduino boards are the natural match for module-based motion control, and this guide shows how to wire and control a high-power BTS7960 from Arduino.

Compatibility checks that prevent the most common mis-buys

  • The IRF520 MOSFET driver board is not a logic-level MOSFET module. It is specified around a 10 V gate and can half-open at 3.3 V, which leads to heat, low output voltage, and unreliable switching. Its product listing targets loads up to 24V and up to 5A, but that “5A” is not a realistic target with low gate drive, and a heatsink cannot fix a half-open gate.
  • For modern 3.3 V microcontrollers, especially ESP8266 builds, TB6612FNG and DRV8833 are the safer small-motor choices.
  • The MiniMoto DRV8830 I2C motor driver runs only at 2.75V–6.8V. It suits low-voltage motors and I2C-controlled motion, not general dual-motor robot drive loads.
  • On L298N boards, ENA and ENB are often jumpered HIGH. If that enable setup is wrong or misunderstood, speed control appears broken. If you still want L298N for a legacy build, review these L298N enable-jumper and wiring basics.
  • TB6612FNG will stay “dead” until the STBY pin is pulled high to exit standby mode.
  • Shared ground between the MCU and driver is mandatory even when motor power and logic power come from separate supplies.
  • Bulk input capacitance in the 470–1000 µF range plus 100 nF ceramic capacitors across brushed motor terminals is a common add-on plan for reducing startup sag, back-EMF spikes, and EMI.
  • BLDC fans and some suppression-heavy loads may sing, twitch, or misbehave on PWM. In those cases, a buck converter is often a better fit than a dc motor driver module or h bridge motor controller.
  • Thermal planning still matters. DRV8833 may need a heatsink above 0.6A motor current, L298N runs hot as load rises, and high-current modules need airflow long before their headline numbers.

FAQs on DC Motor Controllers

Which spec matters most when choosing a motor driver?

The driver’s continuous current must meet or exceed motor stall current, not running current, and stall or startup current is often 5–10× the motor’s rated current. That is the survival spec for the driver. Then check that the supply voltage fits the board and that the controller type matches the job: H-bridge for reversing, MOSFET switch for one-way loads.

Is L298N still worth buying?

Yes — L298N remains usable for older tutorials and higher-voltage wall-powered projects, but its inherent 2–5 V drop makes it a poor choice for low-voltage battery motors. It still earns a place when you want maximum tutorial coverage or need a simple legacy board, but it is not the right pick for 5–6 V robot builds where every volt counts.

Will the IRF520 module work with ESP32 or other 3.3 V boards?

No — IRF520 is not a logic-level MOSFET, is specified around a 10 V gate, and can run hot or under-drive the load at 3.3 V. It may appear to switch, but it often does so inefficiently enough to cause low motor voltage and overheating. For small brushed motors on 3.3 V control logic, TB6612FNG or DRV8833 is the safer purchase.

Do I need an H-bridge, or is a simple MOSFET switch enough?

Reversing requires an H-bridge, while one-direction loads like fans, pumps, LEDs, and heaters can use a single MOSFET switch instead. The switch route uses fewer pins, costs less, and avoids paying for direction control you will not use.

Is the BTS7960 really a 43A motor driver?

No — 43A is a headline or peak-style figure, and buyers commonly plan around about 10–20 A continuous with heatsinking and airflow, typically in the 6–27 V range. That makes it useful for larger brushed motors, but it should not be treated as a true 43A continuous module.

Can these DC motor controllers run a stepper motor?

Only in a basic sense — L298N or TB6612 can spin a 4-wire stepper without current limiting, but they run hot and underperform, so A4988/DRV8825-class stepper drivers are the right choice. Stepper projects need current-controlled drivers, not the brushed DC boards in this category.

Why does a motor sometimes run on a battery but not through the driver?

The usual causes are L298N voltage drop on 5–6 V supplies, missing ENA/ENB enable setup, lack of common ground, and supply sag under stall current. If the motor spins directly from the battery but not through the driver, the problem is often sizing, voltage loss, or wiring setup rather than the motor itself.

Glossary

H-bridge
— A circuit that drives current through a motor in either direction, which is what makes forward and reverse control possible.
Logic-level MOSFET
— A MOSFET that turns on properly from 3.3 V or 5 V logic, which is the key detail the IRF520 lacks.
Stall current
— The maximum current a motor can draw at startup or when blocked, and the figure your driver must survive.
Voltage drop
— The amount of supply voltage lost inside the driver itself, which directly affects motor speed and torque on low-voltage builds.
Brake vs coast
— Brake shorts the motor terminals for a fast stop, while coast lets the motor freewheel down.
Common ground
— A shared electrical reference between the controller board and the motor driver, required for control signals to work reliably.
STBY / standby
— A control pin state that disables the driver until released, as on TB6612FNG boards that need STBY pulled high.
Current sense
— An output proportional to motor current, useful for monitoring load or adding software current limits on higher-power drivers.
To Top
Help
Shop
Account
0 Cart