FANUC codes
FANUCOvertravel/LimitBasic5-15 minutes

506

Fanuc Alarm 506 - 4th Axis Positive Overtravel

Overtravel +4th

Axis overtravel +4th limit triggered. The machine has reached the software or hardware travel limit in the indicated direction.

Root Cause Summary

Fanuc Alarm 506 OVER TRAVEL +n (HARDWARE) occurs when the machine physically triggers the positive hardware overtravel limit switch on the specified axis. This is a hard limit protection indicating the axis has moved beyond its safe mechanical travel range, activating the external limit switch wired to the CNC. Unlike software limits (Alarm 500), this requires physical intervention to retract the axis.

Safety

  • Jog slowly away from limit

Causes and Fixes

  1. 1

    Check DIAGNOSIS > I/O screen for limit switch status. Navigate to SYSTEM > DIAGNOSIS > I/O and verify X: +OT (or corresponding axis) shows '1' indicating active limit switch contact. Note the axis number 'n' in the alarm message.

  2. 2

    Reset alarm and enter MANUAL mode with feedrate override at 0%. Press RESET, then manually jog axis in negative direction using handwheel or slow jog (5-10%) to retract from limit switch until I/O signal clears.

    If axis will not move in jog mode, enable Parameter 1815#0 (OTL) = 1 temporarily to allow overtravel release. Return to 0 after clearing limit.

  3. 3

    Verify machine reference point is correct. Execute RETURN TO ZERO sequence from SYSTEM > MANUAL > REF RETURN. Check Parameter 1815 (reference point return direction) and Parameters 1850-1854 (stored stroke limits) match machine mechanical travel.

  4. 4

    Check software limit parameters to prevent recurrence. Verify Parameter 1320-1327 (software overtravel +) and 1420-1427 (software overtravel -) are set correctly with margin inside hardware limits. Typical margin is 5-10mm from hardware switch position.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Hardware limit switch requires replacement
  • ·Encoder feedback system malfunction
  • ·Mechanical binding requires disassembly

Prevention

  • Regularly verify software travel limit parameters
  • Include limit checking in NC programs
  • Perform reference return after power cycles
  • Monitor servo load trends for mechanical wear

Common Mistakes

  • Ignoring software limit parameter verification
  • Assuming reference position is always correct
  • Not checking work coordinate offsets
  • Forcing axis movement while alarm is active

Related Alarms

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.