SINUMERIK 810D Alarm 300501: Spindle Drive Measuring Circuit

1. Problem Summary: Triple Spindle Drive Alarm on SINUMERIK 810D

When the operator presses the spindle start key on a SINUMERIK 810D control, three related alarms may appear simultaneously on the HMI:

1. Alarm 300501 – Axis SP1 driver 3 error in measuring circuit of absolute current
2. E-R-Module General Alarm – Encoder / Resolver module fault
3. Axis SP1 drive fault – Follow-up drive stop

All three alarms share a single root cause chain: alarm 300501 is the originating fault, and the two remaining alarms are cascaded reactions from the drive monitoring and the encoder/resolver evaluation path. Because the spindle cannot be enabled, the machine is fully down until the fault is cleared and the drive is acknowledged.

2. Affected Hardware: 810D Architecture and the CCU Box

The SINUMERIK 810D differs from the larger 840D in that drives 1, 2, and 3 are physically integrated into the CCU box (Compact Control Unit). There is no separate SIMODRIVE 611D power module rack to swap – the spindle drive regulator (typically a 6SN1123 or 6SN1118 series) lives on a plug-in module inside the CCU chassis, along with the NCU, PLC-CPU, and the resolver/encoder interface.

The line-side power is delivered by the LT module (Link / Line Transformer module) that sits to the right of the CCU in the cabinet. The LT module feeds the DC link (≈600/700 V DC) that all three integrated drives share. Motor power cables for the spindle are then routed from the CCU drive output (or, on some configurations, from a terminal block on the LT module).

3. Root Cause Analysis: Why 300501 Triggers

Alarm 300501 "Driver 3 error in measuring circuit of absolute current" is generated by the spindle drive firmware (SIMODRIVE 611D / 6SN1123) when the analog absolute current sensing path returns a value that is either out of range, stuck at zero, or has a checksum / plausibility error against the DSP reference. The "absolute current" term refers to the unregulated, time-critical phase-current measurement (typically via Hall-effect transducers or current shunts with isolated amplifier stages) – not the speed/position feedback.

On the 810D this error has five field-proven root causes, in order of probability:

1. Defective LT module producing a noisy, drooping, or unbalanced DC link. The drive's current measurement offsets drift and the plausibility check fails.
2. Defective drive module inside the CCU – the IGBT power stage or the current-sense board has failed. Most common on machines that are 8+ years old or have suffered a mains transient / short circuit at the motor.
3. Resolver / encoder cable damage on the 1PH motor. The "E-R Module General Alarm" appearing simultaneously is the giveaway that the feedback path is also suspect.
4. Resolver head failure on the motor (rotating transformer, bearings, or sense windings). A previously repaired 1PH7133 with a new encoder can still fail inside the resolver if the bearings were not changed.
5. Open contactor between LT module and motor. The drive sees an inductive load with no return path, and the absolute current monitor trips on the asymmetric first cycle.

4. 1PH7133-2NG32-0CK0 Spindle Motor Reference Data

The reported machine is equipped with a Siemens 1PH7133-2NG32-0CK0 induction spindle motor from the 1PH7 series. The "-2" winding and the "-0CK0" option code specify the electrical and mechanical configuration. For sizing the replacement LT module or verifying the existing one, the following data is mandatory:

The 1PH7 family uses a hollow-shaft resolver that is mechanically and electrically sensitive to vibration and bearing wear. A motor that has just had a "new encoder and bearing" replacement is still a candidate for resolver failure if the encoder manufacturer reused the old resolver stator or if the air gap was not set correctly.

5. Diagnostic Procedure: Field-Proven Step Sequence

1. Capture all active alarms and their numbers. Open the alarm history (HMI Advanced: Alarm → Selection → History) and write down every alarm code. 300501 plus its follow-ups must be confirmed before any swap decision is made. A single missing alarm number means a hidden cascade.
2. Open the control cabinet and photograph the hardware. Document the CCU box label, the LT module type number (e.g. 6SN1145, 6SN1146), the X1/X2 wiring, and the motor power cable landing point. This is required for the Siemens service report if escalation is needed.
3. Verify the DC link voltage at the LT module terminals with a calibrated multimeter (DC, 1000 V range). With mains ON and drives disabled, the DC link should sit at 1.35 × V_LL (e.g. 540 V DC nominal for 400 V mains). A reading below 480 V or above 780 V indicates LT module degradation or capacitor failure.
4. Check the motor power cable continuity end-to-end (U, V, W, PE) with the cabinet de-energized and locked-out. An intermittent U-phase open is a common cause of single-cycle absolute current trips.
5. Inspect the resolver cable for kinks, chafing, and shield continuity. A resolver cable run that is bundled with the motor power cable is a common installer error and injects common-mode noise that produces E-R module alarms. The shield must be grounded at the CCU end only, with 360° contact at the connector backshell.
6. Measure resolver impedance at the CCU connector (resolver pins: sine, cosine, excitation, return). Typical values: excitation winding 30–60 Ω, sine/cosine windings 100–200 Ω, all windings to chassis > 10 MΩ. Any short to chassis or between windings confirms a motor-side fault.
7. Verify the contactor (if any) between LT module and motor is fully closing under load. A contactor with pitted main contacts will pass the pre-charge current but drop out under motor inrush, producing the alarm pattern described.
8. Cross-check on the HMI: enter Start-up → Drive → Service → Drive status and read the diagnostic double-words for drive 3. A persistent current-sense error word in the diagnostic screen confirms a hardware, not configuration, fault.

