Decoding Servo Pulse Width: Sizing, Wiring, and Selecting the Right Motor

The Core Metric: Decoding Servo Pulse Width and Position

When you command a microcontroller to move a robotic arm or pan-tilt camera, you aren't sending a target angle directly to the motor. You are sending a servo pulse width. Standard RC (radio control) servos operate on a 50Hz PWM (Pulse Width Modulation) signal, meaning a new control pulse is sent every 20 milliseconds. The actual position of the servo horn is dictated entirely by the duration of the HIGH state within that 20ms window.

The universal standard for positional servos maps a 1.0ms pulse width to 0 degrees, a 1.5ms pulse to the 90-degree center, and a 2.0ms pulse to 180 degrees. If you send a 1.25ms pulse, the internal potentiometer and control board will drive the DC motor until the horn reaches exactly 45 degrees, then apply braking current to hold it there.

Understanding this timing is critical because if your microcontroller's PWM timer drifts, or if your power supply sags and stretches the pulse width by even 50 microseconds, your servo will jitter or hunt for position. According to the Pololu RC Servo Guide, maintaining strict pulse width integrity is the difference between a smooth robotic joint and a vibrating, gear-stripping mess.

Motor Type Showdown: When to Pick a Servo Over Steppers or DC

A common mistake in embedded design is treating stepper motors and servos as interchangeable position-control devices. They are fundamentally different in how they generate torque and handle loads. Here is how they compare when you need precise angular movement.

Which motor fits your load profile? If your application requires moving a load to a specific angle, holding it there against gravity, and you don't want to wire a complex homing-switch routine, the RC Servo wins. Steppers require homing on boot to know their absolute position; servos know their position inherently via the internal potentiometer and the pulse width command.

Sizing the Servo: Load Profiles and Torque Margins

Servo torque is rated in kg-cm (kilogram-centimeters) or oz-in. This is a static stall torque rating measured at 1cm from the center of the output shaft. To size a servo correctly, you must calculate the dynamic load and apply a safety margin.

The Sizing Rule of Thumb: Calculate the worst-case static torque (Load Mass × Distance from Pivot), then multiply by 1.5 to 2.0 to account for dynamic acceleration, friction, and the fact that servos lose significant torque when moving at speed.

Worked Load Example

You are building a camera pan-tilt mechanism. The camera weighs 400g (0.4kg), and the center of mass sits 12cm away from the servo's pivot shaft.

• Static Torque: 0.4 kg × 12 cm = 4.8 kg-cm.
• Dynamic Margin (×1.5): 4.8 × 1.5 = 7.2 kg-cm.
• Minimum Required Servo: 7.2 kg-cm.

If you select a standard micro servo like the SG90 (rated at 1.8 kg-cm), it will instantly strip its plastic gears. A standard MG90S (2.2 kg-cm) will also fail. You need to step up to a standard-size metal gear servo. The TowerPro MG996R (rated at 11-13 kg-cm depending on voltage) or the DS3218 (20 kg-cm digital) are the correct choices here, providing the necessary headroom to accelerate the camera without stalling.

Wiring, Terminals, and Driver Demands

Standard RC servos use a 3-pin JST or Dupont connector. Identifying the terminals correctly is critical; reversing VCC and GND will instantly fry the internal control PCB.

What Driver/Controller Does It Demand?

A servo demands two things: a clean 50Hz PWM signal with precise 1-2ms pulse widths, and a high-current 4.8V to 6.0V power rail. A 15 kg-cm servo can draw 2.5 Amps at stall. Never power a standard or high-torque servo directly from an Arduino or ESP32's onboard 5V regulator. The voltage drop will cause a brownout, resetting your microcontroller mid-motion.

The Power Solution: Use an external UBEC (Universal Battery Eliminator Circuit), such as a Hobbywing 5V/6V 3A switching BEC, wired directly from your main battery pack to the servo's red and brown wires. Tie the BEC ground to the microcontroller ground to establish a common reference.

The Signal Solution: For AVR Arduinos, the built-in Servo.h library handles the 50Hz pulse width timing via hardware timers. However, if you are using an ESP32, the Espressif LEDC (LED Control) peripheral is the native way to generate precise PWM. Alternatively, if you are driving more than two servos, offload the pulse width generation entirely to a PCA9685 I2C PWM breakout board. The PCA9685 handles the 50Hz timing in hardware, freeing your MCU and eliminating jitter caused by WiFi interrupts on the ESP32.

Failure Signatures: Diagnosing Hum, Jitter, and Thermal Stall

When a servo misbehaves, it is rarely a mystery if you know what to listen and look for. Here are the primary failure signatures and their root causes:

• The "Hum" or "Buzzing" (Hunting): The servo is stationary but vibrating audibly. Cause: The mechanical load is slightly exceeding the holding torque, or the pulse width signal has microsecond jitter. Fix: Increase the servo size, or switch from an analog to a digital servo (which updates the motor drive at 300Hz internally, locking the position tighter).
• Random Spasms or Jitter: The servo twitches to random angles. Cause: Power supply noise or VCC brownout. When the servo draws peak current, the voltage drops, pulling the MCU's logic levels down and corrupting the PWM signal. Fix: Add a 470µF electrolytic capacitor across the servo's VCC and GND wires at the connector, and ensure your BEC is rated for at least 3A.
• Overheat and Thermal Stall: The servo casing becomes too hot to touch, and it stops responding. Cause: Holding a heavy static load near the servo's maximum torque limit. Servos draw maximum current when stalled. Fix: Redesign the mechanical linkage to reduce the static load, or add a physical mechanical brake/counterweight so the servo doesn't have to use electrical current to fight gravity.

The Decision Tree: Selecting Your Exact Servo and Drive

Stop guessing and follow this decision path to lock in your exact bill of materials for your next embedded motion project.