Haas Alarm 102 — SERVOS OFF: Real Causes, Companion Alarms, and Fast Recovery Checklist (NGC & Classic)

Haas Alarm 102 “SERVOS OFF” means the machine is in a state where the servo motors are off (motion disabled). In many cases it appears as a normal startup condition or as a “headline alarm” that accompanies a deeper fault (safety chain, drive, tool changer, power event, etc.). Treat Alarm 102 as a symptom and immediately look for the companion alarm(s) that explain why the control refuses to enable servos. oai_citation:0‡CNC Replacement Parts

What Alarm 102 Usually Means on Haas

• Servos are disabled, so the machine cannot move under program control.
• Tool changer and spindle/coolant may be inhibited depending on machine state and fault chain. oai_citation:1‡CNC Replacement Parts

Most Common Real-World Causes (What Shops Actually See)

1) Safety chain not satisfied

• Door/guard switch state, E-stop circuit, or an interlock input not in the expected state.

2) A “real fault” is present and 102 is only the top-level symptom

• Servo/axis alarm (e.g., axis fault), power event, tool changer fault, amplifier error, or encoder-related fault often causes the control to hold servos off. oai_citation:2‡Practical Machinist

3) Tool changer / spindle enable sequence not completed

• Some machines show 102 alongside other alarms when the tool changer cannot complete a required state.

Fast Recovery Checklist (Safe, Operator-Friendly)

1) Record the screen: alarm text + any additional alarms (scroll alarm history).
2) Release E-stop; confirm doors/guards are closed; confirm air pressure is within your shop’s spec.
3) Press RESET once, then Power Up/Restart if the control requests it.
4) If Alarm 102 returns immediately, do NOT keep resetting:

• Open the active alarms list and identify the companion alarm(s).
• Troubleshoot the companion alarm first (servo error, overtravel, tool changer, drive fault, etc.). oai_citation:3‡IndustryArena

Pro Tip: Why “102 cannot reset” happens

When 102 will not clear, it usually means a deeper condition is still present (amplifier fault, axis cable short, tool changer state fault, safety circuit fault). In those cases, chasing 102 itself wastes time—find the root alarm and fix it. oai_citation:4‡cnczone.com

Prevention (What Pros Standardize)

• Start every program with a deterministic “safe start” block (cancel cycles/comp, explicit modes).
• Use a consistent safe retract strategy before tool changes and long rapids.
• Keep a simple alarm log: alarm text + root cause + fix; it prevents repeat downtime.