Siemens Masterdrive MC Plus F006 Overvoltage Fault Root Cause

Problem Overview

The Siemens MASTERDRIVES MC PLUS (6SE70/6SE71 series with Motion Control firmware, e.g., version 1.6) reports fault F006 (overvoltage) while the actual DC link voltage at the bus capacitors is normal (~560 V DC for a 400 V class unit). The drive keypad, r006 parameter, and SIMOVIS/DriveMonitor may report an inflated value such as 805 V DC, and the indication persists even after the DC supply is disconnected. The drive typically trips to OFF2 or OFF3, and the motor coasts to a stop. In some installations a companion fault F008 (DC link undervoltage) appears on the same or on parallel drives after a delay of several hours of operation.

F006 on MASTERDRIVES is a latching, hardware-monitored fault sourced in the DC link measurement chain. It cannot be acknowledged until the internal monitoring logic no longer flags an overvoltage condition. The root cause is almost always one of the following, ranked by frequency observed in field service:

1. DC link voltage measurement circuit drift or contamination (false F006).
2. Real overvoltage caused by regenerative energy with inadequate dissipation path.
1. Braking chopper not present, disabled, undersized, or set to a high activation threshold.
2. Ramp-down time too short for the load inertia / kinetic energy.
3. Missing or failed braking resistor.
3. Encoder feedback loss interpreted as motor stall, forcing the drive to assume regenerative behavior.
4. Udc-max controller (P515) disabled while regen transients are present.
5. DC link pre-charge or measurement PCB failure on the small-form-factor units with two boards.

Affected Equipment and Configuration

MASTERDRIVES MC PLUS is the motion-control variant of the SIMOVERT MASTERDRIVES family, distinguished from the standard VC PLUS by the integrated positioning, synchronization, and free-function-block firmware. The 6SE70xx series covers frame sizes 1 (smallest) through 6 (largest), with the F006 measurement-circuit pathology most often reported on the compact, two-PCB chassis (frame size A/B, types 6SE7016/6SE7018 and similar).

Fault Code and DC Link Behavior

F006 is defined in the MASTERDRIVES fault list as DC link overvoltage. F008 is its undervoltage counterpart. Both faults can be:

• Real: The DC link voltage actually exceeds (F006) or falls below (F008) the hardware threshold.
• Indicated: The hardware is sound but the analog measurement chain reports a wrong value.

Real vs. indicated is the first diagnostic branch. The fastest way to split the two is to compare the keypad/r006 reading to a direct, isolated measurement at terminals C (+) and D (-) on the drive. The disagreement reported in the field case (560 V measured vs. 805 V indicated) places the fault firmly in the indicated branch on first pass; the second pass must then confirm whether the drive's braking system is actually capable of holding the link below the trip envelope under worst-case regen.

Key Parameters and Test Points

Use the following parameter set to map the drive before any invasive work. Parameters are accessed from the PMU keypad, the OP1S operator panel, or SIMOVIS / DriveMonitor over the serial USS / PROFIBUS link.

Root Cause 1: Encoder-Induced False Regeneration

A slipped, contaminated, or open encoder can present itself to the speed controller as "motor not following the setpoint." The MC PLUS firmware reacts in two ways:

1. The current controller pushes the inverter toward the demanded speed, and if the rotor is not rotating at the rate the encoder reports, the drive interprets the slip as motor regenerating into the link.
2. The DC link rises rapidly, and if the chopper cannot sink the energy, F006 trips.

This root cause is identified by:

• Fault occurring on the inverter side of a DC-bus-coupled system, with no faults on the line-side regenerative supply unit.
• Trip happens during steady-state operation or even after the line contactor is opened, because the rotor's residual kinetic energy is dumped into the link through the inverter's anti-parallel diodes feeding the capacitors.
• Encoder-related warning bits appearing in r047 (speed controller status) or r158 (encoder diagnostic) before the trip.

Resolution:

1. Replace the encoder with a known-good unit. Verify coupling concentricity with a dial indicator (typical runout < 0.05 mm).
2. Re-verify encoder wiring shield grounding at the drive end only, with the shield drain wire landed on the SUB-D backshell.
3. Set the encoder gain in P150 (speed-actual source) and confirm track assignment in P151 for the MC PLUS (TTL/HTL, A/B track, marker).
4. Capture a speed-actual trace in DriveMonitor (trace function 030 or higher) and confirm no glitches correlate with the F006 timestamp.

Root Cause 2: Braking Chopper Mis-Selection or Disabled

The chopper (braking IGBT module + external braking resistor) is the primary energy sink during deceleration. A common field defect is the chopper configured with a turn-on threshold set too high (e.g., 760 V when the hardware trips at 760 V), meaning the chopper never engages in time. Re-size the chopper to:

Selection of resistor R_br:

• Step 1: Decide required peak power P_peak from the table.
• Step 2: Set R_br = V_chopper,on² / P_peak. Example: at 670 V on and 10 kW peak, R_br = 670² / 10000 = 44.9 Ω.
• Step 3: Verify continuous rating P_avg against the resistor's continuous power.
• Step 4: Verify the chopper module's peak current: I_peak = V_dc / R_br must be below the IGBT module rating (typical MASTERDRIVES chopper is rated 100-300 A peak depending on frame).

Root Cause 3: Ramp-Down Time Too Short

The MASTERDRIVES MC PLUS ramp generator uses P462-P469 (4 ramp pairs) plus the MC-specific profiles. If the mechanical decel rate is faster than the ramp generator's output, the speed controller commands negative torque and pushes the motor into regen. The simple corrective is to lengthen the decel ramp, then re-size the chopper around the new ramp:

