4 Faults and alarms
4.2 List of faults and alarms
SINAMICS G120 Control Units CU240B-2/CU240E-2
830 List Manual (LH11), 01/2016, A5E33839529
F07405 (N, A) Drive: Kinetic buffering minimum speed fallen below
Message class: Application/technological function faulted (17)
Reaction: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Acknowledge: IMMEDIATELY
Cause: During kinetic buffering the speed fell below minimum speed (p1257 or p1297 for vector drives with U/f control) and
the line supply did not return.
Remedy: Check the speed threshold for the Vdc_min controller (kinetic buffering) (p1257, p1297).
See also: p1257 (Vdc_min controller speed threshold), p1297 (Vdc_min controller speed threshold (U/f))
F07406 (N, A) Drive: Kinetic buffering maximum time exceeded
Message class: Application/technological function faulted (17)
Reaction: OFF3 (IASC/DCBRK, NONE, OFF1, OFF2, STOP2)
Acknowledge: IMMEDIATELY
Cause: The maximum buffer time (p1255 and p1295 for vector drives with U/f control) has been exceeded without the line
supply having returned.
Remedy: Check the time threshold for Vdc-min controller (kinetic buffering) (p1255, p1295).
See also: p1255 (Vdc_min controller time threshold), p1295 (Vdc_min controller time threshold (U/f))
A07409 (N) Drive: U/f control, current limiting controller active
Message class: Application/technological function faulted (17)
Reaction: NONE
Acknowledge: NONE
Cause: The current limiting controller of the U/f control was activated because the current limit was exceeded.
Remedy: The alarm is automatically withdrawn after one of the following measures:
- increase current limit (p0640).
- reduce the load.
- slow down the ramp up to the setpoint speed.
F07410 Drive: Current controller output limited
Message class: Application/technological function faulted (17)
Reaction: OFF2 (NONE, OFF1)
Acknowledge: IMMEDIATELY
Cause: The condition "I_act = 0 and Uq_set_1 longer than 16 ms at its limit" is present and can be caused by the following:
- motor not connected or motor contactor open.
- motor data and motor configuration (star-delta) do not match.
- no DC link voltage present.
- power unit defective.
- the "flying restart" function is not activated.
Remedy: - connect the motor or check the motor contactor.
- check the motor parameterization and the connection type (star-delta).
- check the DC link voltage (r0070).
- check the power unit.
- activate the "flying restart" function (p1200).
F07411 Drive: Flux setpoint not reached when building up excitation
Message class: Application/technological function faulted (17)
Reaction: OFF2
Acknowledge: IMMEDIATELY
Cause: When quick magnetizing is configured (p1401.6 = 1) the specified flux setpoint is not reached although 90% of the
maximum current is specified.
- incorrect motor data.
- motor data and motor configuration (star-delta) do not match.
- the current limit has been set too low for the motor.
- induction motor (encoderless, open-loop controlled) in I2t limiting.
- power unit is too small.
- the magnetizing time is too short.
To Next Page
Loading...
