Heidenhain codes
HeidenhainOvertravel/LimitIntermediate30-120 minutes

230-04D3

HEIDENHAIN 230-04D3 - Faulty monitoring of the software limit switches

Faulty monitoring of the software limit switches

Software limit switch monitoring was disabled via OEM macro. This is no longer permitted in current software versions.

Root Cause Summary

This alarm is triggered by the TNC's internal safety monitoring detecting an error condition in the software limit switch logic or configuration. The control continuously verifies that software limits are logically consistent and that the machine position remains within allowable boundaries. When this monitoring detects a fault—whether from incorrect parameters, position outside limits, or data corruption—it halts operation to prevent potential axis overtravel.

Safety

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

Causes and Fixes

  1. 1

    Access machine parameters

    Press MOD key, enter code (if required), select 'Machine Parameters', navigate to general geometry parameters section

    On iTNC 530 and TNC 620/640, use the search function in machine parameters (MOD > Search) to quickly find MP1500, MP1510, and MP1520 parameters

  2. 2

    Check software limit activation status

    Locate MP1500.x for each axis (X=0, Y=1, Z=2, etc.). Verify value is set to '1' (active) if software limits should be enabled, or '0' (inactive) if not used. Confirm this matches machine design intent

    Disabling software limits (MP1500.x = 0) removes an important safety feature - only do this if hardware limit switches provide adequate protection

  3. 3

    Verify minus software limit values

    Check MP1510.x for each axis. Values must be in machine coordinate system (mm or inches). Ensure minus limit represents the most negative position the axis should reach

    Software limits are always defined in the machine coordinate system (REF-referenced coordinates), not in workpiece coordinates

  4. 4

    Verify plus software limit values

    Check MP1520.x for each axis. Values must be greater than corresponding MP1510.x values. Ensure plus limit represents the most positive position the axis should reach

    The relationship MP1520.x > MP1510.x must always be true, or the control will generate this fault

  5. 5

    Save parameters and restart

    After correcting values, exit MOD function which automatically saves changes. Perform a control restart (MOD > System Restart or power cycle) to reinitialize monitoring system

    Always document original parameter values before making changes - use MOD > Backup function to save configuration to USB

DIY Feasiblemedium confidence

Call a technician if:

  • ·PLC modifications required beyond basic parameter changes
  • ·Firmware downgrade needed
  • ·Machine safety systems affected

Prevention

  • Document all parameter changes before modifications
  • Backup PLC programs before updates
  • Review firmware release notes before updates
  • Establish software limit testing procedures

Common Mistakes

  • Disabling software limits for convenience without understanding safety implications
  • Modifying wrong parameter series (MP7400 vs MP7500)
  • Not checking PLC marker status after parameter changes
  • Ignoring firmware compatibility when updating

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.