Converting MASTERDRIVE VC VCD Files: Simovis to DriveMonitor

Converting MASTERDRIVE VC VCD Backup Files: Simovis to DriveMonitor Workflow

Engineers retiring 1990s-era Siemens MASTERDRIVE VC (Vector Control) drives frequently inherit the original commissioning records as VCD-format backup files. The original Simovis DOS commissioning tool is the only software that can natively read these files, and DriveMonitor — the Windows successor — cannot open them directly. The practical recovery path is therefore a two-stage process: load the VCD/XXD backup into Simovis (DOS), run the converter utility that shipped on the original MASTERDRIVE product CD, then open the resulting binary file in DriveMonitor to view, edit, or migrate the parameter set into a SINAMICS replacement.

This document captures the file-format chain, the conversion procedure, the parameter-numbering conventions used in the ASCII dump, the troubleshooting matrix, and the migration path to the SINAMICS platform, with verified Siemens references for legacy support. For background on the active SINAMICS platform, see the Siemens SINAMICS drives portfolio; for legacy support inquiries, contact Siemens Industry Online Support with the 6SE70 order number of the drive.

1. MASTERDRIVE VC Product Background

MASTERDRIVE VC is a member of the SIMOVERT MASTER DRIVES family (6SE70 / 6SE71 series) released by Siemens in the early 1990s. The "VC" suffix distinguishes the Vector Control firmware from the older FC (Frequency Control / V/f) and SC (Servo Control) firmware variants running on the same hardware platform. VC firmware closed-loop controls the rotor flux and torque-producing current components independently, which made it the preferred choice for demanding applications such as paper machines, wire-rod mills, hoists, winders, extruders, and high-inertia centrifuges.

The hardware platform remained compatible with FC and SC firmware via parameter P060 (firmware selection) throughout the product life. MASTERDRIVE VC reached phase-out status in 2014 with active spare-part support continuing regionally and migration paths into SINAMICS G120 (book-format general purpose), G130 / G150 (chassis / cabinet high-power), or S120 (high-performance servo / vector) platforms depending on the application profile. Because the product is formally out of production, the original commissioning software is no longer bundled with new drives and must be retrieved from archived media or Siemens legacy support.

Key order-number ranges for the family:

MASTERDRIVE VC firmware introduced high-resolution field-oriented control and supported multiple encoder interfaces (resolver, HTL, TTL, SSI). Communication options included PROFIBUS DP per IEC 61158, USS over RS485, peer-to-peer SIMOLINK fiber ring, and CAN option modules. The default parameter set is stored on the EPROM / flash card and may be backed up via DriveMonitor (binary), Simovis (XXD text), or directly to the operator panel OP1S / OP2 as a VCD dump.

2. Backup File Format Chain Across Three Eras

MASTERDRIVE backup files exist in three distinct formats that match the commissioning tool that produced them. Knowing the format determines which software can read the file.

The VCD format is a human-readable ASCII dump. The first several lines are a header containing the drive order number, firmware version, commissioning date, and the operator-panel / commissioning-tool identifier. Following the header, each parameter occupies one line in the form:

P060 = 5
P100 = 50.00
P107 = 0.400
P383 = 10.00
r003 = 0
r028 = 12.7
B0010 = 0
K0001 = 0.00
n001 = 3.20
END_HEADER
P050 = 380
P051 = 7.40
P052 = 47.0
P053 = 50.00
P054 = 2900

The parameter number is followed by an equals sign and the parameter value in its native engineering units (not raw counts). Read-only diagnostic parameters (r-numbers) appear in the same layout. Because the encoding is ASCII, the file can be opened with Notepad and scanned line-by-line, but interpreting the values still requires cross-reference against the MASTERDRIVE parameter list (parameter manual, edition determined by the firmware revision recorded in n001).

Header Block Anatomy

The header block of a VCD file typically contains:

• Line 1: File magic, e.g. VCD_VER=1.0
• Line 2: Order number, e.g. ORDER=6SE7016-1EA61
• Line 3: Firmware revision, e.g. FW=3.20
• Line 4: Commissioning date, e.g. DATE=1998-04-12
• Line 5: Source tool, e.g. TOOL=OP2 or TOOL=SIMOVIS_1.30
• Line 6: Operator name, often blank in panel-dumped files
• Line 7: Project identifier, customer-defined
• Line 8: Separator, e.g. END_HEADER

