WEG ADL300 drive fault codes list

A technical guide to diagnosing, troubleshooting, and resetting common alarms and faults on the WEG ADL300 (Gefran SIEIDrive) elevator inverter.

The WEG ADL300 series (originally developed as part of the Gefran SIEIDrive lift line and now supported under WEG Automation Europe) is a specialized vector inverter designed specifically for elevator and lift applications. It is engineered to control both asynchronous (induction) and synchronous (permanent magnet) motors, ensuring smooth travel profiles, precise landing control, and strict safety compliance.

This guide explains how to interpret these alarm codes, perform a safe system reset, and carry out diagnostics for common elevator drive issues.

WEG ADL300 Fault and Alarm Reference Table

Refer to your specific diagnostic codes to identify the exact warning or trip active on your drive's keypad display or serial communication tool. Matching the active code to its specific trigger speeds up the troubleshooting process.

WEG ADL300 drive fault codes list

WEG ADL300 drive fault codes list

Alarm Code, Display [Integrated Keypad] Cause and Solution / Remedy
0

No alarm
Cause:

No alarm present.

Remedy:

No action required.
1 [OV]

Overvoltage

Display: O U
Cause:

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.

Remedy:

  • Extend the deceleration ramp.
  • Use a braking resistor to dissipate the energy recuperation, to be connected to the specific terminals (see section "7.1.9 Connection of braking resistor (optional)" on manual pages).
  • Use the VDC Control function.
2 [UV]

Undervoltage

Display: U u
Cause:

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 voltage 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.).


Remedy:

Check the connections and mains voltage.
3 [GNDF]

Ground fault

Display: G n d F
Cause:

Ground short circuit alarm.

Remedy:

  • Check drive and motor wiring.
  • Check that the motor is not grounded.
4 [OC]

Overcurrent

Display: o C
Cause:

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.

Remedy:

  • Check the current regulator parameters (menu 17).
  • Check wiring towards the motor.
5 [DES]

Desaturation

Display: d E S
Cause:

Instantaneous overcurrent in the IGBT bridge alarm.

Remedy:

  • Switch the drive off and then switch it on again.
  • Check the condition of the braking resistor isolation. Make sure there are no earth leakages.
  • If the alarm persists, contact the technical service centre.
6 [MUV]

MultiUndervolt

Display: n U O
Cause:

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.

Remedy:

Too many Undervoltage alarms. Adopt the proposed solutions for the Undervoltage alarm.
7 [MOC]

MultiOvercurr

Display: n O C
Cause:

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

Remedy:

Too many Overcurrent alarms. Adopt the proposed solutions for the Overcurrent alarm.
8 [MDES]

MultiDesat

Display: n d E S
Cause:

Two attempted 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.

Remedy:

Too many Desaturation alarms. Adopt the proposed solutions for the Desaturation alarm.
9 [HOT]

Heatsink OT

Display: H o t
Cause:

Heatsink temperature too high alarm.

Remedy:

  • 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.
10 [HSOT]

HeatsinkS OTUT

Display: H S O t
Cause:

IGBT modules temperature too high or too low alarm.

Remedy:

  • 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 [IOT]

Intakeair OT

Display: I O t
Cause:

Input air temperature too high alarm.

Remedy:

  • Check correct fan operation.
  • Check that panel cooling air openings are unobstructed.
  • Check temperature in electrical panel.
12 [MOT]

Motor OT

Display: n O t
Cause:

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.


Remedy:

  • Change the processing cycle.
  • Use a cooling fan to cool the motor.
13 [DOL]

Drive overload

Display: d o L
Cause:

Drive overload alarm.
  • The inverter output current has exceeded the allowed overload value.
  • The overload cycle has exceeded the allowed values.


Remedy:

  • Check that the load is not excessive.
  • Check that accelerations are not excessive.
  • Check that the overload cycle is within allowed limits.
14 [MOL]

Motor overload

Display: n O L
Cause:

Motor overload alarm. The current absorbed during operation is greater than that specified on the motor data plate.

Remedy:

  • Reduce the motor load.
  • Increase the size of the motor.
15 [BOL]

Bres overload

Display: b o L
Cause:

Braking resistor overload alarm. The current absorbed by the resistor is greater than the rated current.

