Siemens SINUMERIK codes
Siemens SINUMERIKCommunicationBasic5 - 15 minutes

28003

Siemens 28003 - Synchronization of the life cycle in the NCU link failed after attempts.

Synchronization of the life cycle in the NCU link failed after attempts.

Siemens SINUMERIK alarm 28003: Synchronization of the life cycle in the NCU link failed after attempts. Detailed remedy is being verified against the current Siemens diagnostics manual.

Root Cause Summary

SINUMERIK alarm 28003 SS2 Active indicates that Safe Stop 2 (SS2) safety function has been triggered, causing controlled deceleration of drives to standstill while maintaining power to actuators. This typically occurs due to safety input activation, E-stop conditions, or safety PLC logic execution requiring immediate but controlled machine stop.

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. 1

    Check safety input status

    Navigate to HMI > Diagnostics > Safety > Safety Inputs and verify status of all configured safety inputs in MD36300 (SAFE_INPUT_ASSIGN).

    Use SINUMERIK Operate safety diagnostics screen to see real-time safety input states

  2. 2

    Inspect physical safety devices

    Verify all safety gates are properly closed, light curtains are unobstructed, and emergency stop buttons are not activated.

    Do not bypass safety devices - resolve the actual safety condition first

  3. 3

    Reset safety system

    After clearing safety condition, perform safety acknowledgment via HMI safety reset button or execute safety reset sequence defined in MD36350 (SAFE_RESET_MODE).

    Some systems require two-hand reset or key switch activation for safety reset

DIY Feasiblehigh confidence

Call a technician if:

  • ·Safety parameter modification required
  • ·PROFIsafe configuration changes needed
  • ·Safety acceptance test must be performed

Prevention

  • Regular safety device testing and maintenance
  • Monitor PROFIsafe communication statistics
  • Keep safety program documentation current
  • Perform periodic safety system validation

Common Mistakes

  • Bypassing safety devices instead of fixing root cause
  • Modifying safety parameters without proper validation
  • Ignoring intermittent safety communication errors
  • Not documenting safety events for compliance

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.