After END_HEADER, the file is a flat list of parameter = value lines. Read-only diagnostics are usually included by default, although the OP1S / OP2 panels allow a slimmed dump that excludes r-numbers to save memory. When troubleshooting an old backup, the most efficient first step is to verify the header is intact: corrupted or missing header lines will cause Simovis and the conversion utility to reject the file or, worse, silently misidentify the drive variant.

3. Simovis (DOS): Original Commissioning Tool

Simovis is the DOS-based commissioning tool Siemens supplied with the earliest MASTERDRIVE units. It predates DriveMonitor and was distributed on floppy disk and later on the same CD that contained the drive firmware, parameter list, and the conversion utility described in Section 4.

Functionally, Simovis can:

• Open XXD and VCD backups
• Edit parameter values, binector/connector wiring, and function-block configuration
• Download parameter sets to the drive via RS232 serial interface (drive side: OP1S / OP2 port or the X500 programming interface)
• Upload from drive to file
• Compare current parameters against a stored reference set
• Print parameter reports on dot-matrix and laser printers (LPT1)

Simovis requires an MS-DOS environment or a Windows 9x/NT DOS prompt running in real mode. Under modern 64-bit Windows, Simovis cannot be launched natively; users run it inside DOSBox or a virtual machine with FreeDOS. The tool does not require a hardware dongle. The installation footprint is roughly 4 MB on disk, with the runtime executable SIMOVIS.EXE and supporting drivers. Communication with the drive uses direct serial I/O on COM1 / COM2 at 9600 or 19200 baud, 8N1.

Original Siemens documentation describing Simovis operation was distributed as the "Simovis for MASTERDRIVES Operating Instructions" manual, included on the product CD alongside the parameter list. The same CD also contained a small command-line conversion utility capable of translating XXD / VCD dumps into the binary format DriveMonitor accepts.

4. Converting XXD / VCD Files to DriveMonitor Format

The conversion utility on the original MASTERDRIVE product CD is the bridge between Simovis-era backups and the modern DriveMonitor toolchain. The procedure is deterministic and takes a few minutes of operator time.

Prerequisites

• XXD or VCD backup file from the original commissioning
• Simovis (DOS) installed locally or running in DOSBox / FreeDOS VM
• Conversion utility (commonly XXD2DRV.EXE; bundled with the MASTERDRIVE product CD in a TOOLS\ subdirectory)
• DriveMonitor or DriveMonitor ES installed on a Windows host

Procedure

1. Copy the XXD / VCD file into the working directory of Simovis.
2. Launch Simovis and verify the file opens without error. If Simovis reports an unrecognized header, check the first lines for drive-order consistency — Simovis uses the order number to determine the parameter subset to expose.
3. From the Simovis file menu, export the loaded parameter set to the conversion utility's input format. Earlier revisions used the binary ".dmp" intermediate; later revisions used a renamed XXD.
4. Run the conversion utility from the command line: C:\MASTERDV>XXD2DRV input.xxd output.drv The utility emits a binary file consumable by DriveMonitor. Some utility revisions use the syntax XXD2DRV /I=input.xxd /O=output.drv.
5. Launch DriveMonitor and open File → Open → Parameter Set. Navigate to the converted file.
6. DriveMonitor will display a warning dialog stating that no drive type is selected. Click OK to dismiss.
7. From the Drive menu, select Select Drive Type and pick the matching 6SE70 / 6SE71 order number from the catalog. DriveMonitor then loads the parameter subset appropriate to the selected drive.
8. Cross-check critical parameters — P060 (firmware selection), P100 / P101 (control mode), P383 (motor encoder type), and P452 / P453 (PROFIBUS node address and baud) — against the original commissioning record to confirm the conversion preserved the intended values.
9. Save the project under a new filename to avoid overwriting the converted artifact.

If the conversion utility rejects the file with an "unrecognized firmware version" message, the parameter list inside the file references a VC firmware release (e.g., 2.xx or 3.xx) that the utility's catalog does not include. Updating the utility from a later MASTERDRIVE CD or asking Siemens legacy support for the most recent version usually resolves this.