Remedy:

  • Check the size of the braking resistor.
  • Check the condition of the braking resistor.
16 [PHL]

Phase loss

Display: P H L
Cause:

Power phase loss alarm.

Remedy:

Check the mains voltage and whether any protections upstream of the drive have been tripped.
17 [OPTB]

Opt Bus fault

Display: o P t b
Cause:

Error in the configuration stage or communication error.
  • XXX0H-X: If the first digit to the left of "H" in the alarm sub-code is equal to 0, the error relates to a communication problem.
  • XXXXH-X: If the first digit to the left of "H" in the alarm sub-code is other than 0, the error relates to a configuration problem.


Remedy:

For configuration errors, check the configuration of the Bus communication, Bus type, Baudrate, address, and parameter settings.

For communication errors verify wiring, resistance of terminations, interference immunity, and timeout settings. For further details reference should be made to the datasheet of the bus being used.
18 [OPT1]

Opt 1 IO fault

Display: o P t 1
Cause:

Error in the communication between Regulation and I/O expansion card in slot 1 (Advanced version only).

Remedy:

Check that it has been inserted correctly, see Appendix section A.1.
19

Opt 2 IO fault

Display: o P t 2
Cause:

Error in the communication between Regulation and encoder expansion card in slot 2 (Advanced version only).

Remedy:

Check that it has been inserted correctly, see Appendix section A.1.
20 [OPTE]

Opt Enc fault

Display: o P t E
Cause:

Error in the communication between Regulation and Encoder feedback card (Advanced version only).

Remedy:

Check that it has been inserted correctly, see Appendix section A.1.
21 [EF]

External fault

Display: E F
Cause:

External alarm present. A digital input has been programmed as an external alarm, but the +24V voltage is not available on the terminal.

Remedy:

Check that the terminal screws are tight.
22 [SFL]

Speed fbk loss

Display: S F L
Cause:

Speed feedback loss alarm. The encoder is not connected, not connected properly or not powered: verify encoder operation by selecting the PAR 260 Motor speed parameter in the MONITOR menu.

Remedy:

See parameter 2172 SpdFbkLoss code for information about the cause of the alarm and chapter 10.2 Speed fbk loss [22] alarm.
23 [OS]

Overspeed

Display: o S
Cause:

Motor overspeed alarm. The motor speed exceeds the limits set in the PAR 4540 parameter.

Remedy:

  • Limit the speed reference.
  • Check that the motor is not driven in overspeed during rotation.
24 [SRL]

Speed ref loss

Display: S r L
Cause:

Speed reference loss alarm; occurs if the difference between the speed regulator reference and the actual motor speed is more than 100 rpm. This condition occurs because the drive is in the current limit condition. It is only available in the Flux Vect OL and Flux Vect CL mode (see PAR 4550).

Remedy:

Check that the load is not excessive.
26 [PRR]

Power down

Display: P d
Cause:

The drive was enabled with no supply voltage at the power section.

Remedy:

Check drive power supply.
27 [PHLO]

Phaseloss out

Display: P H L o
Cause:

Output phase loss.

Remedy:

Check Drive/motor connection.
28 [OVSF]

OV safety

Display: b U S F
Cause:

Safety status alarm caused by Overvoltage situations.

Remedy:

The firmware attempts to reset the card automatically. If the condition is removed (the alarm cleared message is displayed), the alarm can be reset and the drive restarted by deactivating and reactivating Enable and Start.
29 [SF]

Safety failure

Display: S F
Cause:

The state of the "safety function" is communicated to the regulation card via 2 digital inputs: SAFETY_ON (pin P1.8) and SAFETY_EN (pin P1.9).

Remedy:

Switch the drive off and then back on. If the error persists, contact the technical service centre.
30 [MOTL]

Mot phase loss

Display: n O t L
Cause:

Output phase loss.

Remedy:

Check Drive/motor connection.
31 [ROPC]

Rope change

Display: P o P C
Cause:

This may occur under two conditions:
  • The drive continues to run but the rope usage threshold set in parameter 3404 Ropes change thr has been reached.
  • The drive finishes the current travel and then locks because parameter 3414 Direction counter has reached 0 (corresponding to parameter 3412 Ropes usage = 100%).


