Heidenhain codes
HeidenhainServo/AxisIntermediate30-120 minutes

231-4260

Heidenhain 231-4260 - 4260 Limit through I^2*t monitoring

4260 Limit through I^2*t monitoring

Heidenhain TNC error 231-4260: 4260 Limit through I^2*t monitoring. This alarm indicates a fault or error condition on the Heidenhain TNC control that requires investigation. Refer to the Heidenhain NC error message documentation for the specific cause and remedy for this alarm code.

Root Cause Summary

Alarm 231-4260 indicates the servo motor has exceeded its thermal current limit (I²t monitoring) in the specified axis. This protection prevents motor damage from overheating due to excessive current draw over time.

Safety

  • Refer to Heidenhain service manual
  • Ensure qualified technician performs repairs

Causes and Fixes

  1. 1

    Check axis movement manually

    In Manual mode, move the affected axis at low feedrate (F100) and observe current display in machine parameter MP7300 (actual current).

    Ensure machine is properly homed and workpiece/tooling is clear before manual movement.

  2. 2

    Inspect mechanical components

    Check ballscrew backlash, linear guide condition, and lubrication. Verify MP1020 (ballscrew pitch) matches actual hardware.

    Listen for unusual noise during movement - grinding indicates mechanical binding.

  3. 3

    Verify cutting parameters

    Reduce feedrate and spindle speed in active program. Check if alarm clears with lighter cutting loads.

    Monitor MP7300 current values - should not exceed 80% of MP1110 (maximum motor current) during normal operation.

DIY Feasiblemedium confidence

Call a technician if:

  • ·Motor parameter changes required
  • ·Servo amplifier replacement needed
  • ·Mechanical binding cannot be resolved

Prevention

  • Regular lubrication of linear guides and ballscrews
  • Monitor cutting loads and adjust parameters for material hardness
  • Keep motor cooling systems clean and functional
  • Perform periodic servo parameter verification

Common Mistakes

  • Ignoring mechanical binding and only adjusting parameters
  • Increasing I²t limits without addressing root cause
  • Not checking motor cooling before parameter changes
  • Confusing I²t monitoring with simple overcurrent protection

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.