61323

Access the active probing cycle call in the NC program. Identify the _KNUM assignment statement (typically appears as _KNUM=5xxxx or similar in CYCLE974-CYCLE998 macro invocation).

Ensure you are viewing the correct channel context matching alarm parameter %1.

Verify machine parameter MD 32000 (Probe configuration table entries) and related probe definition parameters (MD 32010-MD 32099). Cross-reference the 5th position value in _KNUM against the valid probe index range configured in these parameters.

Values differ by machine OEM configuration; consult machine documentation for valid probe indices.

Correct the _KNUM assignment to use a valid 5th position value within the range 0 to [max_probe_index-1]. For example, change _KNUM from 52000 to 51000 if only probe indices 0-8 are defined.

Test the corrected cycle block in MDI mode on the affected channel before resuming production program execution.

Inspect the probing cycle source code for both _KNUM and _MVAR assignments in the same block or preceding statements. Verify _MVAR points to a valid R-parameter (e.g., R10-R99) or local variable with sufficient scope for probe result storage.

Check that _MVAR variable is not declared as read-only or protected via OEM-specific parameter locks.

Access Diagnostics → Parameter → Measured values (or equivalent NCK menu) to confirm _MVAR address is accessible and not reserved by system functions. Verify variable type matches expected measurement result (REAL for analog probe, INT for digital trigger).

Cross-check MD 34100 ff. (Probe enable/disable and assignment parameters) to ensure _MVAR assignment is consistent with the probe index specified in _KNUM 5th position.

Some SINUMERIK configurations enforce strict _MVAR-to-probe-index pairings via machine parameters.

Reassign _MVAR to a confirmed free variable location and re-test the cycle block.

Verify installed SINUMERIK software version and probing cycle package version. Access Help → System Information or Diagnostics menu to confirm cycle library version matches machine parameter set (compare CYCLE macro release date against MD 32500 ff. probe parameter date stamps if available).

Extract and review the probing cycle source code (typically stored in /nc/cycles/ directory on SINUMERIK HMI or engineering station). Search for _KNUM assignments and validate the 5th position is set conditionally based on machine configuration, not hardcoded to an invalid value.

Do not modify OEM-supplied cycle macros without authorization; instead, request updated cycle library from Siemens or OEM.