SIMOREG 6RA70 6RA7096 Voltage Measurement Errors Field

Problem Summary: SIMOREG 6RA7096-4MV62 Armature and Field Sensing Errors

Two SIMOREG DC-Master 6RA7096-4MV62-0-Z drives connected in parallel and rated 950 V AC line, 1000 V DC link, 2200 A DC each report incorrect analog readings on first commissioning. The errors are reproducible on both units, present at no-load and at light load, and do not change after an operator-panel parameter reset. A calibrated Category IV bench multimeter is used as the reference; the drive PMU panel and any connected DriveMonitor trace are the suspect sources.

Two characteristics narrow the search immediately. First, the AC and DC voltage errors are not proportional (1.170 vs. 1.333). A single global scaling parameter cannot produce two different gain errors on the same plant. Second, the field current error is negative while the voltage errors are positive, which means the field path is not on the same signal chain as the armature path. The parallel configuration rules out a wiring issue confined to one drive.

Hardware Architecture Relevant to the Fault

On a SIMOREG 6RA70, the analog measurements that appear on the PMU and on DriveMonitor follow a fixed signal path. Understanding the path is essential because the symptoms above point to specific stages of it. Reference the official SIMOREG DC-Master 6RA70 operating instructions on the Siemens Industry Online Support portal for the full architecture and the parameter list for the firmware revision installed on the affected drives.

Figure 1 — Analog signal path on a 6RA7096 chassis. The voltage sensor board is the analog front-end; CUD1 owns the A/D converters and the scaling math; PMU, OP1S, and DriveMonitor are pure read-only consumers.

Key boards in this path on a 6RA7096 chassis:

• Voltage sensor board (sometimes called the VS or analog interface board; in 6RA70 it carries Siemens part numbers in the C98043-A… family). It contains resistor dividers, isolation amplifiers, and per-channel gain / offset trims for the armature AC line sensing and the DC link sensing. It is bolted to the power section frame.
• Current sensor / shunt board. Field current on a 6RA70 is measured through a calibrated shunt in the field bridge; armature current is sensed via shunt resistors in the DC link or via current transducers. These are separate analog chains from the voltage path.
• CUD1 — Control Unit Digital. The main processor board. It hosts the firmware, the parameter EEPROM, the A/D converters, and the connectors that distribute values to the PMU operator panel, OP1S, DriveMonitor, and the analog outputs.
• PMU / OP1S / DriveMonitor. Read-only displays; they cannot introduce measurement error on their own. A mis-mapped U-parameter can, however, make a correct value appear wrong.

The split between the voltage sensor board (analog front end) and CUD1 (digital back end) is what makes the symptom set diagnostic. The two different voltage errors (1.170 vs. 1.333) and the negative field error cannot all originate in the same A/D channel. They must come from at least two different physical locations on the analog front end.

Why the Error Ratios Matter

Each of the three measured values goes through a different scaling chain before it shows up on the PMU. Listing the chains explicitly makes the symptom set interpretable:

Because the AC path and the DC path on the 6RA70 voltage sensor board are physically different channels with their own gain stages, two independent gain errors are physically possible on a single sensor board. That is consistent with the 1.170 vs. 1.330 split. The negative field error suggests the field chain has either a low-side bias, a wrong rated value in P104, or a separate gain error on the field / shunt board.

Root Cause Matrix

Rank the candidates from most to least likely, given that the fault is identical on both parallel bridges and that the errors are not proportional:

Pre-Diagnostic Setup and Required Tools

Before opening the cabinet, gather the following and confirm you have working access to the parameter set:

1. Calibrated Category IV true-RMS multimeter (Fluke 87V, Gossen MetraHit, or equivalent) with a current date on the calibration certificate.
2. Insulated 1000 V probes and a clip adapter so a second person can record readings safely.
3. A copy of the SIMOREG DC-Master 6RA70 parameter list for the firmware version installed on the affected drives (downloadable from the Siemens Industry Online Support portal).
4. Access to the operator panel (PMU) and, if installed, an OP1S or a DriveMonitor trace.
5. The parameter dump attached to the original incident (so you can compare against factory defaults).
6. A working spare CUD1 and a working spare voltage sensor board, if your organization stocks them. The 6RA7096 chassis uses the larger C98043-A…-series sensor board — confirm the exact part number from the BOM before ordering a spare.
7. ESD wrist strap and a clean, dry bench if a board swap is required.

Reference the official SIMOREG 6RA70 documentation at the Siemens Industry Online Support portal. The operating instructions and the parameter list are both available there; the support pages for the 6RA70 family index the firmware notes and the list manual.

