axismd.ai
Heidenhain Controller
Overtravel/Limit · Intermediate · 30-120 minutes
HEIDENHAIN 230-04E0 - Progmmd. limit switch/protection zone incorrect for axis
Alarm 230-04E0 occurs when protection zones are incorrectly configured for modulo axes (typically rotary axes) on TNC systems that don't support this combination. The control detects an incompatible configuration between the axis type definition and protection zone settings.
230-04E0
HEIDENHAIN 230-04E0 - Progmmd. limit switch/protection zone incorrect for axis
Progmmd. limit switch/protection zone incorrect for axis
Protection zones for modulo axes are not supported in this software version. The configuration is incompatible.
Root Cause Summary
Alarm 230-04E0 occurs when protection zones are incorrectly configured for modulo axes (typically rotary axes) on TNC systems that don't support this combination. The control detects an incompatible configuration between the axis type definition and protection zone settings.
Safety
- Refer to Heidenhain service manual
- Ensure qualified technician performs repairs
Causes and Fixes
- 1
Check axis configuration
Access Setup > Machine Parameters > Axes and verify if the affected axis has modulo settings enabled (parameter 1320 MODULO for the axis).
Look for MODULO = 360.000 or similar values indicating rotary axis wraparound
- 2
Review protection zones
Navigate to Setup > Protection Zones and check if any zones are defined for the modulo axis shown in the alarm message.
Document existing protection zone coordinates before making changes
- 3
Disable conflicting protection zones
Either deactivate the protection zones for the modulo axis or reconfigure the axis as non-modulo if protection zones are required.
Consider using software limit switches instead of protection zones for rotary axes
Call a technician if:
- ·Parameter restoration fails
- ·Software update required
- ·Axis behavior changes unexpectedly after correction
Prevention
- Verify axis type before configuring protection zones
- Document parameter changes during setup
- Regular parameter backup schedule
Common Mistakes
- Assuming all axes support protection zones
- Not checking modulo parameter when configuring limits
- Forgetting to restart control after parameter changes
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 freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.