IBT-2 43A Motor Driver (BTS7960)

> [!IMPORTANT] > motorSpeed is set manually (on-canvas slider or Property Inspector) — it is not derived from > the RPWM/LPWM/R_EN/L_EN pin voltages at all.

Actuators8 blocksMicroPythonC++
IBT-2 43A Motor Driver (BTS7960)

At a glance

Pins and properties exactly as the circuit editor and simulator define this part. The text below explains how to use them.

Pinout

Pinout of the IBT-2 43A Motor Driver (BTS7960), drawn as in the circuit editor. Select a label to see that pin in the table below.

Pins

Pins of this part
PinLabelType
B_MINUSB-Ground
B_PLUSB+Power in
M_PLUSM+Power in
M_MINUSM-Power in
RPWMRPWMSignal in
LPWMLPWMSignal in
R_ENR_ENSignal in
L_ENL_ENSignal in
R_ISR_ISSignal out
L_ISL_ISSignal out
VCCVCCPower in
GNDGNDGround

1. Hardware Specifications & Pinout

The IBT-2 is a high-current dual BTS7960B H-bridge module (marked HW-039 on the real board, often just called "IBT-2"), built around two BTS7960B half-bridge power ICs (U2/U3) and a 74HC244D octal buffer (U1) that shapes the logic-level control signals. Rated 43A continuous.

  • Motor Supply Voltage: 6V to 27V, via the top screw terminals — completely separate from logic power.
  • Logic Voltage: 5V (VCC/GND on the bottom header).
  • Pin Configuration — 4 top power screw terminals + 8 bottom logic header pins:
    • B- / B+: Motor power supply input (from a separate battery/PSU — never your board's own power pin).
    • M+ / M-: Motor terminals — wired straight to the motor.
    • RPWM: PWM input, drives the motor forward.
    • LPWM: PWM input, drives the motor reverse.
    • R_EN / L_EN: Enable pins for the forward/reverse half-bridges — must be driven HIGH for that direction to work at all.
    • R_IS / L_IS: Optional current-sense/fault outputs. Most projects leave these unconnected.
    • VCC / GND: 5V logic power and ground.

2. How it Works (Dual Half-Bridge H-Bridge)

  • Two Independent Half-Bridges: Unlike a single-chip driver (L298N), the IBT-2 uses one BTS7960B chip per direction — U2 handles forward current, U3 handles reverse. Each is a full high-side+low-side switch pair on its own.
  • PWM + Enable, Not Direction Pins: There's no separate "direction" pin. Speed and direction are set together: drive RPWM with a PWM signal (LPWM at 0) to go forward, or drive LPWM (RPWM at 0) to go reverse. R_EN/L_EN must both be HIGH for the corresponding side to respond at all — they're a hardware-level safety enable, separate from the PWM duty cycle.
  • Never Drive Both Sides At Once: Setting both RPWM and LPWM active simultaneously would fight the two half-bridges against each other. Every real driver pattern (and every Blockly block below) always zeroes the inactive channel before driving the active one.

3. Component Properties

The IBT-2 now has a real simulated component (ibt2_motor_driver) — drag it onto the Circuit Canvas from the Components palette. It exposes:

  • Motor Speed & Direction (motorSpeed) — range -100 to 100%, default 0. Negative = reverse, positive = forward, 0 = stopped.
  • Motor Supply Voltage (vccMotor) — range 6V–27V, default 12V.

[!IMPORTANT] motorSpeed is set manually (on-canvas slider or Property Inspector) — it is not derived from the RPWM/LPWM/R_EN/L_EN pin voltages at all. Checked ibt2_motor_driver's state() and spice.build() directly, and searched the whole simulator engine (GoldSimEngine.ts, the MicroPython/RP2040 shims) for anything reading those four pins or reacting to a motor-driver marker — there is none. Compare to the Servo (Chapter 6.4) or Buzzer (6.2), where a real PWM duty cycle written by your compiled program genuinely drives the simulated behavior. Here, a real program using the Blockly blocks below (Section 5) generates correct, real hardware code — but running it in the Circuit Simulator has zero effect on the simulated motor. The only way to see the simulated H-bridge respond today is to drag the on-canvas slider or edit the property directly.

All twelve pins are wired: B+/B- and M+/M- carry the motor power path (see Section 4's electrical model), VCC/GND power the logic side, and RPWM/LPWM/R_EN/ L_EN/R_IS/L_IS are present as real pins you can wire to — they just don't currently feed back into the simulation (per the note above).


4. Simulator Behavior

With the component placed and the circuit running:

  • Drag the horizontal slider below the component (visible only during simulation, -100% to +100%) to set motorSpeed directly. A status readout next to it shows FWD <n>% / REV <n>% / STOPPED 0%, color-coded (green forward, blue reverse).
  • Click STOP to zero the speed instantly.
  • A live text readout shows IBT-2 43A | Motor: FWD <n>% / REV <n>% / IDLE continuously while powered (logic VCC above 3.0V) — always-visible, not a hover-only tooltip. A LOW LOGIC VCC fault triggers between 3.0V and 4.5V on the logic supply.
  • Electrical model: the motor power path is a real dual-diagonal full H-bridge — driving forward closes the B+→M+ / M-→B- diagonal (≈32mΩ per switch when active, 100kΩ when off); reverse closes the other diagonal (B+→M-/M+→B-), so current genuinely reverses through the simulated motor rather than just toggling one fixed-polarity path. A 470µF bulk capacitor (with a 100kΩ bleed resistor) sits across B+/B-, and all six logic pins (RPWM/LPWM/R_EN/L_EN/R_IS/L_IS) present a real 100kΩ input impedance — but as Section 3 explains, none of that logic-side wiring currently influences which diagonal is active; only the motorSpeed prop does.

5. Supported Blockly Blocks

Drawing the blocks…

IBT-2 43A Motor Driver (BTS7960) — OMS Parts