Emotron DSV Drive Fault Codes List
Troubleshoot your Emotron DSV15 or DSV35 drive. Learn how to navigate the P155.00 error history buffer, diagnose common faults, and reset trips safely.
The Emotron DSV series (including the DSV15 and DSV35 models) is a range of highly compact and functional AC drives covering power levels from 0.25 kW up to 30 kW . These drives support both asynchronous and synchronous motor control, offering high-performance features such as integrated Safe Torque Off (STO) and Ethernet-based fieldbus communication.
Emotron DSV Fault Codes Reference Table
Refer to your specific diagnostic tables to identify the exact 4-digit hexadecimal code active on your drive's display. Knowing the active code points you directly to the affected electrical circuit or parameter path.
Emotron DSV Drive Fault Codes List
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| Motor I2t I2t value exceeded. |
Cause: Motor overload according to programmed I2t settings. Remedy:
|
| PTC Motor thermistor exceeds maximum level. |
Cause: Motor overheating detected by PTC. Remedy:
|
| Motor Lost Phase loss or excessive imbalance on motor phases. |
Cause: Missing phase or poor motor connections. Remedy:
|
| Locked Rotor Torque limit reached at standstill. |
Cause: Mechanical blocking of rotor. Remedy:
|
| Over Temp Heatsink temperature too high. |
Cause: High ambient temperature, insufficient cooling, blocked fans or excessive current. Remedy:
|
| Over Curr F Motor current exceeds peak drive current. |
Cause: Short acceleration time, high load, short circuit or bad connections. Remedy:
|
| Over Volt D DC link overvoltage during deceleration. |
Cause: Deceleration time too short or brake resistor issue. Remedy:
|
| Under Voltage DC link voltage too low. |
Cause: Low supply voltage or mains voltage dip. Remedy:
|
| PF Curr Err Error in current balancing. |
Cause: Current imbalance between modules or phases. Remedy:
|
| Brake Brake fault or brake not engaged during stop. |
Cause: Brake acknowledge signal missing or brake circuit fault. Remedy:
|
| 8784 | 0x2250 CiA: continuous overcurrent (inside the device) Keypad display: PU over current |
Cause:
Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset after a blocking time of 5 s.)
|
| 8992 | 0x2320 CiA: Short circuit/earth leakage (internal) Keypad display: Earth leak |
Cause:
Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset after a blocking time of 5 s.)
|
| 9024 | 0x2340 CiA: Short circuit (device internal) Keypad display: Motor shorted |
Cause: Short circuit of motor cable. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset after a blocking time of 5 s.)
|
| 9040 | 0x2350 CiA: i²*t overload (thermal state) Keypad display: i2t motor |
Cause: Motor thermally overloaded, e.g. by an impermissible continuous current or by frequent or too long acceleration processes. Remedy: Response: Fault (The error can only be reset after a blocking time of 5 s. The error type can be configured in 0x2D4B:003 (P308.03).)
|
| 9090 | 0x2382 I*t error Keypad display: Ixt error |
Cause: Device utilisation (I*t) too high by frequent and too long acceleration processes. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset after a blocking time of 3 s. The error type can be configured in 0x2D40:005 (P135.05).)
|
| 9091 | 0x2383 I*t warning Keypad display: Ixt warning |
Cause: Device utilisation (I*t) too high by frequent and too long acceleration processes. Remedy: Response: Warning
|
| 9095 | 0x2387 Imax: Clamp responded too often Keypad display: Clamp timeout |
Cause: Maximum current of the axis (display in 0x2DDF:002) has been reached too often in succession. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts).)
|
| 9096 | 0x2388 SLPSM stall detection active Keypad display: SLPSM stall det. |
Cause: Overload of the motor with sensorless control for synchronous motors (SL-PSM). Remedy: Response: Trouble (The inverter is inhibited immediately. The motor becomes torqueless (coasts).)
|
| 12576 | 0x3120 Mains phase fault Keypad display: Mains Phase fail |
Cause: Mains phase failure. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts).)
|
| 12672 | 0x3180 Operation at UPS active Keypad display: UPS oper. active |
Cause: Operation on uninterrupted 1x230V current supply (UPS) has been activated: Only a reduced output current is provided. Remedy: Response: Warning
|
| 12816 | 0x3210 DC bus overvoltage Keypad display: DC Bus OV |
Cause: DC-bus voltage has exceeded the error threshold for overvoltage due to a too high braking energy or a too high mains voltage. The error threshold (display in 0x2540:006 (P208.06)) results from the setting of the rated mains voltage in 0x2540:001 (P208.01). Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts).)
|
| 12817 | 0x3211 DC bus overvoltage warning Keypad display: Warn.DC Bus OV |
Cause: DC-bus voltage has exceeded the warning threshold for overvoltage set in 0x2540:005 (P208.05) due to a too high braking energy or a too high mains voltage. Remedy: Response: Warning
|
| 12832 | 0x3220 DC bus undervoltage Keypad display: DC Bus UV |
Cause: DC-bus voltage has fallen below the error threshold for undervoltage. The error threshold (display in 0x2540:003 (P208.03)) results from the setting of the rated mains voltage in 0x2540:001 (P208.01). Remedy: Response: Trouble
|
| 12833 | 0x3221 DC bus undervoltage warning Keypad display: Warn.DC Bus UV |
Cause: DC-bus voltage has fallen below the warning threshold for undervoltage set in 0x2540:002 (P208.02). Remedy: Response: Warning
|
| 12834 | 0x3222 DC-bus voltage to low for power up Keypad display: DC-bus on-UV |
Cause: The input voltage is too low to switch on the inverter. Remedy: Response: Warning
|
| 16912 | 0x4210 PU: overtemperature fault Keypad display: PU Overtemp. |
Cause: The heatsink temperature of the power unit (display in 0x2D84:001 (P117.01)) has exceeded the fixed error threshold (100 °C).
Remedy: Response: Fault
|
| 17024 | 0x4280 Heat sink temperature sensor fault Keypad display: Heatsink sensor |
Cause: Sensor for the temperature monitoring of the power unit is defective. The failure of the temperature monitoring function poses the risk of overheating! Remedy: Response: Fault
|
| 17025 | 0x4281 Heat sink fan warning Keypad display: Heatsink fan |
Cause: Warning of the heatsink fan. Remedy: Response: Warning
|
| 17029 | 0x4285 Power section overtemperature warning Keypad display: Warn.PU Overtemp |
Cause: The heatsink temperature of the power unit (display in 0x2D84:001 (P117.01)) has exceeded the warning threshold set in 0x2D84:002.
Remedy: Response: Warning
|
| 17168 | 0x4310 Motor overtemperature error Keypad display: Overtemp. motor |
Cause: The motor temperature sensor connected to terminals X109/T1 and X109/T2 measures a too high motor temperature.
Remedy: Response: Fault (The error can only be reset after a blocking time of 5 s. The error type can be configured in 0x2D49:002 (P309.02).)
|
| 20754 | 0x5112 24 V supply critical Keypad display: 24V supply low |
Cause: 24V voltage failed or too low. Remedy: Response: Warning
|
| 20864 | 0x5180 24 V supply overload Keypad display: Overlaod 24V |
Cause: Output current at the 24V output or at the digital outputs too high. Remedy: Response: Warning
|
| 21376 | 0x5380 OEM hardware incompatible Keypad display: Incomp. OEM HW |
Cause: The control unit (OEM hardware) is not compatible with the power unit (OEM hardware). Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset by mains switching.)
|
| 24970 | 0x618A Internal fan warning Keypad display: Internal fan |
Cause: Warning of the internal fan. Remedy: Response: Warning
|
| 25216 | 0x6280 Trigger/functions connected incorrectly Keypad display: P400 config err |
Cause: The assignment directives have not been observed.
Remedy: Response: Trouble Check and correct the assignment of the triggers for the functions.
|
| 25217 | 0x6281 User-defined fault 1 Keypad display: User fault 1 |
Cause: Flexible I/O configuration: the "Activate fault 1" function was activated via the trigger selected in 0x2631:043 (P400.43). Remedy: Response: Fault
|
| 25218 | 0x6282 User-defined fault 2 Keypad display: User fault 2 |
Cause: Flexible I/O configuration: the "Activate fault 2" function was activated via the trigger selected in 0x2631:044 (P400.44). Remedy: Response: Fault
|
| 25232 | 0x6290 Reversal warning Keypad display: Invert rotation |
Cause:
Remedy: Response: Warning (The motor is brought to a standstill, since a reversal of the rotating direction is not permissible.)
|
| 25233 | 0x6291 Number of maximum permissible faults exceeded Keypad display: Trouble overflow |
Cause: The number of permitted restart attempts after a fault set in 0x2839:003 (P760.03) was exceeded. The fault occurred too frequently and could not be reset. Remedy: Response: Fault (The motor remains at a standstill, no automatic restart is executed.)
|
| 25248 | 0x62A0 AC Drive: user fault Keypad display: AC Dr. UserFault |
Cause: The "Activate fault" function was triggered via bit 10 of the LECOM control word 0x400B:002 (P592.02). Remedy: Response: Fault
|
| 25249 | 0x62A1 Network: user fault 1 Keypad display: Netw.UserFault 1 |
Cause: The "Activate fault 1" function was triggered via the NetWordIN1 data word 0x4008:001 (P590.01). Remedy: Response: Fault
|
| 25250 | 0x62A2 Network: user fault 2 Keypad display: Netw.UserFault 2 |
Cause: The "Activate fault 2" function was triggered via the NetWordIN1 data word 0x4008:001 (P590.01). Remedy: Response: Fault
|
| 25265 | 0x62B1 NetWordIN1 configuration incorrect Keypad display: NetWordIN1 error |
Cause: Two bits of the NetWordIN1 data word 0x4008:001 (P590.01) were assigned to the same function. Remedy: Response: Trouble Check and correct configuration of the NetWordIN1 data word.
|
| 25505 | 0x63A1 CU: load error ID tag Keypad display: CU ID tag error |
Cause: Calibration data of the control unit not compatible or faulty. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset by mains switching.)
|
| 25506 | 0x63A2 PU: load error ID tag Keypad display: PU ID tag error |
Cause: Calibration data of the power unit not compatible or faulty. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset by mains switching.)
|
| 25507 | 0x63A3 Power section unknown Keypad display: PU unknown |
Cause: The power unit installed is not supported by the software. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset by mains switching.)
|
| 28800 | 0x7080 Monitoring of connection level (Low/High) Keypad display: Assertionlevel |
Cause: The last setting of the connection level differs from the saved setting. Remedy: Response: Fault
|
| 28801 | 0x7081 Error of analog input 1 Keypad display: AI1 fault |
Cause: The monitoring function of the input signal configured for analog input 1 in 0x2636:008 (P430.08) and 0x2636:009 (P430.09) has been triggered. Remedy: Response: Fault (The error type can be configured in 0x2636:010 (P430.10).)
|
| 28802 | 0x7082 Analog input 2 fault Keypad display: AI2 fault |
Cause: The monitoring function of the input signal configured for analog input 2 in 0x2637:008 (P431.08) and 0x2637:009 (P431.09) has been triggered. Remedy: Response: Fault (The error type can be configured in 0x2637:010 (P431.10).)
|
| 28803 | 0x7083 HTL input fault Keypad display: HTL input fault |
Cause: The monitoring function of the input signal configured for the HTL input has been triggered. Remedy: Response: No response (The error type can be configured in 0x2641:006 (P416.06).)
|
| 28833 | 0x70A1 Analog output 1 fault Keypad display: AO1 fault |
Cause: Open circuit or short circuit at analog output 1. Remedy: Response: Warning
|
| 28834 | 0x70A2 Analog output 2 fault Keypad display: AO2 fault |
Cause: Open circuit or short circuit at analog output 2. Remedy: Response: Warning
|
| 28961 | 0x7121 Pole position identification fault Keypad display: Pole pos. error |
Cause:
Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error type can be configured in 0x2C60.)
|
| 29056 | 0x7180 Motor overcurrent Keypad display: Mot max current |
Cause: The motor current has exceeded the warning/error threshold for the motor current monitoring set in 0x2D46:001 (P353.01). Remedy: Response: Fault (The error can only be reset after a blocking time of 1 s. The error type can be configured in 0x2D46:002 (P353.02).)
|
| 29445 | 0x7305 Encoder open circuit Keypad display: Encoder error |
Cause: The encoder signal loss monitoring function has detected a failure of the encoder signal. Remedy: Response: Warning (The error type can be configured in 0x2C45 (P342.00).)
|
| 29573 | 0x7385 Feedback system: speed limitation Keypad display: F.fdb spd limit |
Cause: The feedback system exceeds the maximum permissible frequency range of the digital inputs. Remedy: Response: Warning
|
| 30336 | 0x7680 Memory module is full Keypad display: EPM full |
Cause: The memory module contains too many parameter settings. Remedy: Response: Warning (The parameter settings were not saved in the memory module.)
|
| 30337 | 0x7681 No memory module Keypad display: EPM not present |
Cause: The inverter memory module was removed. Remedy: Response: Fault (The default setting stored in the inverter firmware has been loaded. The error cannot be reset by the user.)
Note: The memory module cannot be replaced during ongoing operation! |
| 30338 | 0x7682 Memory module invalid user data Keypad display: EPM invalid data |
Cause: The user parameter settings in the memory module are invalid. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The user parameter settings are lost. The default settings were automatically loaded.)
|
| 30340 | 0x7684 Data not completely saved before switch-off Keypad display: Save incomplete |
Cause: Saving of the parameter settings was interrupted by an unexpected disconnection. Remedy: Response: Warning (The user parameter settings were not fully saved. At the next switch-on, the data stored are copied to the user memory.)
|
| 30342 | 0x7686 Internal communication error Keypad display: Int. Comm.Err. |
Cause: Communication between the power unit and the control unit is faulty. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts).)
|
| 30345 | 0x7689 Memory module: invalid OEM data Keypad display: OEM data invalid |
Cause: The OEM memory contains invalid parameter settings or is empty. Remedy: Response: Warning (The user parameter settings were automatically loaded.)
|
| 30346 | 0x768A Memory module: wrong type Keypad display: Wrong EPM |
Cause: The memory module connected is not supported by the inverter. Remedy: Response: Fault (The default setting stored in the inverter firmware has been loaded. The error cannot be reset by the user.)
|
| 30352 | 0x7690 EPM firmware version incompatible Keypad display: EPM-FW incomp. |
Cause: The parameter settings saved in the memory module are incompatible with the firmware version. Remedy: Response: Fault (The data have been loaded into the RAM memory, but they are incompatible.)
|
| 30353 | 0x7691 EPM data: firmware type incompatible Keypad display: EPM: FW incomp. |
Cause: The parameter settings saved in the memory module are incompatible with the firmware type. Example: Memory module of an inverter with an application IO is used in an inverter with a standard IO. Remedy: Response: Fault (The data have been loaded into the RAM memory, but they are incompatible.)
|
| 30354 | 0x7692 EPM data: new firmware type detected Keypad display: UserCU not match |
Cause: The parameter settings saved in the memory module do not match the inverter hardware. Remedy: Response: Fault (The data have been loaded into the RAM memory without being modified, and they are compatible. The settings loaded must be accepted by the user.)
|
| 30355 | 0x7693 EPM data: PU size incompatible Keypad display: EPM PU size inco |
Cause: The parameter settings saved in the memory module are incompatible with the inverter. Remedy: Response: Fault (The data have been loaded into the RAM memory, but they are incompatible.)
|
| 30356 | 0x7694 EPM data: new PU size detected Keypad display: EPM new PU size |
Cause: The parameter settings saved in the memory module comply with a different hardware. Example: Memory module of an inverter with a power of 3 kW is used in an inverter with a power of 18.5 kW. Remedy: Response: Fault (The data have been loaded into the RAM memory without being modified, and they are compatible. The settings loaded must be accepted by the user.)
|
| 30357 | 0x7695 Invalid configuration of parameter change-over Keypad display: InvalidChgovrCfg |
Cause: One or more parameters can no longer be used for the "Parameter change-over" function. Remedy: Response: Warning (The parameter change-over function is deactivated.)
|
| 30358 | 0x7696 EPM data: unknown parameter found Keypad display: Unkn. Par in EPM |
Cause: The memory module contains parameter settings for one or several parameters that are not known to the inverter. Remedy: Response: Info
|
| 30359 | 0x7697 Changed parameters lost Keypad display: Parameter loss |
Cause: A voltage failure has occurred and changed parameter settings that had not been saved yet were available. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The parameter settings changed have been lost.)
|
| 33042 | 0x8112 Network: timeout explicit message Keypad display: TO expl. msg |
Cause:
Remedy: Response: Warning (The error type can be configured in 0x2859:006 (P515.06).)
|
| 33044 | 0x8114 Network: overall communication timeout Keypad display: TO overall comm |
Cause:
Remedy: Response: Warning (The error type can be configured in 0x2859:007 (P515.07) (EtherNet/IP), 0x2859:007 (P515.07) (Modbus TCP).)
|
| 33045 | 0x8115 Time-out (PZÜ) Keypad display: Time-out (PAM) |
Cause: The parameter access monitoring (PAM) function has been activated. For a time longer than the time-out period set in 0x2552:003 (P595.03), no value was entered into the "Keep-alive-Register" 0x2552:002 (P595.02). Remedy: Response: No response (The error type can be configured in 0x2552:004 (P595.04).)
|
| 33046 | 0x8116 Modbus TCP master time-out Keypad display: MBTCP mast t-out |
Cause: No valid messages have been received by the Modbus master for a time longer than the time-out period set in 0x23B6:001 (P514.01). Remedy: Response: Fault (The error type can be configured in 0x2859:008 (P515.08).)
|
| 33047 | 0x8117 Modbus TCP Keep Alive time-out Keypad display: MB.Keep Alive TO |
Cause: For a time longer than the time-out period set in 0x23B6:002 (P514.02), no value was entered into the Keep alive register 0x23B6:005 (P514.05). Remedy: Response: Fault (The error type can be configured in 0x2859:009 (P515.09).)
|
| 33154 | 0x8182 CAN: bus off Keypad display: CAN bus off |
Cause: Too many faulty frames have been received.
Remedy: Response: Trouble (Change to the "Bus-Off" communication status. The error type can be configured in 0x2857:010.)
|
| 33155 | 0x8183 CAN: warning Keypad display: CAN bus warning |
Cause: Too many faulty frames have been received.
Remedy: Response: Warning (The error type can be configured in 0x2857:011.)
|
| 33156 | 0x8184 CAN: heartbeat time-out consumer 1 Keypad display: CAN heartb. C1 |
Cause: Within the heartbeat time 0x1016:001 (P520.01), no heartbeat telegram was received by node 1 to be monitored. Remedy: Response: Fault (The error type can be configured in 0x2857:005.)
|
| 33157 | 0x8185 CAN: heartbeat time-out consumer 2 Keypad display: CAN heartb. C2 |
Cause: Within the heartbeat time 0x1016:002 (P520.02), no heartbeat telegram was received by node 2 to be monitored. Remedy: Response: Fault (The error type can be configured in 0x2857:006.)
|
| 33158 | 0x8186 CAN: heartbeat time-out consumer 3 Keypad display: CAN heartb. C3 |
Cause: Within the heartbeat time 0x1016:003 (P520.03), no heartbeat telegram was received by node 3 to be monitored. Remedy: Response: Fault (The error type can be configured in 0x2857:007.)
|
| 33159 | 0x8187 CAN: heartbeat time-out consumer 4 Keypad display: CAN heartb. C4 |
Cause: Within the heartbeat time 0x1016:004 (P520.04), no heartbeat telegram was received by node 4 to be monitored. Remedy: Response: Fault (The error type can be configured in 0x2857:008.)
|
| 33168 | 0x8190 Network: watchdog timeout Keypad display: Watchdog timeout |
Cause: Time-out during cyclic data reception, e.g. due to an interrupted communication link to the master or missing cyclic data. Remedy: Response: Trouble (The error type can be configured in: 0x2859:001 (P515.01) (PROFIBUS), 0x2859:001 (P515.01) (EtherCAT), 0x2859:001 (P515.01) (EtherNet/IP), 0x2859:001 (P515.01) (PROFINET).)
|
| 33169 | 0x8191 Network: disruption of cyclic data exchange Keypad display: Cycl data error |
Cause: The communication partner has interrupted the cyclic data exchange. Remedy: Response: No response (The error type can be configured in 0x2859:002 (P515.02).)
|
| 33170 | 0x8192 Network: initialisation error Keypad display: Net. Init. error |
Cause: The initialisation of the communication stack has been interrupted due to an incorrect address setting or communication configuration. Remedy: Response: Trouble (The error type can be configured in: 0x2859:004 (P515.04) (PROFIBUS), 0x2859:004 (P515.04) (EtherCAT), 0x2859:004 (P515.04) (EtherNet/IP), 0x2859:004 (P515.04) (PROFINET), 0x2859:004 (P515.04) (Modbus TCP).)
|
| 33171 | 0x8193 Network: invalid cyclic process data Keypad display: Inv. cyclic data |
Cause: The cyclic process data received are invalid. Remedy: Response: Trouble (The error type can be configured in: 0x2859:005 (P515.05) (PROFIBUS), 0x2859:005 (P515.05) (EtherCAT), 0x2859:005 (P515.05) (EtherNet/IP), 0x2859:005 (P515.05) (PROFINET).)
|
| 33185 | 0x81A1 Modbus: network time-out Keypad display: Modbus time-out |
Cause: No valid messages have been received via the Modbus for a longer time than the time-out time set in 0x2858:002 (P515.02). Remedy: Response: Fault (The error type can be configured in 0x2858:001 (P515.01).)
|
| 33186 | 0x81A2 Modbus: incorrect request by master Keypad display: Modbus request |
Cause: The request by the master is invalid, e. g. invalid CRC checksum, non-supported function code, or impermissible data access. Remedy: Response: Warning (The inverter (slave) responds to the master with an error code: 0x01 = invalid function code, 0x02 = invalid data address, 0x03 = invalid data value, 0x04 = slave device failure) Check request by the master:
|
| 33200 | 0x81B0 iCIF connection lost Keypad display: iCIF disconnect. |
Cause: In case of the Ethernet communication interface, an internal software error has occurred. Remedy: Response: Fault
|
| 33414 | 0x8286 Network: PDO mapping error Keypad display: PDO map error |
Cause:
Remedy: Response: Trouble (The error type can be configured in: 0x2859:003 (P515.03) (PROFIBUS), 0x2859:003 (P515.03) (EtherCAT), 0x2859:003 (P515.03) (EtherNet/IP), 0x2859:003 (P515.03) (PROFINET), 0x2859:003 (P515.03) (Modbus TCP).)
|
| 33425 | 0x8291 CAN: RPDO1 time-out Keypad display: Timeout RPDO1 |
Cause: RPDO3 was not received within the time-out period set in 0x1402:005 (P542.05) or with the sync configured. Remedy: Response: Fault (The error type can be configured in 0x2857:001.)
|
| 33426 | 0x8292 CAN: RPDO2 time-out Keypad display: Timeout RPDO2 |
Cause: RPDO2 was not received within the time-out period set in 0x1401:005 (P541.05) or with the sync configured. Remedy: Response: Fault (The error type can be configured in 0x2857:002.)
|
| 33427 | 0x8293 CAN: RPDO3 time-out Keypad display: Timeout RPDO3 |
Cause: RPDO1 was not received within the time-out period set in 0x1400:005 (P540.05) or with the sync configured. Remedy: Response: Fault (The error type can be configured in 0x2857:003.)
|
| 33553 | 0x8311 Torque limit reached Keypad display: Torque limit |
Cause: Motor has reached the torque limit:
Remedy: Response: No response (The error type can be configured in 0x2D67:001 (P329.01).)
|
| 36992 | 0x9080 Keypad removed Keypad display: Keypad removed |
Cause: The keypad was removed while the keypad control was activated. Remedy: Response: Fault
|
| 65282 | 0xFF02 Brake resistor: overload warning Keypad display: BrkResistor OL.F |
Cause: The calculated thermal load of the brake resistor has reached the error threshold set in 0x2550:009 (P707.09). The regenerative energy is too high. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset after a blocking time of 5 s. The error type can be configured in 0x2550:011 (P707.11).)
Note: The error status will be reset if the thermal load falls below the error threshold - 20 %. |
| 65285 | 0xFF05 Safe Torque Off error Keypad display: STO error |
Cause: The safety module or safety circuit of the device was detected as being defective. Remedy: Response: Fault (The inverter is inhibited immediately. The motor becomes torqueless (coasts). The error can only be reset by mains switching.)
|
| 65286 | 0xFF06 Motor overspeed Keypad display: Motor overspeed |
Cause: The motor speed has reached the error threshold for overspeed set in 0x2D44:001 (P350.01). Remedy: Response: Fault (The error can only be reset after a blocking time of 1 s. The error type can be configured in 0x2D44:002 (P350.02).)
|
| 65289 | 0xFF09 Motor phase missing Keypad display: Mot.Phase miss. |
Cause: A failure of several motor phases has been detected. Remedy: Response: No response (The error can only be reset after a blocking time of 2 s. The error type can be configured in 0x2D45:001 (P310.01).)
|
| 65290 | 0xFF0A Phase U motor phase failure Keypad display: Phase U failure |
Cause: A failure of the motor phase U has been detected. Remedy: Response: No response (The error can only be reset after a blocking time of 2 s. The error type can be configured in 0x2D45:001 (P310.01).)
|
| 65291 | 0xFF0B Motor phase failure phase V Keypad display: Phase V failure |
Cause: A failure of the motor phase V has been detected. Remedy: Response: No response (The error can only be reset after a blocking time of 2 s. The error type can be configured in 0x2D45:001 (P310.01).)
|
| 65292 | 0xFF0C Motor phase failure phase W Keypad display: Phase W failure |
Cause: A failure of the motor phase W has been detected. Remedy: Response: No response (The error can only be reset after a blocking time of 2 s. The error type can be configured in 0x2D45:001 (P310.01).)
|
| 65305 | 0xFF19 Motor parameter identification fault Keypad display: Motor ID fault |
Cause: During the automatic identification of the motor, an error has occurred. Remedy: Response: Fault
|
| 65334 | 0xFF36 Brake resistor: overload warning Keypad display: BrkResistor OL.W |
Cause: The calculated thermal load of the brake resistor has reached the warning threshold set in 0x2550:008 (P707.08). The regenerative energy is too high. Remedy: Response: Warning (The error type can be configured in 0x2550:010 (P707.10).)
Note: The warning status is reset if the thermal load falls below the warning threshold of 20 %. |
| 65335 | 0xFF37 Automatic start disabled Keypad display: Auto start disab |
Cause: At mains connection, a start command was already available and the automatic start at power-up is set in 0x2838:002 (P203.02) to "Off [0]". Remedy: Response: Fault
|
| 65366 | 0xFF56 Maximum motor frequency reached Keypad display: Max. motor freq. |
Cause:
Remedy: Response: Warning
|
| 65413 | 0xFF85 Keypad full control active Keypad display: Keypad full ctrl |
Cause: If the "Keypad Full Control" control mode is active. Remedy: Response: Warning (Both the activity of controlling and the setpoint selection are carried out via the keypad.)
|
How to Safely Reset an Emotron DSV Fault
Always investigate and resolve the electrical or mechanical issue before resetting the drive . The DSV can be reset using one of four standard methods:
- Keypad Reset: Press the red stop/reset key on the diagnostic or control panel . Note that after a critical fault, the drive has a built-in safety blocking time of 5 seconds before a reset can be accepted .
- Digital Input Reset: Trigger a transition pulse on a digital terminal mapped to the "Fault Reset" function .
- Power Cycle (Power-On Reset): Disconnect the main AC power lines . Safety Requirement: Due to residual energy stored in the capacitors, you must wait at least 3 minutes after switching off the mains voltage before touching terminal connections or opening covers .
- Network Reset: Send a reset bit command over your network module (CANopen, Modbus, or PROFIBUS) .
Common DSV-Specific Faults and Troubleshooting
While the diagnostic system covers many parameters, a few common codes represent the majority of typical service calls:
1. Short Circuit / Earth Fault
This code triggers when the drive detects a sudden current surge to earth or across the output phases .
- Diagnostic: Check the output cables and the motor windings for insulation degradation . If the fault occurs on long cable runs, it may be triggered by high capacitive charging currents; consider installing an output reactor if cable lengths exceed manufacturer limits .
2. AI1 Fault (0x7081 / 28801)
This triggers when the analog input signal falls outside the expected range defined in your protection configurations .
- Diagnostic: Keypad display shows
AI1 fault. Check the physical 4-20mA or 0-10V signal connection running to Analog Input 1 . Ensure that the wire is not broken and that the sensor or potentiometer is powered correctly.
3. UserCU not match (0x7692 / 30354)
This code occurs when the parameter settings saved in the pluggable memory module do not match the physical control unit or power unit hardware .
- Diagnostic: The parameter data is loaded into the drive's RAM but remains blocked . Execute the device command "Load default settings" and re-verify your user parameter configurations .
4. EPM PU Size (0x7694 / 30356)
The drive triggers this error when the pluggable memory module (EPM) is moved from a drive of one power rating (e.g., 4 kW) to a drive of a different power rating (e.g., 7.5 kW) .
- Diagnostic: Keypad display shows
EPM: new PU size. The data is loaded into RAM but requires confirmation . Review your parameters to make sure they match the new physical power stage, and perform a reset .
Best Practices for Maintaining the DSV Drive
Proactive care of your Emotron DSV drive prevents unexpected downtime and extends hardware life:
- Secure Control Modules: The DSV uses a modular power unit and control unit assembly . Ensure the control modules and option slot cards are fully seated and screwed down securely to prevent intermittent connection alarms .
- Backup to the Memory Module: The DSV has an exchangeable memory module (X20 interface) . Always backup your verified parameter settings to the module . This allows for plug-and-play parameter transfer if a drive needs to be replaced .
- Monitor Heatsink Fan Ventilation: Keep the vents clean. Dust buildup in the heat sink fins can trap heat, triggering thermal overtemperature protection.
By monitoring the P155.00 error history buffer and resolving warning codes early, you can optimize the reliability of your Emotron DSV AC drive .
Comments
Post a Comment