Diagnose, troubleshoot, and reset common alarms, faults, and pressure sensor errors on the WEG ADP200 (Gefran) servopump injection molding drive.

The WEG ADP200 series (originally designed under the Gefran SIEIDrive family and now supported by WEG Automation Europe) is a specialized variable speed drive engineered for servopump control in hydraulic systems, particularly injection molding machines (IMMs) . Operating with synchronous servo motors in a closed-loop field-oriented control (FOC) configuration, it uses a highly integrated PID-IMM application software to manage precise flow and pressure dynamics .

Because hydraulic and injection molding applications demand precise timing and mechanical coordination, the ADP200 incorporates sophisticated self-protection routines. Diagnoses are generally split into two categories on the integrated keypad:

• Alarms: Non-critical warnings that indicate an out-of-spec operational state (such as a minor thermal overload warning). The drive will continue to run, but action should be taken to prevent a hard shutdown.
• Faults: Critical trip events that immediately disable the drive's output power to protect the internal power stage (IGBTs) and the connected servo motor. The drive remains in a faulted lock state until it is cleared.

This technical guide details how to navigate these system diagnostics, safely clear trips, and troubleshoot common servopump-specific faults.

WEG ADP200 Fault and Alarm Reference Table

Locate the specific fault code or alarm message shown on your HMI display or through the serial communication interface to identify the corrective action needed.

