Unidrive Trip Code
|
No.
|
String
|
Cause of trip
|
|
1
|
UU
|
DC link under voltage. Under voltage trip and
restart levels are as follows:
|
|
Drive voltage rating UU trip level UU restart
level
|
||
|
200 175 215
|
||
|
400 330 425
|
||
|
575 435 590
|
||
|
690 435 590
|
||
|
2
|
OU
|
DC link over voltage. This could be because
the d.c. link voltage has exceeded the maximum level or has
remained above the maximum continuous level for more than 15s. This trip
cannot be reset until the voltage falls below the maximum continuous level.
|
|
Drive voltage rating Instantaneous trip Max
continuous level
|
||
|
200V 415V 400V
|
||
|
400V 830V 800V
|
||
|
575V 990V 955V
|
||
|
690V 1190V 1150V
|
||
|
If the drive is operating in low voltage
battery mode the over voltage trip level is 1.45 x parameter 06.46.
|
||
|
3
|
OI.AC
|
AC instantaneous over current.
|
|
4
|
OI.br
|
Braking resistor instantaneous current trip.
|
|
5
|
PS
|
Internal drive power supply trip
|
|
6
|
Et
|
External trip (see 10.32)
|
|
7
|
O.SPd
|
Overspeed
|
|
8
|
PS.10V
|
10V user power supply overload
|
|
9
|
PS.24V
|
24V internal power supply overload
|
|
10
|
t010
|
User trip
|
|
11
|
tunE1
|
The position feedback did not change or required
speed could not be reached during the inertia test (see 05.12)
|
|
12
|
tunE2
|
Position feedback direction incorrect, or motor
could not be stopped during the inertia test, or minimal movement phasing
test failed (see 05.12)
|
|
13
|
tunE3
|
Drive encoder commutation signals connected
incorrectly, or measured inertia out of range, or motor was rotating when the
minimal movement phasing test started (see 05.12)
|
|
14
|
tunE4
|
Drive encoder U commutation signal fail (see
05.12)
|
|
15
|
tunE5
|
Drive encoder V commutation signal fail (see
05.12)
|
|
16
|
tunE6
|
Drive encoder W commutation signal fail (see
05.12)
|
|
17
|
tunE7
|
Motor poles or encoder counts per revolution
set-up incorrectly (see 05.12)
|
|
18
|
tunE
|
Auto-tune stopped before completion (see 05.12)
|
|
19
|
It.br
|
I2t on braking resistor (see 10.31)
|
|
20
|
It.AC
|
I2t on drive output current (see 04.15)
|
|
21
|
O.ht1
|
Drive over-heat (IGBT junctions) based on thermal
model (see 05.18)
|
|
22
|
O.ht2
|
Drive over-heat based on heatsink temperature (see
07.04)
|
|
23
|
O.CtL
|
Drive over-heat based on control board temperature
(see 07.05)
|
|
24
|
th
|
Motor thermistor trip (see 07.11)
|
|
25
|
thS
|
Motor thermistor short circuit (see 07.11)
|
|
26
|
O.Ld1
|
Digital output overload
|
|
27
|
O.ht3
|
Drive over-heat based on thermal model (see 07.35)
|
|
The drive will attempt to stop the motor before
tripping. If the motor does not stop in 10seconds the drive trips
immediately.
|
||
|
28
|
cL2
|
Analogue input 2 current mode: current loss (see
07.11)
|
|
29
|
cL3
|
Analogue input 3 current mode: current loss (see
07.11)
|
|
30
|
SCL
|
Serial comms timeout with remote keypad
on drive 485 comms port
|
|
31
|
EEF
|
Internal drive EEPROM checksum. See trips 36 and
37 below. When this trip occurs the drive mode becomes Open-loop and all the
parameters are set to default. The trip can only be removed by entering a
load default command (i.e. 1233, 1244, etc.) into parameter x.00
before reseting the drive.
|
|
32
|
PH
|
High input voltage phase imbalance or input phase
loss. Normally a motor load of between 50 and 100% or drive rating is
required to trigger the trip. The drive will attempt to stop the motor before
tripping except in Regen mode. This trip is initiated when phase loss is
detected from d.c. link ripple.
|
|
33
|
rS
|
Failure to measure resistance during auto-tune or
when starting in open-loop voltage modes 0 or 3. This is either because the
resistance exceeds the maximum measurable value or the drive was not enabled
(see 05.12, 05.14, 05.17)
|
|
34
|
Pad
|
If an LED or LCD keypad are fitted directly to the
drive, and the drive is in keypad reference mode, and the keypad is removed
the drive produces this trip.
|
|
35
|
CL.bit
|
Trip initiated from the control word (parameter
06.42)
|
|
36
|
SAVE.Er
|
The drive holds two banks of user save parameters
in EEPROM. This trip indicates that the power was removed when parameters
were being saved which resulted in an error in a user save parameter bank.
The drive will revert back to the user save parameters that were last saved
successfully. If errors occur in both banks an EEF trip is initiated. This
trip will occur on every subsequent power up until parameters are saved
again.
|
|
37
|
PSAVE.Er
|
Power down save parameters are saved during power
down and can be saved when user parameters are saved. The drive holds two
banks of power down save parameters in EEPROM. This trip indicates that the
power was removed when parameters were being saved which resulted in an error
in a power down save parameter bank. The drive will revert back to the power
down save parameters that were last saved successfully. If errors occur in
both banks an EEF trip is initiated. This trip will occur on every subsequent
power up until power down save parameters are saved again (i.e. a power down
on a normal supply or a parameter save is initiated by the user).
|
|
38
|
t038
|
User trip
|
|
39
|
L.SYNC
|
Drive failed to synchronise to the
supply voltage in Regen mode (see 03.08)
|
|
40-89
|
t040 - t089
|
User trips
|
|
90
|
UP div0
|
User Program: attempted divide by zero
|
|
91
|
UP Par
|
User Program: attempted access to a non-existent
parameter
|
|
92
|
UP ro
|
User Program: attempted write to a read only
parameter
|
|
93
|
UP So
|
User Program: attempted read of a write only
parameter. (This trip should never occur as there are no write only
parameters in the drive.)
|
|
94
|
UP ovr
|
User Program: attempted out-of-range parameter
write
|
|
95
|
UP OFL
|
User program: Variables and function block calls
using more than the allowed RAM space (stack overflow)
|
|
96
|
UP uSEr
|
User program: program requested a trip
|
|
97
|
UP udf
|
User program: undefined trip
|
|
98
|
UP ACC
|
User Program: the user program in the drive is
inaccessible during a transfer of a user program from a SMART card to the
drive. This can occur if the user program file in the drive is being accessed
via comms at the same time.
|
|
99
|
t99
|
User trip
|
|
100
|
Drive reset (see 10.38)
|
|
|
101
|
t101
|
User trip
|
|
102
|
Oht4.P
|
Power module rectifier over temperature
|
|
103
|
OIbr.P
|
Power module braking IGBT over current
|
|
104
|
OIAC.P
|
Power module over current detected from the module
output currents
|
|
105
|
Oht2.P
|
Power module heatsink over temperature
|
|
106
|
OV.P
|
Power module over voltage
|
|
107
|
PH.P
|
Power module phase loss detection
|
|
108
|
PS.P
|
Power module power supply fail
|
|
109
|
OIdC.P
|
Power module over current detected from IGBT on
state voltage monitoring
|
|
110
|
Unid.P
|
Power module unidentified trip
|
|
111-160
|
t111 - t160
|
User trips
|
|
161
|
EnC11
|
Drive encoder trip: A failure has occurred during
the alignment of the analogue signals of a SINCOS encoder with the digital
count derived from the sine and cosine waveforms and
the comms position (if applicable). This fault is usually due to noise
on the sine and cosine signals.
|
|
162
|
Enc12
|
Drive encoder trip: Hiperface encoder -
The encoder type could not be identified during auto-configuration
|
|
163
|
Enc13
|
Drive encoder trip: EnDat encoder - The
number of encoder turns read from the encoder during auto-configuration is
not a power of 2
|
|
164
|
Enc14
|
Drive encoder trip: EnDat encoder - The
number of comms bits defining the encoder position within a turn
read from the encoder during auto-configuration is too large.
|
|
165
|
Enc15
|
Drive encoder trip: The number of periods per
revolution calculated from encoder data during auto-configuration is either
less than 2 or greater than 50000.
|
|
166
|
Enc16
|
Drive encoder trip: EnDat encoder - The
number of comms bits per period for a linear encoder exceeds 255.
|
|
167
|
Enc17
|
Drive encoder trip: The periods per revolution
obtained during auto-configuration for a rotary SINCOS encoder is not a power
of two.
|
|
168- 175
|
t166- t175
|
User trips
|
|
176
|
EnP.Er
|
Data error from electronic nameplate data stored
in selected position feedback device.
|
|
177
|
C.Boot
|
A write to a menu 0 parameter has been initiated
via the keypad by exiting edit mode and parameter 11.42 is set for auto or
boot mode, but the necessary boot file has not been created on the SMART card
to take the new parameter value. This occurs when 11.42 is changed to auto or
boot mode, but the drive is not subsequently reset.
|
|
178
|
C.BUSy
|
An attempt has been made to access a SMART card,
but the SMART card is already being accessed by an option module.
|
|
179
|
C.Chg
|
An attempt has been made to store a data in a
SMART card data block which already exists.
|
|
180
|
C.Optn
|
Parameter data or default difference data is being
transferred from a SMART card to the drive, but the option module categories
are different between source and destination drives. This trip does not stop
the data transfer, but is a warning that the data for the option modules that
are different will be set to the default values and not the values from the
card.
|
|
This trip also applies if a compare is attempted
between the data block and the drive.
|
||
|
181
|
C.RdO
|
An attempt has been made to modify a read-only
SMART card (i.e. erase the card, erase a file or create a file). A SMART card
is read-only if the read-only flag has been set or the card contains data
blocks with numbers from 500 to 999. Attempting to create data blocks with
numbers from 500 to 999 will always cause a trip.
|
|
182
|
C.Err
|
An attempt has been made to transfer a data block
from a SMART card to the drive or to compare a SMART card data block and the
checksum is incorrect or the data structure on the card is incorrect.
|
|
183
|
C.dat
|
An attempt has been made to transfer a data block
from a SMART card to the drive or to compare a SMART card data block and the
block does not exist.
|
|
184
|
C.FULL
|
An attempt has been made to create a data block on
a SMART card, but there is not enough space on the card.
|
|
185
|
C.Acc
|
An attempt has been made to access a SMART card,
but a card is not present or communications failure has occurred between the
drive and the card. This trip is also produced if an attempt is made to
access a data block that has already been opened by an option module.
|
|
186
|
C.rtg
|
Parameter data or default difference data is being
transferred from a SMART card to the drive, but the current and /or voltage
ratings are different between source and destination drives. This trip does
not stop the data transfer, but is a warning that the data for the option
modules that are different will be set to the default values and not the
values from the card.
|
|
This trip also applies if a compare is attempted
between the data block and the drive.
|
||
|
187
|
C.Typ
|
This trip is produced during a compare if the
drive mode in the data block is different from the current drive mode and the
file is a parameter or defaults differences file. This trip is also produced
if an attempt is made to transfer parameters from a parameter or default
difference to the drive if the drive mode in the data block is outside the
allowed range of drive modes for the drive.
|
|
188
|
C.cpr
|
A compare has been carried out between a data
block on a SMART card and the drive and the compare has failed. This trip
only occurs if the compare has not already failed with the following
trips: C.Typ, C.rtg, C.Optn, C.BUSy, C.Acc or C.Err
|
|
189
|
EnC1
|
Drive encoder trip: power supply short circuit
|
|
190
|
EnC2
|
Drive encoder trip: wire break
|
|
191
|
EnC3
|
Drive encoder trip: UVW phase angle incorrect
whilst running (servo mode only) or SINOS phase error.
|
|
192
|
EnC4
|
Drive encoder trip: Comms timeout or set
up transfer time too long
|
|
193
|
EnC5
|
Drive encoder trip: Checksum or CRC error or SSI
not ready
|
|
194
|
EnC6
|
Drive encoder trip: Encoder has indicated an error
or SSI power supply fail
|
|
195
|
EnC7
|
Drive encoder
trip: Initialisation failed. (Initialisation is required
because the encoder type parameter 03.38 has been changed,
but initialisation has not occurred, or
the initialisation process has failed due to encoder comms failure.)
|
|
196
|
EnC8
|
Drive encoder trip: Auto-configuration failed.
(Auto-configuration has been requested by changing parameter 03.41, but
an initialisation has not occurred to perform auto-configuration.)
|
|
197
|
EnC9
|
Drive encoder trip: Position feedback selected is
not valid (i.e. not from a position feedback option module)
|
|
198
|
Enc10
|
Drive encoder trip: Servo mode phasing failure
because the phasing angle (03.25 or 21.20) is incorrect.
|
|
199
|
dESt
|
Destination parameter clash
|
|
200
|
SL1.HF
|
Option module in slot 1: hardware fault. This
could occur because the module cannot be identified, or the module has not
indicated it is running within 5s of drive power-up, or an internal hardware
fault has occurred in the module. If the module is removed after power-up the
drive also produces this trip.
|
|
201
|
SL1.tO
|
Option module in slot 1: watchdog timeout. The
module has started the watchdog system, but has not subsequently serviced the
watchdog within the timeout period.
|
|
202
|
SL1.Er
|
Option module in slot 1: error. The module has
detected an error and tripped the drive. The reason for the error is stored
in parameter x.50.
|
|
203
|
SL1.nF
|
Option module in slot 1: not fitted. The option
module is identified by the drive by an option code. The drive stores the
codes of the modules fitted when the drive parameters are saved. The stored
codes are compared with the codes from the option modules at power-up. If a
module is not present, but a code is stored in drive EEPROM to indicate that
it should be fitted the drive trips.
|
|
204
|
SL1.dF
|
Option module in slot 1: different fitted. The
option module is identified by the drive by an option code. The drive stores
the codes of the modules fitted when the drive parameters are saved. The
stored codes are compared with the codes from the option modules at power-up.
If a module is different to the code stored in drive EEPROM the drive trips.
|
|
205
|
SL2.HF
|
Option module in slot 2: Hardware fault
|
|
206
|
SL2.tO
|
Option module in slot 2: watchdog timeout
|
|
207
|
SL2.Er
|
Option module in slot 2: error
|
|
208
|
SL2.nF
|
Option module in slot 2: not fitted
|
|
209
|
SL2.dF
|
Option module in slot 2: different fitted
|
|
210
|
SL3.HF
|
Option module in slot 3: hardware fault
|
|
211
|
SL3.tO
|
Option module in slot 3: watchdog timeout
|
|
212
|
SL3.Er
|
Option module in slot 3: error
|
|
213
|
SL3.nF
|
Option module in slot 2: not fitted
|
|
214
|
SL3.dF
|
Option module in slot 3: different fitted
|
|
215
|
SL.rtd
|
An option module failed
to recognise that the drive mode had changed.
|
|
216
|
t216
|
User trip
|
|
217-232
|
HF17 - HF32
|
Hardware faults
|