Resolving F60007 Line Overvoltage Fault on Siemens 6RA80 DCM

1. Fault Overview: F60007 on SINAMICS DCM 6RA80

The SINAMICS DCM (catalog designation 6RA80) is a fully-digital, armature-controlled DC drive that monitors the three-phase line supply feeding its armature converter and the single-phase auxiliary supply feeding its field converter. Fault F60007 is raised by the drive's line monitoring function when the measured line voltage exceeds the configured overvoltage threshold for longer than the configured delay time.

Unlike transient DC-link overvoltages (which are reported separately as F60001, F60002, F60003, or F60004 depending on the converter stage), F60007 indicates a sustained AC line-side excursion. The fault is latching by default and stops the drive according to the configured OFF response.

Reference: SINAMICS DCM 6RA80 List Manual and SINAMICS DCM Operating Instructions (Compact Operating Instructions for 6RA80).

2. Triggering Logic and Timing

The line-monitoring block inside the SINAMICS DCM firmware continuously samples the armature supply (terminals U1, V1, W1) and the field supply (terminals 3U1, 3W1). The sampled RMS values are compared against two configurable references:

• The rated line voltage configured in p50078[0] (armature) and p50078[1] (field).
• The percentage overvoltage threshold configured in p50352 (line overvoltage threshold, expressed as a percentage of the rated value).

A trip is generated when the measured line voltage remains above the threshold for a continuous period exceeding p50362 (line monitoring overvoltage delay time).

The trigger chain can be represented as the following timing diagram:

Figure 1 — Timing of F60007: a sustained overvoltage above the p50352 threshold for longer than p50362 produces the trip event.

3. Diagnostic Parameter Reference

When F60007 trips, the drive writes diagnostic information into a small set of parameters. Reading these values immediately after the trip is the fastest path to root cause.

Reference: SINAMICS DCM Parameter List (6RA80), section "Line monitoring".

4. Reading r0949 and r50047 Correctly

For the case documented in the field where r0949 = 0 and r50047[1] = 0, the drive is reporting overvoltage in armature phase UV with a generic fault classification. The reading r50047[2] should be recorded to quantify how far the voltage exceeded the rating. If r50047[2] shows a very small percentage but the drive still trips, the issue is rarely a true utility-side excursion — the most common causes are listed in §6.

5. Configuration Parameter Reference

5.1 p50078[0] / p50078[1] — Rated supply voltage

Both indices are read-only by design. They are written automatically from the drive's internal commissioning profile during first-time commissioning or when the rated nameplate data is downloaded. If the displayed value (for example 400 V) does not match the actual transformer secondary, the auxiliary transformer ratio or the voltage-sensing tap must be rechecked; the parameter itself cannot be typed in.

5.2 p50352 — Line overvoltage threshold

The default value is 20 %, meaning the drive tolerates up to 480 V on a 400 V rated supply before the overvoltage comparator activates. Common adjustments:

• Reduce to 10 % for sites with documented poor line regulation.
• Increase to 25 – 30 % only when the upstream transformer is known to charge to a high no-load voltage (typical for lightly-loaded transformers on weak grids).

5.3 p50362 — Line overvoltage delay time

Factory default is 0 ms (instantaneous trip). Many sites raise this to 200 – 1000 ms to ride through capacitor-bank switching and motor starting transients on shared feeders. The Siemens recommendation in field practice is not to exceed 2000 ms because the drive must protect its thyristor bridge from sustained overvoltage that will push the DC-link above its rated ceiling.

5.4 p50086 — Auto-restart

Setting p50086 > 0 enables the drive to attempt an automatic restart after F60007. Each attempt consumes one count; the counter resets when the fault is acknowledged manually or after a configurable dwell time.

6. Root-Cause Matrix

7. Field-Proven Case: False Overvoltage from Sensing Board

A common site failure mode is the voltage-sensing board inside the CUD (Control Unit, DCM) drifting high. In one documented case, the drive reported 450 V incoming while an independent Fluke 87V measurement at the same instant showed only 235 V AC. The ratio was nearly 2:1, which is too high to be a calibration drift alone — it indicates a sensing-board failure that is roughly doubling the measured signal.

Field procedure used to confirm this failure:

1. Read r50047[2] immediately after trip.
2. Clamp a calibrated true-RMS DMM onto the same phases feeding the drive.
3. Trigger the drive into run and capture both readings simultaneously on a two-channel oscilloscope or a datalogger such as the IBA daq system.
4. If the drive's internal measurement diverges from the external measurement by more than 5 %, replace the CUD. Do not attempt to recalibrate — the sensing resistors and op-amps are laser-trimmed and not field-adjustable.

As an interim diagnostic (not a permanent fix), setting p50362 = 250 ms can mask intermittent sensing-board glitches. This must not be left in place on a permanent basis because it reduces the protection margin against genuine overvoltages.

8. Step-by-Step Troubleshooting Procedure

8.1 Prerequisites

• Starter, Startdrive, or the AOP30 Advanced Operator Panel with access level 2 (Service) or higher.
• Calibrated true-RMS digital multimeter (Fluke 87V or equivalent, < 0.5 % accuracy).
• Insulated torque screwdriver for terminal blocks.
• Access to the drive commissioning sheet with p50078 values recorded.

8.2 Procedure

1. Capture diagnostics before acknowledgement. Read r0949, r50047[1], and r50047[2]. Note the index that tripped and the percentage deviation.
2. Verify external line voltage. Measure line-to-line at the drive's input terminals with the DMM in true-RMS AC mode. Log at least 10 minutes of data.
3. Compare to p50078 reference. If measured value > 1.05 × p50078 for > 80 % of the log window, the line is genuinely high — investigate utility supply.
4. Compare drive internal reading to external. Use r50047[2] and the DMM. A divergence > 5 % indicates a sensing issue.
5. Inspect sense wiring. Check torque on terminal X1 / X2 (or the equivalent terminal per the wiring diagram in the operating instructions). Reference: SINAMICS DCM 6RA80 Operating Instructions, chapter "Electrical installation".
6. Adjust thresholds only if measurements are nominal. If external line is within tolerance but the drive still trips, raise p50362 in 100 ms steps or p50352 in 5 % steps. Document every change.
7. Temporarily enable auto-restart for diagnosis. Set p50086 = 2 and observe whether the drive restarts without intervention. This indicates the trip is transient.
8. Replace CUD if sensing board is faulty. Replace the unit, repeat the verification procedure, and record new baseline readings.

9. Verification Checklist

After every intervention, run the following verification block and record the results on the maintenance sheet.

• Line voltage under load: r50047[2] = 0 % within rated tolerance band of p50078.
• Trip event: F60007 does not reappear for at least 72 hours under normal duty cycle.
• Thermal headroom: Heatsink temperature stable at < 80 % of rated maximum.
• Auto-restart counter: r50086 reports zero unsuccessful retries during the verification window.
• Operator panel: No pending or historical faults other than those cleared for cause.

10. Adjacent Faults to Differentiate

Several other F6xxxx faults share overlapping indicators. Cross-check before concluding F60007 is the root cause.

Reference: SINAMICS DCM List Manual, chapter "Faults and warnings".

11. Preventive Maintenance

• Annual: Verify p50078[0] / p50078[1] match the as-built transformer secondary.
• Annual: Trend r50047[2] for at least one production cycle and archive.
• Quarterly: Inspect terminal torque on line-voltage sense wires; vibration and thermal cycling can loosen them.
• Five-year: Replace CUD backup capacitor and re-verify measurement accuracy with calibrated source.
• On every utility event: If a brown-out or surge was reported, run the verification checklist in §9 before returning the line to production.