Resolving Siemens 802D Alarm 25030 After Simodrive 611 Power Module Replacement
Alarm 25030 on a Sinumerik 802D-controlled turning centre, surfacing immediately after a Simodrive 611 LT-module (line/transistor power section) swap, is one of the most frequently misdiagnosed spindle faults in field service. The drive is mechanically intact, the motor rotates briefly under command, and the controller inhibits the axis within a fraction of a second. Operators typically assume the new power section is defective, or that the firmware is incompatible, when the actual root cause is a mismatch between the commanded velocity and one of the speed-monitoring thresholds, a corrupted or partial parameter set, an inverted phase, or — as confirmed in the field case documented here — a multi-stage gearbox that was not re-engaged correctly after the module change. This reference walks through the diagnostic ladder, the specific machine data to check, the SimoCom U validation procedure, and the mechanical checks that must always be performed before returning the spindle to production.
Affected Hardware and Configuration
The reported case involved a turning CNC controlled by a Sinumerik 802D with a Simodrive 611 U (universal) spindle drive. The failed and replacement modules were:
| Item | Failed Module (Original) | Replacement Module (New) |
|---|---|---|
| Siemens MLFB / Order Number | 6SN1123-1AA00-0LA1 | 6SN1123-1AA00-0LA3 |
| Designation | LT power section (Line / Transistor Module) | LT power section (Line / Transistor Module) |
| Drive family | SIMODRIVE 611 U / 611 D | SIMODRIVE 611 U / 611 D |
| Control board | 611U (6SN1118-xDAxx-xAAx/ABx) | 611U (6SN1118-xDAxx-xAAx/ABx) |
| Controller | Sinumerik 802D | Sinumerik 802D |
| Spindle | 1PH / 1PH2 induction spindle motor | 1PH / 1PH2 induction spindle motor |
| Mechanical gear | 3-stage gearbox (low / mid / high) | 3-stage gearbox (low / mid / high) |
The trailing designator in the 6SN1123 MLFB identifies the power-section variant (current rating, internal configuration, and resolver/external-encoder interface). A 0LA1 and a 0LA3 are both 611U LT modules but they are not bit-for-bit equivalent: the inverter stage, the brake-chopper sizing, and the assigned drive parameters (notably P1100–P1103 on the 611U control board) differ between the two suffixes. Swapping a 0LA1 for a 0LA3 is mechanically compatible but it is not a transparent, drop-in replacement — the spindle must be re-commissioned so the new power-section code is written into the drive's parameter set and the speed/position controller is re-tuned to the new IGBT stage. Skipping this re-commissioning is the single most common reason alarm 25030 appears on first spindle command.
For the full 611U configuration list, refer to the SIMODRIVE 611 universal / digital configuration manual and the Sinumerik 802D base software / diagnostics guide in the Siemens Industry Online Support portal.
Alarm 25030: Definition and Triggers
Alarm 25030 belongs to the Sinumerik 802D axis-monitoring class. According to the 802D Diagnostics Guide, alarm 25030 is the "actual velocity has exceeded the monitoring threshold" alarm. The 802D continuously compares the position-controller-derived actual velocity against the threshold defined in machine data MD 36200 AX_VELO_LIMIT. When the actual velocity exceeds this limit, the controller clears the axis enable, ramps down the drive, and latches alarm 25030.
The standard remedies listed in the Diagnostics Guide are:
- Check the speed setpoint cable (bus / PROFIBUS cable from the NCK to the drive).
- Check the actual values and the position-control direction.
- Reverse the position-control direction by setting
MD 32110 $MA_ENC_FEEDBACK_POL = < -1 / 0 / 1 >. - Increase the monitoring limit value in
MD 36200 $MA_AX_VELO_LIMIT.
MD 36200 is a workaround, not a fix. The correct value of MD 36200 is 5–10 % above the maximum axis velocity stored in MD 32000 $MA_MAX_AX_VELO. Raising MD 36200 past the safe envelope of the mechanical system hides the real fault — typically a wrong sign, a wrong gearbox stage, or a wrong spindle-encoder polarity — and risks mechanical damage on the next rapid move.On Simodrive 611U, alarm 25030 is also raised when the 611U's own speed monitoring trips and the fault word is propagated to the 802D. The relevant 611U parameters to inspect are:
| 611U Parameter | Designation | Typical Value (Spindle) | Notes |
|---|---|---|---|
| P1401 | Speed monitoring, max speed | ≈ 110 % of max mechanical speed | Mirror of MD 36200; do not desynchronise. |
| P1405 | Speed monitoring, threshold | 110 % of P1401 / MD 36200 | Final cutoff for alarm 25030. |
| P1100 / P1101 / P1102 | Power section code | Must match the installed LT module suffix | Wrong code = wrong current/torque limits. |
| P1110 / P1111 / P1112 | Motor code | Per motor nameplate | Selected by the spindle commissioning wizard. |
If the 802D also reports alarm 25020 (position-control monitoring) or 25050 (contour monitoring), the root cause is the same physical event — an uncontrolled velocity excursion — and the diagnostic path in this document applies unchanged.
Pre-Replacement Preparation
Before removing the suspect LT module, capture the following so you can verify the new module behaves the same way after re-commissioning:
- Back up the 802D NC machine data. On the 802D, navigate to Commissioning → NC data → MD and save the MD list to a CF card or to a backed-up commissioning file (MMC). The original machine-builder commissioning file is mandatory for a like-for-like module replacement.
-
Back up the 611U drive parameters. Connect a PC running SimoCom U (Siemens ordering designation SimoCom U Tool, ordering number 6SN1117-2CA00-0AA0) to the 611U's serial X471 service port. Read the parameter set, save it as a
.dptfile, and copy it to a known-good laptop. - Label the power cabling. Mark U, V, W and the protective earth at both ends of the motor cable and at the DC-link terminals. A swapped U-V-W pair inverts the rotating field and is the second-most common cause of 25030 after a parameter fault.
-
Verify the new module suffix. The new 6SN1123-1AA00-0LA3 must be the suffix listed in the machine-builder BoM. Do not substitute a similar suffix (e.g.,
0LA2or0LA4) without re-validating the entire spindle parameter set. - Verify input voltage and DC bus. Confirm the 600 V DC link is discharged before unplugging. The 611U has a 5-minute discharge time after the line contactor opens; measure at the DC bus test points before contact.
Step-by-Step Diagnostic Procedure
Execute the following steps in order. Do not skip the lower steps when a higher step appears to clear the alarm — in the field case documented here, every step (a)–(e) was performed and the alarm persisted, which correctly steered the engineer toward the mechanical root cause at step (f).
- Confirm the 802D alarm log. Read the alarm history under Diagnosis → Alarm log. Multiple 25030 entries with no 25020 or 25021 in between confirm a clean velocity-excursion event rather than a position-controller instability.
-
Cross-check MD 32000 and MD 36200. The maximum axis velocity (
MD 32000) and the monitoring threshold (MD 36200) must be consistent. As a rule of thumb:MD 36200 = 1.05 × MD 32000to1.10 × MD 32000. If MD 32000 has been changed (for example, by a parameter reset), MD 36200 must follow. -
Verify the encoder polarity. Issue a small M03 S100 command and observe the actual velocity feedback. If the actual velocity reads negative while the setpoint is positive, the encoder polarity is inverted. Set
MD 32110 $MA_ENC_FEEDBACK_POLto the opposite sign, or swap the resolver / encoder leads per the 802D commissioning manual. - Check the 611U drive enables in SimoCom U. Connect SimoCom U and verify that all enable indicators in the lower-left status block are GREEN. Any orange or red LED — particularly Pulse enable and Controller enable — will cause the drive to ignore or immediately revoke the command.
-
Compare 611U parameters against the original commissioning file. Load the original
.dptfile into SimoCom U and run an Online → Parameter list → Compare. The only difference should be the power-section code (P1100–P1103) and the resulting current-loop gains. If any other parameter has drifted, restore it to the original value. - Re-commission the spindle. If the power-section code has changed, run the SimoCom U commissioning wizard and re-load the motor code, the current-loop gain, the speed-loop gain, and the field-weakening threshold. A power-section swap that changes the IGBT module forces a fresh Calculate controller data pass.
- Verify the gearbox mechanical stage. Command M03 S100 with a small programmed gear stage. Observe the actual velocity feedback. If the actual velocity reads approximately 10× the setpoint, the gearbox has been left in the wrong stage (typically the high-speed stage while the controller still commands the low-speed ratio). Engage the correct gear stage and re-test.
Machine Data Verification: MD 32000, MD 36200, MD 32110
The three machine data words that govern the velocity envelope on the 802D are:
| Machine Data | Designation | Default (Spindle) | Safe Range | Effect |
|---|---|---|---|---|
| MD 32000 $MA_MAX_AX_VELO | Maximum axis velocity | 10 000 mm/min (linear) or 1000 rpm (spindle) | Per machine builder | Sets the highest velocity the axis is allowed to move at. |
| MD 36200 $MA_AX_VELO_LIMIT | Axis velocity monitoring threshold | 115 % of MD 32000 | 105–110 % of MD 32000 | If actual velocity exceeds this, alarm 25030 trips. |
| MD 32110 $MA_ENC_FEEDBACK_POL | Encoder feedback polarity | 1 | -1, 0, or 1 | Sign inversion of the actual velocity. A wrong sign = runaway at first command. |
The relationship is simple but rigid:
MD 36200 = (1.05 to 1.10) × MD 32000
If MD 32000 = 3000 rpm (a typical spindle maximum for a turning centre with a 3-stage gearbox in the high-speed range), then MD 36200 must be set between 3150 rpm and 3300 rpm. Setting MD 36200 = 5000 rpm to "stop the alarm" is unsafe — a real runaway that exceeds the mechanical rating of the spindle bearings will no longer be caught by the controller.
MD 32110 is the most dangerous of the three to leave in the wrong state. A polarity error of the spindle encoder means that on the first M03 command the controller believes the spindle is decelerating (because the actual velocity reads opposite to the setpoint) and increases the output. The drive then accelerates the spindle past MD 36200 in a fraction of a second, the monitoring trips, and alarm 25030 is raised. If you see the actual velocity feedback swing the wrong way at the moment of command, do not raise MD 36200 — invert MD 32110 instead.
SimooCom U Commissioning Tool Validation
SimoCom U is the PC-based commissioning tool for Simodrive 611U drives. The tool talks to the drive over a serial RS-232 cable on connector X471, or over PROFIBUS if the optional CBP module is fitted. The tool gives full read/write access to the drive's parameter set and a live diagnostic screen that mirrors the drive's enable word, the actual velocity, the current, and the DC-link voltage.
Validation sequence after the new LT module is bolted in:
- Connect SimoCom U, go online, and read the parameter list.
- Open Commissioning → Drive configuration and confirm the displayed power-section code matches the 6SN1123-1AA00-0LA3 suffix on the new module's nameplate.
- Open Commissioning → Motor configuration and confirm the motor code matches the nameplate of the 1PH / 1PH2 spindle motor.
- Open Diagnostic → Status word and check every status LED. All six enable indicators (Pulse enable, Controller enable, Speed controller enable, Setpoint enable, Drive enable, On) must read GREEN before the drive will accept a command from the 802D.
- Open Commissioning → Controller data and click Calculate. The wizard uses the new power-section code and the motor code to compute the current-loop, speed-loop, and field-weakening parameters. Accept the calculated values and write them to the drive.
- Save the parameter set to a
.dptfile on the laptop.
The screenshot referred to in the source field report showed a partially-discharged enable word on SimoCom U — a common red herring. After a power-section swap, the drive may also be in a latched-fault state from the old module's final fault. Clear all latched faults (SimoCom U: Diagnostics → Clear fault) before commanding the spindle.
Wiring and Phase Verification
A Simodrive 611U LT module drives a 3-phase AC motor from the U2, V2, W2 terminals on the front of the module. The cable between the module and the motor is a 4-core shielded cable (U, V, W, PE). If two of the three phase conductors are swapped (for example, U and V reversed), the rotating field in the motor inverts and the motor runs the wrong way. The 802D sees the inverted direction through the encoder and reacts by trying to correct the polarity — which, because the encoder is now reading a negative rotation, is interpreted as runaway.
Verification procedure:
- De-energise the cabinet, wait five minutes, verify zero DC-link voltage, then disconnect the motor cable at the LT module terminals.
- Using a continuity tester, ring out U, V, W, and PE from the module side to the motor side. Each conductor must trace to the same letter at the motor junction box.
- Verify the shield is bonded to PE at the cabinet end and isolated at the motor end (or bonded on both ends through a high-frequency low-impedance bond — follow the machine-builder drawing).
- Re-connect, torque to the spec on the terminal label (typically 4 Nm for the 6SN1123-1AA00-0LAx LT module), and re-verify with a second continuity test.
The original field report explicitly verified that the U, V, W phases were not swapped, which correctly moved the diagnostic focus away from the wiring and toward the gearbox.
Mechanical Verification: Gear Box Position
The single most common reason a 25030 alarm persists after a clean electrical re-commissioning of the spindle is a multi-stage gearbox that has been left in the wrong stage. On a 3-stage turning-centre spindle, the gearbox is typically shifted by an external gear-change actuator (a hydraulic or electric shift cylinder plus a position switch for each stage). The 802D commands the spindle through the M40–M45 range and selects the gear stage that the controller thinks is currently engaged.
The failure mode looks like this:
- Mechanic removes the LT module for replacement and disconnects the spindle encoder cable and the motor cable at the LT module end.
- While the cables are loose, the gearbox is bumped (or was previously left in mid-shift), so the gear-change actuator is sitting in the high stage position while the controller still has the low stage selected.
- The new LT module is installed, the spindle is re-commissioned in low stage, and the controller commands M03 S100 — expecting a spindle speed of 100 rpm at the chuck.
- The gearbox is actually in high stage (1:10 ratio), so 100 rpm commanded at the motor becomes 1000 rpm at the chuck. The actual velocity exceeds
MD 36200. Alarm 25030 trips.
Diagnostic check: with the spindle stopped and the spindle override forced to 0 %, command M03 S100 and watch the actual velocity in the 802D's Axis service screen. If the actual velocity reads approximately the gearbox ratio × the commanded velocity, the gearbox is in the wrong stage. Shift the gearbox to the correct stage, re-home the spindle, and re-test.
Final Resolution Path
Summarising the diagnostic ladder for a 802D / Simodrive 611U spindle that raises alarm 25030 after a 6SN1123-1AA00-0LAx power-section swap:
| Step | Check | Tool / Reference | Pass Criterion |
|---|---|---|---|
| 1 | 802D alarm log | 802D HMI → Diagnosis | 25030 entries present, no 25020 in between |
| 2 | MD 32000 vs. MD 36200 ratio | 802D HMI → Commissioning | 36200 = 1.05–1.10 × 32000 |
| 3 | Encoder polarity | MD 32110 + axis service screen | Actual velocity sign matches setpoint sign |
| 4 | SimoCom U enable word | SimoCom U → Status | All six enable LEDs GREEN |
| 5 | 611U parameter compare | SimoCom U → Online compare | Only power-section code differs from original file |
| 6 | Controller data recalculation | SimoCom U → Calculate | Current/speed loop gains regenerated |
| 7 | U / V / W phase continuity | Continuity tester | Each phase maps letter-to-letter |
| 8 | Gearbox mechanical stage | Manual actuation + position switch | Actuator position matches controller-selected stage |
Field-Validated Lessons
- A power-section swap is not firmware work. The 611U control board firmware does not change when the LT module changes. Re-flashing the firmware will not clear alarm 25030 and may introduce additional fault codes (notably F-0070 or F-0071 on the 611U side) if the firmware version drifts away from the boot loader version.
- Original parameter files are irreplaceable. If the machine builder's commissioning file is lost, contact the OEM or a Siemens service partner with the 802D serial number and the 611U control board's order number (6SN1118-xDAxx-xAAx/ABx). The parameter set can be regenerated from the motor nameplate, but the gearbox ratios, the encoder pole count, and the OEM-specific protection limits will not be recovered without the original file.
- Mechanical disturbances count. A gearbox that was bumped during the module swap is statistically the most common cause of a 25030 alarm that survives a clean electrical re-commissioning. Always verify the gear-stage position switch and the actuator state before declaring the spindle healthy.
- Do not raise MD 36200 to clear the alarm. The monitoring limit exists to protect the mechanical envelope. Raising it past 1.10 × MD 32000 hides the real fault and risks a runaway event on the next rapid move.
- Allow the DC link to discharge. Five minutes minimum, then verify with a meter. Hot-swapping the LT module with a charged DC link will trip the line-side input fuse and may damage the new module's IGBT stack on insertion.
Frequently Asked Questions
Does replacing a Simodrive 611 LT module require a firmware update on the 611U control board?
No. A 6SN1123-xAAxx-0LAx LT-module swap does not require a firmware update. Re-commission the spindle with SimoCom U so the new power-section code is written into the drive parameter set, then recalculate the current-loop and speed-loop gains. Reflashing firmware without a documented trigger will typically introduce F-0070 or F-0071 faults on the 611U.
What is the difference between 6SN1123-1AA00-0LA1 and 6SN1123-1AA00-0LA3?
Both are 611U LT power sections, but the trailing suffix identifies a different IGBT stage, current rating, and brake-chopper configuration. The 0LA3 is not a transparent, drop-in replacement for a 0LA1: the drive parameters P1100–P1103 must be updated, and the controller data must be recalculated in SimoCom U. The motor cable (U, V, W, PE) and the encoder cable are mechanically compatible.
What MD should I check first when 802D alarm 25030 appears after a power-section swap?
Check MD 36200 $MA_AX_VELO_LIMIT against MD 32000 $MA_MAX_AX_VELO. MD 36200 must equal 1.05–1.10 × MD 32000. If the ratio is outside that range, restore it before raising the limit. Then verify the encoder polarity via MD 32110 $MA_ENC_FEEDBACK_POL and the actual velocity sign in the axis-service screen.
Can alarm 25030 be caused by the gearbox rather than the drive?
Yes. A 3-stage spindle gearbox that is left in the wrong stage (typically the high stage while the controller commands the low stage) multiplies the actual velocity at the chuck by the gear ratio, which will exceed MD 36200 within milliseconds. Verify the gear-stage position switch and the actuator state before assuming a drive-side fault.
Where can I find the official alarm description for 802D alarm 25030?
Alarm 25030 is documented in the Sinumerik 802D base software / diagnostics guide, available on the Siemens Industry Online Support portal at support.industry.siemens.com. The same document lists the standard remedies (setpoint cable, position-control direction, MD 32110, and MD 36200) that form the entry point of the diagnostic procedure.
Is it safe to clear alarm 25030 by writing MD 32110 to a different sign?
Yes, if the original sign was incorrect. MD 32110 $MA_ENC_FEEDBACK_POL accepts -1, 0, or 1. Always confirm the change by commanding a small M03 S100 and watching the actual velocity sign in the axis-service screen before applying the new value to a production move.