Siemens 6RA8075 DCM Drive F60300 F60050 Tuning Troubleshooting

1. Problem Statement

A SINAMICS DCM converter type 6RA8075-6FV62-0AA0 (four-quadrant, 75 A continuous armature, 415 V class, firmware V6.2) drives the spindle of a surface-grinding machine. The original 11 kW DC motor (220 V armature, 62 A, 300–1200 RPM, 0.5–3.0 A field) has been removed and a 20 kW DC motor (400 V armature, 59 A, 600–1800 RPM, 1.0–3.5 A field) is being installed on the same converter. The pulse encoder on the motor shaft is unchanged.

After entering the new motor nameplate data, the converter trips with the following sequence of events:

• F60300 — Infeed fault, raised when the armature voltage climbs past roughly 250 V DC during ramp-up.
• F60050 — Optimization aborted, with the optimizer status word r949 = 0 on the runs P50051 = 24 (speed controller), P50051 = 26 (field-weakening speed controller) and P50051 = 27 (additional optimization).
• Field-weakening optimization terminates with the internal status 409 — the speed collapsed more than 12.5 % below setpoint during the auto-ramp.
• Mechanical vibration is observed on the motor shaft as soon as the drive is enabled, even before the F60300 trip.

This document captures the parameter migration, the fault-tree analysis, and the no-load commissioning sequence required to clear the F60300 / F60050 conditions and complete the field-weakening optimization on the 20 kW machine.

2. System Configuration – Original vs Replacement Motor

Two important electrical changes accompany the mechanical swap:

1. The armature voltage requirement rises from 220 V to 400 V DC — a 1.82× increase. The drive must be supplied from a three-phase source that can deliver at least 400 / 1.35 ≈ 296 V at the line input. A 415 V AC three-phase line produces a theoretical DC link of 1.35 × 415 ≈ 560 V, which is more than enough. A 220 V AC single-phase source would only deliver 1.35 × 220 ≈ 297 V DC, which is below the 400 V command and explains the F60300 trip near 250 V.
2. The base speed shifts from 300 to 600 RPM, so the field-weakening range becomes 600 → 1800 RPM (3:1) instead of 300 → 1200 RPM (4:1). The field-current vs. back-EMF map stored from the 11 kW motor no longer matches the new machine, which is the root cause of the observed shaft vibration.

3. Parameter Migration Matrix

4. Fault Code Reference

4.1 F60300 — Infeed fault

The SINAMICS DCM List Manual classifies F60300 as a line-side / DC-link fault in the Controlled Feed unit. Typical causes on the 6RA80 platform:

• Line voltage below the configured P50078[1] tolerance window.
• Missing line phase (single-phase operation on a three-phase supply).
• Pre-charge contactor not closing or pre-charge resistor damaged.
• Line frequency outside the 47–63 Hz window.
• DC-link voltage exceeding the hardware ceiling (over-voltage trip).

The trip occurring just above 250 V DC is a strong indicator that the actual line voltage is significantly lower than the 415 V the parameter now claims, or that the drive is being fed from a single-phase 220 V source where the theoretical maximum DC link is 220 × √2 ≈ 311 V peak. The hardware clamps the operating envelope to about 85 % of that peak, placing the trip just where it is observed.

4.2 F60050 — Optimization aborted

Per the same List Manual, F60050 indicates that the optimization routine selected by P50051 terminated due to an internal cause. The status word r949 holds the abort reason. r949 = 0 in this case means the optimization did not reach a measurable milestone — typically because the line or field converter had already been taken offline by another fault, or because the converter could not be enabled when the routine requested the ON / OFF1 command.

4.3 Internal status 409 — Field-weakening abort

