SIMOVERT Masterdrives F011 Overcurrent Fault at Startup: Comprehensive Diagnosis and Repair

Overview

The SIMOVERT Masterdrives family of vector-controlled drives remains in service across water and wastewater utilities, HVAC installations, process lines, and heavy industry where units were commissioned between the mid-1990s and 2005. Fault F011 — a motor I²t overload trip — appearing on the run-up ramp and frequently accompanied by a brief reverse-then-forward oscillation of the motor shaft, is one of the more common failure modes on drives that have been in continuous service for two decades. This article documents a field-proven diagnostic and repair workflow for a 6SE7233-6FS00-3AB0-Z drive fitted with a 6SE7090-0XX84-0AB0 CUVC control card installed in a drinking-water pump station since approximately 2000, but the same workflow applies to any SIMOVERT Masterdrives Compact or chassis unit exhibiting the same symptom set.

Drive and Component Identification

Confirm the exact part numbers before starting any work; the diagnostic approach differs slightly between firmware releases, frame sizes, and control-card variants.

The CUVC card is the brain of the drive. It hosts the 80C166 processor, non-volatile parameter memory, the encoder interface, and the analog and digital I/O. If the firmware version is older than 2.x of the 84 series, Siemens released several updates that addressed stability issues in the current controller — these are worth applying if the drive is on an early firmware. Reference the Siemens Industry Online Support portal for legacy Masterdrives documentation, including the Masterdrives Compendium and the parameter list for the specific firmware installed.

F011 Fault Code Definition

Fault F011 in SIMOVERT Masterdrives Compact and chassis units is the motor I²t overload trip. The drive continuously calculates the thermal model of the connected motor from the measured output current and the parameters P102 (motor rated current) and P108 (motor no-load current), with weighting defined by P114 (motor cooling method). When the calculated temperature exceeds the trip threshold, F011 is raised and the drive free-wheels to stop with the response defined by P805 (fault reaction, typically OFF2 / fast stop).

The actual root cause of the trip is almost always upstream of the thermal model — the drive is detecting sustained or pulsed overcurrent because of one of the conditions described in the root-cause section below, and the I²t integrator simply records the symptom. The motor oscillation (small reverse/forward steps before the trip) is a strong indicator that the current control loop is unstable, that a phase is being lost, or that a current sensor is reading incorrectly. Treat the F011 as the effect, not the cause.

Symptom Analysis — Why the Motor Jogs

The reported behaviour — the motor rotates roughly a quarter-turn in reverse, then snaps back in the forward direction, and finally trips on F011 within 1-2 seconds — narrows the root cause significantly. The following mechanical and electrical states can produce this exact signature:

• Phase-loss or asymmetric output: One phase firing late, weakly, or not at all. The motor develops a non-uniform rotating field, settles at a position defined by the remaining two phases, and twitches back when the next cycle starts.
• Current sensor (CT) reading zero or biased: The current controller reacts to perceived imbalance, produces an asymmetric output, and the I²t integrator trips on the over-corrected phase.
• Encoder feedback failure: If P100 is set to a vector mode that uses encoder feedback, a broken wire or dirty encoder produces immediate instability in the speed and current loops.
• Severe motor parameter mismatch: Wrong field orientation produces a torque reversal at every zero-crossing of the stator flux, manifested as a small back-and-forth motion.
• DC bus ripple: Excessive 100/120 Hz ripple on the DC bus couples into the current measurement and the current loop oscillates.

The fact that the original poster decoupled the pump is helpful — it rules out mechanical binding in the load — but does not rule out the motor itself. A failing bearing, an encoder mounted on a worn coupling, or a single-phased stator winding will produce the same symptom with the load removed.

Root Cause Analysis

Triage the unit in the order shown. Causes are listed in approximate statistical likelihood for a 20+ year-old drive exhibiting the quarter-turn oscillation symptom.

1. Current Sensor (CT) Open or Loose Connection

SIMOVERT Masterdrives Compact units use Hall-effect current transducers in each output phase (or, in some variants, CTs in the DC link). If one CT connector is loose, has a cold solder joint, or has a broken wire, the drive will see one phase current as zero or as a small offset. The current controller, reacting to the perceived imbalance, will drive the inverter output asymmetrically — producing the characteristic twitching rotation as the field attempts to stabilize. Within a few cycles, the calculated I²t exceeds the limit and F011 trips.

