Nidec & Control Technique Unidrive M200 Drive

Nidec & Control Technique Unidrive M200 Drive Fault Codes:

Fault Code and MeaningCause and Remedy

C.Acc (185)


NV Media Card Write fail

Cause: The drive was unable to access the NV Media Card. If the trip occurs during data transfer to the card, the file may be corrupted. If it occurs during transfer to the drive, the transfer may be incomplete.



Remedy:

  • Check NV Media Card is installed / located correctly.

  • Replace the NV Media Card.

C.by (178)


NV Media Card cannot be accessed (busy)

Cause: An attempt was made to access a file on the NV Media Card, but the card is already being accessed by an option module.



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; parameters on the 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: 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: 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: An error has been detected in the data structure on the card. Causes may include missing folder structure, corrupted .DAT files, or duplicate file IDs.



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: There is not enough space left on the card to create the data block. 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)


Option module installed is different between source and destination

Cause: The option module category is different between the source and destination drives during a transfer or compare. The data for the different module will be set to default values.



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 drive derivative

Cause: Drive Derivative (11.028) or Product Type (11.063) are different between the source and target drives.



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.

C.rdo (181)


NV Media Card has the Read Only bit set

Cause: An attempt has been made to modify data on a read-only NV Media Card or read-only data block.



Remedy:

  • Clear the read only flag by setting Pr 00 to 9777 and reset the drive.

C.rtg (186)


Voltage and/or current rating of source and destination drives are different

Cause: Parameter data is being transferred but current/voltage ratings differ. Rating specific parameters may not be transferred.



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)


Option module file transfer has failed

Cause: Transfer of an option module file failed because the option module did not respond correctly. The sub-trip indicates the slot number.



Remedy:

  • Check option module installation and status.

  • Retry the operation.

C.tyP (187)


NV Media Card parameter set not compatible with current drive mode

Cause: The drive mode in the data block is different from the current drive mode, or 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: Current loss detected on Analog input 1 (Terminal 2). Current fell below 3 mA in 4-20 mA or 20-4 mA mode.



Remedy:

  • Check control wiring is correct.

  • Check control wiring is undamaged.

  • Check the Analog Input 1 Mode (07.007).

  • Ensure current signal is present and greater than 3 mA.

CL.bt (35)


Trip initiated from the Control Word

Cause: 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 (06.043).

  • Clear the trip 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 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 file system write is active changing parameters while the drive is enabled (Drive Active 10.002 = 1). Actions include loading defaults, changing mode, or transferring data.



Remedy:

  • Ensure the drive is not enabled when loading defaults.

  • Ensure the drive is not enabled when changing drive mode.

  • Ensure the drive is not enabled when transferring data from NV media card.

dcct (110)


DCCT reference out of range (size 5 upwards)

Cause: The DCCT has caused the trip.



Remedy:

  • Hardware fault – contact the supplier of the drive.

dEr.E (246)


Derivative file error

Cause: Derivative file is missing, invalid, does not match control board hardware, or has a different derivative number.



Remedy:

  • Contact the supplier of the drive.

dEr.I (248)


Derivative product image error

Cause: An error was detected in the derivative product image. Reasons can include CRC error, insufficient RAM, OS function requirements, invalid ID code, or option module conflicts.



Remedy:

  • Contact the supplier of the drive.

dESt (199)


Two or more parameters are writing to the same destination

Cause: 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. The exact cause/reason of the trip can be identified from the sub-trip number (e.g., parameter database version changed, CRC failure, drive mode outside range, etc.). This often happens if power is removed while saving parameters.



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 Et trip has occurred. An external trip can also be initiated 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 mm.000 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:

This trip cannot be reset until 10s after the trip was initiated.



Remedy:


  • Check that the fan is fitted 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 configuration has changed.



Remedy:


  • Power cycle the drive.
FI.In
237

Firmware Incompatibility
Cause:

The FI.In trip indicates that the user firmware is incompatible with the power firmware.



Remedy:


  • Re-program the drive with the latest version of the drive firmware for Unidrive M200, using Unidrive M Connect.
HF01

Data processing error: CPU hardware fault
Cause:

The HF01 trip indicates that a CPU address error has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF02

Data processing error: CPU memory management fault
Cause:

The HF02 trip indicates that a DMAC address error has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF03

Data processing error: CPU has detected a bus fault
Cause:

