Simovert Master Drive FC Manual Package and FC1 to CUVC

Overview

The Siemens SIMOVERT MASTERDRIVES FC (Frequency Control) chassis-type converter is a legacy AC drive platform originally released under the 6SE70 series. Field engineers still encounter these drives in service, retrofit, and migration projects because of long installed lifecycles in metals, mining, paper, water/wastewater, and HVAC infrastructure. The FC variant uses an open-loop V/Hz or closed-loop vector control strategy on induction motors and ships from the factory with one of two main control architectures: the older CU1/CB1 board pair, or the newer CUVC (Vector Control, Voltage/frequency/closed-loop) board with a CBP (Communication Board, PROFIBUS) or CBC (CAN) option.

Two recurring field problems appear when working on these drives:

1. Documentation availability. The complete manual package (Operating Instructions Part 1 + Part 2, parameter list, function diagrams, COM board manuals, drive monitor manual) is not bundled on a single download page. Engineers must request the bundle through Siemens Online Support.
2. Parameter file incompatibility. Drives with the legacy CU1 board save parameters in FC1 format, while the CUVC board expects a different binary structure. Field-converted files frequently fail to load into DriveMonitor, and DriveMonitor itself ships with multiple database versions (commonly v1.2 and v1.3) that are mutually incompatible for the same firmware build.

This reference consolidates the documented path to obtain the manual bundle, the FC1 to CUVC parameter conversion procedure, the DriveMonitor version compatibility rules, and a verification checklist for chassis-type FC drives.

Drive Architecture and Chassis Form Factors

The MASTERDRIVES FC chassis line spans a wide power range delivered in different mechanical frame sizes. The chassis (chassis-type) variant is the free-standing, panel-mount cabinet-style construction typically rated from approximately 2.2 kW up through several hundred kW at 400–480 V three-phase (with 690 V variants available on selected part numbers).

The Vector Control documentation set (Siemens order number 6SE7087-6JP60, revision dated 05.2003) covers the CUVC firmware, parameter set, function blocks, and free-function blocks for the MASTERDRIVES platform. The same chassis-type mechanical construction is reused across FC and VC (Vector Control) drives, but the firmware, parameter structure, and binary file format differ.

Obtaining the Complete Manual Package

Siemens does not host a single zipped archive that contains the entire MASTERDRIVES FC chassis documentation set. The complete set typically comprises:

• Operating Instructions Part 1 (installation, commissioning, diagnostics)
• Operating Instructions Part 2 (function descriptions, parameter list, fault/warning list)
• Parameter list (Excel or PDF)
• Function diagram set (FBDs for CU/CUVC firmware)
• COM board manual (CBP, CBC, Ethernet options)
• DriveMonitor / SIMOVIS software manual
• Spare parts list and dimensional drawings for the specific chassis frame

Steps for the support request:

1. Open the Siemens Industry Online Support portal at support.industry.siemens.com.
2. Sign in with a registered Siemens customer account (free registration).
3. Navigate to "My Support" → "Service Request" and create a new request.
4. In the request, include the drive's MLFB / order code (for example, 6SE7031-...FC or 6SE7087-...FC), serial number, firmware version printed on the CU/CUVC label, and the precise list of manuals you need.
5. Submit. Siemens Support will respond with PDF attachments or links; turnaround is typically several business days.

Engineering firms that maintain a Siemens partner agreement (Solution Partner / Approved Partner) may also obtain the bundle through the partner extranet, which often includes the same PDFs in a structured download tree.

CU1 / CB1 to CUVC / CBP Replacement – Hardware Migration

Siemens officially documented a path to retire the legacy CU1/CB1 electronics and fit the modern CUVC + CBP electronics on the same chassis. The motivations are usually one of:

• Failure of the obsolete CU1 board (no spare stock, end of life).
• Need to integrate the drive into a modern PROFIBUS-DPV1 or PROFINET network.
• Need to use DriveMonitor's newer functionality (free function blocks, firmware r2.x and later).

The migration checklist:

1. Verify mechanical compatibility. The CUVC board is a different PCB geometry than CU1. A mechanical adapter plate or replacement electronics box is required. Confirm the part number from the Siemens conversion guide that matches your chassis frame.
2. Replace the control board. Power down the drive, wait for DC-link capacitors to discharge (typically 5 minutes after mains removal per the warning on the cabinet), and swap CU1 → CUVC, CB1 → CBP.
3. Apply CUVC firmware. Use DriveMonitor (or a SIMATIC Field PG with the appropriate EPROM / flash programming tools) to load the CUVC firmware image. Choose firmware that matches the drive's power section rating.
4. Convert the parameter file. This step is detailed in the next section.
5. Verify current transducer scaling. CUVC uses a different parameter range for current and torque scaling than CU1/FC1. Always run the automatic motor identification (P115 = 1 or equivalent) before enabling the drive on load.
6. Re-verify safety wiring. The STO (safe torque off) wiring, if any, must be re-confirmed against the CUVC terminal assignment; pin assignments differ from CU1.

