Common Robotics Wiring Mistakes (And How to Avoid Them)

I've built enough robots to have made all of these mistakes personally, usually at 11pm, usually with the robot doing something dramatic. This is the list I wish existed.

1. Undersized wire gauge for motor leads

The most common mistake. Someone specs 22AWG hookup wire because it's in the kit, runs it to motors that pull 2A each at stall, and wonders why the robot loses power under load. Rule: motor lead gauge should handle 2× stall current continuously. For our MDD10A setup with N20 motors at 0.8A stall each, 20AWG is minimum; we use 18AWG to leave headroom.

2. No common ground between logic and power

If your motor driver, motor power supply, and microcontroller don't share a ground, the PWM signal from MCU to driver is referenced to different potentials. The motor driver sees the signal as floating — the motor may spin erratically, not respond, or damage the driver input. Always connect GND from MCU to GND on the motor driver, even when they're on separate power rails.

3. Reverse polarity on LiPo

JST and XT60 connectors are not foolproof. JST-PH connectors can be forced backward with moderate pressure. XT60 are keyed but aftermarket plugs sometimes have manufacturing defects. Add a diode or an ideal diode circuit on the battery line, or at minimum double-check polarity with a multimeter before first connection. Reverse polarity on a LiPo can destroy the motor driver, MCU, and occasionally start a fire.

4. Motor driver current rating vs. peak current

L298N is rated 2A continuous per channel. N20 motors stall at 0.8A — so it seems fine. But L298N's thermal design is marginal at rated current. At 1.2A continuous with a 50% duty cycle and no heatsink, it throttles or fails within 20-30 minutes. The Cytron MDD10A handles this better because of its MOSFET design (lower Rdson = less heat). If you're using L298N (RP2350 kit), add the heatsink tab and don't run sustained loads above 1A.

5. I2C address conflicts

MPU-6050 (I2C address 0x68 or 0x69 via AD0 pin), SSD1306 OLED (0x3C or 0x3D), and many other common breakouts share the same default addresses. Put two of these on the same I2C bus without checking and the bus fails silently — neither device responds predictably.

# Scan for I2C devices on RP2350 (MicroPython)
import machine
i2c = machine.I2C(0, sda=machine.Pin(4), scl=machine.Pin(5))
devices = i2c.scan()
for d in devices:
    print(f"Found device at 0x{d:02x}")

6. Skipping strain relief on connectors

A robot moves. Wire joints that aren't strain relieved will fail at the solder joint after 100-200 flex cycles. On a mobile robot that may have thousands of cycles per day, that's a few days before intermittent failure starts. Use heat shrink over all solder joints, cable tie wire bundles to the chassis at regular intervals, and leave service loops (a little extra wire) at connectors so they're not under tension when assembled.

The Wiring Checklist We Run Before Every Maiden Power-On

• Verify battery polarity with multimeter before connecting
• Check all motor lead gauges against stall current spec
• Confirm common ground between all logic and power subsystems
• Scan I2C bus before powering sensors (catch address conflicts early)
• Inspect all solder joints under magnification or strong light
• Confirm strain relief on all connectors that will experience motion
• Measure supply voltage at the load, not just at the source (catches voltage drop)
• Dry-run with current-limited bench supply before LiPo on new builds