Haas codes
HaasOvertravel/LimitBasic5-15 minutes

304

Haas Alarm 304 - Z Positive Limit

Z AXIS LIMIT +

This alarm activates when the Z-axis travels or attempts to travel beyond the positive software or hardware travel limit during rapid positioning, feed moves, or manual jogging. The MOCON continuously monitors Z-axis encoder position feedback against the travel limit values in Settings 42 and 43. When the limit is exceeded, all axis motion halts immediately to protect the spindle head, column ways, and prevent upward collision with mechanical stops.

Root Cause Summary

ALARM 304 Z AXIS LIMIT + occurs when the Z-axis travels beyond its positive software or hardware limit, triggering Input 33 on the I/O diagnostics. This protective alarm immediately stops all motion to prevent collision with the machine column or spindle head assembly.

Safety

  • Jog slowly away from limit

Causes and Fixes

  1. 1

    Check Active Work Coordinate System

    Press OFFSET/SETTING, then WORK to view current work coordinates. Note which coordinate system is active (G54, G55, etc.) and check the Z-axis offset value.

    The active coordinate system is shown in the position display area

  2. 2

    Verify Z-offset Against Machine Limits

    Compare the Z-offset value to Parameter 221 (Z+ Software Limit). Ensure the offset doesn't cause programmed moves to exceed this limit.

    Never set work coordinates that would cause the spindle to crash into the column

  3. 3

    Correct Work Coordinate Z-offset

    If offset is incorrect, re-establish work coordinates using proper touch-off procedures or manually adjust the Z-offset value in the work coordinate table.

  4. 4

    Test with Cautious Movement

    Use JOG mode with reduced feed rate override to verify the corrected coordinates allow safe Z-axis travel within limits.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Hardware limit switch replacement required
  • ·Encoder feedback issues detected
  • ·Parameter changes needed beyond operator authority
  • ·Repeated alarms after corrections

Prevention

  • Always verify work coordinate offsets before running programs
  • Use program simulation to check tool paths
  • Maintain proper software limit parameters
  • Regularly inspect limit switches during preventive maintenance

Common Mistakes

  • Ignoring work coordinate system when setting up jobs
  • Setting software limits too close to hardware limits
  • Not re-referencing machine after power loss
  • Assuming limit switches are working without verification

Seeing Multiple Alarms?

Seeing another alarm with this one? Enter the code.

Get machine-aware diagnosis

AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.