The HF03 trip indicates that a bus fault has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF04

Data processing error: CPU has detected a usage fault
Cause:

The HF04 trip indicates that a usage fault has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF05

Reserved
Cause:

Reserved.



Remedy:


  • N/A
HF06

Reserved
Cause:

Reserved.



Remedy:


  • N/A
HF07

Data processing error: Watchdog failure
Cause:

The HF07 trip indicates that a watchdog failure has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF08

Data processing error: CPU Interrupt crash
Cause:

The HF08 trip indicates that a CPU interrupt crash has occurred. This trip indicates that the control PCB on the drive has failed. The crash level is indicated by the sub-trip number.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF09

Data processing error: Free store overflow
Cause:

The HF09 trip indicates that a free store overflow has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF10

Reserved
Cause:

Reserved.



Remedy:


  • N/A
HF11

Data processing error: Non-volatile memory comms error
Cause:

The HF11 trip indicates that a non-volatile memory comms error has occurred.



Remedy:


  • Hardware fault – contact the supplier of the drive (Sub-trip 1).

  • Re-program drive with compatible user firmware (Sub-trip 2: EEPROM size incompatible).
HF12

Data processing error: main program stack overflow
Cause:

The HF12 trip indicates that the main program stack overflow has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF13

Reserved
Cause:

Reserved.



Remedy:


  • N/A
HF14

Reserved
Cause:

Reserved.



Remedy:


  • N/A
HF15

Reserved
Cause:

Reserved.



Remedy:


  • N/A
HF16

Data processing error: RTOS error
Cause:

The HF16 trip indicates that a RTOS error has occurred. This trip indicates that the control PCB on the drive has failed.



Remedy:


  • Hardware fault – Contact the supplier of the drive.
HF17

Reserved
Cause:

Reserved.



Remedy:


  • N/A
HF18

Data processing error: Internal flash memory has failed
Cause:

The HF18 trip indicates that the internal flash memory has 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:

The HF19 trip indicates that the CRC check on the drive firmware has failed. The drive is now in its bootloader mode.



Remedy:


  • Re-program the drive, with latest control and power firmware using Unidrive M 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:

The It.Ac trip indicates a motor thermal overload based on the Motor Rated Current and Motor Thermal Time Constant. The drive will trip when the accumulator gets to 100%.



Remedy:


  • Ensure the load is not jammed / sticking.

  • Check the load on the motor has not changed.

  • Tune the motor rated speed parameter (Pr 5.008) (RFC-A mode only).

  • Ensure the motor rated current is not zero.
It.br
19

Braking resistor overload timed out (I2t)
Cause:

The It.br trip indicates that braking resistor overload has timed out. The trip is initiated when the Braking Resistor Thermal Accumulator reaches 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 and software overload protection is not required, set Pr 10.030, Pr 10.031 or Pr 10.061 to 0 to disable the trip.
LF.Er
90

Communication has been lost / errors detected between power, control and rectifier modules
Cause:

This trip is initiated if there is no communications between power, control or the rectifier module or if excessive communication errors have been detected.



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:

This trip indicates that the 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:

In open-loop mode, if the Post-ramp Reference exceeds the threshold. In RFC-A mode, if the Estimated Frequency exceeds the Over Frequency Threshold.



Remedy:


  • Reduce the Frequency Controller Proportional Gain (03.010) to reduce the frequency overshoot (RFC-A mode only).

  • Check that a mechanical load is not driving motor.

  • Reduce Current Controller Ki Gain (04.014).
Oh.dc (27)

DC bus over temperature
Cause: A DC bus component over temperature has been detected based on a software thermal model. The estimated temperature is displayed as a percentage of the trip level in Pr 07.035.



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.

  • Check motor map settings (Pr 05.006 – Pr 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).

  • Disconnect the load and complete a rotating autotune (Pr 05.012).
Oht.C (219)

Control stage over-temperature
Cause: Control stage over-temperature has been detected. This often occurs if Cooling Fan control (06.045) = 0.



Remedy:




  • Increase ventilation by setting Cooling Fan control (06.045) > 0.
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 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. The Thermistor location is identified by the sub-trip.



Remedy:




  • Check enclosure / drive fans are still functioning correctly.

  • Force the heatsink fans to run at maximum speed.

  • Check enclosure ventilation paths and door filters.

  • Increase ventilation.

  • Reduce the drive switching frequency.

  • Reduce duty cycle or motor load.

  • Increase acceleration / deceleration rates.

  • Use S ramp (Pr 02.006).

  • Check the derating tables and confirm the drive is correctly sized for the application.
OI.A1 (189)

Analog input 1 over-current
Cause: Current input on analog input 1 exceeds 24mA.



Remedy:




  • Check the signal source and wiring for Analog Input 1.

  • Ensure input current is within specification (< 24mA).
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 the trip was initiated.



Remedy:




  • Increase acceleration/deceleration rate.

  • If seen during autotune 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.

  • 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.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.

  • Install an output line reactor or sinusoidal filter.
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?
Out.P (98)

Output phase loss detected
Cause: Phase loss has been detected at the drive output. Sub-trips indicate if U, V, or W phase was disconnected.



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/maximum
Cause: The DC bus voltage has exceeded the VM_DC_VOLTAGE[MAX] or VM_DC_VOLTAGE_SET[MAX] for 15s.



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. The trip is related to the table uploaded from the power system at power-up.



Remedy:




  • Hardware fault – Contact the supplier of the drive.
PAd
34

Keypad has been removed when the drive is receiving the reference from the keypad
Cause: The drive is in keypad mode [Reference Selector (01.014) = 4 or 6] and the keypad has been removed or disconnected from the drive.



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 Unidrive M Connect and power cycle drive.
Pb.Er
93

Communication has been lost / errors detected between control and power processor
Cause: There is no communications between the control board processor and the power board processor.

Sub-trips:

1: PLL operating region out of lock

2: Power board lost communication with user board

3: User board lost communication with power board

4: Communication CRC error



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: Input phase loss or large supply imbalance. The drive monitors ripple voltage on the DC bus; if ripple exceeds threshold, the drive trips.

Potential causes: Input phase loss, Large supply impedance, severe output current instability.

Sub-trips:

00: Phase loss detected based on control system feedback.

01: Phase loss has been detected by the rectifier module.



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 (if appropriate).
PSU
5

Internal power supply fault
Cause: One or more internal power supply rails are outside limits or overloaded.

Sub-trip 00: Internal power supply overload.



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.



Remedy:




  • Derivatives can customize menus 18 and 20. Check option module configuration.
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.
Reserved
Various

Reserved trips
Cause: These trip numbers are reserved trip numbers for future use.

(Codes: 01, 09, 12, 14-17, 23, 29, 38-39, 91, 94-96, 99, 101-109, 111, 168-172, 176-177, 190-198, 205-217, 222-224, 229-230, 233, 238-244, 249, 251-254)



Remedy:




  • No specific remedy listed; contact support if persistent.
rS
33

Measured resistance has exceeded the parameter range
Cause: Measured stator resistance during autotune exceeded maximum possible value.

Sub-trips:

0: Resistance > (VFS / √2) / Full Scale Current Kc.

2: Transient Inductance > 500 mH or Stator Inductance > 5000 mH.

3: User entered resistance value > range limits.

4: Measured resistance not > sub-trip 0 check but outside firmware usable range.



Remedy:




  • Ensure the stator resistance of the motor falls within the range of the drive model.

  • 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 and motor terminals.

  • 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 slot 1 is a different type to that installed when parameters were last saved.

Sub-trips:

1: No module installed previously.

2: Same ID, set-up menu changed/defaults loaded.

3: Same ID, applications menu changed/defaults loaded.

4: Same ID, set-up and applications menu changed/defaults loaded.



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 00.
SL.Er
202

Option module in option slot 1 has detected a fault
Cause: The option module in option slot 1 on the drive has detected an error.



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 regarding the option module.

Sub-trips:

1: Module category not identified.

2: Menu table not supplied or corrupt.

3: Insufficient memory.

4: Module not running correctly during power-up.

5: Module removed after power-up or stopped working.

(See manual for full list 6-10)



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: Option module in 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: Option module installed in Slot 1 has 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: Soft start relay in the drive failed to close or the soft start monitoring circuit has failed.

Sub-trip 1: Soft-start failure.

Sub-trip 2: DC bus capacitor failure on 110 V drive (size 2 only).



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.



Remedy:




  • Enter 1299 in Pr 00 and press reset to clear the trip.

Sto (234)