Remedy:

Replace the ropes. By switching the drive off and back on, you can run a single travel to bring the car to a better position for the procedure. After you have changed the ropes, reset the direction change counter to eliminate the lock condition.
32 [PERR]

Phasing error

Display: P E r r
Cause:

Motor phasing error at startup.

Remedy:

Check encoder configuration parameters, parameter 2028 Take status, and encoder electrical connections.
33 ... 40 [PLC1...8]

Plc1 fault ... Plc8 fault

Display: P L C 1 ... P L C 8
Cause:

Enabled application developed in the IEC 61131-3 environment has found the conditions for generating this specific alarm to be true. The meaning of the alarm depends on the type of application.

The XXXXH-X sub-code indicates the reason for the error.

Remedy:

Refer to the documentation concerning the enabled application. Make a note of the XXXXH-X code to discuss it with the service centre.

With regards to the standard application EFC, refer to the Functional Parameter Manual section LIFT ALARMS. For the applications DCP3/DCP4, EPC, and CiA 417, refer to the application manual section ALARMS.
41 [WDT]

Watchdog

Display: y d t
Cause:

May occur during functioning when the watchdog microcontroller protection is enabled; the alarm is included in the list of alarms and alarm log. Following this alarm:
  • The drive automatically runs a reset.
  • Motor control is not available.
The XXXXH-X sub-code indicates the reason for the error.

Remedy:

If the alarm was the consequence of a change in the drive configuration (parameter setting, option installation, PLC application download), remove it. Switch the drive off and then on again. Make a note of the XXXXH-X code to discuss it with the service centre.
42 [TRAP]

Trap error

Display: E r A P
Cause:

This condition can occur during operation when the trap micro protection is enabled. The alarm is included in the list of alarms and alarm log. Following this alarm:
  • The drive automatically runs a reset.
  • Motor control is not available.
The XXXXH-X code (SubHandler-Class) indicates the reason for the error.

Remedy:

If the alarm was a consequence of a variation to the drive configuration (parameter setting, installation of an option, downloading of a PLC application), remove it. Switch the drive off and then switch it on again. Make a note of the XXXXH-X (SubHandler-Class) code to discuss it with the service centre.
43 [SYS]

System error

Display: 5 4 5
Cause:

This condition can occur during operation when the operating system protection is enabled. The alarm is included in the list of alarms and alarm log. Following this alarm:
  • The drive automatically runs a reset.
  • Motor control is not available.
The XXXXH-X code (Error-Pid) indicates the reason for the error.

Remedy:

If the alarm was a consequence of a variation to the drive configuration (parameter setting, installation of an option, downloading of a PLC application), remove it. Switch the drive off and then switch it on again. Make a note of the XXXXH-X (Error-Pid) code to discuss it with the service centre.
44 [USR]

User error

Display: U S r
Cause:

This condition can occur during operation when the software protection is enabled. The alarm is included in the list of alarms and alarm log. Following this alarm:
  • The drive automatically runs a reset.
  • Motor control is not available.
The XXXXH-X (Error-Pid) code indicates the reason for the error.

Remedy:

If the alarm was a consequence of a variation to the drive configuration (parameter setting, installation of an option, downloading of a PLC application), remove it. Switch the drive off and then switch it on again. Make a note of the XXXXH-X (Error-Pid) code to discuss it with the service centre.
45 [PE]

Param error

Display: P E
1 [LDEF]

Load default param

Display: L d E F
Cause:

May occur during loading of the parameter database saved in flash. This normally appears at initial power-on when a new firmware version is downloaded, when the regulation is installed on a new size, or when the region is changed.

If this message is displayed when the drive is already operating, this means that a problem has occurred in the parameter database saved in Flash. If this message is displayed, the drive automatically performs the Load default command.

Diagnostic Sub-codes:
  • 0001H-1: The database saved is not valid
  • 0002H-2: The database saved is not compatible
  • 0003H-3: The database saved refers to a different size from the current size
  • 0004H-4: The database saved refers to a different region from the current region

Remedy:

Set the parameters to the value required and perform Save parameter.
2, 3, 4 [OPT1, OPT2, OPT3]

Option detect slot 1, 2, 3

