Resolving Siemens Master Drive CUVC F002 F029 F070 Faults

Problem Overview

Replacing a CUVC (Control Unit Vector Compact) card in a Siemens SIMOVERT MASTER DRIVES converter is a high-risk maintenance action. When the replacement is performed without first completing the power section definition, the drive typically refuses to start and instead reports a chain of faults: F002 (DC link monitoring / inverter-side fault), F029 (power section not defined or mismatched), and F070 (parameter set download error). A parameter download is then rejected for a subset of parameters (commonly 5 to 10 indices), and the commissioning parameters P051 and P052 disappear from the operator menu, leaving the technician with no clear path to recover.

This article consolidates field-proven recovery steps for the SIMOVERT MASTER DRIVES family (VC and MC series) based on the official Siemens CUVC/CUMC Card Replacement knowledge base article (ID 24124826) and applied diagnostics for the supporting hardware: PSU1, PSU2, IVI, and VDU boards.

CUVC, CUMC, and the Master Drive Control Architecture

The SIMOVERT MASTER DRIVES platform separates the control electronics from the power electronics. A successful start-up depends on every board in the stack being electrically and logically consistent.

The CUVC receives the DC link voltage through the VDU and PSU chain. If any element in that path is open or shorted, the CUVC sees a wildly incorrect value and either refuses to start (F029) or trips immediately on apparent over-/under-voltage (F002). After a CUVC swap, the new card arrives blank and the firmware does not yet know which power section it is bolted to — the root cause of the rejection storm that follows.

Fault Code Reference (Master Drive VC/MC)

Root Cause Analysis

When a CUVC card is replaced, the new card is electrically and logically empty. The old card stored the power section code that identifies the inverter rating (e.g., 6SE7090-0XX85-1XX0). Without that code, the firmware cannot validate:

1. That the parameter set being downloaded applies to the connected hardware.
2. That the current and voltage limits in r006 (DC link voltage display), r017 (output current), and the protection thresholds are within range.
3. That the DC link voltage readback (scaled through VDU → PSU → CUVC) is mapped to the correct scaling factor.

The Siemens KB article 24124826 states explicitly that the power section definition must be completed before any parameter set download. The typical failure chain looks like this:

1. Technician installs the new CUVC and immediately uploads the saved parameter file.
2. Downloader writes what it can, but 5–10 parameters fall into a "rejected" bucket — these are the power-section-dependent indices.
3. F070 is raised on completion of the partial download.
4. Operator attempts to navigate to P051 / P052 to set the power section manually, but the parameters are not visible because the parameter tree is locked to a different access level or the firmware is still in a fault-latched state.
5. Operator attempts to start. The CUVC reads the DC bus through the VDU/PSU chain. The firmware either sees a 0 V readback (F002) or, if the readback works, sees a value that does not match the un-defined power section's expected scaling (F029).

A second contributor, present in the original case, is the phantom 70 V DC that appears on the PMU before start, drops to 0 V during the start attempt, and returns to 70 V twenty seconds after stop. This pattern is diagnostic of a healthy DC link with a broken sensing path: the 70 V is residual bias from the VDU divider, the 0 V is the CUVC resetting the sense input during pre-charge, and the slow recovery is the VDU/PSU filter discharging.

Pre-Replacement: Document Everything

Before powering down for the card swap, capture the following so the new card can be brought back to a known state:

1. Read and record all Pxxx parameters on the old CUVC, or upload the parameter set via DriveMonitor / SIMOVIS to a project file (.dnx or .pnx depending on version).
2. Note the power section code from the old card. This is usually in P052 or printed on a label on the old CUVC — record the 6SE70 order number (e.g., 6SE7090-0XX85-1XX0).
3. Record the CUVC firmware version from the label (e.g., V2.x, V3.x). The replacement card must run the same major firmware line; mixing V1.x parameter sets onto V3.x firmware is the single most common cause of mass parameter rejection.
4. Record the DC link voltage at the bus terminals with a calibrated meter for comparison with r006 after the swap.
5. Photograph the terminal strip, encoder wiring, and any option boards (CBP2, CBC, SLB).

Step-by-Step Recovery Procedure

1. Confirm isolation and discharge. Lock out the upstream breaker. Wait the capacitor discharge time printed on the cabinet door (typically 5–20 minutes for 900 V class). Measure 0 V at the DC bus with a 1000 V DC meter.
2. Swap the CUVC. Remove the ribbon cables, fiber-optic leads, and the card itself. Install the new card. Do not re-attach the fiber-optic links to the IGBT gate drivers until the power section is defined, to avoid nuisance gate-drive faults.
3. Power up the control section only (DC link still discharged). The PSU1/PSU2 will boot from the residual bias; this is normal. The PMU should show "--- ---" or the firmware banner.
4. Set the access level. On the PMU, navigate to P051 in some firmware builds, or to a parameter access selector in others, and set it to the Commissioning level (value 2 or 3 depending on firmware). This is the step that makes P052 appear in the menu. If P051/P052 are not visible, the access level is still at the Operator level (typically 0 or 1).
5. Enter the power section code. Open P052 (or the equivalent power section parameter for your firmware) and enter the code recorded from the old card. Acknowledge. The CUVC will reset its parameter tree and rebuild the access list.
6. Verify F029 clears. Acknowledge any active faults. Power cycle the control electronics. The PMU should now show a healthy state with no F029 or F070 latched.
7. Verify the DC link readback. Re-energize the line. With the line on and the inverter still disabled, the DC bus should rise to ≈1.35 × V_LL (e.g., 935 V DC from a 690 V supply, 1080 V DC from an 800 V supply). Read r006 on the PMU; it should match the bus meter within ±2 %.
8. Now download the saved parameter set. With the power section defined, DriveMonitor / SIMOVIS will accept the full parameter file. The previously rejected indices (typically motor data, current limits, switching frequency, V/f shape) will write cleanly.
9. Auto-tune and verify. Run the motor identification routine (typically P115 = 1 for stationary measurement or P115 = 2 for rotating measurement, firmware-dependent). Verify r017, r018, and the encoder feedback if used.