Step-by-Step Diagnostic Procedure

Work the matrix in order. The procedure is designed so that you localize the fault to a single replaceable assembly before swapping anything.

Step 1 — Confirm the operator is reading r-parameters, not a U821 alias

Operators frequently assign a free U-parameter to a connector that is convenient for commissioning, then forget. If the value on the PMU does not match the corresponding r-parameter, the r-parameter is the truth and U821 is the suspect.

1. On the PMU, navigate to the r-parameter that corresponds to the line voltage, DC link voltage, and field current for the affected drive. The exact r-numbers depend on the firmware version; consult the parameter list.
2. Write the three r-values down.
3. Navigate to U821 and any other U-parameter the operator is using to read these values; write those down too.
4. If the r-parameters match the multimeter and the U-parameters do not, the analog front end is fine. The U-parameter mapping is the fault. Re-map U821 to the correct connector and re-verify.

Step 2 — Verify the power-section code

On the SIMOREG 6RA70, the power-section code is a small set of parameters that tells the firmware which analog front-end scaling curves to apply. A miscoded drive will read wrong on all channels, but typically uniformly.

1. Read the order code (MLFB) on the drive nameplate. For the affected units this is 6RA7096-4MV62-0-Z.
2. Locate the power-section code parameter P078 and any related P077 / rated-data parameters on 6RA70; cross-check the values against the order code. The factory default for a 6RA7096-4MV62-0-Z is set at the bench and should not be edited in the field.
3. If a code is wrong, write it down and correct it to the value from the parameter list. Power-cycle the drive and re-measure.

Step 3 — Read the raw A/D values and the diagnostic r-parameters

Most 6RA70 firmware versions expose a diagnostic r-parameter that reports the raw A/D counts for each channel, expressed as a percentage of full scale. If your firmware supports it, log the raw values at the same moment you write down the multimeter reading.

1. With the drive at no-load and a stable AC line, log the diagnostic r-parameter for the line-voltage channel.
2. Log the diagnostic r-parameter for the DC link channel.
3. Log the diagnostic r-parameter for the field-current channel.
4. Compare the three to the known inputs. If the diagnostic r-parameters are off by a fixed factor, the analog front end is the suspect. If the diagnostic r-parameters are correct and the displayed values are wrong, the scaling math in the CUD1 is the suspect.

Step 4 — Cross-swap the voltage sensor boards

This is the definitive localization step. If both drives have the same error, swapping sensor boards is the fastest way to determine whether the fault lives on the sensor board or on the CUD1.

1. De-energize, lock-out, verify zero energy on the DC bus.
2. Remove the voltage sensor board from drive A and install it in drive B. Use the exact part number from the BOM. The board is keyed and cannot be installed backwards, but connector pin count varies between 6RA70 chassis sizes — confirm the part number before seating it.
3. Re-energize drive B and re-measure the three values.
4. Repeat for the board from drive B into drive A.
5. If the errors follow the board, the board is the fault. If the errors stay with the chassis, the CUD1 is the fault.

Step 5 — Inspect the field current path

The −4.6% on field current is independent of the voltage errors and points to a separate path. The most common causes in order of likelihood:

1. Wrong rated field current in P104. Compare to the motor nameplate.
2. Shunt calibration. Verify with a clamp-on ammeter at a known reference current.
3. Field / shunt board gain drift. Replace the board if steps 1 and 2 do not resolve the issue.

Hardware Replacement: Voltage Sensor Board and CUD1

When the cross-swap in Step 4 localizes the fault, replace the suspect board. Follow the Siemens operating instructions for the 6RA70 family, available on the Siemens Industry Online Support portal. The high-level procedure is the same for all 6RA7096 chassis; only the board part numbers differ.

Voltage sensor board replacement

1. De-energize, LOTO, verify zero energy on the DC bus, and wait the full discharge period.
2. Open the cabinet, photograph the connector layout, and label every cable. The voltage sensor board typically has 3–4 edge connectors to the power section and one to the CUD1.
3. Remove the board. Place it in an ESD bag.
4. Install the replacement board, torque the mounting screws to the spec printed on the chassis, and re-seat the connectors.
5. Restore power, navigate to the parameter list, and confirm P078 and the related power-section codes still match the order code.

CUD1 replacement

The CUD1 carries the parameter EEPROM. If the new CUD1 is supplied empty, the parameter set must be reloaded from the parameter dump or from a saved commissioning file. Do not assume a swap with a blank CUD1 will run.