The internal status 409 returned during the field-weakening optimization (P50051 = 25 / 26) is the "speed-deviation" abort. The optimizer ramps the motor above base speed expecting back-EMF and speed to track the setpoint; if the actual speed drops more than 12.5 % below the setpoint the routine aborts to protect the un-characterized machine. Reading r50047[1] (speed setpoint) and r50047[2] (speed actual) immediately before the abort reveals whether the field is too weak to develop torque, or whether the encoder is losing pulses under speed.

5. Root Cause Analysis

Three interacting root causes are present in this drive:

1. DC-link headroom. The drive trips F60300 at ≈250 V because the configured 415 V AC is not the supply actually wired to the converter. The drive calculates a DC-link ceiling from P50078[1] and a hardware ceiling from the actual rectified line; when the actual line is 220 V the ceiling is 297 V, but pre-charge, line monitor, and DC-link thresholds clip operation near 250–260 V before the controller can reach the 400 V command.
2. Optimization not permitted to run. Because the converter has a pending F60300, it cannot accept the internal ON command that P50051 = 24 / 26 / 27 use. The routines abort with F60050 and r949 = 0.
3. Field characteristic not adapted. Even if the line supply is correct, the new motor has a different field-flux vs. current slope and a different base-speed EMF. With a stale field map the controller over-fluxes at low speed (causing the observed vibration) and under-fluxes above base speed (causing the speed-collapse abort 409).

6. Pre-Optimization Validation Checklist

1. Measure the line-to-line voltage at the drive input terminals with a true-RMS meter. Confirm whether it is 380 / 400 / 415 V AC three-phase or 220 V AC single-phase.
2. Verify the three line fuses and the pre-charge circuit. The pre-charge contactor must close within 3 s of power-on; the DC-link voltage must rise to at least 1.35 × V_LL × 0.9 within 5 s of mains-on.
3. Measure the field supply voltage at the drive's field terminals (X111) and confirm it matches P50078[2] = 220 V.
4. Confirm encoder wiring and shield grounding. Check r0061 (speed actual) follows a hand-wheel turn of the motor shaft smoothly with no glitching or negative readings on direction change.
5. Clear the F60300 fault with the OFF1 / ACK sequence and acknowledge all other faults before starting optimization.
6. Decouple the motor from the grinding spindle — field-weakening optimization must run uncoupled and unloaded. Any residual mechanical load produces the 409 abort.
7. Save the parameter set with p0977 = 1 (or via STARTER / Startdrive) before the optimization run so the previous good set can be restored if needed.

7. Step-by-Step Resolution Procedure

Follow this sequence; do not skip ahead. Each step is verified by a measured value before moving on.

Step 1 — Correct the line voltage parameter

Set P50078[1] to the actual measured line-to-line voltage. If the supply is 220 V single-phase, the 6RA8075 cannot develop 400 V armature — the 20 kW motor cannot be used on this drive at its nameplate voltage, and either a different drive (e.g. 6RA8085-6FV62 at 125 A in a 480 V class cabinet) or a step-up transformer is required. If the supply is 415 V three-phase, leave P50078[1] = 415 and re-tighten the line-side terminations.

Step 2 — Factory reset and re-enter motor data

Perform a factory reset (P0970 = 1) and reload the parameter set for the 20 kW motor:

P50100   = 59      ; rated armature current (A)
P50101   = 400     ; rated armature voltage (V DC)
P50102   = 3.5     ; rated field current (A)
P50103   = 1.0     ; minimum field current (A)
P50104   = 600     ; base speed (RPM)
P2000    = 1800    ; reference speed (RPM)
P50078[1] = 415    ; line voltage (V AC, 3-phase)
P50078[2] = 220    ; field voltage (V AC)

Step 3 — Verify DC link with no ON command

Power the drive, observe r0080 (DC-link voltage). It should rise to 1.35 × 415 ≈ 560 V with the line at 415 V. A value below 500 V indicates a line-side problem (fuse, contactor, or undersized transformer).

Step 4 — Run field-current optimization (P50051 = 23)