Inspection points:

• CT connectors at the power module — should be fully seated, locking clip engaged
• Wiring between CT and CUVC card (ribbon cable on some variants)
• CT mounting screws (loose CT = wrong reading)
• Shield grounding of signal leads
• Continuity of the CT supply voltage (typically ±15 V on the transducer body)

2. IGBT Module Degradation

After 20+ years of thermal cycling, the bond wires inside the IGBT modules can lift, producing increased Vce(sat) on individual phases. One weak phase will conduct less current, the other two will be driven harder to maintain torque, and the I²t calculation trips prematurely. Module failure can also be triggered by previous short-circuit events that did not blow a fuse but degraded the silicon. In water-utility service, the combination of humidity, ambient temperature swings, and continuous low-load operation accelerates this degradation compared to indoor industrial use.

3. Motor Parameter Mismatch

If the drive was commissioned with a particular motor and the motor was later replaced, or if the parameters were downloaded from a different unit, the I²t model is computing against the wrong nameplate. Especially common errors:

• Different rated current at the same power rating
• Different power factor or efficiency class
• Different service factor (1.0 vs 1.15)
• Different no-load current (often estimated rather than measured)
• 50 Hz vs 60 Hz base frequency

4. DC Bus Capacitor Health

The original poster noted that capacitors "checked correct" with a hand-held tester — but ESR testers only measure capacitance at one frequency and voltage, and aged electrolytics in a live DC bus often pass such tests while still having unacceptably high ESR under load. The result is excessive 100/120 Hz ripple on the DC bus, which couples into the current control loop and causes oscillation. The proper check is to measure DC bus ripple with an oscilloscope at the test points on the power module with the drive enabled but motor disconnected.

5. Mechanical Binding

Even with the pump decoupled, the motor itself has bearings and an encoder coupling (if used). A failing bearing, a misaligned encoder, or partial single-phasing of the stator can produce the jogging motion. Spin the motor shaft by hand with the leads disconnected — it should turn smoothly with no rough spots, no end play, and no audible grinding.

6. Setpoint Source Instability

An analog setpoint that is unstable (noise, ground loop, faulty DAC in the HMI, or a 4-20 mA loop with insufficient loop voltage) can command small oscillations around zero. Confirm with r020 (speed setpoint) and r021 (actual speed) traces via DriveMonitor before assuming the drive itself is the source of the oscillation.

7. Encoder Feedback Failure

If P100 is set to a vector mode using encoder feedback (typically P100 = 4 or 5), a broken encoder wire, dirty encoder disk, or faulty encoder supply produces the exact symptom: small jittering motion followed by a fault. Confirm P100 setting and check the encoder wiring and supply voltage (typically 5 V or 24 V depending on encoder type) at the X300 connector on the CUVC card.

Diagnostic Procedure

Apply the following steps in order. Do not skip the parameter-backup step — if the unit is repaired, you will need the original parameters to restore the machine to its previous operating point.

1. Document the fault: Read r947 (fault number), r949 (fault time / power-on hours), r951 (fault value), and the fault history from r026 / r027 (most recent faults) and r030 / r031 (most recent warnings). Note the DC bus voltage at trip (r016), output frequency (r012), output current (r014), and heatsink temperature (r018).
2. Backup parameters: Connect DriveMonitor via RS485 (X100 on the CUVC card). Upload all parameters and save the .dnl file. If you have a previous good backup, compare parameter-by-parameter using the DriveMonitor comparison function.
3. Visual inspection: Look for discoloured components on the CUVC card, bulging or leaking capacitors, dust buildup, corrosion on connectors, and loose ribbon cables. Pay particular attention to the backplane connector where the CUVC plugs into the power module.
4. Test the current sensors: With the motor disconnected, set P100 = 0 (V/f linear) and command a small fixed frequency (for example 5 Hz). Use a true-RMS clamp meter on each output phase. The currents should be within ±10% of each other. If one phase is significantly different, that CT or its wiring is suspect.
5. Test the IGBT module: With the drive powered off and discharged (wait at least 5 minutes after isolation, then verify with a meter), use a multimeter on diode-test mode between each output terminal and the DC+ and DC- bus. You should see a forward voltage drop of roughly 0.3-0.5 V on each junction. An open reading in any direction, or a short, indicates a failed module.
6. Test the motor: Megger the motor windings phase-to-phase and phase-to-ground. A short or low resistance to ground will cause the drive to detect a fault. Also measure phase-to-phase resistance with a low-ohm meter — all three should match within 5%.
7. Test the DC bus: With the drive powered and enabled but motor disconnected, measure the DC bus ripple with an oscilloscope. Ripple should be below 5% of nominal bus voltage (for example below 30 V on a 600 V bus). Higher ripple indicates capacitor degradation.
8. Run in V/f mode: If the drive still trips in V/f mode (P100 = 0), the problem is in the power stage, not the vector controller. If it runs without tripping in V/f mode but trips in vector mode (P100 = 3 or 4), the issue is in motor parameters, encoder, or current sensing.