• P464 (Ramp-Down Time 1) is the most common target. Increase by 2× to 3× and re-test.
• If the application cannot tolerate a long decel, use P515 Udc-max controller to auto-extend the ramp only when regen threatens to overvoltage the link.

Root Cause 4: Udc-Max Controller (P515) Disabled

P515 controls the Vdc-max regulator, an inner loop that increases the torque-producing current limit when V_dc approaches the chopper turn-on level, effectively giving the drive authority to lengthen the ramp at the precise moment the link would overvoltage. In MASTERDRIVES this is normally OFF.

Setting P515 = 1 or 2 is a standard mitigation for installations where the chopper is undersized or absent but the load is constant. The drive will automatically stretch the ramp only as much as required to keep the link below the trip envelope, preserving the original fast decel when no regen is present. Always re-test the F006 trip envelope after enabling P515: if the V_dc at the link climbs above 700 V with P515 active, the controller is not configured correctly for the firmware build (P515 was redefined in 1.6x and again in 2.x; verify with the firmware-specific manual).

Root Cause 5: DC Measurement Circuit Failure (Small-Frame Units)

On the small MASTERDRIVES MC PLUS units (frame A/B, 2-PCB construction), the DC link measurement amplifier is on the power PCB adjacent to the chopper IGBT. Heat, dust, and contamination induce drift in the divider network, producing a falsely high r006. Indications:

• Keypad shows ~700-820 V at power-up with the drive in standby, no mains.
• r006 reading is higher than the direct measurement at terminals C/D by > 5%.
• F006 trips on every cold start regardless of motion profile.

Resolution path:

1. With the drive de-energized and discharged (verify with meter at C/D), remove the front cover and inspect the power PCB for dust accumulation, especially on the HV divider and around the chopper IGBT heatsink.
2. Clean with ESD-safe vacuum and a soft, dry antistatic brush. Do not use compressed air on the populated PCB; this can drive conductive dust into the isolation gaps.
3. Reassemble, apply control voltage only, and read r006 on the keypad. A clean PCB will typically bring the reading within ±2% of a direct measurement at C/D.
4. If the reading remains inflated after cleaning, replace the measurement-amplifier section of the power PCB. The two-PCB units are not field-repairable at component level for this fault; the PCB assembly is the line-replaceable unit.

F008 (Undervoltage) Companion Fault

F008 on the same drive population usually indicates a different problem on the same measurement chain. When both F006 and F008 appear on the same site (different drives, same DC bus), the cause is often:

• Supply-side problem: brownouts, undersized line impedance, weak source.
• Pre-charge resistor / contactor wear: a high-resistance pre-charge will let V_dc fall during load steps, triggering F008 on deceleration-then-acceleration cycles.
• DC link capacitor end-of-life: ESR rises, and a loaded link collapses faster than the firmware can ride through.

For F008, measure the line voltage under load with a true-RMS meter and compare to r025 (line voltage parameter, if configured). A drop of more than 10% at peak load confirms a supply issue; otherwise, inspect the pre-charge circuit and bulk capacitors.

Step-by-Step Troubleshooting Procedure

1. Capture the fault memory. Read n001 through n016 before acknowledging. Record the r006 value at trip and the operating state (r047 speed controller, r156/r158 encoder diagnostic).
2. Measure V_dc at terminals C and D with a properly rated, isolated meter. Compare to r006 with the drive in standby and again under no-load steady state.
3. Branch decision:
   • If r006 matches the meter reading within ±2%, the measurement chain is OK and the F006 is a real overvoltage. Go to step 4.
   • If r006 disagrees with the meter, the measurement chain has failed. Go to step 6.
4. Real overvoltage path. Verify the chopper: read r029 during a controlled decel; verify the gate signal is present at the chopper IGBT with an isolated scope probe; verify the resistor with an ohmmeter (de-energized, discharged). If absent, configure or install a chopper. If present but disabled, lower P516 to 670 V and re-test. If correctly configured, enable P515 Udc-max controller and re-test.
5. Encoder path. Inspect the encoder and coupling. Capture a speed-actual trace. Replace the encoder if any track glitch is observed within 5 s of the F006 timestamp.
6. Indicated-overvoltage path. De-energize, discharge, open the unit. Inspect and clean the power PCB. Re-test. If still failing, replace the power PCB assembly or send to a Siemens-authorized repair center for component-level repair.
7. Re-test under worst-case load. Command a fast decel from rated speed to zero with full inertia. Capture r006 and r008 traces. The link should peak at no more than 720 V (chopper on) or ramp-clamped below the F006 trip point (P515 active).
8. Document and commission. Record final P515, P516, P517, P464 settings; record chopper size and resistor; record encoder replacement details. Update the maintenance log.

Verification and Commissioning

Preventive Maintenance Notes

• Inspect the power PCB for dust at every 12-month preventive maintenance visit. Sites with airborne contamination (paper, textile, cement) may need 6-month intervals.
• Verify the DC link capacitors' ESR at 24-month intervals; a 20% rise in ESR or a 10% drop in capacitance is the typical end-of-life indicator.
• Replace the encoder coupling set screw with a fresh, thread-locked fastener if the application has any vibration above 5 m/s² RMS.
• Keep firmware at the latest field-stable version for the frame. The MASTERDRIVES MC PLUS firmware family had a 1.6 → 2.1 → 2.3 → 3.1 progression with several F006-related corrections in the 2.x line; consult the release notes for the installed build before making parameter changes.