Display: o P t 1 / o P t 2 / o P t 3
Cause:

When the drive is turned on, it recognises the presence of an optional card. One of the sub-code messages is shown on the display for a few seconds.

Diagnostic Sub-codes:
  • 0H-0: None
  • 0004H-4: Can
  • 0008H-8: Enc 1 EXP-DE-I1R1F2-ADL
  • 0108H-264: Enc 2 EXP-SE-I1R1F2-ADL
  • 0208H-520: Enc 3 EXP-SESC-I1R1F2-ADL
  • 0308H-776: Enc 4 EXP-EN/SSI-I1R1F2-ADL
  • 0408H-1032: Enc 5 EXP-HIP-I1R1F2-ADL
  • 0508H-1288: Enc 6 EXP-RES-I1-ADP/ EXP-RES-I1R1-ADP
  • 0101H-257: I/O 1 EXP-IO-D4-ADL
  • 0501H-1281: I/O 1 EXP-IO-D8R4-ADL
  • 0901H-2305: I/O 1 EXP-IO-D16R4-ADL
  • 0F01-3841: I/O 1 EXP-IO-D12A2R4-ADL
  • 1301H-4865: I/O 1 EXP-IO-D8A4R4-ADL
  • 1501H-5377: I/O 1 EXP-IO-D6R2-F-ADL
  • 00FFH-255: Unknown

Remedy:

This is a temporary informational display. No troubleshooting action is required unless the wrong module type is identified.
5 [SLFT]

Autotune (motor)

Display: S L F t
Cause:

May occur during the self-tuning procedure.

Diagnostic Sub-codes:
  • 0: No error.
  • 1: N.A.
  • 2: N.A.
  • 3: The motor plate data parameters have changed but the Take parameters command, PAR 2020, has not been executed.
  • 4: The motor is not connected.
  • 5: While running self-tuning, the ESC key was pressed, the enable contact was opened, or an alarm occurred. The self-tuning command was sent with the drive in the alarm condition.
  • 6: A setting performed by the self-tuning function produced a parameter value outside the min or max range (e.g., motor plate data or drive/motor sizes combined incorrectly).
  • 7: The self-tuning command was sent without being enabled.
  • 8 ... 21: A setting performed by self-tuning has reached a measurement method limit.
  • 30: The Enable was not given or removed in time during the phasing procedure.

Remedy:

If the message appears with a value other than 0, follow the instructions supplied for each particular case and repeat self-tuning. This should be performed using the wizard function available from the keypad (STARTUP WIZARD) and the Tool software on the PC.

Pay attention to all motor plate data parameters, especially:
  • Rated speed, Motor rated speed in rpm:
    • Asynchronous motor: Take care not to set the Rated speed parameter to the synchronous speed. The value of the Rated speed parameter must be less than: [(Rated frequency × 60) / Pole pairs].
    • Synchronous motor: Take care to set the Rated speed parameter to the synchronous speed.
  • Rated frequency, Motor rated frequency in Hz
  • Pole pairs, Motor pole pairs
If the problem persists, confirm the values of the motor plate parameters and execute the Take parameters command, but do not run self-tuning.
5 [SLFT]

Autotune (phasing) - Only Synchronous

Display: S L F t
Cause:

May occur during the self-tuning phasing procedure on synchronous motors.

Diagnostic Sub-codes:
  • 0: No error
  • 40: The encoder card in use cannot manage automatic phasing.
  • 41: Incorrect Incremental encoder impulse count.
  • 42: Incorrect absolute encoder impulse count.
  • 43: Incorrect incremental encoder impulse count or incorrect absolute encoder impulse count probably caused by an incorrect value of the pole pairs parameter or a load applied to the motor.
  • 44: Incorrect incremental encoder impulse count probably caused by the incorrect value of the encoder impulse parameter.
  • 45: Incorrect absolute encoder impulse count.
  • 46: Incremental encoder impulse count sign inverted with respect to the absolute encoder impulse count.
  • 47: Incremental encoder impulse count sign inverted with respect to the absolute encoder impulse count.
  • 48: Incorrect phase sequence. (Message not signalled)
  • 49: During automatic phasing, a communication channel is activated between the drive and encoder. An error has occurred on this communication channel.

Remedy:

If the message has a value other than 0, follow the instructions provided for each case and repeat automatic phasing:
  • For sub-code 40: Use the appropriate encoder card.
  • For sub-code 41 / 44: Check the electric signals of the incremental encoder. Check the value of the encoder impulse parameter.
  • For sub-code 42 / 45: Check the electric signals of the absolute encoder. Check the configuration of the absolute encoder.
  • For sub-code 43: Check the value of the pole pairs parameter, and check whether a load is applied.
  • For sub-code 46: Invert the A+ and A- signal of the incremental encoder.
  • For sub-code 47: Invert the A+ and A- signal of the absolute encoder.
  • For sub-code 48: The automatic procedure has modified the setting of the Encoder direction parameter. No other action is required.
  • For sub-code 49: Repeat the procedure.
6 [PC]

Power config

Display: P C
Cause:

May occur during recognition of power cards. If this message is displayed, it is not possible to drive the motor.

Diagnostic Sub-codes:
  • 0020H-32: The power card is configured for a drive that is incompatible with the regulation card.
  • 0021H-33: The configuration of the power card is not compatible with the regulation card.
  • 0017H-23: The configuration required is not available on the power card.

Remedy:

Download the correct configuration on the power card.
7 [FAIL]

Save par failed

Display: F A I L
Cause:

Occurs during transfer of the parameters from the drive to the memory of the keypad.

Diagnostic Sub-codes:
  • 0H-0: Communication error.
  • 0023H-35: Communication error.
  • 0023H-36: Communication error.
  • 0025H-37: The data saved on the keypad are not valid.

Remedy:

Verify keypad physical connection and check for noise on the communication bus.
8 / 9 [FAIL]

Load par failed / Load par incomplete

Display: F A I L
Cause:

Occurs during transfer of the parameters from the memory of the keypad to the drive.

Diagnostic Sub-codes:
  • 0H-0: Communication error.
  • 0023H-35: Communication error.
  • 0023H-36: Communication error.
  • 0025H-37: The data saved on the keypad are not valid. No parameter is transferred from the keypad to the drive.
  • 0026H-38: Incompatible drive series. No parameter is transferred.
  • 0027H-39: Incompatible software version. All the parameters present in the memory of the keypad have been transferred to the drive. The set of parameters transferred refers to a drive with a different firmware version; therefore, certain parameters may not be updated.
  • 0028H-40: Incompatible drive size. All the parameters present in the memory of the keypad (excluding those that depend on the size of the drive) have been transferred to the drive. The parameters that depend on size maintain their original value.
  • 0029H-41: Error during saving of parameters on the drive. The transfer of one or more parameters has caused an "out of range" error, or one or more parameters does not exist. At the end of transfer, some parameters may not have been updated.
  • 002AH-42: PLC application release and version not compatible. All parameters in the keypad memory have been transferred to the drive. The transferred set of parameters relates to a drive with a PLC application in which the version and release of the application are different.
  • 002BH-43: PLC application not compatible. All parameters in the keypad memory except those relating to the PLC application have been transferred to the drive.

Remedy:

Recover a set of parameters from a compatible drive (matching model and size).
10 [OPTC]

Options config error

Display: o P t C
Cause:

May occur at drive start-up, during recognition of the optional cards installed.

Diagnostic Sub-codes:
  • 0001H-1: Non-permissible optional card in slot 1
  • 0002H-2: Non-permissible optional card in slot 2
  • 0004H-4: Slot configuration mismatch
  • 0010H-16: Conflict slot 1 with slot 2
  • 0020H-32: Slot configuration mismatch
  • 0040H-64: Slot configuration mismatch

Remedy:

Remove the optional cards from the incorrect slots and insert them in the correct slots.
11 [LDPL]

Load def plc

Display: L d P L
Cause:

May occur during loading of the parameter database saved in the Flash of the Mdplc application. Normally appears at initial power-on after downloading a new application.

If this message is displayed when the drive is already operating, this means that a problem has occurred in the parameter database saved in Flash. The drive restores the default database.
  • 0001H-1: The database saved is not valid.

Remedy:

Set the parameters to the value required and perform Save parameter.
12 [PLCE]

Plc cfg error

Display: P L C E
Cause:

May occur during loading of the Mdplc application. The Mdplc application present on the drive is not run.
  • 0004H-4: The application downloaded has a different CRC on DataBlock and Function table.
  • 0065H-101: The application downloaded has an invalid identifier (Info).
  • 0066H-102: The application downloaded has an incorrect task number (Info).
  • 0067H-103: The application downloaded has an incorrect software configuration.
  • 0068H-104: The application downloaded has a different CRC on DataBlock and Function table.


Remedy:

Remove the Mdplc application or download a correct Mdplc application.
12 [PLCE]

Plc cfg error (Continuation)

Display: P L C E
Cause:

Fault related to Mdplc application loading (continued).
  • 0069H-105: A Trap error or System error has occurred. The drive automatically performs a Power-up operation. The application is not run. See in Alarm List for further information regarding the error occurred.
  • 006AH-106: The application downloaded has an incorrect identifier (Task).
  • 006BH-107: The application downloaded has an incorrect task number (Task).
  • 006CH-108: The application downloaded has an incorrect CRC (Tables + Code).


Remedy:

Remove the Mdplc application or download a correct, valid Mdplc application file.
13, 14, 15, 16 [PLC1...4]

Plc 1 ... Plc 4

Display: P L C 1 / P L C 2 / P L C 3 / P L C 4
Cause:

Reserved messages dedicated to the PLC application.

Remedy:

See the application manual for specific PLC instructions.
17 [OPTB]

Opt bus fault

Display: o P t b
Cause:

This may occur during fieldbus card setup on drive power-on. It indicates a configuration or communication error.
  • XXX0H-X (Communication Problem): If the first digit to the left of "H" in the alarm sub-code is 0.
  • XXX0H-X (Configuration Problem): If the first digit to the left of "H" in the alarm sub-code is other than 0.


Remedy:

  • For configuration errors, check the configuration of the bus communication, type of bus, baudrate, address, and parameter settings.
  • For communication errors, verify wiring, termination resistors, disturbance immunity, and timeout settings.
Refer to the user guide for the specific bus in use.
18 [KEYF]

Wrong key

Display: H E 4 F
Cause:

This may occur when powering the drive if the incorrect enable key is inserted for a given firmware function.
  • xxxxH-x: Incorrect PLC key. PLC application is not available.


Remedy:

Contact WEG to obtain the correct key to enable the desired firmware function.
19 [KEYE]

Key expiring

Display: H E 4 E
Cause:

This may occur at drive power-on if an incorrect enabling key was inserted for a given firmware function. At this stage, the firmware function can still be used freely, but the trial time limit is about to expire.
  • xxxxH-x: Number of hours for which the function can still be used freely.


Remedy:

Contact WEG to obtain the correct permanent key to enable the desired firmware function.
20 [FAIL]

SD card error

Display: F A I L
Cause:

This condition may occur when sending data from the drive to the SD card or from the SD card to the drive. It is typically caused by a memory card that is incompatible or not present.
  • XXX0H-X: Communication error.


Remedy:

Check the physical connection and compatibility of the memory card being used.
21 [PE]

Parameter error

Display: P E
Cause:

An error occurs during the activation of the parameter database saved in flash; one or more parameters have values out of range.
  • XXX0H-X: Code XXXXH-X indicates the number of the parameter (Hex-Dec) that has caused the error.


Remedy:

Set the parameter causing the error to the correct value and execute Save parameters, then switch the drive off and back on again. Make a note of the specific sub-code to discuss with the service center.
22 [ENCE]

Encoder error

Display: E n C E
Cause:

This condition may occur when the drive is powered during encoder setup each time parameter 552 Regulation mode is set.
  • 100H-256: An error occurred during setup; the information received from the encoder is not reliable. If the encoder is used for feedback, the Speed fbk loss alarm is also generated.
  • 200H-512: The firmware on the optional encoder card is incompatible with that on the regulation card. The information received from the encoder is not reliable.


Remedy:

  • For sub-code 100H-256, take the recommended action for the Speed fbk loss alarm.
  • For sub-code 200H-512, contact WEG to update the firmware on the optional encoder card.
23 [OCFG]

Options cfg changed

Display: o C F G
Cause:

This may occur when powering the drive if an expansion card has been removed or replaced, or the incorrect enable key is inserted for a given firmware function.
  • 0064H-100: Card removed from slot 1
  • 0014H-20: Card removed from slot 2
  • 0078H-120: Card removed from slot 1 and from slot 2


Remedy:

Check the physical hardware configuration, then press ESC. Save the parameters (Save parameters, menu 04.01 par 550) to save the new hardware configuration.
24 [FAIL]

Fw update failed

Display: F A I L
Cause:

During a firmware update, the system detected that the file is in the wrong format or is corrupt.

Remedy:

Try the update again with a correct, uncorrupted firmware file.

How to Safely Reset a WEG ADL300 Drive Fault

Before attempting to clear a fault, you must identify and address its physical cause. Resetting a persistent hardware or mechanical fault repeatedly can result in component damage. The ADL300 can be reset using these standard practices:

  1. Power Cycle (Mains Disconnection): Switch off the main AC input disconnect. Important Safety Requirement: For ADL300 frame sizes 1 through 5, you must wait at least 300 seconds (5 minutes) to allow the DC link capacitors to discharge to a safe voltage level before accessing internal parts or re-applying power.
  2. Keypad Reset: Press the red reset or stop key on the drive's HMI.
  3. Digital Input (DI) Control: If one of your control terminal inputs is mapped to the "Fault Reset" function, trigger that command from the elevator control cabinet or PLC.

Primary Categories of ADL300 Faults

While the lift controller displays various codes, most service calls for elevator drives relate to a few specific parameters:

1. Overvoltage [OV]

The [OV] code indicates that the DC link voltage has exceeded the maximum safety limit. This typically occurs during deceleration of a heavy cabin or when the car travels in a regenerative direction (e.g., a fully loaded cabin traveling down or an empty cabin traveling up).

  • Solution: Verify that the dynamic braking resistor is correctly wired and has not suffered an open circuit. Measure the resistor's resistance value and verify that it matches the recommended specifications.

2. Undervoltage [UV]

An [UV] alarm occurs when the DC link voltage drops below the minimum operating threshold. This is common during line power sags, when output contactors drop out, or due to poor incoming electrical connections.

  • Solution: Check the stability of the incoming utility lines and ensure all power terminal screws are tightened. If the elevator uses an emergency UPS or battery backup, ensure the battery bank is sufficiently charged.

3. Overcurrent [OC]

The [OC] fault triggers when current draw exceeds safe inverter thresholds. It can point to an instantaneous short circuit, a grounded motor winding, or incorrect tuning of the current regulator loop.

  • Solution: Perform an insulation test (megger test) on the motor cables and check for output phase imbalances. If the motor was recently replaced, check the motor parameters and verify the autotuning process was completed successfully.

4. Encoder & Speed Feedback Alarms [PLS]

Elevator drives rely heavily on precise encoder feedback to maintain speed curves, especially on synchronous permanent magnet gearless machines. A loss of signal or mismatched reading triggers speed feedback or encoder error alarms.

  • Solution: Check the mechanical mounting of the encoder to the motor shaft. Verify that the encoder cable shielding is grounded correctly to prevent high-frequency electrical noise from corrupting the signal.

Best Practices for Elevator Drive Maintenance

Because elevator drives run in semi-controlled environments, a regular preventative maintenance schedule helps keep them operational:

  • Manage Cabinet Ventilation: Elevator machine rooms can experience high ambient temperatures. Clean or replace cabinet air filters and verify that the drive’s internal heatsink fan operates correctly.
  • Check Brake Monitoring Systems: In compliance with elevator safety standards (such as EN 81-20/50 and A3 amendments), ensure the mechanical brake microswitches are properly integrated with the drive's monitoring inputs.
  • Mitigate Vibration: Keep control cabinets isolated from heavy mechanical vibrations, which can cause loose terminal connections or premature fatigue in internal relay contacts.

Carefully evaluating active codes and maintaining a clean environment will help keep your WEG ADL300 drive operating reliably over its service life.

Comments

Popular posts from this blog

Allen Bradley Kinetix 5500 Drive Fault Codes List

Danfoss VACON 100 FLOW Drive Fault Codes List

ABB ACH580 Drive Fault Codes List