Blog / MDDRC5: When to Use This RC Motor Driver (and When Not To)

Motor Driver

MDDRC5: When to Use This RC Motor Driver (and When Not To)

November 17, 2026 · 8 min read · Flouw Robotics

You want an RC robot driving this weekend. Not a coding project. Just a transmitter in your hands and two motors that do exactly what the sticks say. That's the job the Cytron MDDRC5 was built for.

But pick the wrong motor driver and you find out the hard way: a robot that stalls mid-push, a board that doesn't fit, or a week lost writing code you didn't need. This guide shows when the MDDRC5 is the right choice, when it isn't, and how to get it running in six steps.

TLDR

  • RC-only, small robot, want it driving today: get the MDDRC5. No code needed.
  • Bigger motors that pull more than 5A continuous: get the MDDRC10.
  • Sensors, autonomous mode or a USB gamepad: you need a controller board like the Motion 2350 Pro.
  • Setup: motors to M1/M2, battery to V+/V-, receiver CH1 to RC1 and CH2 to RC2. Steps below.
Cytron MDDRC5 RC motor driver board, angled view showing the screw terminals, RC input pins and USB-C port

What the MDDRC5 is

The MDDRC5 is a 2-channel DC motor driver made for RC. Your RC receiver plugs straight into it. There's no Arduino in between and no code to write. Power it up and drive.

  • Current: 5A continuous, 20A peak per channel
  • Input voltage: 7V to 30V DC (2S to 6S LiPo)
  • Size: 69.1 x 35.6mm, four 3mm mounting holes
  • Modes: Mixed (MIX) or Independent (IND), set with an onboard slide switch
  • Motor alignment: onboard potentiometers to balance forward and reverse speed
  • Test button: check motors and direction without a transmitter
  • LEDs: power, motor status, overcurrent (OC1, OC2) and error (ERR1, ERR2)
  • USB-C: update the firmware, or reprogram the board with your own code
MDDRC5 board layout with labels for the RC inputs, mode switch, alignment potentiometers, LEDs, buttons, USB-C port and motor and power terminals

MDDRC5 board layout. Image: Cytron.

When the MDDRC5 is the right choice

1. RC-only robots

If the robot is driven by a person with a transmitter, you don't need a microcontroller at all. The MDDRC5 reads the receiver and drives the motors. Fewer parts, less wiring, fewer things to break on match day.

2. 500g RC sumo and other small robots

In the 500g class every gram and every millimetre counts. The MDDRC5 is much smaller than the MDDRC10, so you free up space for tuning weights. The 20A peak handles the hard pushes and sudden direction changes in the ring.

3. First-time builders and fast builds

No code means a beginner can wire it, test it and drive it in one session. It's also a good backup plan for a team whose coded robot isn't ready before the competition.

4. Builders who want to grow into code later

Start with plug-and-play RC. When you're ready, connect USB-C and program the board yourself. Cytron publishes Arduino and CircuitPython examples for it. More on that below.

Illustration of a small RC sumo robot with an MDDRC5 board, two gear motors, a LiPo battery and an RC receiver inside a black body with a steel front blade

How an MDDRC5 fits in a small RC sumo build. AI illustration.

When to pick a different board

  • Bigger motors that pull more than 5A continuous: get the MDDRC10. Same RC plug-and-play idea, with 10A continuous and 30A peak per channel.
  • Autonomous robot with sensors: get the Motion 2350 Pro or URC10. You need a microcontroller to read sensors and make decisions.
  • RC with a USB gamepad instead of a transmitter: get the Motion 2350 Pro. The gamepad plugs into the board's USB host, so no receiver is needed.
  • Four motors on separate channels: get the Motion 2350 Pro. It has 4 motor channels built in.
  • One robot for both Auto and RC: get the Motion 2350 Pro. One program can switch between modes.

That last point is why our EduKit 7-in-1 and Predator Mini kits run on the Motion 2350 Pro. They have to do autonomous and RC with the same robot. If your robot only ever does RC, the MDDRC5 is the simpler path.

Check your motors' stall current before you choose. A motor that stalls against an opponent can pull far more than its rated current. Keep the 5A continuous limit in mind for long pushes, and step up to the MDDRC10 for bigger motors.

Not sure which driver fits your robot? Message us on Facebook with your motor model and battery. We'll tell you which board to use, free.

Getting it running

What you need

  • MDDRC5 motor driver
  • Two brushed DC gear motors, such as the GM25 980RPM or Pulse 850
  • An RC transmitter and receiver with standard PWM output
  • A 2S to 6S LiPo battery, such as the Gaoneng 850mAh 3S for a small robot
  • A LiPo balance charger and a LiPo checker