WEG ADP200 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 between terminals BR1 and BR2 to dissipate the recovered energy. 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. Verify parameters and trace incoming power lines.
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. 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: Intake drive 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. Motor temperature probe not connected or incorrect setting of parameters 4530, 4538 and 4522. Remedy: Change the processing cycle. Use a cooling fan to cool the motor. Check the connection of the motor temperature probe or the settings of parameters 4530, 4538 and 4522.
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. The overload threshold of the accumulator of the I²t braking resistor thermal image has been exceeded. For standard external braking resistor the Max overload (factory set) is 1” service 10% (see Table 5.4.1 on ADP200 QS manual). Remedy: Check the size of the braking resistor. Check the condition of the braking resistor. Use braking resistor with higher energy value and change the parameters on 22.5 - FUNCTIONS/BRES OVERLOAD menu.
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, parameter setting. For communication errors verify wiring, resistance of terminations, interference immunity, and timeout settings. For further details, please refer to the user guide for the specific bus.
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. Remedy: Check that it has been inserted correctly, see Appendix section A.1.
19 [OPT2] Opt 2 IO fault Display: o P t 2	Cause: Error in the communication between Regulation and encoder expansion card in slot 2. 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. 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. Generated in case of an encoder fault. Each type of encoder generates a “Loss of feedback” alarm differently. Remedy: Check encoder wiring for integrity. Check that the encoder is connected to the power supply. With the drive disabled, turn the motor clockwise (seen from the motor shaft side). A positive value must be displayed. If the value does not change or values are indicated randomly, check the encoder power supply and cables. If the value displayed is negative, invert the encoder connections. Change channel A+ and A- or B+ and B-. Check that the encoder electronics are consistent with those of the relative expansion card. 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. Remedy: Check the drive load conditions. Check the number of encoder impulses. Note: It is only available in the Flux Vect OL and Flux Vect CL mode (see PAR 4550).
25 [EMGS] Emg_stop_alarm Display: E N G S	Cause: Emergency stop alarm. The Stop key on the keypad was pressed with the PAR 1008 Stop key mode parameter set to EmgStop&Alarm. Active in remote control mode (PAR 1012=1) both by using “Terminals” command or “Digital” commands and, in local control mode (PAR 1012=0) by using “Terminals” command. Remedy: Eliminate the reason for which the Stop key on the keypad was pressed and reset the drive.
26 [PD] Power down Display: P d	Cause: The drive was enabled with no supply voltage at the power section. Remedy: Check the drive power supply.
30 [PROT] Motor pre OT Display: P r o t	Cause: Motor overtemperature prealarm. % value of threshold compared to PAR 4532 MotorOT thr. Remedy: Verify if the value is set too low for the current duty cycle. Ensure the motor is not overloaded.
31 [PHLO] Mot phase loss Display: P H L o	Cause: Output phase loss. Remedy: Check the Drive/motor output connections.
33 ... 40 [PL01...08] 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.
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: t 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 [PRR] Param error Display: P r r	Cause: An error occurs during the enabling of the parameter database saved in the Flash memory; one parameter value is out of range. The XXXH-X code indicates the number of the parameter (Hex) that has caused the error when the database is enabled. Remedy: Set the parameter causing the error to a value within the range and run Save parameter. Switch the drive off and then switch it back on again. If the IPA of the parameter is not shown in the manual, contact the service centre.
46 [LD] Load default Display: L d	Cause: Can occur during loading of the parameter database saved in the Flash memory. This is normal if it appears under the following conditions: The first time the drive is switched on. When a new version of the firmware is downloaded. When the regulation card is installed on a new size. When a new region is entered. If this message appears when the drive is already in use, it means there has been a problem in the parameter database saved in the Flash memory. When displayed, the drive restores the default database. 0001H-1: The database saved is not valid 0002H-2: The database saved is not compatible 0003H-3: The saved database refers to a different size and not to the current size 0004H-4: The saved database refers to a different region and not to the current region Remedy: Set the parameters to the desired value and execute Save parameters.
47 [PLCE] Plc cfg error Display: P L C E	Cause: Occurs during MDPLC application loads. The Mdplc application on the drive is not run. 0004H-4: The application that has been downloaded has a different CRC on the DataBlock and Function table. 0065H-101: The application that has been downloaded has an invalid identification code (Info). 0066H-102: The application that has been downloaded uses an incorrect task number (Info). 0067H-103: The application that has been downloaded has an incorrect software configuration. 0068H-104: The application that has been downloaded has a different CRC on the DataBlock and Function table. 0069H-105: A Trap error or System error has occurred. The drive has automatically executed a Power-up operation. Application not executed. See the Alarm List for more information about an error that has occurred. 006AH-106: The application that has been downloaded has an invalid identification code (Task). 006BH-107: The application that has been downloaded uses an incorrect task number (Task). 006CH-108: The application that has been downloaded has an incorrect CRC (Tables + Code). Remedy: Remove the MDPLC application or download a correct MDPLC application.
48 [LDP] Init_LdPlcPar Display: L d P	Cause: Can occur during loading of the parameter database saved in the Flash memory of the MDPLC application. This is normal if it appears the first time the drive is switched on, after downloading a new application. If it appears when already in use, there has been a database error. The drive automatically runs the Load default PAR 580 command. 0001H-1: The database saved is not valid. Remedy: Set the parameters to the desired value and run Save parameter.
49 [KEY] Key failed Display: H E 4	Cause: This can occur at drive power-on if the wrong enabling key is entered for a given firmware function. 0001H-1: Incorrect PLC key. PLC application not available. Remedy: Contact WEG to request the key to enable the desired firmware function.
50 [ENC] Encoder error Display: E n C	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 [22] 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 [22] alarm. For sub-code 200H-512, contact WEG to update the firmware on the optional encoder card.
51 [OCFG] Opt cfg change 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. 0003H-3: Card removed from slot 3. 0078H-120: Card removed from slot 1 and from slot 2. 0067H-103: Card removed from slot 1 and from slot 3. 0017H-23: Card removed from slot 2 and from slot 3. 007BH-123: Card removed from slot 1, from slot 2, and from slot 3. Remedy: Check the hardware configuration, then press ESC. Save the parameters (Save parameters, menu 04.01 par 550) to save the new hardware configuration.
52 [PCFG] Power config Display: P C F G	Cause: It can occur at the power-on during the recognition size phase. Remedy: Contact the WEG technical support centre.
53 ... 60 [PL09...16] Plc9 fault ... Plc16 fault Display: P L 0 9 ... P L 1 6	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.
64 [FC64] Fault code 64 Display: F C 6 4	Cause: It can occur at drive disabling. Remedy: Contact the WEG technical support center.
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 2 (EXP-IO-D8R4-ADL) 0901H-2305: I/O 3 (EXP-IO-D16R4-ADL) 0F01H-3841: I/O 4 (EXP-IO-D12A2R4-ADL) 1301H-4865: I/O 5 (EXP-IO-D8A4R4-ADL) 1501H-5377: I/O 6 (EXP-IO-D5R3-F-ADL) 1F01H-7937: I/O 7 (EXP-IO-D10A3R2-ADP) 2301H-8961: I/O 8 (EXP-IO-D8A4R2-ADP) 2701H-9985: I/O 9 (EXP-IO-D8A4R2-SM-ADP) 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 Autotune procedure. Diagnostic Sub-codes: 0: No error 1: The commands are not configured in Local mode. 2: The Commands local sel parameter has not been configured from the keypad. 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 Autotune command was sent with the drive in the alarm condition. 6: A setting performed by the Autotune function produced a parameter value outside the min or max range. (e.g., motor plate data or drive/motor sizes combined incorrectly). 7: The Autotune command was sent without being enabled. 8: Internal calculation error concerning IGBT control. 9: The drive has measured a stator resistance value exceeding the set limit. 10: The drive has measured a stator resistance value below the set limit. 11-12: Measurement of DTL internal compensation voltage outside accepted range. 13-14: Measurement of DTS internal voltage outside accepted range. 15-16-17: LS leakage inductance value outside accepted range. 18-19: Measurement of Im magnetising current outside accepted range. 20-21: Measurement of Rr rotor resistor outside accepted range. 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 Autotune. This should be performed using the keypad wizard function (STARTUP WIZARD) or the PC Tool software. Ensure all motor plate data parameters are correct, especially: Rated speed / Motor rated speed in rpm. Rated frequency / Motor rated frequency in Hz. Pole pairs / Motor pole pairs. Ensure the Rated speed parameter is configured to the synchronous speed. If the problem persists, confirm the values of the motor plate parameters and execute the Take parameters command, but do not run Autotune.
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: System error, the memory is insufficient. 0024H-36: System error, memory is not valid. Remedy: Check keypad connection. If memory is insufficient or invalid, clear unneeded configuration files or contact technical support.
8 [FAIL] Load par failed 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. 0024H-36: System error, the memory is insufficient. 0025H-37: The data saved on the keypad are not valid. No parameter is transferred from the keypad to the drive. Remedy: Verify the keypad connection. Re-save parameter data to the keypad or confirm the source parameter data is valid.
9 [LPNC] Load par incomplete Display: L P n C	Cause: Occurs during parameter loading from keypad memory due to structural incompatibilities. Diagnostic Sub-codes: 0026H-38: Incompatible drive series. No parameter is transferred from the keypad to the drive. 0027H-39: Incompatible software version. All parameters transferred, but some might not update due to different firmware versions. 0028H-40: Incompatible drive size. All parameters except those dependent on size are transferred. 0029H-41: Error during saving of parameters. Transfer caused an "out of range" error or missing parameter. 002AH-42: PLC application release and version not compatible. 002BH-43: PLC application not compatible. Application parameters will not update. Remedy: Recover a valid set of parameters from a compatible drive 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 / 0010H-16: Conflict slot 1 with slot 2 0020H-32 / 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 memory 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 automatically 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. 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 Mdplc application.
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 and dedicated to the PLC application. Remedy: See the application manual.
17 [OPTB] Opt bus fault Display: o P t b	Cause: This may occur when the drive is turned on, during fieldbus card setup. Error during 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, check wiring, termination resistors, disturbance immunity, and timeout settings. For further details, please refer to the user guide for the specific bus.
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. 0001H-1: Incorrect PLC key. PLC application not available. Remedy: Ask WEG to supply 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 the incorrect enabling key was inserted for a given firmware function. At this stage the firmware function can still be used freely, but this time limit is about to expire. XXXXH-X: Number of hours for which the function can still be used freely. Remedy: Ask WEG for the correct key to enable the desired firmware function.
20 [PE] Parameter error Display: P E	Cause: An error occurs during the enabling of the parameter database saved in flash; one parameter value is out of range. XXXXH-X (Code 0001H-1): Indicates that one or more parameters have value out of range. Remedy: Press the esc key and go inside Alarm log. Inside alarm Log there is Param error with a hex code of IPA parameter causing the error. Set the parameter that has caused the error to the correct value within the range and run Save parameters. Switch the drive off and then switch it back on again. If the IPA of the parameter is not shown in the manual, contact the service centre.
21 [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.
22 [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 0003H-3: Card removed from slot 3 0078H-120: Card removed from slot 1 and from slot 2 0067H-103: Card removed from slot 1 and from slot 3 0017H-23: Card removed from slot 2 and from slot 3 007BH-123: Card removed from slot 1, from slot 2, and from slot 3 Remedy: Check the hardware configuration, then press ESC. Save the parameters (Save parameters, menu 04.01 par 550) to save the new hardware configuration.
23 [SLFP] Autotune (phasing) Display: S L F P	Cause: This may occur during the Autotune procedure. 0: No error. 1: The commands are not configured in Local mode. 2: The Commands local sel parameter has not been configured from the keypad. 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 Autotune command was sent with the drive in the alarm condition. 6: A setting performed by the Autotune function produced a parameter value outside the min or max range (E.g., motor plate data or drive and motor sizes combined incorrectly). 7: The Autotune command was sent without being enabled. 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 1, 2, 7: Execute the requested configuration. For sub-code 3: Execute the Take parameters command. For sub-code 4: Connect the motor. For sub-code 5: Eliminate the reason for the alarm, remove the reason for the opening of the enable contact, and reset alarms. For sub-code 6: Check the motor plate data or drive and motor sizes. 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.
27 [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 could be due to an incompatible or missing memory card. 0000H-0: Communication error Remedy: Check the compatibility and physical presence of the memory card being used.
28 [FAIL] Fw update failed Display: F A I L	Cause: When updating the firmware, check whether the file is in the wrong format or corrupt. Remedy: Try again with a correct, uncorrupted firmware file.

How to Safely Reset a WEG ADP200 Drive Fault

Before executing any reset command, verify that the root cause of the error has been addressed. The ADP200 provides a few main pathways to execute a fault reset:

1. Power Cycle (Mains Disconnection): Disconnect the incoming three-phase AC power. Safety Precaution: Because the ADP200 is a high-performance system (handling capacities up to 75 kW), wait at least 15 minutes to allow the internal DC bus capacitors to fully discharge to safe voltage levels before touching any electrical terminals . Afterward, reapply power.
2. Digital Input (DI) Command: If you have mapped a digital input terminal (commonly DI5 or equivalent) to the "Fault Reset" function, trigger that contact via the machine’s main PLC .
3. Fieldbus Interface Reset: For installations utilizing industrial fieldbuses (such as CANopen or Modbus), you can transmit a "Fault Reset" control word directly from the master controller .

Common ADP200 Servopump Faults and Quick Diagnostics

Due to the specific physical demands of hydraulic servo-pump setups, certain warnings and trips are more prevalent than others in industrial settings:

1. Speed Feedback Loss Alarms

Because the ADP200 utilizes closed-loop vector control, any interruption in the encoder or resolver feedback signal will prompt a safety trip .

• Check: Inspect the resolver/encoder expansion card's seating in the control slots. Check the integrity of the encoder cable shielding, ensuring it is grounded correctly to prevent high-frequency electrical noise from corrupting the signal.

2. Application-Specific Pressure Sensor Alarms

When the drive runs in closed-loop pressure-flow mode, it monitors the analog voltage or current signal from the hydraulic manifold’s pressure transducer .

• Check: Alarms like "Pressure Sensor Alarm" indicate that the feedback signal has fallen outside the expected 4–20 mA or 0–10 V range . Check the physical sensor wiring, examine the sensor power supply, and verify that the hydraulic lines are free of air pockets.

3. Motor Overtemperature (Motor OT)

Servopump motors experience heavy duty cycles and can overheat if run continuously at high pressures without adequate cooling .

• Check: Verify that the motor temperature sensor (often a PT100 or PTC thermistor) is correctly wired to the designated terminal block on the drive's control board . Ensure the motor's independent cooling fan (if equipped) is operational.

4. Bres Overload [BOL] (Braking Resistor Overload)

This alarm occurs when excessive regenerative energy is fed back into the drive during high-deceleration cycles of the hydraulic pump .

• Check: Verify the physical condition of your dynamic braking resistor . If this occurs frequently during fast mold-opening or decompression phases, you may need to increase the braking resistor's wattage rating or adjust the deceleration ramp parameters.

Proactive Maintenance Guidelines

To avoid unexpected faults and extend the operational life of your ADP200 drive, establish the following preventive habits:

• Keep the Heatsink Clear: Hydraulic fluid mist mixed with dust can quickly coat the drive’s heatsink fins and internal fans. Regularly blow out dust and clean vents to prevent thermal trips.
• Secure Control Board Flat Cables: If the power boards or control cards are serviced or replaced, make sure all internal flat ribbon cables are locked securely using correct adapter brackets to prevent intermittent communication faults .
• Monitor Hydraulic Oil Temperatures: Hot hydraulic fluid transfers heat directly to the pump and motor shaft, raising the system's baseline temperature. Maintaining correct fluid temperatures helps prevent motor overload trips.

Approaching ADP200 diagnostics systematically helps you identify the root electrical or mechanical issue quickly, ensuring your hydraulic machinery remains safe and productive.