Scope of this technical record
A practical series-level entry for Siemens SIMOVERT MASTERDRIVES 6SE70 / 6SE71 Vector Control systems. It distinguishes device and cabinet configurations, provides the fault-to-circuit entry points most relevant to legacy service work, and routes users into DC-link, communication and output-stage records rather than treating the platform as a generic VFD.
SIMOVERT MASTERDRIVES equipment contains hazardous mains and stored DC-link energy. Isolation, discharge verification, electrical measurement and any replacement or commissioning operation must be carried out by qualified industrial-drive personnel using the correct Siemens documentation for the exact MLFB/type code.
Why MASTERDRIVES is a high-value legacy drive track
SIMOVERT MASTERDRIVES remains a technically demanding service subject because it appears in machine systems where the drive is part of a coordinated process rather than an isolated motor starter: web handling, cranes, steel and paper lines, test stands and multi-motor installations. The uploaded Siemens training material identifies these industrial use cases and presents the 6SE70/71 platform as a wide-power-range vector-control system.
For IndustrialDriveData, the value is not a copied manual directory. The value is mapping a technician’s real starting point—an F002 precharge trip, F006/F008 DC-link problem, F011 overcurrent event, lost communication or a 6SE70 type-code/drawing query—to the correct system boundary and evidence set.
System structure: 6SE70 device versus 6SE71 cabinet system
The source material separates 6SE70 devices from 6SE71 cabinet systems. A 6SE70 can be a frequency converter, rectifier, inverter, regenerative/rectifier element or a module in a shared DC system. When installed with line switching, contactors, filters, line reactors, output reactors and cabinet options, the resulting system context is commonly represented as 6SE71.
This distinction is diagnostic, not cosmetic. An AC-AC converter has an internal line-to-DC-to-output energy path. A DC-AC inverter fed from a common bus requires tracing an upstream rectifier/regenerative source and the behaviour of other connected axes. A trip caused by shared bus energy cannot be safely reduced to “replace inverter board.”
System configuration and diagnostic implication
| Configuration | What it means in service | Likely entry pages |
|---|---|---|
| AC-AC frequency converter | Line supply, internal DC link and inverter are investigated as one unit | F002 / F006 / F008 / F011 |
| DC-AC inverter on common DC bus | Upstream bus generation and peer drive behaviour can cause trips | DC-link and regenerative path |
| Rectifier / regenerative unit + inverter | Energy return and main-contactor/precharge logic matter | F006 / energy-path workflow |
| Cabinet system (6SE71 context) | External line-side and system options are part of diagnosis | Model/platform record |
Control and communication architecture
The uploaded material identifies CUVC as the control-board context for Vector Control and describes PMU/OP1S and DriveMonitor as parameterization interfaces. USS can serve local or upper-level serial communication, with OP1S using USS and CUVC COM2/X101 supporting system connection contexts. SIMOLINK is described as optical, deterministic process-data communication intended for coordinated MASTERDRIVES or controller-to-drive operation.
A communication failure must therefore be classified before hardware decisions are made. Loss of panel access over USS is not the same fault boundary as missing SIMOLINK exchange in a synchronized system. Where parameters or machine sequencing are valuable, recovering fault history and configuration evidence before board substitution may be worth far more than the replacement board alone.
Highest-value fault entry points
The initial fault set is deliberately narrow. F002 points into precharge and contactor/DC-link readiness; F006 and F008 reveal excessive or insufficient DC-link energy; F011 demands separation of motor/cable/load evidence from the inverter bridge and driver/status circuits. Siemens OEM documentation gives these fault names and directs investigations toward line voltage, rectifier/DC link, output short or earth fault and load conditions.
Each record connects a fault to a workflow and circuit path. This means a user searching a precise fault code reaches an actionable diagnostic structure without IndustrialDriveData pretending to replace OEM commissioning rules.
Fault-to-path routing
| Fault | Primary boundary | Next record |
|---|---|---|
| F002 Pre-charging fault | Supply / fuses / precharge / DC-link readiness | Precharge and DC-link workflow |
| F006 DC-link overvoltage | Supply or regenerative energy path | DC-link and regenerative path |
| F008 DC-link undervoltage | Line/rectifier/DC-link supply integrity | Precharge and DC-link workflow |
| F011 Overcurrent | Motor/cable versus output-stage/driver evidence | Output-stage workflow |
Lifecycle and commercial relevance
Siemens Industry Support currently identifies MASTERDRIVES items and CUVC/PSU1 records as spare-part/service information, while product notices state that production of certain CH I and CH II MASTERDRIVES replacement units was discontinued from April 30, 2023. That combination—installed equipment, repair evidence and narrowing replacement availability—creates a meaningful diagnostic and modernization use case.
A qualified inquiry should include full MLFB/type code, cabinet or common-bus arrangement, fault code and value, operating condition, control unit/options, any prior repair and photographs of labels. This is enough to distinguish a documentation request from a board-identification, repair or modernization opportunity.
How to decide which page to enter from the plant floor
A maintenance engineer rarely starts with a full schematic. They start with a production fact: the line cannot start after a power event, a winder trips when slowing, a shared DC system stops together, or an old cabinet has lost its operator and control communication. The database converts each fact into a narrow path. Startup inability belongs in precharge/DC-link readiness; motion-dependent bus trips belong in regenerative energy; output-stage protection belongs in motor/cable and driver isolation; lost parameter access belongs in CUVC and communications preservation.
This routing prevents two costly habits common in legacy-drive repair: reading hundreds of manual pages without knowing the affected subsystem, and changing expensive assemblies before the external or system-level cause is cleared. The system page therefore sits above the fault, board and circuit records and should be used to establish the machine topology before any parts decision.
Plant symptom routing
| Observed plant symptom | First page path | Required evidence |
|---|---|---|
| No enable after line energization | F002 / precharge workflow | Type code, supply and contactor sequence |
| Trip during deceleration or lowering | F006 / regenerative path | Motion event and DC-bus topology |
| Trip while accelerating or under torque | F011 / output-stage workflow | Fault value and motor/cable condition |
| Drive energized but system communication lost | Communications workflow | CUVC/options and network topology |
Publishing boundary and future expansion
The MASTERDRIVES track is intentionally built as a relationship database: system family, matched device/drawing set, fault, board area, circuit path and diagnostic procedure. It will not become a raw PDF archive. Public records explain verified relationships, cite OEM material where available and use redrawn or textual signal paths when internal diagram review adds value.
The next layer after these foundational pages should be exact MLFB and module records driven by evidence from real searches or enquiries: a user searching a 6SE7023 type code, a CUVC/PSU1 part number or an F011 event tied to a particular chassis. That sequencing avoids publishing hundreds of generic Siemens pages before the high-intent routes are proven.
Field record checklist
- Full Siemens MLFB/type code and unit arrangement
- Fault number and fault value before reset
- AC-AC, DC-AC or rectifier/regenerative/common-bus context
- CUVC/optional communications hardware and parameter backup status
- Evidence of prior board or power-stage replacement
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
OEM basis for system configuration, safety, terminals and fault/service context.
OEM parameterization, BICO, PMU/OP1S, DriveMonitor and faults/alarms reference.
Model records
Platform reference distinguishing standalone 6SE70 units from integrated 6SE71 cabinet systems, and mapping converter, inverter, rectifier/regenerative and common-DC-bus configurations to diagnostic work.
Editorial circuit-map entry based on identified 6SE7021, 6SE7022 and 6SE7023 schematic sets, used to organize auxiliary supply, DC-link, IGBT-drive and status/protection signal investigations without distributing original drawings.
Fault records
The drive does not complete DC-link precharge within the monitored period and prevents normal enable.
The MASTERDRIVES unit trips as the DC-link voltage rises above the permitted limit, often under regeneration or deceleration.
The drive disables pulses because DC-link voltage is below the permissible level for operation.
The drive trips on excessive current; the OEM fault value can indicate the affected U, V or W phase in supported units.
Circuit and diagnostic records
Maps the line-side or common-DC supply path through precharge and DC-link energy management to the inverter, with diagnostic relevance for F002, F006 and F008.
Organizes local parameterization, operator-panel communication and synchronous drive-system data exchange around CUVC, PMU/OP1S, USS, SIMOLINK and PROFIBUS-DP contexts.
Editorial map of visible circuit relationships in identified 6SE7021 and 6SE7023 drawings, including DC-link supply, auxiliary rails, IGBT switching, fan supply and current/load/temperature status signals.
A MASTERDRIVES system stops with F002, F006 or F008, or cannot progress safely from precharge to operation.
The unit reports F011 or a suspected output-stage current event after start, acceleration or previous module repair.
A legacy MASTERDRIVES unit cannot be parameterized reliably, communication is lost, or a synchronized drive system no longer exchanges expected data.