FC1 to CUVC Parameter File Conversion

The binary parameter file produced by a CU1 (FC generation) drive is encoded with the FC parameter set. A CUVC drive will reject this file when downloaded through DriveMonitor unless the file is converted. The conversion is performed inside DriveMonitor (or via the standalone SIMOVIS tool) using the firmware / database pair that matches the CUVC build.

Conversion procedure:

1. Open DriveMonitor and connect to the old CU1 board. Upload the parameter set from the drive and save it locally as *.dnx (or *.pdv, depending on DriveMonitor version).
2. Note the firmware version printed on the CU1 PCB label (for example, "FC1 Vx.x").
3. Install or select the DriveMonitor database matching the target CUVC firmware. Siemens ships multiple database files (commonly DB v1.2 and DB v1.3) that map to different CUVC firmware revisions. The database version is independent of the firmware version printed on the CUVC PCB.
4. Open the uploaded FC1 file in DriveMonitor. DriveMonitor will prompt "Convert to current database?" Confirm.
5. DriveMonitor writes a new file in CUVC binary format. Save the file with the same filename and a _CUVC suffix to avoid overwriting the original.
6. Connect DriveMonitor to the CUVC drive (RS232 via OP1S, RS485 USS, or PROFIBUS-DP via CBP with DriveMonitor in online mode).
7. Download the converted file to the CUVC drive. Cycle power, then verify parameters P000 to P050 against the conversion report DriveMonitor generates at the end of step 4.

Common conversion issues

DriveMonitor Database Version Compatibility

DriveMonitor historically shipped with multiple firmware databases. Two versions encountered in service are v1.2 and v1.3. Engineers attempting to build a new database from scratch inside DriveMonitor often see the build fail at the very last step ("Database generation failed at step N of N"). This is typically caused by:

• A read-only file attribute on the working folder.
• Antivirus / Windows Controlled Folder Access blocking the binary write.
• Mixing firmware images from different drive families (FC vs VC) inside one build.
• Insufficient user rights to write to C:\Program Files (x86)\Siemens\DriveMonitor\....

The recommended workflow is to never build a database from scratch in the field. Instead, obtain the pre-built database from Siemens Support (matching the CUVC firmware printed on the drive), copy it into the DriveMonitor database folder (typically ...\DriveMonitor\DB), restart DriveMonitor, and select the new database via "Extras → Select database".

Firmware Identification and Parameter Set Boundaries

The CUVC firmware version is displayed on the PMU keypad at power-up (two-digit firmware version code) and printed on the EPROM/Flash label on the CUVC PCB. The parameter set is split into functional groups used for both online editing and offline conversion:

During FC1 → CUVC conversion, DriveMonitor emits a conversion report listing every parameter that mapped to a new index. Parameters in the P800+ free-function-block range almost always require manual review because FFB programming is not auto-translatable.

Common Fault Codes on FC Chassis Drives After Migration

Verification Checklist After FC1 → CUVC Conversion

1. PMU keypad shows the expected firmware version after power-up.
2. Drive status is "Ready" (r000 = 0.0 Hz, r001 = 0 V, status word bit "Operation enabled" = 0).
3. All parameters listed in the DriveMonitor conversion report are at the expected values.
4. Open-loop test: command a small setpoint via PMU (P060 = PMU, P100 = 0 or 1). Motor ramps correctly.
5. Closed-loop test (if used): run automatic motor identification P115 = 1 with the motor uncoupled if possible; verify motor nameplate values match P200 – P209.
6. Fieldbus test: from the PLC, send a control word 0x047E → 0x047F and verify status word response, then 0x047F → enable.
7. Fault simulation: trigger a controlled stop via emergency-off circuit and verify STO behavior.
8. Backup the new parameter file from CUVC and store it off-drive (DriveMonitor upload + save as *.dnx with timestamp).

Troubleshooting Matrix

Long-Term Spares and Migration Path

The MASTERDRIVES FC platform is no longer in active production. Siemens' recommended successor for the FC chassis line is the SINAMICS G120 / G130 / G150 / S120 family. Field engineers planning a full migration should:

1. Use the conversion guides Siemens published to map FC1 / CUVC parameters to SINAMICS parameters.
2. Verify mechanical mounting adapters (Siemens offered chassis-mount adapter plates for several common FC frame sizes into SINAMICS G150).
3. Replace any remaining CU1/CB1 stock with CUVC/CBP only as a bridge solution — plan the SINAMICS migration within the next major maintenance window.
4. Maintain a parameter-file archive (DNX format) of every FC/CUVC drive in service for as long as the drive remains installed, so a SINAMICS migration can use the parameter file as a starting reference.

FAQ