Servo Motor: What Is It? Sizing, Wiring, and Selection Guide

A servo motor is a closed-loop rotary actuator that uses positional feedback—typically an internal potentiometer or optical encoder—to precisely control angular position, velocity, and acceleration. Unlike a standard brushed DC motor that spins continuously or a stepper motor that moves in open-loop discrete steps, a servo continuously reads its actual shaft position and adjusts internal H-bridge power to eliminate the error between its current state and your target command.

For embedded builders using an ESP32, Arduino, or Raspberry Pi, servos are the default choice for robotic joints, camera gimbals, and automated valves because the motor driver and feedback loop are entirely self-contained. You simply send a pulse-width modulation (PWM) signal or a serial bus command, and the onboard electronics handle the heavy lifting.

The Core Mechanics: How Closed-Loop Feedback Works

Inside a standard hobby servo (like the ubiquitous TowerPro MG996R), you will find three core subsystems:

1. The DC Motor: Provides the raw rotational force.
2. The Gear Train: Steps down the motor’s high RPM into high torque at the output shaft. Gears are typically plastic (for cheap, light loads), brass (mid-range), or steel/titanium (high torque).
3. The Feedback and Control Circuit: A potentiometer physically linked to the output shaft measures the exact angle. An internal error amplifier compares this reading to the incoming PWM pulse width. If there is a discrepancy, the circuit drives the motor in the necessary direction until the error is zero.

Servo vs. Stepper vs. Brushed DC: Load Profile Matching

Treating servos and steppers as interchangeable is a common mistake that leads to stalled projects. Steppers excel at holding heavy static loads and precise open-loop positioning, but they lose torque rapidly at high speeds. Servos maintain torque across their speed curve and recover from missed steps, but they consume power continuously when holding against a load.

Sizing Rule of Thumb and Worked Load Example

Servo torque is universally rated in kg-cm (or oz-in for imperial) at a specific voltage (usually 5V or 7.4V). This rating represents the stall torque—the maximum force the servo can exert before it physically stops moving. You should never design a system that operates at stall torque.

The Rule of Thumb: Calculate your theoretical load torque, then apply a minimum 2x safety factor (3x for dynamic/impact loads) to select your servo. Operating a servo above 50% of its rated torque leads to gear stripping, overheating, and severe current spikes.

Worked Example: Robotic Arm Joint

Imagine you are building a robotic arm. The forearm is 15 cm long (from the joint axis to the center of mass of the payload). You need to lift a 500g (0.5 kg) payload.

1. Calculate Force: $F = m \times g = 0.5 \text{ kg} \times 9.81 \text{ m/s}^2 = 4.9 \text{ N}$.
2. Calculate Torque: $\tau = F \times r = 4.9 \text{ N} \times 0.15 \text{ m} = 0.735 \text{ Nm}$.
3. Convert to kg-cm: $0.735 \text{ Nm} \approx 7.5 \text{ kg-cm}$.
4. Apply Safety Factor: $7.5 \text{ kg-cm} \times 2.0 = 15.0 \text{ kg-cm}$.

The Pick: You need a servo rated for at least 15 kg-cm. A standard 13 kg-cm MG996R will overheat and fail prematurely. You must step up to a DSServo DS3218 (20 kg-cm) or similar 20+ kg-cm metal-gear unit to ensure reliable operation.

Wiring, Terminals, and Controller Demands

Standard PWM servos use a 3-wire interface. Wire colors generally follow the JR or Futaba standards:

• Brown or Black: Ground (GND).
• Red: Power (VCC). Typically 4.8V to 6.0V for standard servos, up to 7.4V (2S LiPo) for high-voltage (HV) digital servos.
• Orange, Yellow, or White: Signal (PWM).

For advanced projects requiring daisy-chaining or positional read-back, you must upgrade from PWM to a Serial Bus Servo (like the Robotis Dynamixel line). These use a half-duplex UART protocol (TTL or RS485) on a single data wire, demanding specific hardware serial pins and libraries, but they eliminate PWM jitter and allow you to read internal temperature and load metrics in real-time.

Failure Signatures: Hum, Overheat, and Stall

Servos fail in highly predictable ways. Recognizing these signatures saves hours of debugging:

• The "Hum" or "Jitter" (Hunting): The servo vibrates rapidly around the target position. Cause: Dirty internal potentiometer, mechanical backlash in the gear train, or an unstable PWM signal from the microcontroller (common on Arduino if using software-servos instead of hardware timers). Fix: Use hardware PWM (like ESP32's LEDC peripheral) and ensure a clean 5V power rail with a decoupling capacitor (470µF) near the servo.
• Silent Overheat: The servo is hot to the touch but not moving. Cause: The servo is being commanded to hold a position against a continuous gravitational load. The internal motor is essentially stalled, drawing maximum current to maintain the magnetic field. Fix: Redesign the mechanical linkage to be self-locking (e.g., use a worm gear) so the servo doesn't have to use power to fight gravity.
• Stripped Gears (Crunching Sound): Cause: Shock loading exceeding the gear shear strength, or binding in the mechanical linkage. Fix: Upgrade from plastic/brass gears to CNC steel gears, or add a mechanical hard-stop so the servo doesn't drive past its physical limits.

The Decision Tree: Pick Your Exact Motor

Stop guessing. Follow this decision matrix to select the exact part number for your embedded project.

The Default Recommendation

If you are building a general-purpose robotic arm or heavy-duty animatronic joint using an ESP32 or Raspberry Pi, and you do not need serial bus telemetry, default to the DSServo DS3218 (20 kg-cm). It operates on standard 50Hz PWM, utilizes a robust steel gear train, runs on a widely available 6V to 7.4V supply, and provides the exact torque sweet spot that prevents the premature failures common with cheaper 13 kg-cm alternatives. Pair it with a dedicated 5A buck converter set to 6.0V, and your drive system will run reliably for years.