22100

Access Diagnostics > Machine Data (MD) via SINUMERIK HMI or NCK Editor. Navigate to spindle-specific MD parameters (typically indexed by spindle number in $MA_SPIND_VELO_LIMIT[spindle_index]).

Document current MD 35100 value and compare against machine nameplate maximum speed and drive controller maximum speed setting (verify in SINAMICS control unit or servo drive parameter list).

Do not arbitrarily increase MD 35100 without confirming mechanical and electrical limits with machine manufacturer.

If MD 35100 is below rated spindle speed, increase it incrementally (e.g., +5%) and retest with M3/M4 commands below the new limit. Monitor actual spindle speed via Diagnostics > Actual Values > Spindle rpm feedback.

If alarm recurs after adjustment, check MD 1 reconfiguration flag and verify via System > Alarms > 22100 to confirm this alarm is enabled for your spindle group.

In SINUMERIK Diagnostics, open Actual Values > Spindle Data and log both commanded spindle speed (setpoint) and actual speed (feedback from encoder/resolver) during a speed ramp test (e.g., M3 S2000). Confirm overshoot magnitude.

Access the SINAMICS drive (HMI or Starter software) and review spindle servo loop parameters: proportional gain, integral gain, speed controller bandwidth, and acceleration/deceleration ramps. Cross-reference against SINAMICS tuning guidelines for your motor and load inertia.

Incorrect servo tuning can cause mechanical vibration or damage. Consult Siemens SINAMICS commissioning guide before modifying gains.

Reduce drive acceleration ramp time (e.g., in SINAMICS or via MD 35040 $MA_SPIND_ACCEL_TIME) and lower proportional gain slightly to dampen overshoot. Retest speed ramp and confirm overshoot is eliminated.

If overshoot persists, verify encoder/resolver signal quality and resolution at the drive (check signal voltage and frequency in drive diagnostics); a faulty or noisy feedback signal will cause control instability.

In the SINUMERIK HMI, open Diagnostics > Channel Information and note the active block number (%3 in the alarm message). Cross-reference the source NC program (DIN file) and locate the S-word command causing the overspeed.

Verify the S-word value does not exceed MD 35100 * 1.1 (e.g., if MD 35100 = 5000 rpm, alarm triggers above 5500 rpm). If program commands exceed this, reduce S-values or split high-speed operations into separate spindle groups with adjusted MD 35100.

Check if multiple spindles are active and whether the alarm references the correct spindle number (%2 in alarm). Confirm each spindle has its own MD 35100 index and that no program logic transfers high-speed commands between spindles with differing limits.