H-Bridge ESC + Radio is an integrated, programmable controller for an FPV RC car with a brushed DC motor. Its stated goal is to combine motor control and radio-related electronics on one board, reducing separate modules and wiring.
The project contains 48 components across 46 nets. The explanation below is based on its description, component inventory, and the capture of your screen—not a verified inspection of its schematic connections, routing, or firmware. No project changes were made.
Core components and how they interact
Table
Block
Identified components
Intended role and interaction
Motor power stage
IRLR7843TRPBF MOSFETs
Form the switching elements of the H-bridge, applying either polarity to the motor for forward/reverse operation. PWM can regulate average motor power.
Gate drive
IR2101SPBF drivers
Translate control signals into high-side and low-side MOSFET gate drive. Their support circuitry and timing are essential to safe switching.
Power input and storage
XT60-M, UVR1V102MHD, tantalum capacitors
Provide a battery connection and local energy storage to help accommodate motor-current transients. Exact capacitor placement and ratings were not checked.
Regulated supply
L7805CV
Provides a linear-regulated 5 V supply for compatible auxiliary loads. The actual loads and available current are unverified.
Auxiliary switching/support
BC547B, 1N5818, 1N4148, resistors
Likely serve signal conditioning, switching, or driver support functions; their specific roles require net-level inspection.
FPV video
Eachine TX805
A video-transmitter module for an FPV system. It does not by itself establish an RC command-receiver function.
User interface and connections
0.91-inch 128×32 I²C OLED, three-pin headers, screw terminal, other connectors
Support status display and external wiring. Header assignments and the motor connection were not verified.
Mechanical integration
M3 mounting holes
Allow attachment to a vehicle chassis or enclosure.
A programmable control block would coordinate motor commands, PWM, and display updates. The inventory provided does not establish the controller identity, radio-command interface, or firmware architecture. The project title suggests radio integration, but the confirmed named radio-related component is the FPV video transmitter.
Design and functionality
The intended signal chain is control command → programmable controller → gate drivers → MOSFET H-bridge → brushed motor. Battery power feeds the motor stage and auxiliary supply circuitry; the display and video transmitter provide operator feedback and FPV functionality.
An H-bridge can support forward drive, reverse drive, coasting, and electrical braking. Which modes this board actually implements depends on wiring and firmware. Safe operation requires preventing simultaneous conduction of the upper and lower MOSFETs in either bridge leg—otherwise the battery is effectively shorted through the power stage.
Key choices and trade-offs
Discrete MOSFETs and gate drivers: Offer flexibility in power-stage design, but demand careful layout, switching control, and thermal validation compared with an integrated motor-driver solution.
Linear 5 V regulation: Simple and potentially quiet, but dissipates approximately (battery voltage − 5 V) × load current as heat. A buck converter is generally more efficient for higher battery voltages or substantial auxiliary loads.
Single-board integration: Reduces wiring and connector count, but places sensitive control/video electronics near a noisy, high-current motor stage.
Brushed motor architecture: Avoids three-phase commutation complexity, at the cost of brush wear and commutator-generated electrical noise.
Challenges and performance considerations
No safe battery-voltage or motor-current rating can be established from the inventory alone. Key validation areas are:
Stall current and heating: MOSFET conduction loss, switching loss, PCB copper, connectors, and cooling must be sized for starting and stalled-motor conditions—not merely normal running current.
Switching integrity: Gate resistors, dead time, bootstrap circuitry, local decoupling, and compact switching loops govern reliability and EMI.
Braking transients: Depending on the switching mode, motor energy can raise the supply voltage. Battery acceptance, capacitor ratings, and transient protection need review.
Noise isolation: Motor switching and brush noise can disrupt control signals, the OLED, or FPV video unless return paths and supply filtering are well managed.
Fail-safe behavior: Loss of command, reset, or brownout should force a defined safe motor state. I have not verified that protection here.
Applications and improvements
The architecture suits FPV RC cars, small ground robots, and programmable brushed-motor platforms. Priorities for improvement are current sensing and hardware overcurrent shutdown, verified gate timing, temperature monitoring, supply-transient protection, and robust command-loss handling. An efficient auxiliary regulator and better separation/filtering of motor and video supplies may improve runtime and video quality.
Scaling to larger motors requires redesigning the complete current and thermal path—not simply fitting larger MOSFETs. Future firmware could add controlled acceleration, braking profiles, telemetry, and fault reporting once the controller and interfaces are confirmed.
Project state: Unchanged; schematic connectivity, PCB implementation, firmware, and operating limits remain unverified. Execution stopped because your ACUs ran out.
The component with the designator U2 is an IR2101, a high-voltage, high-speed power MOSFET and IGBT driver. It is manufactured by Infineon Technologies. This component is typically used to drive the gates of power transistors such as MOSFETs or IGBTs in applications like motor drives, power supplies, and other power control systems.
Key Features of the IR2101:
High-Side and Low-Side Driver: It can drive both the high-side and low-side MOSFETs. This is useful when controlling the switching of an H-Bridge, as in your project.
Bootstrap Operation: It uses a bootstrap capacitor connected between the VB and VS pins to provide the necessary gate drive voltage for the high-side MOSFET.
Under-Voltage Lockout (UVLO): It ensures that the MOSFETs are not turned on until the supply voltage is high enough for reliable operation.
Matched Propagation Delays: This helps in minimizing the dead time between high-side and low-side switching, reducing the chances of short-circuiting through the MOSFETs.
Pin Functions:
VCC (Pin 1): Supply voltage for the control logic.
HIN (Pin 2) and LIN (Pin 3): Logic inputs for the high-side and low-side driver. These determine whether the corresponding MOSFET is on or off.
COM (Pin 4): Common ground for the logic and signal terminals.
LO (Pin 5): Output to drive the gate of the low-side MOSFET.
VS (Pin 6): Return path for the high-side gate drive, usually connected to the source of the high-side MOSFET.
HO (Pin 7): Output to drive the gate of the high-side MOSFET.
VB (Pin 8): Supply voltage for the high-side driver, derived from the bootstrap capacitor.
In your schematic, U2 likely interfaces to control both the high and low-side MOSFETs in an H-Bridge configuration, driving a brushed motor for your FPV RC car project.
meghajnbarhate
copilot
- High-Side and Low-Side Driver: It can drive both the high-side and low-side MOSFETs. This is useful when controlling the switching of an H-Bridge, as in your project.
- Bootstrap Operation: It uses a bootstrap capacitor connected between the VB and VS pins to provide the necessary gate drive voltage for the high-side MOSFET.
- Under-Voltage Lockout (UVLO): It ensures that the MOSFETs are not turned on until the supply voltage is high enough for reliable operation.
- Matched Propagation Delays: This helps in minimizing the dead time between high-side and low-side switching, reducing the chances of short-circuiting through the MOSFETs.
Pin Functions: