61543

Review the part program (NC code) block %2 where CYCLE402/435/442/447 is called. Verify the dresser parameter argument (typically the first or second positional parameter in the cycle call).

Block number references the NCK compilation address, not the source line number.

Confirm the dresser parameter value is set to 1, 2, or 3 only. Check for variables or expressions evaluating to invalid values (e.g., uninitialized variables, calculation errors).

Correct the cycle call syntax: ensure dresser argument is a literal integer 1–3 or a variable containing a valid integer in that range.

Do not use parametric expressions that resolve to out-of-range values.

Reload and verify the corrected part program via the NCK editor (Diagnostics > Program > Load) or MDI command line.

Access Diagnostics > Machine Data > Grinding Dressing to verify dresser tool definitions are present for all three dressing stations (dresser 1, 2, 3).

Dresser configuration is machine/process-specific; consult the machine builder's documentation.

Confirm that dresser tool offset data is loaded in the tool management system (TM or integrated tool database) for the selected dresser number.

If dressing tools are missing, create tool entries with appropriate geometry and kinematic assignments in the machine data editor.

Incorrect tool definitions can cause subsequent servo errors during dressing motion.

In the NC program, explicitly initialize the dresser parameter variable before each CYCLE call. Use format: R100 = 2 (or appropriate dresser number 1–3).

Variables persisting across block boundaries can accumulate incorrect values; reset before each cycle invocation.

Enable NCK debugging or trace mode (Diagnostics > Trace) to capture the actual parameter value passed to the cycle at the point of alarm.

Add assertion or guard logic in the NC program to validate the dresser variable: IF R100 < 1 OR R100 > 3 THEN issue error message and halt.

This prevents invalid values from reaching the servo layer.