Restoring P051 and P052 to the Menu

The case described — "P052, P051 not coming in the list as it not exist" — is the single most common recovery blocker after a CUVC swap. The parameters are not missing; they are filtered out by the access level. Use the following diagnostic ladder:

1. Press the PMU P key, enter 051, press P again. If the value shown is 0 or 1, the access level is locked at Operator or Standard.
2. Change P051 (or the access-level parameter for your firmware) to 2 (Commissioning) or 3 (Service). Acknowledge.
3. Re-enter the parameter menu. P052 and the rest of the power-section-dependent parameters are now visible.
4. If the PMU still shows n.u. (nicht verwendet / not used) on these parameters, the firmware in the new CUVC does not match the power section of the connected inverter. Verify the order number on the CUVC label against the inverter nameplate.

DC Bus Sensing Path Diagnostics

The "70 V phantom → 0 V at start → 70 V after stop" signature indicates the DC link is healthy but the CUVC cannot see it. Trace the sensing path in this order:

1. Confirm actual DC bus voltage. Measure across the DC+ and DC- bus bars with a 1000 V DC meter. Expect 900–950 V DC for a 690 V supply after pre-charge.
2. Check the DC bus fuses to the inverter section. Two fuses sit between the rectifier output and the IGBT DC link on 900 V class units. A blown fuse will leave the rectifier charging the bus while the inverter sees a sagging or zero voltage. The bus will appear healthy on the rectifier side and dead on the inverter side. r006 will reflect the inverter-side voltage.
3. Check the VDU board. On 900 V class drives the VDU is a small PCB connected to the DC bus through high-impedance resistors and to the PSU through a ribbon or plug. Inspect for discoloration, cracked solder joints, and proper seating of the connector. The VDU is the most common point of failure when the phantom 70 V appears.
4. Check the PSU1 board. The PSU receives the attenuated DC link voltage from the VDU and conditions it for the CUVC. A failed PSU scaling amplifier will return a constant or zero value to the CUVC. Swap PSU1 with a known-good spare to isolate.
5. Check the IVI board. The IVI carries the current and voltage feedback between the power stack and the CUVC. A failed IVI can present a "stuck at zero" voltage to the CUVC even when the bus is live.
6. Check the ribbon cable between VDU → PSU → CUVC. A bent pin or oxidised contact at the ribbon connector is enough to break the sense path. Reseat, and if the fault recurs, replace the ribbon.

Fuse and Power Path Verification

On a 900 V class Master Drive, the DC link is fused between the rectifier and the IGBT capacitor bank. The fuses are typically:

• Two high-speed semiconductor fuses (e.g., Bussmann / Ferraz Shawmut, ratings such as 630 A / 1000 V for 400 kW units, or per the inverter nameplate).
• Located inside the cabinet, often behind a clear protective cover, in series with the DC+ and DC- rails.

Test procedure:

1. With the drive isolated and the bus confirmed discharged, remove the fuse holders.
2. Measure continuity on each fuse with a multimeter on the diode / resistance range.
3. Replace any fuse that reads open. Do not bypass the fuse — the fuse is the only overcurrent protection between the IGBTs and the DC link capacitors.
4. Inspect the fuse holders for arcing, discoloration, or loose crimps. A hot fuse holder indicates a high-resistance joint that will fail again.

Parameter Download Best Practices After a Card Swap

1. Always perform the power section definition first, per Siemens KB 24124826. The order is: power section → access level → motor data → application data → option-board configuration.
2. Match firmware before downloading. A parameter set saved from a V2.x CUVC will not load cleanly onto a V3.x CUVC and vice-versa. Compare the firmware labels on the old and new cards before connecting DriveMonitor.
3. Use a clean download buffer. After defining the power section, reset the CUVC to factory defaults (typically P970 = 1 or P060 = 1, firmware-dependent) before the first upload. This clears any partial-write artefacts from a previous failed download.
4. Identify the rejected parameters by number. DriveMonitor logs each rejected parameter with its index. Common culprits are P095 (motor type), P100 (rated current), P101 (rated voltage), P107 (rated power factor), P108 (rated speed), P114 (control mode), P115 (auto-tune trigger), and the current limit parameters. If any of these are rejected, the power section definition was incomplete.
5. Verify after download. Read back the full parameter set and compare against the source file. DriveMonitor's parameter comparison view will highlight any index that did not write.

Commissioning Verification Checklist

Troubleshooting Matrix

When to Escalate to a Service Partner

If the fault persists after PSU1, PSU2, IVI, VDU, base card, and CUVC have all been swapped with known-good spares, escalate with the following data package:

1. Photos of the CUVC firmware label and the inverter nameplate.
2. Full DriveMonitor parameter dump from the unit in its current state.
3. Fault history (typically accessible via r947, r949, firmware-dependent).
4. DC bus voltage measured at the terminals versus r006.
5. Output of the operating-hours and trip counters.

Provide this to a Siemens-certified Master Drive service partner or open a case through the official Siemens Industry Online Support portal referencing KB 24124826.