What causes Siemens SINUMERIK alarm 103013?

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 103013?

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 103013 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 103013

Siemens 840D 103013 - No agreement could be given

Alarm 103013 occurs when the control system cannot obtain required agreement or confirmation from a necessary component, typically during configuration changes, safety circuit verification, or PLC handshake processes. This alarm indicates a communication breakdown or missing acknowledgment between the NCK (Numerical Control Kernel) and other system components such as PLC, HMI, or safety modules.

Siemens SINUMERIKProgram/G-codeIntermediate30-120 minutes

103013

Siemens 840D 103013 - No agreement could be given

No agreement could be given

Root Cause Summary

Alarm 103013 occurs when the control system cannot obtain required agreement or confirmation from a necessary component, typically during configuration changes, safety circuit verification, or PLC handshake processes. This alarm indicates a communication breakdown or missing acknowledgment between the NCK (Numerical Control Kernel) and other system components such as PLC, HMI, or safety modules.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
Check PLC status on the HMI under Diagnostics > PLC. Verify that the PLC is in RUN mode and not in STOP or error state.
2
Review the alarm buffer for preceding PLC alarms (61000-62999 range) that may indicate why the PLC cannot provide agreement.
3
Access PLC diagnostics and monitor the interface signals DB19 and DB21. Check for stuck bits or signals that should toggle but remain static.
Document current signal states before making changes for comparison.
4
Verify PLC program logic for acknowledgment signals related to mode changes, axis enable requests, or configuration changes. Look for missing RESET conditions or timeout logic errors.

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.