Siemens Masterdrives MC 6SE7015 Parameter Backup via DriveMonitor

Overview

The Siemens Masterdrives Motion Control (MC) inverter, order number 6SE7015-0EP50-ZC23+G91, is a 1.5 kW digital drive in the SIMOVERT MASTERDRIVES product family. A complete parameter backup is mandatory before any firmware update, hardware swap, or major commissioning change. Three parameter backup methods are available through the DriveMonitor service tool, each producing a different file type with different downstream uses. A fourth path - transparent PROFIBUS access via DriveES SIMATIC - is available when the drive is already networked to a SIMATIC S7 PLC.

This reference covers the cable selection, software configuration, the P060 menu parameter, all three DriveMonitor backup methods, and the PROFIBUS alternative. The serial cable for the Masterdrives MC is the Siemens part 9AK1012-1AA00, not the 6SE6400-1PC00-0AA0 that appears in some service notes (the latter is a USS cable for the MICROMASTER 4 / SINAMICS G120 line and is not mechanically or electrically compatible with the Masterdrives X300 socket).

Product Identification: 6SE7015-0EP50-ZC23+G91

The order number breaks down as follows. The base code 6SE7015 places the unit in the 6SE70 MASTERDRIVES family at 1.5 kW. The 0EP50 segment encodes the chassis form factor and the power-section key (line voltage class, cooling type, and physical size). The trailing ZC23 is a Z-order option code that integrates a fixed combination of features into the factory build. The +G91 suffix is a software/option designation that enables additional function groups in the parameter layout. In the Masterdrives MC product line, the +G91 option typically exposes the technology parameter range used for position control, synchronous operation, and electronic gearing - features that distinguish the MC variant from the Vector Control (VC) variant. The exact parameter range enabled by +G91 is firmware-version dependent; a current read-out is available at parameter P045 (control unit firmware version) and the option read-out parameters in the U950-U999 function group.

When ordering a replacement or a bench spare, the order number must be matched exactly. A 1.5 kW Masterdrives MC with +G91 is a different drive from a 1.5 kW Masterdrives VC without +G91, and the parameter backup file from one will not load on the other without manual parameter re-mapping.

Prerequisites

• Siemens Masterdrives MC 6SE7015-0EP50-ZC23+G91 with line voltage applied. The motor can remain connected; an upload is a read-only operation and will not start the drive.
• DriveMonitor software installed on a Windows engineering PC. DriveMonitor V5.4 SP3 or later is recommended for MASTERDRIVES firmware V1.x and V2.x. DriveMonitor V6.x ships as part of DriveES V6.x and includes the same drive-browse functionality plus S7 routing.
• Serial cable Siemens 9AK1012-1AA00 (PC RS-232 DB-9 to Masterdrives X300 DB-9).
• If the engineering PC has no DB-9 COM port, a USB-to-RS-232 DB-9 adapter (FTDI FT232-based recommended). USB-to-RS-485 adapters are not acceptable - the X300 port is RS-232 only.
• For PROFIBUS backup: DriveES SIMATIC V5.x or V6.x, a SIMATIC S7-300/400 CPU with an Ethernet (PN/CP) interface, a CBP2 (6SX7010-0FF05) or CBP (6SX7010-0FF00) PROFIBUS option on the drive, and the S7 routing table configured in STEP 7 / TIA Portal.
• Drive password (P061) known, or the drive returned to factory default (P061 = 0). The default at delivery is no password; if a password has been set, DriveMonitor will prompt for it before any read or write.

Serial Cable Selection: 9AK1012-1AA00 vs 6SE6400-1PC00-0AA0

The two cable part numbers are often confused in field service because both are referenced in the wider Siemens inverter documentation. The functional and mechanical differences are summarized in the table below.

X300 Connector Pinout and Signal Reference

The X300 service socket is a 9-pin female D-sub on the Control Unit (CU) board, located directly below the PMU (Parameterization Unit) display. The drive is wired as a DCE device, so the connection to a PC COM port (DTE) requires a null-modem-style crossover. The 9AK1012-1AA00 cable integrates this crossover. The pinout is:

