axismd.ai
Siemens SINUMERIK Controller
System · Intermediate · 30-120 minutes
Siemens 4017 - Axis container , location already used by NCU
Alarm 4017 fires when the same axis container location is assigned to multiple logical axes in the machine data parameter MN_AXCONF_LOGIC_MACHAX_TAB. In multi-NCU configurations, this conflict may originate from another NCU in the NCU group, causing resource contention at the hardware interface level.
4017
Siemens 4017 - Axis container , location already used by NCU
Axis container, location already used by NCU
A multiple reference to the axis container location has been made via the logical axis table (MD10002 $MN_AXCONF_LOGIC_MACHAX_TAB). With the NCU link, the multiple reference may also have been made by another NCU in the NCU group. Example: Container1 location1 was referenced twice incorrectly - $MN_AXCONF_LOGIC_MACHAX_TAB[0] = CT1_SL1 - $MN_AXCONF_LOGIC_MACHAX_TAB[6] = CT1_SL1 Control reaction: NC not ready. Channel not ready. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Alarms.
Root Cause Summary
Alarm 4017 fires when the same axis container location is assigned to multiple logical axes in the machine data parameter MN_AXCONF_LOGIC_MACHAX_TAB. In multi-NCU configurations, this conflict may originate from another NCU in the NCU group, causing resource contention at the hardware interface level.
Safety
- Only qualified personnel should diagnose and clear control alarms; follow the machine builder's safety procedures and lockout/tagout where hardware work is required.
Causes and Fixes
- 1
Access Siemens HMI: Diagnostics > Machine Data > MD 30100 (MN_AXCONF_LOGIC_MACHAX_TAB). Export or screenshot the entire logical axis table to identify duplicate [Container, Location] pairs.
Do not modify machine data while the machine is in AUTO mode; switch to MANUAL/EDIT first.
- 2
Cross-reference the duplicate container/location entry with the axis alias name. Determine which logical axis assignment is incorrect based on machine kinematic design and CAM profile requirements.
- 3
Correct the erroneous row by reassigning it to an unused Container/Location pair. Verify availability in the axis container resource pool (typically MD 30110 and related axis declaration parameters).
- 4
Save machine data changes and trigger a cold restart (Ctrl+Shift+F5 or power cycle NCK). Verify alarm clears in Diagnostics > Alarms > Active Alarms list.
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.