What causes Siemens SINUMERIK alarm 22035?

Programming error in the part program related to the spindle function. Spindle configuration parameter mismatch for the commanded operation. Spindle encoder signal fault preventing speed or position control. Spindle drive fault affecting the ability to execute the commanded function. Gear stage or spindle mode conflict with the commanded function.

How do I fix Siemens SINUMERIK alarm 22035?

1. Review the program block that triggered the alarm for spindle command errors. 2. Check the SINAMICS spindle drive diagnostics for fault codes. 3. Verify spindle encoder signal quality in the diagnostics screen. 4. Review spindle configuration parameters for the commanded gear stage and mode. 5. Consult the Siemens SINUMERIK alarm manual for alarm 22035 specific remedy.

axismd.ai

Siemens SINUMERIK Controller

Spindle · Intermediate · 30-120 minutes

Alarm 22035

Siemens 840D 22035 - Channel block following spindle unable to determine the

Alarm 22035 occurs when the SINUMERIK 840D cannot calculate the spindle override correction value ($AA_COUP_CORR[Sn]) via VDI signal DB31.DBX31.6 'Correct synchronism' because conflicting spindle synchronization conditions exist. This typically indicates either simultaneous following spindle motions or an improperly configured spindle coupling without active master spindle reference.

Siemens SINUMERIKSpindleIntermediate30-120 minutes

22035

Siemens 840D 22035 - Channel block following spindle unable to determine the

Channel block following spindle unable to determine the

Root Cause Summary

Alarm 22035 occurs when the SINUMERIK 840D cannot calculate the spindle override correction value ($AA_COUP_CORR[Sn]) via VDI signal DB31.DBX31.6 'Correct synchronism' because conflicting spindle synchronization conditions exist. This typically indicates either simultaneous following spindle motions or an improperly configured spindle coupling without active master spindle reference.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
Verify block sequence in NC program: ensure only one following spindle (Sn) executes per block. Check for G96/G97 mode conflicts or overlapping electronic coupling commands (COUPLE/DECOUPLE) in adjacent blocks.
Review the current block %2 and preceding 3-5 blocks for concurrent spindle synchronization commands
2
Inspect machine data MD18026 (CfgSpindleMode) and MD18028 (CfgFollowSpindleMode) for each spindle to confirm only one master/slave relationship is active. Verify MD35100 (CoupleSpindleMask) settings do not enable multiple simultaneous couplings.
3
Check SINUMERIK Operate > Diagnosis > Spindle menu for real-time spindle state: confirm slave spindle status shows 'idle' or 'coupled' (not conflicting states). Monitor $AC_SPINDLE[Sn].actual_override during execution.
4
Modify NC program to insert DECOUPLE commands or spindle stop (M5) between conflicting synchronization blocks. Allow 200-500ms dwell time between spindle mode transitions using G04.

Service Recommended confidence

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 free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.