Do not extend the cable with an unshielded gender changer or a passive null-modem adapter; signal reflections and EMI from the cabinet will corrupt long uploads. If the PC must be located more than 3 m from the drive, the better approach is a USB-to-RS-232 adapter on the PC end, not a long cable run.

Baud rate and protocol

The X300 service port always uses 9600 bit/s, 8 data bits, even parity, 1 stop bit (8E1). The COM port on the PC must be configured to match. DriveMonitor sets this automatically once the correct COM port is selected. Do not change P060 or any service-affecting parameter while DriveMonitor is connected; doing so will drop the link and may leave the parameter set in an inconsistent state.

USB-to-Serial Considerations for Modern PCs

Most engineering PCs in 2024 have no DB-9 COM port. The 9AK1012-1AA00 cable requires a DB-9. To use DriveMonitor on a modern PC, add a USB-to-RS-232 DB-9 adapter. Recommendations:

• Use an FTDI FT232-based adapter. The driver is signed for Windows 7, 10, and 11, and the chip produces clean RS-232 signal levels.
• Prolific PL2303-based adapters work on Windows 7 with the legacy driver, but on Windows 10/11 the Microsoft-provided driver does not enumerate; install the Prolific "official" driver v3.8.x or later.
• CH340/CH341-based adapters are low-cost and adequate for non-critical applications, but some users report parity-bit handling issues with DriveMonitor on long uploads.
• Set the COM port number in Windows Device Manager to a value between COM1 and COM9. DriveMonitor historically assumes a low COM number; COM10 and higher can require manual configuration in the registry on older DriveMonitor versions.
• USB-to-RS-485 adapters will not work. X300 is RS-232 only. The 6SE6400-1PC00-0AA0 cable referenced in some service notes includes a built-in RS-232 to RS-485 converter and is for the MICROMASTER 4 USS bus, not the Masterdrives X300 service port.

DriveMonitor Software Installation

DriveMonitor is a Windows 32-bit application. On a 64-bit Windows 10 or Windows 11 PC, run it in compatibility mode if needed. The installation procedure:

1. Insert the DriveMonitor installation media (or mount the ISO). The installer is Setup.exe in the root directory.
2. Choose Custom install. Verify that Masterdrives and Simovert drivers are both selected.
3. Accept the default install directory (C:\Siemens\DriveMonitor on a default English Windows).
4. Restart the PC. The USB-to-serial adapter driver loads at boot.
5. Start DriveMonitor. The splash screen displays the version (e.g., V5.4 SP3 HF7). Confirm the version on the Help → About menu before connecting to a drive.

DriveMonitor V5.4 SP3 supports MASTERDRIVES firmware V1.x and V2.x. For firmware V3.x and later (rare on the 1.5 kW MC chassis, but seen on the larger MC units), use DriveMonitor V5.5 or V6.x. DriveES V6.x and V7.x include a DriveMonitor module with the same dialog structure plus S7 routing. The standalone DriveMonitor V5.4 is sufficient for an upload-only workflow.

DriveMonitor Connection Procedure

1. Connect the 9AK1012-1AA00 cable between the PC COM (or USB-to-serial adapter) and the X300 socket on the Masterdrives CU board.
2. Apply line power to the drive. Wait for the PMU to display a run/stop state (typical PMU display: oP 0.0 with the dot indicating readiness).
3. Start DriveMonitor. In the menu bar, select Online → Drive → Settings.
4. Set the Interface field to RS232. Set the COM port to the appropriate value (COM1, COM2, etc.). Confirm 9600/8E1 in the Advanced dialog.
5. Click Connect. DriveMonitor sends the USS handshake to the drive. On a successful link, the status bar displays the drive order number (6SE7015-0EP50-ZC23+G91), the firmware version (P045), and the active parameter set number.

P060 Menu Selection: Detailed Reference