Workflow Diagram

5. Manual Parameter Extraction from ASCII VCD Files

When neither Simovis nor the conversion utility is available, the VCD file can still be read with a text editor and cross-referenced against the parameter manual. This is slower but feasible for parameter subsets that need to be transplanted into a SINAMICS migration project.

Recommended workflow:

1. Open the VCD file in any text editor. The header block typically ends with the line END_HEADER or a separator of dashes.
2. Identify the firmware version line (e.g., FW=3.20). It identifies which parameter manual edition to load.
3. Filter on the parameter groups of interest using the editor's Find function. Common groups during a SINAMICS migration:
   • P050 – P099: Motor data (rated voltage, current, power, cos φ, speed)
   • P100 – P199: Setpoint / control configuration (control mode, ramp-function generator)
   • P200 – P299: Power section / pulse pattern
   • P300 – P399: Encoder interfaces
   • P400 – P499: Communication (PROFIBUS, USS, SIMOLINK)
   • P500 – P599: Function-block free blocks
   • P600 – P699: Diagnostics / fault memory
   • P700 – P799: Technology controller / supplementary functions
   • P800 – P899: Drive-specific special functions
   • P900 – P999: Parameter-set management, parameter copy
4. For each parameter of interest, write down the parameter number and value. Use a spreadsheet to keep the inventory.
5. Cross-check parameter attributes (minimum, maximum, factory default) in the parameter manual. The VCD dump records only the present value; limits must be looked up.
6. Identify binector-to-connector wiring lines if the file contains them (entries of the form B0xxx = KK0yyy). These describe the free-function-block logic and cannot be migrated automatically to SINAMICS — they must be re-implemented in SINAMICS free blocks or DCC.
7. Verify parameter-modulo values for arrayed parameters. VCD files from OP1S panels sometimes truncate sub-indices greater than 99. If sub-index 7 of a 16-element array is missing, the file may have been truncated by panel memory limits — not corrupted.

6. MASTERDRIVE Parameter Numbering Scheme

MASTERDRIVE parameters follow a structured numbering scheme. Knowing the scheme lets you navigate the parameter list quickly even without the tool.

Parameter indices use a four-digit base number with a two-digit sub-index for arrayed parameters. For example, P100.01 and P100.02 are two indices of parameter P100. The VCD dump displays arrayed parameters on consecutive lines with the same base number and different sub-indices:

P100.01 = 5
P100.02 = 50.00
P100.03 = 380

The P-prefix parameter number is also the addressing scheme used by PROFIBUS DPV1 parameter-access telegrams. P-numbers and r-numbers are mapped onto PROFIBUS slot / index by a fixed offset table published in the MASTERDRIVE PROFIBUS manual. When migrating to SINAMICS, the PROFIBUS GSD file provides the new slot / index mapping.

7. Migration to SINAMICS Drives

MASTERDRIVE VC migrations target the SINAMICS G120 (book-format low-voltage general purpose), G130 / G150 (chassis / cabinet low-voltage high-power), or S120 (high-performance servo / vector) families. Parameter values are not portable one-to-one: the SINAMICS parameter numbering, parameter-set layout, and free-function-block engine are different.

Siemens provides migration support through:

• SINAMICS Support Tools: a Windows utility that imports DriveMonitor binary parameter sets from MASTERDRIVE and proposes equivalent SINAMICS parameters based on a catalog table. The user manually reviews the proposed mapping.
• SINAMICS Drive Control Chart (DCC): a graphical editor replaces MASTERDRIVE free-function blocks with DCC blocks. DCC charts run inside the SINAMICS Control Unit and are stored as part of the project.
• Application engineering services: for complex MASTERDRIVE applications (e.g., sectional drives with dancer / load-cell control), Siemens application engineering produces a per-machine parameter list. Local Siemens representatives coordinate this engagement.

The parameter groups most frequently migrated to SINAMICS:

Binector-to-connector wiring in MASTERDRIVE does not migrate directly; each link must be re-implemented as a SINAMICS free block, DCC chart, or PLC-side wiring. Where the customer has the original PLC program (e.g., STEP 7 / TIA Portal), the PLC may already encapsulate the binector logic, and the drive migration reduces to a parameter-block transplant.

