|
|
SINAMICS alarms
Remedy:
- check the parameterized line frequency and if required change (p0211).
- check the alarm threshold (p0285).
- check the line supply.
- check the line supply quality.
See also: p0211, p0285
206400
<location>Infeed: Line supply data identification selected/active
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The line supply data identification is selected and active.
The line inductance and the DC link capacitance are measured at the next pulse enable.
See also: p3410 (Infeed identification method)
Remedy:
Not necessary.
This alarm is automatically withdrawn after the measurement has been completed.
206401
<location>Infeed: Transformer data identification/test mode selected/active
Drive object:
A_INF, A_INF_840, R_INF
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A transformer data identification type or a transformer test operation has been selected or is active.
Alarm value (r2124, interpret decimal):
11: Identification type 1 selected for transformer data (automatic determination of the magnetizing inductance).
12: Identification type 2 selected for transformer data (automatic determination of transformer phase shift and gain
correction).
13: Identification type 3 selected for transformer data (determination of total leakage inductance of transformer during line
data identification).
101: Test mode 1 selected.
102: Test mode 2 selected.
See also: p5480 (Transformer magnetization mode)
Remedy:
Not necessary.
This alarm is automatically withdrawn after the identification has expired.
206500
<location>Infeed: Line synchronization not possible
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The line synchronization is not possible within the monitoring time.
The infeed was re-synchronized to the line supply because it was interrupted due to an incorrect line frequency or due to
excessively high line voltage distortion.
After 20 attempts, synchronization - and therefore also the switching-on operation - were interrupted.
Especially for ALM chassis units, one possible cause is that the bypass contactor or circuit breaker does not close.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
975
SINAMICS alarms
Remedy:
- check the parameterized line frequency and if required change (p0211).
- check the setting of the threshold values (p0284, p0285).
- check the line supply.
- check the connecting terminals
- check the bypass contactor (if one is being used) and its associated control.
- check the state of the circuit breaker and its associated control.
- for significant line voltage distortion, after assessment by experts, the tolerance threshold p3457[2] can be adapted.
When using a Voltage Sensing Module (VSM):
- check the line supply connection at the terminals (X521, X522).
- check VSM activation (p0145, p3400).
- check the line supply quality.
Note:
In the case of chassis power units, the availability of correct VSM voltage measured values is imperative for line
synchronization.
See also: p0211, p0284, p0285, p3457
206502
<location>Infeed: Unable to achieve line synchronization in transformer magnetization
Drive object:
A_INF, A_INF_840, R_INF
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
Line synchronization is not possible within the monitoring time (p5481[2]).
Remedy:
- check the setting of the threshold value (p5485).
- check the setting of the maximum time (p5481[2])
- check the line supply quality.
See also: p5481 (Transformer magnetization times), p5485 (Transformer magnetization voltage thresholds)
206503
<location>Infeed: Line black start unsuccessful
Drive object:
A_INF, A_INF_840, R_INF, S_INF
Message value:
%1
Reaction:
OFF1 (NONE, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The line black start was unsuccessful.
Fault value (r0949, interpret decimal):
State of the black start (corresponds to r5482).
The following applies for fault value r0949 = 109:
At the start of a black start (p5581 = 1), a line supply was identified (frequency and voltage within the specified limits p0281
to p0285).
The following applies to all other fault values:
The maximum time for a black start (p5581[2]) was exceeded.
Remedy:
- check the conditions of a line black start.
- check the parameterization of the line black start.
See also: p5581 (Island grid times)
206504
<location>Infeed: Island line supply synchronization unsuccessful
Drive object:
A_INF, A_INF_840, R_INF, S_INF
Message value:
%1
Reaction:
NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
976
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The island line supply synchronization was unsuccessful.
Alarm value (r2124, interpret decimal):
State, in which the island line supply synchronization has remained (corresponds to r5482).
See also: r5482 (Line synchronization status)
Remedy:
- check the conditions for the island line supply synchronization.
- check the parameterization of the island line supply synchronization.
See also: p5581 (Island grid times)
206505
<location>Infeed: For transformer magnetization current limit exceeded
Drive object:
A_INF, A_INF_840, R_INF, S_INF
Message value:
%1
Reaction:
OFF1 (OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The current limit was exceeded when magnetizing the transformer (r0068 > p5494[1] * r0207).
Remedy:
- check the setting of the current limit (p5494[1])
- check the primary side of the transformer for a short-circuit.
- check the control and feedback signal of the circuit breaker.
See also: p5494 (Transformer magnetization scaling values)
206601
<location>Infeed: Current offset measurement interrupted
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Defective current measurement or a DC current is present during the offset measurement.
Alarm value (r2124, interpret decimal):
1: Excessively high phase current has occurred during the current offset calibration.
2: The measured current offset is greater than the 3% of the maximum permissible converter current (e.g. due to a ground
fault in the DC link).
Remedy:
For alarm value = 1:
- possible counter-measure if there is no line contactor: Power up an adequately long time before OFF1 = 1.
For alarm value = 2:
- defective current measurement or a DC current is present during the offset measurement.
- check the DC link for a ground fault.
206602
<location>Infeed: Current offset measurement not possible
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
After an OFF1 = 1 no valid current offset measurement was able to be made within the monitoring time (p3491) before
closing the line contactor. The current offset is set to 0.
See also: p3491 (Infeed I-offset measurement monitoring time)
Remedy:
- check the DC link for a ground fault. A ground fault can destroy parts and components!
- check the monitoring time setting and if required increase (p3491). At least 100 ms is required for a valid measurement
(p3491 > 100 ms).
Notice:
If there is no valid measurement, then under certain circumstances the quality of the DC link control will be reduced.
See also: p3491 (Infeed I-offset measurement monitoring time)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
977
SINAMICS alarms
206700
<location>Infeed: Switch line contactor for load condition
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
NONE (OFF2)
Acknowledge:
IMMEDIATELY
Cause:
For an ON command, the infeed line contactor should be switched under load.
Remedy:
- do not load the DC link if the infeed has not issued an operating signal (r0863.0 = 1).
- after the infeed has been switched off, all power units connected to the DC link should be switched off. To realize this, the
operating signal of the infeed (r0863.0) must be suitably interconnected.
206800
<location>Infeed: Maximum steady-state DC link voltage reached
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The DC link voltage setpoint has reached the maximum steady-state voltage parameterized in p0280.
The DC link voltage is increased by the modulation depth reserve controller for the following reasons:
- modulation depth reserve is too low (p3480).
- line supply voltage is too high.
- supply voltage (p0210) parameterized to be too low.
- excessively high setpoint for the reactive line current.
Remedy:
- check the line supply voltage setting (p0210).
- check the line supply for an overvoltage condition.
- reduce the modulation depth reserve (p3480).
- reduce the reactive current setpoint.
See also: p0210, p0280, p3480
206810
<location>Infeed: DC link voltage alarm threshold fallen below
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
In operation, the DC link voltage has dropped to below the alarm threshold. The alarm threshold is obtained from the sum
of p0279 and r0296.
Note:
When the alarm threshold is fallen below, this is also indicated using status bit r3405.7.
Possible causes:
- line supply voltage dip or another line supply fault.
- overload of the infeed.
- for Active Line Module: Controller incorrectly parameterized.
See also: p0279, r0296, r3405
Remedy:
- check the line voltage and line supply quality.
- reduce the power drawn, avoid step-like load changes
- for Active Line Module: Adapt the controller parameterization (e.g. automatic line supply identification (p3410 = 4, 5)).
206849
<location>Infeed: Short-circuit operation active
Drive object:
A_INF, A_INF_840, R_INF
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Alarms
978
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The current hysteresis controller sequence control has detected a short circuit (r5452, r5522). The absolute line supply
voltage (r5444[0], r5512[0]) is below the short-circuit voltage limit (p5459[2], p5529[2]), and the current limitation is
active (r5402.3 = 1, r5502.3 = 1).
Note:
The effective current limit is obtained from the parameterized overcurrent (p5453) and the hysteresis width (p5454).
Remedy:
- check the parameterization of the current hysteresis controller (p5453).
- check the line supply cables for a short-circuit.
See also: r5452 (Current hysteresis controller sequence control status word), p5453 (Current hysteresis controller
overcurrent limit)
206850
<location>Infeed: Short-circuit prevailing for too long
Drive object:
A_INF, A_INF_840, R_INF
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The maximum permissible duration (p5458[1], p5528[1]) for the short-circuit has been exceeded. The short-circuit could
not be cleared within this time.
See also: p5509 (Dynamic grid support scaling values)
Remedy:
- check the minimum time parameter setting (p5458[1], p5528[1]).
- check the line supply and fuses.
See also: p5458 (Current hysteresis controller minimum time operating state), p5528 (Dynamic grid control operating state
times)
206851
<location>Infeed: Distributed infeed line monitoring tripped
Drive object:
A_INF, A_INF_840, R_INF
Message value:
%1
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The line monitoring of the distributed line infeed has tripped.
Alarm value (r2124, interpret hexadecimal):
Corresponds to status word (r5542).
Remedy:
- check the line supply.
- check the parameterization of the line monitoring (p5540 ... p5559).
See also: p5540 (Line monitoring configuration), r5542 (Line monitoring status word)
206855
<location>Infeed: Line filter monitor responded
Drive object:
A_INF, A_INF_840, R_INF
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
A threshold value parameterized in p3678 has been exceeded or undershot in the line filter.
Fault value (r0949, interpret decimal):
0: Voltage threshold, alpha/beta voltage monitoring fallen below (p3678[0]).
2: Voltage threshold value of the phase voltage monitoring fallen below (p3678[0]).
x1:
Current threshold value exceeded (p3678[1]).
The 10th position codes the power unit number of the Active Interface Module involved.
Example:
01: overcurrent in line filter 1.
11: Overcurrent in line filter 2.
See also: p3678 (Filter monitoring threshold values), p3679 (Transformer filter monitoring times)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
979
SINAMICS alarms
Remedy:
- check the parameterization of the threshold values for filter monitoring (p3678]).
- check filter.
For fault value = 0:
- check the parameterization of the voltage monitoring smoothing time (p3679[0]).
For fault value = 1:
- check the parameterization of the current monitoring minimum time (p3679[1]).
206860
<location>Infeed: Function module activation not possible
Drive object:
A_INF, A_INF_840, R_INF
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
Function module activation is not possible.
The power unit used has at least one of the following features:
- gating unit with current limiting control (r0192.19).
- gating unit with all-phase current limiting (r0192.30).
The affected function module is identified in fault value r0949 (the value of r0949 corresponds to the bit of parameter
p0108).
r0949 = 7 "Dynamic grid support" function module
r0949 = 12: "Line droop control" function module
See also: r0192, p5401
Remedy:
- check whether the power unit used has the "gating unit with current limiting control" feature (r0192.19) or "gating unit
with all-phase current limiting" feature (r0192.30).
- if necessary, use a power unit that has at least one of these features.
206900
<location>Braking Module: Fault (1 -> 0)
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The Braking Module signals a fault (1 -> 0) via X21.4 ("booksize" format) or X21.5 ("chassis" format).
This signal is wired to a system digital input and correspondingly interconnected using binector input p3866[0...7].
Possible causes:
- wiring of the signal or BICO interconnection of the signal source incorrect.
- overtemperature
- electronics power supply missing.
- ground fault/short-circuit.
- internal component fault.
See also: p3866 (Braking Module fault)
Remedy:
- check binector input p3866[0...7] and the wiring from terminal X21.4 ("booksize" format) or X21.5 ("chassis" format).
- reduce the number of braking operations.
- check the 24 V power supply of the component.
- check for a ground fault or short circuit.
- replace the component if necessary.
206901
<location>Braking Module: Pre-alarm I2t shutdown
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Alarms
980
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The Braking Module "Booksize" format signals "Pre-alarm I2t shutdown" via terminal X21.3.
This signal is wired to a system digital input and correspondingly interconnected using binector input p3865[0...7].
Note:
This function is not supported for the "chassis" format.
Remedy:
- reduce the number of braking operations.
- check binector input p3865[0...7] and the wiring from terminal X21.3 of the particular Braking Module.
206904
<location>Braking Module internal is inhibited
Drive object:
B_INF, B_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The internal Braking Module was inhibited via binector input p3680 = 1 signal.
In the inhibited state, energy cannot be dissipated using the braking resistor.
See also: p3680 (Braking Module internal inhibit)
Remedy:
Release the internal Braking Module (BI: p3680 = 0 signal).
206905
<location>Braking Module internal I2t shutdown alarm
Drive object:
B_INF, B_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The internal Braking Module outputs an alarm due to the high I2t value.
80% of the maximum switch-on duration of the braking resistor has been reached.
Note:
This message is also displayed via BO: p3685.
See also: r3685 (Digital Braking Module: Pre-alarm I2t shutdown)
Remedy:
Reduce the number of braking operations.
206906
<location>Braking Module internal fault
Drive object:
B_INF, B_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The internal Braking Module outputs a fault due to overcurrent or an excessively high I2t value and is therefore inhibited.
Note:
This message is also displayed via BO: p3686.
Fault value (r0949, interpret bitwise binary):
Bit 0 = 1: I2t exceeded
Bit 1 = 1: overcurrent
See also: r3686 (Digital Braking Module fault)
Remedy:
Reduce the number of braking operations.
206907
<location>Braking Module internal overtemperature
Drive object:
B_INF, B_INF_840
Message value:
-
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
981
SINAMICS alarms
Cause:
The temperature sensor connected to the braking resistor signals an overtemperature.
The Braking Module is still active. If the overtemperature persists for more than 60 s, fault F06908 is output, and the braking
module is switched off.
See also: r3687 (Digital Braking Module pre-alarm overtemperature)
Remedy:
- reduce the temperature at the sensor.
- check the temperature sensor connection.
206908
<location>Braking Module internal overtemperature shutdown
Drive object:
B_INF, B_INF_840
Message value:
-
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY
Cause:
Braking module shut down due to overtemperature at the temperature sensor of the braking resistor.
The overtemperature is detected by the sensor for longer than 60 s.
See also: r3688 (Braking Module internal overtemperature shutdown)
Remedy:
- reduce the temperature at the sensor.
- check the temperature sensor connection.
206909
<location>Braking Module internal Vce fault
Drive object:
B_INF, B_INF_840
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
In the power unit, the monitoring of the collector-emitter voltage (U_ce) of the power semiconductor to control the braking
resistor has responded.
Possible causes:
- short circuit at the braking resistor terminals.
- defective power semiconductor in the braking resistor control.
Note:
Under certain circumstances, this fault is also output if a braking resistor is not connected, and the energy is fed back into
the Braking Module.
See also: r3689 (Digital Braking Module Uce fault)
Remedy:
- connect a braking resistor.
- check the braking resistor connection.
- check the braking resistor.
- carry out a POWER ON (switch-off/switch-on).
- replace the unit.
206921
<location>Braking resistor phase asymmetry
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
- the three resistors of the braking chopper are not symmetrical.
- DC link voltage oscillations caused by fluctuating loads of the connected drives.
Remedy:
- check the feeder cables to the braking resistors.
- if required, increase the value for detecting asymmetry (p1364).
See also: p1360 (Braking chopper braking resistor cold), p1362 (Braking chopper activation threshold), r1363 (Braking
chopper output voltage), p1364 (Braking chopper resistor asymmetry)
Alarms
982
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
206922
<location>Braking resistor phase failure
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
A phase failure for the brake resistor was detected.
Fault value (r0949, interpret decimal):
11: Phase U
12: Phase V
13: Phase W
See also: p3235 (Phase failure signal motor monitoring time)
Remedy:
Check the feeder cables to the braking resistors.
See also: p1360 (Braking chopper braking resistor cold), p1362 (Braking chopper activation threshold), r1363 (Braking
chopper output voltage), p1364 (Braking chopper resistor asymmetry)
207011
<location>Drive: Motor overtemperature
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
KTY84/PT1000:
The motor temperature has exceeded the fault threshold (p0605) or the timer (p0606) after the alarm threshold was
exceeded (p0604) has expired.
PTC, bimetallic NC contact:
The response threshold of 1650 Ohm was exceeded (for SME p4600 ... p4603 or for TM120 p4610 ... p4613 = 10, 30), or
the timer (p0606) has expired after 1650 Ohm has been exceeded (for SME p4600 ... p4603 or for TM120 p4610 ... p4613
= 12, 32).
Motor temperature model:
The calculated motor temperature is too high.
Possible causes:
- motor overloaded.
- motor ambient temperature too high.
- PTC / bimetallic NC contact: Wire breakage or sensor not connected.
- motor temperature model incorrectly parameterized.
Hysteresis:2K
Fault value (r0949, interpret decimal):
1, 2, 3, 4:
Number of the temperature channel leading to the message (for SME/TM120 (p0601 = 10, 11)).
200:
Motor temperature model 1 (I2t): temperature too high.
300:
Motor temperature model 3: after the monitoring time has expired, the temperature is still higher than the alarm threshold.
301:
Motor temperature model 3: temperature is too high, or the model has not been parameterized.
302:
Motor temperature model 3: Encoder temperature is not within the valid range.
See also: p0351, p0604, p0605, p0606, p0612, p0613, p0617, p0618, p0619, p0625, p0626, p0627, p0628
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
983
SINAMICS alarms
Remedy:
- reduce the motor load.
- check the ambient temperature and the motor ventilation.
- check the wiring and temperature sensor connection.
- check monitoring limits.
- check the encoder type (p0404).
- check the motor type (p0300, p0301).
- check activation of the motor temperature model (p0612).
- check the motor temperature model parameters.
- check the encoder (p0404).
See also: p0351, p0604, p0605, p0606, p0612, p0617, p0618, p0619, p0625, p0626, p0627, p0628, r5397
207011
<location>Drive: Motor overtemperature
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
KTY84/PT1000 or no sensor:
The measured motor temperature or model temperature has exceeded the fault threshold (p0605) or the timer (p0606) has
elapsed following the alarm threshold (p0604) being exceeded.
The response parameterized in p0610 becomes active.
PTC or bimetallic NC contact:
The response threshold of 1650 Ohm was exceeded or the NC contact opened and the timer (p0606) has expired. The
response parameterized in p0610 becomes active.
Possible causes:
- motor is overloaded.
- the motor ambient temperature is too high.
- PTC / bimetallic NC contact: Wire breakage or sensor not connected.
Fault value (r0949, interpret decimal):
200:
Motor temperature model 1 (I2t): temperature too high.
Number of the temperature channel leading to the message (for SME/TM120 (p0601 = 10, 11)).
See also: p0351, p0604, p0605, p0606, p0612, p0613, p0617, p0618, p0619, p0625, p0626, p0627, p0628
Remedy:
- reduce the motor load.
- check the ambient temperature and the motor ventilation.
- check the wiring and the connection of the PTC or bimetallic NC contact.
See also: p0351, p0604, p0605, p0606, p0612, p0617, p0618, p0619, p0625, p0626, p0627, p0628
207012
<location>Drive: Motor temperature model 1/3 overtemperature
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The motor temperature model 1/3 identified that the alarm threshold was exceeded.
Hysteresis:2K
Alarm value (r2124, interpret decimal):
200:
Motor temperature model 1 (I2t): temperature too high.
300:
Motor temperature model 3: temperature too high.
See also: r0034, p0351, p0605, p0611, p0612, p0613
Alarms
984
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- check the motor load and if required, reduce.
- check the motor ambient temperature.
- check activation of the motor temperature model (p0612).
Motor temperature model 1 (I2t):
- check the thermal time constant (p0611).
- check alarm threshold.
Motor temperature model 3:
- check the motor type.
- check alarm threshold.
- check the model parameters.
See also: r0034, p0351, p0605, p0611, p0612, r5397
207013
<location>Drive: Motor temperature model configuration fault
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
A fault has occurred in the configuration of the motor temperature model.
Fault value (r0949, interpret decimal):
300:
Motor temperature model 3: The sensor does not supply the necessary sensor temperature for the thermal model.
301:
Motor temperature model 3: The sensor type is unknown.
302:
Motor temperature model 3: At least one other temperature model was simultaneously activated.
303:
Motor temperature model unknown in the actual firmware version.
See also: p0300, p0301, p0404, p0612
Remedy:
- check the encoder type.
- check the motor type.
- check activation of the motor temperature model (p0612).
- check the parameters of the motor temperature model (p5350 and following).
See also: p0300, p0301, p0404, p0612
207014
<location>Drive: Motor temperature model configuration alarm
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A fault has occurred in the configuration of the motor temperature model.
Alarm value (r2124, interpret decimal):
1:
All motor temperature models: It is not possible to save the model temperature
300:
Motor temperature model 3: Threshold value for alarm (r5398) is higher than the threshold value for fault (r5399).
See also: p0610 (Motor overtemperature response), p5390 (Mot_temp_mod 1/3 alarm threshold), p5391 (Mot_temp_mod
1/3 fault threshold)
Remedy:
- set the response for motor overtemperature to "Alarm and fault, no reduction of I_max" (p0610 = 2).
- check and correct the threshold values (r5398, r5399).
See also: p0610 (Motor overtemperature response), p5390 (Mot_temp_mod 1/3 alarm threshold), p5391 (Mot_temp_mod
1/3 fault threshold)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
985
SINAMICS alarms
207014
<location>Drive: Motor temperature model configuration alarm
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A fault has occurred in the configuration of the motor temperature model.
Alarm value (r2124, interpret decimal):
1:
All motor temperature models: It is not possible to save the model temperature
See also: p0610 (Motor overtemperature response)
Remedy:
- set the response for motor overtemperature to "Alarm and fault, no reduction of I_max" (p0610 = 2).
See also: p0610 (Motor overtemperature response)
207015
<location>Drive: Motor temperature sensor alarm
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
An error was detected when evaluating the temperature sensor set in p0600 and p0601.
With the fault, the time in p0607 is started. If the fault is still present after this time has expired, then fault F07016 is output;
however, at the earliest, 50 ms after alarm A07015.
Possible causes:
- wire breakage or sensor not connected (KTY: R > 1630 Ohm, PT1000: R > 1720 Ohm).
- measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT1000: R < 603 Ohm).
Alarm value (r2124, interpret decimal):
- if SME/TM120 is selected (p0601 = 10, 11),
this is the number of the temperature channel leading to the message.
Remedy:
- make sure that the sensor is connected correctly.
- check the parameterization (p0600, p0601).
- check the setting of the lower threshold (p4622).
See also: r0035, p0600, p0601, p0607, p4622
207016
<location>Drive: Motor temperature sensor fault
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
An error was detected when evaluating the temperature sensor set in p0600 and p0601.
Possible causes:
- wire breakage or sensor not connected (KTY: R > 1630 Ohm, PT1000: R > 1720 Ohm).
- measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT1000: R < 603 Ohm).
Note:
If alarm A07015 is present, the time in p0607 is started. If the fault is still present after this time has expired, then fault
F07016 is output; however, at the earliest, 50 ms after alarm A07015.
Fault value (r0949, interpret decimal):
- if SME/TM120 is selected (p0601 = 10, 11),
this is the number of the temperature channel leading to the message.
See also: p0607 (Temperature sensor fault timer)
Alarms
986
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- make sure that the sensor is connected correctly.
- check the parameterization (p0600, p0601).
- induction motors: Deactivate temperature sensor fault (p0607 = 0).
- When TM120 and SMC/SME (p0601 = 10, 11) are being used, set the same sensor type on the drive (p4610 ... p4613) as
for TM120.
- check the setting of the lower threshold (p4622).
See also: r0035, p0600, p0601, p0607, p4622
207017
<location>Additional temperature alarm threshold exceeded
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The additional temperature has exceeded the alarm threshold in p4102[0]
The time in p4103 is also started with this alarm. Fault F07018 is output if the alarm is still active after this time has expired.
- overtemperature (r4105 > p4102[0]).
See also: p4100, p4102, p4103, r4105
Remedy:
- make sure that the sensor is connected correctly.
- check parameterization (p4100).
207018
<location>Additional temperature fault threshold exceeded
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF1 (ENCODER, NONE, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
The additional temperature has exceeded the fault threshold in p4102[1]
Fault value (r0949, interpret decimal):
0:
Overtemperature (r4105 > p4102[1] or r4105 > p4102[0] for longer than the time in p4103).
1:
Wire breakage or sensor not connected (KTY: R > 1630 Ohm, PT1000: R > 1720 Ohm).
Measured resistance too low (KTY: R < 50 Ohm, PT1000: R < 603 Ohm).
See also: p4100, p4102, p4103, r4105
Remedy:
- make sure that the sensor is connected correctly.
- check parameterization (p4100).
207048
<location>Drive: Incorrect characteristic measurement
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY
Cause:
A fault has occurred during the characteristic measurement.
Fault value (r0949, interpret decimal):
1: Speed threshold for DQ saturation not reached.
Remedy:
For fault value = 1:
- check the closed-loop load machine control.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
987
SINAMICS alarms
207080
<location>Drive: Incorrect control parameter
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, ENC, ENC_840, HLA, HLA_840, HUB, R_INF, S_INF, S_INF_840, SERVO,
SERVO_840, SERVO_AC, TB30, TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, TM54F_MA, TM54F_SL, VECTOR,
VECTOR_AC
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0).
Fault value (r0949, interpret decimal):
The fault value includes the parameter number involved.
See also: p0310, p0311, p0341, p0344, p0350, p0354, p0356, p0357, p0358, p0360, p0400, p0404, p0408, p0640,
p1082, p1300
Remedy:
Modify the parameter indicated in the fault value (r0949) (e.g. p0640 = current limit > 0).
See also: p0311, p0341, p0344, p0350, p0354, p0356, p0358, p0360, p0400, p0404, p0408, p0640, p1082
207082
<location>Macro: Execution not possible
Drive object:
All objects
Message value:
Fault cause: %1, supplementary information: %2, preliminary parameter number: %3
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The macro cannot be executed.
Fault value (r0949, interpret hexadecimal):
ccccbbaa hex:
cccc = preliminary parameter number, bb = supplementary information, aa = fault cause
Fault causes for the trigger parameter itself:
19: Called file is not valid for the trigger parameter.
20: Called file is not valid for parameter 15.
21: Called file is not valid for parameter 700.
22: Called file is not valid for parameter 1000.
23: Called file is not valid for parameter 1500.
24: Data type of a TAG is incorrect (e.g. Index, number or bit is not U16).
Fault causes for the parameters to be set:
25: Error level has an undefined value.
26: Mode has an undefined value.
27: A value was entered as string in the tag value that is not "DEFAULT".
31: Entered drive object type unknown.
32: A device was not able to be found for the determined drive object number.
34: A trigger parameter was recursively called.
35: It is not permissible to write to the parameter via macro.
36: Check, writing to a parameter unsuccessful, parameter can only be read, not available, incorrect data type, value range
or assignment incorrect.
37: Source parameter for a BICO interconnection was not able to be determined.
38: An index was set for a non-indexed (or CDS-dependent) parameter.
39: No index was set for an indexed parameter.
41: A bit operation is only permissible for parameters with the parameter format DISPLAY_BIN.
42: A value not equal to 0 or 1 was set for a BitOperation.
43: Reading the parameter to be changed by the BitOperation was unsuccessful.
51: Factory setting for DEVICE may only be executed on the DEVICE.
61: The setting of a value was unsuccessful.
Remedy:
- check the parameter involved.
- check the macro file and BICO interconnection.
See also: p0015, p0700, p1000, p1500
Alarms
988
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
207083
<location>Macro: ACX file not found
Drive object:
All objects
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The ACX file (macro) to be executed was not able to be found in the appropriate directory.
Fault value (r0949, interpret decimal):
Parameter number with which the execution was started.
See also: p0015, p0700, p1000, p1500
Remedy:
- check whether the file is saved in the appropriate directory on the memory card.
Example:
If p0015 is set to 1501, then the selected ACX file must be located in the following directory:
... /PMACROS/DEVICE/P15/PM001501.ACX
207084
<location>Macro: Condition for WaitUntil not fulfilled
Drive object:
All objects
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The WaitUntil condition set in the macro was not fulfilled in a certain number of attempts.
Fault value (r0949, interpret decimal):
Parameter number for which the condition was set.
Remedy:
Check and correct the conditions for the WaitUntil loop.
207085
<location>Drive: Open-loop/closed-loop control parameters changed
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, VECTOR,
VECTOR_AC
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
Open-loop/closed-loop control parameters have had to be changed.
Possible causes:
1. As a result of other parameters, they have exceeded the dynamic limits.
2. They cannot be used due to the fact that the hardware detected not having certain features.
3. The value is estimated as the thermal time constant is missing.
4. Motor temperature model 1 is activated as thermal motor protection is missing.
Fault value (r0949, interpret decimal):
Changed parameter number.
340:
The motor and control parameters were automatically calculated (p0340 = 1), because the vector control was subsequently
activated as configuration (r0108.2).
611:
The time constant for thermal motor model 1 was estimated.
612:
Thermal motor model 1 was activated (p0612.0 = 1).
1800:
A more favorable pulse frequency was preassigned.
See also: p0640, p1082, p1300, p1800
Remedy:
Not necessary.
It is not necessary to change the parameters as they have already been correctly limited.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
989
SINAMICS alarms
207086
<location>Units changeover: Parameter limit violation due to reference value change
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
A reference parameter was changed in the system. This resulted in the fact that for the parameters involved, the selected
value was not able to be written in the per unit notation.
The values of the parameters were set to the corresponding violated minimum limit/maximum limit or to the factory setting.
Possible causes:
- the steady-state minimum limit/maximum limit or that defined in the application was violated.
Fault value (r0949, parameter):
Diagnostics parameter to display the parameters that were not able to be re-calculated.
See also: p0304, p0305, p0310, p0596, p2000, p2001, p2002, p2003, r2004
Remedy:
Check the adapted parameter value and if required correct.
See also: r9450 (Reference value change parameter with unsuccessful calculation)
207087
<location>Drive: Encoderless operation not possible for the selected pulse frequency
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
Encoderless operation is not possible for the selected pulse frequency (p1800).
Encoderless operation is activated under the following conditions:
- the changeover speed for encoderless operation (p1404) is less than the maximum speed (p0322).
- a control type with encoderless operation has been selected (p1300).
- encoder faults of the motor encoder result in a fault response with encoderless operation (p0491).
See also: p0491, p1300, p1404, p1800
Remedy:
Increase the pulse frequency (p1800).
Note:
In encoderless operation, the pulse frequency must be at least as high as one quarter of the current controller clock cycle
frequency (1/p0115[0]).
207088
<location>Units changeover: Parameter limit violation due to units changeover
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
A changeover of units was initiated. This resulted in a violation of a parameter limit
Possible causes for the violation of a parameter limit:
- When rounding off a parameter corresponding to its decimal places, the steady-state minimum limit or maximum limit was
violated.
- inaccuracies for the data type "FloatingPoint".
In these cases, when the minimum limit is violated then the parameter value is rounded up and when the maximum limited
is violated the parameter value is rounded down.
Fault value (r0949, interpret decimal):
Diagnostics parameter r9451 to display all parameters whose value had to be adapted.
See also: p0100, p0349, p0505, p0595
Remedy:
Check the adapted parameter values and if required correct.
See also: r9451 (Units changeover adapted parameters)
Alarms
990
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
207089
<location>Changing over units: Function module activation is blocked because the units
have been changed over
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
An attempt was made to activate a function module. This is not permissible if the units have already been changed over.
See also: p0100, p0349, p0505
Remedy:
Restore units that have been changed over to the factory setting.
207090
<location>Drive: Upper torque limit less than the lower torque limit
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The upper torque limit is lower than the lower torque limit.
Remedy:
P1 must be >= P2 if parameter P1 is connected to p1522 and parameter P2 to p1523.
207091
<location>Drive: determined current controller dynamic response invalid
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
When one button tuning is activated (p5300 = 1), the current controller is measured after the pulses have been enabled.
Evaluation has indicated that the current control loop was not appropriately set.
Possible causes:
- incorrectly set current controller.
- PRBS amplitude set too high (p5296).
Alarm value (r2124, interpret hexadecimal):
1: Dynamic response too low.
2: Current controller unstable.
Note:
PRBS: Pseudo Random Binary Signal (binary noise)
Remedy:
- the measurement can be repeated with a smaller excitation amplitude (p5296).
- if required, adapt the current controller proportional gain (p1715).
207092
<location>Drive: moment of inertia estimator still not ready
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The moment of inertia estimator has still not determined any valid values.
The acceleration cannot be calculated.
The moment of inertia estimator has stabilized, if the frictional values (p1563, p1564) as well as the moment of inertia value
(p1493) have been determined and the appropriate status signal is set (r1407.26 = 1).
The following parameters influence the response of the moment of the inertia estimator:
p1560, p1561, p1562
Remedy:
Traverse the axis until the moment of inertia estimator has stabilized.
This alarm is automatically withdrawn after the moment of inertia estimator has stabilized.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
991
SINAMICS alarms
207093
<location>Drive: Test signal error
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF3 (NONE, OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
An error was identified when executing the "Test signal" function (p5307.1 = 1).
The function was not executed or was canceled.
Fault value (r0949, interpret decimal):
1: No distance limit has been defined (p5308 = 0).
2: The moment of inertia estimator has not stabilized in the parameterized time (p5309) (r1407.26).
3: The parameterized distance (p5308) was exceeded.
4: no motor encoder parameterized (closed-loop speed control without encoder).
5: Offset (p5297) is too high for the parameterized distance (p5308).
6: Pulse enable was withdrawn while traversing.
7: speed setpoint not equal to zero.
See also: p5307, p5308, p5309
Remedy:
For fault value = 1:
- Define distance limiting (p5308).
For fault value = 2:
- increase the duration or distance limiting (p5309, p5308).
For fault value = 3:
- check distance limiting (p5308).
For fault value = 4:
- configure speed control with encoder.
For fault value = 5:
- increase distance limit p5308 or reduce offset p5297.
- the fault can only be acknowledged after p5300 was set = 0.
- for the factory setting, a test signal duration of approximately 1.3 s is obtained. If an offset (p5297) of 60 rpm is set, for
example, then this results in a distance of approximately 1.3 revolutions. As a consequence, a value must be parameterized
in parameter p5308, which is longer than this distance + 10% controller reserve (e.g. p5308=515°). Further, the distance
depends on the speed controller sampling time (p0115[1]) and the controller configuration (p5271).
For fault value = 6:
- keep the drive switched on until the "Test signal" function has been completely exited.
For fault value = 7:
- set the speed setpoint to zero. It is possible that the setpoint was entered from the control panel.
207094
<location>General parameter limit violation
Drive object:
All objects
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
NONE
Cause:
As a result of the violation of a parameter limit, the parameter value was automatically corrected.
Minimum limit violated --> parameter is set to the minimum value.
Maximum limit violated --> parameter is set to the maximum value.
Alarm value (r2124, interpret decimal):
Parameter number, whose value had to be adapted.
Remedy:
Check the adapted parameter values and if required correct.
207095
<location>Drive: One Button Tuning activated
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Alarms
992
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
NONE
Acknowledge:
NONE
Cause:
The One Button Tuning function is active.
One Button Tuning is performed at the next switch-on command.
See also: p5300
Remedy:
Not necessary.
The alarm is automatically withdrawn after One Button Tuning has been exited (p5300 = 0).
207097
<location>Drive: Test signal error distance limiting
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
Fault cause: %1, traversing distance: %2
Reaction:
OFF3 (NONE, OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
An error was identified when executing the "Test signal" function (p5307.1 = 1) or auto tuning was selected (p5300 = 1).
The function was not executed or was canceled.
Fault value (r0949, interpret decimal):
yyyyxxxx hex: yyyy = error cause, xxxx = traversing distance
Fault cause = 4:
- travel distance to the EPOS software limit switch is not sufficient.
See also: p5307, p5308, p5309
Remedy:
- enter the traversing path in parameter p5308 - or deselect the function involved in p5301.
- for fault cause = 1, 2, shorter traversing paths may be possible.
For fault cause = 1:
- deselect bit 0 and bit 1 in parameter p5301.
For fault cause = 2:
- deselect bit 2 in parameter p5301.
For fault cause = 3:
- deselect bit 4 and bit 5 in parameter p5301.
For fault cause = 4:
- change the travel direction of One Button Tuning via p5308.
- increase the clearance to the EPOS software limit switch by manually traversing.
207098
<location>Drive: One Button Tuning configuration error
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
Fault cause: %1 bin
Reaction:
OFF3 (NONE, OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
The requested One Button Tuning configuration (p5301) is not supported.
Fault value (r0949, interpret binary):
Bit 5:
The function requires that the "Advanced Positioning Control" function module (APC) is activated.
See also: p3700, p5301
Remedy:
For bit 5 = 1:
- activate the "APC" function module (r0108.7 = 1).
- activate the "APC without sensor on the load side" function (p3700.2 = 1).
207100
<location>Drive: Sampling times cannot be reset
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, VECTOR,
VECTOR_AC
Message value:
Parameter: %1
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
993
SINAMICS alarms
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
When resetting drive parameter (p0976) sampling times cannot be reset using p0111, p0112, p0115.
Fault value (r0949, interpret decimal):
Parameter whose setting prevents the sampling times being reset.
See also: r0110 (Basic sampling times)
Remedy:
- continue to work with the set sampling times.
- before resetting the drive parameters, set the basic clock cycle p0110[0] to the original value.
See also: r0110 (Basic sampling times)
207110
<location>Drive: Sampling times and basic clock cycle do not match
Drive object:
All objects
Message value:
Parameter: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The parameterized sampling times do not match the basic clock cycle.
Fault value (r0949, interpret decimal):
The fault value specifies the parameter involved.
See also: r0110, r0111, p0115
Remedy:
Enter the current controller sampling times so that they are identical to the basic clock cycle, e.g. by selecting p0112. Note
which basic clock cycle is selected in p0111.
The sampling times in p0115 can only be changed manually in the sampling times pre-setting "Expert" (p0112).
See also: r0110, r0111, p0112, p0115
207140
<location>Drive: current controller sampling time for spindle does not match
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The parameterized current controller sampling time for the spindle has been set too high.
Remedy:
Set the sampling time equal to or less than the value in r5034 (p0112, p0115).
See also: p0112, p0115, r5034
207200
<location>Drive: Master control ON command present
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, VECTOR,
VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The ON/OFF1 command is present (no 0 signal).
The command is either influenced via binector input p0840 (current CDS) or control word bit 0 via the master control.
Remedy:
Switch the signal via binector input p0840 (current CDS) or control word bit 0 via the master control to 0.
207220
<location>Drive: Master control by PLC missing
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
-
Alarms
994
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
Infeed: OFF1 (NONE, OFF2)
Servo: OFF1 (NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
The "master control by PLC" signal was missing in operation.
- interconnection of the binector input for "master control by PLC" is incorrect (p0854).
- the higher-level control has withdrawn the "master control by PLC" signal.
- data transfer via the fieldbus (master/drive) was interrupted.
Remedy:
- check the interconnection of the binector input for "master control by PLC" (p0854).
- check the "master control by PLC" signal and, if required, switch in.
- check the data transfer via the fieldbus (master/drive).
Note:
If the drive should continue to operate after withdrawing "master control by PLC" then fault response must be parameterized
to NONE or the message type should be parameterized as alarm.
207300
<location>Drive: Line contactor feedback signal missing
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
- the line contactor was not able to be closed within the time in p0861.
- the line contactor was not able to be opened within the time in p0861.
- the line contactor dropped out during operation
- the line contactor has closed although the drive converter is switched off.
Remedy:
- check the setting of p0860.
- check the feedback circuit from the line contactor.
- increase the monitoring time in p0861.
- for G150LE (power expansion)/G150HP (High Power), the following applies:
If, contrary to the appropriate specifications, the circuit breakers are monitored using the line contactor control of drive
object B_INF then, for B_INF, parameter p0869.1 must be set = 0.
See also: p0860 (Line contactor feedback signal), p0861 (Line contactor monitoring time)
207300
<location>Drive: Line contactor feedback signal missing
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
- the line contactor was not able to be closed within the time in p0861.
- the line contactor was not able to be opened within the time in p0861.
- the line contactor dropped out during operation
- the line contactor has closed although the drive converter is switched off.
Remedy:
- check the setting of p0860.
- check the feedback circuit from the line contactor.
- increase the monitoring time in p0861.
See also: p0860 (Line contactor feedback signal), p0861 (Line contactor monitoring time)
207311
<location>Bypass motor switch
Drive object:
VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
995
SINAMICS alarms
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
Fault value (r0949, interpret bitwise binary):
Bit 1: Switch "Closed" feedback signal missing.
Bit 2: Switch "Open" feedback signal missing.
Bit 3: Switch feedback signal too slow.
After switching, the system waits for the positive feedback signal. If the feedback signal is received later than the specified
time, then a fault trip (shutdown) is issued.
Bit 6: Drive switch feedback signal not consistent with the bypass state.
The drive switch is closed when switching-on or when switching-in the motor.
See also: p1260, r1261, p1266, p1267, p1269, p1274
Remedy:
- check the transfer of the feedback signals.
- check the switch.
207312
<location>Bypass Line Side Switch:
Drive object:
VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
The Line Side Switch feedback signal is not plausible.
Fault value (r0949, interpret binary):
Bit 1: Switch "Closed" feedback signal missing.
Bit 2: Switch "Open" feedback signal missing.
Bit 3: Switch feedback signal too slow.
After switching, the system waits for the positive feedback signal. If the feedback signal is received later than the specified
time, then the system is shut down.
Bit 6: Line Side Switch feedback signal not consistent with the bypass state.
When switching-on or when switching-in (staging) the motor, the line side switch is closed without this having been
requested from the bypass.
See also: p1260, r1261, p1266, p1267, p1269, p1274
Remedy:
- check the transfer of the feedback signals.
- check the switch.
207320
<location>Drive: Automatic restart interrupted
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
- the specified number of restart attempts (p1211) has been completely used up because within the monitoring time
(p1213) the faults were not able to be acknowledged. The number of restart attempts (p1211) is decremented at each new
start attempt.
- the monitoring time for the power unit has expired (p0857).
- when exiting commissioning or at the end of the motor identification routine or the speed controller optimization, the drive
unit is not automatically switched on again.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
- increase the number of restart attempts (p1211). The actual number of starting attempts is displayed in r1214.
- increase the delay time in p1212 and/or the monitoring time in p1213.
- either increase or disable the monitoring time of the power unit (p0857).
Alarms
996
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
207320
<location>Drive: Automatic restart interrupted
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
- the specified number of restart attempts (p1211) has been completely used up because within the monitoring time
(p1213) the faults were not able to be acknowledged. The number of restart attempts (p1211) is decremented at each new
start attempt.
- the monitoring time for the power unit has expired (p0857).
- when exiting commissioning or at the end of the motor identification routine or the speed controller optimization, the drive
unit is not automatically switched on again.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
- increase the number of restart attempts (p1211). The actual number of starting attempts is displayed in r1214.
- increase the delay time in p1212 and/or the monitoring time in p1213.
- either increase or disable the monitoring time of the power unit (p0857).
- reduce the delay time to reset the start counter p1213[1] so that fewer faults are registered in the time interval.
207321
<location>Drive: Automatic restart active
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The automatic restart (AR) is active. When the line supply returns and/or the causes of the existing faults are removed the
drive is automatically restarted. The pulses are enabled and the motor starts to rotate.
Remedy:
- the automatic restart (AR) should, if required, be inhibited (p1210 = 0).
- an automatic restart can be directly interrupted by withdrawing the switch-on command (BI: p0840).
207329
<location>Drive: kT estimator, kT(iq) characteristic or voltage compensation does not
function
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A function of the function module "extended torque control" (r0108.1) was activated - however the (complete) function is
not available.
Alarm value (r2124, interpret decimal):
1 ... 3: The kT estimator is active (p1780.3 = 1) without a functioning compensation of the voltage emulation error in the
drive converter. This means that the accuracy is severely restricted.
1: The drive converter voltage emulation error "final value" is 0 (p1952).
2: The drive converter voltage emulation error "current offset" is 0 (p1953).
3: The compensation of the voltage emulation error is disabled (p1780.8 = 0).
4: The kT estimator (p1780.3 = 1), the kT(iq) characteristic (p1780.9 = 1) or the compensation of the voltage emulation error
(p1780.8 = 1) was activated without activating the function module "extended torque control" (when the function module
is activated, the following must apply: r0108.1 = 1).
5: the kT(iq) characteristic has been activated (p1780.9 = 1). However, the kT characteristic value kT1 is 0 (p0645). The
function is not active.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
997
SINAMICS alarms
Remedy:
For alarm value = 1, 2:
- carry out an identification of the voltage emulation error in the drive converter (p1909.14 = 1, p1910 = 1).
- set the parameter to compensate the voltage emulation error in the drive converter (p1952, p1953).
For alarm value = 3:
- enable the compensation of the voltage emulation error in the drive converter (p1780.8 = 1).
For alarm value = 4:
- activate the function module "extended torque control" (r0108.1 = 1) or deactivate the corresponding functions (p1780.3
= 0, p1780.8 = 0, p1780.9 = 0).
For alarm value = 5:
- determine the parameters of the kT characteristic (p0645 ... p0648) using the rotating measurement (p1959.6, p1960).
- enter the parameters of the kT characteristic (p0645 ... p0648) (if known).
- if necessary, deactivate the kT characteristic (p1780.9 = 0).
207330
<location>Flying restart: Measured search current too low
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY
Cause:
During a flying restart, it was identified that the search current reached is too low.
It is possible that the motor is not connected.
Remedy:
Check the motor feeder cables.
207331
<location>Flying restart: Function not supported
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY
Cause:
It is not possible to power up with the motor rotating (no flying restart).
In the following cases, the "flying restart" function is not supported:
Permanent-magnet synchronous motor (PMSM):
- operation with U/f characteristic.
- encoderless operation without a Voltage Sensing Module (VSM) being connected.
Separately excited synchronous motor (SESM):
- operation with U/f characteristic.
Remedy:
- deactivate the "flying restart" function (p1200 = 0).
- change the open-loop/closed-loop control mode (p1300).
- connect a Voltage Sensing Module (VSM) (voltage measurement).
207332
<location>Flying restart: maximum speed reduced
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The maximum speed that can be reached is reduced; at very high speeds problems associated with the flying restart can be
encountered.
Possible causes:
- power ratio, power unit/motor too high
Remedy:
Parameter changes are not required.
Note:
A flying restart at speeds above 3000 rpm should be avoided.
Alarms
998
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
207333
<location>Closed-loop control function not supported
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
A closed-loop control function that is not supported was activated.
Fault value (r0949, interpret decimal):
0:
Open-loop controlled operation (open-loop mode for speeds < p1755) is not supported in the "encoderless torque" control
mode (see p1300, p1501).
Remedy:
For fault value = 0:
When keeping encoderless operation, these options include:
- change the control mode to "Encoderless speed control" (p1300 = 20, p1501 = 0).
- for continuation of torque control:
Activate encoderless operation - including zero frequency - with test pulses (p1750.5 = 1, only SINAMICS S120 + licensing).
207334
<location>Function not possible
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
For this configuration, the selected function is not possible.
Fault value (r0949, interpret decimal):
0:
Function "Travel to fixed end stop" (p1545) was selected, although encoderless operation or U/f operation is active.
Remedy:
For fault value = 0:
- Operate the closed-loop speed control with an encoder.
- If necessary, deselect function "Travel to fixed stop".
207350
<location>Drive: Measuring probe parameterized to a digital output
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The measuring probe is connected to a bi-directional digital input/output and the terminal is set as output.
Alarm value (r2124, interpret decimal):
8: DI/DO 8 (X122.9/X132.1)
9: DI/DO 9 (X122.10/X132.2)
10: DI/DO 10 (X122.12/X132.3)
11: DI/DO 11 (X122.13/X132.4)
12: DI/DO 12 (X132.9)
13: DI/DO 13 (X132.10)
14: DI/DO 14 (X132.12)
15: DI/DO 15 (X132.13)
Regarding the terminal designation:
The first designation is valid for CU320, the second for CU305.
Remedy:
- set the terminal as input (p0728).
- deselect the measuring probe (p0488, p0489, p0580).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
999
SINAMICS alarms
207351
<location>Drive: Measuring probe parameterized to a digital output
Drive object:
SERVO, SERVO_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The measuring probe is connected to a bi-directional digital input/output and the terminal is set as output.
Alarm value (r2124, interpret decimal):
0: DI/DO 0 distributed (X3.2)
1: DI/DO 1 distributed (X3.4)
Remedy:
- set the terminal as input (p4028).
- deselect the probe (p0488, p0489).
See also: p0488, p0489, p4028
207354
<location>Drive: Cogging torque compensation not possible
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
Fault cause: %1, drive data set: %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
Cogging torque compensation is selected and is not (completely) supported.
Alarm value (r2124, interpret hexadecimal):
yyyyxx hex: yyyy = fault cause, xx = drive data set
yyyy = 1:
The encoder evaluation does not support this function.
yyyy = 2:
The encoder has no absolute information.
yyyy = 3:
The motor has no encoder (p0187 = 99).
yyyy = 3:
The motor has no encoder (p0187 = 99).
yyyy = 4:
Learning was activated (p5251) for closed-loop control without encoder (p1300 = 20 or p1404 < 12 rpm or 12 m/min - or
p1317 = 1).
yyyy = 5:
The internal table is active; however, period p5253 has not been set equal to 1.
Remedy:
If required, deselect the cogging torque compensation (p5250 = 0).
For fault cause = 1:
Use an absolute encoder or an encoder evaluation that supports the function (r0459.13 = 1). If required, upgrade the
firmware to a newer version (version 04.50.30.01 or higher is required).
For fault cause = 2:
Use an encoder with absolute information (absolute track, unique zero mark, resolver with one pole pair). The function
cannot be tested as long as the encoder is not reset after learning (encoder fault, parking, POWER ON). Continuous use is
not recommended.
For fault cause = 3:
Only select cogging torque compensation for operation with motor encoder.
For fault cause = 4:
Activate learning, only for operation with encoder (p1300, p1404, p1317).
For fault cause = 5:
- set period p5253 = 1.
- activate the external table and learning (p5250.0 = 1, p5251).
See also: p5250 (Compensation configuration), p5251 (Activate learn cogging torque compensation)
Alarms
1000
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
207355
<location>Drive: cogging torque compensation error when learning
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF1 (NONE, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
A cogging torque compensation error has occurred while learning.
Fault value (r0949, interpret decimal):
1:
The learning velocity is too high.
- rotating: absolute value greater than 5 [rpm]
- linear: absolute value greater than 0.5 [m/min]
2:
The commutation angle offset (p0431) is incorporated in the position and was changed.
Remedy:
For fault value = 1:
Repeat learning with the lower velocity setpoint.
Recommended speeds:
- rotating 2 [rpm]
- linear 0.1 [m/min]
For fault value = 2:
New learning required, which must be saved.
See also: p5250 (Compensation configuration), p5251 (Activate learn cogging torque compensation)
207356
<location>Drive: Cogging torque compensation motor or encoder serial number different
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
Fault cause: %1, drive data set: %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
Cogging torque compensation is activated via external table (p5260, p5261) (p5250.0 = 1), not active or incorrectly
parameterized.
Alarm value (r2124, interpret hexadecimal):
yyyyxx hex: yyyy = fault cause, xx = drive data set
yyyy = 1:
Motor or encoder were replaced, or external table was not learned.
yyyy = 2:
Cogging torque compensation via external table was activated for more than one motor data set, and the serial numbers
do not match. There is only one external table.
yyyy = 3:
Cogging torque compensation via external table was activated for more than one motor data set, and p0826 indicates that
different motors are involved. There is only one external table.
yyyy = 4:
Cogging torque compensation via external table was activated for data sets with different encoder data sets (EDS). Cogging
torque compensation with external table only supports one encoder.
Remedy:
For fault cause = 1:
Relearn cogging torque table (p5251).
For fault cause = 2:
Only activate cogging torque compensation with external table for motor data sets (MDS) with the same motor (p5250.0).
For fault cause = 3:
Only activate cogging torque compensation with external table for motor data sets (MDS) with the same motor (p5250.0).
For the same motor, set p0826 to the same value.
For fault cause = 4:
Only activate cogging torque compensation with external table for data sets with the same encoder (p5250.0, p0187).
See also: p5250 (Compensation configuration), p5251 (Activate learn cogging torque compensation)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1001
SINAMICS alarms
207400
<location>Drive: DC link voltage maximum controller active
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The DC link voltage controller has been activated because of the upper switch-in threshold (p1244).
A system deviation can occur between the setpoint and actual speed.
See also: r0056, p1240
Remedy:
Not necessary.
This alarm is automatically withdrawn after the upper threshold has been distinctly exceeded.
Otherwise, apply the following measures:
- use a Braking Module or regenerative feedback unit.
- increase the ramp-down times (p1121, p1135).
- shut down the Vdc_max controller (p1240 = 0).
207400
<location>Drive: DC link voltage maximum controller active
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The DC link voltage controller has been activated because the upper switch-in threshold has been exceeded (r1242, r1282).
The ramp-down times are automatically increased in order to maintain the DC link voltage (r0070) within the permissible
limits. There is a system deviation between the setpoint and actual speeds.
When the DC link voltage controller is switched out (disabled), this is the reason that the ramp-function generator output
is set to the speed actual value.
See also: r0056, p1240, p1280
Remedy:
If the controller is not to intervene:
- increase the ramp-down times.
- switch off the Vdc_max controller (p1240 = 0 for vector control, p1280 = 0 for U/f control).
If the ramp-down times are not to be changed:
- use a chopper or regenerative feedback unit.
207401
<location>Drive: DC link voltage maximum controller deactivated
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The Vdc_max controller can no longer maintain the DC link voltage (r0070) below the limit value (r1242, r1282) and was
therefore switched out (disabled).
- the line supply voltage is permanently higher than specified for the power unit.
- the motor is permanently in the regenerative mode as a result of a load that is driving the motor.
Remedy:
- check whether the input voltage is within the permissible range (if required, increase the value in p0210).
- check whether the load duty cycle and load limits are within the permissible limits.
207402
<location>Drive: DC link voltage minimum controller active
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Alarms
1002
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The DC link voltage controller has been activated due to the lower switch-in threshold (p1248).
A system deviation can occur between the setpoint and actual speed.
A possible cause can be e.g. that the line supply has failed.
See also: r0056, p1240, p1248
Remedy:
Not necessary.
This alarm is automatically withdrawn after the lower threshold has been distinctly exceeded.
Otherwise, apply the following measures:
- check the line supply and infeed.
- increase the ramp-up times (p1120).
- shut down the Vdc_min controller (p1240 = 0).
207402
<location>Drive: DC link voltage minimum controller active
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The DC link voltage controller has been activated as the lower switch-in threshold has been undershot (r1246, r1286).
The kinetic energy of the motor is used to buffer the DC link. The drive is therefore braked.
See also: r0056, p1240, p1280
Remedy:
The alarm disappears when power supply returns.
207403
<location>Drive: Lower DC link voltage threshold reached
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The DC link voltage monitoring is active (p1240 = 5, 6) and the lower DC link voltage threshold (p1248) was reached in the
"Operation" state.
Remedy:
- check the line supply voltage.
- check the infeed.
- reduce the lower DC link threshold (p1248).
- switch out (disable) the DC link voltage monitoring (p1240 = 0).
207403
<location>Drive: Lower DC link voltage threshold reached
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The DC link voltage monitoring is active (p1240, p1280 = 5, 6) and the lower DC link voltage threshold (r1246, r1286) was
reached in the "Operation" state.
Remedy:
- check the line supply voltage.
- check the infeed.
- adapt the device supply voltage (p0210) or the switch-on level (p1245, p1285).
- disable the DC link voltage monitoring (p1240, p1280 = 0).
207404
<location>Drive: Upper DC link voltage threshold reached
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1003
SINAMICS alarms
Cause:
The DC link voltage monitoring is active (p1240 = 4, 6) and the upper DC link voltage threshold (p1244) was reached in the
"Operation" state.
Remedy:
- check the line supply voltage.
- check the infeed unit or the Braking Module.
- increase the upper DC link voltage threshold (p1244).
- if necessary, deactivate the DC link voltage monitoring (p1240 = 0).
207404
<location>Drive: Upper DC link voltage threshold reached
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
- the DC link voltage monitoring is active (p1240, p1280 = 4, 6) and the upper DC link voltage threshold (r1242, r1282) was
reached in the "Operation" state.
- the monitoring of the DC link voltage (p1284) has responded (only U/f control).
- the DC link voltage control (only when the technology controller is activated r0108.16 = 1) is available and the supply
voltage (p0210, p0212) has been reduced.
Remedy:
- check the line supply voltage.
- check the infeed.
- adapt the device supply voltage (p0210, p0212.0 = 0).
- if necessary, deactivate the DC link voltage monitoring (p1240, p1280 = 0).
- adapt the monitoring of the DC link voltage (p1284, only U/f control).
207405
<location>Drive: Kinetic buffering minimum speed fallen below
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
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))
207406
<location>Drive: Kinetic buffering maximum time exceeded
Drive object:
VECTOR, VECTOR_AC
Message value:
-
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))
207407
<location>Drive: Vdc reduction not permissible
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
For chassis power units, the reduction of the line voltage (see r0212.0) is only possible for closed-loop control of the DC link
voltage.
Alarms
1004
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- Activate DC link voltage control for the motor/generator.
- deactivate line voltage reduction (p0212.0 = 0).
See also: p0212
207409
<location>Drive: U/f control, current limiting controller active
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
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.
207410
<location>Drive: Current controller output limited
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
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.
- no DC link voltage present.
- Motor Module defective.
Remedy:
- connect the motor or check the motor contactor.
- check the DC link voltage (r0070).
- check the Motor Module.
207410
<location>Drive: Current controller output limited
Drive object:
VECTOR, VECTOR_AC
Message value:
-
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).
207411
<location>Drive: Flux controller output limited
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1005
SINAMICS alarms
Cause:
The specified flux setpoint cannot be reached, although the set maximum field current is specified (p1603).
- incorrect motor data.
- motor data and motor configuration (star-delta) do not match.
- the current limit has been set too low for the motor (p0640, p0323, p1603).
- induction motor (encoderless, open-loop controlled) in I2t limiting.
- the Motor Module is too small.
Remedy:
- correct the motor data.
- check the motor configuration.
- correct the current limits (p0640, p0323, p1603).
- reduce the induction motor load.
- if required, use a larger Motor Module.
207411
<location>Drive: Flux setpoint not reached when building up excitation
Drive object:
VECTOR, VECTOR_AC
Message value:
-
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.
- the Motor Module is too small.
- the magnetizing time p0346 is too short.
Remedy:
- correct the motor data. Perform motor data identification and rotating measurement.
- check the motor configuration.
- correct the current limits (p0640).
- reduce the induction motor load.
- if required, use a larger Motor Module.
- check motor supply cable.
- check power unit.
- increase p0346.
207412
<location>Drive: Commutation angle incorrect (motor model)
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
ENCODER (NONE, OFF2)
Acknowledge:
IMMEDIATELY
Alarms
1006
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
An incorrect commutation angle was detected that can result in a positive coupling in the speed controller.
Possible causes:
- the phase sequence of the output phases for the motor is incorrect (e.g. the phases are interchanged).
- the motor encoder is incorrectly adjusted with respect to the magnet position.
- the motor encoder is damaged.
- the angular commutation offset is incorrectly set (p0431).
- data to calculate the motor model has been incorrectly set (p0356 (motor-stator leakage inductance) and/or p0350 (motor-
stator resistance) and/or p0352 (cable resistance)).
- the changeover speed for the motor model is too low (p1752). The monitoring function only becomes effective above the
changeover speed.
- pole position identification might have calculated an incorrect value when activated (p1982 = 1).
- the motor encoder speed signal is faulted.
- the control loop is instable due to incorrect parameterization.
Fault value (r0949, interpret decimal):
SERVO:
0: The comparison of the pole position angle from the encoder and motor model resulted in an excessively high value
(p1778[1] > 80 ° electrical).
1: -
VECTOR:
0: The comparison of the pole position angle from the encoder and motor model resulted in an excessively high value (> 45
° electrical).
1: The change in the speed signal from the motor encoder has changed by > p0492 within a current controller clock cycle.
Remedy:
- check the phase sequence for the motor, and if required, correct (wiring, p1820).
- if the encoder mounting was changed - re-adjust the encoder.
- replace the defective motor encoder.
- correctly set the angular commutation offset (p0431). If required, determine using p1990.
- correctly set the motor stator resistance, cable resistance and motor-stator leakage inductance (p0350, p0352, p0356).
Calculate the cable resistance from the cross-section and length, check the inductance and stator resistance using the motor
data sheet, measure the stator resistance, e.g. using a multimeter - and if required, again identify the values using the
stationary motor data identification (p1910).
- increase the changeover speed for the motor model (p1752). The monitoring is completely deactivated for p1752 > p1082
(maximum speed).
- with pole position identification activated (p1982 = 1) check the procedure for pole position identification (p1980) and
force a new pole position identification procedure by means of deselection followed by selection (p1982 = 0 -> 1).
Note:
For High Dynamic Motors (1FK7xxx-7xxx), for applications with a higher current, if necessary, the monitoring should be
disabled.
See also: r1778 (Motor model flux angle difference)
207412
<location>Drive: Commutation angle incorrect (motor model)
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
ENCODER (NONE, OFF2)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1007
SINAMICS alarms
Cause:
An incorrect commutation angle was detected that can result in a positive coupling in the speed controller.
Possible causes:
- the phase sequence of the output phases for the motor is incorrect (e.g. the phases are interchanged).
- the motor encoder is incorrectly adjusted with respect to the magnet position.
- the motor encoder is damaged.
- the angular commutation offset is incorrectly set (p0431).
- data to calculate the motor model has been incorrectly set (p0356 (motor-stator leakage inductance) and/or p0350 (motor-
stator resistance) and/or p0352 (cable resistance)).
- the changeover speed for the motor model is too low (p1752). The monitoring function only becomes effective above the
changeover speed.
- pole position identification might have calculated an incorrect value when activated (p1982 = 1).
- the motor encoder speed signal is faulted.
- the control loop is instable due to incorrect parameterization.
Fault value (r0949, interpret decimal):
SERVO:
0: The comparison of the pole position angle from the encoder and motor model resulted in an excessively high value
(p1778[1] > 80 ° electrical).
1: -
VECTOR:
0: The comparison of the pole position angle from the encoder and motor model resulted in an excessively high value (> 45
° electrical).
1: The change in the speed signal from the motor encoder has changed by > p0492 within a current controller clock cycle.
Remedy:
- check the phase sequence for the motor, and if required, correct (wiring, p1820).
- if the encoder mounting was changed - re-adjust the encoder.
- replace the defective motor encoder.
- correctly set the angular commutation offset (p0431). If required, determine using p1990.
- correctly set the motor stator resistance, cable resistance and motor-stator leakage inductance (p0350, p0352, p0356).
Calculate the cable resistance from the cross-section and length, check the inductance and stator resistance using the motor
data sheet, measure the stator resistance, e.g. using a multimeter - and if required, again identify the values using the
stationary motor data identification (p1910).
- increase the changeover speed for the motor model (p1752). The monitoring is completely deactivated for p1752 > p1082
(maximum speed).
- with pole position identification activated (p1982 = 1) check the procedure for pole position identification (p1980) and
force a new pole position identification procedure by means of deselection followed by selection (p1982 = 0 -> 1).
Note:
For High Dynamic Motors (1FK7xxx-7xxx), for applications with a higher current, if necessary, the monitoring should be
disabled.
207413
<location>Drive: Commutation angle incorrect (pole position identification)
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
ENCODER (NONE, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
An incorrect commutation angle was detected that can result in a positive coupling in the speed controller.
Within the pole position identification routine (p1982 = 2):
- a difference of > 45 ° electrical to the encoder angle was determined.
For VECTOR, within the encoder adjustment (p1990 = 2):
- a difference of > 6 ° electrical to the encoder angle was determined.
Remedy:
- correctly set the angular commutation offset (p0431).
- re-adjust the motor encoder after the encoder has been replaced.
- replace the defective motor encoder.
- check the pole position identification routine. If the pole position identification routine is not suitable for this motor type,
then disable the plausibility check (p1982 = 0).
Alarms
1008
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
207414
<location>Drive: Encoder serial number changed
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
ENCODER (NONE, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
The serial number of the motor encoder of a synchronous motor has changed. The change was only checked for encoders
with serial number (e.g. EnDat encoders) and build-in motors (e.g. p0300 = 401) or third-party motors (p0300 = 2).
Cause 1:
- the encoder was replaced.
Cause 2:
- a third-party, built-in or linear motor was re-commissioned.
Cause 3:
- the motor with integrated and adjusted encoder was replaced.
Cause 4:
- the firmware was updated to a version that checks the encoder serial number.
Note:
With closed-loop position control, the serial number is accepted when starting the adjustment (p2507 = 2).
When the encoder is adjusted (p2507 = 3), the serial number is checked for changes and if required, the adjustment is reset
(p2507 = 1).
Proceed as follows to hide serial number monitoring:
- set the following serial numbers for the corresponding Encoder Data Set: p0441= FF, p0442 = 0, p0443 = 0, p0444 = 0,
p0445 = 0.
- parameterize F07414 as message type N (p2118, p2119).
Remedy:
For causes 1, 2:
Carry out an automatic adjustment using the pole position identification routine. Acknowledge fault. Initiate the pole
position identification routine with p1990 = 1. Then check that the pole position identification routine is correctly executed.
SERVO:
If a pole position identification technique is selected in p1980, and if p0301 does not contain a motor type with an encoder
adjusted in the factory, then p1990 is automatically activated.
or
Set the adjustment via p0431. In this case, the new serial number is automatically accepted.
or
Mechanically adjust the encoder. Accept the new serial number with p0440 = 1.
For causes 3, 4:
Accept the new serial number with p0440 = 1.
207415
<location>Drive: Angular commutation offset transfer running
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF2
Acknowledge:
NONE
Cause:
The angular commutation offset was automatically determined using p1990 = 1.
This fault causes the pulses to be suppressed - this is necessary to transfer the angular commutation offset to p0431.
See also: p1990 (Encoder adjustment determine angular commutation offset)
Remedy:
The fault can be acknowledged without any additional measures.
207416
<location>Drive: Flux controller configuration
Drive object:
VECTOR, VECTOR_AC
Message value:
Parameter: %1, index: %2, fault cause: %3
Reaction:
NONE
Acknowledge:
NONE
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1009
SINAMICS alarms
Cause:
The configuration of the flux control (p1401) is contradictory.
Alarm value (r2124, interpret hexadecimal):
ccbbaaaa hex
aaaa = Parameter
bb = Index
cc = fault cause
cc = 01 hex = 1 dec:
Quick magnetizing (p1401.6) for soft start (p1401.0).
cc = 02 hex = 2 dec:
Quick magnetizing (p1401.6) for flux build-up control (p1401.2).
cc = 03 hex = 3 dec:
Quick magnetizing (p1401.6) for Rs identification after restart (p0621 = 2).
Remedy:
For fault cause = 1:
- Shut down soft start (p1401.0 = 0).
- Shut down quick magnetizing (p1401.6 = 0).
For fault cause = 2:
- switch-on flux build-up control (p1401.2 = 1).
- Shut down quick magnetizing (p1401.6 = 0).
For fault cause = 3:
- Re-parameterize Rs identification (p0621 = 0, 1)
- Shut down quick magnetizing (p1401.6 = 0).
207417
<location>Drive: Pulse technique not plausible (motor model)
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
The evaluation of the test pulse response indicated incorrect values.
Fault value (r0949, interpret decimal):
0:
An impermissible pulse technique configuration was detected during ramp-up.
Possible causes:
- the pulse technique was initially selected when the system powered up (p1750.5 = 1) but the power unit component does
not support the current oversampling required (see r0192.23). As a consequence, p1750.0 was deselected automatically.
10:
The pulse response is repeatedly implausible.
Possible causes:
- incorrect configuration of the power unit component
- the power unit component is faulty.
20:
For the specified pulse amplitude, the measured pulse response is much higher than the expected value.
Possible causes:
- Strong oscillations have occurred.
- the motor is short-circuited for high frequencies (output filter).
- the motor is damaged.
Alarms
1010
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
For fault value = 0:
Once the pulse technique has been deselected automatically (p1750.5 = 0), there are two possible options:
- acknowledge the fault and save parameter p1750.5 = 0 -> field-oriented control mode to standstill is not used and replaced
by transition to open-loop control at low speeds.
- upgrade the power unit firmware (at least V4.3) -> field-oriented control mode to standstill is available.
For fault value = 10:
With active selection of the pulse technique (p1750.5 = 1):
- POWER ON (switch-off/switch-on) the Control Unit and the power unit together again.
or
- carry out a manual warm restart (p0009 = 30, p0976 = 2, 3).
If this does not solve the problem: Replace the power unit component.
For fault value = 20:
- control parameters might have been adjusted (factory setting, commissioning).
- filters must not be connected between motor and converter/inverter.
- check the motor.
207419
<location>Drive: Current setpoint filter adaptation error
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
An error has occurred when configuring or when using the "Current setpoint filter adaptation" function.
Fault value (r0949, interpret binary):
Bit 0: a filter has still not been assigned (p5281).
Bit 1: the assigned filter belongs to the "Extended current setpoint filter" function module that has not been activated
(r0108.21).
Bit 2: the assigned filter is a type or has a characteristic, which is unsuitable for adaptation.
Bit 3: the assigned filter has not been activated (p1656, p5200).
Bit 4 ... 15: internal fault occurred.
Bit 16 ... 31: number of the drive data set with fault.
See also: p5280 (Current setpoint filter adaptation configuration), p5281 (Current setpoint filter adaptation assignment)
Remedy:
The message can always be removed by deactivating adaptation (p5280 = 0, -1).
If adaptation is to remain active, then the countermeasure should be applied depending on the particular fault value.
For bit 0:
Assign the filter (p5281).
For bit 1:
activate the "Extended current setpoint filter" function module (r0108.21).
For bit 2:
Set the filter type "General filter 2nd order" and set the characteristic of a bandstop filter.
For bit 3:
Activate filter (p1656, p5200).
For bits 4 ... 15:
- carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade firmware to later version.
See also: p5280 (Current setpoint filter adaptation configuration), p5281 (Current setpoint filter adaptation assignment)
207420
<location>Drive: Current setpoint filter natural frequency > Shannon frequency
Drive object:
A_INF, A_INF_840, R_INF
Message value:
%1
Reaction:
NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1011
SINAMICS alarms
Cause:
One of the filter natural frequencies is greater than the Shannon frequency.
The Shannon frequency is calculated according to the following formula: 0.5 / p0115[0]
Fault value (r0949, interpret binary):
Bit 3: Filter 4 (p1673, p1675)
Bit 16: Filter 5 (p5202, p5204)
Bit 18: Filter 7 (p5212, p5214)
Remedy:
- reduce the numerator or denominator natural frequency of the current setpoint filter involved.
- reduce the current controller sampling time (p0115[0]).
- switch out the filter involved (p1656).
207420
<location>Drive: Current setpoint filter natural frequency > Shannon frequency
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
One of the filter natural frequencies is greater than the Shannon frequency.
The Shannon frequency is calculated according to the following formula: 0.5 / p0115[0]
Fault value (r0949, interpret binary):
Bit 0: Filter 1 (p1658, p1660)
Bit 1: Filter 2 (p1663, p1665)
Bit 2: Filter 3 (p1668, p1670)
Bit 3: Filter 4 (p1673, p1675)
Bit 8 ... 15: Data set number (starting from zero)
Bit 16: Filter 5 (p5202, p5204) - extended current setpoint filter (r0108.21)
Bit 17: Filter 6 (p5207, p5209) - extended current setpoint filter (r0108.21)
Bit 18: Filter 7 (p5212, p5214) - extended current setpoint filter (r0108.21)
Bit 19: Filter 8 (p5217, p5219) - extended current setpoint filter (r0108.21)
Bit 20: Filter 9 (p5222, p5224) - extended current setpoint filter (r0108.21)
Bit 21: Filter 10 (p5227, p5229) - extended current setpoint filter (r0108.21)
Remedy:
- reduce the numerator or denominator natural frequency of the current setpoint filter involved.
- reduce the current controller sampling time (p0115[0]).
- switch out the filter involved (p1656).
207421
<location>Drive: Speed filter natural frequency > Shannon frequency
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
One of the filter natural frequencies is greater than the Shannon frequency.
The Shannon frequency is calculated according to the following formula: 0.5 / p0115[1]
Fault value (r0949, interpret binary):
Bit 0: Filter 1 (p1417, p1419)
Bit 1: Filter 2 (p1423, p1425)
Bit 4: Actual value filter (p1447, p1449)
Bit 8 ... 15: Data set number (starting from zero)
Remedy:
- reduce the numerator or denominator natural frequency of the speed setpoint filter involved.
- reduce the speed controller sampling time (p0115[1]).
- switch off the filter involved (p1413, p1414).
Alarms
1012
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
207422
<location>Drive: Reference model natural frequency > Shannon frequency
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The natural filter frequency of the PT2 element for the reference model (p1433) is greater than the Shannon frequency.
The Shannon frequency is calculated according to the following formula: 0.5 / p0115[1]
Remedy:
- reduce the natural frequency of PT2 element for reference model (p1433).
- reduce the speed controller sampling time (p0115[1]).
207423
<location>Drive: APC filter natural frequency > Shannon frequency
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
One of the filter natural frequencies is greater than the Shannon frequency.
The Shannon frequency is calculated according to the following formula: 0.5 / (p0115[1] * x)
Fault value (r0949, interpret binary):
Bit 0: Filter 1.1 (p3711, p3713), x = 1
Bit 4: Filter 2.1 (p3721, p3723), x = p3706
Bit 5: Filter 2.2 (p3726, p3728), x = p3706
Bit 8: Filter 3.1 (p3731, p3733), x = p3707
Bit 9: Filter 3.2 (p3736, p3738), x = p3707
Bit 16 ... 32: Data set number (starting from zero)
Remedy:
- reduce the numerator or denominator natural frequency of the filter involved.
- reduce the speed controller sampling time (p0115[1]) or the sub-sampling (p3706, p3707).
- switch out the filter involved (p3704).
207424
<location>Drive: Operating condition for APC not valid
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Cause:
The APC function (Advanced Positioning Control) has identified an invalid operating condition.
Alarm value (r2124, interpret binary):
Bit 0 = 1:
APC is operating without encoder
Bit 1 = 1:
Possible causes:
- the load measuring system for APC, selected using p3701, has a fault.
- the load measuring system selected using p3701 is in the park state (r0481[0...2].14).
The APC function is disabled.
Bit 2 = 1:
Possible causes:
- the load measuring system for APC, selected using p3701, has a fault.
- the load measuring system selected using p3701 is in the park state (r0481[0...2].14).
The pulse de-coupling is disabled, i.e. the speed of the motor measuring system is used as speed for the closed-loop motor
speed control.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1013
SINAMICS alarms
Remedy:
For bit 0:
Only use the APC function in operation with an encoder.
For bit 1, 2:
Check the load measuring system.
207425
<location>Drive: APC monitoring time for speed limit expired
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF1
Acknowledge:
IMMEDIATELY
Cause:
The limit value (p3778) for the speed/velocity was exceeded for a time longer than that set in the monitoring time (p3779).
Note:
APC: Advanced Positioning Control
Remedy:
- check the measured value.
- check the limit value and monitoring time (p3778, p3779).
207426
<location>Technology controller actual value limited
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The actual value for the technology controller, interconnected via connector input p2264, has reached a limit.
Fault value (r0949, interpret decimal):
1: upper limit reached.
2: lower limit reached.
Remedy:
- adapt the limits to the signal level (p2267, p2268).
- check the actual value normalization (p0595, p0596).
- Deactivate evaluation of the limits (p2252.3)
See also: p0595, p0596, p2264, p2267, p2268
207428
<location>Technology controller parameterizing error
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The technology controller has a parameterizing error.
Alarm value (r2124, interpret decimal):
1:
The upper output limit in p2291 is set lower than the lower output limit in p2292.
Remedy:
For alarm value = 1:
Set the output limit in p2291 higher than in p2292.
See also: p2291 (Technology controller maximum limiting), p2292 (Technology controller minimum limiting)
207429
<location>Drive: DSC without encoder not possible
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF2
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
1014
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The function DSC (Dynamic Servo Control) was activated although there is no encoder.
See also: p1191 (DSC position controller gain KPC), p1192 (DSC encoder selection)
Remedy:
Check the encoder selection configuration (p1192).
Note:
If there is no encoder and connector input p1191 (DSC position controller gain) is interconnected, then connector input
p1191 must have a 0 signal.
207430
<location>Drive: Changeover to open-loop torque controlled operation not possible
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
For encoderless operation, the converter cannot change over to closed-loop torque-controlled operation (BI: p1501).
Remedy:
Do not attempt to cover over to closed-loop torque-controlled operation.
207431
<location>Drive: Changeover to encoderless operation not possible
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY
Cause:
For closed-loop torque control, the converter cannot change over to encoderless operation (p1404).
Remedy:
Do not attempt to change over to encoderless operation.
207432
<location>Drive: Motor without overvoltage protection
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY
Cause:
In the case of a fault at maximum speed, the motor can generate an overvoltage that can destroy the drive system.
Fault value (r0949, interpret hexadecimal):
Associated Drive Data Set (DDS).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1015
SINAMICS alarms
Remedy:
Overvoltage protection can be implemented in the following ways:
1. Limit the maximum speed (p1082) without any additional protection.
The maximum speed without protection is calculated as follows:
Rotary synchronous motors: p1082 [rpm] <= 11.695 * r0297/p0316 [Nm/A]
Linear motors: p1082 [m/min] <= 73.484 * r0297/p0316 [N/A]
Rotary synchronous motor connected to the high-frequency converter:
p1082 [rpm] <= 4.33165E9 * (-p0316 + root(p0316^2 + 4.86E-9 * (r0297 * r0313)^2 * (r0377 - p0233) [mH] * p0234
[µF]) / (r0297 * r0313^2 * (r0377 - p0233) [mH] * p0234 [µF])
Linear motor connected to the high-frequency converter:
p1082 [m/min] <= 689.403 * p0315 * (root(p0316^2 * p0315^2 + 0.191865 * r0297^2 * (r0377 - p0233) [mH] * p0234
[µF]) / (r0297 * (r0377 - p0233) [mH] * p0234 [µF])
Rotary induction motor connected to the high-frequency converter:
p1082 [rpm] <= maximum (2.11383E5 / (r0313 * root((r0377 [mH] + r0382 [mH]) * p0234 [µF])); 0.6364 * r0297 *
p0311[rpm] / p0304)
2. Use a Voltage Protection Module (VPM) in conjunction with the function "Safe Torque Off" (p9601, p9801 - only for
synchronous motors).
When using a synchronous motor with VPM at the high-frequency converter, the following must apply:
p1082 [rpm] <= p0348 * (r0377 + p0233) / p0233
When a fault condition exists, the VPM short-circuits the motors. During the short-circuit, the pulses must be suppressed -
this means that the terminals for the function "Safe Torque Off" (STO) must be connected to the VPM.
When using a VPM, p0643 must be set to 1.
3. Activate the internal voltage protection (p1231 = 3, only for synchronous motors).
In so doing, the following hardware preconditions must be fulfilled:
- the infeed of the group must be capable of energy recovery (Active Line Module, Smart Line Module), and the energy
recovery power of the infeed must not be less than the maximum utilized S1 power of the synchronous motor.
- For Control Unit and infeed, a 24 V power supply other than that for the Motor Module must be used with the voltage
protection activated. The 24 V power supply of this Motor Module must be DC link buffered (e.g. CSM).
- a Braking Module with a correspondingly configured braking resistor must be available at the DC link.
- the synchronous motor must be short-circuit proof.
See also: p0643, p1231
207433
<location>Drive: Closed-loop control with encoder is not possible as the encoder has not
been unparked
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The changeover to closed-loop control with encoder is not possible as the encoder has not been unparked.
Remedy:
- check whether the encoder firmware supports the "parking" function (r0481.6 = 1).
- upgrade the firmware.
Note:
For long-stator motors (p3870.0 = 1), the following applies:
The encoder must have completed the unparking procedure (r3875.0 = 1) before a changeover can be made to closed-loop
control with encoder. The encoder is unparked using binector input p3876 = 0/1 signal and remains until a 0 signal in this
state.
207434
<location>Drive: It is not possible to change the direction of rotation with the pulses enabled
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Alarms
1016
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A drive data set was selected - with the pulses enabled - which has a different parameterized direction of rotation (p1821).
It is only possible to change the motor direction of rotation using p1821 when the pulses are inhibited.
Remedy:
- change over the drive data set with the pulses inhibited.
- ensure that the changeover to a drive data set does not result in the motor direction of rotation being changed (i.e. for these
drive data sets, the same value must be in p1821).
See also: p1821
207435
<location>Drive: Setting the ramp-function generator for sensorless vector control
Drive object:
HLA, HLA_840, VECTOR, VECTOR_AC
Message value:
Parameter: %1
Reaction:
Vector: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3)
Hla: OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
During operation with sensorless vector control (r1407.1) the ramp-function generator was stopped (p1141) or bypassed
(p1122). An internal setting command of the ramp-function generator output caused the set setpoint speed to be frozen
or was not able to be realized.
The drive is switched-on with flying restart activated (p1200), and at the same time the ramp-function generator is bypassed
(p1122).
Remedy:
- deactivate the holding command for the ramp-function generator (p1141).
- do not bypass the ramp-function generator (p1122).
- suppress the fault (p2101, p2119). This is necessary if the ramp-function generator is held using jogging and the speed
setpoint is simultaneously inhibited (r0898.6).
Note:
For sensorless vector control it is not practical to read in the main setpoint of the speed control via p1155 or p1160 (p0922).
In this case, the main setpoint should be injected before the ramp-function generator (p1070). The reason for this is that
the ramp-function generator output is automatically set when transitioning from closed-loop speed controlled into open-
loop speed controlled operation.
207439
<location>Drive: Function not supported
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC
Message value:
%1
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
The power unit does not support the selected function.
Fault value (r0949, interpret decimal):
1:
The function "Current controller dynamic response higher" is selected (p1810.11 = 1), however, this is not supported by the
power unit (r0192.27 = 0).
- firmware of the booksize power unit is not up-to-date.
- blocksize power unit was used.
2:
The function "Current controller dynamic response higher" is selected (p1810.11 = 1), however, this is not supported by the
safety technology without encoder (9506 = 1, 3).
3:
The function "DC link voltage compensation in the power unit" is selected (p1810.1 = 1), however, this is not supported by
the power unit (r0192.28 = 0).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1017
SINAMICS alarms
Remedy:
For fault value = 1:
- if necessary, upgrade the firmware of the booksize power unit to a later version (version >= 4.4).
Note:
If the firmware has already been automatically upgraded, then only a POWER ON (switch-off/switch-on) is required.
- Use a booksize power unit (version >= 4.4).
For fault value = 2:
- if an encoder with Safety position actual values sensing is available (r0458[0...2].19 = 1), reparameterize the encoderless
safety technology (p9506 = 1, 3) to safety technology with encoder (p9506 = 0).
For fault value = 1, 2:
- Deselect the function "Current controller dynamics higher" (p1810.11 = 0) and if required, set the current, speed and
position controller again or calculate (p0340 = 4).
For fault value = 3:
- if necessary, upgrade the firmware of the blocksize power unit to a later version (version >= 4.6).
- deselect the "DC link voltage compensation in the power unit" function (p1810.1 = 0).
See also: r0192, p1810, p9506
207440
<location>EPOS: Jerk time is limited
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The calculation of the jerk time Tr = max(p2572, p2573) / p2574 resulted in an excessively high value so that the jerk time
is internally limited to 1000 ms.
Note:
The alarm is also output if jerk limiting is not active.
Remedy:
- increase the jerk limiting (p2574).
- reduce maximum acceleration or maximum deceleration (p2572, p2573).
See also: p2572 (EPOS maximum acceleration), p2573 (EPOS maximum deceleration), p2574 (EPOS jerk limiting)
207441
<location>LR: Save the position offset of the absolute encoder adjustment
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The status of the absolute encoder adjustment has changed.
In order to permanently save the determined position offset (p2525) and the determined number of the drive data set
(p2733), they must be saved in a non-volatile fashion (p0971, p0977).
Possible causes:
- motor or encoder were replaced (applies to EQN and DQI).
- position-relevant parameters were changed.
- an encoder that was not adjusted was adjusted (save the project in a non-volatile fashion using "Copy RAM to ROM").
Note:
This message is not output when switching-on the axis after having first moved it in the switched-off state, as long as the
parameterizable monitoring window was not exited.
Remedy:
Readjust the encoder.
See also: p2507 (LR absolute encoder adjustment status), p2525 (LR encoder adjustment offset)
207442
<location>LR: Multiturn does not match the modulo range
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Alarms
1018
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Acknowledge:
IMMEDIATELY
Cause:
The ratio between the multiturn resolution and the modulo range (p2576) is not an integer number.
This results in the adjustment being set back, as the position actual value cannot be reproduced after switch-off/switch-on.
Remedy:
Make the ration between the multiturn resolution and the modulo range an integer number.
The ratio v is calculated as follows:
1. Motor encoder without position tracking
v = (p0421 * p2506 * p0433 * p2505) / (p0432 * p2504 * p2576)
2. Motor encoder with position tracking for the measuring gear
v = (p0412 * p2506 * p2505) / (p2504 * p2576)
3. Motor encoder with position tracking for the load gear
v = (p2721 * p2506 * p0433) / (p0432 * p2576)
4. Motor encoder with position tracking for the load and measuring gear
v = (p2721 * p2506) / p2576
5. Direct encoder without position tracking
v = (p0421 * p2506 * p0433) / (p0432 * p2576)
6. Direct encoder with position tracking for the measuring gear
v = (p0412 * p2506) / p2576
Note:
With position tracking, it is recommended that p0412 and p2721 are changed
See also: p0412, p0432, p0433, p2504, p2505, p2506, p2576, p2721
207443
<location>LR: Reference point coordinate not in the permissible range
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The reference point coordinate received when adjusting the encoder via connector input p2599 lies outside the half of the
encoder range and cannot be set as actual axis position.
Fault value (r0949, interpret decimal):
Maximum permissible value for the reference point coordinate.
Remedy:
Set the reference point coordinate to a lower value than specified in the fault value.
See also: p2598 (EPOS reference point coordinate signal source), p2599 (EPOS reference point coordinate value)
207446
<location>Load gear: Position tracking cannot be reset
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The position tracking cannot be reset.
Remedy:
Reset the position tracking as follows:
- select encoder commissioning (p0010 = 4).
- reset position tracking, position (p2720.2 = 1).
- deselect encoder commissioning (p0010 = 0).
Then acknowledge the fault and, if necessary, re-adjust the absolute encoder (p2507).
207447
<location>Load gear: Position tracking, maximum actual value exceeded
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, encoder data set: %2, drive data set: %3
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1019
SINAMICS alarms
Cause:
When the position tracking of the load gear is configured, the drive/encoder (motor encoder) identifies a maximum possible
absolute position actual value (r2723) that can no longer be represented within 32 bits.
Maximum value: p0408 * p2721 * 2^p0419
Fault value (r0949, interpret hexadecimal):
ccbbaa hex
aa = encoder data set
bb = component number
cc = drive data set
See also: p0408, p0419, p2721
Remedy:
- reduce the fine resolution (p0419).
- reduce the multiturn resolution (p2721).
See also: p0419, p2721
207448
<location>Load gear: Position tracking, linear axis has exceeded the maximum range
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Infeed: NONE
Servo: OFF1 (NONE, OFF2, OFF3)
Vector: OFF1 (NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
For a configured linear axis/no modulo axis, the currently effective motor encoder (encoder 1) has exceeded the maximum
possible traversing range.
For the configured linear axis, the maximum traversing range is defined to be 64x (+/- 32x) of p0421. It should be read in
p2721 and interpreted as the number of load revolutions.
Note:
Only the motor encoder in the currently effective drive data set is monitored here. The actual effective drive data set is
displayed in x = r0051 and the corresponding motor encoder is specified in in p0187[x].
Remedy:
The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset position tracking, position (p2720.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and the absolute encoder adjusted.
207449
<location>Load gear: Position tracking actual position outside tolerance window
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Infeed: NONE
Servo: OFF1 (NONE, OFF2, OFF3)
Vector: OFF1 (NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
1020
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
When switched off, the currently effective motor encoder was moved through a distance greater than was parameterized
in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder.
Note:
Only the motor encoder in the currently effective drive data set is monitored here. The actual effective drive data set is
displayed in x = r0051 and the corresponding motor encoder is specified in in p0187[x].
Fault value (r0949, interpret decimal):
Deviation (difference) to the last encoder position in increments of the absolute value after the measuring gear - if one is
being used. The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r2724.
See also: p2722 (Load gear position tracking tolerance window), r2724 (Load gear position difference)
Remedy:
Reset the position tracking as follows:
- select encoder commissioning (p0010 = 4).
- reset position tracking, position (p2720.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507).
See also: p0010, p2507
207450
<location>LR: Standstill monitoring has responded
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
After the standstill monitoring time (p2543) expired, the drive left the standstill window (p2542).
- position actual value inversion incorrectly set (p0410).
- standstill window set too small (p2542).
- standstill monitoring time set too low (p2543).
- position loop gain too low (p2538).
- position loop gain too high (instability/oscillation, p2538).
- mechanical overload.
- Connecting cable, motor/drive converter incorrect (phase missing, interchanged).
- when selecting motor identification, select tracking mode (BI: p2655[0] = 1 signal).
- when selecting function generator, select tracking mode (BI: p2655[0] = 1 signal) and deactivate position control
(BI:p2550 = 0 signal).
Remedy:
Check the causes and resolve.
207451
<location>LR: Position monitoring has responded
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
When the position monitoring time (p2545) expired, the drive had still not reached the positioning window (p2544).
- positioning window parameterized too small (p2544).
- position monitoring time parameterized too short (p2545).
- position loop gain too low (p2538).
- position loop gain too high (instability/oscillation, p2538).
- drive mechanically locked.
Remedy:
Check the causes and resolve.
207452
<location>LR: Following error too high
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1021
SINAMICS alarms
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The difference between the position setpoint position actual value (following error dynamic model, r2563) is higher than
the tolerance (p2546).
- the drive torque or accelerating capacity exceeded.
- position measuring system fault.
- encoder cable interrupted.
- position control sense incorrect.
- mechanical system locked.
- excessively high traversing velocity or excessively high position reference value (setpoint) differences
Remedy:
Check the causes and resolve.
207453
<location>LR: Position actual value preprocessing error
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
An error has occurred during the position actual value preprocessing.
Remedy:
Check the encoder for the position actual value preprocessing.
See also: p2502 (LR encoder assignment)
207454
<location>LR: Position actual value preprocessing does not have a valid encoder
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
One of the following problems has occurred with the position actual value preprocessing:
- an encoder is not assigned for the position actual value preprocessing (p2502 = 0).
- an encoder is assigned, but no encoder data set (p0187 = 99 or p0188 = 99 or p0189 = 99).
- an encoder an an encoder data set have been assigned, however, the encoder data set does not contain any encoder data
(p0400 = 0) or invalid data (e.g. p0408 = 0).
Remedy:
Check the drive data sets, encoder data sets and encoder assignment.
See also: p0187, p0188, p0189, p0400, p2502
207455
<location>EPOS: Maximum velocity limited
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The maximum velocity (p2571) is too high to correctly calculate the modulo correction.
Within the sampling time for positioning (p0115[5]), with the maximum velocity, a maximum of the half modulo length
must be moved through. p2571 was limited to this value.
Remedy:
- reduce the maximum velocity (p2571).
- increase the sampling time for positioning (p0115[5]).
207456
<location>EPOS: Setpoint velocity limited
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Alarms
1022
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Acknowledge:
NONE
Cause:
The actual setpoint velocity is greater than the parameterized maximum velocity (p2571) and is therefore limited.
Remedy:
- check the entered setpoint velocity.
- reduce the velocity override (CI: p2646).
- increase the maximum velocity (p2571).
- check the signal source for the externally limited velocity (CI: p2594).
207457
<location>EPOS: Combination of input signals illegal
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
An illegal combination of input signals that are simultaneously set was identified.
Alarm value (r2124, interpret decimal):
0: Jog 1 and jog 2 (p2589, p2590).
1: Jog 1 or jog 2 and direct setpoint input/MDI (p2589, p2590, p2647).
2: Jog 1 or jog 2 and start referencing (p2589, p2590, p2595).
3: Jog 1 or jog 2 and activate traversing task (p2589, p2590, p2631).
4: Direct setpoint input/MDI and starting referencing (p2647, p2595).
5: Direct setpoint input/MDI and activate traversing task (p2647, p2631).
6: Start referencing and activate traversing task (p2595, p2631).
Remedy:
Check the appropriate input signals and correct.
207458
<location>EPOS: Reference cam not found
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
After starting the search for reference, the axis moved through the maximum permissible distance to search for the
reference cam without actually finding the reference cam.
Remedy:
- check the "reference cam" binector input (BI: p2612).
- check the maximum permissible distance to the reference cam (p2606).
- if axis does not have any reference cam, then set p2607 to 0.
See also: p2606 (EPOS search for reference reference cam maximum distance), p2607 (EPOS search for reference reference
cam present), p2612 (EPOS search for reference reference cam)
207459
<location>EPOS: No zero mark
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
After leaving the reference cam, the axis has traversed the maximum permissible distance between the reference cam and
zero mark without finding the zero mark.
Remedy:
- check the encoder regarding the zero mark
- check the maximum permissible distance between the reference cam and zero mark (p2609).
- use an external encoder zero mark (equivalent zero mark) (p0495).
See also: p0495, p2609
207460
<location>EPOS: End of reference cam not found
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1023
SINAMICS alarms
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
During the search for reference, when the axis reached the zero mark it also reached the end of the traversing range without
detecting an edge at the binector input "reference cam" (BI: p2612).
Maximum traversing range: -2147483648 [LU] ... -2147483647 [LU]
Remedy:
- check the "reference cam" binector input (BI: p2612).
- repeat the search for reference.
See also: p2612 (EPOS search for reference reference cam)
207461
<location>EPOS: Reference point not set
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
When starting a traversing block/direct setpoint input, a reference point is not set (r2684.11 = 0).
Remedy:
Reference the system (search for reference, flying referencing, set reference point).
207462
<location>EPOS: Selected traversing block number does not exist
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A traversing block selected via binector input p2625 ... p2630 was started via binector input p2631 = 0/1 edge "Activate
traversing task".
- the number of the started traversing block is not contained in p2616[0...n].
- the started traversing block is suppressed.
Alarm value (r2124, interpret decimal):
Number of the selected traversing block that is also not available.
Remedy:
- correct the traversing program.
- select an available traversing block number.
207463
<location>EPOS: External block change not requested in the traversing block
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
For a traversing block with the block change enable CONTINUE_EXTERNAL_ALARM, the external block change was not
requested.
Alarm value (r2124, interpret decimal):
Number of the traversing block.
Remedy:
Resolve the reason as to why the edge is missing at binector input (BI: p2632).
207464
<location>EPOS: Traversing block is inconsistent
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
1024
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The traversing block does not contain valid information.
Alarm value (r2124, interpret decimal):
Number of the traversing block with invalid information.
Remedy:
Check the traversing block and where relevant, take into consideration alarms that are present.
207465
<location>EPOS: Traversing block does not have a subsequent block
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
There is no subsequent block in the traversing block.
Alarm value (r2124, interpret decimal):
Number of the traversing block with the missing subsequent block.
Remedy:
- parameterize this traversing block with the block change enable END.
- parameterize additional traversing blocks with a higher block number and for the last block, using the block change enable
END.
207466
<location>EPOS: Traversing block number assigned a multiple number of times
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The same traversing block number was assigned a multiple number of times.
Alarm value (r2124, interpret decimal):
Number of the traversing block that was assigned a multiple number of times.
Remedy:
Correct the traversing blocks.
207467
<location>EPOS: Traversing block has illegal task parameters
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The task parameter in the traversing block contains an illegal value.
Alarm value (r2124, interpret decimal):
Number of the traversing block with an illegal task parameter.
Remedy:
Correct the task parameter in the traversing block.
207468
<location>EPOS: Traversing block jump destination does not exist
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
In a traversing block, a jump was programmed to a non-existent block.
Alarm value (r2124, interpret decimal):
Number of the traversing block with a jump destination that does not exist.
Remedy:
- correct the traversing block.
- add the missing traversing block.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1025
SINAMICS alarms
207469
<location>EPOS: Traversing block < target position < software limit switch minus
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the traversing block the specified absolute target position lies outside the range limited by the software limit switch minus.
Alarm value (r2124, interpret decimal):
Number of the traversing block with illegal target position.
Remedy:
- correct the traversing block.
- change software limit switch minus (CI: p2578, p2580).
207470
<location>EPOS: Traversing block> target position > software limit switch plus
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the traversing block the specified absolute target position lies outside the range limited by the software limit switch plus.
Alarm value (r2124, interpret decimal):
Number of the traversing block with illegal target position.
Remedy:
- correct the traversing block.
- change software limit switch plus (CI: p2579, p2581).
207471
<location>EPOS: Traversing block target position outside the modulo range
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the traversing block the target position lies outside the modulo range.
Alarm value (r2124, interpret decimal):
Number of the traversing block with illegal target position.
Remedy:
- in the traversing block, correct the target position.
- change the modulo range (p2576).
207472
<location>EPOS: Traversing block ABS_POS/ABS_NEG not possible
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the traversing block the positioning mode ABS_POS or ABS_NEG were parameterized with the modulo correction not
activated.
Alarm value (r2124, interpret decimal):
Number of the traversing block with the illegal positioning mode.
Remedy:
Correct the traversing block.
207473
<location>EPOS: Beginning of traversing range reached
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Alarms
1026
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
When traversing, the axis has moved to the traversing range limit.
Remedy:
Move away in the positive direction.
207474
<location>EPOS: End of traversing range reached
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
When traversing, the axis has moved to the traversing range limit.
Remedy:
Move away in the negative direction.
207475
<location>EPOS: Target position < start of traversing range
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The target position for relative traversing lies outside the traversing range.
Remedy:
Correct the target position.
207476
<location>EPOS: Target position > end of the traversing range
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The target position for relative traversing lies outside the traversing range.
Remedy:
Correct the target position.
207477
<location>EPOS: Target position < software limit switch minus
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the actual traversing operation, the target position is less than the software limit switch minus.
Remedy:
- correct the target position.
- change software limit switch minus (CI: p2578, p2580).
See also: p2578 (EPOS software limit switch minus signal source), p2580 (EPOS software limit switch minus), p2582 (EPOS
software limit switch activation)
207478
<location>EPOS: Target position > software limit switch plus
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the actual traversing operation, the target position is greater than the software limit switch plus.
Remedy:
- correct the target position.
- change software limit switch plus (CI: p2579, p2581).
See also: p2579 (EPOS software limit switch plus signal source), p2581 (EPOS software limit switch plus), p2582 (EPOS
software limit switch activation)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1027
SINAMICS alarms
207479
<location>EPOS: Software limit switch minus reached
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The axis is at the position of the software limit switch minus. An active traversing block was interrupted.
Remedy:
- correct the target position.
- change software limit switch minus (CI: p2578, p2580).
See also: p2578 (EPOS software limit switch minus signal source), p2580 (EPOS software limit switch minus), p2582 (EPOS
software limit switch activation)
207480
<location>EPOS: Software limit switch plus reached
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The axis is at the position of the software limit switch plus. An active traversing block was interrupted.
Remedy:
- correct the target position.
- change software limit switch plus (CI: p2579, p2581).
See also: p2579 (EPOS software limit switch plus signal source), p2581 (EPOS software limit switch plus), p2582 (EPOS
software limit switch activation)
207481
<location>EPOS: Axis position < software limit switch minus
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The actual position of the axis is less than the position of the software limit switch minus.
Remedy:
- correct the target position.
- change software limit switch minus (CI: p2578, p2580).
See also: p2578 (EPOS software limit switch minus signal source), p2580 (EPOS software limit switch minus), p2582 (EPOS
software limit switch activation)
207482
<location>EPOS: Axis position > software limit switch plus
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The actual position of the axis is greater than the position of the software limit switch plus.
Remedy:
- correct the target position.
- change software limit switch plus (CI: p2579, p2581).
See also: p2579 (EPOS software limit switch plus signal source), p2581 (EPOS software limit switch plus), p2582 (EPOS
software limit switch activation)
207483
<location>EPOS: Travel to fixed stop clamping torque not reached
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The fixed stop in the traversing block was reached without the clamping torque/clamping force having been achieved.
Alarms
1028
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- check the maximum torque-generating current (r1533).
- check the torque limits (p1520, p1521).
- check the power limits (p1530, p1531).
- check the BICO interconnections of the torque limits (p1522, p1523, p1528, p1529).
207484
<location>EPOS: Fixed stop outside the monitoring window
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF3 (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
In the "fixed stop reached" state, the axis has moved outside the defined monitoring window (p2635).
Remedy:
- check the monitoring window (p2635).
- check the mechanical system.
207485
<location>EPOS: Fixed stop not reached
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
In a traversing block with the task FIXED STOP, the end position was reached without detecting a fixed stop.
Remedy:
- check the traversing block and locate the target position further into the workpiece.
- check the "fixed stop reached" control signal (p2637).
- if required, reduce the maximum following error window to detect the fixed stop (p2634).
207486
<location>EPOS: Intermediate stop missing
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the modes "traversing blocks" or "direct setpoint input/MDI" at the start of motion, the binector input "no intermediate
stop/intermediate stop" (BI: p2640) did not have a 1 signal.
Remedy:
Connect a 1 signal to the binector input "no intermediate stop/intermediate stop" (BI: p2640) and re-start motion.
See also: p2640 (EPOS intermediate stop (0 signal))
207487
<location>EPOS: Reject traversing task missing
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the modes "traversing blocks" or "direct setpoint input/MDI" at the start of motion, the binector input "do not reject
traversing task/reject traversing task" (BI: p2641) does not have a 1 signal.
Remedy:
Connect a 1 signal to the binector input "do not reject traversing task/reject traversing task" (BI: p2641) and restart motion.
See also: p2641 (EPOS reject traversing task (0 signal))
207488
<location>EPOS: Relative positioning not possible
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1029
SINAMICS alarms
Cause:
In the mode "direct setpoint input/MDI", for continuous transfer (p2649 = 1) relative positioning was selected (BI: p2648 =
0 signal).
Remedy:
Check the control.
207489
<location>EPOS: Reference point correction outside the window
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
For the function "flying referencing" the difference between the measured position at the measuring probe and the
reference point coordinate lies outside the parameterized window.
Remedy:
- check the mechanical system.
- check the parameterization of the window (p2602).
207490
<location>EPOS: Enable signal withdrawn while traversing
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
- for a standard assignment, another fault may have occurred as a result of withdrawing the enable signals.
- the drive is in the "switching on inhibited" state (for a standard assignment).
Remedy:
- set the enable signals or check the cause of the fault that first occurred and then result (for a standard assignment).
- check the assignment to enable the basic positioning function.
207491
<location>EPOS: STOP cam minus reached
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF3
Acknowledge:
IMMEDIATELY
Cause:
A 0 signal was detected at binector input p2569, i.e. the STOP cam minus was actuated.
For a positive traversing direction, the STOP cam minus was reached - i.e. the wiring of the STOP cam is incorrect.
See also: p2569 (EPOS STOP cam minus)
Remedy:
- leave the STOP cam minus in the positive traversing direction and return the axis to the valid traversing range.
- check the wiring of the STOP cam.
207492
<location>EPOS: STOP cam plus reached
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF3
Acknowledge:
IMMEDIATELY
Cause:
A 0 signal was detected at binector input p2570, i.e. the STOP cam plus was reached.
For a negative traversing direction, the STOP cam plus was reached - i.e. the wiring of the STOP cam is incorrect.
See also: p2570 (EPOS STOP cam plus)
Remedy:
- leave the STOP cam plus in the negative traversing direction and return the axis to the valid traversing range.
- check the wiring of the STOP cam.
207493
<location>LR: Overflow of the value range for position actual value
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Alarms
1030
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The value range (-2147483648 ... 2147483647) for the position actual value representation was exceeded.
When the overflow occurs, the "referenced" or "adjustment absolute measuring system" status is reset.
Fault value (r0949, interpret decimal):
1: The position actual value (r2521) has exceeded the value range.
2: The encoder position actual value Gn_XIST2 (r0483) or the absolute value after the load gear (r2723) has exceeded the
value range.
3: The maximum encoder value times the factor to convert the absolute position (r0483 and/or r2723) from increments to
length units (LU) has exceeded the value range for displaying the position actual value.
Note:
For a linear encoder, the following must be maintained:
- p0407 * p2503 / (2^p0418*10^7) < 1
- p0407 * p2503 / (2^p0419*10^7) < 1
Remedy:
If required, reduce the traversing range or position resolution (p2506).
Increase the fine resolution of absolute position actual value (p0419).
Note for fault value = 3:
If the value for the maximum possible absolute position (LU) is greater than 4294967296, then it is not possible to make an
adjustment due to an overflow.
For rotary encoders, the maximum possible absolute position (LU) is calculated as follows:
1. Motor encoder without position tracking
p2506 * p0433 * p2505 / (p0432 * p2504)
p2506 * p0433 * p2505 * p0421 / (p0432 * p2504) for multiturn encoders
2. Motor encoder with position tracking for measuring gear
p2506 * p0412 * p2505 / p2504
3. Motor encoder with position tracking for load gear
p2506 * p2721 * p0433 / p0432
4. Motor encoder with position tracking for load and measuring gear
p2506 * p2721
5. Direct encoder without position tracking
p2506 * p0433 / p0432
p2506 * p0433 * p0421 / p0432 for multiturn encoders
6. Direct encoder with position tracking for measuring gear
p2506 * p0412
207494
<location>LR: Drive Data Set changeover in operation
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A Drive Data Set changeover (DDS) with a change of the mechanical relationships (p2503 ... 2506), direction of rotation
(p1821) or the encoder assignment (p2502) was requested in operation.
Note:
DDS: Drive Data Set
Remedy:
To changeover the drive data set, initially, exit the "operation" mode.
207495
<location>LR: Reference function interrupted
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1031
SINAMICS alarms
Cause:
An activated reference function (reference mark search or measuring probe evaluation) was interrupted.
Possible causes:
- an encoder fault has occurred (Gn_ZSW.15 = 1).
- position actual value was set during an activated reference function.
- simultaneously activate reference mark search and measuring probe evaluation (BI: p2508 and BI: p2509 = 1 signal).
- activated reference function (reference mark search or measuring probe evaluation) was deactivated (BI: p2508 and BI:
p2509 = 0 signal).
- the input terminal for the measuring probe is not set.
Remedy:
- check the causes and resolve.
- reset the control (BI: p2508 and BI: p2509 = 0 signal) and activate the requested function.
- set the input terminal for the measuring probe (p0488, p0489 or p2517, p2518).
207496
<location>EPOS: Enable not possible
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
It is not possible to enable the basic positioner because at least one condition is missing.
Alarm value (r2124, interpret decimal):
1: EPOS enable missing (BI: p2656).
2: Position actual value, valid feedback signal missing (BI: p2658).
See also: p2656 (EPOS enable basic positioner), p2658 (EPOS position actual value valid feedback signal)
Remedy:
Check the corresponding missing condition (binector input, signal source).
207497
<location>LR: Position setting value activated
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
While the binector input p2514 has a 1 signal, the position actual value is set to the value received via connector input
p2515. A possible system deviation cannot be corrected.
Remedy:
Not necessary.
The alarm is automatically withdrawn for binector input p2514 = 0 signal.
207498
<location>LR: Measuring probe evaluation not possible
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
When evaluating the measuring probe, an error occurred.
Alarm value (r2124, interpret decimal):
6:
The input terminal for the measuring probe is not set.
4098:
Error when initializing the measuring probe.
4100:
The measuring pulse frequency is too high.
> 50000:
The measuring clock cycle is not a multiple integer of the position controller clock cycle.
Alarms
1032
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
Deactivate the measuring probe evaluation (BI: p2509 = 0 signal).
For alarm value = 6:
Set the input terminal for the measuring probe (p0488, p0489 or p2517, p2518).
For alarm value = 4098:
Check the Control Unit hardware.
For alarm value = 4100:
Reduce the frequency of the measuring pulses at the measuring probe.
For alarm value > 50000:
Set the clock cycle ratio of the measuring clock cycle to the position controller clock cycle to an integer multiple.
To do this, the currently effective measuring clock cycle can be determined from the alarm value as follows:
Tmeas [125 µs] = alarm value - 50000
With PROFIBUS, the measuring clock cycle corresponds to the PROFIBUS clock cycle (r2064[1]).
Without PROFIBUS, the measuring clock cycle is an internal cycle time that cannot be influenced.
207499
<location>EPOS: Reversing cam approached with the incorrect traversing direction
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF3
Acknowledge:
IMMEDIATELY
Cause:
The reversing cam MINUS was approached in the positive traversing direction or the reversing cam PLUS was approached
in the negative traversing direction.
See also: p2613 (EPOS search for reference reversing cam minus), p2614 (EPOS search for reference reversing cam plus)
Remedy:
- check the wiring of the reversing cam (BI: p2613, BI: p2614).
- check the traversing direction to approach the reversing cam.
207500
<location>Drive: Power unit data set PDS not configured
Drive object:
All objects
Message value:
Drive data set: %1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
Only for controlled line supply infeed/regenerative feedback units:
The power unit data set was not configured - this means that a data set number was not entered into the drive data set.
Fault value (r0949, interpret decimal):
Drive data set number of p0185.
Remedy:
The index of the power unit data set associated with the drive data set should be entered into p0185.
See also: p0185 (Power unit Data Set (PDS) number)
207501
<location>Drive: Motor Data Set MDS not configured
Drive object:
All objects
Message value:
Drive data set: %1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
Only for power units:
The motor data set was not configured - this means that a data set number was not entered into the associated drive data
set.
Fault value (r0949, interpret decimal):
The fault value includes the drive data set number of p0186.
Remedy:
The index of the motor data set associated with the drive data set should be entered into p0186.
See also: p0186 (Motor Data Sets (MDS) number)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1033
SINAMICS alarms
207502
<location>Drive: Encoder Data Set EDS not configured
Drive object:
All objects
Message value:
Drive data set: %1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
Only for power units:
The encoder data set was not configured - this means that a data set number was not entered into the associated drive data
set.
Fault value (r0949, interpret decimal):
The fault value includes the drive data set number of p0187, p0188 and p0189.
The fault value is increased by 100 * encoder number (e.g. for p0189: Fault value 3xx with xx = data set number).
Remedy:
The index of the encoder data set associated with the drive data set should be entered into p0187 (1st encoder), p0188 (2nd
encoder) and p0189 (3rd encoder).
207503
<location>EPOS: STOP cam approached with the incorrect traversing direction
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: NONE (OFF1, OFF2, OFF3)
Vector: NONE
Acknowledge:
IMMEDIATELY
Cause:
The STOP cam MINUS was approached in the positive traversing direction or the STOP cam PLUS was approached in the
negative traversing direction.
Remedy:
- check the wiring of the STOP cam (BI: p2569, BI: p2570).
- check the traversing direction to approach the STOP cam.
207504
<location>Drive: Motor data set is not assigned to a drive data set
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A motor data set is not assigned to a drive object.
All of the existing motor data sets in the drive data sets must be assigned using the MDS number (p0186[0...n]). There must
be at least as many drive data sets as motor data sets.
Alarm value (r2124, interpret decimal):
Number of the motor data set that has not been assigned.
Remedy:
In the drive data sets, assign the non-assigned motor data set using the MDS number (p0186[0...n]).
- check whether all of the motor data sets are assigned to drive data sets.
- if required, delete superfluous motor data sets.
- if required, set up new drive data sets and assign to the corresponding motor data sets.
See also: p0186 (Motor Data Sets (MDS) number)
207505
<location>EPOS: Task fixed stop not possible in the U/f/SLVC mode
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
In the U/f/SLVC mode, an attempt was made to execute a traversing block with the "fixed stop" task. This is not possible.
Alarm value (r2124, interpret decimal):
Number of the traversing block with an illegal task parameter.
Alarms
1034
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- check the traversing block and change the task.
- change the open-loop/closed-loop control mode (p1300).
See also: p1300, p2621
207506
<location>EPOS: check BICO interconnection between EPOS and position controller
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The BICO interconnections to transfer setpoints between EPOS and LR (position control) have not been set, although the
BICO interconnections to transfer the fine resolutions have been set.
Remedy:
1. Disconnect BICO interconnections for the fine resolutions (CI: p2694 = 0, CI: p2695 = 0).
2. Set BICO interconnections for the setpoints (CI: p2530 = r2665, CI: p2531 = r2666).
3. Set BICO interconnections for the fine resolutions (CI: p2694 = r2696, CI: p2695 = r2697).
See also: p2530, p2531, r2665, r2666, p2694, p2695, r2696, r2697
207507
<location>EPOS: reference point cannot be set
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
After the reference point correction, the position setpoint lies outside the traversing range limits.
Remedy:
- optimize the position controller.
- due to a possible position controller deviation, reference point coordinate p2599 should not be directly placed at the
traversing range limits.
207509
<location>Drive: Component assignment missing
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
A Drive Data Set (DDS) is assigned to a Motor Data Set (MDS) or Encoder Data Set (EDS) that does not have a component
number.
Fault value (r0949, interpret decimal):
nnmmmxxyyy
nn: Number of the MDS/EDS.
mmm: Parameter number of the missing component number.
xx: Number of the DDS that is assigned to the MDS/EDS.
yyy: Parameter number that references the MDS/EDS.
Example:
p0186[7] = 5: DDS 7 is assigned MDS 5.
p0131[5] = 0: There is no component number set in MDS 5.
Alarm value = 0513107186
Remedy:
In the drive data sets, no longer assign MDS/EDS using p0186, p0187, p0188, p0189 or set a valid component number.
See also: p0131, p0141, p0142, p0186, p0187, p0188, p0189
207510
<location>Drive: Identical encoder in the drive data set
Drive object:
All objects
Message value:
%1
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1035
SINAMICS alarms
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
More than one encoder with identical component number is assigned to a single drive data set. In one drive data set, it is
not permissible that identical encoders are operated together.
Fault value (r0949, interpret decimal):
1000 * first identical encoder + 100 * second identical encoder + drive data set.
Example:
Fault value = 1203 means:
In drive data set 3, the first (p0187[3]) and second encoder (p0188[3]) are identical.
Remedy:
Assign the drive data set to different encoders.
See also: p0141, p0187, p0188, p0189
207511
<location>Drive: Encoder used a multiple number of times
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
Each encoder may only be assigned to one drive and within a drive must - in each drive data set - either always be encoder
1, always encoder 2 or always encoder 3. This unique assignment has been violated.
Fault value (r0949, interpret decimal):
The two parameters in coded form, that refer to the same component number.
First parameter:
Index: First and second decimal place (99 for EDS, not assigned DDS)
Parameter number: Third decimal place (1 for p0187, 2 for p0188, 3 for p0189, 4 for EDS not assigned DDS)
Drive number: Fourth and fifth decimal place
Second parameter:
Index: Sixth and seventh decimal place (99 for EDS, not assigned DDS)
Parameter number: Eighth decimal place (1 for p0187, 2 for p0188, 3 for p0189, 4 for EDS, not assigned DDS)
Drive number: Ninth and tenth decimal place
See also: p0141
Remedy:
Correct the double use of a component number using the two parameters coded in the fault value.
207512
<location>Drive: Encoder data set changeover cannot be parameterized
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
Using p0141, a changeover of the encoder data set is prepared that is illegal. In this firmware release, an encoder data set
changeover is only permitted for the components in the actual topology.
Fault value (r0949, interpret decimal):
Incorrect EDS data set number.
See also: p0187, p0188, p0189
Remedy:
Every encoder data set must be assigned its own dedicated DRIVE-CLiQ socket. The component numbers of the encoder
interfaces (p0141) must have different values within a drive object.
The following must apply:
p0141[0] not equal to p0141[1] not equal to ... not equal to p0141[n]
207514
<location>Drive: Data structure does not correspond to the interface module
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Alarms
1036
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The interface mode "SIMODRIVE 611 universal" was set (p2038 = 1) and the data structure does not correspond to this mode.
The following settings are possible, depending on the number of data sets:
Number of DDS/MDS (p0180/p0130): p0186
1/1: p0186[0] = 0
2/2: p0186[0] = 0, p0186[1] = 1
4/4: p0186[0] = 0, p0186[1] = 1, p0186[2] = 2, p0186[3] = 3
8/8: p0186[0] = 0, p0186[1] = 1, p0186[2] = 2 ... p0186[7] = 7
16/16: p0186[0] = 0, p0186[1] = 1, p0186[2] = 2 ... p0186[15] = 15
32/32: p0186[0] = 0, p0186[1] = 1, p0186[2] = 2 ... p0186[31] = 31
2/1: p0186[0, 1] = 0
4/2: p0186[0, 1] = 0, p0186[1, 2] = 1
8/4: p0186[0, 1] = 0, p0186[1, 2] = 1, p0186[3, 4] = 2, p0186[5, 6] = 3
16/8: p0186[0, 1] = 0, p0186[1, 2] = 1, p0186[3, 4] = 2 ... p0186[14, 15] = 7
32/16: p0186[0, 1] = 0, p0186[1, 2] = 1, p0186[3, 4] = 2 ... p0186[30, 31] = 15
4/1: p0186[0, 1, 2, 3] = 0
8/2: p0186[0, 1, 2, 3] = 0, p0186[4, 5, 6, 7] = 1
16/4: p0186[0, 1, 2, 3] = 0, p0186[4, 5, 6, 7] = 1, p0186[8, 9, 10, 11] = 2, p0186[12, 13, 14, 15] = 3
32/8: p0186[0, 1, 2, 3] = 0, p0186[4, 5, 6, 7] = 1, p0186[8, 9, 10, 11] = 2 ... p0186[28, 29, 30, 31] = 7
8/1: p0186[0...7] = 0
16/2: p0186[0...7] = 0, p0186[8...15] = 1
32/4: p0186[0...7] = 0, p0186[8...15] = 1, p0186[16...23] = 2, p0186[24...31] = 3
16/1: p0186[0...15] = 0
32/2: p0186[0...15] = 0, p0186[16...31] = 1
32/1: p0186[0...31] = 0
9/2: p0186[0...7] = 0, p0186[8] = 1
10/2: p0186[0...7] = 0, p0186[8, 9] = 1
12/2: p0186[0...7] = 0, p0186[8...11] = 1
See also: p0180, p0186, p2038
Remedy:
- check the data structure according to the possible settings mentioned in the cause.
- check the interface mode (p2038).
207515
<location>Drive: Power unit and motor incorrectly connected
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
A power unit (via PDS) was assigned to a motor (via MDS) in a drive data set that is not connected in the target topology.
It is possible that a motor has not been assigned to the power unit (p0131).
Fault value (r0949, interpret decimal):
Number of the incorrectly parameterized drive data set.
Remedy:
- assign the drive data set to a combination of motor and power unit permitted by the target topology.
- adapt the target topology.
- if required, for a missing motor, recreate the component (drive Wizard).
See also: p0121, p0131, p0185, p0186
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1037
SINAMICS alarms
207516
<location>Drive: Re-commission the data set
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The assignment between the drive data set and motor data set (p0186) or between the drive data set and the encoder data
set was modified (p0187). This is the reason that the drive data set must re-commissioned.
Fault value (r0949, interpret decimal):
Drive data set to be re-commissioned.
Remedy:
Commission the drive data set specified in the fault value (r0949).
207517
<location>Drive: Encoder data set changeover incorrectly parameterized
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
In at least two drive data sets (DDS), the same motor data set (MDS) is assigned different encoder data sets (EDS) for the
motor encoder. In various DDSs, it is not permissible for an MDS to have different motor encoders.
The following parameterization therefore results results in an error:
DDS0: p0186[0] = 0, p0187[0] = 0
DDS1: p0186[1] = 0, p0187[1] = 1
Fault value (r0949, interpret decimal):
The lower 16 bits indicate the first DDS. The upper 16 bits indicate the second DDS.
Remedy:
Create two MDS with the same motor data in order to operate one motor with different motor encoders.
Example:
DDS0: p0186[0] = 0, p0187[0] = 0
DDS1: p0186[1] = 1, p0187[1] = 1
207518
<location>Drive: Motor data set changeover incorrectly parameterized
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The system has identified that two motor data sets were incorrectly parameterized.
Parameter r0313 (calculated from p0314, p0310, p0311), r0315 and p1982 may only have different values if the motor data
sets are assigned different motors. p0827 is used to assign the motors and/contactors.
It is not possible to toggle between motor data sets.
Fault value (r0949, interpret hexadecimal):
xxxxyyyy:
xxxx: First DDS with assigned MDS, yyyy: Second DDS with assigned MDS
Remedy:
Correct the parameterization of the motor data sets.
207519
<location>Drive: Motor changeover incorrectly parameterized
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Alarms
1038
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
With the setting p0833.0 = 1, a motor changeover via the application is selected. This is the reason that p0827 must have
different values in the appropriate motor data set.
Alarm value (r2124, interpret hexadecimal):
xxxxyyyy:
xxxx: First MDS, yyyy: Second MDS
Remedy:
- parameterize the appropriate motor data sets differently (p0827).
- select the setting p0833.0 = 0 (motor changeover via the drive).
207520
<location>Drive: Motor cannot be changed over
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The motor cannot be changed over.
Alarm value (r2124, interpret decimal):
1:
The contactor for the motor that is presently active cannot be opened, because for a synchronous motor, the speed (r0063)
is greater than the speed at the start of field weakening (p0348). As long as r0063 > p0348, the current in the motor does
not decay in spite of the pulses being suppressed.
2:
The "contactor opened" feedback signal was not detected within 1 s.
3:
The "contactor closed" feedback signal was not detected within 1 s.
Remedy:
For alarm value = 1:
Set the speed lower than the speed at the start of field weakening (r0063 < p0348).
For alarm value = 2, 3:
Check the feedback signals of the contactor involved.
207530
<location>Drive: Drive Data Set DDS not present
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The selected drive data set is not available (p0837 > p0180). The drive data set was not changed over.
See also: p0180, p0820, p0821, p0822, p0823, p0824, r0837
Remedy:
- select the existing drive data set.
- set up additional drive data sets.
207531
<location>Drive: Command Data Set CDS not present
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The selected command data set is not available (p0836 > p0170). The command data set was not changed over.
See also: p0810, p0811, p0812, p0813, r0836
Remedy:
- select the existing command data set.
- set up additional command data sets.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1039
SINAMICS alarms
207532
<location>Drive: Encoderless control not commissioned
Drive object:
SERVO, SERVO_840, SERVO_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
Encoderless operation was set as fault response to encoder faults (p0491). However, the encoderless control has not yet
been commissioned.
Note:
In at least one drive data set (DDS) the load moment of inertia is zero (p1498 = 0).
See also: p0491 (Motor encoder fault response ENCODER)
Remedy:
Commission the encoderless control.
Perform the following steps to facilitate a simple setting:
- the speed controller must have already been optimized for operation with encoder (e.g. the optimized P gain is in p1460).
- set the load moment of inertia (p1498, e.g. using function module "Moment of inertia estimator/OBT" or "AST" for
SINUMERIK).
- set the current setpoint for open-loop controlled operation without encoder (p1612) for static loads (e.g. vertical axis
without weight compensation, preset value plus torque-generating current (r0077) for the base load).
- set the speed controller.
p1470 = optimized p1460/16 for sampling time = 125 µs (P gain)
p1470 = optimized p1460/25 for sampling time = 62.5 µs (P gain)
p1470 = optimized p1460/30 for sampling time = 31.25 µs (P gain)
p1472 = 140 ms (integral time, default value).
p1451 = 10 ms (speed actual value smoothing encoderless operation).
- set encoderless operation current reduction: p0642 = 2*p0318/p0640 (for a result > 100%, 100% should be entered).
- if the motor moment of inertia changes significantly, then the moment of inertia estimator should be activated using
function module "Moment of inertia estimator/OBT".
- save the set values in a non-volatile fashion (copy RAM to ROM).
- test the function while moving with p4642 = 1 (encoder fault, test function).
Note:
The following must be set if Safety Extended Functions with encoder in the 1-encoder system are enabled:
- No STOP A after encoder fault for 1-encoder Safety (p9516.4 = 1).
- Transition time STOP F to STOP B is long enough to brake the motor (p9555).
If the result is not satisfactory, then encoderless operation must be manually optimized (e.g. temporarily switch over to
encoderless operation using p1300 = 20).
Information about the moment of inertia estimator and encoderless operation is provided in the following reference:
SINAMICS S120 Function Manual Drive Functions
207541
<location>Drive: Data set changeover not possible
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The selected drive data set changeover and the assigned motor changeover are not possible and are not carried out.
For synchronous motors, the motor contactor may only be switched for actual speeds less than the speed at the start of
field weakening (r0063 < p0348).
See also: r0063, p0348
Remedy:
Reduce the speed to below the speed at the start of field weakening (r0063 < p0348).
207550
<location>Drive: Not possible to reset encoder parameters
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Alarms
1040
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
When carrying out a factory setting (e.g. using p0970 = 1), it was not possible to reset the encoder parameters. The encoder
parameters are directly read out of the encoder via DRIVE-CLiQ.
Alarm value (r2124, interpret decimal):
Component number of the encoder involved.
Remedy:
- repeat the operation.
- check the DRIVE-CLiQ connection.
207551
<location>Drive encoder: No commutation angle information
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC
Message value:
Fault cause: %1, drive data set: %2
Reaction:
Servo: OFF2 (IASC/DCBRK)
Hla: OFF2
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The commutation angle information is missing. This means that synchronous motors cannot be controlled (closed-loop
control)
Fault value (r0949, interpret decimal):
yyyyxxxx dec: yyyy = fault cause, xxxx = drive data set
yyyy = 1 dec:
The motor encoder used does not supply an absolute commutation angle.
yyyy = 2 dec:
The selected ratio of the measuring gear does not match the motor pole pair number.
Remedy:
For fault cause = 1:
- check the encoder parameterization (p0404).
- use an encoder with track C/D, EnDat interface of Hall sensors.
- use an encoder with sinusoidal A/B track for which the motor pole pair number (r0313) multiplied by the gear ratio (p0432/
p0433) is less than the encoder pulse number (p0408) - or is an integer multiple of the encoder pulse number (p0408).
- activate the pole position identification routine (p1982 = 1).
For fault cause = 2:
- the quotient of the pole pair number divided by the ratio of the measuring gear must be an integer number: (p0314 *
p0433) / p0432.
Note:
For operation with track C/D, this quotient must be less than 8.
See also: p0402, p0404, p0432, p0433
207551
<location>Drive encoder: No commutation angle information
Drive object:
VECTOR, VECTOR_AC
Message value:
Fault cause: %1, drive data set: %2
Reaction:
OFF2 (IASC/DCBRK)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The commutation angle information is missing. This means that synchronous motors cannot be controlled (closed-loop
control)
Fault value (r0949, interpret decimal):
yyyyxxxx dec: yyyy = fault cause, xxxx = drive data set
yyyy = 1 dec:
The motor encoder used does not supply an absolute commutation angle.
yyyy = 2 dec:
The selected ratio of the measuring gear does not match the motor pole pair number.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1041
SINAMICS alarms
Remedy:
For fault cause = 1:
- check the encoder parameterization (p0404).
- use an encoder with track C/D, EnDat interface of Hall sensors.
- use an encoder with sinusoidal A/B track for which the motor pole pair number (r0313) multiplied by the gear ratio (p0432/
p0433) is less than the encoder pulse number (p0408) - or is an integer multiple of the encoder pulse number (p0408).
- activate the pole position identification routine (p1982 = 1) for motor encoders without absolute position information.
Then, using an encoder adjustment (p1990), the angular commutation offset should be determined.
For fault cause = 2:
- the quotient of the pole pair number divided by the ratio of the measuring gear must be an integer number: (p0314 *
p0433) / p0432.
Note:
For operation with track C/D, this quotient must be less than 8.
See also: p0402, p0404, p0432, p0433
207552
<location>Drive encoder: Encoder configuration not supported
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
Fault cause: %1, component number: %2, encoder data set: %3
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Vector: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Hla: OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The requested encoder configuration is not supported. Only bits may be requested in p0404 that are signaled as being
supported by the encoder evaluation in r0456.
Fault value (r0949, interpret decimal):
ccccbbaa hex: cccc = fault cause, bb = component number, aa = encoder data set
cccc = 1: encoder sin/cos with absolute track (is supported by SME25).
cccc = 3: Square-wave encoder (this is supported by SMC30).
cccc = 4: sin/cos encoder (this is supported by SMC20, SMI20, SME20, SME25).
cccc = 10: DRIVE-CLiQ encoder (is supported by DQI).
cccc = 12: sin/cos encoder with reference mark (this is supported by SME20).
cccc = 15: Commutation with zero mark for separately excited synchronous motors with VECTORMV.
cccc = 23: Resolver (this is supported by SMC10, SMI10).
cccc = 65535: Other function (compare r0456 and p0404).
See also: p0404, r0456
Remedy:
- check the encoder parameterization (p0400, p0404).
- use the matching encoder evaluation (r0456).
207553
<location>Drive encoder: Sensor Module configuration not supported
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
Encoder data set: %1, first incorrect bit: %2, incorrect parameter: %3
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Vector: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Hla: OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
1042
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The Sensor Module does not support the requested configuration.
For incorrect p0430 (cc = 0), the following applies:
- in p0430 (requested functions), at least 1 bit was set that is not set in r0458 (supported functions) (exception: Bit 19, 28,
29, 30, 31).
- p1982 > 0 (pole position identification requested), but r0458.16 = 0 (pole position identification not supported).
For incorrect p0437 (cc = 1), the following applies:
- in p0437 (requested functions), at least 1 bit was set that is not set in r0459 (supported functions).
Fault value (r0949, interpret hexadecimal):
ddccbbaa hex
aa: encoder data set number
bb: first incorrect bit
cc: incorrect parameter
cc = 0: incorrect parameter is p0430
cc = 1: incorrect parameter is p0437
cc = 2: incorrect parameter is r0459
cc = 3: incorrect parameter is p0454
dd: reserved (always 0)
Remedy:
- check the encoder parameterization (p0430, p0437, p0454).
- check the pole position identification routine (p1982).
- use the matching encoder evaluation (r0458, r0459).
See also: p0430, p0437, r0458, r0459, p1982
207555
<location>Drive encoder: Configuration position tracking
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1, encoder data set: %2, drive data set: %3, fault cause: %4
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Vector: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Hla: OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1043
|