Parameter P060 in Masterdrives selects which parameter group is currently active in the PMU and which group DriveMonitor can browse. The full P060 menu is defined in the Masterdrives Compendium, Chapter 2 - Parameter Description. The full table is:

For a complete parameter backup, the correct value is P060 = 7 (free parameterization). The +G91-specific parameters in the U950-U999 range are exposed through P060 = 7 when the option is enabled, and through P060 = 11 for direct access. DriveMonitor typically sets P060 = 7 automatically when an upload is started, but for hand-off troubleshooting sessions or when using a third-party tool, set P060 = 7 manually on the PMU first.

PMU Procedure to Set P060 = 7

1. On the PMU, press the P key. The display changes from the operating readout to a parameter number.
2. Use the + key to step up to P060. The PMU displays P060 in the upper line and the current value in the lower line.
3. Press P again. The value is now editable; the cursor appears in the lower line.
4. Use + or - to step to the value 7.
5. Press P to confirm. The PMU returns to the operating display after 2-3 seconds.

If the PMU displays P in the lower right corner after pressing P at step 3, the drive is password-protected. The user must enter the password via the PMU numeric keys (the +/- keys act as digit increment/decrement) before the value can be changed. If the password is unknown, a factory reset is required: set P060 = 0, then enter the master reset sequence (P971 = 1 followed by the P-key confirm).

Backup Method 1: Binary Parameter Set (.dnx)

This is the most complete backup method. DriveMonitor reads every parameter in the active parameter set and writes it to a single binary file. The resulting file is a .dnx (Drive eXchange) container in DriveMonitor V5.x, or a .pms (Parameter Memory Set) container in older DriveMonitor versions. The file can be reloaded into the same drive - or an identically optioned drive - to restore the exact state.

1. With DriveMonitor online, select Drive → Parameter Set → Upload to PC (V5.4) or Drive → Read → All Parameters (V5.5/V6.x).
2. DriveMonitor prompts for a target file. Use a meaningful filename that encodes the drive order number, firmware version, and date: 6SE7015-0EP50-ZC23+G91_FW2.3_20240615.dnx.
3. DriveMonitor reads the parameter set over RS-232. Progress is shown in the status bar. A full upload for the 1.5 kW MC with +G91 takes 60-180 seconds at 9600 bit/s.
4. On completion, DriveMonitor displays the parameter count and a 16-bit checksum. Record the checksum; it is used to verify that the file is uncorrupted at restore time.

The .dnx file is binary, contains all parameter numbers, the active value, the lower and upper limits, the attribute bits (BICO, motor, BOP, etc.), and the checksum. This is the only file format that allows an exact one-to-one restore via Download from PC. Loss of the .dnx file means the parameter set must be reconstructed from a printed or text export, which is time-consuming and error-prone.

Backup Method 2: Text/CSV Parameter List

The text export produces a human-readable listing of all parameters and their values. This is documentation-grade, not a complete backup, because BICO binector/connector source/target addresses are not always included in the text dump, and the file cannot be reloaded as a parameter set. Use this method to capture the operating state at the moment of backup, to share a parameter listing with engineering, or to drive a documentation report.

1. With DriveMonitor online, select File → Print → Print to File (V5.4) or Drive → Export → Parameter List to TXT (V5.5/V6.x).
2. Choose the format. DriveMonitor supports .txt (tab-separated) and .csv (comma-separated). The .csv variant is directly readable by Microsoft Excel.
3. DriveMonitor prompts for a target file. Use the same naming convention as the .dnx file with a .txt or .csv extension.

The text export also captures the read-only diagnostic parameters (r000-r099 in the Masterdrives scheme), which is useful for capturing the operating state at the moment of backup. To capture BICO data in the same export, enable the Display BICO checkbox in the export dialog, or run a separate BICO dump (Method 3).

Backup Method 3: BICO / Function Diagram Dump

The third method available in the Masterdrives service menu is a function-diagram (FD) or BICO dump. This method writes the current binector and connector interconnection table to a structured text file that can be reloaded by DriveMonitor to rewire the BICO interconnections without touching parameter values. The use case is when the parameter values are unchanged from a known baseline but the BICO wiring is application-specific.