Parameter Verification

Use the following table to verify that the drive parameters match the motor nameplate and the application requirements. Mismatches in this table account for a large fraction of intermittent F011 trips.

Auto-Tuning (Motor Identification) Procedure

The CUVC auto-tune routine (P115) measures P109 through P113 automatically. It must be run with the motor cold, uncoupled from the load, and able to rotate freely through a full mechanical revolution. The drive will apply short test pulses, rotate the motor in small steps, and finally spin it up to a controlled speed. During this routine, monitor r014 (output current) — it should stay below 80% of P102. Higher values indicate that the encoder is mis-wired (if used) or that the motor is mechanically locked.

1. Verify P100, P101-P108 are correct from the nameplate.
2. Decouple the load.
3. Set P115 = 1 and press the green run button on the OP1S or issue a run command via DriveMonitor.
4. Wait for the routine to complete (typically 30-90 seconds).
5. Verify P109-P113 are now populated with non-zero values.
6. Set P115 = 0 to lock the parameters.

Hardware Inspection — Step by Step

Always isolate and lock out the drive before opening it. The DC bus capacitors in a Masterdrives Compact retain dangerous voltage for several minutes after the supply is removed. Verify with a meter on the DC+ and DC- terminals before touching anything inside the chassis.

Disassembly and Visual Checks

1. Isolate the feeder, apply lock-out / tag-out (LOTO).
2. Wait 5 minutes for DC bus to discharge through the internal discharge resistors.
3. Verify zero voltage on DC+ and DC- with a CAT III meter.
4. Remove the CUVC card by sliding it out on the card rails.
5. Inspect the card for capacitor bulging, burnt resistors, and connector damage.
6. Inspect the backplane connector pins for bent or corroded contacts.
7. Re-seat the CUVC card firmly; the locking levers should click into place.
8. Inspect the power module for dust buildup, especially on the heatsink fins.
9. Inspect the cooling fan for free rotation and quiet operation.

Current Sensor (CT) Test

With the motor disconnected and the drive enabled in V/f mode at a fixed frequency, measure each output current with a true-RMS clamp meter. The three phases should be within 10% of each other. A phase reading zero or significantly lower than the others indicates a CT problem or a broken wire between the CT and the CUVC card. A phase reading higher than the others indicates that one of the other CTs is reading low, or that the CUVC card has a faulty input stage.

Output Stage Diode Test

Powered off, isolated, and verified dead:

• Set multimeter to diode test mode.
• Red lead on U output, black lead on DC+: should read 0.3-0.5 V (one IGBT diode forward).
• Red lead on U output, black lead on DC-: should read OL (open).
• Reverse: black on U, red on DC+: OL.
• Black on U, red on DC-: 0.3-0.5 V.
• Repeat for V and W outputs.
• Any short (reading near 0 V in both directions) or open in both directions indicates a failed module.

Motor Insulation Test

Disconnect the motor leads from the drive. Use a 500 V or 1000 V megohmmeter:

• Phase-to-phase: should be greater than 100 MΩ.
• Phase-to-ground (each phase): should be greater than 100 MΩ.
• Any reading below 5 MΩ indicates insulation degradation that will cause overcurrent trips. Windings must be dried, re-impregnated, or replaced.

