What causes Siemens SINUMERIK alarm 104106?

Required machine data or parameter not configured for the requested function. Option bit not set in SINUMERIK to enable the required functionality. Program references a function or axis that has not been configured. Machine commissioning incomplete — required setup step was not performed. Configuration data cleared or lost due to a parameter reset or hardware change.

How do I fix Siemens SINUMERIK alarm 104106?

1. Read the full alarm message to identify what is missing (axis name, parameter number, function name). 2. Consult the SINUMERIK alarm manual for alarm 104106 for the specific configuration requirement. 3. Check the relevant machine data group and set the required parameter. 4. If a specific option is required, verify it is licensed and enabled in the SINUMERIK option settings. 5. Power cycle after making configuration changes to apply the new settings.

axismd.ai

Siemens SINUMERIK Controller

Program/G-code · Intermediate · 30-120 minutes

Alarm 104106

Siemens 840D 104106 - PA: No space in global memory

Alarm 104106 indicates the NCK (Numerical Control Kernel) has exhausted available global memory during program execution or parameter loading. This typically occurs when too many global user data (GUD) variables, tool data, or R-parameters are defined, or when memory-intensive programs are loaded without adequate memory allocation.

Siemens SINUMERIKProgram/G-codeIntermediate30-120 minutes

104106

Siemens 840D 104106 - PA: No space in global memory

PA: No space in global memory

Root Cause Summary

Alarm 104106 indicates the NCK (Numerical Control Kernel) has exhausted available global memory during program execution or parameter loading. This typically occurs when too many global user data (GUD) variables, tool data, or R-parameters are defined, or when memory-intensive programs are loaded without adequate memory allocation.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
Access HMI Commissioning mode and navigate to Setting Data > GUD Variables to review all defined global user data variables.
2
Check total memory usage in Diagnostics > NCK > Memory Usage to identify current global memory consumption percentage.
3
Delete or relocate unused GUD variables from global to channel or axis-specific scope to free memory.
Backup all GUD definition files before making modifications. Changing GUD structure requires NCK restart.
4
If necessary, increase global memory allocation via MD18230 $MN_MM_USER_MEM_DYNAMIC in machine data, then perform power cycle.
Verify sufficient total NCK memory before increasing allocation. Consult system memory map documentation.

Service Recommended confidence

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.