100413

Check NC program line causing alarm

Navigate to Diagnostics > Alarms > Detail view to identify the specific NC block and variable mentioned in %1 parameter.

Use single block mode (SBL1) to isolate the exact program line causing the issue

Verify variable value ranges

Check if assigned values are within valid ranges for the specific system variable using SINUMERIK documentation or HMI variable monitor.

Never assign values outside documented ranges as this can cause system instability

Validate data type compatibility

Ensure the assigned value matches the expected data type (INTEGER, REAL, STRING) for the target variable using variable list in HMI.

Use DEF statements to explicitly declare variable types in subroutines

Test with corrected values

Modify the NC program with valid values and test in single block mode before full execution.

Identify the protected variable

Review the alarm detail to determine which system variable is being illegally accessed, typically shown in the %1 parameter.

Variables starting with $AA_, $AN_, $AC_ are often read-only status variables

Check variable access rights

Navigate to Commissioning > Machine data > Channel data > Variables to verify read/write permissions for the specific variable.

Modifying system variable access rights requires proper authorization and can affect machine safety

Modify program logic

Replace read-only variable assignments with appropriate read-write alternatives or remove the illegal write operation from NC program.

Validate program syntax

Use program editor syntax check function to verify all variable operations are legal before execution.

Backup current machine data

Navigate to Commissioning > Data backup/restore and create complete backup before making any changes.

Always backup machine data before modifications to prevent complete system reconfiguration

Check machine data consistency

Go to Commissioning > Machine data > Check data consistency to identify corrupted or invalid MD parameters.

Focus on MD32000 series for servo parameters and MD20000 series for channel parameters

Reset problematic parameters

Identify and reset invalid machine data parameters to default values using the machine data editor.

Use compare function with known good backup to identify changed parameters

Perform warm restart

Execute warm restart (POWER ON) to reinitialize system with corrected machine data parameters.

Check user access level

Verify current user login level in HMI status bar - some variables require manufacturer (8) or service (4) access level.

Access levels: End user (0), Qualified user (1), Expert (2), Service (4), Manufacturer (8)

Review variable format requirements

Navigate to Diagnostics > Service > Variables and check the format requirements for the specific variable being accessed.

Incorrect format in variable monitor can cause system errors or unexpected machine behavior

Use proper variable syntax

Ensure correct SINUMERIK variable syntax including proper axis indexing [AX1], [AX2] for axis-specific variables.

Use autocomplete function in variable monitor to ensure correct syntax

Validate through alternative method

If direct variable access fails, use appropriate HMI screens or NC commands to achieve the desired parameter change.