axismd.ai
Siemens SINUMERIK Controller
System · Intermediate · 30-120 minutes
Siemens 840D 4013 - Invalid NCU link configuration by machine data =, on NCU_1 =
Alarm 4013 occurs when the local NCU detects a mismatch in link module configuration parameters between itself and the master NCU in a multi-NCU cluster environment. The misalignment typically involves system clock time, communication baudrate, or maximum message retry parameters defined in machine data, preventing proper NCU-to-NCU synchronization.
4013
Siemens 840D 4013 - Invalid NCU link configuration by machine data =, on NCU_1 =
Invalid NCU link configuration by machine data =, on NCU_1 =
Siemens SINUMERIK 840D system notice 4013: Invalid NCU link configuration by machine data =, on NCU_1 =. This is a system-level notification regarding machine data or configuration. Note the message details and take the indicated action.
Root Cause Summary
Alarm 4013 occurs when the local NCU detects a mismatch in link module configuration parameters between itself and the master NCU in a multi-NCU cluster environment. The misalignment typically involves system clock time, communication baudrate, or maximum message retry parameters defined in machine data, preventing proper NCU-to-NCU synchronization.
Safety
- Refer to Siemens documentation
- Ensure qualified technician performs repairs
Causes and Fixes
- 1
Access Siemens HMI or SINUMERIK Operate panel; navigate to [Diagnosis] → [Machine Data] → [MD20101] and [MD20102]. Document the baudrate values shown on both the local NCU and the referenced master NCU in the error message (%3 parameter).
- 2
Power down both NCUs completely (wait 30 seconds). Edit MD20101 and MD20102 on the local NCU to match the master NCU settings exactly (e.g., both set to 100 Mbps for SERCOS III). Use [Edit] → [Machine Data] → [NCU Link] menu path.
Do not modify master NCU parameters during this process; synchronize slave NCUs to master.
- 3
Save changes and perform a warm restart (Ctrl+Alt+Delete on panel, or via NC START-UP). Verify alarm 4013 clears after cluster re-initialization completes (typically 15-30 seconds).
- 4
If alarm persists, document the actual values from both NCUs and contact Siemens service with the baudrate mismatch details and NCU firmware versions.
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 freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.