Haas MOCON Error Troubleshooting: Alarm 101 and 102 Resolution

Overview of the Haas MOCON Subsystem

MOCON is Haas Automation's internal designation for the Motion Control board, a dedicated processor PCB that sits between the main CNC processor (the Maincon or, on newer Classic/NGC controls, the motherboard) and the servo amplifier stack driving the X, Y, and Z axes (and A/B axis where fitted). The MOCON board runs its own real-time firmware that closes the position loop, generates torque commands, monitors encoder feedback, and handles spindle synchronization. Because the MOCON operates as an independent processor, the Maincon communicates with it over a high-speed serial link — and any interruption of that link, or any internal MOCON fault, surfaces to the operator as a MOCON alarm rather than a generic processor fault.

On the Haas Super Mini Mill (and the broader VF/VM/SS product lines), MOCON faults are reported as numbered alarms in the 100–199 range. The two codes most often seen in field service reports are Alarm 101 (communication failure with MOCON / MOCON memory) and Alarm 102 (Servos Off). These alarms can be triggered by either a true hardware failure on the motion control PCB or by a software/firmware bug in the IPS (Interactive Programming System) task layer — and the path to resolution differs significantly between those two causes.

Alarm Code Reference Table

Known Firmware Defect: Software Version 15.04E

Haas control software version 15.04E carries a documented bug in the IPS engraving task that causes Alarm 101 (Comm. Failure w/ MOCON/MOCON Memory) and Alarm 102 (Servos Off) to fire the moment the operator presses Cycle Start on the engraving page — even though the MOCON board hardware is fully functional. The bug is reproducible and was confirmed by Haas technical support after field service calls. The triggering sequence is:

1. Operator navigates to the IPS engraving page in the Haas control.
2. Operator loads or selects an engraving routine and presses CYCLE START.
3. Within ~1 second, the control posts Alarm 101 followed by Alarm 102, disables the servos, and flashes the red light bar.
4. The MOCON, drives, and axes are otherwise healthy — running the same G-code from MDI or from a stored program executes correctly.

Resolution is a control software upgrade coordinated through your Haas dealer (HFO). The upgrade is non-destructive to user programs and parameters when performed by a certified technician, but it should be scheduled because it requires the machine to be offline for 20–60 minutes and the operator should back up all programs to a USB or network share first.

Hardware vs. Software Diagnosis Matrix

Before assuming the 15.04E firmware bug, use the matrix below to rule out actual MOCON hardware failure. The presence or absence of the MOCON fault at cold start is the strongest single indicator.

Diagnostic Procedure: Step-by-Step

Follow this sequence to isolate the MOCON fault before calling service. Total expected time: 5–10 minutes.

1. Capture the alarm history. Press PARAM → Alarm → History and record the last 20 alarms with timestamps. Multiple 101/102 pairs in rapid succession (under 30 seconds apart) suggest a single root cause; alarms spaced minutes apart suggest intermittent hardware.
2. Cycle power. Power off at the main disconnect, wait 60 seconds (allows the MOCON capacitors to discharge and the serial link to fully reset), then power on. Note whether Alarm 101 appears at boot — this is the single most diagnostic data point.
3. Test MDI mode. Type a simple safe motion block (e.g., G00 G91 X1.0; G90) in MDI with the work area clear. If MDI runs without fault, the MOCON and axes are healthy at the hardware level.
4. Test stored program mode. Run a known-good .NC file from LIST. If it runs cleanly, the MOCON hardware path is verified.
5. Test IPS engraving page. Navigate to the IPS engraving page and run the same job. If Alarm 101 fires here only, the fault is in the IPS task and is almost certainly the 15.04E bug.
6. Check parameter checksum. Press PARAM → Diagnostics → look for MOCON parameter checksum errors. A non-zero checksum mismatch confirms MOCON NVRAM corruption and points to hardware replacement, not a software upgrade.
7. Inspect ribbon cables. With power off and locked out, reseat the MOCON-to-Maincon ribbon cable and the MOCON-to-axis-drive ribbon cables. Look for oxidation on the IDC contacts — common in humid shop environments.
8. Check MOCON supply rails. A technician with a DMM should verify +5 VDC and +24 VDC at the MOCON power connector. A sagging 5 V rail under load is a classic precursor to intermittent Alarm 101.

