Commander SE Drive Fault Codes

-

Troubleshooting guide for the legacy Control Techniques Commander SE drive. Learn to interpret mnemonic trips like OI.AC, OV, and HF, access the trip log, and perform resets.

Commander SE Fault Codes Reference Table

Below is the reference list of trips for the Commander SE. These codes are displayed on the front panel when the drive enters a fault state and stops the motor.

Commander SE Drive Fault Codes

Commander SE Trip Codes & Diagnostics

Fault Code and Meaning Cause and Remedy
UU (1)
DC link under voltage		 Cause:
Low AC supply voltage.
Low DC link voltage when supplied by external DC power supply.

Remedy:
Check power supply voltage.
OU (2)
DC link over voltage		 Cause:
Excessive inertia in the machine during deceleration.
Deceleration rate set too fast for inertia of machine.

Remedy:
Adjust deceleration ramp times.
Check for overvoltage trip levels (200V units: 420VDC, 400V units: 830VDC).
OI.AC** (3)
AC instantaneous over current trip		 Cause:
Insufficient ramp times.
Phase to phase or phase to earth short-circuit at the Drive output.

Remedy:
Drive requires autotuning to motor (see parameter 38).
Note: These trips cannot be reset for 10 seconds.
OI.br** (4)
Overcurrent on braking IGBT		 Cause:
Excessive current in braking resistor.
Braking resistor value too small (Does not apply to Size 1 units).

Remedy:
Check braking resistor values.
Note: These trips cannot be reset for 10 seconds.
Et (6)
External trip		 Cause:
External trip terminal opened (when programmed).

Remedy:
Check external circuit connected to trip terminal.
O.SP (7)
Over speed		 Cause:
Excessive motor speed (typically caused by the mechanical load driving the motor).

Remedy:
Check mechanical load conditions.
tunE (18)
Auto-tune failure		 Cause:
Motor loaded or no motor connected.

Remedy:
Ensure motor is connected and free to rotate if necessary.
It.br (19)
I x t on braking resistor		 Cause:
Excessive braking resistor energy (Does not apply to Size 1 units).

Remedy:
Check braking cycles and resistor sizing.
It.AC (20)
Motor overload on current x time		 Cause:
Too much mechanical load.

Remedy:
Reduce mechanical load or check motor sizing.
Oht1 (21)
Overheat		 Cause:
Overheat thermal model.

Remedy:
Check drive ventilation and ambient temperature.
Oht2 (22)
Overheat (heatsink thermistor)		 Cause:
Temperature exceeds 95°C (203°F).

Remedy:
Check heatsink cooling and fans.
th (24)
Over temperature (Motor thermistor)		 Cause:
Excessive motor temperature.

Remedy:
Check motor cooling and load.
O.Ld1* (26)
+24V or digital output overload		 Cause:
Excessive load or short circuit on +24V output.

Remedy:
Check wiring on +24V output.
The Enable/Reset terminal will not reset an O.Ld1 trip. Use the Stop/Reset key.
cL (28)
Current loop loss on terminal 5		 Cause:
Input current less than 3mA when 4-20 or 20-4 modes used.

Remedy:
Check current loop signal source and wiring.
SCL (30)
User serial communications watchdog failure		 Cause:
Failure of serial communications between Drive and master.

Remedy:
Check serial communication cables and master status.
EEF (31)
Failure of internal EEPROM		 Cause:
Possible loss of parameter values.
Corruption due to severe electrical noise.

Remedy:
Set default parameters (see parameter 29).
PH (32)
Phase loss		 Cause:
One of the input phases has become disconnected from the Drive. (This applies to 200V/400V three phase units only, not dual rated units).

Remedy:
Check input supply fuses and wiring.
rS (33)
Stator resistance measurement failure		 Cause:
Motor cable disconnected during measurement.
Motor too small for Drive.

Remedy:
See parameter 38 for more details.
trxx (40-99)
User trips		 Cause:
User trips where xx is the user trip number.

Remedy:
Check user program or PLC logic generating the trip.
F.bus (180)
Field bus disconnection		 Cause:
Field bus disconnection whilst in use.

Remedy:
Check field bus cables and connections.
C.Err (182)
Quickey memory corrupt		 Cause:
Bad connection or memory corrupt.

Remedy:
Check Quickey insertion or replace Quickey.
C.dat (183)
Quickey with no data		 Cause:
New / empty Quickey being read.

Remedy:
Program Quickey before reading.
C.Acc (185)
Quickey write fail		 Cause:
Bad connection or faulty Quickey.

Remedy:
Re-insert or replace Quickey.
C.rtg (186)
Quickey voltage rating change		 Cause:
Already programmed Quickey read by Drive of different rating.

Remedy:
Use Quickey compatible with drive rating.
O.Ld2 (188)
+28V serial communications power supply overload		 Cause:
Overload of more than 110 mA or short circuit on +28V serial communications power supply.

Remedy:
Check serial comms wiring for shorts or excessive load.
O.cL (189)
Current loop input overload		 Cause:
Input current exceeded 25mA.