6. CCU Replacement Procedure

If diagnostic steps 1–8 do not isolate a clear external cause, the next logical move is to swap the CCU box. The 810D CCU is the most cost-effective swap candidate because it contains the three integrated drives, the NCU, and the resolver interface – replacing it addresses three of the five root causes in a single action.

6.1 Prerequisites

• Identical or compatible CCU part number (e.g. 6FC5410-0AY03-0AA0 or equivalent for the 810D CCU3 family). Verify the hardware release against the machine's commissioning logbook.
• NC archive on a PC card or USB (see section 7).
• PLC archive (S7 program, symbol table, FB/FC sources).
• Drive data backup via the Start-up → Backup menu.
• Drive configuration archive (motor data, encoder data, current limits).
• ESD-safe workspace, wrist strap, and original packaging for the removed CCU.

6.2 Replacement Sequence

1. Back up the NC, PLC, and drive data (mandatory, see section 7).
2. Power down the machine at the main disconnect. Wait at least 5 minutes for the DC link to discharge (verify with a voltmeter – the LT module bleeder LED must extinguish).
3. Disconnect the X1, X2, X3, X4, X5 connectors from the CCU. Label every cable. Photograph the rear of the unit.
4. Remove the CCU from its mounting plate (typically four M6 screws).
5. Install the replacement CCU in the same orientation. Torque the mounting screws to the OEM specification (typically 4–6 Nm).
6. Reconnect all connectors in the original order. Verify that resolver, encoder, and motor power cables are not transposed.
7. Power up the cabinet. Observe the CCU 7-segment status display – it must sequence to "6" (drive ready) within ~30 s.
8. Restore the NC, PLC, and drive archives (see section 7).
9. Run a spindle test in jog mode at low RPM. Verify resolver feedback, current draw (should be < 50 % of 42.99 A at no load), and absence of alarm 300501.

7. NC / PLC / Drive Data Backup and Restore

Before any CCU intervention, the following archives must be created and verified for read-back integrity:

Restore order on the replacement CCU: Drive → PLC → NC → Compensation. The drive data must be restored first because the NC initialization reads drive parameters to confirm axis enable logic. A common commissioning error is restoring NC data over the network and missing the drive archive, which leaves the spindle in a non-enabled state with cascading alarms.

8. LT Module Diagnosis and Replacement

If the CCU swap does not clear the alarms, the LT module is the next suspect. Diagnostic signs of a failing LT module on a SINUMERIK 810D:

• DC link LED is dim or flickering instead of steady.
• Pre-charge contactor chatters at power-up.
• Internal 24 V auxiliary output is below 22 V under load.
• Phase monitor relay is in fault state (check the X111 terminals).

Replacement procedure for the LT module:

1. Power down, lock out, verify DC link discharged.
2. Remove the bus bar connections to the CCU drive section.
3. Remove the 24 V control cable and any fan cable.
4. Swap the LT module, observing orientation. The bus bars are polarity-critical (DC+ and DC-).
5. Power up and verify the DC link comes up to nominal within the pre-charge window (typically 2–3 s).
6. Enable the spindle and monitor current-sense diagnostics for one full warm-up cycle.

9. Verification Tests After Repair

After a CCU or LT module swap, perform the following verification sequence to confirm full recovery:

1. Alarm clear test: power up, press CNC Reset, confirm alarm 300501 and the two follow-up alarms clear without re-appearing for at least 5 minutes.
2. Spindle jog test: jog the spindle in both directions at 50 RPM, 500 RPM, and 3000 RPM. Monitor phase current on the HMI service screen. Each phase current should be balanced within ±5 %.
3. Orient / C-axis test: command an orient cycle (M19). Verify the spindle stops within the configured orient window (typically ±1°).
4. Encoder feedback test: enter Start-up → Drive → Service → Actual values. The actual speed must follow the setpoint with < 2 % steady-state error at 1000 RPM.
5. Load test: cut a known reference part at programmed spindle speed. Monitor alarm history for 24 hours of production.
6. DC link stability test: log the DC link voltage over a 30-minute production cycle. Variation must be < ±2 %.

10. Related Alarms and Cross-Reference

11. Safety and ESD Procedures

Working inside the 810D cabinet exposes the technician to:

• DC link voltages up to 700 V DC on the bus bars and LT module terminals. These remain present for several minutes after main disconnect. Always verify zero energy with a CAT III 1000 V meter before contact.
• ESD-sensitive components on the CCU drive module and resolver interface boards. Use a wrist strap bonded to the cabinet ground point.
• Stored charge in motor and cable capacitance. Wait 5 minutes minimum after power-down; do not rely solely on LED indicators.
• Mechanical energy in the spindle (rotor can free-wheel for several minutes after power-off if no brake is configured).

Lockout/tagout the main disconnect and the 24 V control circuit. Verify zero voltage at three test points: LT module DC bus, CCU drive output terminals, and motor junction box.

12. Field-Engineering Decision Matrix

13. Frequently Asked Questions