Motor Control and Timing
How a Servo Reaches a Target Position
Understand command pulses, feedback error and stall-current limitations.
You need to understand the internal functions in “How a Servo Reaches a Target Position” before selecting, connecting or troubleshooting the real equipment.
Trace an RC positional servo from pulse-width command to internal position feedback, bounded motor drive and load response, including calibration and blocked-output heating.
- Select or check first
- Define the required outcome, operating conditions and exact component or system boundary before choosing a part or method.
- Controlling assumption
- Sensors, controller logic, actuator limits, timing, fault response and environmental conditions are defined together.
- Top risk
- Do not find the endpoint by forcing the servo. Begin with a conservative documented command window, disconnect or limit a binding mechanism, and stop if the servo strains or heats. Size the supply and wiring for simultaneous realistic peak loads without exceeding the servo voltage range.
- Proof
- Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test.
Start with the basics Optional foundation before “How a Servo Reaches a Target Position”
Automation-and-control basics
An automatic system measures a condition, decides what it means and commands an actuator while checking whether the expected result actually happened.
- Sensor
- A sensor converts a physical condition into a signal. Its range, uncertainty, response time, environment and failure behaviour matter as much as its nominal output.
- Controller
- A controller reads inputs, applies logic or a control law and issues outputs. Software cannot correct missing measurements, inadequate hardware authority or unsafe architecture.
- Actuator
- An actuator turns a command into physical action, such as motor torque, valve position or switching. Its real limits depend on load, supply, drive and duty.
- Feedback
- Feedback compares measured behaviour with the desired state so error can be corrected. Open-loop command assumes the action occurred; closed-loop control checks it.
- Fault and safe state
- A fault is an abnormal condition that may invalidate control. The safe response must be defined from the hazard and may require independent hardware, not only software.
How to use this article: Trace one complete chain—physical condition, sensor, signal conditioning, controller, drive, actuator and feedback—then ask how each link can fail.
On this page
A positional RC servo is a small closed-loop motion system. The external controller sends a target, while electronics inside the servo compare that target with a position measurement and drive a motor through gears. A correct command therefore does not prove that the shaft reached its target: load, voltage, mechanical stops, gear condition and the servo's own limits still determine the physical result.
The feedback loop closes inside the servo
Diagram description
An illustrative servo cutaway shows a motor, gear train, output shaft, feedback sensor and control board beside a functional negative-feedback loop.
Position error
e = θ_target − θ_measured
The sign convention determines which direction is corrective. Angle units must be consistent. A real controller also applies gain, deadband, damping, current limits and protection; error is not motor voltage by itself.
- e
- signed position error
- θ_target
- commanded output position
- θ_measured
- position reported by the internal sensor
What happens after a new command
- The input decoder converts a valid command pulse into an internal target.
- The position sensor measures the geared output, not merely motor rotation.
- The controller forms a signed error and requests drive in the correcting direction.
- Motor torque moves the gear train and output, reducing the error.
- Near target, the controller reduces or interrupts drive according to its design; it may reapply drive when load disturbs the shaft.
Pulse width requests position; it is not motor-power duty cycle
Diagram description
The teaching plate compares three pulse widths without assigning universal microsecond values or angles and warns that duty cycle is not the commanded quantity.
A common nominal convention uses a pulse near 1.5 ms for neutral and a pulse train near 50 Hz, but those are starting expectations rather than universal guarantees. There is no standard pulse-to-degree mapping, no universal minimum or maximum width and no guaranteed direction for increasing width. Some digital servos accept different update rates or retain the last command when pulses stop. Use the selected servo's documentation and calibrate conservatively.
| Quantity | What it means | Common mistake |
|---|---|---|
| Pulse width | Requested target under that servo's calibration | Treating it as direct motor speed or drive duty |
| Pulse period | How often a new command is presented, within supported limits | Assuming every analog and digital servo accepts any rate |
| Internal feedback | Servo's own estimate of output position | Assuming it is normally sent back to the external controller |
| Physical angle | Actual shaft position under load and limits | Inferring it from pulse width without calibration or external measurement |
Error sets direction, while the drive remains bounded
Diagram description
The graph is a conceptual bounded control law, not universal firmware or a measured response from a named servo.
Deadband can prevent constant hunting around the target; too much deadband reduces positioning precision. Saturation means the requested effort has reached a controller, motor, current or supply limit. More error beyond that point cannot create unlimited torque. Gear backlash, sensor noise, controller gain and load inertia influence overshoot and settling, so two servos receiving the same pulse may move differently.
| Symptom | Possible causes | Useful evidence |
|---|---|---|
| Twitching at rest | Pulse jitter, noisy supply, sensor wear, excessive gain or load disturbance | Command timing, supply waveform, shaft motion and unloaded comparison |
| Slow or incomplete movement | Low voltage, insufficient current, excess load, friction or command limit | Voltage at servo during motion, current, output angle and torque requirement |
| Overshoot or oscillation | Load inertia, compliance, backlash or controller dynamics | Time history of target and measured position |
| Unexpected endpoint | Product-specific pulse range, horn alignment or mechanical stop | Conservative pulse sweep with physical clearance |
Persistent error can become heat instead of motion
Diagram description
A generic blocked servo illustrates the chain from unreached target to elevated current and thermal stress; protection behavior depends on the model.
At or near stall, motor back EMF is low and current can approach the servo's limited stall value. Copper loss grows approximately with current squared, so a modest current increase can produce much more winding heat. Driver losses and a weak connector or supply also add heat. Some servos reduce current or report a fault; others may keep trying. Never assume protection exists unless the selected product documents it.
A practical commissioning sequence
- Verify servo voltage range, connector polarity and signal reference with the manufacturer documentation.
- Power one unloaded servo from a current-limited supply and start near documented neutral.
- Increase and decrease pulse width slowly while measuring the safe physical range; do not drive into stops.
- Add the mechanism and check clearance, load torque, voltage at the servo and current through the full trajectory.
- Test obstruction detection, timeout or torque limiting where a jam can occur.
- Record calibrated command endpoints, direction, update rate and allowable duty cycle for the application.
The difference between a commanded target and verified movement is the same control principle introduced in Open-Loop Commands Versus Real Feedback. For choosing among motion technologies before control details, see DC, Stepper and Servo Motors: Which One Fits?.
Selection boundary and evidence to keep with the decision
Treat “How a Servo Reaches a Target Position” as a selection problem, not only a definition. Record the required result, alternatives considered, the controlling assumption and the condition that would change the choice.
Keep evidence proportional to consequence: Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test. Revisit the decision when the load, environment, duty, interface, regulation or maintenance plan changes.
One-minute questions
Questions to answer before you apply this lesson
What should I select or check first for How a Servo Reaches a Target Position?
Define the required outcome, operating conditions and exact component or system boundary before choosing a part or method.
Which assumption can change the conclusion?
Sensors, controller logic, actuator limits, timing, fault response and environmental conditions are defined together.
What can go wrong if I copy the example directly?
Do not find the endpoint by forcing the servo. Begin with a conservative documented command window, disconnect or limit a binding mechanism, and stop if the servo strains or heats. Size the supply and wiring for simultaneous realistic peak loads without exceeding the servo voltage range.
How do I verify the result in the real system?
Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test.
Sources and further reading
- Servo control interface in detailPololu Corporation · 2026-10-13Manufacturer test article reviewed for pulse-width command behavior, lack of a universal pulse-to-angle mapping, product-specific endpoints and measured load-current behavior.
- Electrical characteristics of servos and introduction to the servo control interfacePololu Corporation · 2026-10-13Manufacturer engineering article reviewed for command conventions, supply-voltage constraints, idle versus stall current and power-supply implications.
- Maestro Servo Controller User's GuidePololu Corporation · 2026-10-13Primary controller documentation reviewed to separate commanded pulse position from physical feedback and to confirm bounded speed and acceleration commands are source-side features.