ADP200 • Quick installation guide - Specifications and connection
73
10 - Troubleshooting
10.1 Alarms
Note !
To reset alarms, see
"8.2.6 Displaying and resetting Alarms"
and
In the following table, the Code is visible only from serial line
Code
Error message shown
on the display [on the
integrated keypad]
Sub-code
Description
0
No alarm
Condition:
No alarm present
1
Overvoltage [OV]
Condition: DC link overvoltage alarm due to energy recovered from the motor.
The voltage arriving at the drive power section is too high compared to the maximum threshold relating to the PAR 560
Mains voltage
parameter setting.
Solution:
- Extend the deceleration ramp.
- Use a braking resistor between terminals BR1 and BR2 to dissipate the recovered energy
- Use the VDC Control function
2
Undervoltage [UV]
Condition:
DC link undervoltage alarm.
The voltage arriving at the drive power section is too low compared to the minimum threshold relating to the 560
Mains voltag
e parameter setting due to:
- the mains voltage being too low or overextended voltage drops.
- poor cable connections (e.g. loose contactor terminals, inductance, filter, etc.).
Solution:
Check the connections.
3
Ground fault [GNDF]
Condition:
Ground short circuit alarm
Solution:
- Check drive and motor wiring.
- Check that the motor is not grounded.
4
Overcurrent [OC]
Condition: Instantaneous overcurrent protection intervention alarm.
This may be due to the incorrect setting of current regulator parameters or a short circuit between phases or ground fault on the drive output.
Solution:
- Check the current regulator parameters (menu 17)
- Check wiring towards the motor
5
Desaturation [DES]
Condition: Instantaneous overcurrent in the IGBT bridge alarm.
Solution:
-
Switch the drive off and then switch it on again.
- If the alarm persists, contact the technical service centre.
6
MultiUndervolt [MUV]
Condition:
The number of attempted automatic restarts after the
Undervoltage
alarm has exceeded the set PAR 4650
UVRep attempts
value in the
PAR
4652 UVRep delay
time.
Solution:
Too many Undervoltage alarms.
Adopt the proposed solutions for the Undervoltage alarm.
7
MultiOvercurr [MOC]
Condition:
2 attempted automatic restarts after the Overcurrent alarm within 30 seconds. If more than 30 seconds pass after the Overcurrent alarm was
generated, the attempt counter is reset.
Solution:
Too many Overcurrent alarms. Adopt the proposed solutions for the Overcurrent alarm.
8
MultiDesat [MDES]
Condition:
2 attempted at automatic restarts after the Desaturation alarm within 30 seconds. If more than 30 seconds pass after the Desaturation alarm
was generated, the attempt counter is reset.
Solution:
Too many
Desaturation
alarms.
Adopt the proposed solutions for the
Desaturation
alarm.
9
Heatsink OT [HOT]
Condition:
Heatsink temperature too high alarm
Solution:
- Verify the correct operation of the cooling fan.
- Check that the heatsinks are not clogged
10
HeatsinkS OTUT [HSOT] Condition:
Heatsink temperature too high or too low alarm
The temperature has exceeded the upper or lower limit set for the linear temperature transducer.
Solution:
- Verify the correct operation of the cooling fan.
- Check that the heatsinks are not clogged
- Check that the openings for the cabinet cooling air are not blocked.
11
Intakeair OT [IOT]
Condition:
Intake air temperature too high alarm.
Solution:
Check correct fan operation
12
Motor OT [MOT]
Condition:
Motor overtemperature alarm. Possible causes:
- Load cycle too heavy
- The motor is installed in a place where the ambient temperature is too high
- If the motor is provided with a blower: the fan is not working
- If the motor is not provided with a blower: the load is too high at slow speeds. Cooling the fan on the motor shaft is not sufficient for this load cycle.
- The motor is used at less than the rated frequency, causing additional magnetic losses.
Solution:
- Change the processing cycle.
- Use a cooling fan to cool the motor.
13
Drive overload [DOL]
Condition:
Drive overload alarm.
- The inverter output current has exceeded the allowed overload value.
- The overload cycle has exceeded the allowed values.