Siemens SINUMERIK codes
Siemens SINUMERIKCommunicationAdvanced30 - 90 minutes

28001

Siemens 28001 - NCU link connection to the NCU of the link network has been aborted

NCU link connection to the NCU of the link network has been aborted

All NCUs in the NCU link network exchange data cyclically (sign-of-life). If this alarm occurs, sign-of-life signals have not been received from one other NCU on the NCU network. (see alarm parameters) This fault in the link can have various causes: - Defective hardware. - The machine data which configure the NCU link are not identical on all NCUs. - An identical interpolator cycle time has not been selected on all NCUs Control reaction: NC not ready. Channel not ready. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm.

Root Cause Summary

SIEMENS alarm 28001 indicates a communication breakdown between the NCK (Numerical Control Kernel) and PLC (Programmable Logic Controller) subsystems within the SINUMERIK system. This alarm typically fires when the cyclic data exchange via the internal PROFIBUS-DP or PROFINET connection is interrupted or when communication timeouts exceed the configured threshold parameters.

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 PLC Cycle Time

    Navigate to HMI → Diagnostics → PLC → Cycle Time and verify the current PLC cycle time is within acceptable limits (typically <20ms for standard applications).

    Compare current cycle time with MD11210 PLC_TIMEOUT setting - cycle time should be significantly less than timeout value.

  2. 2

    Verify PROFIBUS Configuration

    Access HMI → Commissioning → Bus Systems → PROFIBUS-DP and check bus configuration, baud rate settings, and station addresses match the hardware configuration.

    Do not modify PROFIBUS settings during production - schedule downtime for configuration changes.

  3. 3

    Monitor Communication Statistics

    Use diagnostic buffer (HMI → Diagnostics → NCK → Messages) to check for recurring communication errors and examine PROFIBUS diagnostic counters for transmission errors.

  4. 4

    Adjust Timeout Parameters

    If cycle times are consistently high but stable, consider increasing MD11210 PLC_TIMEOUT value incrementally (default 200ms) after consulting system documentation.

    Document original parameter values before making changes for easy rollback if issues persist.

DIY Feasiblehigh confidence

Call a technician if:

  • ·Hardware replacement required
  • ·Parameter corruption suspected
  • ·Multiple simultaneous system faults
  • ·Safety system integration affected

Prevention

  • Regular PROFIBUS cable inspection and strain relief maintenance
  • Monitor PLC cycle times during preventive maintenance
  • Maintain backup copies of NCK and PLC configurations
  • Implement proper cable routing away from interference sources

Common Mistakes

  • Ignoring gradual increase in PLC cycle times before failure
  • Modifying timeout parameters without addressing root cause
  • Replacing hardware without verifying cable integrity first
  • Failing to backup configurations before troubleshooting

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.