DC Bus Ripple Test

With the drive powered and enabled, motor disconnected, and the drive in V/f mode at a small fixed output frequency, measure the DC bus voltage with an oscilloscope set to AC coupling. The peak-to-peak ripple should be below 5% of the nominal bus voltage. For a 400 V class drive the nominal bus is roughly 540-620 V DC, so ripple should stay below 30 V peak-to-peak. Excessive ripple points to capacitor degradation even if the capacitors measure correctly on a hand-held ESR meter.

Power Stage and Current Sensor Repair

If the diode test or current measurement localises the fault to the power module, replacement is the practical solution. The 6SE7233-6FS00 series uses a specific IGBT block that must be ordered by the original part number. In some cases, the CT is a separate component that can be replaced individually; in others it is integrated into the power module and the entire module must be replaced.

If the motor insulation test fails, the motor must be rewound or replaced. Continued operation with degraded insulation will repeatedly trip the drive and may cause catastrophic failure of the IGBT module due to a phase-to-ground short.

If the CUVC card is suspect, swap with a known-good spare (if available) before ordering a replacement. The CUVC card holds the parameter set in non-volatile memory, so a card swap will require reloading parameters from backup.

Re-Commissioning Procedure

After the hardware fault is repaired, follow this re-commissioning sequence to verify correct operation before returning the drive to service.

1. Restore all parameters from the backup file, or re-enter manually if no backup exists.
2. Verify P100 is set to the correct control mode for the application.
3. Set P115 = 1 to run the motor identification (auto-tune) routine. The drive will run the motor at various test points; ensure the motor is decoupled from the load during this step.
4. After auto-tune completes, set P115 = 0 to lock the parameters.
5. Run the motor uncoupled in manual mode at low speed (5-10 Hz). Verify smooth rotation in the correct direction.
6. Check current balance across all three phases. The values should be within 5% of each other.
7. Re-couple the load and run through a complete operating cycle, ramping up to full speed and back down.
8. Monitor r014 (output current) and r018 (heatsink temperature) during the cycle. Current should not exceed P102, and temperature should stabilise well below the trip threshold (typically below 80°C).
9. Set the OP1S panel to display the active fault buffer (P052 = 0 to view r047) and leave it visible during the first production shift.

Verification and Long-Term Monitoring

After re-commissioning, leave the drive on continuous monitoring for at least one full operating week. Capture the following diagnostic words via DriveMonitor on a daily basis:

• r016 — DC bus voltage (look for sagging or excessive ripple)
• r017 — Input voltage (mains quality)
• r014 — Output current (load profile)
• r018 — Heatsink temperature (thermal trend)
• r047 / r048 — Active faults and warnings
• r020 / r021 — Setpoint vs actual speed (loop stability)

Any re-occurrence of F011 within the first month points to a remaining hardware or parameter issue and warrants another diagnostic pass. If the drive ran cleanly for 30 days and then began tripping, suspect a developing hardware fault rather than a parameter problem.

Spare Parts and Migration Planning

For a Masterdrives installation in continuous service, the following spare parts should be kept on hand or have guaranteed short lead times:

New production of SIMOVERT Masterdrives ended in 2005-2007. Refurbished or factory-remanufactured parts are the realistic option for an emergency. Identify the specialist refurbishment vendors in your region before a failure occurs; in water and process utilities, the cost of an unplanned shutdown usually justifies carrying a fully loaded spare CUVC card and a refurbished power module.

Migration Path if Spares Are Unavailable

1. Refurbished CUVC + power module from a specialist vendor: fastest, lowest engineering cost, retains existing motor and cabling.
2. Replacement with SINAMICS G120 or G120X: current Siemens platform; requires mechanical re-fit, new parameterisation, possibly new motor if voltage class changes.
3. Replacement with a third-party VFD (ABB, Schneider, Danfoss): similar engineering effort as option 2; useful when stock of SINAMICS is also constrained.

Preventive Maintenance Schedule

For a 20+ year old drive in a critical water-utility application, the following PM tasks should be on a fixed schedule:

Troubleshooting Matrix

Frequently Asked Questions