Haas Alarm Codes: Common Alarms, Causes, and How to Troubleshoot

Key takeaways

• Haas alarms cluster into a few families: servo and axis faults, spindle faults, air and lubrication, power problems, overtravel, and MOCON or communication errors. Identify the family first and the fix gets much easier.
• The most frequent repeat offenders (low air pressure, low way lube, servo overload) usually trace to shop utilities or mechanical binding, not failed electronics.
• Read the alarm history before touching anything: the first alarm in the sequence is the real story, and later entries such as 102 SERVOS OFF are often just consequences.
• Lock out and tag out before opening the cabinet: servo drives hold a dangerous charge after power off, and a vertical axis can drop when its brake is released.
• Log every alarm as a coded downtime event and track MTBF and MTTR, so chronic alarms get engineering fixes instead of daily resets.

A Haas machine that stops with a flashing alarm costs you spindle minutes every time someone walks over, squints at the screen, and presses RESET without understanding the cause. This guide explains how Haas alarms are displayed, what the common codes usually mean, and a systematic sequence for diagnosing them. It is written for maintenance technicians, maintenance managers, and plant engineers who need the machine cutting again, and staying that way.

How Haas alarms are displayed and logged

When a Haas control raises an alarm, it shows an alarm number and a short text message, and for serious faults it disables the servos and stops the program. Some alarms clear with RESET once the condition is gone; others return immediately because the underlying fault is still active, and a few require a power cycle.

Every Haas control also keeps an alarm history: a time-stamped list of recent alarms. On Next Generation Control machines the alarms screen includes a history tab and built-in help text for each code; on classic controls you reach alarms and their history through the alarm and message displays. The exact navigation varies by control generation.

One caveat before any list of codes: alarm meanings vary by model, control generation, and software version. Always confirm the text shown on your machine against Haas documentation for your serial number before ordering parts.

The major Haas alarm families

• Servo and axis alarms: following errors (103 to 106), overloads (108 to 111), motor overheat (135 to 138), and encoder faults (139 to 142). These point at the axis drivetrain: motor, amplifier, encoder, ballscrew, ways, and lubrication.
• Spindle alarms: drive faults, orientation and gear-change faults, and spindle overheat. Many of these are prevented by the basics covered in our CNC spindle maintenance guide.
• Air, lubrication, and coolant alarms: low air pressure (120), low way lube (121), low coolant, and through-spindle coolant pressure faults. Utility problems masquerading as machine problems.
• Power alarms: overvoltage (119) and regen overheat (122) point at incoming line quality, transformer taps, or the regen circuit.
• Overtravel alarms: an axis has reached a travel or soft limit, usually after a crash, a bad offset, or a lost reference. The recovery logic is similar across controls; see how the same fault presents as Fanuc alarm 500 and 501 overtravel errors.
• MOCON and communication alarms: alarm 101 (communication failure with MOCON, the motor control board) and related processor faults. Often triggered by noise, grounding issues, or a genuine board failure.

Common Haas alarm codes, likely causes, and first checks

The table below covers alarms most maintenance teams will recognize from classic Haas controls. Codes not listed here, and any code whose on-screen text differs from this table, should be confirmed in your machine's documentation rather than assumed.

A systematic troubleshooting sequence

1. Record the exact alarm number and text, then open the alarm history. Alarms arrive in chains: a 103 servo error will typically be followed by 102 servos off, and the first alarm is the one to chase.
2. Look at the machine before the electronics. Chips packed under way covers, a crashed tool, a flooded table, or a kinked air line explain far more Haas alarms than failed boards do.
3. Verify utilities: air pressure at the machine gauge, way lube tank and lines, coolant level and concentration, and cabinet ambient temperature.
4. Use the axis load meters. Jog each axis slowly across full travel and compare readings. An axis pulling noticeably more load than its twin has a mechanical problem: binding, contamination, or lube starvation.
5. Check power quality for 119 and 122 type alarms, especially if they cluster at certain times of day. While you are in that territory, learn the early signs of contactor and motor starter failure, since chattering or pitted contacts create intermittent faults that look random.
6. Only then open the cabinet, and do it safely. Lock out and tag out first. Servo drives and the vector drive hold a lethal capacitor charge for minutes after power off, pneumatic circuits stay pressurized, and a vertical axis can fall under gravity when the motor brake is released. Never bypass door switches or interlocks to keep a machine running.
7. Clear, verify, and watch. After the fix, reset, re-run the program that alarmed, and monitor load meters. An alarm that returns is telling you the root cause is still there.

When to call your Haas Factory Outlet

Some faults are worth an HFO visit rather than trial-and-error parts swapping. Call when you see repeated amplifier or drive faults after mechanical causes are ruled out, encoder or MOCON failures, ground fault alarms, anything that requires parameter changes, or any work on a machine under warranty.

Before you call, gather the machine serial number, software version, and the full alarm history, plus what the machine was doing when it faulted. That one habit routinely turns a two-visit repair into a one-visit repair.

Treat alarms as data, not just interruptions

A machine that alarms on low air every humid afternoon is not unlucky, it is unmeasured. Log every alarm occurrence as a downtime event with a cause code (for example, "alarm 120, plant air"), then track MTBF and MTTR per asset. Once the same code shows up ten times a month, it stops being an operator annoyance and becomes an engineering project: a dedicated air drop, a rebuilt lube system, or a revised preventive maintenance schedule for that machine.

Those alarm minutes are availability losses, and they add up quietly. Our guide to OEE for manufacturing shows how to turn them into a number your plant can actually manage.

Catch the stops your logs miss

Manual downtime logs capture the big breakdowns, but the two-minute alarm resets rarely get written down, and they are where chronic Haas problems hide. Fabrico is computer-vision-verified OEE plus closed-loop maintenance execution: cameras catch stops and micro-stops that manual logs and sensors miss, and maintenance work orders close the loop from detection to fix. If your Haas machines alarm more than your records show, book a Fabrico demo and see the gap for yourself.

Low lube alarms deserve their own diagnosis rather than a reservoir top-up and a reset: see way lube system troubleshooting.

Frequently asked questions

How do I clear an alarm on a Haas machine?

Fix the condition, then press RESET; alarms tied to servo shutdowns usually require pressing POWER UP or cycling power afterwards. If the alarm returns immediately, the fault is still active and resetting again will not help.

What does Haas alarm 102 SERVOS OFF mean?

The servos have been disabled, typically because the E-stop was pressed or another alarm shut them down. Check the alarm history for whatever fired first, since 102 is usually a consequence rather than the root cause.

Why does my Haas keep showing alarm 120 LOW AIR PRESSURE?

Supply pressure at the machine dropped below the required threshold for long enough to trip. Watch the gauge at the machine while it runs: intermittent trips usually mean leaks, a clogged filter or regulator, or an air line too small for everything drawing on it.

What causes SERVO ERROR TOO LARGE alarms (103 to 106)?

The axis fell too far behind its commanded position, which happens after a crash, with mechanical binding or lube starvation, or when a motor, encoder, or amplifier is failing. Jog the axis slowly through full travel and watch the load meter before condemning any electronics.

Are Haas alarm codes the same on every machine?

No. Meanings and numbering vary by model, control generation, and software version, so always confirm the alarm text on the machine itself and in the Haas documentation for your serial number before acting on a code list.