What causes Siemens SINUMERIK alarm 25042?

The defined end position was not reached within the time specified in the machine data.

How do I fix Siemens SINUMERIK alarm 25042?

1. If the drive torque (FXST) was set too low with the result that the force of the motor was not sufficient to reach the end position -> increase FXST. 2. If the machined part is slowly deformed, there may be a delay in reaching the end position -> increase MD36042 $MA_FOC_STANDSTILL_DELAY_TIME. 3. Clear alarm with the RESET key in all channels of this mode group. Restart part program

axismd.ai

Siemens SINUMERIK Controller

Servo/Axis · Intermediate · 30-120 minutes

Alarm 25042

Siemens 25042 - Axis standstill monitoring during torque/force limitation

Alarm 25042 indicates that an axis failed to reach its commanded end position within the standstill monitoring time window while operating under torque or force limitation. This occurs when the NCK detects that axis motion has ceased before the target position was achieved, typically due to mechanical blockage, insufficient drive torque, or improperly configured monitoring parameters.

Siemens SINUMERIKServo/AxisIntermediate30-120 minutes

25042

Siemens 25042 - Axis standstill monitoring during torque/force limitation

Axis standstill monitoring during torque/force limitation

Root Cause Summary

Alarm 25042 indicates that an axis failed to reach its commanded end position within the standstill monitoring time window while operating under torque or force limitation. This occurs when the NCK detects that axis motion has ceased before the target position was achieved, typically due to mechanical blockage, insufficient drive torque, or improperly configured monitoring parameters.

Safety

Drive/power/encoder circuit: hazardous voltages may remain in the DC link after power-off. Lock out / tag out, wait for discharge per the drive documentation, and use qualified personnel only.

Causes and Fixes

1
Access Diagnostics > Axes > [Axis Name] > Parameters and verify MD32100 (Force Limitation Enable) status and MD32102-MD32105 (axis force limit setpoints). Compare against machine specification sheets for nominal torque/force ratings.
Do not increase force limits beyond machine mechanical specifications without engineering review.
2
In the NC program, check for G-code blocks with FMAX or FLIN declarations that may override default MD values. Verify these values are appropriate for the workpiece material and mechanical setup.
3
Increase the force limit incrementally (MD32102-MD32105) in 5-10% steps and re-execute the positioning cycle while monitoring actual axis load in Diagnostics > Measured Data > Drive Current.
4
If force limit is already at specification and alarm persists, escalate to mechanical inspection (backlash, wear, binding).

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.