MDDRC5 wiring: RC receiver plugged into RC1 (throttle) and RC2 (steering), left and right motors on the motor terminals, LiPo battery on the power terminal

The full setup. RC1 is throttle, RC2 is steering. Image: Cytron.

Steps

  1. Wire it up. Left motor to M1A/M1B, right motor to M2A/M2B, battery to V+/V- on the green terminal. Plug receiver CH1 into RC1 and CH2 into RC2. In Mixed mode, RC1 is throttle and RC2 is steering. Check battery polarity twice before you plug in.
  2. Pick your mode. Set the slide switch to MIX or IND. Mixed mode drives the robot from one throttle channel (forward and back) and one steering channel. That's the usual choice for sumo and soccer robots. Independent mode gives each channel its own motor.
  3. Lift the wheels. Put the robot on a stand so the wheels can spin freely.
  4. Test without the transmitter. Use the onboard test button to check both motors run and spin the right way. If one spins backward, swap its two motor wires.
  5. Drive. Turn on the transmitter, then power up the robot. Push the throttle forward and check that the robot actually goes forward. If the throttle stick steers and the steering stick drives, just swap the two receiver leads on RC1 and RC2.
  6. Align the motors. If the robot drifts to one side at full throttle, turn the alignment potentiometer to slow the faster motor until it drives straight.

LiPo batteries can catch fire if they're punctured, overcharged or run too low. Use a LiPo checker, charge them with a proper balance charger, and never leave them charging unattended.

Cytron's Getting Started with MDDRC5 guide shows each connection and switch on the board.

Growing into code

Cytron's Arduino example for the MDDRC5 uses the Raspberry Pi Pico board setting in Arduino IDE, so if you've coded a Pico before, it will feel familiar. The example does RC mixing in just a few lines. This is the core of it, from Cytron's example:

// Differential-drive mixing.

int16_t leftCommand = constrain(throttle + steering, -255, 255);

int16_t rightCommand = constrain(throttle - steering, -255, 255);

Once you can edit this, you can add your own touches: a slower "precision" mode, softer acceleration, or different speed limits for each motor. The full Arduino and CircuitPython examples are on Cytron's MDDRC5 GitHub.

To put the original firmware back:

  1. Disconnect the battery, motors and RC receiver.
  2. Connect the MDDRC5 to your computer with a USB-C cable that carries data.
  3. Hold BOOT, press and release RESET, then let go of BOOT.
  4. A drive called RPI-RP2 appears. Copy the .uf2 firmware file onto it.
  5. The board restarts by itself when the copy is done. Don't unplug it while copying.

USB-C only powers the control side of the board. It won't run the motors, so you still need the battery to test them.

If it doesn't work

  • Both ERR LEDs keep double-blinking: the board isn't getting a valid RC signal. Check that the transmitter is on, the receiver is bound and its cables are in the right pins.
  • No lights at all: check the battery charge and polarity. The input needs at least 7V.
  • Throttle and steering are swapped: swap the receiver leads on RC1 and RC2.
  • Robot drives backward or turns the wrong way: swap that motor's wires, or reverse the channel on your transmitter.
  • Robot pulls to one side: adjust the alignment potentiometer.
  • Robot feels weak mid-match: check your battery charge first, then whether the motors are too big for 5A continuous.

FAQ

Do I need to know how to code?

No. Out of the box the MDDRC5 reads your RC receiver and drives the motors. Code is optional, for when you want to customize it.

Can the MDDRC5 run an autonomous robot?

It's built for RC. For a robot that reads sensors and decides on its own, use a controller board like the Motion 2350 Pro, which has motor drivers built in.

MDDRC5 or MDDRC10?

Start with your motors. If they stay under 5A continuous, the smaller MDDRC5 saves space and weight. If they pull more, or you're building a heavier robot, go with the MDDRC10.

What battery should I use?

Any 2S to 6S LiPo, since the board takes 7V to 30V. A single-cell (1S) battery is too low to run it.

Where can I buy one in the Philippines?

The MDDRC5 is available in the Flouw shop, and our team is one message away if you get stuck setting it up.

Ready to build?

Get your MDDRC5 from the Flouw shop and have your RC robot driving this weekend. Still deciding? Send us your motor and battery on Facebook and we'll help you pick the right driver.

Coaching a school team? Our 1-day robotics training takes students from zero to a competing robot in one day.

More from the blog

See all

Get new posts by email

Tutorials, build stories and tips from Flouw, straight to your inbox.

New posts go to the Gmail you sign in with. You can unsubscribe any time, from any email or from My account.