Issue ON, then set P50051 = 23. The drive injects a field-current ramp from P50103 to P50102 and records the magnetization characteristic. The run takes approximately 30 s. This step has already returned "OK" in the reported session.

Step 5 — Run speed-controller optimization (P50051 = 24)

Keep the motor decoupled and unloaded. Set P50051 = 24 and follow the prompts. The drive injects a small speed step and identifies P50225 / P50226 (gain) and P50227 / P50228 (reset time) of the speed controller. This step requires F60300 to be cleared; if it aborts with r949 = 0, return to Steps 1 and 3.

Step 6 — Run field-weakening characteristic (P50051 = 25)

The drive measures the back-EMF constant at base speed and builds the field-weakening map. Already "OK" in the reported session.

Step 7 — Run field-weakening speed controller (P50051 = 26)

Identifies the field-current controller for the weakening range. This is the step that aborts with status 409 if the field is too weak to maintain the commanded speed. The abort is caused by either (a) the motor is still mechanically loaded, (b) the field-supply voltage P50078[2] is wrong, or (c) the minimum field current P50103 = 1.0 A is set too high and prevents the speed from climbing. Lower P50103 to 0.4 A temporarily for the optimization run, then restore the motor's specified value once the run is complete.

Step 8 — Run additional optimization (P50051 = 27)

Finalizes torque limits, friction compensation, and the auto-reversing test. Aborts with r949 = 0 if any of the previous steps were not successful; clear the F60050 first and confirm Steps 5 and 7 completed before re-running this one.

Step 9 — Save and back up

Set P0977 = 1 to write the parameters to the non-volatile memory, then save the project to STARTER / Startdrive and export the parameter file (.dvc) to a service laptop.

8. Field-Weakening Optimization Notes

The field-weakening range of a DC motor is defined by the ratio of maximum speed to base speed:

n_max / n_base = 1800 / 600 = 3.0

The required minimum field current is approximately:

I_f_min ≈ I_f_rated × (n_base / n_max) ≈ 3.5 × (600 / 1800) ≈ 1.17 A

The configured P50103 = 1.0 A sits at the lower edge of this physical limit — a small error in P50104 or in the line voltage can pull the optimizer into a region where the motor cannot develop the required torque above base speed, which is exactly the symptom of abort code 409. If the optimization is still marginal, raise P50104 by 5 % (to 630 RPM) and reduce P2000 to 1750 RPM, complete the optimization, then restore the production setpoints.

The 409 abort threshold is implemented in the firmware as a 12.5 % deviation between r50047[1] and r50047[2] sustained for more than 2 s during the auto-ramp. To prove the source, set the drive to a manual speed of 1500 RPM in field weakening, watch the two diagnostic values, and decide whether the collapse is torque-limited (field too weak) or feedback-limited (encoder losing pulses).

9. Verification Procedure

1. Run the motor unloaded from 0 to 1800 RPM in a 1 s ramp. Monitor r0061 (speed actual), r0027 (armature current), and r50047[1/2] (speed setpoint vs. actual). The deviation between setpoint and actual should stay under 1 % at steady state and under 5 % during ramp.
2. Apply a step load of 50 % rated torque. Speed dip should be under 6 % and recovery within 400 ms with the new P50225 / P50226 values.
3. Run from 600 → 1800 RPM in field-weakening with the motor unloaded. The field current should taper from 3.5 A to ~1.2 A, the armature voltage should hold at 400 V DC ± 5 %, and the speed controller should not saturate.
4. Re-couple to the grinding spindle and run a no-cut spindle test at top speed for 30 min. Monitor drive heatsink temperature (r0037); it should stay below 80 °C in a 40 °C ambient.
5. Capture a STARTER trace of the optimization run on P50051 = 26 and archive it with the commissioning report. This is the evidence to clear the F60050 / 409 condition permanently.

10. Diagnostic Flow

11. Related Parameters and Diagnostic Variables

12. Frequently Asked Questions