1004

Access NCK machine data

Navigate to Commissioning > Machine data > NCK-specific MD > Channel-specific data and locate MD11600 series parameters.

Always backup current MD settings before making changes

Verify alarm reaction settings

Check MD11600[n] values against the valid alarm reaction bit patterns in the SINUMERIK documentation. Common invalid combinations include conflicting STOP and CANCEL reactions.

Incorrect alarm reactions can compromise machine safety

Reset to default values

Set MD11600 entries to manufacturer default values, then perform NCK reset with POWER ON to activate changes.

Use HMI function 'Reset to default' for systematic restoration

Validate configuration

Trigger a test alarm condition to verify the alarm reaction behaves correctly without generating alarm 1004.

Check safety configuration consistency

In STEP 7 Safety, verify that all safety-related alarm reactions match the NCK machine data settings, particularly for emergency stop and safety door functions.

Safety configuration changes require qualified personnel

Compare F-DB blocks

Examine F-DB blocks in the safety program for any recent changes that affect NCK alarm handling, especially timeout and reaction parameters.

Use the safety signature comparison function to identify changes

Reload safety configuration

Download the verified safety program to the F-CPU and perform a complete safety acceptance test to ensure proper NCK integration.

Synchronize NCK and safety systems

Execute a coordinated restart of both NCK and safety systems to establish proper communication and alarm reaction synchronization.

Review software upgrade documentation

Check the SINUMERIK upgrade notes for changes to alarm reaction handling and any required machine data modifications for your specific version.

Focus on 'Migration' and 'Compatibility' sections in release notes

Run configuration migration tool

Use the SINUMERIK configuration migration utility in Commissioning > Service > Migration to update deprecated alarm reaction parameters.

Create a complete backup before running migration tools

Update machine data to new format

Manually update any alarm reaction machine data that wasn't automatically migrated, following the new software version's parameter structure.

Perform system validation

Execute a complete system test including all alarm scenarios to ensure compatibility with the new software version.

Verify hardware configuration MDs

Check MD10050, MD10060 (NUM_CHAN_AXES), and MD10070 (NUM_MACHAX) against the actual installed hardware configuration.

Use HMI diagnostics to compare configured vs. detected hardware

Scan actual hardware topology

Navigate to Diagnostics > Hardware and perform an automatic hardware scan to identify all connected drives and I/O modules.

Correct hardware machine data

Update the hardware configuration MDs to match the scanned hardware, ensuring all alarm reaction targets are valid for the actual system.

Incorrect hardware MDs can cause drive faults and system instability

Rebuild alarm reaction tables

Perform NCK reset and allow the system to rebuild internal alarm reaction tables based on the corrected hardware configuration.