Causes and remedies
|
Cause
|
Remedy
|
Severity/response
|
|
–
Continuous overcurrent on the inverter/motor side.
–
Overcurrent at the brake chopper (brake transistor).
–
DC bus relay has not been closed due to a malfunction.
|
–
Check motor and wiring for short circuits.
–
Check brake resistor and wiring.
–
Check motor switching.
–
Check settings of the motor data.
|
Fault
–
The inverter is disabled immediately. The motor has no torque (is coasting).
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
–
Short circuit/earth fault of motor cable
–
Capacitive charging current of the motor cable
too high.
|
–
Check motor cable.
–
Check length of the motor cable.
–
Use shorter or lower-capacitance motor cable.
|
Fault
–
The inverter is disabled immediately. The motor has no torque (is coasting).
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Short circuit of motor cable
|
Check motor cable for short circuit.
|
Fault
–
The inverter is disabled immediately. The motor has no torque (is coasting).
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Motor thermally overloaded, e. g.
by an impermissible continuous current or by frequent or too long acceleration processes.
|
–
Check drive sizing.
–
Check machine/driven mechanics for excessive load.
–
Check settings of the motor data.
–
Reduce values for slip compensation 0x2B09:001 (P315.01), 0x2B09:002 (P315.02) and oscillation damping 0x2B0A:001 (P318.01), 0x2B0A:002 (P318.02).
|
Fault (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
||
|
Setting parameters: 0x2D4B:003 (P308.03)
|
|
Related topics
|
Motor overload monitoring (i²xt)|
Cause
|
Remedy
|
Severity/response
|
|
Device utilisation (ixt) too high by frequent and too long acceleration processes.
|
Check drive sizing.
–
Reduce the maximum current of the inverter 0x6073 (P324.00).
–
In case of high mass inertias, reduce maximum current of the inverter 0x6073 (P324.00) to 150 %.
|
Fault (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
||
|
Setting parameters: 0x2D40:005 (P135.05)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Device utilisation (ixt) too high by frequent and too long acceleration processes.
|
Check drive dimensioning.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Maximum current of the axis (display in
0x2DDF:002) has been reached
too often in succession.
|
–
Select a flatter speed ramp.
–
Reduce the load.
–
Set Imax controller more dynamically.
|
Fault
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Overload of the motor with sensorless control for synchronous motors (SL-PSM).
|
–
Reduce load at the axis.
–
Check settings of the SL-PSM parameters.
|
Trouble
–
The inverter is disabled immediately. The motor has no torque (is coasting).
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The actual current0x6078 (P103.00) is equal to or higher than the max. current 0x6073 (P324.00).
|
Information
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Mains phase failure
|
–
Check wiring of the mains connection.
–
Check fuses.
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Operation on uninterrupted 1x230V current supply (UPS) has been activated: Only a reduced output current is provided.
|
Switch back to operation with regular mains voltage.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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).
|
–
Reduce dynamic performance of the load profile.
–
Check mains voltage.
–
Check settings for brake energy management.
–
0x2541:001 (P706.01) = [0]: Connect brake resistor to the power unit and activate the integrated brake chopper.
|
Fault
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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.
|
–
Reduce dynamic performance of the load profile.
–
Check mains voltage.
–
Check settings for brake energy management.
–
0x2541:001 (P706.01) = [0]: Connect brake resistor to the power unit and activate the integrated brake chopper.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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).
|
–
Check mains voltage.
–
0x2D87 (P105.00)Check DC-bus voltage.
–
Check mains settings.
–
Check fuses.
|
Trouble
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
DC-bus voltage
has fallen below the warning threshold for undervoltage set in 0x2540:002 (P208.02).
|
–
Check mains voltage.
–
0x2D87 (P105.00) Check DC-bus voltage.
–
Check mains settings.
–
Check fuses.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The input voltage is too low to switch on the inverter.
|
–
Check mains voltage.
–
Check mains settings.
–
Check fuses.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The heatsink temperature of the power unit (display in 0x2D84:001 (P117.01)) has exceeded the
fixed error threshold (100 °C).
–
Ambient temperature too high.
–
Fan or ventilation slots are polluted.
–
Fan is defective.
|
–
Check mains voltage.
–
Provide for a sufficient cooling of the device. In case of a 100 % load, 60 C to +70°C are normal. Display of the heatsink temperature in 0x2D84:001 (P117.01).
–
Clean fan and ventilation slots. If required, replace fan.
–
Reduce switching frequency 0x2939 (P305.00)
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Sensor for the temperature monitoring of the power unit is defective. The failure of the temperature monitoring function poses the risk of overheating!
|
Hardware error: it is necessary to contact the manufacturer, since
the device must be replaced.
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Warning of the heatsink fan.
|
Clean fan and ventilation slots. If required, replace fan. The fans can be unlocked via locking hooks and can then be removed.
|
Warning
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The heatsink temperature of the power unit (display in 0x2D84:001 (P117.01)) has exceeded the warning threshold set in 0x2D84:002.
–
Ambient temperature too high.
–
Fan or ventilation slots are polluted.
–
Fan is defective.
|
–
Provide for a sufficient cooling of the device.
–
Clean fan and ventilation slots.
–
If required, replace fan.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The motor temperature sensor connected to terminals X109/T1 and X109/T2 measures a too high motor temperature.
–
Motor too hot by impermissibly
high currents.
–
Motor too hot by frequent and too
long acceleration processes.
|
–
Check drive dimensioning.
–
Check motor temperature sensor and wiring.
|
Fault (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
||
|
Setting parameters: 0x2D49:002 (P309.02)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
External supply voltage failed or too low.
|
–
Check optional external 24V voltage supply (terminal X3/24E), if connected.
–
Check mains voltage.
|
Warning
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Output current at the 24V output or at the digital outputs too high.
|
Check 24V output and digital outputs for earth fault or overload.
|
Warning
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The control unit (OEM hardware) is not compatible with the power unit (OEM hardware).
|
–
Use compatible hardware.
–
Contact the OEM.
|
Fault
–
The inverter is disabled immediately. The motor has no torque (is coasting).
–
The event can only be reset by mains switching.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Warning of the internal fan.
|
Check/replace internal fan.
|
Warning
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The assignment directives have not been observed.
–
If the "flexible I/O configuration" is active as control source, the "Enable inverter" or "Run" function must be connected to a digital input in order that the motor can be stopped again any time!
–
The use of the "Start forward (CW)" and "Start reverse (CCW)" functions excludes the use of the "Run forward (CW)" and "Run reverse (CCW)" functions, and vice versa.
|
Check and correct the assignment of the triggers to the functions.
–
With keypad or network control, the two "Enable inverter 0x2631:001 (P400.01)" and "Run 0x2631:002 (P400.02)" functions can also be set to "Constant TRUE [1]" to start the motor.
|
Trouble
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Flexible I/O configuration: the "Activate fault 1" function was activated via the trigger selected in 0x2631:043 (P400.43).
|
Eliminate error cause and then reset error.
|
Fault
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Flexible I/O configuration: the "Activate fault 2" function was activated via the trigger selected in 0x2631:044 (P400.44).
|
Eliminate error cause and then reset error.
|
Fault
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
–
Negative setpoint selection with an active limitation of rotation 0x283A (P304.00).
–
The "Reverse rotational direction" 0x2631:013 (P400.13) function was requested with an active limitation of rotation 0x283A (P304.00).
|
Warning
–
The motor is brought to a standstill, since a reversal of the rotating direction is not permissible.
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The number of permitted restart attempts after a fault set in 0x2839:003 (P760.03) was exceeded. The fault occurred to frequently and could not be reset.
|
Check and the eliminate the fault.
|
Fault
–
The motor remains at a standstill, no automatic restart is executed.
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The "Activate fault" function was triggered via bit 10 of the LECOM control word 0x400B:002 (P592.02).
|
Eliminate error cause and then reset error.
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The "Activate fault 1" function was triggered via the NetWordIN1 data word 0x4008:001 (P590.01).
|
Eliminate error cause and then reset error.
|
Fault
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The "Activate fault 2" function was triggered via the NetWordIN1 data word 0x4008:001 (P590.01).
|
Eliminate error cause and then reset error.
|
Fault
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Two bits of the NetWordIN1 data word 0x4008:001 (P590.01) were assigned to the same function.
|
Check and correct configuration of the NetWordIN1 data word.
–
The functions that are to be triggered via bits 0 ... 15 of the NetWordIN1 data word are defined in 0x400E:001 (P505.01) ... 0x400E:016 (P505.16).
|
Trouble
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The device ID of the device was changed manually.
|
1.
Execute device command "Save user data" 0x2022:003 (P700.03).
2.
Switch inverter off and on again.
|
Fault
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The “Back-to-Box” system command has been executed. The standard parameter set has been written and saved. Communication is deactivated and the device is in stop status.
|
Switch inverter off and on again.
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Calibration data of the control unit not compatible or faulty.
|
–
Update firmware of the inverter to the most recent version.
–
If the error persists, the control unit or the device has to be replaced. In this case, please contact the manufacturer.
|
Fault
–
The inverter is disabled immediately. The motor has no torque (is coasting).
–
The event can only be reset by mains switching.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Calibration data of the power unit not compatible or faulty.
|
–
Update firmware of the inverter to the most recent version.
–
If the error persists, the power unit or the device has to be replaced. In this case, please contact the manufacturer.
|
Fault
–
The inverter is disabled immediately. The motor has no torque (is coasting).
–
The event can only be reset by mains switching.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The power unit installed is not supported by the software.
|
Update firmware of the inverter to the most recent version.
|
Fault
–
The inverter is disabled immediately. The motor has no torque (is coasting).
–
The event can only be reset by mains switching.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The last setting of the connection level differs from the saved setting.
|
1.
Execute device command "Save user data" 0x2022:003 (P700.03).
2.
Switch inverter off and on again.
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
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.
|
–
Check input signal at analog input 1.
–
Check configuration of the monitoring function.
|
Fault (configurable)
|
|
Setting parameters: 0x2636:010 (P430.10)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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.
|
–
Check input signal at analog input 2.
–
Check configuration of the monitoring function.
|
Fault (configurable)
|
|
Setting parameters: 0x2637:010 (P431.10)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
No response (configurable)
|
||
|
Setting parameters: 0x2641:006 (P416.06)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Open circuit
or short circuit at analog output 1.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Open circuit
or short circuit at analog output 2.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
–
Too many deviations during the pole position identification.
–
Compared to the inverter, the rated motor current is too high or too low.
|
–
Check setting of the motor data.
–
Ensure that the motor is at a standstill during the pole position identification process.
–
Ensure that the motor and inverter match each other in terms of power.
|
Fault (configurable)
|
|
Setting parameters: 0x2C60
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The motor current has exceeded the warning/error threshold for the motor current monitoring set in 0x2D46:001 (P353.01).
|
–
Check motor load.
–
Check drive dimensioning.
–
Check warning threshold or error threshold set in 0x2D46:001 (P353.01).
|
Fault (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 1 s
|
||
|
Setting parameters: 0x2D46:002 (P353.02)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The encoder signal loss monitoring function has detected a failure of the encoder signal.
|
–
Check the encoder connection.
–
Check encoder cable for wire breakage.
–
Check encoder current supply.
|
Warning (configurable)
|
|
Setting parameters: 0x2C45 (P342.00)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The feedback system exceeds the maximum permissible frequency range of the digital inputs.
|
Check feedback system.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The memory module contains too many parameter settings.
|
Execute "Save user data" 0x2022:003 (P700.03) device command again. This reinitialises the user memory with the current parameter settings. In this way, parameter settings that are no longer required are automatically deleted.
|
Warning
–
The parameter settings were not saved in the memory module.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The inverter memory module was removed.
|
1.
Switch off inverter.
2.
Plug the memory module into the inverter.
3.
Switch the inverter on again.
Note: The memory module cannot be replaced during ongoing operation!
|
Fault
–
The default setting stored in the inverter firmware has been loaded.
–
The error cannot be reset by the user.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The user parameter settings in the memory module are invalid.
|
1.
Execute user parameter settings again.
2.
Execute device command "Save user data" 0x2022:003 (P700.03).
|
Fault
–
The user parameter settings are lost.
–
The default settings were automatically loaded.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Saving of the parameter settings was interrupted by an unexpected disconnection.
|
1.
Check user parameter settings. (The loaded backup is an older version.)
2.
If required, repeat the changes made last.
3.
Execute device command "Save user data" 0x2022:003 (P700.03).
|
Warning
–
The user parameter settings were not fully saved.
–
At the next switch-on, the data stored are copied to the user memory.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The OEM memory contains invalid parameter settings or is empty.
|
–
Execute device command "Save OEM data" 0x2022:006 (P700.06).
–
Thus, the user parameter settings get lost!
|
Warning
–
The user parameter settings were automatically loaded.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The memory module connected is not supported by the inverter.
|
1.
Switch off inverter.
2.
Replace plugged-in memory module by a memory module that matches the inverter.
3.
Switch the inverter on again.
|
Fault
–
The default setting stored in the inverter firmware has been loaded.
–
The error cannot be reset by the user.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The parameter settings saved in the memory module
are incompatible with the firmware version.
|
1.
Execute device command "Load default settings" 0x2022:001 (P700.01).
2.
Execute "Save user data" 0x2022:003 (P700.03) or "Save OEM data" 0x2022:006 (P700.06) device command.
|
Fault
–
The data have been loaded into the RAM memory, but they are incompatible.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The parameter settings saved in the memory module are incompatible with the firmware type.
Example: Memory module of an inverter with an application I/O is used in an inverter with a standard I/O.
|
1.
Execute device command "Load default settings" 0x2022:001 (P700.01).
2.
Execute "Save user data" 0x2022:003 (P700.03) or "Save OEM data" 0x2022:006 (P700.06) device command.
|
Fault
–
The data have been loaded into the RAM memory, but they are incompatible.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The parameter settings saved in the memory module
do not match the inverter hardware.
|
1.
Check parameter settings.
2.
Reset error.
3.
Execute "Save user data" 0x2022:003 (P700.03) or "Save OEM data" 0x2022:006 (P700.06) device command.
|
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 (see remedy).
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The parameter settings saved in the memory module
are incompatible with the inverter.
|
1.
Execute device command "Load default settings" 0x2022:001 (P700.01).
2.
Execute "Save user data" 0x2022:003 (P700.03) or "Save OEM data" 0x2022:006 (P700.06) device command.
|
Fault
–
The data have been loaded into the RAM memory, but they are incompatible.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
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.
|
1.
Check parameter settings.
2.
Reset error.
3.
Execute "Save user data" 0x2022:003 (P700.03) or "Save OEM data" 0x2022:006 (P700.06) device command.
|
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 (see remedy).
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
One or more parameters can no longer be used for the "Parameter change-over" function.
|
1.
Check error message for parameter change-over in 0x4047:001 (P756.01).
2.
Correct the list entry shown in 0x4047:002 (P756.02).
|
Warning
–
The parameter change-over function is deactivated.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The memory module contains parameter settings for one or several parameters that are not known to the inverter.
|
Execute the "Save user data" 0x2022:003 (P700.03) device command. This reinitialises the user memory with the current parameter settings. In this way, parameter settings that are no longer required are automatically deleted.
|
Information
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
A voltage failure has occurred and changed parameter settings that had not been saved yet were available.
|
1.
Execute parameter settings again.
2.
Execute device command "Save user data" 0x2022:003 (P700.03).
|
Fault
–
The parameter settings changed
have been lost.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
–
Within the time-out period for explicit messages, which has been parameterised by the scanner, no "explicit message" was received.
–
The connection to the scanner has been interrupted.
–
Failure of an explicit connection.
|
–
Check cables and terminals.
–
Plug network cables into the Ethernet port.
–
Check the requested package interval (RPI) of the explicit connection.
–
Increase time limit for explicit messages in the scanner.
|
Warning (configurable)
|
|
Setting parameters: 0x2859:006 (P515.06)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
–
EtherNet/IP: the maximum permissible time-out period for the CIP communication set in 0x23A1:010 (P510.10) has been exceeded.
–
Modbus TCP/IP: the maximum permissible time-out period for the TCP communication set in 0x23B1:010 (P510.10) has been exceeded.
|
–
Check cables and terminals.
–
Connect network cable.
|
Warning (configurable)
|
|
Setting parameters:
0x2859:007 (P515.07) (EtherNet/IP)
0x2859:007 (P515.07) (Modbus TCP)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
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).
|
–
Check
communication.
–
Check settings of the parameter access monitoring (PAM) function.
|
No response (configurable)
|
|
Setting parameters: 0x2552:004 (P595.04)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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).
|
Check communication with the master.
|
Fault (configurable)
|
|
Setting parameters: 0x2859:008 (P515.08)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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).
|
Check communication with the master.
|
Fault (configurable)
|
|
Setting parameters: 0x2859:009 (P515.09)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Too many faulty frames have been received.
–
Defective cable (e. g. loose contact).
–
Two nodes with the same node address.
|
–
Check wiring of the network.
–
Check bus terminating resistor.
–
Set the identical baud rate for each node of the network.
–
Assign a unique node address to each node of the network.
–
Eliminate EMC interferences.
|
Trouble (configurable)
–
Change to the "Bus-Off" communication status.
|
|
Setting parameters: 0x2857:010
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Too many faulty frames have been received.
–
Defective cable (e. g. loose contact).
–
Two nodes with the same node address.
|
–
Check wiring of the network.
–
Check bus terminating resistor.
–
Set the identical baud rate for each node of the network.
–
Assign a unique node address to each node of the network.
–
Eliminate EMC interferences.
|
Warning (configurable)
|
|
Setting parameters: 0x2857:011
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Within the heartbeat time 0x1016:001 (P520.01), no heartbeat telegram was received by node 1 to be monitored.
|
–
Check communication with the heartbeat producer.
–
Reactivate heartbeat producer.
|
Fault (configurable)
|
|
Setting parameters: 0x2857:005
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Within the heartbeat time 0x1016:002 (P520.02), no heartbeat telegram was received by node 2 to be monitored.
|
–
Check communication with the heartbeat producer.
–
Reactivate heartbeat producer.
|
Fault (configurable)
|
|
Setting parameters: 0x2857:006
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Within the heartbeat time 0x1016:003 (P520.03), no heartbeat telegram was received by node 3 to be monitored.
|
–
Check communication with the heartbeat producer.
–
Reactivate heartbeat producer.
|
Fault (configurable)
|
|
Setting parameters: 0x2857:007
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Within the heartbeat time 0x1016:004 (P520.04), no heartbeat telegram was received by node 4 to be monitored.
|
–
Check communication with the heartbeat producer.
–
Reactivate heartbeat producer.
|
Fault (configurable)
|
|
Setting parameters: 0x2857:008
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Time-out during cyclic data reception, e.g. due to an interrupted communication link to the master or missing cyclic data.
|
–
Check wiring of the network.
–
Eliminate EMC interferences.
|
Trouble (configurable)
|
|
Setting parameters:
0x2859:001 (P515.01) (PROFIBUS)
0x2859:001 (P515.01) (EtherCAT)
0x2859:001 (P515.01) (EtherNet/IP)
0x2859:001 (P515.01) (PROFINET)
0x2859:001 (POWERLINK)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The communication partner has interrupted the cyclic data exchange.
|
–
Check wiring of the network.
–
The slave must receive new parameterisation and configuration files by the master, in order to be able to exchange data again.
|
No response (configurable)
|
|
Setting parameters: 0x2859:002 (P515.02)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The initialisation of the communication stack has been interrupted due to an incorrect address setting or communication configuration.
|
Check master/slave configuration and restart the devices.
|
Trouble (configurable)
|
|
Setting parameters:
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)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The cyclic process data received are invalid.
|
Check cyclic process data sent by the master.
|
Trouble (configurable)
|
|
Setting parameters:
0x2859:005 (P515.05) (PROFIBUS)
0x2859:005 (P515.05) (EtherCAT)
0x2859:005 (P515.05) (EtherNet/IP)
0x2859:005 (P515.05) (PROFINET)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
No valid messages have been received via the Modbus for a longer time than the time-out time set in 0x2858:002 (P515.02).
|
–
Check communication with the master.
–
Check wiring.
–
Check bus termination.
|
Fault (configurable)
|
|
Setting parameters: 0x2858:001 (P515.01)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The request by the master is invalid, e. g. invalid CRC checksum, non-supported function code, or impermissible data access.
|
Check request by the master:
–
Value in the valid range?
–
Function code valid?
–
No impermissible write access? (e. g. with regard to read-only parameters)
|
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
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
In case of the Ethernet communication interface, an internal software error has occurred.
|
–
Switch inverter off and on again.
–
In the event of a power failure during a firmware download, it is required to reload the firmware via the USB module and then restart the inverter.
|
Trouble
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
SoC of master was not received.
|
Check configuration and system setup.
|
Trouble (configurable)
|
|
Setting parameters: 0x2859:011
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
CRC frame defective.
|
Check system setup.
|
Trouble (configurable)
|
|
Setting parameters: 0x2859:010
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
–
Invalid PDO assignment by the master.
–
Internal PDO assignment was changed and does not comply with the configuration available in the master.
|
Check data mapping in the master and slave.
|
Trouble (configurable)
|
|
Setting parameters:
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)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
RPDO1 was not received within the time-out period set in 0x1400:005 (P540.05) or with the sync configured.
|
Fault (configurable)
|
|
|
Setting parameters: 0x2857:001
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
RPDO2 was not received within the time-out period set in 0x1401:005 (P541.05) or with the sync configured.
|
Fault (configurable)
|
|
|
Setting parameters: 0x2857:002
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
RPDO3 was not received within the time-out period set in 0x1402:005 (P542.05) or with the sync configured.
|
Fault (configurable)
|
|
|
Setting parameters: 0x2857:003
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Motor has reached the torque limit:
–
0x2949:003 (P337.03): Actual positive torque limit
–
0x2949:004 (P337.04): Actual negative torque limit
|
–
Observe load requirements.
–
Reduce motor load.
–
Check set torque limits and sources for the torque limits.
|
No response (configurable)
|
|
Setting parameters: 0x2D67:001 (P329.01)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The selected function is not permissible in the chosen operating mode.
–
Selection of torque mode [-1] in 0x6060 (P301.00) with incompatible motor control in 0x2C00 (P300.00).
|
–
Note: selection of torque mode [-1] in 0x6060 (P301.00) with incompatible motor control in 0x2C00 (P300.00).
–
Check settings of operation modes.
|
Warning
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The keypad was removed while the keypad control was activated.
|
–
Plug keypad back in or activate another control source.
|
Fault
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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.
|
–
Check drive dimensioning.
–
Check settings for the brake energy management.
Note: The error status will be reset if the thermal load
falls below the error threshold - 20 %.
|
Fault (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
||
|
Setting parameters: 0x2550:011 (P707.11)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
The safety module or safety circuit of the device was detected as being defective.
The integrated safety technology is defective.
|
Hardware error: it is necessary to contact the manufacturer since the device must be replaced.
The inverter must be replaced.
Note!
The user is not allowed to change inverters that come with integrated safety technology.
–
The safety module must not be removed.
–
The user must not carry out any repairs on the safety module.
–
The safety module is not a spare part.
|
Fault
–
The inverter is disabled immediately. The motor has no torque (is coasting).
–
The event can only be reset by mains switching.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
The motor speed has reached the error threshold for overspeed set in 0x2D44:001 (P350.01).
|
Adapt the maximum motor speed 0x6080 (P322.00) and the warning threshold or error threshold 0x2D44:001 (P350.01).
|
Fault (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 1 s
|
||
|
Setting parameters: 0x2D44:002 (P350.02)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
A failure of several motor phases has been detected.
|
–
Check wiring between inverter and motor.
–
In case of a false tripping, adapt the settings for the motor phase failure detection.
|
No response (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
||
|
Setting parameters: 0x2D45:001 (P310.01)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
A failure of the motor phase U has been detected.
|
–
Check wiring between inverter and motor.
–
In case of a false tripping, adapt the settings for the motor phase failure detection.
|
No response (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
||
|
Setting parameters: 0x2D45:001 (P310.01)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
A failure of the motor phase V has been detected.
|
–
Check wiring between inverter and motor.
–
In case of a false tripping, adapt the settings for the motor phase failure detection.
|
No response (configurable)
–
The event can only be reset after a blocking time.
|
|
Blocking time: 2 s
|
||
|
Setting parameters: 0x2D45:001 (P310.01)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
No response (configurable)
–
The event can only be reset after a blocking time.
|
||
|
Blocking time: 2 s
|
||
|
Setting parameters: 0x2D45:001 (P310.01)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
During the automatic identification of the motor, an error has occurred.
|
–
Set motor data so that they comply
with the data on the motor nameplate.
–
Check wiring of the motor.
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Configuration or runtime error
|
–
Check configuration
–
Check FMF error code 0x4050:002 to determine the error cause.
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Cascade function for pumps and fans The maximum frequency in 0x2916 (P211.00) has been reached and no free additional pump is available.
|
–
Check configuration of the cascade function.
–
Check drive sizing.
|
Warning
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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.
|
–
Check drive dimensioning.
–
Check settings for the brake energy management.
Note: The warning status is reset if the thermal load
falls below the warning threshold of - 20 %.
|
Warning (configurable)
|
|
Setting parameters: 0x2550:010 (P707.10)
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
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]".
|
Deactivate starting command and reset error.
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
In a running motor, the motor load (current) is monitored. When the motor load falls below the threshold value specified in Load loss detection: threshold (0x4006:001 (P710.01)) for the period of time specified in Load loss detection: delay time (0x4006:002 (P710.02)), load loss protection is triggered.
|
Check utilisation
|
No response (configurable)
|
|
Setting parameters: 0x4006:003 (P710.03)
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
If the apparent motor current exceeds a defined threshold value 0x4007:002 for a certain amount of time 0x4007:001, heavy duty monitoring is triggered.
|
Check the motor load.
|
No response (configurable)
|
|
Setting parameters: 0x4007:003
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
–
The limitation of the maximum motor speed set in 0x6080 (P322.00) is active.
–
The maximum output frequency of the inverter has been reached.
–
Depending on the parameter setting of 0x2D44:001 (P350.01) (Overspeed monitoring: threshold), the speed limitation (0x6080 / Max. motor speed) may become active before speed monitoring.
|
Check application.
|
Warning
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Indicates the deactivation of the manual speed control.
|
Warning
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Indicates the activation of the manual speed control.
|
Warning
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
If "manual operation" is active, an error is generated in case the communication links get lost.
|
The error can be only be reset if the connection is restored or the control mode is changed to a different value than "manual operation".
|
Fault
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
A wrong password has been entered several times.
|
Wait until the blocking time has elapsed and then enter the correct password.
|
Warning
–
The blocking time for entering a password is more than 10 seconds. (The blocking time is doubled every time an incorrect password is entered.)
–
No password can be entered as long as the blocking time is active.
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Inverter is not compatible with the Controller/PLC (brand protection).
–
The Controller has not written a deactivation password in the parameter yet.
–
The deactivation password written by the Controller is incorrect.
|
Use corresponding (compatible) OEM components.
|
Warning
–
No response from the inverter.
–
The decision on whether the machine will be commissioned or
not is made by the Controller.
|
|
Related topics
|
|
Cause
|
Remedy
|
Severity/response
|
|
Error when reading the data from the control unit.
|
–
Switch inverter off and on again.
–
If the error occurs again, the manufacturer must be contacted, since the control unit or the device has to be replaced.
|
Fault
–
Operation of the inverter is not possible.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
Error when reading the data from the power unit.
|
–
Switch inverter off and on again.
–
If the error occurs again, the manufacturer must be contacted, since the power unit or the device has to be replaced.
|
Fault
–
Operation of the inverter is not possible.
|
|
|
|
Cause
|
Remedy
|
Severity/response
|
|
If the "Keypad Full Control" control mode is active.
|
To exit the control mode, press the keypad key CTRL.
|
Warning
–
Both the activity of controlling and the setpoint selection are carried out via the keypad.
|
|
Related topics
|