Build a 4WD Arduino Remote Control Car: HC-05 Bluetooth & L298N Guide

Building an arduino remote control car is a rite of passage for embedded hobbyists, but most online tutorials fail at the power delivery and debugging stages. By pairing an Arduino Uno R3 with an HC-05 Bluetooth module and an L298N dual H-bridge, you bypass the line-of-sight limits of IR remotes and the complex pairing routines of 2.4GHz NRF24L01 transceivers. This guide provides a table-forward, bench-tested approach to wiring, coding, and troubleshooting a 4WD Bluetooth rover.

Power & Torque Spec Sheet: Matching Motors to Drivers

Before cutting a single wire, you must understand the electrical limits of your drivetrain. The most common failure in DIY rover builds is pairing high-stall motors with under-specced drivers or weak batteries. The table below outlines the real-world operating parameters for the standard yellow TT gearmotors and the L298N driver.

Exact Parts List & Board Variants

This build specifically targets the Arduino Uno R3 (ATmega328P DIP or SMD variant). While the code will compile for the Nano or Mega, the physical pinout and power routing below assume the Uno R3 form factor.

• Microcontroller: Arduino Uno R3 (ATmega328P).
• Motor Driver: L298N Dual H-Bridge Module (Red board with onboard 7805 5V regulator).
• Communication: HC-05 Bluetooth Module on ZS-040 breakout board (includes 3.3V LDO and LED).
• Chassis & Drivetrain: 4WD Acrylic Chassis Kit with 4x TT Gearmotors and rubber tires.
• Power Supply: 2S LiPo Battery (7.4V, 1500mAh, minimum 25C discharge) OR 6x AA NiMH battery holder (7.2V nominal). Never use a 9V PP3 alkaline battery; its high internal resistance will cause immediate brownouts under motor load.
• Passives: 1kΩ and 2kΩ resistors (for HC-05 RX voltage divider).
• Hardware: M3 brass standoffs, M3 screws, female-to-female and male-to-female DuPont jumper wires.

Pin Mapping & Wiring Matrix

We use SoftwareSerial on pins 10 and 11 for the HC-05. This leaves hardware pins 0 and 1 free for the USB Serial Monitor, which is critical for debugging. For a deeper look at software serial limitations, refer to the official Arduino SoftwareSerial documentation.

Assembly & Wiring Steps

1. Prepare the L298N Power Jumper: Locate the 5V jumper cap next to the power terminals on the L298N. Because our 2S LiPo maxes out at 8.4V (well below the 12V threshold), leave this jumper ON. The onboard 7805 regulator will step the battery voltage down to 5V to power the Arduino Uno via the VIN pin.
2. Wire the Battery: Connect the LiPo positive (red) to L298N +12V (labeled VCC on some boards) and negative (black) to L298N GND. Do not connect the battery yet.
3. Build the Voltage Divider: The HC-05 RX pin operates at 3.3V logic. Feeding 5V from the Arduino TX pin will eventually fry the Bluetooth IC. Connect a 2kΩ resistor from HC-05 RX to GND, and a 1kΩ resistor in series between Arduino Pin 11 and HC-05 RX.
4. Connect the Motors: Wire the left-front and left-rear motors in parallel to L298N OUT1 and OUT2. Wire the right-front and right-rear motors in parallel to OUT3 and OUT4. Polarity dictates forward/reverse; if a wheel spins backward, swap its two wires.
5. Bridge the Grounds: Run a wire from the L298N GND terminal to one of the Arduino Uno GND pins. Without a common ground reference, the PWM and logic signals will float, causing erratic motor twitching.
6. Mount and Route: Secure the Uno and L298N to the acrylic chassis using M3 brass standoffs. Keep high-current motor wires separated from the low-voltage HC-05 signal wires to prevent EMI interference.

Complete C++ Control Code

This code targets the Arduino Uno R3. It uses hardware PWM on pins 5 and 6 for smooth speed control and SoftwareSerial for Bluetooth communication. Upload this via the Arduino IDE (ensure board is set to Arduino Uno and port is correct).

#include <SoftwareSerial.h>

// --- Pin Definitions ---
#define ENA 5   // PWM Left Motors
#define IN1 4   // Dir Left A
#define IN2 7   // Dir Left B
#define IN3 8   // Dir Right A
#define IN4 9   // Dir Right B
#define ENB 6   // PWM Right Motors

#define BT_RX 10 // Arduino RX -> HC-05 TX
#define BT_TX 11 // Arduino TX -> HC-05 RX (via divider)

SoftwareSerial BTSerial(BT_RX, BT_TX);

const int BASE_SPEED = 210; // PWM duty cycle (0-255). 210 ~= 82% power

void setup() {
  // Initialize Hardware Serial for USB debugging
  Serial.begin(9600);
  // Initialize Software Serial for HC-05 (default baud is 9600)
  BTSerial.begin(9600);

  // Set motor control pins as outputs
  pinMode(ENA, OUTPUT);
  pinMode(ENB, OUTPUT);
  pinMode(IN1, OUTPUT);
  pinMode(IN2, OUTPUT);
  pinMode(IN3, OUTPUT);
  pinMode(IN4, OUTPUT);

  // Ensure car starts in a stopped state
  stopMotors();
  Serial.println("System Ready. Waiting for Bluetooth commands...");
}

