axismd.ai
Siemens SINUMERIK Controller
Spindle · Intermediate · 30-120 minutes
Siemens 22052 - Block spindle no standstill on block change
Alarm 22052 fires when a spindle is programmed as an active spindle or axis in the current block while a SPOSA (spindle positioning beyond block limits) command from a previous block has not yet completed. The NCK detects ongoing spindle positioning motion and blocks the new spindle command until standstill is reached.
22052
Siemens 22052 - Block spindle no standstill on block change
Block spindle no standstill on block change
The displayed spindle has been programmed as spindle or as axis even though a positioning operation is still running from the previous block (with SPOSA. spindle positioning beyond block limits). Example: N100 SPOSA [2] = 100: N125 S2 = 1000 M2 = 04; Error, if spindle S2 from block N100 is still running! Control reaction: NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm.
Root Cause Summary
Alarm 22052 fires when a spindle is programmed as an active spindle or axis in the current block while a SPOSA (spindle positioning beyond block limits) command from a previous block has not yet completed. The NCK detects ongoing spindle positioning motion and blocks the new spindle command until standstill is reached.
Safety
- Spindle hazard: ensure the spindle is at standstill before working near it; follow lockout/tagout procedures.
Causes and Fixes
- 1
Review NC program: locate SPOSA block and identify the immediately following block containing S-word or spindle M-codes (M3, M4, M5, M19). Example: N100 SPOSA[2]=100 should have dwell before N125 S2=1000.
- 2
Insert G04 (dwell) or M0/M1 (stop/optional stop) between SPOSA completion and next spindle command to ensure spindle reaches zero speed. Check MD37100 (SpindleTimeConstant) and MD37110 (MaxSpindleSpeed) to calculate adequate dwell duration.
Insufficient dwell may still trigger alarm if spindle encoder feedback (MD37250 SpindleIsAxisEncFeedback) shows non-zero velocity.
- 3
Verify SPOSA syntax: confirm SPOSA block references correct spindle number and target position value is valid per spindle configuration. Check if SPOSA uses WAITP condition or if block boundary crossing is expected.
- 4
Test program with reduced feedrate (FMAX or manual override 50%) and observe spindle actual speed (SDR spindle display) until it reaches zero before block change occurs.
Seeing Multiple Alarms?
Seeing another alarm with this one? Enter the code.
Get machine-aware diagnosis
AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.
Start freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.