axismd.ai
Siemens SINUMERIK Controller
Spindle · Intermediate · 30-120 minutes
Siemens 22036 - Block Axis/spindle Synchronism override not possible (reason
Alarm 22036 fires when a spindle synchronism offset correction is requested via DB31.6 'Correct synchronism' or $AA_COUP_CORR[Sn] variable, but the NCK cannot apply it because reference point approach, zero mark synchronization, or NC reset operations are active. This prevents the coupling correction from being processed during incompatible system states.
22036
Siemens 22036 - Block Axis/spindle Synchronism override not possible (reason
Block Axis/spindle Synchronism override not possible (reason
The synchronism override intended by setting the VDI interface signal DB31.,DBX31.6 'Correct synchronism' or writing variable $AA_COUP_CORR[Sn] cannot currently be considered. The reasons may be: - Reason 1: Reference point approach or zero mark synchronization for spindles is active. - Reason 2: Deletion of synchronism override is active. - Reason 3: Writing is not allowed Control reaction: Alarm display.
Root Cause Summary
Alarm 22036 fires when a spindle synchronism offset correction is requested via DB31.6 'Correct synchronism' or $AA_COUP_CORR[Sn] variable, but the NCK cannot apply it because reference point approach, zero mark synchronization, or NC reset operations are active. This prevents the coupling correction from being processed during incompatible system states.
Safety
- Spindle hazard: ensure the spindle is at standstill before working near it; follow lockout/tagout procedures.
Causes and Fixes
- 1
Verify homing status by checking the NCK status display: press [DIAGNOSIS] > [STATUS] > [AXIS/SPINDLE] and confirm no axes show 'REF POINT' state or 'HOMING IN PROGRESS' indicator.
Do not attempt to override synchronism while reference point approach is running; wait for completion indicated by MD32100 becoming FALSE.
- 2
Review part program for G74/G75 or automatic calibration cycles; these must complete before issuing synchronism correction commands via PLC interface (DB31.6).
- 3
If homing is stuck, perform controlled NC RESET (Ctrl+Del or key sequence per HMI); this clears active reference point approach and allows synchronism correction retry in next cycle.
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.