Overview of Alarm 25050 on Sinumerik 840D
Alarm 25050 [Channel %1:] Axis %2 contour monitoring is raised by the Sinumerik 840D NCK when the geometric deviation between the interpolated position setpoint and the actual position reported by the active measuring system exceeds the tolerance window configured for that axis. The alarm is axis-specific: on the ELB grinder reported here, the Y axis was the affected drive. Once the threshold is crossed, the NC clears the controller enable, drops the axis into follow-up mode, and freezes the part program until the operator resets.
Alarm 25050 is a symptom-level fault, not a root cause. The contour monitor is a parallel diagnostic running in the IPO cycle; it does not care why the actual position is lagging, only that the lag has crossed the configured limit. The four major categories of root cause are:
- Mechanical: brake not released, gearbox lock, coupling shear, lubrication failure, ballscrew binding, or excessive backlash.
- Electrical: open or high-resistance conductor in the motor power cable, brake cable, or encoder cable; connector pin damage; shield break; ground loop.
- Drive: SIMODRIVE 611D or SINAMICS S120 power module degraded, DC link under-voltage, IGBT fault, encoder interface failure.
- Feedback: encoder contamination, glass disc damage, resolver failure, feedback cable noise, zero-mark loss.
The reported incident is a textbook electrical/mechanical interaction: the brake release signal was interrupted between the relay output and the motor terminals, so the spring-applied holding brake remained engaged. The drive tried to accelerate a locked rotor, the actual position stayed at zero while the setpoint advanced, and the contour monitor tripped within milliseconds.
Sinumerik 840D Contour Monitoring Architecture
The contour monitor on the 840D operates inside the NCK as a virtual position comparator. The IPO breaks the programmed path into per-axis position setpoints at the IPO cycle (typically 4 ms to 12 ms depending on configuration). The position controller closes the inner loop by comparing the setpoint against the actual position returned by the active encoder, and outputs a velocity command to the drive. The contour monitor runs alongside that loop, continuously computing the difference between the setpoint trajectory and the actual trajectory, axis by axis.
Critically, the contour monitor uses the active measuring system. For most feed axes on a grinder, this is the motor-mounted encoder (encoder 1) unless MD 30200 $MA_NUM_ENCS is set to 2 and the second encoder is declared the active one. Selection of the active encoder is made by MD 30240 $MA_ENC_FEEDBACK_POL and the related bits in MD 30230 $MA_ENC_INPUT_NR.
When the deviation between setpoint and actual position exceeds the threshold defined in MD 36400 $MA_CONTOUR_TOL for longer than the IPO cycle count, the NC triggers 25050. The drive may also independently raise a drive-side alarm (for example 300608 Axis %1 drive %2 speed controller at limit) because the speed controller saturates while trying to force the rotor against the locked brake.
Key Machine Data for Contour Monitoring
| Machine Data | Description | Engineering Note |
|---|---|---|
| MD 36400 $MA_CONTOUR_TOL | Contour monitoring tolerance window (mm or deg) | Direct threshold for 25050. Default typically 1.0 mm. Do not increase to mask a real fault. |
| MD 36410 $MA_TOL_SWITCH_MON | Switch / standstill monitoring tolerance | Related; interacts with 25040 standstill alarm. |
| MD 32200 $MA_POSCTRL_GAIN (Kv) | Position loop gain (1/s) | Typical 1.0 to 16.0. Higher Kv tightens response but reduces tolerance to mechanical disturbance. |
| MD 32250 $MA_RATED_OUTVAL | Reference output for velocity normalization | Set to match drive rated speed in MD 32260. |
| MD 32260 $MA_RATED_VELO | Rated axis velocity (deg/min or mm/min) | Defines 100% velocity in the IPO. |
| MD 36310 $MA_ENC_ZERO_MONITORING | Encoder zero-mark monitoring | Type 0 disables, 1 enables. Loss of zero mark may interact with contour monitoring. |
| MD 30200 $MA_NUM_ENCS | Number of encoders on this axis | 1 = motor encoder only; 2 = motor + direct measuring system (e.g., glass scale). |
| MD 30240 $MA_ENC_FEEDBACK_POL | Active encoder and sign | Determines which encoder the contour monitor uses. |
| MD 36010 $MA_STOP_LIMIT_FINE | Exact-stop fine window | Defines exact-stop, not directly contour tolerance. |
| MD 36020 $MA_POSITIONING_TIME | Positioning time window | Time allowed for positioning after a move command. |
To inspect or change these values on the 840D HMI:
- Select Commissioning → Machine Data → Axis MD.
- Filter by the affected axis (for example Y2 or the configured logical axis name).
- Locate MD 36400 and record the existing value before any modification.
- Use the Search function with the mnemonic CONTOUR_TOL to confirm spelling.
1FT6082-1AF71-3AH1 Servo Motor Identification
The Y axis on the ELB grinder is driven by a Siemens 1FT6 series permanent-magnet synchronous servo motor, type 1FT6082-1AF71-3AH1. The order number breaks down as:
- 1FT6 — 1FT6 series synchronous servo motor, designed for SIMODRIVE 611 digital and SINAMICS S120 drive systems.
- 08 — Shaft height 80 mm.
- 2 — Stack length 2 (medium stack within the 80 mm frame).
- 1AF71 — Winding code and feedback variant (resolver or absolute encoder EQN/ECN family).
- 3AH1 — Option code: holding brake fitted, connector variant, shaft detail, and balance grade.
1FT6 motors in the grinder/feed-axis class are typically equipped with:
- A spring-applied, electrically-released 24 V DC holding brake.
- A motor-mounted encoder (resolver or absolute encoder depending on the 1AF7x sub-variant).
- Power and signal connectors sized for the 80 mm frame; on this motor the power connector carries the brake conductors.
For authoritative motor data, refer to the Siemens SIMODRIVE 1FT6 Configuration Manual and the nameplate on the actual motor. The nameplate lists rated torque, rated speed, rated current, holding brake voltage and current, the encoder type and resolution, and the IP rating.
Root Cause: Brake Release Signal Path Failure
The reported sequence of events points unambiguously to a brake release failure. The reasoning chain is:
- With the motor coupling physically disconnected from the gearbox, no mechanical load is applied to the rotor.
- The Y axis still trips 25050 immediately on any JOG command.
- Other axes (X, Z, V, W) move correctly in JOG, eliminating NCK-level and global drive faults.
- The PLC output that commands brake release is energized, the relay LED confirms actuation, and 24 V is measured on the relay contact load side.
- 0 V is measured at the motor-side brake terminal.
- Continuity testing of the cable run from the relay output to the motor connector reveals an open or high-resistance conductor.
A spring-applied holding brake requires continuous 24 V to release. With the supply missing, the brake remains engaged, mechanically locking the rotor. The drive cannot move a locked rotor no matter how much torque it commands, so the actual position remains at zero while the setpoint ramps. The contour monitor detects a deviation that grows faster than the tolerance window and trips 25050. The drive-side speed controller saturates and would also raise 300608 in steady state.
Brake Release Signal Path
The energy and signal chain from PLC to brake on a 1FT6 motor driven by an 840D system is:
The PLC digital output energizes the relay coil; the relay contact closes; 24 V is switched through the motor cable to the brake coil inside the 1FT6 motor. Any single break in this path keeps the brake locked. The PLC output, the relay contact, and the brake coil itself can each be a failure point; the motor cable is the most common intermittent offender on shop-floor machines, especially when run through a drag chain.
Step-by-Step Diagnostic Procedure
Use this procedure when an axis raises 25050 in JOG and the motor is decoupled from any mechanical load.
- Confirm the alarm and isolate the axis. On the HMI, read the active alarm list. Verify that 25050 names the expected axis. Note any drive-side alarm (for example 300608, 300507, or 300504) that appears at the same time.
- Decouple the mechanical load. Disconnect the motor coupling from the gearbox or ballscrew. This eliminates the mechanical load as a variable. A correctly released brake should let the rotor turn freely by hand once the drive enable is removed and the DC link is discharged.
- Check the brake release signal at the PLC output. Force the brake DO in the PLC, or observe the DO status when the axis is commanded to enable. Measure 24 V at the PLC terminal with respect to 0 V.
- Check the interposing relay. With the DO energized, the relay LED should be lit, the coil should be energized, and the contact should be closed. Measure 24 V on the load side of the contact.
- Check voltage at the motor terminal box or connector. With the relay still commanded, measure 24 V at the brake terminals on the motor. This is the critical measurement. 0 V here means the cable is open, the connector is damaged, or the brake coil is open.
- Continuity-test the brake conductors. Disconnect the cable at both ends. Measure end-to-end resistance. A good conductor reads near 0 ohm. An open or intermittent conductor reads OL or fluctuating high resistance, especially when the cable is flexed.
- Insulation-test the brake conductors. Use a 500 V insulation tester between each conductor and ground. A reading below 1 MΩ indicates insulation damage and a probable leakage path.
- Measure the brake coil resistance. At the motor terminal box, measure across the brake coil. 1FT6 holding brakes are typically in the tens of ohms to low hundreds of ohms. Compare with the nameplate specification. An open coil means the brake itself has failed and the motor must go to a Siemens repair center.
- Inspect the connector. Look for pushed-back pins, corrosion, oil ingress, or thermal discoloration. Pin damage on the power connector is a frequent cause of intermittent brake failure.
- Re-test with a known-good cable or with the cable replaced. Before declaring the motor faulty, substitute a known-good brake cable. If 25050 clears and the rotor turns, the original cable is confirmed as the failure.
If all the above checks pass and the rotor still will not turn, the fault is inside the motor or the drive module. The motor is then typically sent to an authorized Siemens repair center; the drive module is checked for proper enable signals, DC link voltage, and IGBT health.
Drive and Feedback Path Verification
Even when the brake is the root cause, the drive and feedback path should be verified before the axis is returned to production. A locked rotor can produce high current transients that stress the drive, and a brake failure may have masked an underlying drive issue.
| Check | Test Point / Method | Expected Result |
|---|---|---|
| DC link voltage | SIMODRIVE 611D: terminals P600 / M600 on the line module. SINAMICS S120: DC link test points on the Active Line Module or Smart Line Module. | Within drive rating, typically 600 V DC for a 400 V AC supply (no-load, may be higher). Steady, no ripple collapse. |
| Pulse enable | SIMODRIVE 611D: terminal 663. SINAMICS S120: PROFIBUS / PROFINET control word bit 0 or hardwired enable input. | Present when axis is commanded to move. |
| Controller enable | SIMODRIVE 611D: terminal 65.x. SINAMICS S120: control word bit 1 / STW1.1. | Present and stable during axis motion. |
| Drive ready signal | Relay output on the drive module, e.g. terminal 72 / 73.1 on SIMODRIVE 611. | Closed (ready) when the drive is healthy and enable signals are correct. |
| Encoder feedback integrity | HMI service screen for the drive, or SINUMERIK OPERATE → Diagnostics → Axis diagnostics. | Position actual value increments smoothly during a manual move, no spikes or jumps. Following error stays within tolerance. |
| Following error | Service display for the axis. | Stays within MD 36400 during motion and returns to zero at standstill. |
| Torque / current limit | Service display, drive parameter r0079 / r0080 (SINAMICS) or analog output on SIMODRIVE 611. | Stays well below rated current during normal moves. Saturation indicates a mechanical or brake problem. |
For SIMODRIVE 611D systems, refer to the SIMODRIVE 611D Function Manual for terminal assignments and the enable signal chain. For SINAMICS S120 retrofits or newer 840D sl installations, refer to the SINAMICS S120 Commissioning Manual and the Sinumerik 840D sl Operator Components and Networking Manual.
PLC Interface and Brake Release Signal Chain
The S7-300 PLC on an 840D-controlled machine typically handles brake control in the axis-specific user program. A simplified signal chain on a 1FT6 axis is:
- Axis enable logic. The PLC combines NC readiness, drive readiness, axis-specific interlocks, and operator enable requests. A dedicated axis enable bit feeds the brake and the drive enable signal in parallel.
- Brake DO. The PLC output is wired to the coil of an interposing relay, never directly to the brake. Driving the brake through a relay protects the PLC output and allows easy field-side diagnosis.
- Interposing relay. The relay contact switches 24 V from a fused source to the motor cable. A 24 V free-wheel diode is normally placed across the relay coil for PLC-side protection, and a suppression element across the brake coil inside the motor handles the inductive kick.
- Motor cable. The brake conductors share the power cable with the motor phases on most 1FT6 configurations. The cable is run through a drag chain on most grinder installations; this is the highest-risk section.
- Brake coil. 24 V across the brake coil releases the brake. Power removal re-applies the brake.
A useful PLC diagnostic is to read back the brake output through a dedicated DI or to monitor the brake current with an analog input. If the PLC commands the brake open but the current stays at zero, the break is downstream of the PLC and most likely in the cable or connector.
Cable and Connector Integrity Testing
The 1FT6 motor cable is the most common failure source for intermittent brake operation on production grinders. Cable damage modes include:
- Conductor fatigue break at the connector crimp, especially in drag-chain applications.
- Insulation chafing from cable ties, sharp edges, or chain links.
- Oil or coolant ingress into the connector, leading to corrosion and high resistance.
- Pin push-back in the power connector, intermittent on temperature or vibration cycles.
- Shield break causing EMC injection into the encoder cable run in the same chain.
Recommended field test sequence for the motor cable:
- Disconnect the cable at both the drive end and the motor end.
- Measure each conductor end-to-end with a low-voltage ohmmeter. Target < 0.5 ohm for power and brake conductors, < 1.0 ohm for encoder conductors.
- Run the cable through several full drag-chain cycles while monitoring resistance. A fluctuating reading under flex confirms a fatigue break.
- Perform a 500 V insulation test between each conductor and ground, and between conductor pairs. Reject below 1 MΩ.
- Inspect the connector pin condition under magnification. Replace the connector if any pin shows deformation, burning, or corrosion.
When replacing the cable, observe the manufacturer's minimum bend radius and drag-chain segregation rules. Encoder and power cables should not share a chain unless the chain is shielded and approved for mixed use. Failure to follow the routing rules often leads to repeat failures within weeks.
Related Alarms and Cascading Faults
A 25050 event rarely stands alone. The drive side typically reacts before or after the NC-side trip, and a single mechanical cause can produce a cascade of alarms in the alarm history.
| Alarm | Source | Meaning in This Context |
|---|---|---|
| 25050 Axis contour monitoring | NCK | Setpoint vs actual deviation exceeded MD 36400. Primary fault. |
| 25040 Standstill monitoring | NCK | Axis was commanded to stop but the actual position did not converge within tolerance. Often appears in the same alarm history. |
| 25020 Position setpoint limit | NCK | Position setpoint exceeded an axis limit. Cascades from uncontrolled follow-up. |
| 300608 Axis %1 drive %2 speed controller at limit | Drive (SIMODRIVE 611D / SINAMICS S120) | Speed controller output saturated at torque limit. Direct downstream effect of a locked rotor. |
| 300504 Encoder %1 frequency exceeded | Drive | Encoder interface overload. May indicate a damaged encoder cable or a defective encoder on a heavily loaded drive. |
| 300507 Commutation error | Drive | Encoder / motor pole pair mismatch or resolver failure. Independent cause but interacts with positioning. |
| 25201 Axis %1 drive %2 fault | Drive | Drive-side fault forwarded to the NC. Indicates a hardware issue inside the drive module. |
Investigate and clear every alarm in the history. A 25050 trip followed by a brief 300608 confirms the mechanical/lock scenario. A 25050 trip followed by 300507 or 300504 indicates a feedback-system failure and a different diagnostic path. Always read the full alarm history before concluding on root cause.
Verification and Re-Commissioning
After the cable is replaced and the brake is confirmed released at the motor terminals, the axis must be re-commissioned through a controlled sequence. Do not skip the verification steps; a partial release can produce a 25050 only under load and is harder to reproduce.
- Visual and electrical confirmation. With the drive disabled and the DC link discharged, confirm 24 V at the brake terminals in the motor terminal box. The brake should be released; the rotor should turn freely by hand.
- Drive-side enable check. On the HMI, command the axis to enable. Verify pulse enable, controller enable, and drive ready signals are present. Use the service display to confirm the position actual value updates with manual rotation of the motor shaft.
- Low-speed JOG test. Run the axis in JOG at a low override (5 to 10 percent) for at least 30 seconds in both directions. Watch for any momentary 25050 in the alarm bar. A brake that is partially engaging will trip 25050 under low-speed commutation stress.
- Contour test under load. Run a small G01 block at feedrate and inspect the following error on the service display. Following error should stay well within MD 36400 and return to zero at the end of the block.
- Full part program dry run. Run the full part program in dry-run or single-block mode. Inspect the contour trace on the HMI if available. The trace should match the programmed path within the configured tolerance.
- Production ramp-up. Bring the machine back to production at reduced feedrate for the first 5 to 10 parts, then to normal feedrate. Log the alarm history daily for the first week.
Preventive Maintenance Recommendations
For grinders with 840D controls and 1FT6 feed motors, build the following checks into the scheduled maintenance plan:
- Monthly: Brake voltage check. With the axis enabled, measure the brake voltage at the motor terminal box. Target 24 V ± 10 percent. Any reading below 22 V indicates a cable or connector issue developing.
- Monthly: Cable drag-chain inspection. Visually inspect the cable along the chain run. Look for kinks, jacket abrasion, exposed shielding, and oil or coolant ingress. Check that the chain radius matches the manufacturer specification.
- Quarterly: Connector pin inspection. Disconnect the motor connector and inspect pin condition under magnification. Replace the connector at the first sign of pitting, discoloration, or push-back.
- Quarterly: PLC output load check. With the brake released, measure the DC current drawn by the brake through the relay. Compare with the nameplate value. A drop in current indicates cable degradation; a rise indicates coil degradation or partial short.
- Annually: Insulation test. Perform a 500 V insulation test on the motor power cable, encoder cable, and brake conductors. Reject any reading below 1 MΩ. Replace the cable proactively if insulation is degrading.
- Annually: Axis service data review. Export the axis service data (following error peak, current peak, brake voltage history) from the HMI. Trend the data to detect a developing mechanical or electrical issue before it trips 25050.
- Annually: Brake release time check. Measure the time from PLC DO command to the point the drive actual position begins to move. Compare with the baseline. A rising release time indicates a brake nearing end of life.
Summary of the Reported Incident
| Item | Detail |
|---|---|
| Machine | ELB CNC Grinder |
| Control | Siemens Sinumerik 840D |
| Alarm | 25050 Y Axis contour monitoring |
| Affected drive | Y axis servo drive |
| Motor | Siemens 1FT6082-1AF71-3AH1 (1FT6 series, shaft height 80 mm, with holding brake) |
| Feedback | Motor-mounted encoder (encoder 1) |
| Mechanical decoupling | Motor coupling removed from gearbox; fault persisted, eliminating load |
| PLC output | OK (24 V present) |
| Interposing relay | OK (LED on, contact closed, 24 V on load side) |
| Motor-side brake voltage | 0 V (open circuit) |
| Continuity test | Open / high-resistance conductor in motor brake cable |
| Repair action | Replace motor brake / power cable |
| Result | Axis returns to operation, 25050 cleared |
The lesson is operational: a 25050 alarm on a single axis with the motor decoupled almost always reduces to a brake, encoder, or drive enable problem. A PLC-output OK, relay OK, motor-side 0 V reading points squarely at the cable or connector. Replacement and verification complete the loop.
What does Sinumerik 840D alarm 25050 mean?
Alarm 25050 is the NCK contour monitoring alarm. It triggers when the deviation between the position setpoint calculated by the NCK and the actual position reported by the active measuring system exceeds the tolerance window defined in MD 36400 $MA_CONTOUR_TOL. It is a symptom-level fault indicating the axis is not following its commanded path within the configured window.
Can I increase MD 36400 to clear alarm 25050?
You can increase the value, but it is strongly discouraged. The tolerance window is a safety boundary; increasing it masks real mechanical, drive, or feedback failures and risks scrap, tool damage, or crash. The correct response is to identify and fix the underlying cause, then keep MD 36400 at its engineered value.
How do I confirm a brake release failure on a 1FT6 motor?
With the drive disabled and the DC link discharged, measure 24 V DC directly at the brake terminals in the motor terminal box while the PLC commands the brake to release. 0 V at the motor with 24 V at the relay output indicates a cable or connector fault. Confirm with end-to-end continuity and 500 V insulation testing of the brake conductors.
Why does the motor still not turn in JOG with the gearbox disconnected?
With the gearbox decoupled, the only thing restraining the rotor is the holding brake. A spring-applied, electrically-released 1FT6 brake locks the rotor whenever 24 V is absent. Drive enable is present, the drive tries to accelerate, the rotor cannot move, the actual position stays at zero, and the contour monitor trips 25050 within the first IPO cycle.
What other alarms should I expect alongside 25050 on a locked rotor?
The drive typically raises 300608 Axis %1 drive %2 speed controller at limit because the speed controller saturates while trying to force the locked rotor. The NC may also raise 25040 standstill monitoring if the axis was supposed to be stationary, or 25020 position setpoint limit if follow-up is triggered. Always read the full alarm history before concluding the root cause.
Which Siemens manual lists the 25050 alarm and contour monitoring parameters?
Alarm 25050 is documented in the Sinumerik 840D sl Diagnostics Manual and the Parameter Manual. The contour monitoring machine data are described in the Sinumerik 840D sl Machine Data Lists. The 1FT6 motor family is documented in the SIMODRIVE 1FT6 Configuration Manual. Drive enable and terminal assignments are in the SIMODRIVE 611D Function Manual for legacy installations and the SINAMICS S120 Commissioning Manual for current installations.