axismd.ai
Siemens SINUMERIK Controller
Servo/Axis · Intermediate · 20-60 minutes
Siemens 25220 - Axis gear ratio changed with ESR enabled
SIEMENS alarm 25220 occurs when measuring cycles like CYCLE997/998/978 fail due to probe hardware malfunctions, incorrect machine data parameters, or violated cycle preconditions. The NCK generates this alarm when expected probe trigger signals are not received, measurement tolerances are exceeded, or required coordinate system references are invalid.
25220
Siemens 25220 - Axis gear ratio changed with ESR enabled
Axis gear ratio changed with ESR enabled
Because a change in the gear ratio has an effect on the retraction path traveled by the drive, no changes may be made to the gear ratio during the following periods of time: - Between the last programming of the retraction path with ESRR and the ESR enable - As from ESR enable The following machine data define the gear ratios of an axis MD31050 $MA_DRIVE_AX_RATIO_DENOM MD31060 $MA_DRIVE_AX_RATIO_NUMERA MD31064 $MA_DRIVE_AX_RATIO2_DENOM MD31066 $MA_DRIVE_AX_RATIO2_NUMERA The gear ratio must not be changed during the periods of time described above, e.g. by changing the parameter set Control reaction: NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm.
Root Cause Summary
SIEMENS alarm 25220 occurs when measuring cycles like CYCLE997/998/978 fail due to probe hardware malfunctions, incorrect machine data parameters, or violated cycle preconditions. The NCK generates this alarm when expected probe trigger signals are not received, measurement tolerances are exceeded, or required coordinate system references are invalid.
Safety
- Only qualified personnel should diagnose and clear control alarms; follow the machine builder's safety procedures and lockout/tagout where hardware work is required.
Causes and Fixes
- 1
Check Probe Status in HMI
Navigate to Diagnostics > Hardware > Measuring Probe and verify probe status shows 'Ready' and battery voltage >2.4V for wireless probes.
Use MD9410 to check probe interface configuration matches actual hardware setup
- 2
Verify Probe Trigger Function
In Manual mode, manually trigger probe and observe signal change in Diagnostics > PLC > Inputs. Check DB21.DBX for probe trigger bit status.
Ensure spindle is stopped before manual probe testing
- 3
Inspect Probe Connections
Check probe cable connections at machine interface and verify MD9400-9420 probe machine data parameters match hardware configuration.
Clean probe stylus and check for mechanical damage or bent stylus
Call a technician if:
- ·Probe hardware replacement needed
- ·Machine data backup/restore required
- ·Systematic measurement accuracy issues
Prevention
- Regular probe calibration using CYCLE996
- Validate cycle parameters in simulation mode
- Maintain clean probe stylus and connections
- Establish reference points before measuring
Common Mistakes
- Using incorrect probe type in MD9400
- Forgetting to establish coordinate system
- Setting unrealistic tolerance values
- Running cycles without proper tool compensation
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.