1013

Note the exact error number (%2 parameter) displayed with the alarm and document the machine operation that was occurring when the alarm triggered.

Perform a complete power cycle: Switch control OFF, wait 30 seconds, power ON and observe if alarm reoccurs immediately or during specific operations.

Ensure all axes are in safe positions and workpiece is secured before power cycling.

Access alarm logbook via Diagnostics menu and check for preceding alarms or warnings that may have caused the system error. Export alarm log for analysis.

If alarm persists, boot the system with NC backup data (START-UP mode) and restore the last known good NCK configuration. Contact Siemens support with error number for software patch evaluation.

Backup all current machine and part programs before restoring NCK data.

Identify and isolate the specific NC program block where the alarm occurred. Check the program for unusual nesting depth (>8 levels), excessive GOTO statements, or array boundary violations.

Reset the control (NC START disable) and attempt to run a simple test program (G0/G1 movements only) to verify basic channel functionality without the suspect program.

Review program for improper use of system variables, synchronized actions, or compile cycles. Simplify complex macro calls and reduce simultaneous polynomial/spline operations.

If a specific program consistently triggers the alarm, enable extended trace mode (SERUPRO access level) and capture detailed NCK execution log during alarm occurrence for analysis.

Trace mode significantly reduces system performance; use only for diagnostics.

Access Service menu and run NCU internal diagnostics. Check for hardware errors in the system memory test and processor communication status.

Machine operation will be interrupted during hardware diagnostics.

Inspect NCU module for proper seating, check all internal connectors, and verify cooling fan operation. Look for component overheating indicators or capacitor bulging.

Perform this check with power OFF and observe ESD precautions when handling electronic components.

Review NCK load statistics (display NCK load in diagnostics) to identify if system resources are consistently above 85%, indicating insufficient processing capacity for current configuration.

If hardware fault is suspected, swap NCU module with known good spare (if available) or contact Siemens for NCU diagnostics and potential replacement. Document error number for warranty claim.

NCU replacement requires complete system backup, software authorization transfer, and recalibration of all axes.