Menu
Servo Motor Failure: Symptoms, Causes, and How to Test One

Servo Motor Failure: Symptoms, Causes, and How to Test One

Learn the warning signs of servo motor failure, what causes it, and how to test windings, encoder, and brake safely before replacing the motor or drive.
Servo Motor Failure: Symptoms, Causes, and How to Test One

Key takeaways

  • Many suspected servo motor failures are actually encoder, cable, brake, drive, or mechanical binding problems. Isolate the fault before buying a motor.
  • The classic symptoms are following-error alarms, hunting at standstill, overheating, new noise or vibration, and intermittent faults tied to axis position.
  • The core electrical tests are an insulation resistance (megger) test with the drive fully disconnected, a phase-to-phase resistance balance check, and a back-EMF spin test.
  • Never megger through the drive and never megger the encoder circuit. Lockout/tagout first, and treat DC bus capacitors and vertical axes as live stored energy.
  • Log every servo fault as a coded downtime event and track MTBF, so a repeat offender gets an engineering fix instead of a third replacement motor.

Industrial servo motors rarely die without warning, but the warnings are easy to misread, and a healthy motor gets replaced while the real fault stays in the machine. This guide is for maintenance technicians, maintenance managers, and plant engineers who need to diagnose a suspect servo axis, confirm the actual failed component, and stop the fault from coming back.

Rule zero: motor, drive, or mechanics?

A servo axis is a loop: drive, motor, feedback, coupling, and driven mechanism. Any element can produce the same alarm, so the first job is isolation, not replacement. A seized ballscrew, a dragging brake, and a failing amplifier can all throw the same following-error fault.

Before condemning the motor, do three cheap checks. With the machine locked out, rotate the axis by hand (or with the brake safely released) and feel for mechanical binding, roughness, or tight spots. Read the drive's alarm history and note whether faults are current-related, feedback-related, or position-related. And check whether the fault follows a pattern: one axis position, one time of day, one part program.

Symptoms of a failing servo motor

Match the symptom to the most likely cause before touching a meter.

SymptomMost likely causesFirst check
Position error / following-error alarmEncoder or feedback cable fault, mechanical binding, load increaseRotate axis by hand under lockout; inspect encoder connector
Hunting or oscillation at standstillLoose coupling, backlash, noisy feedback, tuning driftInspect coupling and mechanical connection to the load
Motor runs hot or thermal alarmsOverload, dragging brake, degrading winding insulationCompare running current to nameplate; verify brake releases fully
Growling, grinding, or new vibrationBearing wear, contamination in the motorSpin the uncoupled shaft by hand and feel for roughness
Intermittent faults at certain axis positionsFlexing cable fatigue in the cable trackWiggle-test cable sections while monitoring the fault
No movement, no torque, axis deadBrake not releasing, open winding, drive output failureConfirm brake voltage present; measure phase resistance

Alarm numbers help too, but treat them as pointers rather than verdicts. On Fanuc controls, for example, servo alarm 414 indicates the digital servo system has detected a fault on the amplifier or motor side, and the precise meaning varies by control model and software version, so always confirm in the machine documentation. If an alarm code is ambiguous, diagnose from measurements, not from the number.

What actually kills servo motors

In rough order of how often they show up on the shop floor:

  1. Winding insulation breakdown. Heat, age, and voltage stress degrade the insulation until turns short together or a phase shorts to ground. Overheating accelerates this dramatically.
  2. Encoder and feedback failure. The encoder is the most fragile part of the motor. Shock, heat, and contamination corrupt feedback long before the windings fail. See our guide to encoder failure symptoms and testing.
  3. Bearing wear. Worn bearings add friction, runout, and vibration, which then overheats the motor and stresses the encoder. The progression follows the same stages as any rolling-element bearing; our article on bearing failure modes and symptoms covers what to listen and feel for.
  4. Contamination and coolant ingress. Coolant wicks along cable jackets into connectors, causing corrosion, ground faults, and maddening intermittent errors. Look for green residue or oil inside connector shells.
  5. Brake failure. A holding brake that will not release makes the motor fight itself (heat, overcurrent); a brake that will not hold lets a vertical axis drift or drop.
  6. Cable flexing fatigue. Conductors in the cable track work-harden and crack. The signature is faults that correlate with axis position or motion, not with load.
  7. Drive-side failures misdiagnosed as the motor. Failed output transistors, DC bus problems, and current-sensor drift mimic motor faults. The logic is similar to troubleshooting a VFD overcurrent fault: prove which side of the cable the problem is on.

Safety before any test

