Commander SX Drive Fault Codes

-

Troubleshooting guide for the IP66/NEMA 4X Control Techniques Commander SX drive. Learn to decode mnemonic trips, access fault history, and fix hardware faults.

Commander SX Fault Codes Reference Table

Below is the reference list of trips for the Commander SX. Locate the code shown on your drive’s integrated LED display to determine the cause of the protective shutdown.

Control Techniques COMMANDER SX Faults and Diagnostics

Commander SX Faults and Diagnostics

Fault Code and Meaning Cause and Remedy
cL1
ADI1 loss		 Cause: Loss of the current reference on analog input ADI1.

Remedy:
  • Check that current is > 3 mA.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
cL2
ADI2 loss		 Cause: Loss of the current reference on analog input ADI2.

Remedy:
  • Check that current is > 3 mA.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
cL3
ADIO3 loss		 Cause: Loss of the current reference on analog input ADIO3.

Remedy:
  • Check that current is > 3 mA.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
EEF
EEPROM fail.		 Cause: Drive rating does not match with XPressKey.

Remedy:
  • Return to default factory settings (see 65).
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
enC2
Encoder rot		 Cause: The measured position does not vary (the encoder is incorrectly connected or not supplied with power or the shaft is not turning).

Remedy:
  • Check encoder connections.
  • Check the motor rotation is normal.
EnC1
U sign. loss		 Cause: Loss of channel U.

Remedy:
  • Check the speed feedback.
  • Replace the encoder.
EnC2
V sign. loss		 Cause: Loss of channel V.

Remedy:
  • Check the encoder voltage and connections.
EnC3
W sign. loss		 Cause: Loss of channel W.

Remedy:
  • Check the encoder voltage and connections.
Fbus
Fieldbus loss		 Cause: Disconnection of the fieldbus.

Remedy:
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
  • Check fieldbus connections and status.
It.AC
Motor I²t		 Cause: Motor overload I x t.

Remedy:
  • Read the battery value in 4.19.
  • Check that the motor is not overloaded.
  • Adjust the rated speed.
  • Check that the motor rated current is correctly set (06).
  • Speed feedback: check the coupling, and check that the signal is not disturbed.
  • Check the number of motor poles in 62.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
It.br
Brak. resist.		 Cause: Braking resistor overload I x t.

Remedy:
  • Read the battery value in 10.39.
  • Increase the resistor ohmic value.
  • Check that 10.30 and 10.31 are set correctly (braking cycle too long).
  • Check the resistor wiring.
  • Check the integrated transistor.
Oht1
Dv over heat		 Cause: IGBT overheating (sensor).

Remedy:
  • Reduce the motor load, the cycle, the switching frequency and the acceleration and deceleration ramps.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
Oht2
BR over heat		 Cause: Internal resistor overheating (sensor).

Remedy:
  • Reduce the switching frequency.
  • Reduce the cycle and the motor load.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
OI.AC
Over current		 Cause: Overcurrent at drive output.

Remedy:
  • Check motor insulation and connection.
  • Increase acceleration and deceleration rates.
  • Check feedback devices.
  • Check motor cable length.
  • Reduce the speed controller gains 29 (3.10), 30 (3.11) and 3.12.
  • If not already set, perform an autotune 63 = 2.
  • Reduce current controller gains 31 (4.13) and 32 (4.14).
OIbr
Brak.IGBT		 Cause: IGBT braking overcurrent.

Remedy:
  • Check the resistor insulation.
  • Correct the short-circuit at the resistor output.
  • Set a higher resistor ohmic value.
Old1
24V over Id		 Cause: Overload on +24V source or logic output.

Remedy:
  • Check the total current consumption.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
OSP
Over speed		 Cause: Overspeed.

Remedy:
  • The speed is higher than 1.2 times the value of 02.
  • Check that the load is not driving.
  • Check that the overspeed threshold has been set correctly.
  • Adjust the speed loop gains.
  • Set a longer deceleration time.
OU
DC over volt		 Cause: DC bus overvoltage.

Remedy:
  • Provide a braking resistor (optional). If a resistor is already connected, reduce its value (within permitted limits).
  • Check that the mains supply is not disturbed.
  • Check the motor insulation.
  • Set a longer deceleration time in 04.
  • Check the deceleration mode.
ph
In Ph. loss		 Cause: Phase loss. Note: The loss of one phase can only be detected if the active current is between 50% and 100% of the rated value.

Remedy:
  • Check the mains supply (3 phases present and balanced).
  • Check the level of supply voltage (at full load).
