Comprehensive guide to Control Techniques Commander C200 drive trips. Learn how to diagnose OI.AC, It.AC, and Ph.lo errors, use “Connect” software, and reset fault.

Commander C200 Fault Codes Reference Table

Below is the complete reference list of trips for the Commander C series. Use the table below to cross-reference the abbreviation appearing on your drive’s display.

Commander C200 Drive Fault Codes

Fault Code and Meaning	Cause and Remedy
C.Acc (185) NV Media Card Write fail	Cause: The C.Acc trip indicates that the drive was unable to access the NV Media Card. If the trip occurs during the data transfer to the card then the file being written may be corrupted. If the trip occurs when the data being transferred to the drive then the data transfer may be incomplete. If a parameter file is transferred to the drive and this trip occurs during the transfer, the parameters are not saved to non-volatile memory, and so the original parameters can be restored by powering the drive down and up again. Remedy: Check NV Media Card is installed / located correctly. Replace the NV Media Card.
C.by (178) NV Media Card cannot be accessed as it is being accessed by an option module	Cause: The C.by trip indicates that an attempt has been made to access a file on NV Media Card, but the NV Media Card is already being accessed by an Option Module. No data is transferred. Remedy: Wait for the option module to finish accessing the NV Media Card and re-attempt the required function.
C.cPr (188) NV Media Card file/data is different to the one in the drive	Cause: A compare has been carried out between a file on the NV Media Card and the drive, a C.cPr trip is initiated if the parameters on the NV Media Card are different to the drive. Remedy: Set Pr 00 to 0 and reset the trip. Check to ensure the correct data block on the NV Media Card has been used for the compare.
C.d.E (179) NV Media Card data location already contains data	Cause: The C.d.E trip indicates that an attempt has been made to store data on a NV Media Card in a data block which already contains data. Remedy: Erase the data in data location. Write data to an alternative data location.
C.dAt (183) NV Media Card data not found	Cause: The C.dAt trip indicates that an attempt has been made to access a non-existent file on the NV Media Card. No data is transferred. Remedy: Ensure data file number is correct.
C.Err (182) NV Media Card data structure error	Cause: The C.Err trip indicates that an attempt has been made to access the NV Media Card but an error has been detected in the data structure on the card. Resetting the trip will cause the drive to erase and create the correct folder structure. On an SD card, whilst this trip is present, missing directories will be created and if the header file is missing it will be created. The cause of the trip can be identified by the sub-trip: Sub-trip Reason 1 The required folder and file structure is not present 2 The 000.DAT file is corrupted 3 Two or more files in the <MCDF\> folder have the same file identification number Remedy: Erase all the data block and re-attempt the process. Ensure the card is located correctly. Replace the NV Media Card.
C.Ful (184) NV Media Card full	Cause: The C.Ful trip indicates that an attempt has been made to create a data block on a NV Media Card, but there is not enough space left on the card. No data is transferred. Remedy: Delete a data block or the entire NV Media Card to create space. Use a different NV Media Card.
C.OPt (180) NV Media Card trip; option module installed is different between source drive and destination drive	Cause: The C.OPt trip indicates that parameter data is being transferred from the NV Media Card to the drive, but the option module category is different between the source and destination drives. This trip does not stop the data transfer, but is a warning that the data for the option module that is different will be set to the default values and not the values from the card. This trip also applies if a compare is performed between the data block on the card and the drive, and the option module fitted is different between the source and target. Remedy: Ensure the correct option module is installed. Press the red reset button to acknowledge that the parameters for the option module installed will be at their default values. This trip can be suppressed by setting Pr 00 to 9666 and resetting the drive.
C.Pr (175) NV Media Card data blocks are not compatible with the drive derivative	Cause: The C.Pr trip is initiated either at power-up or when the card is accessed. If Drive Derivative (11.028) or Product Type (11.063) are different between the source and target drives. This trip can be reset and data can be transferred in either direction between the drive and the card. Sub-trip Reason 1 If Drive Derivative (11.028) is different between the source and target drives. This trip is initiated either at power-up or when the SD card is accessed. 2 If Product Type (11.063) is different between the source and target drives or the file is corrupted or incompatible. Remedy: Use a different NV Media Card. This trip can be suppressed by setting Pr 00 to 9666 and resetting the drive. Choose a file compatible between the source and target drives, if sub-trip 2.
C.rdo (181) NV Media Card has the Read Only bit set	Cause: The C.rdo trip indicates that an attempt has been made to modify data on a read-only NV Media Card or to modify a read-only data block. A NV Media Card is read-only if the read-only flag has been set. Remedy: Clear the read only flag by setting Pr 00 to 9777 and reset the drive. This will clear the read-only flag for all data blocks in the NV Media Card.
C.rtg (186) NV Media Card Trip; The voltage and / or current rating of the source and destination drives are different	Cause: The C.rtg trip indicates that parameter data is being transferred from the NV Media Card to the drive, but the current and / or voltage ratings are different between source and destination drives. This trip also applies if a compare (using Pr mm.000 set to 8yyy) is performed between the data block on a NV Media Card and the drive. The C.rtg trip does not stop the data transfer but is a warning that rating specific parameters with the RA attribute may not be transferred to the destination drive. Remedy: Reset the drive to clear the trip. Ensure that the drive rating dependent parameters have transferred correctly. This trip can be suppressed by setting Pr 00 to 9666 and resetting the drive.
C.SL (174) NV Media Card trip; Option module file transfer has failed	Cause: The C.SL trip is initiated, if the transfer of an option module file to or from a module failed because the option module does not respond correctly. If this happens this trip is produced with the sub-trip number indicating the option module slot number. Remedy: Check module installation and compatibility.
C.tyP (187) NV Media Card parameter set not compatible with current drive mode	Cause: The C.tyP trip is produced during a compare if the drive mode in the data block on the NV Media Card is different from the current drive mode. This trip is also produced if an attempt is made to transfer parameters from a NV Media Card to the drive if the operating mode in the data block is outside the allowed range of operating modes, for the target drive. Remedy: Ensure the destination drive supports the drive operating mode in the parameter file. Clear the value in Pr 00 and reset the drive. Ensure destination drive operating mode is the same as the source parameter file.
cL.A1 (28) Analog input 1 current loss	Cause: The cL.A1 trip indicates that a current loss was detected in current mode on Analog input 1 (Terminal 2). In 4-20 mA and 20-4 mA modes loss of input is detected if the current falls below 3 mA. Remedy: Check control wiring is correct. Check control wiring is undamaged. Check the Analog Input 1 Mode (07.007). Current signal is present and greater than 3 mA.
CL.bt (35) Trip initiated from the Control Word (06.042)	Cause: The CL.bt trip is initiated by setting bit 12 on the control word in Pr 06.042 when the control word is enabled (Pr 06.043 = On). Remedy: Check the value of Pr 06.042. Disable the control word in Control Word Enable (Pr 06.043). Bit 12 of the control word set to a one causes the drive to trip on Control Word. When the control word is enabled, the trip can only be cleared by setting bit 12 to zero.
Cur.c (231) Current calibration range	Cause: Current calibration range error. Remedy: Hardware fault - Contact the supplier of the drive.
Cur.O (225) Current feedback offset error	Cause: The Cur.O trip indicates that the current offset is too large to be trimmed. Remedy: Ensure that there is no possibility of current flowing in the output phases of the drive when the drive is not enabled. Hardware fault – Contact the supplier of the drive.
d.Ch (97) Drive parameters are being changed	Cause: A user action or a file system write is active that is changing the drive parameters and the drive has been commanded to enable, i.e. Drive Active (10.002) = 1. The user actions that change drive parameters are loading defaults, changing drive mode, or transferring data from an NV memory card to the drive. The file system actions that will cause this trip to be initiated if the drive is enabled during the transfer is writing a parameter or macro file to the drive. Remedy: Ensure the drive is not enabled when one of the following is being carried out: Loading defaults Changing drive mode Transferring data from NV media card
dcct (110) dcct reference out of range for size 5 upwards only	Cause: The sub-trip number indicates the DCCT that has caused the trip. Remedy: Hardware fault - Contact the supplier of the drive.
dEr.E (246) Derivative file error	Cause: Derivative file error with sub-trips: Sub-trip Reason Comments 1 The derivative file is missing or is invalid Occurs when the drive powers-up. Load valid derivative file matching the control board hardware. 2 The derivative file does not match the control board hardware Occurs when the drive powers-up. Load valid derivative file matching the control board hardware. 3 The derivative file has been changed for a file with a different derivative number. Occurs when the drive powers-up or the file is programmed. The file tasks will not run. Remedy: Contact the supplier of the drive.
dEr.I (248) Derivative product image error	Cause: The dEr.I trip indicates that an error has been detected in the derivative product image. The reason for the trip can be identified by the sub-trip number. Sub-trip Reason 1 Divide by zero 2 Undefined trip 3 Attempted fast parameter access set-up with non-existent parameter 4 Attempted access to non-existent parameter 5 Attempted write to read-only parameter 6 Attempted an over-range write 7 Attempted read from write-only parameter 30 The image has failed because either its CRC is incorrect, or there are less than 6 bytes in the image... 31 The image requires more RAM for heap and stack than can be provided by the drive. 32 The image requires an OS function call that is higher than the maximum allowed. 33 The ID code within the image is not valid. 34 The derivative image has been changed for an image with a different derivative number. 40 The timed task has not completed in time and has been suspended. 41 Undefined function called, i.e. a function in the host system vector table that has not been assigned. 51 Core menu customization table CRC check failed. 52 Customizable menu table CRC check failed. 53 Customizable menu table changed. 61 The option module installed in slot 1 is not allowed with the derivative image. 80 Image is not compatible with the control board. 81 Image is not compatible with the control board serial number. Remedy: Contact the supplier of the drive.
dESt (199) Two or more parameters are writing to the same destination parameter	Cause: The dESt trip indicates that destination parameters of two or more functions (Menus 7, 8, 9, 12 or 14) within the drive are writing to the same parameter. Remedy: Set Pr 00 to 'dest' or 12001 and check all visible parameters in all menus for parameter write conflicts.
dr.CF / 232 Drive configuration	Cause: The hardware ID does not match the user software ID. Remedy: Hardware fault - Contact the supplier of the drive.
EEF / 31 Default parameters have been loaded	Cause: The EEF trip indicates that default parameters have been loaded. This occurs if parameter banks in non-volatile memory are corrupted (e.g., power removed during save). Remedy: Default the drive and perform a reset. Allow sufficient time to perform a save before the supply to the drive is removed. If the trip persists - return drive to supplier.
Et / 6 An External trip is initiated	Cause: An external trip has occurred. Can be initiated via sub-trip or by writing a value of 6 in Pr 10.038. Remedy: Check the value of Pr 10.032. Select ‘dest’ (or enter 12001) in Pr 00 and check for a parameter controlling Pr 10.032. Ensure Pr 10.032 or Pr 10.038 (= 6) is not being controlled by serial comms.
FAn.F / 173 Fan fail	Cause: The drive fan has failed or is obstructed. Cannot be reset until 10s after trip initiation. Remedy: Check that the fan is installed and connected correctly. Check that the fan is not obstructed. Contact the supplier of the drive to replace the fan.
Fi.Ch / 247 File changed	Cause: File changed event detected. Remedy: Power cycle the drive.
FI.In / 237 Firmware incompatibility	Cause: The user firmware is incompatible with the power firmware. Remedy: Re-program the drive with the latest version of the drive firmware for the Commander C200/C300, using Connect.
HF01 Data processing error: CPU hardware fault	Cause: CPU address error has occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF02 Data processing error: CPU memory management fault	Cause: DMAC address error has occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF03 Data processing error: CPU has detected a bus fault	Cause: Bus fault occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF04 Data processing error: CPU has detected a usage fault	Cause: Usage fault occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF07 Data processing error: Watchdog failure	Cause: Watchdog failure occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF08 Data processing error: CPU Interrupt crash	Cause: CPU interrupt crash occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF09 Data processing error: Free store overflow	Cause: Free store overflow occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF11 Data processing error: Non-volatile memory comms error	Cause: Non-volatile memory comms error. Control PCB failure. Remedy: Hardware fault – contact the supplier of the drive. (If sub-trip 2): Re-program drive with compatible user firmware.
HF12 Data processing error: Main program stack overflow	Cause: Main program stack overflow has occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF16 Data processing error: RTOS error	Cause: RTOS error has occurred. Control PCB failure. Remedy: Hardware fault – Contact the supplier of the drive.
HF18 Data processing error: Internal flash memory has failed	Cause: Internal flash memory failed when writing option module parameter data. Remedy: Hardware fault - contact the supplier of the drive.
HF19 Data processing error: CRC check on the firmware has failed	Cause: CRC check on drive firmware failed. Drive is in bootloader mode. Remedy: Re-program the drive with latest control and power firmware using Connect. Hardware fault - Contact the supplier of the drive.
HF23 Hardware fault	Cause: General hardware fault. Remedy: If this trip occurs, contact the supplier of the drive.
It.Ac / 20 Output current overload timed out (I2t)	Cause: Motor thermal overload based on Motor Rated Current and Motor Thermal Time Constant. Remedy: Ensure the load is not jammed / sticking. Check the load on the motor has not changed. Tune the motor rated speed parameter (Pr 05.008) (RFC-A mode only). Ensure the motor rated current is not zero.
It.br / 19 Braking resistor overload timed out (I2t)	Cause: Braking resistor overload has timed out. Accumulator reached 100%. Remedy: Ensure the values entered in Pr 10.030, Pr 10.031 and Pr 10.061 are correct. Check resistor value and power rating. If an external thermal protection device is used, disable software protection by setting parameters to 0.
LF.Er / 90 Communication has been lost	Cause: Lost communications between power, control, or rectifier modules. Remedy: Hardware fault - contact the supplier of the drive.
no.PS / 236 No power board	Cause: No communication between the power and control boards. Remedy: Hardware fault - contact the supplier of the drive.
O.Ld1 / 26 Digital output overload	Cause: Total current drawn from the AI Adaptor 24 V or from the digital output has exceeded the limit. Remedy: Check total loads on digital outputs and 24 V. Check control wiring is correct. Check output wiring is undamaged.
O.SPd / 7 Motor frequency has exceeded the over frequency threshold	Cause: Post-ramp Reference or Estimated Frequency exceeded the threshold set in Pr 03.008. Remedy: Reduce the Frequency Controller Proportional Gain (03.010) to reduce frequency overshoot (RFC-A mode only). Check that a mechanical load is not driving motor. Reduce Current Controller Ki Gain (04.014).
Oht.C / 219 Control stage over temperature	Cause: Control stage over-temperature detected. Remedy: Increase ventilation by setting Cooling Fan control (06.045) > 0.
Oh.dc (27) DC bus over temperature	Cause: DC bus component over temperature based on a software thermal model. The drive includes a thermal protection system to protect the DC bus components within the drive. Remedy: Check the AC supply voltage balance and levels. Check DC bus ripple level. Reduce duty cycle. Reduce motor load. Check the output current stability. If unstable, check motor map settings (Pr 05.006 - 05.011). Disable slip compensation (Pr 05.027 = 0) (Open loop). Disable dynamic V to F operation (Pr 05.013 = 0) (Open loop). Select fixed boost (Pr 05.014 = Fixed) (Open loop). Select high stability space vector modulation (Pr 05.019 = 1) (Open loop). Disconnect the load and complete a rotating auto-tune (Pr 05.012). Reduce frequency loop gains (Pr 03.010 - 03.012) (RFC-A).
Oht.I (21) Inverter over temperature based on thermal model	Cause: An IGBT junction over-temperature has been detected based on a software thermal model. The trip is initiated when the thermal model reaches 145 °C. Remedy: Reduce the selected drive switching frequency. Ensure Auto-switching Frequency Change Disable (05.035) is set to Off. Reduce duty cycle. Increase acceleration / deceleration rates. Reduce motor load. Check DC bus ripple. Ensure all three input phases are present and balanced.
Oht.P (22) Power stage over temperature	Cause: A power stage over-temperature has been detected. From the sub-trip 'xxyzz', the Thermistor location is identified by 'zz'. Remedy: Check enclosure / drive fans are still functioning correctly. Force the heatsink fans to run at maximum speed. Check enclosure ventilation paths. Check enclosure door filters. Increase ventilation. Reduce the drive switching frequency. Reduce duty cycle. Increase acceleration / deceleration rates. Use S-ramp (Pr 02.006). Reduce motor load. Check the derating tables and confirm the drive is correctly sized. Use a drive with larger current / power rating.
OI.A1 (189) Analog input 1 over-current	Cause: Current input on analog input 1 exceeds 24 mA. Remedy: Check wiring and source signal for Analog Input 1.
OI.AC (3) Instantaneous output over current detected	Cause: The instantaneous drive output current has exceeded VM_DRIVE_CURRENT_MAX. This trip cannot be reset until 10s after trip initiation. Remedy: Increase acceleration/deceleration rate. If seen during auto-tune reduce the voltage boost. Check for short circuit on the output cabling. Check integrity of the motor insulation using an insulation tester. Is the motor cable length within limits for the frame size? Reduce the values in the frequency loop gain parameters (Pr 03.010, 03.011, 03.012) or (Pr 03.013, 03.014, 03.015). Reduce the values in the current loop gain parameters.
OI.br (4) Braking IGBT over current detected	Cause: Over current has been detected in braking IGBT or braking IGBT protection has been activated. Cannot be reset until 10s after trip. Remedy: Check brake resistor wiring. Check braking resistor value is greater than or equal to the minimum resistance value. Check braking resistor insulation.
OI.SC (228) Output phase short-circuit	Cause: Over-current detected on drive output when enabled. Possible motor earth fault. Remedy: Check for short circuit on the output cabling. Check integrity of the motor insulation using an insulation tester. Is the motor cable length within limits for the frame size?
OI.Sn (92) Snubber over-current detected	Cause: An over-current condition has been detected in the rectifier snubbing circuit. Remedy: Ensure the internal EMC filter is installed. Ensure the motor cable length does not exceed the maximum for selected switching frequency. Check for supply voltage imbalance. Check for supply disturbance such as notching from a DC drive. Check the motor and motor cable insulation with an insulation tester. Fit an output line reactor or sinusoidal filter.
Out.P (98) Output phase loss detected	Cause: Phase loss has been detected at the drive output. Remedy: Check motor and drive connections. To disable the trip set Output Phase Loss Detection Enable (06.059) = 0.
OV (2) DC bus voltage exceeded peak or maximum continuous level	Cause: The DC bus voltage has exceeded the VM_DC_VOLTAGE[MAX] or VM_DC_VOLTAGE_SET[MAX] for 15 s. Remedy: Increase deceleration ramp (Pr 04). Decrease the braking resistor value (staying above the minimum value). Check nominal AC supply level. Check for supply disturbances which could cause the DC bus to rise. Check motor insulation using an insulation tester.
P.dAt (220) Power system configuration data error	Cause: There is an error in the configuration data stored in the power system. Remedy: Hardware fault – Contact the supplier of the drive.
PAd (34) Keypad has been removed	Cause: The drive is in keypad mode [Reference Selector (01.014) = 4 or 6] and the keypad has been removed or disconnected. Remedy: Re-install keypad and reset. Change Reference Selector (01.014) to select the reference from another source.
Pb.bt (245) Power board is in bootloader mode	Cause: Power board is in bootloader mode. Remedy: Send power board firmware file to reprogram the power board using Connect and power cycle drive.
Pb.Er (93) Communication lost / errors between control and power	Cause: Communication between the control board processor and the power board processor has been lost. Remedy: Hardware fault – Contact the supplier of the drive.
Pb.HF (235) Power board HF	Cause: Power processor hardware fault. The sub-trip number is the HF code. Remedy: Hardware fault - Contact the supplier of the drive.
Pd.S (37) Power down save error	Cause: An error has been detected in the power down save parameters saved in non-volatile memory. Remedy: Perform a 1001 save in Pr 00 to ensure that the trip doesn’t occur the next time the drive is powered up.
PH.Lo (32) Supply phase loss	Cause: The drive has detected an input phase loss or large supply imbalance. The drive monitors DC bus ripple; if ripple exceeds the threshold, this trip occurs. Potential causes include input phase loss, large supply impedance, or severe output current instability. Remedy: Check the AC supply voltage balance and level at full load. Check the DC bus ripple level with an isolated oscilloscope. Check the output current stability. Check for mechanical resonance with the load. Reduce the duty cycle. Reduce the motor load. Disable the phase loss detection, set Pr 06.047 to 2.
PSU (5) Internal power supply fault	Cause: One or more internal power supply rails are outside limits or overloaded. Remedy: Remove the option module and perform a reset. There is a hardware fault within the drive – return the drive to the supplier.
r.All (227) RAM allocation error	Cause: An option module derivative image has requested more parameter RAM than is allowed. The failure with the highest sub-trip number is given. Sub-trips are calculated based on parameter size, type, and sub-array number. Remedy: Check option module derivative customization. Verify Menu 18 and 20 customizations.
r.b.ht (250) Hot rectifier/brake	Cause: Over-temperature detected on input rectifier or braking IGBT. Remedy: Increase ventilation by setting Cooling Fan Control (06.045) > 0.
rS (33) Measured resistance has exceeded the parameter range	Cause: The measured stator resistance of the motor during an auto-tune test has exceeded the maximum possible value of Stator Resistance (05.017). This can happen if the motor is very small compared to the drive rating or if incorrect values are entered. Remedy: Ensure the stator resistance of the motor falls within the range of the drive model (Ratio of drive size to motor size > 15:1 may cause this). Check that a value has not been entered in the stator resistance for the presently selected motor map that exceeds the allowed range. Check the motor cable / connections. Check the integrity of the motor stator winding using an insulation tester. Check the motor phase to phase resistance at the drive terminals. Check the motor phase to phase resistance at the motor terminals. Ensure the stator resistance of the motor falls within the range of the drive model. Select fixed boost mode (Pr 05.014 = Fd) and verify the output current waveforms with an oscilloscope. Replace the motor.
SCL (30) Control word watchdog has timed out	Cause: The control word has been enabled and has timed out. Remedy: Once Pr 06.042 bit 14 has been changed from 0 to 1 to enable the watchdog, this must be repeated every 1s or a SCL trip will be initiated. The watchdog is disabled when the trip occurs and must be re-enabled if required when the trip is reset.
SL.dF (204) Option module in option slot 1 has changed	Cause: The option module in option slot 1 is a different type to that installed when parameters were last saved. Sub-trips indicate if no module was installed previously, or if setup/application menus have changed. Remedy: Turn off the power, ensure the correct option module is installed in the option slot and re-apply the power. Confirm that the currently installed option module is correct, ensure option module parameters are set correctly and perform a user save in Pr mm.000.
SL.Er (202) Option module in option slot 1 has detected a fault	Cause: The option module in slot 1 has detected an error. The sub-trip number may be displayed as a code or string. Remedy: See relevant option module User Guide for details of the trip.
SL.HF (200) Option module 1 hardware fault	Cause: Generated by the drive when the option module fails. Reasons include unidentifiable category, corrupt tables, insufficient memory, or communication timeouts. Remedy: Ensure the option module is installed correctly. Replace the option module. Replace the drive.
SL.nF (203) Option module in option slot 1 has been removed	Cause: The option module in option slot 1 has been removed since the last power up. Remedy: Ensure the option module is installed correctly. Re-install the option module. To confirm that the removed option module is no longer required perform a save function in Pr 00.
SL.tO (201) Option module watchdog function service error	Cause: The option module installed in Slot 1 started the option watchdog function and then failed to service the watchdog correctly. Remedy: Replace the option module.
So.St (226) Soft start relay failed to close, soft start monitor failed	Cause: The soft start relay in the drive failed to close or the soft start monitoring circuit has failed. Sub-trips: 1=Soft-start failure, 2=DC bus capacitor failure (110V drive). Remedy: Hardware fault – Contact the supplier of the drive.
St.HF (221) Hardware trip has occurred during last power down	Cause: A hardware trip (HF01 – HF18) has occurred and the drive has been power cycled. The sub-trip number identifies the specific HF trip. Remedy: Enter 1299 in Pr 00 and press reset to clear the trip.
Sto (234) No Safe Torque Off board fitted	Cause: STO board not fitted correctly. Remedy: Hardware fault – Contact the supplier of the drive.
th (24) Motor thermistor over-temperature	Cause: Motor thermistor connected to terminal 14 (digital input 5) indicates over-temperature. Feedback value is higher than Thermistor Trip Threshold (07.048). Remedy: Check motor temperature. Check threshold level (Pr 07.048). Check thermistor continuity.
th.br (10) Brake resistor over temperature	Cause: Hardware based braking resistor thermal monitoring is connected and the resistor overheats. Remedy: Check brake resistor wiring. Check braking resistor value is greater than or equal to the minimum resistance value. Check braking resistor insulation.
tH.Fb (218) Internal thermistor has failed	Cause: An internal thermistor has failed in the drive (i.e. open circuit or short circuit). Remedy: Hardware fault – Contact the supplier of the drive.
thS (25) Motor thermistor short circuit	Cause: The motor thermistor connected to terminal 14 (digital input 5) is short circuit or low impedance (< 50 Ohms). Remedy: Check thermistor continuity. Replace motor / motor thermistor.
tun.S (18) Autotune test stopped before completion	Cause: The drive was prevented from completing an autotune test, because either the drive enable or the drive run were removed. Remedy: Check the drive enable signal (Terminal 31 & 34 on size 1 to 4 or terminals 31 & 35 on size 5 to 9) were active during the autotune. Check the run command was active in digital input 3 or 4 state (Pr 08.003 or Pr 08.004) during the autotune.
tun.1 (11) Required speed could not be reached	Cause: The drive has tripped during an autotune. The cause of the trip can be identified from the sub-trip number. Sub-trip 2: The motor did not reach the required speed during rotating autotune or mechanical load measurement. Remedy: Ensure the motor is free to turn i.e. mechanical brake is released. Ensure Mechanical Load Test Level (05.021) is set correctly.
tun.3 (13) Measured inertia has exceeded the parameter range (RFC-A mode only)	Cause: The drive has tripped during a rotating autotune or mechanical load measurement test. The cause of the trip can be identified from the associated sub-trip number. Sub-trip 1: Measured inertia has exceeded the parameter range. Sub-trip 3: Unable to identify the motor inertia. Remedy: Check motor cable wiring is correct.
U.OI (8) User OI ac	Cause: A U.OI trip is initiated if the output current of the drive exceeds the trip level set by User Over Current Trip Level (04.041). Remedy: Check load and User Over Current Trip Level settings.
U.S (36) User Save error / not completed	Cause: The U.S trip indicates that an error has been detected in the user save parameters saved in non-volatile memory. For example, following a user save command, if the power to the drive was removed when the user parameters were being saved. Remedy: Perform a user save in Pr 00 to ensure that the trip doesn’t occur the next time the drive is powered up. Ensure that the drive has enough time to complete the save before removing the power to the drive.
UP.uS (96) Trip generated by an onboard user program	Cause: This trip can be initiated from within an onboard user program using a function call which defines the sub-trip number. Remedy: Check the user program.
UPrG (249) Onboard user program error	Cause: An error has been detected in the onboard user program image. The sub-trip indicates the reason for the trip: Sub-trip Reason 1 Divide by zero. 2 Undefined trip. 3-7 Attempted access/write to invalid/non-existent parameters. 30-34 Image failure (CRC, RAM, ID code, or Version issues). 40-41 Timed task suspended or undefined function called. 52-53 Customizable menu table CRC failed or changed. 80-81 Image not compatible with control board/serial number. 100-104 Pointer/Array bounds violation or invalid data type conversion. 200 User program invoked "divide" service with denominator of zero. Remedy: Review the onboard user program logic regarding the specific sub-trip code. Compile and download the corrected user program image.
br.res Brake resistor overload	Cause: Braking Resistor Thermal Accumulator (10.039) in the drive has reached 75.0 % of the value at which the drive will trip. Remedy: Check the braking resistor sizing and load. Monitor parameter 10.039.
OV.Ld Motor Protection Accumulator	Cause: Motor Protection Accumulator (04.019) in the drive has reached 75.0 % of the value at which the drive will trip and the load on the drive is >100 %. Remedy: Reduce motor load. Check motor rated current settings.
d.OV.Ld Drive over temperature	Cause: Percentage Of Drive Thermal Trip Level (07.036) in the drive is greater than 90 %. Remedy: Check drive cooling fans and ambient temperature. Reduce drive load.
tuning Autotune in progress	Cause: The autotune procedure has been initialized and an autotune is in progress. Remedy: Wait for the autotune process to complete.
LS Limit switch active	Cause: Indicates that a limit switch is active and that is causing the motor to be stopped. Remedy: Check physical limit switches. Check wiring to limit switch inputs.
Opt.Al Option slot alarm	Cause: An alarm has been detected in the Option slot module. Remedy: Check the specific Option module documentation. Verify module installation.
Lo.AC Low voltage mode	Cause: The drive is operating in low voltage mode. Remedy: See Low AC Alarm (10.107) parameter for details. Check input supply voltage.
I.AC.Lt Current limit active	Cause: The drive is actively limiting the current output. Remedy: See Current Limit Active (10.009). Check for mechanical binds or excessive load.
24.LoSt 24V Backup not present	Cause: 24V Backup supply is missing or disconnected. Remedy: See 24V Alarm Loss Enable (11.098). Check external 24V power supply connections.
inh Inhibited	Cause: The drive is inhibited and cannot be run. The Safe Torque Off signal is not applied to Safe Torque Off terminals or Pr 06.015 is set to 0. (Drive Output Stage: Disabled) Remedy: Apply Safe Torque Off signal. Set Pr 06.015 to 1.
rdy Ready	Cause: The drive is ready to run. The drive enable is active, but the drive inverter is not active because the final drive run is not active. (Drive Output Stage: Disabled) Remedy: Give run command to start the motor.
Stop Stopped	Cause: The drive is stopped / holding zero speed. (Drive Output Stage: Enabled) Remedy: Normal operational state when holding zero speed.
S.Loss Supply Loss	Cause: Supply loss condition has been detected. (Drive Output Stage: Enabled) Remedy: Check main power supply connections. Check for blown fuses.
dc.inj DC Injection	Cause: The drive is applying dc injection braking. (Drive Output Stage: Enabled) Remedy: Wait for braking cycle to complete.
Er Error / Trip	Cause: The drive has tripped and no longer controlling the motor. The trip code appears in the display. (Drive Output Stage: Disabled) Remedy: Investigate the specific trip code shown on display. Reset the drive after clearing the fault.
UV Under Voltage	Cause: The drive is in the under voltage state either in low voltage or high voltage mode. (Drive Output Stage: Disabled) Remedy: Check DC bus voltage. Check input supply voltage levels.
HEAt Motor Pre-heat	Cause: The motor pre-heat function is active. (Drive Output Stage: Enabled) Remedy: No action required (normal operation if configured).
PS.LOAD Waiting for power stage	Cause: The drive is waiting for the processor in the power stage to respond after power-up. Remedy: Wait for start-up sequence to complete. If stuck, cycle power.
LOAD OPtion Waiting for option module	Cause: The drive is waiting for the option module to respond after power-up. Remedy: Ensure option module is seated correctly.
UPLOAD Loading parameter database	Cause: At power-up it may be necessary to update the parameter database held in the drive because an Option module has changed. This may involve data transfer between the drive and option module. Remedy: Wait for 'UPLOAD' message to clear. Do not remove power during this process.
LOAD.I Bootloading drive firmware	Cause: The drive is waiting for the bootloader file to be transferred to the processor. Remedy: Wait for firmware update to complete.
HFxx Internal faults	Cause: These indicate internal problems (Priority 1). All drive features are inactive after any of these trips occur. Remedy: These faults cannot be reset. Hardware replacement or service may be required.
{St.HF} Stored HF trip	Cause: Stored Hardware Fault. Remedy: This trip cannot be cleared unless 1299 is entered into Parameter 00 and a reset is initiated.
{EEF} Volatile memory failure	Cause: Failure in volatile memory (Priority 3). Remedy: Reset if Parameter 00 is set to 1233 or 1244. Or if Load Defaults (11.043) is set to a non-zero value.
{PSU} Internal 24V	Cause: Rectifier 24V issue (Priority 4). Remedy: Check internal power supply.

 

