What causes Siemens SINUMERIK alarm 101154?

Normal control operation generated this status message. User action or program command triggered this notification. System configuration or commissioning activity produced this message. Machine data or parameter change created this notification.

How do I fix Siemens SINUMERIK alarm 101154?

1. Read the complete message text on the SINUMERIK screen — note any parameter values shown. 2. If action is required, follow the instructions in the message. 3. Acknowledge the message on the operator panel to continue operation. 4. Consult the Siemens SINUMERIK alarm documentation for message 101154 if clarification is needed. 5. If this message appears unexpectedly, review recent parameter or configuration changes.

axismd.ai

Siemens SINUMERIK Controller

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

Alarm 101154

Siemens 840D 101154 - PI service refused

Alarm 101154 indicates that a PI (Program Invocation) service request was refused because the NCK (Numerical Control Kernel) or drive system is not in the correct operational state to execute the requested function. This typically occurs when attempting to start programs, perform mode changes, or execute commands while the system is in a state that prohibits such actions, such as during active alarms, reset conditions, or incomplete startup sequences.

Siemens SINUMERIKProgram/G-codeIntermediate30-120 minutes

101154

Siemens 840D 101154 - PI service refused

PI service refused

Root Cause Summary

Alarm 101154 indicates that a PI (Program Invocation) service request was refused because the NCK (Numerical Control Kernel) or drive system is not in the correct operational state to execute the requested function. This typically occurs when attempting to start programs, perform mode changes, or execute commands while the system is in a state that prohibits such actions, such as during active alarms, reset conditions, or incomplete startup sequences.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
Check the machine control panel and HMI for active alarms, emergency stop status, or safety door interlocks that may prevent NCK ready state.
2
Verify NCK startup has completed successfully by checking NCK state in diagnostics (Service > NCK > Status) - must show 'ready' or 'active'.
3
Acknowledge any existing alarms and perform NCK reset (NC-Start or power cycle) to allow the system to reach operational state.
Ensure machine is safe before performing reset operations
4
Verify machine data MD11210 (NCK start sequence) and MD11200 (NCK boot mode) are configured correctly per machine specifications.

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.