Apply lockout/tagout before opening cabinets or touching the mechanism. Servo drives hold a charge in their DC bus capacitors after power-off, so wait the manufacturer's stated discharge time and verify zero voltage before touching terminals. Physically block or pin vertical axes before releasing a brake: gravity is stored energy, and a released brake drops the load instantly. Never bypass interlocks or guard switches to speed up a test.

How to test a servo motor, step by step

1. Insulation resistance (megger) test

Disconnect the motor leads from the drive first. A megger applied through the drive will destroy the output stage. With the leads free, test each phase to the motor frame ground, typically at 500 V DC for low-voltage machine-tool motors (confirm the rating in the motor documentation). A healthy motor reads very high, usually in the hundreds of megohms; readings drifting down toward single-digit megohms indicate insulation degradation, and near zero means a ground fault. Never connect the megger to the encoder or its cable, which the test voltage will destroy.

2. Phase-to-phase resistance balance

With a good milliohm-capable meter, measure U-V, V-W, and W-U. The three readings should be low, per the datasheet, and balanced within a few percent of each other. A noticeably low leg suggests shorted turns; an open-circuit leg means a broken winding or a broken conductor in the cable, so repeat the measurement at the motor terminals to separate cable from motor.

3. Back-EMF spin test

With the motor disconnected and uncoupled, spin the shaft at a steady speed by hand or with a drill and measure AC voltage across each phase pair. All three should produce similar, balanced voltages. Unequal voltages point to winding damage even when resistance readings look acceptable.

4. Encoder and feedback checks

Inspect the encoder connector for contamination and bent pins, verify the drive's reported position tracks smooth hand rotation of the shaft, and check the alarm history for feedback-specific faults. Marginal encoders often work cold and fail hot.

5. Brake check

With the axis blocked and locked out, apply the brake's rated voltage (commonly 24 V DC, confirm on the nameplate) from a bench supply. You should hear a distinct click and the shaft should turn freely. No click, no release, or a shaft that still drags means the brake is failing or its supply circuit is.

Swap known-good components methodically

If measurements are inconclusive, swap one component at a time: motor to a known-good drive, known-good motor to the suspect drive, or exchange identical axes where the machine allows it. Change one variable per test and record the result. One critical caution: never connect a replacement drive to an untested motor. A shorted winding can take out the new drive in seconds, turning one failure into two.

Measure it, or you will fix it forever

A servo fault that gets cleared with a power cycle and no record will return. Log every occurrence as a downtime event with a cause code (encoder, winding, brake, cable, drive, mechanical), even the two-minute resets. Track MTBF and MTTR for the asset: if the same axis faults every few weeks, that is a chronic engineering problem (contamination path, cable routing, undersized motor), not a run of bad luck. Availability losses from repeat servo faults flow straight into your OEE numbers, and the short stops are usually the ones nobody writes down.

Catch the failures your logbook misses

Fabrico is computer-vision-verified OEE plus closed-loop maintenance execution: cameras catch the stops and micro-stops that manual logs and sensors miss, and maintenance work orders close the loop from detection to fix. For a recurring servo fault, that means the 90-second alarm resets get counted, coded, and turned into a work order history you can act on instead of vanishing between shifts. If you want to see how that works on your lines, book a Fabrico demo.

When the motor and drive test healthy but the axis still misbehaves, check the mechanics: ball screw wear and backlash mimics several servo symptoms.

Frequently asked questions

How do I know if the servo motor or the drive is bad?

Test the motor independently: insulation resistance to ground, phase-to-phase resistance balance, and a back-EMF spin test. If the motor passes all three and the encoder checks out, suspicion shifts to the drive, the cable, or mechanical binding. Confirm by swapping a known-good component one variable at a time.

Can you megger a servo motor?

Yes, but only with the motor leads fully disconnected from the drive, and never on the encoder circuit. Test each phase to frame ground at the voltage specified for the motor (often 500 V DC for low-voltage motors) and compare against the manufacturer's minimum acceptable reading.

What causes a servo motor to overheat?

The usual causes are mechanical overload or binding, a holding brake that is not fully releasing, degraded winding insulation, excessive duty cycle, and blocked cooling. Check current draw against the nameplate and verify the brake releases before assuming the motor itself is at fault.

What does a failing servo motor sound like?

Bearing wear produces growling or grinding that changes with speed. Hunting or buzzing at standstill usually indicates feedback noise, loose coupling, or tuning problems rather than the motor. A rhythmic click once per revolution suggests physical damage or debris.

How long do servo motors last?

There is no universal figure; life depends on load, duty cycle, temperature, and contamination. Bearings and encoders typically fail before windings. Tracking MTBF per axis in your maintenance system gives you a real number for your machines instead of a guess.

Latest from our blog

Define Your Reliability Roadmap
Validate Your Potential ROI: Book a Live Demo
Define Your Reliability Roadmap
By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration