Troubleshooting Simovert Masterdrive F026 Fault Complete

1. Problem Overview: Simovert Masterdrive F026

The F026 fault code on the Simovert Masterdrive family (6SE70 / 6SE71 / compact and chassis units) indicates a fault inside the inverter power section or its associated firing and current-sensing circuitry. The drive trips during the deceleration ramp from full speed to zero, but it is typically able to operate correctly at low speed without intervention. This signature — fault on high-speed deceleration, no fault at low speed — is the single most useful diagnostic observation when triaging an F026 event in the field.

F026 is not a single-component failure code. It is a class of faults that can be produced by any of the following:

• Shorted or open IGBT modules in the inverter stack.
• Defective IGD (Impulse Gate Driver / firing) board.
• Defective IVI (current / voltage interface) board.
• Damaged or aged optical fiber cables between the CU (Control Unit) and the IGD.
• Failed current transformers (CTs) on the AC bus.
• Deceleration ramp programmed too aggressively for the load inertia (parameter P464).

Each cause produces the same fault code at the keypad, which is why F026 is one of the more frequently misdiagnosed events on legacy Masterdrive installations. A systematic, component-by-component isolation is required.

2. Affected Drive Population and Firmware Revisions

F026 applies across the Simovert Masterdrive VC (Vector Control) and MC (Motion Control) ranges, including:

Firmware versions through approximately V3.3x and V4.x for the 6SE70 and V2.x for the 6SE71 share the F026 mapping. Drives that have been retrofitted to newer CU boards (CUSA, CUSI) generally preserve the same fault definitions, but a firmware update is recommended as part of any repair to ensure known IGD initialization issues are patched.

3. Root Cause Categories for F026

The F026 trip is generated when the firing circuit, current sensing path, or the IGBT stack itself produces a signal that is inconsistent with the command issued by the control board. The four primary root-cause groups, in order of field frequency, are:

1. Power section (IGBTs): Short-circuit, open-base, or thermal failure of one or more inverter modules.
2. Firing circuit (IGD): Loss of gate drive, desaturation latch, or loss of fiber-optic receive signal.
3. Current measurement (IVI / CT): Open CT secondary, saturated CT core, or drift in the IVI current-signal conditioner.
4. Optical fiber link: Cracked, bent, contaminated, or aged plastic fiber between CU and IGD.

A fifth, non-hardware root cause is also common: an aggressive deceleration ramp (P464) combined with high inertia produces DC-link overvoltage that the drive interprets as a power-section event and reports as F026. The fault is real, but the fix is parameter-only.

4. Diagnostic Sequence: From Field to Bench

Follow this sequence before swapping any module. The order minimizes wasted spares and ensures the actual root cause is identified, not just the most visible symptom.

1. Capture fault context. Read the drive memory using DriveMonitor / Drive ES on a PC connected to the RS232 (X300) or via USS on the terminal strip. Note the actual values of r015 (DC link voltage), r017 (motor current), r018 (output frequency), and the timestamp relative to the deceleration event.
2. Review P464 (ramp-down time). A P464 value too low for the load GD² will force the line-side regenerative limit and produce a DC bus spike at zero speed. Increase P464 in 10 s increments and re-test before opening the cabinet.
3. Inspect fibers visually. With the drive isolated, remove the plastic optical fibers between the CU and the IGD/IVI. Look for tight bends (radius < 25 mm), yellowed plastic, cracked tips, or contamination on the lens face.
4. Test IGBTs in-circuit. Use a digital multimeter on diode mode across each IGBT emitter-collector and gate-emitter junction. A shorted or open module is detected in seconds.
5. Measure CT resistances. On the compact unit the current transformers present a known resistance pattern; deviation indicates a damaged CT or open secondary winding.
6. Swap the IGD board. If all of the above pass, replace the IGD with a known-good spare and re-test. The IGD is the most failure-prone board in the firing path.
7. Swap the IVI board. Last in the swap chain, because the IVI rarely fails without a corresponding CT or fiber symptom.

5. IGBT Power Module Testing Procedure

For a chassis drive with paralleled modules, test each module independently. For a compact drive, the inverter is a single integrated block; the test sequence still applies to each of the three half-bridges.

Procedure with the drive de-energized and the DC link verified at 0 VDC:

1. Disconnect the motor leads from terminals U, V, W to isolate the inverter from the cable/motor.
2. Disconnect the DC bus input (P, N) so the line-side rectifier is removed from the measurement path.
3. Set the multimeter to diode test. Measure collector-to-emitter (C → E) and emitter-to-collector (E → C) for each of the three phases.
4. A healthy module reads 0.3 – 0.7 V in the forward direction and open (> 1.5 V or OL) in the reverse.
5. Measure gate-to-emitter (G → E). A shorted gate-emitter junction (0 V or 0.0x V in both polarities) is a failed module.
6. Compare the three phases to each other. A delta of more than 0.1 V between phases on the same leg suggests a partial degradation that will trip F026 under load.

6. IGD (Impulse Gate Driver) Board Verification

The IGD converts the fiber-optic gate commands from the CU into the isolated gate-drive signals for the IGBT modules, and it returns a fiber-optic status (desaturation, fault, power-good) back to the CU. A defective IGD can produce F026 with a perfectly good IGBT.

Field checks before replacement:

• LED indicators: The IGD typically carries one LED per phase plus a status LED. A missing or red status LED during power-up indicates the board is not initializing.
• Power supply rails: With the drive isolated but the auxiliary 24 V present, measure the IGD supply rails at the test points (typically +5 V, +15 V, -15 V). Any rail outside ±5% of nominal causes gate drive instability.
• Desat trip point: The IGD monitors Vce(sat) of the IGBT during turn-on. A drifted desat comparator will trip the IGD on inrush current that the IGBT is actually capable of handling. The result is a false F026 on every ramp.

If any of the above conditions are present, replace the IGD with a known-good unit. On the 6SE70 compact, the IGD is a plug-in card; on chassis drives it is a slot-in module. Always reseat the optical fibers with the proper latching connectors and avoid forcing the plastic bodies — the latches break easily.

7. IVI Board and Current Transformer (CT) Checks

The IVI (current/voltage interface) board conditions the CT secondary currents and the DC link voltage measurement for the CU. If a CT is open, the IVI sees infinite impedance on that phase and the CU registers a current that is impossible for the firing pattern, triggering F026.

Reference resistance values for the compact-type CTs used in Masterdrive chassis units are:

Procedure to measure:

1. Isolate the drive. Verify zero DC link.
2. Disconnect the CT secondary lead at the IVI terminal block.
3. Measure resistance between the two secondary terminals of each CT with a 4-wire ohmmeter (or a DMM in resistance mode if 4-wire is unavailable).
4. Compare the reading against the expected value. A reading of OL (open) or 0 ohm (shorted) means the CT is failed and must be replaced.
5. If all three CTs read within tolerance, the IVI board itself is suspect. Bench-test the IVI by injecting a known test current and verifying the analog output, or simply swap with a spare.

CTs rarely fail without an associated event (mechanical shock, water ingress, thermal cycling) — look for evidence of the trigger during the visual inspection of the cabinet before condemning the CT.

8. Optical Fiber Cable Inspection

Plastic optical fiber (POF) on the Masterdrive is a wear item. The polymer yellows and becomes brittle with heat, and a bend radius below approximately 25 mm causes internal cracking that the drive interprets as a gate-driver fault. F026 produced by a damaged fiber is one of the most common field scenarios.

• Inspect the full fiber run from the CU to the IGD and from the IGD to the IVI. Pay attention to cable ties that have been over-tightened and to any section passing near a heatsink or power cable.
• Pull each fiber from its connector and inspect the lens face. Even a fingerprint on the POF endface attenuates the signal by 30% or more, enough to trip the IGD's loss-of-signal detector.
• Clean the endfaces with a dedicated POF cleaning swab and isopropyl alcohol. Do not use a paper wipe — the fiber scratches easily.
• Replace any fiber that shows cracking, yellowing, or that was previously routed with a tight bend.

9. Parameter Adjustment: Ramp-Down Time (P464)

When a brand-new drive still trips F026 under the same load and ramp profile, the cause is mechanical, not electrical. The load is feeding energy back into the DC link faster than the brake chopper (if fitted) can dissipate it, and the bus voltage rises to a level that the drive reads as a power-section event.

The relevant parameters on the 6SE70 family are:

Field-proven method to size P464:

1. Compute the deceleration energy: E_dec = 0.5 × J_total × (ω_max² − ω_stop²) where J_total = J_motor + J_load in kg·m².
2. If a brake chopper is fitted, ensure its resistor is sized for the expected dissipation: P_brake = E_dec / t_dec.
3. Set P464 such that the required brake power stays below the resistor's continuous rating, with margin for repeated cycles.
4. Validate by monitoring r015 during a controlled ramp. The bus voltage should remain below the brake-chopper turn-on threshold (typically 750 VDC on a 400 V class drive) for the entire ramp.

A common starting value for a high-inertia fan or centrifuge is P464 = 60 s, then trim from there based on the captured trace. Setting P464 to a value lower than the time required for the load to coast to stop will always trip F026 at the bottom of the ramp.

10. Replacement Procedure and Re-Commissioning

Once the failed component has been identified, follow the manufacturer-recommended replacement sequence:

1. Document the existing parameter set using DriveMonitor or the PMU (parameterization unit) on the keypad. Save the parameter file (.dnl or .par) to a PC.
2. Replace the failed component with a new or factory-rebuilt unit. For chassis drives, lift the IGD out of its slot using the extraction levers; do not pry with a screwdriver.
3. Re-seat the optical fibers. Confirm the latches click and that the fibers are routed with a minimum 25 mm bend radius.
4. Re-apply control power only. Verify the CU, IGD, and IVI initialize without fault. Look for a clean READY (r001 = 008) state.
5. Apply main power. Verify DC link pre-charge completes and the bus voltage reaches nominal.
6. Restore the parameter file. Confirm critical parameters (P060, P070, P100, P101, P107, P108, P464) match the saved values.
7. Run the motor uncoupled (no load) and verify balanced three-phase currents on the DriveMonitor trace.
8. Re-couple to the load and run through a full ramp-up / ramp-down cycle, capturing the F026 trigger condition (full speed to zero) for verification.

11. Verification and Functional Testing

The repair is not complete until the original trip condition is reproduced without fault. Verification steps:

• Static test: With the drive in READY, command a ramp from f_max to 0 with the previously failing P464. The drive should reach 0 Hz without F026.
• Dynamic test: Capture r015 (DC link voltage) and r017 (motor current) during the ramp. Look for transient overshoots exceeding the brake-chopper threshold.
• Thermal soak: Run the drive at full load for a minimum of 30 minutes, then repeat the ramp. Some IGBT and IGD failures are thermally intermittent and only show up after the inverter reaches operating temperature.
• Trip counter: Read the fault memory (P053 / r947 family) and confirm F026 is no longer incrementing after the test cycle.

12. Preventive Maintenance and Field Notes

A short PM schedule reduces the probability of a repeat F026 event by a significant margin:

Field notes from repeated service calls on this fault family:

• A drive that was just replaced and still trips F026 almost always points at the load (P464) or at a shared component upstream (line quality, regenerated bus from another drive on the same DC bus).
• When two drives share a common DC bus, the second drive's P464 must be set to match the energy-return capability of the source, not just the motor inertia.
• CTs with the compact form factor (23.9 / 53.5 ohm) are sourced separately from the bus bars; a partial CT failure can read close to spec and still cause F026 under load. Replace and verify, do not only measure.