Heidenhain codes
HeidenhainOvertravel/LimitIntermediate30-120 minutes

1A0-0194

HEIDENHAIN 1A0-0194 - The limit switches of a modulo axis are invalid

The limit switches of a modulo axis are invalid

The software limits or protection zones set for a modulo axis violate one or more geometric rules. Valid limits must stay within a single 360-degree window with the lower bound above -360° and the upper bound below +360°, and the two must not overlap or leave gaps.

Root Cause Summary

The fundamental issue is a configuration conflict where an axis is simultaneously defined as modulo (unlimited continuous rotation via MP1010) and restricted by limit switches (hardware inputs or software limits in MP1020/MP1030). Heidenhain TNC controls enforce logical consistency by generating this alarm when detecting this incompatible configuration, as modulo axes by definition have no travel limits.

Safety

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

Causes and Fixes

  1. 1

    Access machine parameters in service mode

    Enter MOD function, select 'Machine Parameters', and authenticate with appropriate password level (typically OEM or service level required for MP access)

    Document all existing parameter values before making changes. Incorrect machine parameters can cause machine damage or unexpected behavior.

  2. 2

    Identify the affected modulo axis

    Review the alarm context or check MP1010 for all axes. The affected axis will have MP1010.x set to a non-zero value (e.g., 360 for degrees, 400 for gon). Note the axis number/letter (x = axis index).

  3. 3

    Check and clear software limit parameters

    For the identified axis, check MP1020.x (positive software limit) and MP1030.x (negative software limit). For modulo axes, these MUST be set to inactive values. Set MP1020.x = 9999999999 and MP1030.x = -9999999999 (or per machine manufacturer specification).

    Some machine manufacturers use different inactive values. Check MP documentation or compare with other known-good modulo axes on the same machine model.

  4. 4

    Save parameters and restart control

    Save the modified machine parameters, exit the parameter editor, and perform a full control restart (power cycle or controlled restart via MOD functions) to ensure parameters take effect.

    Ensure all machine motion is stopped and safe before restarting the control.

  5. 5

    Verify axis configuration

    After restart, navigate to Test -> Axis diagnostic and verify the affected axis shows as 'Modulo' type with no limit switch indicators active. Test axis motion across the modulo boundary (e.g., move from 350° to 10°).

    Use MDI mode to execute a controlled test move that crosses the modulo rollover point to confirm proper continuous rotation without limit interference.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Parameter changes don't resolve alarm
  • ·Encoder or mechanical issues suspected
  • ·Multiple axes affected simultaneously

Prevention

  • Always validate modulo axis parameters before importing
  • Maintain parameter backups with version documentation
  • Use TNC parameter validation tools before applying changes

Common Mistakes

  • Setting software limits to exactly ±360°
  • Forgetting modulo axis 360° range restriction
  • Not accounting for protection zone interactions

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.