AutomateDirectUSAMotion LibraryShop the parts catalog

Troubleshooting

How to Tell if a Servo Motor Is Actually Faulty

Servo and stepper motion Published 8 min read

Short answer

A servo motor is only confirmed faulty when it still fails with a known-good drive, verified feedback, and the load uncoupled. Read the commanded motion, the measured motion, and the motor current during the same event: high current with no movement points to the load or the feedback, and no command with no movement points upstream of the motor.

On this page
  1. What should you check before replacing a servo motor?
  2. Which readings decide where a servo fault is?
  3. Why does the servo draw no current and not move?
  4. Why does the servo draw high current and not move?
  5. How do you test the motor through the drive software?
  6. How do you know if the current is normal for the load?
  7. Does a hot servo motor mean the motor is faulty?
  8. What result confirms the motor itself is faulty?
  9. Questions asked

A servo motor earns condemnation only after it fails the same move with a good drive, honest feedback, and the load uncoupled, and the test that settles it is arithmetic on current: multiply the measured amps by the motor's torque constant and compare the result to the continuous rating. In the calculated example in this article, 6.0 A at a stall with a 0.85 N·m/A torque constant is 5.1 N·m, which is 128 percent of a 4.0 N·m continuous rating — that number, with the shaft frozen, convicts the mechanics, not the motor. Until you have that comparison, a stopped axis can equally well be a missing command, an enable that never closed, a damaged encoder cable, or a binding ball screw. Three readings, captured during the same event, sort it out: what the controller commanded, what the feedback measured, and what current the drive pushed into the motor. The sections below follow that fault tree in the order you meet it, and each branch ends in a decision.

What should you check before replacing a servo motor? #

Record the fault before touching anything: the drive's fault code, the drive status, the operating mode, and the exact moment the failure occurs — at enable, during acceleration, at constant speed, on reversal, or while holding position. Save the drive's diagnostic history and a trend of the failing move; a code captured at the moment of failure is worth ten taken afterwards.

A replacement motor leaves the symptom untouched when the real fault is an encoder cable, a missing command, a drive parameter, or a bound transmission, and the swap changes alignment, cable routing, and feedback setup at once — several variables move, and you learn nothing about which one mattered. Raising loop gain is the other reflex to avoid: gain sets how hard the loop fights error, and it cannot restore missing feedback or free a stuck axis. Pushed too far it brings oscillation, higher current, and heating. If the axis hums or dithers around position, read why a servo motor oscillates between two positions before touching a gain number.

Which readings decide where a servo fault is? #

Four readings decide it, and they must come from the same event: the commanded position or speed, the measured feedback, the motor current, and the drive status, because a snapshot taken after the axis stops misses the spike or dropout that caused the trip. Capture all four in one trend of the failing move:

  • Commanded position or speed, from the controller or drive monitor — a missing or frozen command convicts the path upstream of the drive.
  • Measured position or speed from the feedback device — judge the tracking error against the tolerance the drive is configured to allow.
  • Motor current, from the drive monitor — compare it with the motor's continuous rating and the drive's peak limit, including how long peak is permitted.
  • Drive status and fault code — the code names the limit the drive hit, not the part that caused it.

Read the units before comparing anything: a percentage of rated current, a current in amperes, and a torque estimate are not interchangeable without the drive's scaling data.

Why does the servo draw no current and not move? #

Go upstream of the motor: an axis that draws no current has not been asked to move, so check the Run or Enable input, the command source, the operating mode, and the controller's motion request before touching any hardware. Work through these cheapest first.

Confirm the Run or Enable input is actually closed in the drive's I/O monitor, not just wired. Confirm the command source selected in the drive matches where the command should come from, and that the operating mode matches what the controller sends — a drive configured for one command type ignores another it was never set to read. Note that a drive which is powered but never enabled may be reacting to feedback it does not recognize, so a feedback fault can present as silence. Decision: no command and no current means the fault is upstream — interlock, network, controller logic — and the motor is cleared without being touched.

