Wiring a robot without the magic smoke

Wiring a robot is the part nobody teaches in a course. It's craft, learned from blown components and confusing crashes. The good news: ten rules cover 95% of practical robot wiring. Get them right and your robot will be one of the rare ones that works on first power-up.

The ten rules

1. Star ground

All ground wires meet at one physical point — typically the battery's negative terminal or a dedicated bus bar. From there, fan out to every subsystem.

Why: if you daisy-chain grounds, currents flowing through one link create voltage drops in others (ground loops). MCU sees a "ground" that's actually 100 mV above motor "ground." Sensor readings drift; control gets weird.

Fix: never daisy-chain. Star.

2. Heavy wires for high current

Wire resistance produces heat and voltage drop. AWG sizing for typical robot currents:

Current	Min AWG
< 0.5 A (signals)	28 AWG
2 A (small motors)	22 AWG
5 A (medium motors)	18 AWG
10 A (BLDCs)	14 AWG
30 A+ (battery main)	10 AWG

When in doubt, go heavier. Wires don't get worse by being beefy.

3. Decoupling capacitors at every IC

Every MCU, sensor, and amplifier needs a 0.1 µF ceramic cap between its VCC and GND pins, as physically close as possible. This filters high-frequency noise.

For larger ICs (Jetson, big regulators): also add a 10–100 µF electrolytic or tantalum.

Skip these and your sensors get noisy, your MCU resets randomly, your I²C bus gets corrupted. They cost cents.

4. Bulk caps near power-hungry loads

A motor driver pulling 5 A pulses creates voltage dips on its supply rail. Add a large electrolytic (470–2200 µF) right at the driver's input pins. The cap supplies the dynamic current; battery supplies the average.

For BLDC drivers: 1000 µF per 5 A peak is a reasonable starting point.

5. Twisted pairs for differential signals

Long wires (more than ~30 cm) carrying high-speed digital signals (I²C, SPI, encoder quadrature) should be twisted pairs: signal + ground twisted together. Cancels EMI; reduces capacitive coupling.

For very long runs (1+ m), use shielded cable with the shield grounded at one end.

6. Separate power and signal grounds

Even with star grounding: route motor-current return paths separately from signal ground until they meet at the star point. A 5 A motor pulse running through a shared ground trace looks like noise to a sensor reading 50 mV.

7. Connectors with positive locking

Vibration unlatches bare jumper wires in minutes. Use:

• JST-XH or JST-PH: small signal connectors, latching.
• Molex Mini-Fit: medium-current power.
• XT60 / XT90: high-current battery connectors, polarized.
• Anderson PowerPole: lab/test setups.

Avoid: bare jumper-wire connections in any production robot.

8. Color-code consistently

Standard:

• Red = +V (any voltage).
• Black or White = ground.
• Yellow = signal/data.
• Green = digital ground (alternative).

Pick a convention; document it; never deviate. Future-you will thank you.

9. Fuse the battery

An inline fuse rated ~1.5× peak current sits between battery and main bus. If a wire shorts (when, not if), the fuse blows; the battery doesn't catch fire.

For 10A robots: 15A automotive blade fuse. Cents per fuse; the lithium pack survives.

10. Strain relief

Wires bend at connectors; they break at the bend. Add strain relief: glue the wire to the connector body, use heat shrink boots, or zip-tie to a nearby structural point.

Cable strain breaks are the most common silent failure on running robots.

The EMI rules of thumb

• Switching power supplies emit noise: keep sensors physically far from the regulator. Or shield.
• BLDC commutation creates noise spikes: route motor wires away from sensor wires; cross at right angles if you must.
• USB and cables: USB cables conducting noise into a computer is a real phenomenon. Use ferrite chokes if you see weird interference.
• Use shielded enclosures: aluminum or steel chassis significantly reduce radiated EMI. Wooden or plastic chassis: more EMI vulnerability.

Debugging a misbehaving robot

When your robot does something weird, in order:

1. Check power: actual voltage at the MCU pin, with motors running. Brownout?
2. Check ground: voltage between two ostensibly-grounded points. Should be < 50 mV.
3. Check decoupling caps: are they present? Soldered?
4. Check connections: every wire actually connected? Solder joint solid?
5. Check shielding: motor wires and sensor wires running parallel? Move them.
6. Check fuses: blown?

Two minutes per check; covers ~80% of "intermittent" robot bugs.

The best practice nobody follows

Document your wiring. Sketch the schematic in any tool (KiCad if you'll spin a PCB; pen-and-paper otherwise). Label every wire with what connects to what. Keep the doc with the robot.

When something breaks 6 months later, you'll thank yourself.

What kits get wrong

Many robotics kits ship with bare jumper wires + breadboards + no fuse + skinny power wires. They work for a demo. Then you add a heavy load; brownouts. Then a wire pops out; intermittent crashes. Then you replace components in frustration.

Step up to: terminal blocks, 18 AWG silicone wire, JST connectors, an inline fuse. The robot behaves dramatically better.

Exercise

Take any robot you've built. Audit the wiring against the ten rules. Star ground? Yes/no. Adequate wire gauge? Yes/no. Decoupling caps? Yes/no. (etc.) Fix the worst offender. Watch the robot become more reliable overnight.

Next

Jetson Orin for on-board AI — the heaviest component your power budget has to support, and the platform that runs most modern robotics inference.