The SINAMICS STARTER commissioning tool or the TIA Portal Startdrive add-on accepts the converted DriveMonitor binary through the Migrate MASTERDRIVE project menu. The migration wizard maps known parameter equivalents and flags un-mappable entries for manual review. Plan for a 30% to 50% effort overhead on top of the actual drive swap for engineering, verification runs, and customer FAT.

8. Sourcing Legacy MASTERDRIVE Software

Simovis and the original conversion utility are no longer distributed through Siemens public download portals because the product is in phase-out status. Practical sourcing paths:

1. Original CD: archived customer CDs from the original commissioning, often retained by the maintenance department. The CD label identifies firmware version and includes Simovis plus the conversion utility in a TOOLS\ subdirectory. Look for files dated 1996 – 2003 in the CD root.
2. Siemens regional representative: for active phase-out products, regional support organizations maintain a small library of legacy tools. Contact the local Siemens Industry Online Support representative with the drive order number and request the latest MASTERDRIVE commissioning toolkit.
3. Siemens Industry Online Support Knowledge Base: keyword search "MASTERDRIVE Simovis" or "6SE70 commissioning tool" surfaces Siemens-authored entries that may include an attached archive. Attachments are gated by Siemens Industry Online Support registration but are free to access with a registered account.
4. Siemens regional spare-parts CD: certain regional Siemens spare-parts CDs bundled a complete MASTERDRIVE commissioning environment including Simovis and the DriveMonitor binary import filter.

For users with active support contracts, the most reliable path is to open a Siemens support request referencing the 6SE70 order number of the drive and the specific need (Simovis runtime, conversion utility, or DriveMonitor import filter). Response time under standard SLA is 5 – 10 business days; phase-out product support typically routes through regional application engineering rather than the central hotline. Have ready: drive order number, firmware revision (n001), serial number, and the file header of the VCD you need to convert.

9. RS232 Serial Interface Specifics

The MASTERDRIVE RS232 interface on OP1S / OP2 ports uses the following fixed settings; matching these in Simovis or any terminal emulator is required for parameter download.

Pinout of the OP1S / OP2 connector (X500) on MASTERDRIVE:

Pin 2: RXD (drive receives)
Pin 3: TXD (drive transmits)
Pin 5: GND
Pin 7: RTS (drive side, hard-wired to +V via internal pull-up)
Pin 8: CTS (drive side, hard-wired to GND via internal pull-down)

A standard null-modem cable works without modification. USB-to-RS232 adapters from FTDI or similar industrial-grade chipsets generally work; chipset-less cables (e.g., Prolific PL2303 clones) may stall at higher baud rates. Use a shielded cable in panels with VFD power sections to avoid noise pickup on the receive line.

10. PROFIBUS Communication Parameters

When the converted backup is destined for re-commissioning on a PROFIBUS-controlled drive, confirm the PROFIBUS parameters before energizing the bus:

SINAMICS uses the PROFIdrive profile (per IEC 61800-7) with telegram selection in p922 and node address in p918. Telegram 1 (standard) maps cleanly between MASTERDRIVE and SINAMICS for control word 1 and status word 1; telegrams 3 and 4 (additional setpoint / actual channels) require manual mapping review.

11. Troubleshooting Matrix

12. Verification Steps After Conversion

After completing the conversion, run a four-step verification to ensure the imported parameter set is safe to download into a replacement drive or to use as the source of a SINAMICS migration:

1. Firmware identity check: in DriveMonitor, confirm the firmware identifier (r060 / n001) matches the original commissioning record. Mismatched firmware leads to unexpected parameter omissions.
2. Motor data integrity check: compare P100 – P106 against the motor nameplate. The most common commissioning error is to copy motor data from one drive to another of different rating.
3. Encoder configuration check: P383 / P384 should match the connected encoder type. Loading a parameter set from a resolver-equipped drive onto a TTL-equipped drive (or vice versa) triggers fault F006 (encoder error) at first run.
4. Communication node check: P452 / P453 (PROFIBUS address and baud) must match the host PLC project; mismatched addresses cause PROFIBUS diagnostic alarms at startup.

13. Frequently Asked Questions