Simovert VC DriveMonitor: Restoring P053 and P60 Parameter Access
When Siemens DriveMonitor software detects a Simovert VC (6SE70 series) MASTERDRIVES unit on the serial service bus but cannot read the technology variant (VC vs. FC) or report the firmware version, the problem is almost always a locked parameter access level on the drive. The drive replies to the bus scan because the USS layer is still active, but the parameter server returns empty or generic data because P053 (Parameter Access) is preventing the expert parameter set from being opened and P60 (Parameter Menu Selection) is not pointing to the full menu. Setting P053 = 6 (binary 00000110) and P60 = 7 restores the access required for DriveMonitor to identify the drive and load the correct technology database.
1. Problem Description
Operators and commissioning engineers regularly encounter the following situation in the field:
- DriveMonitor is launched on the engineering PC and a USS/SSV scan is initiated from Online → Search for Online Drives.
- The software lists one or more Simovert VC drive nodes on the connected bus, complete with the configured USS address.
- However, the Technology field is blank or reports "Unknown", and the Firmware field shows dashes, question marks, or "
??". - A spare drive of the same catalog number on the bench (typically still in factory default state) is identified correctly in the same software session.
This pattern is the signature symptom of a parameter access restriction: the drive's serial link is healthy, the address responds, but the expert parameters that DriveMonitor queries to identify the technology and read the firmware version are not visible to the PC. DriveMonitor cannot load its matching technology database without those parameters, which is why the unit appears as a "shell" with no firmware information.
P053 and P60.2. Affected Products and Software Versions
| Item | Description | Catalog / Version Identifier |
|---|---|---|
| Simovert VC (drive) | MASTERDRIVES Voltage Control, vector/voltage-controlled variant for excitation and high-performance drives | 6SE70 series (compact: 6SE7016-..., 6SE7021-...; chassis: 6SE7031-..., 6SE7041-...) |
| Simovert FC (sibling) | Frequency Control variant of the same MASTERDRIVES family | 6SE70 series FC technology |
| DriveMonitor | Siemens commissioning tool for MASTERDRIVES, SIMOREG, COMBIVERT | DriveMonitor v5.x and v6.x (e.g., V5.4, V5.5, V6.0) for Windows |
| Connection | RS232 (SSV1) or RS485 (SSV2) point-to-point via Siemens cable | 6SE7090-0XX84 series cable assemblies |
| Protocol | USS (Universal Serial Interface) over the serial service port | USS protocol, 9600 or 19200 baud (drive parameter adjustable) |
| Parameter set | Expert parameters required for technology/firmware identification | Driven by P053/P60 access level |
The Simovert VC platform is used in industrial applications such as turbine excitation, large hoists, rolling mill drives, and high-inertia fans. The fact that the source problem occurs on a drive controlling the excitation of a vapor (steam) turbine is typical of legacy retrofits and refurbishments where the drive has been in service for years and its parameters have been progressively locked by plant engineers to prevent unauthorized changes.
3. Root Cause: P053 and P60 Lock the Expert Parameter Set
The MASTERDRIVES platform uses two parameters to control what the operator panel (PMU) and the PC commissioning tool can see and modify:
3.1 P053 - Parameter Access
P053 is an 8-bit field that gates access to the various parameter groups. Each bit enables a specific access level. The Siemens documentation defines the bits as follows (LSB = bit 0):
| Bit | Decimal Value | Function |
|---|---|---|
| 0 | 1 | Enable commissioning parameters |
| 1 | 2 | Enable parameter menus |
| 2 | 4 | Enable download to operator panel (OP/PMU) |
| 3 | 8 | Enable download to PC (DriveMonitor / STARTER) |
| 4 | 16 | Enable expert mode in operator panel |
| 5 | 32 | Write protection for all parameters |
| 6 | 64 | Reserved / drive-specific |
| 7 | 128 | Reserved / drive-specific |
To read and write the values required for DriveMonitor identification and configuration, the sum of the relevant bits must be set. A common expert-mode value is:
-
P053 = 6(binary00000110) = bits 1 and 2: parameter menus plus download to OP/PMU.
This minimal expert setting opens the parameter menu structure for the operator panel and unlocks the same set on the PC side, which is what DriveMonitor needs to enumerate the technology and firmware. Higher values (e.g., 14 = 00001110 for PC download, or 30 = 00011110 for full expert access) extend the access further; for the symptom described in this article, P053 = 6 is sufficient.
P053 = 6 also exposes the parameter set to DriveMonitor over USS. The original Siemens moderator recommendation in the field report specifies exactly this combination.3.2 P60 - Parameter Menu Selection
P60 selects which menu is displayed on the PMU and on DriveMonitor's parameter tree. The value range differs slightly between VC and FC units, but the common interpretation is:
| P60 Value | Menu |
|---|---|
| 0 | Operating parameters (read-only, runtime values) |
| 1 | Commissioning parameters |
| 2 | Drive / motor data |
| 3 | Motor / encoder data |
| 4 | Control / function diagrams |
| 5 | Power section |
| 6 | Communication / boards |
| 7 | All parameters / expert menu (includes identification, firmware, and technology parameters) |
Setting P60 = 7 opens the full parameter tree, which is where DriveMonitor looks for the identification parameters (firmware version, technology variant, and option module inventory) needed to display the drive correctly.
4. Solution: Set P053 = 6 and P60 = 7
Restore DriveMonitor's ability to read the technology and firmware by performing the following two parameter changes on the drive:
- Set
P053 = 6(binary00000110). - Set
P60 = 7(parameter menu "all parameters / expert").
These changes can be made either from the drive's PMU (operator panel) before launching DriveMonitor, or from DriveMonitor itself if the drive is at least partially readable. The recommended sequence is to set both parameters from the PMU, save to non-volatile memory, and then re-launch the online search.
4.1 Can P053 and P60 Be Changed While the Drive Is Running?
The general MASTERDRIVES rules apply:
- P60 (menu selection): Can be changed at any time, online or offline, without affecting the running process. It only changes the visible menu.
- P053 (parameter access): Can typically be changed online without interrupting the running drive, but the change takes effect immediately. In a process-critical application (e.g., turbine excitation), it is best practice to perform the change during a planned maintenance window or with the drive in a safe state, in case the new access level reveals an offline parameter (e.g., a default factory value) that the controller was hiding from the running logic.
5. Step-by-Step Commissioning Procedure
5.1 Prerequisites
- Siemens DriveMonitor installed (V5.x or V6.x) on a Windows PC with an available RS232 (COM) port, or a USB-to-RS232 adapter tested with a known-good loopback.
- Siemens SSV/USS PC cable, 6SE7090-0XX84 series. The exact sub-variant depends on the PC's COM port (e.g., 6SE7090-0XX84-4HA0 class for a 9-pin D-Sub on the PC).
- Drive PMU (operator panel) accessible, or a previously commissioned working drive on the same network for comparison.
- USS address of the target drive known (default 0, configurable via P788 / DIP switch on the option board).
5.2 Setting the Parameters from the PMU
- Power the drive's electronics (the 24 V supply to the CU board does not need the DC link to be charged for parameter editing, but P053 changes take effect only after a parameter save cycle on some firmware versions).
- On the PMU, press the P key to enter parameter mode. The display shows the current parameter number.
- Use the ↑ / ↓ keys to navigate to
053. Press P to enter edit mode. - Set the value to
6using the numeric keys, then press P to confirm. The display returns to the parameter list. - Navigate to
060(note: on some firmware versions the parameter is displayed asP60; on others asr60if it is read-only - P60 is writable on MASTERDRIVES VC). - Set the value to
7and confirm with P. - If the PMU shows a "Save" prompt, confirm to write the values to non-volatile memory. If the drive does not prompt, the changes are stored automatically when the parameter is confirmed; however, P053 may need a separate save command (P052 in some firmware versions, or the PMU's "Save parameters" menu entry) to survive a power cycle.
5.3 Verifying in DriveMonitor
- Open DriveMonitor and select Online → Search for Online Drives (or the equivalent in the localized menu: "Search online", "Search for nodes").
- Select the correct COM port and baud rate (default 9600, sometimes 19200 if the drive has been reconfigured; check the working spare for the actual setting).
- Click Start Search. The drive should appear with a populated Technology field (e.g., "VC") and a populated Firmware field (e.g., "V2.x").
- Double-click the drive to go online. The parameter tree should now show all expert parameters, including identification and option-board parameters.
5.4 Saving the Parameters Permanently
On the MASTERDRIVES family, parameter changes made over USS or from the PMU are stored in the drive's volatile RAM by default. To retain them across a power cycle, perform a parameter save:
- From the PMU: enter parameter mode, navigate to the "Save" or "Copy RAM to EEPROM" entry, confirm.
- From DriveMonitor: use the Upload/Download or Save to EEPROM function, typically found in the Drive menu.
6. Cable, Connector, and Physical Layer
DriveMonitor communicates with the Simovert VC over Siemens's serial service interface (SSV). The two relevant ports on the drive are:
| Port | Location | Interface | Use |
|---|---|---|---|
| SSV1 (X300) | CU / PMU board | RS232 (3-wire: TX, RX, GND) | Direct PC connection, peer-to-peer commissioning |
| SSV2 (X308) | CU / option board | RS485 (2-wire or 4-wire) | Multi-drop bus, PC with RS485 adapter or SIMATIC S7 PPI/MPI |
For a single-drive bench connection, the Siemens 6SE7090-0XX84 cable (RS232 PC end to drive SSV1) is the standard accessory. The cable contains a level shifter to convert the drive's serial levels to RS232 line levels. For multi-drop networks, a SIMATIC RS485 adapter or a third-party USB-to-RS485 isolator can be used, but DriveMonitor's "search" function works best with a 1:1 connection during initial commissioning.
7. DriveMonitor Communication Settings
Configure DriveMonitor's online interface as follows (verify against the actual dialog in your localized version):
| Setting | Recommended Value | Notes |
|---|---|---|
| COM port | COM1 or COMx (whichever the USB-Serial adapter enumerates) | Check Windows Device Manager |
| Baud rate | 9600 (default) or 19200 | Must match drive's P790/P791 or DIP setting |
| Parity / Data / Stop | Even / 8 / 1 (USS default) | USS protocol standard |
| USS address | 0 (default), scan range 0-30 or 0-31 | Each drive on the bus must have a unique address |
| Timeout | 1500-3000 ms | Increase if the bus is noisy |
8. Verification: Confirm the Drive Is Fully Online
After applying P053 = 6 and P60 = 7, run the following checks to confirm the drive is fully online and identified:
- Identification test: DriveMonitor's "Search for Online Drives" result row for the affected drive now shows the technology (VC) and firmware (e.g., V2.4 SPx).
- Parameter read test: Open parameter r001 (firmware version) or the technology-identifier parameter in the expert set. The value must read a numeric firmware code, not a placeholder.
- Parameter write test: Change a non-critical parameter (e.g., a display unit or a monitoring timeout) and re-read it. If the read confirms the write, the bidirectional USS link is fully functional.
- Fault buffer read: DriveMonitor can read the fault buffer (r947, r949). The drive must return a populated fault list. A locked drive returns an empty buffer or a "parameter not available" error.
- Save cycle: Trigger a save to EEPROM and power-cycle the drive. After power-up, P053 must still read 6 and P60 must still read 7. If they revert to 0, the save did not commit - this is itself a useful diagnostic.
9. Parameter Reference Summary
| Parameter | Name | Type | Default | Recommended Value | Effect |
|---|---|---|---|---|---|
| P053 | Parameter Access | Bit-coded (CST/UST) | 0 (or 6 in some firmware defaults) | 6 (binary 00000110) | Unlocks parameter menus and OP download for DriveMonitor identification |
| P60 | Parameter Menu Selection | Integer 0-7 | 0 (operating) | 7 (all / expert) | Selects the full parameter tree, exposing identification and technology parameters |
| P052 | Save Parameters (firmware variant) | Command | - | 1 (Save) | Writes current RAM values to non-volatile memory |
| r001 | Firmware version (read) | Read-only | - | - | Read after P053=6 / P60=7 to confirm identification |
| P790 | USS address at SSV1 (X300) | Integer 0-31 | 0 | Per plant | Must be unique on the bus |
| P791 | Baud rate at SSV1 | Integer / enum | 9600 | 9600 or 19200 | Must match DriveMonitor |
10. Troubleshooting Matrix
| Symptom | Likely Cause | Action |
|---|---|---|
| Drive found, technology blank, firmware blank | P053/P60 locked (this article) | Set P053=6, P60=7 |
| Drive not found at all | Cable, COM port, baud rate, USS address mismatch | Test with the working spare on the same cable and port |
| Drive found but parameter tree empty | P60 not set to expert (7) | Set P60=7 |
| Drive found, identified, but read-only | Bit 5 of P053 set (write protection) or expert bits insufficient | Set P053 to remove write protection (clear bit 5), add bit 0 if commissioning is also locked |
| Drive found but P053 itself read-only | Expert bit (bit 4) not set, or a higher-level key switch / password is active | Check for a hardware key switch on the PMU; consult plant parameter owner for password |
| Working spare found, installed unit not | Different firmware, different default baud, or option board difference | Match baud and address; verify option board inventory |
| All drives found briefly, then communication errors | Termination, ground loop, or noisy RS485 bus | Enable RS485 termination on the two end nodes; isolate ground |
| Drive found, identified, but DriveMonitor reports "wrong technology database" | DriveMonitor's database (e.g., MASTERDRIVES_V2.x) does not match the drive's firmware | Install the matching DriveMonitor service pack or upgrade to a version that includes the firmware |
11. Additional Considerations for Turbine Excitation Applications
The original symptom is on a drive controlling the excitation of a vapor (steam) turbine. A few field-proven points specific to that context:
- Excitation current is a safety-critical loop. The drive must remain in closed-loop current control throughout the parameter edit. If P053 or P60 is changed while the excitation current is being regulated, ensure the change does not briefly interrupt the field current (some firmware versions momentarily halt the regulator during certain parameter commits). Where possible, perform the edit with the field current at a known setpoint and a standby controller in service.
- Synchronization with the grid. If the turbine is grid-synchronized, do not change P053/P60 without informing the grid operator. Some protection relays derive a permissive from the excitation regulator; an unexpected parameter change should not be visible to the relay, but the parameter-save cycle can briefly increase CPU load.
- Field-flash and de-excitation paths. After a parameter save and power cycle, verify that the field-flash sequence (initial magnetization of the rotor) completes correctly. A locked parameter set can mask a misconfigured field-current setpoint or related parameter; once unlocked, the engineer may discover latent issues that were previously hidden.
- Plant parameter documentation. The fact that a parameter was locked (P053 = 0) and a spare in the warehouse is unlocked is a strong indicator that a plant engineer deliberately set the lock. Confirm with the original equipment vendor or the plant's automation engineer that unlocking P053 will not void a warranty, a SIL-rated configuration, or a regulatory commitment.
12. Migrating to STARTER / SINAMICS Startdrive
DriveMonitor is a legacy Siemens commissioning software for the MASTERDRIVES family. For new commissioning or major retrofits, Siemens recommends the STARTER (for SINAMICS G/S drives) or SINAMICS Startdrive (TIA Portal) commissioning tool. Some engineering workflows retain DriveMonitor for legacy VC units because the firmware, parameter set, and identification strings are not always replicated 1:1 in STARTER. When a Simovert VC is replaced by a SINAMICS G150/G130 or SINAMICS S120, plan a parallel commissioning: the old unit continues to run on DriveMonitor until the new SINAMICS drive is fully loaded, parameterized, and run-tested. The P053/P60 unlock procedure is specific to MASTERDRIVES and does not apply to SINAMICS; the SINAMICS access levels are managed under Parameters → Access level in STARTER, or via the drive's p0000-class setting.
13. Related Error and Symptom Codes
Although the source problem is not a fault code, the following related diagnostic information is useful when troubleshooting MASTERDRIVES VC drives with DriveMonitor:
| Code / Display | Meaning | Common Cause |
|---|---|---|
| DriveMonitor: "Online drive found, but no technology identified" | Drive responds on USS but identification parameters are not readable | P053 / P60 locked (this article) |
| DriveMonitor: "Timeout reading parameter r001" | Drive does not respond to the parameter read request | Address mismatch, baud rate mismatch, or hardware fault |
| PMU: "F001" | Overcurrent | Motor or cable fault, ramp too steep |
| PMU: "F002" | DC link overvoltage | Regenerative energy, line condition, brake chopper configuration |
| PMU: "F003" | IGBT desaturation / output stage fault | Power section hardware fault |
| PMU: "F006 / F008 / F011" | CU board fault | Replace or reflash the CU board |
| PMU: "PS xxx" | Active parameter set (set 1, 2, 3, or 4) | Not a fault - informational |
| PMU: "EE" or "EEnnn" | EEPROM fault or error during save | Failed save cycle; replace CU board if persistent |
14. Summary of the Two-Parameter Fix
The complete resolution to the original "DriveMonitor finds the Simovert VC but does not recognize the technology or firmware" symptom is:
- Set
P053 = 6(binary00000110) to enable parameter menus and OP download. - Set
P60 = 7to select the expert / all-parameters menu. - Save the parameters to non-volatile memory (PMU save command or DriveMonitor's "Save to EEPROM" function).
- Re-run Online → Search for Online Drives in DriveMonitor. The drive should now be identified with its technology and firmware version.
After the fix, the commissioning engineer has full parameter access to read the drive's configuration, modify setpoints, and integrate the unit with the plant's DCS or turbine governor.
Frequently Asked Questions
What does P053 = 6 actually do on a Simovert VC drive?
P053 = 6 (binary 00000110) sets bits 1 and 2 of the parameter access field. Bit 1 enables the parameter menus, and bit 2 enables download to the operator panel. Together they unlock the parameter set that DriveMonitor needs to identify the drive's technology and firmware version.
Why is P60 = 7 required in addition to P053 = 6?
P60 selects which parameter menu is exposed. P60 = 7 selects the expert / all-parameters menu, which contains the identification parameters (technology variant, firmware version, option-board inventory) that DriveMonitor queries. Without P60 = 7, even an unlocked access level would not show the identification parameters to the PC.
Can P053 and P60 be changed while the drive is running?
P60 (menu selection) can be changed online safely. P053 (parameter access) can also be changed online in most MASTERDRIVES firmware versions, but the change takes effect immediately. For process-critical applications such as turbine excitation, perform the change during a planned maintenance window or with the drive in a safe state to avoid any brief interruption during the parameter commit cycle.
Why does DriveMonitor find the drive at all if P053 is locked?
The USS protocol layer (the bus scanner) is independent of the parameter access level. The drive replies to the address-poll request with its USS address even when P053 is 0, because that does not require parameter-server access. The parameter-server access (which reads the identification parameters) is what is blocked, so DriveMonitor can list the node but cannot fill in the technology and firmware fields.
What cable is needed to connect a Simovert VC to a PC running DriveMonitor?
Use a Siemens SSV/USS cable, 6SE7090-0XX84 series, with a 9-pin D-Sub RS232 connector on the PC end and the matching connector on the drive's SSV1 (X300) port. For multi-drop RS485 networks, use an RS485 adapter at the PC end and connect to SSV2 (X308). If using a USB-to-RS232 adapter, choose an industrial-grade unit with a TI or FTDI chipset to ensure correct RS232 voltage levels.
Will this procedure work on a Simovert FC or other MASTERDRIVES variant?
Yes. The P053 bit assignment and the P60 menu selection are common across the MASTERDRIVES family (FC, VC, and Compact Plus), so the same P053 = 6 / P60 = 7 settings restore DriveMonitor access on any MASTERDRIVES unit. The technology string reported by DriveMonitor will differ (FC vs. VC), but the fix is identical.