Why does the servo draw high current and not move? #

The drive is delivering torque and the axis is not turning, which points at the mechanics, a brake that never released, or feedback that lies about position — the motor is doing its job and is the last thing to condemn. A reported failure case with 8 A of running current spiking to 26 A at enable traced to the drive fighting the motor over wrong feedback or mechanical binding, not to a failed motor.

Before your hands go near the transmission, lock out the machine and verify zero energy — in US plants that means the site's OSHA 1910.147 energy-control procedure — and confirm the drive's DC bus has discharged before touching a power terminal. Then rotate the shaft by hand with the drive disabled and feel for hard spots; check that a fitted brake actually releases when its control signal is on; watch the feedback count while the shaft turns slowly — it should move in the direction of rotation with no dropouts or jumps. On an older axis, confirm what feedback type you are reading before trusting it, as covered in how to identify geared resolver and encoder feedback on old servos.

With the coupling exposed, inspect it for looseness or a pinch; if the coupling is the part that has failed, replace it with a flexible shaft coupling matched to both shaft diameters and the drive torque, then repeat the same test. Decision: clean feedback plus a shaft that turns hard convicts the mechanics; jumpy or dead feedback convicts the feedback channel. Either way the motor survives to the next test.

How do you test the motor through the drive software? #

Jog the axis from the drive's setup software first, then repeat the identical move from the controller: local success with controller failure clears the motor and convicts the command path between them. Use the manufacturer's documented test mode, not a workaround: limit the travel in the drive, clear the envelope of tools and people, keep every guard and interlock in the circuit, and never bypass a safety function to get a test to run.

Command a slow, short move from the setup software and record requested motion, measured motion, current, and status. Then issue the same move from the controller. Local success narrows the fault to the command path — wiring, scaling, source selection, enable sequencing, or the controller's motion request — but it does not prove the axis can carry its load. Decision: local jog good and controller move dead means command path; local jog also bad means continue to the current comparison and the uncoupled test.

How do you know if the current is normal for the load? #

Convert the current reading to torque with the motor's torque constant, then compare it to the continuous rating: with 0.85 N·m per ampere and 6.0 A at a stall, the motor is making 5.1 N·m, 128 percent of a 4.0 N·m continuous rating. Here is the full calculation for a calculated example, not a measured result.

Take a motor whose datasheet lists a torque constant of 0.85 N·m/A and a continuous current of 4.7 A. The torque it can hold all day is 0.85 N·m/A × 4.7 A = 4.0 N·m (3.995 before rounding). The symptom: the axis stalls partway into a feed, and the drive monitor captured during the stall shows 6.0 A with measured position frozen. The torque being produced is 0.85 N·m/A × 6.0 A = 5.1 N·m, and 5.1 N·m ÷ 4.0 N·m = 1.28, so the motor stands at 128 percent of continuous while not moving — inside the peak band, but only for the seconds the drive permits, after which it trips on overload or overheats. Uncouple the load and jog the same speed: current falls to 1.1 A, which is 0.85 × 1.1 = 0.94 N·m, and measured position follows the command with no tracking fault.

Decision: a free motor that needs 0.94 N·m and tracks cleanly passes, while 5.1 N·m of demanded torque with zero motion convicts the mechanics — a binding screw, crashed way covers, a misadjusted gib — and clears the motor.

Does a hot servo motor mean the motor is faulty? #

No: heat is accumulated loss, not a verdict on the windings, because sustained load, repeated acceleration, a stall, and an oscillating control loop all heat a healthy motor, so read the thermal state together with the current that caused it. The question is never whether the motor is hot, but hot at what current and what duty. An axis run at or under its continuous rating for its duty cycle that still overheats points at ambient temperature, a blocked cooling path, or a motor whose condition has changed — which is when the winding checks in the next section earn their place. Heat that appears because current sits above continuous, or because the loop hunts, is a load or tuning problem, not a motor defect.