1. From the existing CUD1, perform a parameter upload via DriveMonitor or via the OP1S to a CompactFlash card or to a connected engineering station. Confirm the upload completed and the file size is non-trivial.
2. De-energize, LOTO, verify zero energy, and swap the CUD1. Re-seat the card if present.
3. Re-energize and perform a parameter download to the new CUD1.
4. Power-cycle and re-measure. If the errors persist with a known-good sensor board, the new CUD1 is also suspect and the procedure is to bench-test the original CUD1 against a working unit.

Re-Commissioning and Verification

After any board swap, run the full no-load to full-load verification before returning the drive to production. The verification must close the loop on all three measured quantities, not just the one that triggered the swap.

1. Apply AC line voltage. Drive at no-load. Compare PMU and OP1S readings to a calibrated multimeter on the AC bus, the DC bus, and the field supply. Acceptable error on a healthy 6RA70 is within the sensor-board spec — typically ±1% of full scale for armature voltage and ±2% of full scale for field current at room temperature. Anything beyond that is a regression.
2. Enable the drive with zero speed setpoint. Confirm internal r-values for line voltage, DC link voltage, armature current, and field current are stable and within the same tolerance.
3. Ramp the speed setpoint in 10% steps to 100%. At each step, log the r-values and the multimeter readings. The error ratio must remain constant across speed; if it changes with speed, the sensor board is not the only problem.
4. Apply a step load change at 50% speed and 100% speed. Confirm the field current is stable within ±2% during the load step.
5. Run the drive under load for 30 minutes and re-measure. Sensor board drift under thermal stress is a known failure mode on aged 6RA70 electronics; a 30-minute heat soak is the cheapest way to find it.

Field-Proven Diagnostic Flowchart

Figure 2 — Diagnostic decision tree for the reported 6RA7096-4MV62 fault pattern. The cross-swap at Step 4 is the single most informative action; it localizes the fault to one of two assemblies in a few minutes.

Quantifying the Two-Error Signature

The non-proportional error pair (1.170 on AC, 1.333 on DC) is a useful diagnostic signature. The two channels on the 6RA70 voltage sensor board use different resistor dividers and different isolation amplifier gains, so a partial failure of the analog front end can produce two different gain errors simultaneously. A single global scaling parameter cannot, so any path that explains the fault with one parameter is wrong.

For the 6RA7096-4MV62-0-Z specifically:

• AC line sensing uses a three-phase resistor divider feeding a single AC measurement. A 17% gain error on this channel implies either a divider resistor out of spec (commonly a thermal-mechanical failure on the high-side resistor) or an isolation amplifier gain drift.
• DC link sensing uses a direct-connection isolation amplifier across the DC bus. A 33% gain error on this channel is too large to be a resistor drift; the most common cause is a failed component on the sensor board itself, typically an isolation amplifier IC or a precision reference in the DC channel only.
• Field current sensing is on a different board and is consistent with a low-side bias or with P104 set above the actual motor field rating. If the motor is rated 65 A and P104 reads 70 A, the displayed field current will be 65/70 ≈ 0.93 of the actual — directionally consistent with a 4.6% low reading, but the actual error is closer to 7% in that scenario. Verify P104 against the motor plate.

Spare-Parts and Stocking Notes

The 6RA70 family is mature hardware. Some boards are still available from Siemens spares, others are not. Stock both sensor boards and a CUD1 in the panel shop if the drive is on a critical process. The 6RA7096 chassis uses a larger sensor board than the 6RA7081 / 6RA7082 units; do not interchange them. Confirm part numbers from the BOM before ordering.

When ordering a replacement CUD1, specify whether the firmware is to be pre-loaded. The firmware version is printed on the CUD1 label; firmware 2.x and 3.x have different parameter set layouts, and a CUD1 with a different firmware version will not run the existing parameter dump without conversion.

Closing Notes on the Specific Installation

The reported installation uses two 6RA7096-4MV62-0-Z in parallel. In a parallel configuration, both drives must use the same firmware version and the same parameter set; this is enforced at the cabinet-build stage and is not adjustable in the field. The first check on a parallel 6RA70 pair is therefore to confirm that both drives report the same firmware version under the standard parameter view and that both have the same parameter dump loaded. If the firmware versions differ, parameter sets will be interpreted differently and the analog front end will appear to be at fault when the actual cause is firmware mismatch.

The 6RA7096-4MV62-0-Z designation decodes as: family 6RA70, frame size 96 (large chassis, 2200 A class), -4 = 4-quadrant operation, M = motor / connector variant, V = voltage class, 62 = variant code, -0 = standard, Z = additional option suffixes appended to the order code. The Z suffix must be cross-referenced against the build sheet to confirm the exact hardware revision on the affected units, since some Z-suffix options change the analog front end.

FAQ