1. With DriveMonitor online, select Drive → Export → BICO Connections (V5.4) or Drive → Function Diagram → Save As (V5.5/V6.x).
2. DriveMonitor writes a .bix (BICO exchange) or .fdx (function diagram exchange) file.

In practice, the third method is rarely used in field service. Most engineers rely on the binary .dnx upload/download as the primary backup, and the text .csv export as a human-readable documentation artifact. The BICO dump is useful for system integrators who share standardized function diagrams across multiple drives or for replicating the same BICO wiring across a fleet of identical 6SE7015 units.

Comparison of the Three Backup Methods

PROFIBUS Backup via DriveES SIMATIC

If the Masterdrives MC is connected to a SIMATIC S7-300 or S7-400 PLC via PROFIBUS, DriveES SIMATIC provides a transparent routing path from the PC (connected via Ethernet to the PLC's PN port) to the drive (on PROFIBUS). This avoids the need for a direct RS-232 link and works for both the engineering station and runtime diagnostics.

Required components:

• Masterdrives with CBP2 communication board (6SX7010-0FF05) or CBP (6SX7010-0FF00). The CBP2 is the modern variant and supports PROFIBUS DP-V1. The original CBP supports DP-V0 only.
• SIMATIC S7-300 or S7-400 CPU with an Ethernet (PN) port. S7-300 CPUs with integrated PN (e.g., 315-2 PN/DP, 317-2 PN/DP) or with a CP343-1 work. S7-1200/1500 CPUs do not support S7 routing in the same way; use the TIA Portal routing path instead.
• DriveES SIMATIC V5.x or V6.x. The DriveMonitor module inside DriveES has the same dialog structure as standalone DriveMonitor, but with additional configuration to find the drive over the S7 routing path.
• STEP 7 V5.4 SP5 (for DriveES V5.x) or TIA Portal V13 SP1 / V14 (for DriveES V6.x) to configure the S7 routing table.

Procedure:

1. Open STEP 7 (or TIA Portal) and confirm the S7 project containing the Masterdrives on PROFIBUS is loaded on the CPU. The CBP2 GSD file (SIEM8110.GSD for CBP or SI018110.GSD for CBP2) must be installed.
2. Configure the S7 routing: the PC is on the Ethernet side, the S7 CPU is the router, and the Masterdrives is on the PROFIBUS side. The PC must have a reachable Ethernet route to the S7 CPU (ping the CPU first), and the S7 CPU must be configured as a router (S7 routing is enabled by default in S7-300/400 PN CPUs).
3. Open DriveMonitor (the DriveES instance). In Online → Drive → Settings, select the PROFIBUS via S7 interface. Enter the Ethernet IP address of the S7 CPU, the PROFIBUS address of the Masterdrives (set on the CBP2 DIP switches or via P918), and the PROFIBUS slot number.
4. Click Connect. DriveMonitor routes through the S7 CPU to the Masterdrives. The first connection attempt can take 5-15 seconds while the S7 routing handshake completes. The status bar will display the drive order number once the link is established.
5. Once connected, DriveMonitor works as if the drive were on a direct RS-232 link. The same three backup methods apply, with one caveat: over PROFIBUS, parameter set upload takes 10-30 seconds instead of 60-180 seconds.

The DriveES PROFIBUS path is preferred in large plants where every drive is networked and engineers have a single Ethernet-based maintenance terminal. The drawback is the additional engineering overhead (one-time S7 routing configuration) and the per-PC cost of a DriveES license. For a single 6SE7015-0EP50-ZC23+G91 at a remote site with no PLC, the direct RS-232 path with DriveMonitor standalone is more economical.

Restoring a Parameter Set

The .dnx file from Method 1 is restored to the drive with the inverse procedure:

1. With DriveMonitor online, select Drive → Parameter Set → Download from PC (V5.4) or Drive → Write → All Parameters (V5.5/V6.x).
2. Select the .dnx file. DriveMonitor prompts for confirmation: a parameter download will overwrite the entire parameter set.
3. DriveMonitor uploads the parameters to the drive. Progress is shown in the status bar. After the write, the drive is in a parameter-defined state; many parameters require a subsequent save (P971 = 1) to be written to non-volatile memory.
4. Cycle the drive power to activate the new parameter set. Some parameters take effect only after a power cycle (P022, P070, P100, the +G91 option parameters).

Verification and Validation

After a successful upload, validate the backup with the following checks. The same procedure is used after a download to confirm the parameter set matches the expected baseline.

1. DriveMonitor displays the parameter count. The number should be in the range of 800-1500 parameters for a fully optioned Masterdrives MC, depending on the +G91 contents. Record the count and the checksum.
2. Open the .dnx file with DriveMonitor's File → Compare with Online Drive function. The comparison must report zero differences. Any difference indicates a parameter was written or changed during the upload session.
3. Open the .csv export and spot-check five known parameters: P045 (firmware version), P060 (menu selection), P070 (control word source), P100 (motor code), and the +G91-specific option parameters in the U950-U999 range. The values should match the drive's PMU display.
4. If BICO data is critical, run a BICO dump (Method 3) and verify a known cross-reference: the connector for the analog setpoint input is typically K0001 or K0010 in the Masterdrives setpoint channel; the binector for the enable is typically B0100 or B0004 depending on the source.
5. Verify the parameter set number in the status bar matches the expected baseline (P057 in Masterdrives reports the active parameter set number).

Troubleshooting Matrix

Safety and High-Voltage Considerations

The Masterdrives MC is a high-voltage drive. The DC bus capacitors retain dangerous voltage for up to 5 minutes after line power is removed. Always observe the discharge time before opening the cabinet or touching the X300 socket. The X300 socket itself is SELV-class (low voltage), but the surrounding board and backplane can carry DC bus potential if the drive is energized.

During an upload (read), the drive does not need to be in operation and the motor can be at standstill. The upload is a read-only operation at the protocol level, but DriveMonitor may still attempt to set P060 = 7, which is a write; ensure the drive is not in a critical state that would be disrupted by a P060 change.

During a download (write), the drive must be inhibited (no enable signal on the control word, P654 bit 0 or P840 bit 0 depending on control source). Always perform a download during a planned maintenance window with the motor mechanically isolated (e.g., the coupling removed or the brake engaged). A download to a running drive can cause immediate and violent motion if the control structure is changed.

Personal protective equipment (PPE) for work on an energized drive: arc-rated face shield, arc-rated jacket (ATPV 8 cal/cm² or higher), voltage-rated gloves (Class 0, 1000 V AC), and hearing protection if the drive is running.

Best Practices for Parameter Backup Archives

• Store the .dnx file on a network share with versioned backup. Loss of the .dnx file means a full re-commissioning, which for a 1.5 kW MC with +G91 can take 4-8 hours of engineering time.
• Pair the .dnx file with the .csv export, the BICO dump, and a PDF of the function diagram. The four together constitute a complete documentation packet that any engineer can read in 30 minutes.
• Date the filename with YYYYMMDD so a sorted directory reveals the backup history. Include the firmware version in the filename to spot firmware mismatches at restore time.
• Record the firmware version (P045) and the +G91 option code in a separate index. This index is the first reference for a maintenance engineer who is restoring a backup and needs to confirm the right .dnx file.
• Re-validate the backup on a bench setup before field replacement. A .dnx file from a 1.5 kW Masterdrives MC is only useful for the same model and option code; a different power rating or different option code will reject the file during download or will result in immediate overcurrent/overvoltage faults.
• Take a backup immediately after commissioning, after every parameter change, and before every firmware update. Three copies is a good rule: one on the maintenance PC, one on the engineering server, one off-site (tape or cloud).
• Encrypt the .dnx file at rest. A .dnx file is a complete recipe for the drive and is sensitive in a competitive context.

FAQ