61102

Review NC program block sequence before CYCLE86/87/88/840/POCKET3/4 call. Insert M3 or M4 command minimum 1-2 blocks prior to cycle invocation.

Ensure M-code is in same channel as cycle call; verify via Diagnostics > Channel > Active M-functions menu

Check machine tool spindle control configuration: Verify MD10200 (SpindleRange[]) and MD10210 (SpindleDefaultDirection) are correctly parameterized for your spindle type in NCK > Spindle Data menu.

Validate cycle syntax: Ensure CYCLE86(param1, param2...) includes all mandatory parameters per SINUMERIK 840D macro library. Missing parameters may prevent proper spindle state initialization.

Navigate to Diagnostics > Machine > Spindle menu and verify spindle assignment to current channel. Check MD10100 (SpindleSelection) and MD28100 (IsSpindleAxis) parameters for axis assignment.

Verify spindle enable state via HMI Diagnostics > Axis > Spindle submenu. Confirm spindle power supply and encoder feedback are active (green status indicators).

Do not manually enable spindle if hardware fault exists; check servo drive LED status first

Reset alarm via soft reset (NC STOP + NC START) or parameter reload if spindle configuration was recently modified. Verify via NC > Parameter > Load from NVRAM.

Review canned cycle call syntax: Check CYCLE86/POCKET3 parameter list for spindle-related arguments (typically _SPDIR or _SPINDLEDIR). Verify parameter is set to M3 equivalent (1) or M4 equivalent (-1), not 0.

If using custom macro subroutine wrapper around canned cycle, ensure spindle M-code is issued in calling program context before CYCLE invocation. Use Program > Trace feature (HMI Diagnostics menu) to verify M-function execution order.

Trace must be enabled before alarm occurrence; restart program from block start

Check machine tool documentation for cycle-specific spindle mode requirements. Some cycles require S-value (spindle speed) programmed concurrently with M3/M4; verify via MD10220 (SpindleAcceleration) and program S-parameter presence.