SIMOVERT Master Drives Family Overview
Siemens SIMOVERT Master Drives (commercial type designation 6SE70 series) are three-phase AC drive converters that have been deployed across industrial automation since the 1990s. The family is built on a common inverter power section, DC-link bus, and precharge/regeneration hardware. What changes between the operating modes of the family is the firmware personality that runs on the control card, the control card itself, and the way the drive closes the current loop around the motor. Two dominant operating modes exist in the Master Drives family: Vector Control (VC) and Motion Control (MC). Both are field-oriented, both use PWM IGBT output stages, and both are wired to three-phase stator windings, but the engineering intent, default parameter sets, encoder interfaces, and torque-loop behavior diverge significantly.
Vector Control (VC) is engineered for squirrel-cage induction motors. It uses the CUVC control board. The drive maintains a decoupled flux-producing current (id) and torque-producing current (iq) reference frame, executes high-bandwidth current control, and exposes torque, speed, and process-level interfaces for general industrial loads. It is the default choice for pumps, fans, conveyors, mixers, extruders, and similar applications where induction-motor behavior, robustness, and moderate dynamic response are required.
Motion Control (MC) is engineered for servo applications. It uses the CUMC control board. The drive is delivered with a parameter set, encoder-evaluation logic, and position-loop firmware that is tailored to permanent-magnet synchronous servo motors. MC is also offered in two hardware formats: as a self-contained converter (rectifier + DC link + inverter) and as an inverter module that is fed from a shared DC bus. The inverter-module form factor allows multi-axis servo clusters where several CUMC-equipped inverters share a common rectifier and braking unit.
6SE7021-0TP60 and 6SE7021-0TP50) share a chassis, an IGBT module, a DC-link capacitor bank, and a cooling arrangement, but the personality they boot into is fundamentally different.
Part Number Decoding: 6SE7021-0TP60 vs 6SE7021-0TP50
The Siemens 6SE70 type designation is a structured alphanumeric code. Decoding it correctly is the first step toward understanding whether a substitute is mechanically, electrically, and firmware-compatible. The relevant components for this discussion are summarized below.
| MLFB segment | Meaning (general Siemens convention) | Source-confirmed role |
|---|---|---|
6SE70 |
SIMOVERT Master Drives product family | Common to all Master Drives units |
21 |
Frame size / power-range identifier | Same frame size for both units discussed |
0TP50 |
Variant suffix: Motion Control (MC) | Carries CUMC control card |
0TP60 |
Variant suffix: Vector Control (VC) | Carries CUVC control card |
The variant suffix is the field on which the engineering difference pivots. The first three characters of the suffix identify the operating mode, the firmware load, and the control-card hardware expected at first power-up. Two drives of identical power rating but different suffix are, for commissioning purposes, different products.
When ordering a replacement, always quote the full MLFB (Maschinenlesbare Fabrikate-Bezeichnung, the machine-readable product designation). Specifying only the frame size will not be sufficient to disambiguate VC from MC, and will frequently result in the wrong control card being shipped.
Control Card Architecture: CUVC vs CUMC
Both control cards are plug-in electronics boards that mount on the Master Drives chassis and execute the closed-loop regulation. The chassis provides the same connector pinout for analog and digital I/O, encoder feedback, serial interface, and Profibus/USS option slot, but the firmware and the active signal paths on each card differ.
CUVC — Vector Control card
The CUVC board implements field-oriented control for induction motors. It evaluates encoder feedback (where fitted) to derive rotor position and speed, executes the Park/Clarke transformation, and maintains a high-bandwidth current loop with sampling times that are short enough to support the dynamic torque build-up described in Siemens application literature. The board's parameter tree is organized around induction-motor equivalents: stator resistance, rotor resistance, magnetizing reactance, leakage reactance, and rotor time constant. Auto-tuning routines shipped with CUVC walk the user through a no-rotation and a rotating identification cycle to extract these values from the connected motor.
CUMC — Motion Control card
The CUMC board implements field-oriented control for permanent-magnet synchronous servo motors. It includes high-resolution encoder evaluation paths for servo-grade feedback devices (typically sine/cosine encoders with commutation track), an internal position loop, and a parameter set oriented around the equivalent circuit of a permanent-magnet machine. The board can also operate as an inverter module in a multi-axis DC-bus configuration, with the DC link fed from a parallel rectifier or from another converter. CUMC firmware expects encoder feedback by default, because the rotor position is required to align the stator field with the magnet axis for every electrical cycle.
| Attribute | CUVC (VC) | CUMC (MC) |
|---|---|---|
| Default motor type | Squirrel-cage induction | Permanent-magnet synchronous servo |
| Encoder feedback | Optional (sensorless vector supported) | Expected (high-resolution required) |
| Position loop | External / not standard | Integrated on the card |
| Module form factor | Converter (rectifier + inverter) | Converter and inverter module |
| Auto-tuning model | Induction-motor equivalent circuit | PM-motor equivalent circuit with saturation |
| Configuration recognition | Drive detects board at boot | Drive detects board at boot |
Vector Control (VC) Operating Principle
Vector control separates stator current into two orthogonal components in the rotor-flux reference frame: a flux-producing component (id) and a torque-producing component (iq). The Master Drives VC implementation is described in Siemens application documentation as a fast current-injection scheme with short sampling times, which in turn allows a highly dynamic build-up of torque. The bandwidth of the inner current loop is high enough to serve as the foundation of higher-level speed and position loops hosted on a supervisory controller, on a SIMATIC S7, or on the drive's own speed regulator.
In practical terms, an induction motor running on a CUVC-equipped Master Drive exhibits:
- Fast torque response to step load changes, with the current loop closing in a small number of PWM cycles.
- Stable operation down to low speeds, including near-zero speed with encoder feedback (closed-loop vector) or with sensorless estimation in less demanding applications.
- Decoupling between flux and torque, which simplifies tuning — the flux reference is set once based on motor nameplate voltage, and the torque reference is the only dynamic setpoint the speed regulator needs to manipulate.
- A parameter tree organized around the induction-motor equivalent circuit, with explicit entries for stator resistance, rotor resistance, magnetizing inductance, and rotor time constant.
The benefit of the high current-loop bandwidth is that any speed or position loop layered on top of the VC drive inherits a fast torque path. For most industrial applications, this dynamic class is more than adequate and avoids the cost and complexity of a true servo system.
Motion Control (MC) Operating Principle
Motion Control, as Siemens defines the term for the Master Drives family, is the control functionality tailored to the demands of servo-drive engineering using special servo motors. The CUMC board extends the field-oriented concept with hardware and firmware that is purpose-built for permanent-magnet synchronous machines. Two features that distinguish MC from VC in practice:
- Encoder-first operation. The control loop relies on continuous, high-resolution rotor position feedback. The encoder channel on the CUMC card is dimensioned for sine/cosine encoders and resolver feedback, and the commutation angle is updated every current-loop cycle. Sensorless operation is not a typical MC use case.
- Integrated position loop. The card itself can close a position loop around a position setpoint. The Master Drive thus behaves as a complete single-axis positioning controller, not just a torque/speed actuator. The CUMC also accepts higher-level motion profiles from a SIMOTION controller or a SIMATIC S7 with FM/CPU-side motion blocks.
MC firmware is available on the CUMC board in both converter form (self-contained drive with its own rectifier) and inverter-module form (DC bus fed externally). The inverter-module variant is the building block of multi-axis systems: one active line module supplies the DC bus, and several CUMC inverter modules close individual position/speed loops around their respective servo motors. This architecture is the conceptual ancestor of today's SINAMICS S120 multi-axis drive system.
Direct Replacement Feasibility Analysis
The original engineering question was whether a SIMOVERT Master Drive VC (6SE7021-0TP60) can be directly swapped for a SIMOVERT Master Drive MC (6SE7021-0TP50) when no VC spare is available. The answer is governed by the control card.
| Substitution aspect | VC → MC swap result | Comment |
|---|---|---|
| Mechanical fit | Likely compatible | Same frame size, same mounting footprint, same power section |
| Power-section compatibility | Compatible | IGBT module, DC link, gate drives are shared hardware |
| Control card type | Incompatible (CUVC ≠ CUMC) | Drive will detect mismatch at boot |
| Parameter set | Incompatible | VC and MC parameter trees are different structures; a parameter download from a VC commissioning will not load on a CUMC board |
| Motor type | Incompatible | MC firmware assumes PM synchronous machine, not induction motor |
| Encoder feedback | Required for MC, optional for VC | An induction motor without an encoder may not be controllable on CUMC |
The mechanical and electrical fit of the power stage do not, by themselves, validate a swap. The control card difference is the disqualifying condition. A drive that boots, detects a CUMC card where the firmware and parameter set expect a CUVC card, will either refuse to leave the startup state or will fault during the first run-up attempt. A parameter download from the original VC commissioning into an MC unit will, in most cases, load only a subset of compatible parameters and will leave the operating-mode-dependent parameters at defaults that are not appropriate for the motor on the shaft.
The correct response to a missing VC spare is therefore not to substitute an MC unit. The correct responses are, in order of preference: source a like-for-like 6SE7021-0TP60 spare; explore a Siemens-supported retrofit path; or migrate the affected axis to a current-platform drive (see Migration section).
Parameter and Function Block Differences
The two control cards expose different parameter trees. The parameter numbers overlap in the low ranges (drive identification, ramp-function generator, basic setpoint source) but diverge in the higher ranges that are specific to the operating mode. Typical divergence points include:
| Parameter class | VC firmware (CUVC) | MC firmware (CUMC) |
|---|---|---|
| Motor model parameters | Induction-machine equivalent circuit (Rs, Rr, Lm, Lσ, Tr) | PM-machine equivalent circuit (Ld, Lq, ke, J, Tach) |
| Current model | Rotor-flux model with current injection | Magnet-aligned model with encoder-based commutation |
| Speed/position loop | Speed loop standard; position loop external | Speed and position loops integrated on the card |
| Ramp-function generator | Standard ramps with rounding | Standard ramps with additional jerk limiting for motion profiles |
| Auto-tuning | Standstill and rotating identification of induction parameters | Encoder alignment and PM-motor identification |
| Brake-control logic | Standard motor holding brake sequence | Same module plus motion-specific sequencing |
Function-block diagrams internal to the firmware also differ. The MC build includes a position controller block, a feed-forward path, and interpolation buffers that are not present in the VC build. The VC build, in turn, includes sensorless-speed estimation blocks that are not relevant for the encoder-first MC operating mode.
Migration Path to SINAMICS Platform
As the SIMOVERT Master Drives family reaches end-of-life, the long-term migration target is the SINAMICS platform. Siemens offers migration kits and adapted parameter sets that map Master Drives parameter numbers to SINAMICS parameter numbers, easing the transition for plants that have dozens of Master Drives in service. The relevant SINAMICS families for a Master Drives retrofit are:
| Master Drives origin | Recommended SINAMICS replacement | Form factor |
|---|---|---|
| VC (induction motor, general industrial) | SINAMICS G120 / G120C / G120P | Modular / single-axis converter |
| MC (servo motor, motion) | SINAMICS S110 / S120 | Single-axis or multi-axis inverter |
| MC inverter module in DC-bus cluster | SINAMICS S120 (booksize / chassis format) | Multi-axis with shared Active Line Module |
The migration is not a one-to-one screw-terminal swap. A SINAMICS replacement typically requires new parameterization, new encoder cables (or adapters where the existing cable can be re-terminated), and a verification run before the production line is recommissioned. The cost of a migration is usually less than the cumulative risk of holding a growing inventory of obsolete Master Drives spares, and it also resolves the long-term spare-parts availability issue.
For users who must keep Master Drives in service during a transition, the recommended interim strategy is to maintain a rotating spare pool of tested units, paired with a documented replacement procedure, and to engage a Siemens service organization for repair of failed units where local service coverage exists. Where local service coverage is limited, the practical options narrow to either a structured migration to SINAMICS or to a last-time-buy of Master Drives spares while they remain available in the channel.
Diagnostic Behavior and Fault Codes
When a Master Drive is asked to run in an operating mode for which its control card is not configured, the drive reports a configuration or parameterization fault. Specific fault numbers vary by firmware version, but the categories are stable. The table below lists the most frequently encountered fault families relevant to a VC/MC mismatch.
| Fault number (typical) | Text | Trigger condition | Resolution |
|---|---|---|---|
| F001 | Overcurrent | Output stage overcurrent trip | Check motor connection, encoder wiring, and motor parameters |
| F002 | DC-link overvoltage | Regenerative energy exceeded braking capacity | Verify braking resistor sizing, ramp-down rate, and supply conditions |
| F015 | Motor identification not performed | Auto-tuning has not been completed | Run motor identification cycle appropriate for the connected motor type |
| F019 | Motor stator resistance identification failed | Standstill measurement out of range | Verify motor wiring, nameplate data entry, and motor isolation |
| F035 | Parameter error / configuration error | Parameter set inconsistent with detected control card | Reload correct firmware/parameter set for the installed control card |
| F080 | Control card initialization failed | Firmware/board mismatch or board not seated | Reseat control card; verify MLFB and firmware version match |
| F082 | Encoder fault | Encoder signal lost or out of tolerance | Check encoder cable, shield grounding, and encoder supply voltage |
On a Master Drive that has been misconfigured for the wrong control card, F035 and F080 are the most common faults. The drive can usually still be interrogated with the parameterization tool (DriveMonitor on a PC, or SimoCom U for older units) when the unit is in a fault state, but it will not enter the run state until the configuration is corrected. The fault buffer is non-volatile and survives power cycles, which is useful for post-incident diagnosis.
Commissioning and Verification Procedure
Whether commissioning a like-for-like replacement, a control-card-level repair, or a SINAMICS migration, the verification procedure follows a stable pattern. The sequence below is the recommended field procedure for any Master Drive swap on a controlled motor axis.
- Confirm the MLFB. The replacement unit must match the original MLFB, including the variant suffix, before power is applied. Mismatches at this stage create the faults discussed above.
- Verify mechanical installation. Mounting footprint, cooling airflow, and DC-bus connections (if the unit is part of a multi-axis cluster) must match the original installation. A drive that physically fits but is wired for a different bus role will misbehave on first power-up.
- Verify the control card. With the drive de-energized and isolated, open the control-card compartment and confirm visually that the board type (CUVC vs CUMC) matches the MLFB. The board is usually marked with its type designation in clear text on the front panel.
- Connect the parameterization tool. Use DriveMonitor (or SimoCom U for older firmware) over the serial service interface or over Profibus, depending on the option fitted. Read the parameter set currently in the drive and confirm that the operating-mode parameters match the expected variant.
- Download the commissioning parameters. Load the parameter file from the original drive. Confirm that no parameter errors are reported during the download. The tool will list any rejected parameters; investigate each rejection before continuing.
- Run the motor identification cycle. With the motor decoupled from the load where possible, run the standstill (and rotating, where required) identification sequence appropriate for the operating mode. The drive will measure the equivalent-circuit parameters of the connected motor and store them in non-volatile memory.
- Verify the run command path. With the motor still decoupled, issue a low-speed run command from the controlling PLC. Confirm that the encoder feedback (if fitted) is in the correct direction, that the speed setpoint is being followed, and that no fault is raised.
- Verify the load response. Re-couple the motor to the load and run the axis through a representative duty cycle. Verify that the current loop, speed loop, and any position loop behave as expected. Watch for nuisance faults, encoder warnings, or unusual current draw.
- Sign off and update documentation. Record the unit serial number, the firmware version in service, the parameter file used, and the date of commissioning. A migrated drive is only as maintainable as the documentation that travels with it.
Each step has a verification check; if any verification check fails, the procedure halts and the failure is investigated before the next step. This is especially important for a fleet of 30 Master Drives, where a single bad commissioning can propagate to spare-pool units that have not yet been deployed.
Field-Engineering Recommendations and Spares Strategy
For a plant operating a fleet of approximately 30 SIMOVERT Master Drive VC units on induction motors in vector control, the engineering recommendation depends on the long-term life expectancy of the driven process. A small fleet where the process is expected to remain in service for many years warrants a structured migration plan; a fleet near end-of-life can often be sustained by a smaller spare pool and a repair contract.
| Plant profile | Recommended strategy | Notes |
|---|---|---|
| Process in service 10+ years, spare availability declining | Plan a phased migration to SINAMICS, axis by axis | Order long-lead replacement drives before they are needed |
| Process near end-of-life, 1-3 years of remaining service | Maintain a small spare pool of tested VC units | Stock at least one unit per unique MLFB |
| Process mid-life, no immediate migration budget | Engage a repair service for failed units; explore last-time-buy options | Document the contract terms and turnaround time |
| Process in a region without local Siemens service | Stock a higher fraction of spares, including control cards and IGBT modules | Consider training in-house technicians on the parameterization tools |
The temptation to substitute an MC unit into a VC slot is a symptom of a wider spare-availability problem. The correct resolution is not the substitution; it is a structured look at the spare-pool policy, the repair options, and the long-term migration plan. A drive fleet of 30 units on a process with high downtime cost is large enough to justify a planned migration, and the SINAMICS G120/S120 platforms are the engineered replacement for the Master Drives VC and MC families respectively.
For users without local Siemens service coverage, the practical interim measures are: build a tested-spare pool, hold critical sub-assemblies (control cards, IGBT modules, fans, DC-link capacitors) where the channel allows, and document the parameter files for every drive on the plant. With those measures in place, a Master Drives VC fleet remains maintainable for the remainder of its service life, and a staged migration to SINAMICS can proceed at the rate the maintenance budget allows.
Frequently Asked Questions
Can a SIMOVERT Master Drive MC replace a VC unit on an induction motor?
No. The MC variant carries a CUMC control card that is firmware- and parameter-configured for permanent-magnet synchronous servo motors. The drive's configuration recognition will detect a control-card mismatch, and the MC firmware expects encoder-based commutation that is not available on a sensorless induction-motor installation. The mechanical and electrical fit of the power section is not sufficient to validate a swap.
What control card is fitted in a 6SE7021-0TP60 vs a 6SE7021-0TP50?
The 6SE7021-0TP60 (VC) is fitted with a CUVC control card. The 6SE7021-0TP50 (MC) is fitted with a CUMC control card. The cards are not interchangeable: the VC firmware will not run on a CUMC card, and the MC firmware will not run on a CUVC card.
What is the main difference between Vector Control and Motion Control in Master Drives?
Vector Control is the general-purpose field-oriented mode for induction motors, with a fast current-injection scheme, short current-loop sampling times, and a dynamic torque build-up suitable as the basis for higher-level closed loops. Motion Control is the servo-engineered mode, with high-resolution encoder feedback, an integrated position loop, and a parameter set optimized for permanent-magnet synchronous servo motors. MC is also available in inverter-module form for multi-axis DC-bus configurations.
Can the parameter file from a VC drive be loaded onto an MC unit?
Not as a like-for-like replacement. The parameter trees differ: VC firmware uses induction-motor equivalent-circuit parameters (stator resistance, rotor resistance, magnetizing inductance, rotor time constant), while MC firmware uses PM-motor parameters (Ld, Lq, EMF constant, inertia). A cross-load will typically trigger a parameter-error fault during download and will not produce a running drive.
What is the recommended modern replacement for a SIMOVERT Master Drives fleet?
VC applications on induction motors are best replaced with SINAMICS G120, G120C, or G120P. MC applications on servo motors are best replaced with SINAMICS S110 or S120, with the S120 platform supporting the same multi-axis DC-bus architecture that the MC inverter-module form factor offered. Siemens provides migration documentation and parameter-mapping tools to ease the transition.