No Safe Torque Off board fitted

Cause: Internal STO board not fitted correctly.



Remedy:

  • Hardware fault – Contact the supplier of the drive.

th (24)



Motor thermistor over-temperature

Cause: The motor thermistor connected to terminal 14 (digital input 5) has indicated a motor over temperature.



Remedy:

  • Check threshold level (Pr 07.048).

  • Check motor temperature.

  • Check thermistor continuity.

th.br (10)



Brake resistor over temperature

Cause: The 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 is short circuit or low impedance (<50 Ω).



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 11) was 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 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

Cause: Measured inertia has exceeded parameter range or mechanical load test was unable to identify motor inertia.



Remedy:

  • Check motor cable wiring is correct.

U.OI (8)



User OI ac

Cause: The output current of the drive exceeds the trip level set by User Over Current Trip Level (04.041).



Remedy:

  • Check the load current.

  • Adjust the User Over Current Trip Level (04.041) if appropriate.

U.S (36)



User Save error / not completed

Cause: Error detected in the user save parameters saved in non-volatile memory (e.g. power removed during save).



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.



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 (e.g. Divide by zero, Array bounds violation, Invalid pointer).



Remedy:

  • Check sub-trip code in drive diagnostics.

  • Check user program code logic (e.g. divide by zero errors).

  • Ensure image compatibility with control board.

  • Reload the user program.
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 braking resistor 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:

  • Check motor load conditions.

  • Monitor parameter 04.019.
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 and ambient temperature.

  • Monitor parameter 07.036.
tuning

Autotune in progress
Cause:

The autotune procedure has been initialized and an autotune is in progress.



Remedy:

  • Wait for autotune 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 limit switch configuration.
Opt.Al

Option slot alarm
Cause:

Option slot alarm detected.



Remedy:

  • Check the option module installed in the slot.

  • Review option module specific documentation.
Lo.AC

Low voltage mode
Cause:

Drive is in Low voltage mode.



Remedy:

  • See Low AC Alarm parameter (10.107).
I.AC.Lt

Current limit active
Cause:

Current limit is active.



Remedy:

  • See Current Limit Active parameter (10.009).

  • Check for mechanical binds or excessive load.
24.LoSt

24V backup not present
Cause:

24V backup supply is not detected.



Remedy:

  • See 24V Alarm Loss Enable (11.098).

  • Check external 24V power supply connections.
inh

Drive inhibited
Cause:

The drive is inhibited and cannot be run. Either the drive enable signal is not applied to the drive enable terminals or Pr 06.015 is set to 0.



Remedy:

  • Check drive enable terminals.

  • Check Parameter 06.015.

  • Output stage: Disabled.
rdy

Drive 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.



Remedy:

  • Apply run command to start motor.

  • Output stage: Disabled.
StoP

Drive stopped
Cause:

The drive is stopped / holding zero speed.



Remedy:

  • Normal operational state.

  • Output stage: Enabled.
S.Loss

Supply loss
Cause:

Supply loss condition has been detected.



Remedy:

  • Check incoming power supply.

  • Output stage: Enabled.
dc.inJ

DC injection braking
Cause:

The drive is applying dc injection braking.



Remedy:

  • Information only (Braking operation).

  • Output stage: Enabled.
Er

Drive tripped
Cause:

The drive has tripped and no longer controlling the motor. The trip code appears in the display.



Remedy:

  • Investigate the specific trip code displayed.

  • Output stage: Disabled.
UV

Under voltage
Cause:

The drive is in the under voltage state either in low voltage or high voltage mode.



Remedy:

  • Check DC bus voltage.

  • Check input line voltage.

  • Output stage: Disabled.
HEAt

Motor pre-heat
Cause:

The motor pre-heat function is active.



Remedy:

  • Information only.

  • Output stage: Enabled.
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 to complete.
LOAD OPtion

Waiting for option module
Cause:

The drive is waiting for the Option Module to respond after power-up.



Remedy:

  • Wait for start-up to complete.

  • Check Option Module seating if persists.
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.



Remedy:

  • Wait for database transfer to complete.

  • Note: This may involve data transfer between drive and option module.
LOAD.I

Bootloading drive firmware
Cause:

The drive is waiting for the bootloader file to be transferred to the processor.



Remedy:

  • Ensure firmware file is valid.

  • Do not power off during transfer.