MDI Workaround Procedure (Pre-Upgrade Mitigation)

While waiting for the firmware upgrade, operators can continue to run engraving jobs by launching them from MDI rather than the IPS page. This is the documented field workaround for the 15.04E bug:

1. From the IPS engraving page, complete the engraving setup (text, depth, feed) as normal.
2. Press CYCLE START once. Expect Alarm 101/102 — this transfers the generated G-code to the MDI buffer.
3. Press RESET to clear the alarms.
4. Press MDI to open the MDI page. The engraving G-code will be visible in the MDI buffer.
5. Press CYCLE START from MDI. The program will execute normally.

MOCON Board Replacement Procedure

If diagnosis points to a hardware fault, board replacement is the standard corrective action. MOCON boards are not field-repairable — they are replaced as units and the replacement board is flashed with the machine-specific parameter set from the Maincon.

1. Back up all parameters and programs. Use a USB stick or RS-232 transfer. Settings to preserve include: Parameter 1.x (axis scaling), Parameter 3.x (servo loop gains), and the full macro variable table.
2. Lock out / tag out the main disconnect. Verify zero energy at the MOCON connector with a known-good meter.
3. Remove the MOCON PCB from its card-cage slot. Note the orientation of all ribbon cables and label them. The MOCON is typically the second-largest PCB in the electrical cabinet, located in the back of the control housing.
4. Install the replacement board in the same slot. Reconnect all cables finger-tight, then seat fully.
5. Power on and allow parameter sync. The Maincon will automatically download the saved MOCON parameters to the new board. Do not interrupt this process — a power loss during parameter download can brick the new MOCON.
6. Run the MOCON verification routine. Press PARAM → Diagnostics → MOCON TEST. All axes should report PASS.
7. Run a full three-axis reference return and verify each axis returns to its machine zero without following-error alarms.

Verification and Commissioning Checklist

After either a firmware upgrade or a MOCON board swap, run the following checks before returning the machine to production:

Preventive Maintenance and Long-Term Reliability

MOCON boards are sensitive to thermal cycling, dust accumulation, and supply-rail noise. A quarterly preventive-maintenance routine substantially reduces the rate of intermittent 101/102 faults:

• Cabinet air filter inspection/replacement every 90 days. Clogged filters raise internal cabinet temperature and accelerate electrolytic capacitor aging on the MOCON.
• Spare-board burn-in. If you operate a fleet of Haas mills, keep a spare MOCON in climate-controlled stock and power it up monthly for 30 minutes to re-form its capacitors.
• Grounding integrity check. Verify the machine's earth ground resistance is below 5 Ω annually. Poor grounding injects common-mode noise on the MOCON serial link.
• Firmware currency. Subscribe to Haas service bulletin notifications through your HFO. Bug-fix releases (15.04F, 15.05A, etc.) are typically non-disruptive and prevent other known issues.
• Record MOCON serial numbers. Tracking MOCON serial numbers by install date helps identify boards approaching the 5–7 year mean-time-between-failure window.

Related Alarms and Edge Cases

Spindle MOCON faults (152/153): Some Haas configurations use a separate spindle MOCON card. Alarms 152 and 153 follow the same diagnostic pattern as 101/102 but indicate spindle-specific MOCON issues. Do not confuse with axis MOCON faults.

Alarm 101 with axis drive alarms (111–119): If Alarm 101 appears together with an axis drive fault, suspect the amplifier-to-MOCON ribbon cable rather than the MOCON itself. Reseat the cable first; replace only if the fault persists.

Alarm 101 correlated with regen over-temperature (158/159): Sustained heavy cuts can trip the regen resistor thermal switch, which in turn causes the MOCON to flag a comm loss. Add cooling time to the program or inspect the regen assembly.

Repeat 101/102 after power cycle on a cold morning: A classic sign of marginal MOCON NVRAM. Replace the MOCON board — the fault will progress to "will not clear at all" within weeks.

Frequently Asked Questions