Ph.AC
Out Ph. loss		 Cause: Motor phase loss.

Remedy:
  • Check the connection of phases U, V and W in both the motor and the drive.
rot
A/B reversed		 Cause: The a, b, a\, b\ signals are the wrong way round.

Remedy:
  • Reverse 2 motor phases or 2 encoder channels.
rS
Stator res.		 Cause: Stator resistance measurement fault.

Remedy:
  • Adapt the drive power to that of the motor.
  • Check the connection of the motor cables.
SCL
COM loss		 Cause: Serial link fault.

Remedy:
  • Replace the keypad or the cable.
  • Check the connectors between the keypad and the drive.
  • Check that the cable is not damaged.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
Secd
Sec.disable		 Cause: Secure input fault.

Remedy:
  • Give a stop command before enabling the drive.
Th
Motor PTC		 Cause: Motor sensor trip.

Remedy:
  • Check the motor load.
  • Reduce the level of overload.
  • Check the motor cooling and the ambient temperature.
  • Check the wiring of the ADI2 terminal on the control terminal block.
  • If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
tr01 - tr10
User 1 - 10		 Cause: User fault 1 through 10 via logic input or serial link.

Remedy:
  • Check logic inputs or serial communications.
  • For tr05, tr10: If 10.37 = 1 (Ctld), the drive decelerates the motor without tripping.
tun3
UVW revers.		 Cause: The u, v, w switching signals are the wrong way round.

Remedy:
  • Check encoder and motor connections.
tun4
U sign.miss.		 Cause: Some signals are present, but U is missing.

Remedy:
  • Check encoder connections.
tun5
V sign.miss.		 Cause: Some signals are present, but V is missing.

Remedy:
  • Check encoder connections.
tun6
W sign.miss.		 Cause: Some signals are present, but W is missing.

Remedy:
  • Check encoder connections.
tun7
Pole count		 Cause: The number of pairs of poles set is incorrect (the revolutions measured mechanically and electrically are inconsistent).

Remedy:
  • Check encoder lines per revolution.
  • Verify 5.11 (62) "number of motor poles" setting.
tunE
Autotun. fail		 Cause: Autocalibration error.

Remedy:
  • Drive set to fault mode during the autocalibration phase.
  • The Stop key has been pressed.
  • The SDI2 contact has been opened during the autocalibration phase.
UU
Under volt.		 Cause: DC bus undervoltage.

Remedy:
  • Check the mains supply.
 

How to Read SX Faults via Parameters

The Commander SX may be physically rugged, but its internal logic is sophisticated. In 2026, the best way to troubleshoot an intermittent trip is to access the drive’s internal trip log via the keypad or serial communications.

  • Trip History (Menu 10): The drive automatically stores the last 10 trips in Parameters 10.20 through 10.29.
    • Pr 10.20: Shows the most recent trip.
    • Pr 10.21 – 10.29: Shows previous trips in order of occurrence.
  • Status Indicators:
    • rd: Ready (The drive is healthy).
    • ih: Inhibit (The drive is safe but cannot run because the Enable/STO signal is missing).
    • tr: Tripped (A fault has occurred).
  • Connect Software: For deep diagnostics, the SX can be connected to a PC using the CT-USB-Cable. This allows you to view the trip log with precise run-hour timestamps and monitor the DC bus voltage and output current in real-time.

Frequently Asked Questions (FAQ)

Q: What is the difference between a Trip and a Warning?

A: A Trip (Solid code) indicates a critical error that has stopped the motor. A Warning (Flashing code) indicates a “near-trip” condition, such as Hot (Heatsink Alarm), where the drive is still running but will trip soon if the temperature is not reduced.

Q: How do I reset a Commander SX trip?

A: Once the fault condition is resolved, you can reset the drive by:

  • Pressing the Red Reset Button on the keypad.
  • Toggling a Digital Input that has been programmed for the “Reset” function.
  • Cycling the Main Power (Wait until the display goes completely dark before turning it back on).

Q: Where is the fault history stored?

A: The fault history is stored in Menu 10. It is non-volatile, meaning the records stay in the log even if the drive is powered off or loses its supply. Newer trips will eventually push older trips out of the 10-slot memory.

Q: What does “HF” mean on the display?

A: “HF” stands for Hardware Fault. These are internal power-stage or control-circuit errors (e.g., HF01 to HF20). Because the SX is sealed for IP66 protection, an HF fault often requires professional service as the internal components are not easily accessible for field repair.

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