What result confirms the motor itself is faulty? #

Condemn the motor only when it fails with the variables removed: verified feedback, a matched known-good drive, and the coupling open, it still draws abnormal current, misses the commanded motion, or shows unbalanced phase-to-phase resistance. The bench checks that close the case are direct, and the substitution that follows them uses a spare motor and the manufacturer's commissioning steps — alignment, feedback setup, current limits — before judgment.

Keep in mind the two failure classes that make servos fail without warning: high-frequency electrical phenomena attacking bearings and windings, and gradual feedback-signal degradation that the loop hides until it cannot. A motor that has failed one of these ways will not pass the free jog or the bench checks. The whole fault tree in one place:

  • No command, no current, no motion — enable, interlock, command source, or controller logic; fix it there.
  • High current, no motion, feedback clean, shaft stiff by hand — mechanics or brake; free the load.
  • Current spikes at enable and feedback jumps, drops out, or runs backward — feedback wiring, pairing, or configuration.
  • Local jog good, controller move dead — command path between controller and drive.
  • Abnormal current or lost motion with a known-good drive, verified feedback, and the coupling open — the motor; replace it.

Questions asked

Is swapping in a spare servo motor a valid first test?

Only if the spare is on the drive's supported motor list with the same feedback type, and you re-run the exact same command afterward. If the symptom persists with the spare, the motor was never the fault, and you have changed alignment and feedback setup for nothing. Save substitution for after the fault tree narrows the location.

Can a servo motor that jogs fine uncoupled still be faulty?

Yes. A no-load jog proves the drive commutates the windings and the feedback tracks the shaft, but it only asks for friction-level torque, a small fraction of the rating. A motor with winding damage can pass the free jog and still stall under load; the coupled-current comparison is the test that exposes it.

Does one servo axis always mean one servo motor?

No. An axis is a controlled degree of freedom, not a motor count. A two-axis gantry commonly runs three motors, two synchronized on the long direction and one on the cross, and a four-axis controller commands four coordinated axes however many motors drive them. When a fault appears on a gantry, test each motor of the pair on its own drive channel first.

How do you check the motor windings directly?

With the drive locked out and the motor cables disconnected, measure phase-to-phase resistance on all three pairs and compare them with each other and with the value in the motor's documentation. Then measure insulation resistance from each phase to the frame at the test voltage the documentation specifies. A large imbalance or low insulation condemns the motor regardless of how it jogs.

Keep reading

  • Troubleshooting

    Why a Servo Motor Oscillates Between Two Positions

    A servo that hunts in a stable 30-50 degree band and restarts on a light shaft nudge has a working position loop running on wrong motor or load data. Fix the configuration — engineering units, load description, pole count, resolver excitation — before swapping phases or retuning: in the documented case, converting metric values into the drive's lbf-ft fields and correcting the load entry stopped it.

    Servo and stepper motion

  • How-to

    How to Identify Geared Resolver and Encoder Feedback on Old Servos

    Treat the resolver plus its geared 1:4 and 1:80 channels as one integrated coarse-and-fine, multi-turn position package: the resolver reads absolute angle within one shaft revolution, and the geared channels count revolutions above it. Identify each channel by resistance checks, ratio counting and waveform capture before choosing a replacement drive, because the resolver model number alone establishes neither commutation nor multi-turn position recovery.

    Sensors, encoders and machine vision on the machine

  • Selection guide

    Choosing Servo or Stepper for a 1% Speed Regulation Pinch Wheel

    Pick the servo: behind a 45:1 planetary reducer, a velocity-mode servo meets a 1% wheel-speed tolerance with margin, because 200-300 lb-in at 80 rpm needs only 4.9-7.4 lb-in at the motor and the loop corrects load-induced error. A stepper qualifies only when its torque-speed curve clears the load with margin at the required motor speed and a measured ripple test holds the wheel inside 0.8 rpm.

    Servo and stepper motion