New Version Siemens Cuvc Board 6SE7090-0XX84-0AB0 6SE70900XX840AB0 6SE7O9O-OXX84-OABO 6SE7 090-0XX84-0AB0

Siemens 6SE7090-0XX84-0AB0 | SIMOVERT MASTERDRIVES CUVC Control Module — Vector Control, Open/Closed Loop

Part Number: 6SE7090-0XX84-0AB0

Manufacturer: Siemens AG (Germany)

Product Type: CUVC — Closed-Loop/Open-Loop Vector Control Module

Product Range: SIMOVERT MASTERDRIVES

Control Mode: Vector Control (open-loop and closed-loop)

Overview

The 6SE7090-0XX84-0AB0 is the CUVC — Closed-Loop and Open-Loop Vector Control module — for the Siemens SIMOVERT MASTERDRIVES AC drive platform.

This is the drive's control intelligence: the board that executes the vector control algorithm, manages the closed-loop current and speed regulation loops, handles all digital and analog I/O interfacing, and communicates with upstream automation systems over its serial interfaces. 

It replaces or serves as the primary control board across the full range of SIMOVERT MASTERDRIVES configurations where vector control is the specified operating mode.

The SIMOVERT MASTERDRIVES system built its reputation on high-performance AC motor control.

Vector control — also known as field-oriented control — fundamentally changed what was achievable with AC drives when it was introduced. By computing and separately controlling the flux-producing and torque-producing components of the motor current, vector control delivers dynamic performance approaching that of a DC drive, with the mechanical simplicity and reduced maintenance of a squirrel-cage induction motor.

The 6SE7090-0XX84-0AB0 implements this capability in both closed-loop (with speed feedback from an encoder or tachometer) and open-loop (without speed feedback, using mathematical motor model estimation).

Closed-loop mode delivers the highest accuracy and stiffest speed regulation; open-loop mode provides very good performance without the cabling and maintenance overhead of an encoder.

Key Specifications

Vector Control — Open Loop vs Closed Loop

The 6SE7090-0XX84-0AB0 supports both control variants, each suited to different application requirements.

In closed-loop vector control, an incremental encoder mounted on the motor shaft sends speed feedback to the CUVC module through its HTL encoder input terminal strip. The control loop compares the measured speed against the setpoint and adjusts the motor current vectors in real time.

This produces very stiff speed regulation — the drive actively corrects for load variations to hold the commanded speed accurately. It is the correct choice for precision applications: winding systems, positioning drives, tension control, and anywhere that speed accuracy under varying load is critical.

Open-loop vector control removes the encoder and instead uses the drive's mathematical motor model to estimate rotor speed from the measured stator current and voltage.

This estimation, combined with the vector control algorithm, gives dynamic performance substantially better than basic V/f (scalar) control, with no external encoder hardware to install or maintain. Many pump, fan, compressor, and general industrial drive applications run comfortably on open-loop vector control.

Interfaces and Connectivity

The RS232/RS485 serial interface on the 6SE7090-0XX84-0AB0 connects to a PC running MASTERDRIVES Drive Monitor software or to an OP1S operator panel. The OP1S gives field technicians a local parameter display and modification interface.

Drive Monitor allows more detailed commissioning, parameter backup, diagnostic trace capture, and firmware management from a laptop computer connected at the drive cabinet.

The USS bus (RS485) allows the CUVC to operate as a node on a multi-drive network.

A single RS485 cable daisy-chained across multiple drives allows a PLC or SCADA system to set speed references, read actual values, and monitor fault states for each drive on the bus without individual point-to-point wiring.

The configurable digital I/Os on the module handle local drive enable/disable, direction commands, run/stop signals, and fault reset functions.

The analog inputs accept both current (0–20mA / 4–20mA) and voltage (0–10V) speed reference signals from PLCs, process controllers, or operator potentiometers.

Commissioning and Parameter Notes

The CUVC firmware V3.4 on this board supports the standard MASTERDRIVES parameterisation procedure. Motor data — nameplate values of voltage, current, frequency, speed, and power — must be entered, and the drive runs a motor identification routine to determine the actual motor equivalent circuit parameters.

After auto-tuning, the vector control gains are computed from the identified motor parameters. The drive is then ready for load commissioning.

Parameters are stored in the CUVC module's non-volatile memory and are retained when power is removed. If the CUVC module is replaced, all parameters must be re-entered or loaded from a backup file.

Keeping a Drive Monitor parameter backup on file for every drive is strongly recommended maintenance practice.

FAQ

Q1: The SIMOVERT MASTERDRIVES generates fault F011 (drive overtemperature) when running closed-loop at rated current. The heatsink is confirmed not hot. Could the 6SE7090-0XX84-0AB0 be the cause?

F011 at normal heatsink temperature points to a fault in the temperature monitoring circuit on the CUVC board rather than a genuine overtemperature condition.

The motor temperature sensor input (NTC/KTY84) on the CUVC module, or the heatsink temperature sensor connection, may have an open-circuit or incorrect resistance reading. 

Check the sensor wiring and connector at the CUVC terminal strip. 

If the wiring is confirmed intact and the fault persists, the CUVC module's sensor input circuit may have failed.

Q2: The drive runs correctly on open-loop vector control but gives rough speed regulation on closed-loop. The encoder cable and connections have been checked. What should be examined next?

Rough speed regulation in closed-loop mode typically indicates either an incorrectly set speed control gain (P-gain too high produces oscillation; too low gives sluggish response) or an encoder pulse count entered incorrectly in the drive parameters.

Confirm that the encoder PPR (pulses per revolution) entered in the relevant CUVC parameter matches the actual encoder specification. 

Also verify that the HTL level of the encoder signal is within the CUVC module's input specification. If parameters are confirmed correct and the hardware is good, a partial failure of the CUVC module's encoder input circuit is possible.

Q3: After replacing the 6SE7090-0XX84-0AB0, the drive powers on but shows F015 (motor data not plausible). What should be done?

F015 after a board replacement indicates that the motor parameters stored in the old CUVC's memory were lost when the board was changed, and the new board's default motor data does not match the connected motor.

Re-enter the motor nameplate data (P100–P115 series in standard MASTERDRIVES parameterisation) and run the motor identification routine.

If a Drive Monitor backup from the original board is available, upload the full parameter set to the replacement board.

Q4: Can the 6SE7090-0XX84-0AB0 be used in any SIMOVERT MASTERDRIVES chassis size, or is it specific to a design range?

The 6SE7090-0XX84-0AB0 CUVC module is designed to plug into the electronics box of SIMOVERT MASTERDRIVES units across the standard chassis range (designs A through H and larger).

The XX in the part number is a wildcard indicating that this board serves multiple chassis configurations. 

The same CUVC board hardware is used regardless of the drive's power output — the drive's power rating is determined by the connected Power Electronics, not by the CUVC. Confirm the firmware version compatibility with the specific drive design before installing.

Q5: The drive is being replaced with a new SINAMICS platform. Can the parameter settings from the 6SE7090-0XX84-0AB0 be migrated to the new drive?

Parameter sets from MASTERDRIVES CUVC modules are in the MASTERDRIVES format and are not directly compatible with SINAMICS parameter structures.

The two platforms use different parameter numbering, different motor model approaches, and different commissioning software (MASTERDRIVES Drive Monitor vs STARTER/TIA Portal). Migration requires re-commissioning the new SINAMICS drive from the motor nameplate data and performing a new motor identification. 

The old MASTERDRIVES parameter backup serves as a reference for application-level settings (speeds, ramp times, I/O function assignments), but each parameter must be translated to its SINAMICS equivalent.