Remedy:
Check current source signal level.
(No Code)
Motor runs unstable		 Cause:
Motor or motor connections changed.

Remedy:
Check motor connections.
Re-autotune Drive to motor (see parameter 38).
 

How to Read Commander SE Faults via Parameters

Because the Commander SE predates modern mobile apps and USB connectivity, diagnostics are performed primarily through the keypad by accessing specific parameters.

  • The Trip Log (Pr 10.20 to 10.29): The Commander SE stores its last 10 trips.
    • Pr 10.20: Displays the most recent trip code.
    • Pr 10.21 – 10.29: Displays previous trips in descending order.
  • Status Indicators: When the drive is not tripped, the display shows the drive status:
    • rd: Ready (Drive is healthy and waiting for a run command).
    • ih: Inhibit (Drive is disabled, usually due to a missing enable signal).
    • tr: Tripped (The drive has encountered a fault).
  • SESoft Tool: For those with the correct serial lead (RS232/485), the legacy SESoft software can still be used in 2026 to view parameters and fault history on a PC.

Frequently Asked Questions (FAQ)

Q: How do I reset a Commander SE fault?

A: Once the cause of the trip is fixed, you can reset the drive by:

  • Pressing the Red Reset Button on the keypad.
  • Toggling the Digital Input assigned to the Reset function (Terminal 12 by default).
  • Cycling the Input Power (Wait 30 seconds for the internal capacitors to discharge before reapplying power).

Q: What is the most common trip on an aging Commander SE?

A: In 2026, many SE drives trip on It.AC (Motor Thermal Overload) or UV (Under Voltage). UV trips are frequently caused by drying electrolytic capacitors on the internal power board, a common side effect of the drive’s age.

Q: Can I clear the fault history?

A: No, the fault history is a rolling log. New trips will push older trips out of the 10-slot memory. However, performing a “Load Defaults” (setting Pr 00.29 to EUR or USA) will reset most parameters, but the trip log is generally retained for diagnostic purposes.

Q: What does “OI.AC” mean?

A: This stands for Overcurrent (AC). The drive has detected a peak current exceeding its safety threshold. This is usually caused by a short circuit in the motor cables, a grounded motor winding, or an extremely aggressive acceleration ramp.

Comments

Post a Comment

Popular posts from this blog

3210 DC bus overvoltage fault in lenze i550 drive

-
Fault Code 3210 in a Lenze i550 drive indicates a DC bus overvoltage fault . This means the voltage on the DC bus within the drive has exceeded its safe operating limit. Potential Causes Drive Internal Components: A fault in the drive's rectifier, smoothing capacitor, or control circuitry. Solution: This often requires professional inspection and repair or replacement of the faulty component. Power Supply Issues: Excessive AC voltage input to the drive. Solution: Check the power supply for voltage fluctuations or overvoltage conditions. Motor Issues: A short circuit or other fault within the motor can cause excessive back EMF, leading to DC bus overvoltage. Solution: Inspect the motor for any signs of damage or malfunction. Drive Configuration Issues: Incorrectly configured drive parameters, such as excessive regeneration or improper motor data. Solution: Review and adjust drive parameters to match the motor and application requirements. Troubleshooting Steps Check Power ...
Read more

7180 Motor overcurrent fault in lenze i550 drive

-
Fault Code 7180 in a Lenze i550 drive indicates a motor overcurrent fault . This means the motor connected to the drive is drawing more current than its rated capacity, which can lead to overheating and potential damage. Potential Causes Overloaded Motor: The motor is being asked to do more work than it's designed for. Solution: Reduce the load on the motor or ensure it's rated for the required power. Mechanical Issues: Jamming: The motor or its connected machinery might be jammed, causing excessive current draw. Friction: Increased friction due to misalignment or worn components can lead to higher currents. Solution: Check for mechanical obstructions, ensure proper alignment, and replace worn parts if necessary. Electrical Problems: Short Circuit: A short circuit within the motor windings can cause excessive current. Incorrect Wiring: Improper connections can lead to overloading. Solution: Inspect for short circuits, verify wiring diagrams, and correct any issue...
Read more

FF06 Motor overspeed fault in lenze i550 drive

-
Fault Code FF06 in a Lenze i550 drive indicates a motor overspeed fault . This means the motor connected to the drive is spinning at a speed that exceeds its rated maximum speed. Potential Causes Drive Configuration Issues: Incorrectly set maximum speed limit or frequency. Solution: Verify and adjust drive parameters to match the motor's specifications. Mechanical Problems: Jamming or Binding: Obstructions in the mechanical system can cause the motor to accelerate beyond its rated speed. Loose Coupling: A loose coupling between the motor and the driven load can lead to overspeed. Solution: Check for mechanical obstructions, ensure proper alignment, and tighten couplings as needed. Sensor Issues: A faulty speed sensor or incorrect sensor calibration can provide inaccurate speed readings, leading to overspeed. Solution: Verify the sensor's functionality, calibrate it if necessary, or replace it if faulty. Drive Internal Components: A fault within the drive's contr...
Read more