
axismd.ai
Heidenhain Controller
Overtravel/Limit · Intermediate · 30-120 minutes
HEIDENHAIN 1A1-0044 - Setting of software limits for roll-over axis not permitted
The alarm indicates a fundamental configuration conflict where the control cannot apply fixed travel limits to an axis defined to rotate continuously. This typically results from incomplete machine parameter configuration during setup or axis type changes, where either the modulo setting or the software limit values need correction to match the intended axis behavior.
HEIDENHAIN 1A1-0044 - Setting of software limits for roll-over axis not permitted
Setting of software limits for roll-over axis not permitted
A rollover axis cannot accept software limit-switch values. The control rejects any attempt to assign limit boundaries to this axis type.
Root Cause Summary
The alarm indicates a fundamental configuration conflict where the control cannot apply fixed travel limits to an axis defined to rotate continuously. This typically results from incomplete machine parameter configuration during setup or axis type changes, where either the modulo setting or the software limit values need correction to match the intended axis behavior.
Safety
Causes and Fixes
Access machine parameters
Press MOD key, enter machine parameter access code if required, select 'Machine Parameters' and navigate to the axis parameters section. Identify the rotary axis showing the alarm (check error log for axis designation).
Use the search function (MP NUMBER field) to jump directly to parameter 1020 for faster navigation on controls with many installed axes.
Verify MP1020 modulo setting
For the affected axis, check MP1020.x (where x is axis number). If value = 1, the axis is configured as roll-over/modulo. Confirm this matches your machine design - typically C-axes, rotary tables, and indexers use modulo = 1.
Document current value before changes. Some rotary axes on mill-turn machines may intentionally NOT use modulo if mechanical stops are present.
Check software limit parameters
Navigate to MP1410.x (negative software limit) and MP1411.x (positive software limit) for the same axis. Record current values. If these show anything other than 9E99 (or 9.9E99 depending on TNC generation), they are active and causing the conflict.
Do not change parameters while programs are running or axes are in motion. Ensure machine is in a safe state.
Disable software limits for modulo axis
Set MP1410.x = 9E99 and MP1411.x = 9E99 for the roll-over axis. This disables software limit checking which is incompatible with modulo operation. Save parameters and perform a control reboot (not just reset).
After reboot, verify axis display shows proper modulo behavior - position should wrap from 359.999° to 0.000° rather than incrementing indefinitely.
Test axis operation
In manual mode (handwheel or axis keys), rotate the axis through multiple revolutions in both directions. Verify no limit violations occur and position display wraps correctly. Test programmed G-code with multi-revolution movements.
Execute a test program with both shortest-path (M126) and direction-specific (M127) rotary moves to ensure modulo calculations work correctly.
Call a technician if:
Prevention
Common Mistakes
Seeing Multiple Alarms?
Seeing another alarm with this one? Enter the code.
AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.
Start freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.