What causes Siemens SINUMERIK alarm 26018?

Parameter or machine data configuration error. Hardware fault on the NC or drive component. Part program error or illegal command. Communication fault between NC and drive or I/O modules. Software or firmware error requiring system restart.

How do I fix Siemens SINUMERIK alarm 26018?

1. Note the complete alarm text including any axis, channel, or block number values. 2. Check for related alarms active simultaneously in the SINUMERIK alarm list. 3. Power cycle the machine to clear transient faults. 4. Review the SINUMERIK machine data for parameters related to the alarm. 5. Consult the Siemens SINUMERIK alarm manual for alarm 26018 detailed remedy.

axismd.ai

Siemens SINUMERIK Controller

Overtravel/Limit · Intermediate · 30-120 minutes

Alarm 26018

Siemens 840D 26018 - Axis setpoint output drive used more than once

Alarm 26018 fires when multiple axes are configured to output their setpoint commands to the same physical drive module via machine data 30110 $MA_CTRLOUT_MODULE_NR. This configuration conflict prevents proper axis control isolation and must be resolved by assigning unique drive modules to each axis.

Siemens SINUMERIKOvertravel/LimitIntermediate30-120 minutes

26018

Siemens 840D 26018 - Axis setpoint output drive used more than once

Axis setpoint output drive used more than once

Root Cause Summary

Alarm 26018 fires when multiple axes are configured to output their setpoint commands to the same physical drive module via machine data 30110 $MA_CTRLOUT_MODULE_NR. This configuration conflict prevents proper axis control isolation and must be resolved by assigning unique drive modules to each axis.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
Access Diagnostics > Machine Data > Axis-specific parameters in SINUMERIK HMI or via Siemens SCOUT TIA software. Navigate to axis [%1] configuration.
2
Review MD 30110 $MA_CTRLOUT_MODULE_NR for all configured axes (typically axis 1, 2, 3, 4). Document the module assignment for each axis.
Identify which axes share identical module numbers - these are in conflict.
3
Verify hardware configuration: confirm available drive modules in the control cabinet (check SINAMICS G120, POSMO, or equivalent modules installed). Each axis must map to a unique, physically installed module.
4
Reassign MD 30110 $MA_CTRLOUT_MODULE_NR for conflicting axes to unique module numbers (e.g., Axis 1 → Module 1, Axis 2 → Module 2). Save changes and perform warm restart (POWER OFF > 10 seconds > POWER ON).

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.