How to Read C200 Faults via “Connect” Software

For more complex issues in 2026, relying on the 3-digit LED display may not be enough. Connecting the drive to a PC provides a significantly clearer picture of the drive’s status.

• Connect Software: By using the “Connect” commissioning tool and a 485-to-USB adapter (connected to the drive’s serial port), you can access the Trip Log.
• Detailed Trip Descriptions: The software translates abbreviations like It.AC into plain English (“Motor Thermal Overload”) and provides the values for voltage and current at the exact moment the trip occurred.
• Diagnostic Parameters: Check Pr 10.020 through Pr 10.029. These parameters store the last 10 trips in order, with the most recent trip at index 0.
• SD Card Backups: If you are using the optional AI-Backup module, you can save the fault history and parameters to an SD card for remote analysis by technical support.

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 stops the motor to prevent damage. A Warning (Flashing code) indicates the drive is reaching a limit—such as br.res (Braking Resistor Overload)—but it will keep running until the limit is exceeded.

Q: How do I reset a Commander C200 trip?

A: Once the cause is cleared, you can reset the drive by:

• Pressing the Red Reset Button on the keypad.
• Cycling the main AC power (wait for the display to go blank first).
• Toggling a digital input programmed for “Reset” (typically Terminal 2 if configured).
• Sending a reset command via the communication network (Modbus RTU).

Q: Where is the trip history stored?

A: Trip history is stored in the drive’s non-volatile memory. You can view it through the keypad by navigating to Menu 10, or through the “Connect” software interface. Even after power cycles, the last 10 events remain in the log.

Q: What does “Ph.lo” mean?

A: This stands for Phase Loss. It means the drive has detected a missing phase on the input power or a high degree of voltage imbalance between phases. Check your input fuses and supply stability.