101604

Identify the line number in the NC program where the alarm occurred by checking the alarm details and current block display.

Review the GUD variable definition file (GUD3.DEF, GUD4.DEF, etc.) to verify the actual array dimensions and confirm the valid index range.

Check the NC program line for the variable reference and verify the subindex value does not exceed the defined array size (e.g., if VAR[10] is defined, valid indices are 0-9).

Correct the program syntax to use valid subindex values or modify the GUD definition to accommodate the required array size, then reload the GUD file.

After modifying GUD definitions, a control restart may be required to activate changes

Check the alarm diagnostics buffer for the specific machine data number (MD) being accessed when the alarm triggered.

Consult the Siemens SINUMERIK 840D parameter manual for your specific software version to verify if the MD supports subindexing and what the valid range is.

MD structure varies between software versions - always use documentation matching your NCK software version

Review any synchronized actions, PLC access, or initialization files (INI) that may be accessing this MD with incorrect subindex syntax.

Correct the MD access syntax to remove the subindex if not applicable or use the correct subindex range as specified in documentation.

Access the GUD definition files via HMI (Settings > GUD) or service mode and review the DEF file for syntax errors, particularly in array declarations.

Look for inconsistencies such as missing brackets, incorrect dimension syntax (e.g., [n,m] vs [n][m]), or special characters in variable names.

Compare with a known good backup of the GUD file or verify against OEM machine documentation for correct variable definitions.

Always create backup of current GUD files before making modifications

Correct any syntax errors in the DEF file, save, and perform a control restart to recompile the GUD definitions.