SIMOREG CUVC Parameterization via Drive Monitor: Cable, PMU, Baud

Overview

The SIMOREG DC Master drive family uses the CUVC control board as the central armature and field-side regulator. When a CUVC is replaced in the field — typically after a suspected EEPROM, ASIC, or over-voltage failure — the new board ships with a blank or default parameter set and must be re-loaded with the application-specific configuration before the drive can be returned to service. Siemens provides DriveMonitor (historically bundled with the SIMOREG Compendium) as the engineering tool for this task. DriveMonitor talks to the drive through the PMU (Parameterization and Monitoring Unit) — the 9-pin serial port on the front of the CUVC — so commissioning always starts with a verified point-to-point link from the PC to the PMU before any parameter is touched.

This reference consolidates the field-proven procedure: building a PMU RS-232 cable, choosing the right PC connection (native COM vs. USB adapter), setting the USS bus address and baud rate, configuring DriveMonitor, downloading the parameter file, and verifying the result. It also resolves the most common confusion reported on replacement jobs: the LED indicators on the CUVC and adjacent option cards.

CUVC Card Identification and LED Clarification

A point that trips up almost every first-time SIMOREG technician: the CUVC base board itself has no front-facing status LEDs. The 4 or 6 LEDs visible on the control board assembly belong to the optional communication sub-cards plugged into the CUVC slots:

Prerequisites

Before connecting anything, confirm the following:

1. Drive is safe to power. Verify the line contactor is open, the DC link is discharged (SIMOREG DC Master Compendium requires ≥5 min after mains removal), and the field supply is off. A powered-up SIMOREG with the CUVC removed or partially seated can destroy the new board.
2. CUVC part number matches the slot. Common variants: 6RA7000-0MV62-0 (basic), -0MV62-1 (with CBP2), -0MV62-2 (with SLB). Check the order number on the side label.
3. DriveMonitor version. Use DriveMonitor 5.x or newer for Windows 10/11; legacy DriveMonitor 4.x works on Windows XP/7. DriveMonitor is part of the STARTER / DRIVEMONITOR package on the Siemens Industry Online Support portal.
4. Parameter backup (if available). If the previous CUVC could still be read before removal, export the .dnx / .pd parameter file from DriveMonitor — this becomes the upload source for the new board.
5. Motor nameplate data (rated armature voltage, rated armature current, field current, base speed, encoder PPR) so you can re-key critical parameters if no backup exists.

PMU Interface and Cable Construction

The CUVC exposes a 9-pin Sub-D male connector labelled X500 on the front edge of the board. This port carries the PMU (USS) protocol at RS-232 levels. Because every drive ships with this port as standard, it is the default service interface for DriveMonitor.

Build the cable to the following pinout (from the SIMOREG Compendium):

The connector at the drive end is male DB-9; the connector at the PC end is female DB-9. Use only shielded, twisted-pair cable (e.g., LiYCY 3×0.34 mm²) and keep the run under 15 m. Do not route the cable parallel to the armature power cabling — at minimum 200 mm of separation, or cross at 90°.

PC Connection: Native COM vs. USB Adapter

The PMU is RS-232, not RS-485 or USB. The PC side therefore needs a true RS-232 UART. Three options exist, with field reliability in the order shown:

For a SIMATIC Box PC (e.g., SIMATIC IPC227G, IPC627, or older Box PC 620), COM1 is the recommended port. Verify in Windows Device Manager that the COM number assigned by the adapter matches the one selected in DriveMonitor (Online → Settings → COM port).

Baud Rate and USS Bus Address (No "Enable" Parameter)

A common field question is: "which parameter enables the PMU for DriveMonitor?" The answer is none. The PMU USS port is hard-enabled at firmware level on every CUVC. The only settings that matter are:

1. Bus address (node number) — default 0, parameter P051.01 (USS address of PMU). DriveMonitor must address the same node; this is set in Online → Settings → Drive Address.
2. Baud rate — must match exactly between drive and DriveMonitor. Typical PMU baud rates supported by SIMOREG 6RA70 are 9600 (default) and 19200. The drive-side baud is selected on the PMU front panel under the communications menu, or by writing to the appropriate USS parameter (refer to the SIMOREG 6RA70 Compendium, Chapter "Communication / USS").
3. Parity / data bits — 8-E-1 (8 data, even parity, 1 stop) is the SIMOREG USS default.