void loop() {
  if (BTSerial.available()) {
    char cmd = BTSerial.read();
    
    // Echo command to Serial Monitor for debugging
    Serial.print("BT Cmd Received: ");
    Serial.println(cmd);

    switch(cmd) {
      case 'F': moveForward(); break;
      case 'B': moveBackward(); break;
      case 'L': turnLeft(); break;
      case 'R': turnRight(); break;
      case 'S': stopMotors(); break;
      default: 
        Serial.println("Unknown command. Ignoring.");
        break;
    }
  }
}

// --- Motor Control Functions ---

void moveForward() {
  digitalWrite(IN1, HIGH); digitalWrite(IN2, LOW);
  digitalWrite(IN3, HIGH); digitalWrite(IN4, LOW);
  analogWrite(ENA, BASE_SPEED);
  analogWrite(ENB, BASE_SPEED);
}

void moveBackward() {
  digitalWrite(IN1, LOW); digitalWrite(IN2, HIGH);
  digitalWrite(IN3, LOW); digitalWrite(IN4, HIGH);
  analogWrite(ENA, BASE_SPEED);
  analogWrite(ENB, BASE_SPEED);
}

void turnLeft() {
  // Stop left motors, drive right motors forward
  digitalWrite(IN1, LOW); digitalWrite(IN2, LOW);
  digitalWrite(IN3, HIGH); digitalWrite(IN4, LOW);
  analogWrite(ENA, 0);
  analogWrite(ENB, BASE_SPEED);
}

void turnRight() {
  // Drive left motors forward, stop right motors
  digitalWrite(IN1, HIGH); digitalWrite(IN2, LOW);
  digitalWrite(IN3, LOW); digitalWrite(IN4, LOW);
  analogWrite(ENA, BASE_SPEED);
  analogWrite(ENB, 0);
}

void stopMotors() {
  digitalWrite(IN1, LOW); digitalWrite(IN2, LOW);
  digitalWrite(IN3, LOW); digitalWrite(IN4, LOW);
  analogWrite(ENA, 0);
  analogWrite(ENB, 0);
}

Debugging: First Three Things to Check

When your arduino remote control car fails to operate, do not start rewriting code. Hardware and power faults account for 90% of initial failures. Check these three items first:

1. Upload Fails with Sync Error

Exact Error String: avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00

Cause: The HC-05 module is physically connected to hardware pins 0 and 1 (TX/RX), blocking the USB-to-Serial chip from flashing the ATmega328P.

Fix: Disconnect the HC-05 TX/RX wires before clicking "Upload" in the IDE, or verify you are using the SoftwareSerial pins (10 and 11) as defined in the code above. Reconnect after flashing.

2. Car Twitches or Resets When Motors Engage

Symptom: The HC-05 LED drops connection, or the Arduino restarts the moment you send the 'F' command.

Cause: Severe voltage brownout. The 4 TT motors pull over 2A combined on startup. If you are using a standard 9V alkaline battery, its internal resistance causes the voltage to sag below the Arduino's 2.7V brownout detection threshold.

Fix: Measure the L298N VCC terminal with a multimeter while commanding the motors to spin. If it drops below 6.5V, replace the battery with a 2S LiPo or a fresh 6x AA NiMH pack. Ensure your LiPo has a C-rating of at least 20C (1.5Ah * 20 = 30A max burst capability).

3. HC-05 LED Blinks Rapidly, Phone Won't Pair

Symptom: The Bluetooth module LED flashes roughly 10 times per second. Your smartphone Bluetooth scanner cannot find "HC-05".

Cause: The module is stuck in AT Command Mode, or the baud rate is mismatched.

Fix: Check the EN (or KEY) pin on the ZS-040 breakout. If it is pulled HIGH (connected to 5V), the module enters AT mode and disables standard pairing. Leave the EN pin floating or tied to GND for normal transparent serial operation. The default pairing PIN is usually 1234 or 0000.

Extending or Simplifying the Build

Once your base rover is driving reliably, you can scale the complexity up or down based on your project goals.

To Simplify (Lower Cost & Weight):
Drop the 4WD chassis for a 2WD configuration with a rear caster wheel. Replace the bulky L298N with an L9110S or TB6612FNG motor driver. The TB6612FNG uses MOSFETs instead of BJTs, dropping the voltage loss from 2.5V down to roughly 0.5V, which yields significantly longer run times on smaller battery packs.

To Extend (Add Autonomy):
Mount an HC-SR04 Ultrasonic Sensor on a front bracket. Wire the Trig pin to Arduino Pin 12 and Echo to Pin 13 (via a 1k/2k voltage divider, as the Echo pin outputs 5V). You can modify the loop() to poll the distance every 50ms; if an obstacle is detected within 20cm, interrupt the Bluetooth command queue and execute an automated reverse-and-turn maneuver. For advanced builders, swapping the Uno and HC-05 for an ESP32-CAM allows you to stream low-latency FPV video over WiFi while controlling the motors via the ESP32's native PWM peripherals.