DriveMonitor Configuration

1. Launch DriveMonitor and select Online → Settings (or press F2).
2. Under Interface, choose USS (not PROFIBUS).
3. Set COM port to the physical port: COM1 for a Box PC native port, or the COM number assigned by the USB adapter.
4. Set Baud rate to the value programmed into the drive (9600 default).
5. Set Drive address to 0 unless P051.01 was changed.
6. Click OK.
7. Press the green Online button or F5. DriveMonitor should report the device type (e.g., SIMOREG 6RA70 6RA7081-...<F>) and firmware version within 2-3 seconds.

If the connection drops or returns Timeout / No response from drive, the baud-rate mismatch is the #1 cause. Cycle the drive control voltage (24 V on terminal X101) and retry.

Step-by-Step Parameterization Procedure

Step 1 — Establish Online Connection

Power the drive electronics only (no armature mains). Confirm the PMU 7-segment shows 0.0 or o.0 (drive in "standby / no fault" state). Open DriveMonitor as above. A successful handshake is shown by a green icon in the status bar and a populated parameter list in the left tree view.

Step 2 — Upload from Drive (if old CUVC still readable)

1. Online → Parameter → Upload (Drive → PC).
2. Select All parameters.
3. Save as backup_<drive_tag>_<date>.dnx.

Step 3 — Download to New CUVC

1. Open the parameter file from Step 2 (or a known-good archive file).
2. Verify drive type and rated current match the connected armature circuit.
3. Online → Parameter → Download (PC → Drive).
4. Select All parameters and confirm. The drive will perform a parameter check (≈5-15 s) and may briefly drop the PMU link during the EEPROM write cycle.
5. Wait for the Parameter download complete prompt before issuing any further commands.

Step 4 — Verify Critical Parameters

After download, read back and confirm the following (typical values shown for a generic 6RA70 application):

Always cross-check the actual current and voltage values against the parameter file used for the download — the most common reason a drive trips immediately after a CUVC swap is a leftover default (e.g., P100 = 100 A on a 760 A armature).

Verification Checklist

• ☐ DriveMonitor reports correct device type and firmware version after online connect.
• ☐ Upload (Drive → PC) returns the same parameter set that was downloaded (byte-equal compare).
• ☐ PMU 7-segment shows 0.0 with no active fault.
• ☐ P100, P101, P102 match motor nameplate.
• ☐ P051.01 matches DriveMonitor's drive-address setting.
• ☐ Field current is observed on r038 with field supply enabled (typically 60-90% of rated).
• ☐ Encoder count increments correctly when shaft is rotated by hand (check r023 or P741-related r-parameters).
• ☐ With mains applied and run command given, armature voltage appears on r019 and motor turns without F031 (overspeed) or F035 (field loss).

Troubleshooting Matrix

Alternative Interfaces: When PMU Is Not the Best Choice

For initial commissioning on a new machine, the PMU/USS path is sufficient. For larger fleets or production-line deployments, prefer:

• PROFIBUS-DP via CBP2 — set the CBP2 node address with rotary switches on the card, configure DriveMonitor to PROFIBUS interface, and use a Siemens PC adapter (6GK1571-0BA00-0AA0 or current equivalent).
• PROFINET via CBE20 — supported on 6RA80 series only; not applicable to CUVC-based 6RA70 drives.
• USS over Ethernet (RS-232-to-Ethernet server) — useful for remote diagnostics but adds a failure mode (TCP keep-alive, latency); recommended only for monitoring, not for the initial parameter download.

Notes on EEPROM, Firmware, and Spare Cards

The CUVC stores its parameter set in on-board EEPROM. A failed EEPROM write is rare but possible if control voltage dips below 18 V during the download. Symptoms include:

• DriveMonitor reports parameter inconsistency on next power-up.
• PMU shows F042 (parameter error) on boot.
• r047 (parameter checksum) returns a non-zero value.

Recovery: re-enter factory defaults via P052 = 1 (carefully — this erases the parameter set), then re-download the backup. If the EEPROM itself is the failed part, the CUVC must be replaced.

Always keep at least one known-good spare CUVC per drive rating in the spares cabinet. Bench-test spares by connecting them to a dummy 24 V supply and the PC; this catches dead boards before they are installed in a production drive.