SINUMERIK 840D sl, SINAMICS S120. Alarms. Diagnostics Manual (2020) - page 14

 

  Index      Manuals     SINUMERIK 840D sl, SINAMICS S120. Alarms. Diagnostics Manual (2020)

 

Search            copyright infringement  

 

   

 

    

 

Content      ..     39      40      41      42     ..

 

 

 

SINUMERIK 840D sl, SINAMICS S120. Alarms. Diagnostics Manual (2020) - page 14

 

 

SINAMICS alarms
- check whether there is a DRIVE-CLiQ communication error between the Control Unit and the Motor Module involved and,
if required, carry out a diagnostics routine for the faults identified.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- Terminal Module 54F (TM54F).
- onboard F-DI (only CU310-2).
- PROFIsafe.
- machine control panel.
For message value = 7003, 7004:
- if required, adapt the settings for the times for Tdp, Ti and To - or increase the monitoring clock cycle p9500 (rule Tdp = 2
x n x p9500, n= 1, 2, 3, ...).
See also: p9300 (SI Motion monitoring clock cycle (Motor Module)), p9500 (SI Motion monitoring clock cycle (Control Unit))
201712
<location>SI Motion P1 (CU): Defect in F-IO processing
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
906
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
When cross checking and comparing the two monitoring channels, the drive detected a difference between parameters or
results of the F-IO processing and initiated a STOP F. One of the monitoring functions no longer reliably functions - i.e. safe
operation is no longer possible.
The safety message C01711 with message value 0 is also displayed due to initiation of STOP F.
If at least one monitoring function is active, the safety message C01701 "SI Motion: STOP B initiated" is output after the
parameterized timer has expired.
Message value (r9749, interpret decimal):
Number of the cross-compared data that resulted in this message.
1: SI discrepancy monitoring time inputs (p10002, p10102).
2: SI acknowledgment internal event input terminal (p10006, p10106).
3: SI STO input terminal (p10022, p10122).
4: SI SS1 input terminal (p10023, p10123).
5: SI SS2 input terminal (p10024, p10124).
6: SI SOS input terminal (p10025, p10125).
7: SI SLS input terminal (p10026, p10126).
8: SI SLS_Limit(1) input terminal (p10027, p10127).
9: SI SLS_Limit(2) input terminal (p10028, p10128).
10: SI Safe State signal selection (p10039, p10139).
11 SI F-DI input mode (p10040, p10140).
12: SI F-DO 0 signal sources (p10042, p10142).
13: Different states for static inactive signal sources (p10006, p10022 ... p10031).
14: SI discrepancy monitoring time outputs (p10002, p10102).
15: SI acknowledgment internal event (p10006, p10106).
16: SI test sensor feedback signal test mode selected for test stop (p10046, p10146, p10047, p10147).
17: SI delay time for test stop at DOs (p10001).
18 ... 25: SI test sensor feedback signal (p10046, p10146, p10047, p10147). Expected state of internal readback signal,
generated from the selected test stop mode.
26 ... 33: SI test sensor feedback signal (p10046, p10146, p10047, p10147). Expected state of external readback signal,
generated from the selected test stop mode.
34 ... 41: SI test sensor feedback signal (p10046, p10146, p10047, p10147). Expected state of second internal readback
signal, generated from the selected test stop mode.
42: Internal data for processing the second internal readback signal, generated from the selected test stop mode (p10047,
p10147).
43: Internal data for processing the internal readback signal, generated from the selected test stop mode (p10047, p10147).
44: Internal data for processing the external readback signal, generated from the selected test stop mode (p10047, p10147).
45: Internal data for initialization state of test stop mode, dependent upon test stop parameters.
46: SI digital inputs debounce time (p10017, p10117)
47: Selection F-DI for PROFIsafe (p10050, p10150)
48: Screen form of the F-DIs used (p10006, p10022 ... p10031).
49: SI SDI positive input terminal (p10030, p10130).
50: SI SDI negative input terminal (p10031, p10131).
51: SI SLP input terminal (p10032, p10132).
52: SI SLP select input terminal (p10033, p10133).
53: Internal data for retraction logic (p10009, p100109).
54: SI F-DI for retraction SLP (p10009, p100109).
Remedy:
- check parameterization in the parameters involved and correct if required.
- ensure equality by copying the SI data to the second channel and then carry out an acceptance test.
- check monitoring clock cycle in p9500 and p9300 for equality.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- onboard F-DI (only CU310-2).
- PROFIsafe.
- machine control panel.
See also: p9300 (SI Motion monitoring clock cycle (Motor Module)), p9500 (SI Motion monitoring clock cycle (Control Unit))
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
907
SINAMICS alarms
201714
<location>SI Motion P1 (CU): Safely-Limited Speed exceeded
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The drive has moved faster than that specified by the velocity limit value (p9531). The drive is stopped as a result of the
configured stop response (p9563).
Message value (r9749, interpret decimal):
100: SLS1 exceeded.
200: SLS2 exceeded.
300: SLS3 exceeded.
400: SLS4 exceeded.
1000: Encoder limit frequency exceeded.
Remedy:
- check the traversing/motion program in the control.
- check limits for SLS and if required adapt accordingly (p9531).
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- Terminal Module 54F (TM54F).
- onboard F-DI (only CU310-2).
- PROFIsafe.
- machine control panel.
Note:
SI: Safety Integrated
SLS: Safely-Limited Speed / SG: Safely reduced speed
See also: p9531, p9563
201715
<location>SI Motion P1 (CU): Safely-Limited Position exceeded
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The axis has moved past a parameterized position that is monitored by the "SLP" function.
Message value (r9749, interpret decimal):
10: SLP1 violated.
20: SLP2 violated.
Remedy:
- check the traversing/motion program in the control.
- check the limits for "SLP" function and if required, adapt (p9534, p9535).
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
Prerequisite:
- deselect "SLP" function and retract the axis into the permitted position range.
Carry out a safe acknowledgment using one of the following options:
- Terminal Module 54F (TM54F).
- onboard F-DI (only CU310-2).
- PROFIsafe.
- machine control panel.
Note:
SI: Safety Integrated
SLP: Safely-Limited Position / SE: Safe software limit switches
See also: p9534, p9535
201716
<location>SI Motion P1 (CU): Tolerance for safe motion direction exceeded
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Alarms
908
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The tolerance for the "safe motion direction" function was exceeded. The drive is stopped as a result of the configured stop
response (p9566).
Message value (r9749, interpret decimal):
0: Tolerance for the "safe motion direction positive" function exceeded.
1: Tolerance for the "safe motion direction negative" function exceeded.
Remedy:
- check the traversing/motion program in the control.
- check the tolerance for "SDI" function and if required, adapt (p9564).
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
Prerequisite:
- deselect the "SDI" function and if required select again.
Carry out a safe acknowledgment using one of the following options:
- Terminal Module 54F (TM54F).
- onboard F-DI (only CU310-2).
- PROFIsafe.
- machine control panel.
Note:
SDI: Safe Direction (safe motion direction)
SI: Safety Integrated
See also: p9564, p9565, p9566
201717
<location>SI Motion P1 (CU): SLA limit exceeded
Drive object:
HLA, SERVO, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The acceleration limit for the "Safely-Limited Acceleration" function was exceeded. The drive is stopped as a result of the
configured stop response (p9579).
Message value (r9749, interpret decimal):
0: The monitoring of the coarsely resolved acceleration has violated the acceleration limit.
1: The monitoring of the finely resolved acceleration and possibly filtered acceleration has violated the acceleration limit.
Remedy:
- check the traversing/motion program in the control.
- check the acceleration limit for the "SLA" function and if required, adapt (p9578).
- carry out a safe acknowledgment.
For message value = 0:
Analyze the causes using r9714[0] and r9714[3].
For message value = 1:
Analyze the causes using r9789[0], r9789[1] and r9789[2].
Note:
SI: Safety Integrated
SLA: Safely-Limited Acceleration
See also: p9578, p9579
201730
<location>SI Motion P1 (CU): Reference block for dynamic Safely-Limited Speed invalid
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
909
SINAMICS alarms
Cause:
The reference block transferred via PROFIsafe is negative.
A reference block is used to generate a referred velocity limit value based on the reference quantity "Velocity limit value
SLS1" (p9531[0]).
The drive is stopped as a result of the configured stop response (p9563[0]).
Message value (r9749, interpret decimal):
requested, invalid reference block.
Remedy:
In the PROFIsafe telegram, input data S_SLS_LIMIT_IST must be corrected.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- PROFIsafe.
Note:
SI: Safety Integrated
SLS: Safely-Limited Speed / SG: Safely reduced speed
201745
<location>SI Motion P1 (CU): Checking braking torque for the brake test
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
POWER ON (IMMEDIATELY)
Cause:
The scaling of the brake torque for the brake test can be changed using parameter p2003.
An acceptance test must be carried out again for the braking test. This determines whether the braking test is still carried
out with the correct braking torque.
Remedy:
- carry out a POWER ON (switch-off/switch-on) for all components.
- repeat the acceptance test for the safe brake test if the brake test is used.
See also: p2003
201750
<location>SI Motion P1 (CU): Hardware fault safety-relevant encoder
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The encoder that is used for the safety-relevant motion monitoring functions signals a hardware fault.
Message value (r9749, interpret decimal):
Encoder status word 1, encoder status word 2 that resulted in the message.
Remedy:
- check the encoder connection.
- replace encoder.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- Terminal Module 54F (TM54F).
- onboard F-DI (only CU310-2).
- PROFIsafe.
- machine control panel.
Note regarding encoder replacement for a third-party motor:
The serial number of the encoder must be copied in order to acknowledge this safety message.
This can be realized using p0440 = 1 or p1990 = 1.
201751
<location>SI Motion P1 (CU): Effectivity test fault safety-relevant encoder
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
910
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The DRIVE-CLiQ encoder for safe motion monitoring signals an error for the effectivity tests.
Message value (r9749, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy:
- check the encoder connection.
- replace encoder.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- Terminal Module 54F (TM54F).
- onboard F-DI (only CU310-2).
- PROFIsafe.
- machine control panel.
201752
<location>SI Motion P1 (CU): reference position invalid
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The transferred reference position is invalid.
Message value (r9749, interpret decimal):
1: It is not possible to directly transfer the reference position (p9573=89).
2: It is not possible to transfer the reference position into the motion.
Remedy:
- unpark axis/encoder.
- acknowledge encoder fault
- deactivate gearbox stage switchover.
- when referencing via the Safety Control Channel (SCC), enable the function "Referencing via SCC" (p9501.27/9301.27).
This message can be acknowledged as follows:
- motion monitoring functions integrated in the drive: Via Terminal Module 54F (TM54F) or PROFIsafe
201770
<location>SI Motion P1 (CU): Discrepancy error of the failsafe inputs/outputs
Drive object:
SERVO, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The failsafe digital inputs/digital outputs (F-DI/F-DO) show a different state longer than that parameterized in p10002/
p10102 - or too many switching operations took place within a monitoring cycle p10002.
Fault value (r0949, interpret bitwise binary):
yyyyxxxx bin
xxxx: Discrepancy error for failsafe digital inputs (F-DI).
Bit 0: Discrepancy error for F-DI 0
Bit 1: Discrepancy error for F-DI 1
yyyy: Discrepancy error for failsafe digital outputs (F-DO).
Bit 0: Discrepancy error for F-DO 0
Note:
If several discrepancy errors occur consecutively, then this message is only signaled for the first error that occurs.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
911
SINAMICS alarms
Remedy:
- check the wiring of the F-DI (contact problems).
- if the wiring is correct, and for example there is no wire breakage, then a check must be made as to whether the switching
frequency at F-DI is too high and must therefore be reduced (switching pulses must have a longer time between them). The
time interval between each signal edge at an F-DI must be at least equal to the discrepancy time before the input is switched
again.
Note:
This message can be acknowledged via F-DI or PROFIsafe (safe acknowledgment).
Discrepancy errors of an F-DI can only be acknowledged if safe acknowledgment was carried out once after the cause of the
error was resolved (p10006, acknowledgment via PROFIsafe, extended message acknowledgment). As long as safety
acknowledgment was not carried out, the corresponding F-DI stays in the safe state internally.
When the "Extended message acknowledgment" function (p9507.0) is active, the following applies:
If the F-DI assigned for STO or SS1 is in a failsafe state due to a discrepancy error, then when deselecting via this F-DI, safe
acknowledgment can no longer be executed.
Sets the discrepancy time for fast switching operations at the F-DIs:
For fast switching operations at the failsafe digital inputs (F-DI), it may be necessary to adapt the discrepancy time to the
switching frequency:
- the period of a cyclic switching pulse must be less than half of the discrepancy time (if necessary, round down).
- the time between two fast switching pulses should be longer than the discrepancy time (if necessary, round up).
- the discrepancy time must be at least p9500 (it must always be rounded-down or rounded-up to an integer multiple of the
SI sampling time p9500).
If a debounce time has been parameterized (p10017 > 0), then the shortest possible discrepancy time is directly specified
using the debounce time.
- the period of a cyclic switching pulse must be less than half of the discrepancy time p10017 (if necessary, round down).
- the time between two fast switching pulses should be longer than the discrepancy time+p10017 (if necessary, round up).
- the discrepancy time must be at least p9500 The debounce time must always be set less than the discrepancy time.
Example:
If the SI sampling cycle is 12 ms and the switching frequency is 110 ms (p10017 = 0), the maximum discrepancy time which
can be set is as follows:
p10002 <= 110/2 ms - 12 ms = 43 ms --> rounded-off, the following is obtained p10002 <= 36 ms
Since the discrepancy time can only be accepted as a whole SI sampling time, the value will need to be rounded up or down
to a whole SI sampling time value if it is not an exact integer multiple of an SI sampling time.
Basic secondary condition to set the discrepancy time:
The discrepancy time of the F-DIs must always be longer than the longest SI sampling time of all drives that use Safety
Integrated with TM54F (p9780/p9500).
Note:
F-DI: Failsafe Digital Input
F-DO: Failsafe Digital Output
201772
<location>SI Motion P1 (CU): Test stop for failsafe digital outputs running
Drive object:
SERVO, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The forced checking procedure (test stop) for the failsafe digital inputs is currently in progress.
Remedy:
The alarm is automatically withdraw after successfully ending or canceling (when a fault condition occurs) the test stop.
Note:
F-DO: Failsafe Digital Output
201773
<location>SI Motion P1 (CU): Test stop failsafe digital output error
Drive object:
SERVO, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
912
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A fault has occurred on processor 1 during the forced checking procedure (test stop) of the failsafe digital output.
Fault value (r0949, interpret hexadecimal):
RRRVWXYZ hex:
R: Reserved.
V: Actual state of the DO channel concerned (see X) on processor 1 (corresponds to the states read back from the hardware,
bit 0 = DO 0, bit 1 = DO 1, etc.).
W: Required state of the DO channel concerned (see X, bit 0 = DO 0, bit 1 = DO 1, etc.).
X: DO channels involved, which indicate an error (bit 0 = DO 0, bit 1 = DO 1, etc.).
Y: Reason for the test stop fault.
Z: State of the test stop in which the fault has occurred.
Y: Reason for the test stop fault
Y = 1: Processor 2 in incorrect test stop state (internal fault).
Y = 2: Expected states of the DOs were not fulfilled (CU305: readback via DI 22 / CU240 readback DI 5).
Y = 3: Incorrect timer state on processor 1 (internal fault)
Y = 4: Expected states of the diag DOs were not fulfilled (CU305: internal readback on processor 2).
Y = 5: Expected states of the second diag DOs were not fulfilled (CU305: internal readback on processor 1).
X and V indicate the DI or Diag-DO state dependent upon the reason for the fault (2, 4 or 5).
In the event of multiple test stop faults, the first one that occurred is shown.
Z: Test stop state and associated test actions
Z = 0 ... 3: Synchronization phase of test stop between processor 1 and processor 2 no switching operations
Z = 4: DO + OFF and DO - OFF
Z = 5: Check to see if states are as expected
Z = 6: DO + ON and DO - ON
Z = 7: Check to see if states are as expected
Z = 8: DO + OFF and DO - ON
Z = 9: Check to see if states are as expected
Z = 10: DO + ON and DO - OFF
Z = 11: Check to see if states are as expected
Z = 12: DO + OFF and DO - OFF
Z = 13: Check to see if states are as expected
Z = 14: End of test stop
Diag expected states in table format:
Test stop state: Expectation Mode 1 / Mode 2 / Mode 3 / Mode 4
5: 0/-/-/1
7: 0/-/-/0
9: 0/-/-/0
11: 1/-/-/1
13: 0/-/-/1
Second diag expected states in table format:
Test stop state: Expectation Mode 1 / Mode 2 / Mode 3 / Mode 4
5: -/-/-/1
7: -/-/-/0
9: -/-/-/1
11: -/-/-/0
13: -/-/-/1
DI expected states in table format:
Test stop state: Expectation Mode 1 / Mode 2 / Mode 3 / Mode 4
5: -/1/1/-
7: -/0/0/-
9: -/0/1/-
11: -/0/1/-
13: -/1/1/-
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
913
SINAMICS alarms
Example:
Fault F01773 (P1) is signaled with fault value = 0001_0127 and fault F30773 (P2) is signaled with fault value 0000_0127.
This means that in state 7 (Z = 7) the state of the external readback signal was not set correctly (Y = 2) after DO-0 (X = 1)
was switched to ON/ON.
Fault value 0001_0127 indicates that 0 was expected (W = 0) and 1 (V = 1) was read back from the hardware.
Fault value 0000_0127 on the processor 2 indicates that the states were as expected.
In the case of fault F30773, W and V are always identical; a value of 0 always means that 0 was expected at the readback
input but was not present on processor 1.
Remedy:
Check the wiring of the failsafe digital output (F-DO) and restart the test stop.
Note:
- the fault is withdrawn if the test stop is successfully completed.
- in the event of multiple test stop faults, the first one that occurred is shown. Once the test stop has been restarted the next
queued test stop fault will be signaled (if there is one).
F-DO: Failsafe Digital Output
201774
<location>SI Motion P1 (CU): Test stop for failsafe digital outputs required
Drive object:
SERVO, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The time set in p10003 for the forced checking procedure (test stop) for the failsafe digital outputs has been exceeded. A
new forced checking procedure is required.
After the next time the forced checking procedure is selected, the message is withdrawn and the monitoring time is reset.
Note:
- this message does not result in a safety stop response.
- the test must be performed within a defined, maximum time interval (p10003, maximum of 8760 hours) in order to
comply with the requirements as laid down in the standards for timely fault detection and the conditions to calculate the
failure rates of safety functions (PFH value). Operation beyond this maximum time period is permissible if it can be ensured
that the forced checking procedure is performed before persons enter the hazardous area and who are depending on the
safety functions correctly functioning.
See also: p10003
Remedy:
Carry out the forced checking procedure for the digital outputs.
The signal source to select the forced checking procedure is set via binector input p10007.
Note:
F-DO: Failsafe Digital Output
See also: p10007
201780
<location>SBT When selected, the brake is closed
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Following brakes are closed: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Cause:
When selecting the brake test or starting the brake test, not all of the brakes were open.
Alarm value (r2124, interpret binary):
Bit 0 = 1:
The internal brake is closed.
Bit 1 = 1:
The external brake is closed (p10230.5, p10235.5, p10202).
Note:
The alarm is also issued, if a brake has not been configured in p10202.
SBT: Safe Brake Test
See also: p10202, p10230, p10235
Alarms
914
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
Open all brakes and reselect the brake test (p10230.0, p10235.0).
201781
<location>SBT brake opening time exceeded
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Cause:
The maximum time (11 s) to open the brake during the brake test was exceeded.
Possible causes:
- during the brake test the drive went into a fault condition, and therefore the brake was closed by the drive.
- for an external brake, the feedback signal "Brake closed" was signaled too long (p10230.5, p10235).
Alarm value (r2124, interpret binary):
Bit 0 = 1:
Internal brake was not able to be opened.
Bit 1 = 1:
External brake was not able to be opened.
Note:
SBT: Safe Brake Test
Remedy:
- carry out a safe acknowledgment.
- restart the brake test (p10230.1, p10235.1).
See also: p10230, p10235
201782
<location>SBT brake test incorrect control
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Cause:
The brake test was canceled as a result of incorrect control.
Alarm value (r2124, interpret binary):
Alarm value 0:
The brake test was canceled as a result of a fault (brake opening time or brake closing time exceeded).
Bit 0:
The safe brake test was canceled by resetting the brake test selection.
Bit 1:
The safe brake test was canceled by resetting the brake test start.
Bit 2:
The brake, which was selected at the start of the brake test, has not been configured in p10202.
When starting the brake test, as a result of the test top selection, brake 1 is not configured as internal brake.
There is a brake test configuration error. In this case, alarm A01785 is also output.
Note:
SBT: Safe Brake Test
See also: p10202
Remedy:
- check parameterization of the brake test (p10202).
- check as to whether alarm A01785 is present, and if so, evaluate.
- carry out a safe acknowledgment.
- if required, restart the brake test.
201783
<location>SBT brake closing time exceeded
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
915
SINAMICS alarms
Reaction:
NONE
Acknowledge:
NONE
Cause:
The maximum time (11 s) to close the brake during the brake test was exceeded.
Alarm value (r2124, interpret binary):
Bit 0 = 1:
Internal brake was not able to be closed.
Bit 1 = 1:
External brake was not able to be closed.
Note:
SBT: Safe Brake Test
Remedy:
- When using an external brake, check that the feedback signal "brake closed" is correctly interconnected with the control
word of the brake test (p10230.5, p10235.5).
- When using an internal brake with external feedback signal, check whether the feedback signal is correctly interconnected
with the extended brake control.
- carry out a safe acknowledgment.
- restart the brake test (p10230.1, p10235.1).
201784
<location>SBT brake test canceled with fault
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The safe brake test was canceled as a result of a fault.
Alarm value (r2124, interpret binary):
Bit 17 = 1: fault in the brake test sequence (cause, see bits 0 ... 10).
Bit 18 = 1: the internal brake is closed. It must be open when the external brake is tested (p10202).
Bit 19 = 1: the external brake is closed. It must be open when the internal brake is tested (p10202).
Bit 20 = 1: not all brakes are open (p10202).
Bit 21 = 1: axis position during the brake test not valid due to parking axis.
Bit 22 = 1: internal software error.
Bit 23 = 1: the permissible position range of the axis was violated with the brake closed (p10212/p10222).
Bit 24 = 1: the tested internal brake was opened while the brake test was active.
Bit 25 = 1: the tested external brake was opened while the brake test was active.
Bit 26 = 1: during the active brake test, the test torque left its tolerance bandwidth (20 %).
Cause for alarm value bit 17:
Bit 0 = 1: operation when selecting the brake test not enabled (r0899.2 = 0).
Bit 1 = 1: external fault occurred (e.g. the brake test that has already started is canceled by the user).
Bit 2 = 1: when selecting the brake test a brake is closed.
Bit 3 = 1: when determining the load torque a brake is closed.
Bit 4 = 1: A fault has occurred with stop response (e.g. OFF1, OFF2 or OFF3) - or the pulse enable was withdrawn (e.g. STO
selected or operation no longer enabled).
Bit 5 = 1: when selecting the brake test the axis speed setpoint is too high.
Bit 6 = 1: the actual speed (r0063) of the axis is too high (e.g. brake does not hold during the brake test).
Bit 7 = 1: Incorrect speed controller mode (e.g. encoderless speed control or U/f operation).
Bit 8 = 1: closed-loop control not enabled or function generator active.
Bit 9 = 1: control does not switch over to the brake test (e.g. because PI speed control has not been parameterized).
Bit 10 = 1: torque limit reached (r1407.7, r1408.8).
Note:
SBT: Safe Brake Test
Alarms
916
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- remove the fault cause.
- carry out a safe acknowledgment.
- if required, restart the brake test.
For bit 17 = 1 with bit 6 = 1 or bit 23 = 1:
If the brake closing time of the motor holding brake (p1217) has been set too low, then at the start of the brake test, the
brake is closed too late. The brake closing time should be adapted (p1217).
201785
<location>SBT brake test configuration error
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Error when parameterizing the brake test.
In this configuration, the brake test cannot be started or cannot be started without error.
Alarm value (r2124, interpret decimal):
1:
No motion monitoring functions have been enabled.
2:
Two internal brakes were configured (p10202).
4:
No internal brakes were configured (p10202).
8:
The brake test is configured for an internal brake, however the safety brake control is not enabled (p9602/p9802).
Note:
From firmware version 5.1, SBT without SBC is also permitted for the internal brake.
16:
The safe brake test and Safety without encoder are simultaneously enabled (p9306/p9506). This is not permissible.
32:
The Safe Brake Test and vector U/f control is enabled. The safe brake test is not possible in this control mode.
Note:
SBC: Safe Brake Control
SBT: Safe Brake Test
Remedy:
Check parameterization of the brake test.
201786
<location>SCC signal source changed
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The signal source in p10235 or p10250 was changed.
The new signal source is effective immediately.
Note:
SCC: Safety Control Channel
See also: p10235 (SI Safety Control Channel control word S_STW3B), p10250 (SI Safety Control Channel control word
S_STW1B)
Remedy:
Acknowledge fault.
201787
<location>SBT motor type different
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF2
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
917
SINAMICS alarms
Acknowledge:
IMMEDIATELY
Cause:
The motor type set for the safe brake test (p10204) does not match the motor type set via the function module (r0108.12).
Remedy:
Adapt the motor type set for the safe brake test.
Note:
All of the parameters for the brake test, whose unit depends on the motor type, should be checked.
See also: p10204, p10209
201788
<location>SI: Automatic test stop waits for STO deselection via motion monitoring functions
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The automatic test stop (forced checking procedure) was not able to be carried out after powering up.
Possible causes:
- the STO function is selected via safe motion monitoring functions.
- a safety message is present, that resulted in a STO.
Note:
STO: Safe Torque Off
Remedy:
- deselect STO via safe motion monitoring functions.
- remove the cause of the safety messages and acknowledge the messages.
Note:
The automatic test stop is performed after removing the cause.
201789
<location>SI: Automatic test stop and brake test when test stop is selected not permitted
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The parameterization of the automatic test stop (p9507.6/p9307.6) and the brake test when a test stop is selected (p10203
= 2) are not permissible.
The test stop is not automatically carried out when the powering up.
Remedy:
- correct the parameter assignment.
- set p10203 not equal to 2 or deactivate the automatic test stop.
Note:
A warm restart or POWER ON is required to carry out the automatic test stop.
201794
<location>SI Motion: check modulo value for safe position via PROFIsafe
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
When parameterizing the modulo value for safe position via PROFIsafe (p9505) the position actual value can jump when the
range that can be represented overflows.
Range that can be represented:
- 32-bit value: +/- 2048 revolutions
- 16-bit value: +/- 2048 revolutions (depending on p9574)
Alarms
918
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
Correct the parameter assignment.
Set p9505 to 2^n revolutions - and to complete revolutions (i.e. a multiple of 360 °).
Note:
This alarm can be hidden for the case that the possible position actual value jump can be tolerated for the particular
application, or does not represent a problem; for example because the parameterized modulo range fits "almost as integer
number" in the range of +/- 2048 revolutions that can be represented.
To re-parameterize the alarm to "NO REPORT", it is not permissible that the alarm is present. As a consequence, the following
sequence is required for the re-parameterization:
- correct p9505 to "2^n".
- re-parameterize the alarm using p2118 and p2119.
- set p9505 back to the required value.
201795
<location>SI Motion P1 (CU): Wait time after exiting the safe pulse cancellation expired
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
After exiting safe pulse cancellation, within the wait time of 5 seconds, encoderless actual value sensing was not able to be
activated for the extended functions without selection.
A change is again made into the "safe pulse cancellation" state.
Remedy:
- check missing enable signals, which prevent the drive control from being commissioned (r0046).
- evaluate possible fault messages of the encoderless actual value sensing and remove.
201796
<location>SI P1 (CU): Wait for communication
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The drive waits for communication to be established to execute the safety-relevant motion monitoring functions.
Note:
STO is active in this state.
Alarm value (r2124, interpret decimal):
1: Wait for communication to be established to SINUMERIK.
2: Wait for communication to be established to TM54F.
3: Wait for communication to be established to PROFIsafe F-Host.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
919
SINAMICS alarms
Remedy:
If, after a longer period of time, the message is not automatically withdrawn, the following checks have to be made as
appropriate:
For communication with SINUMERIK, the following applies:
- check any other PROFIBUS messages/signals present and remove their cause.
- check that assignment of the axes on the higher-level control to the drives in the drive unit is correct.
- check enable signal of the safety-relevant motion monitoring functions for the corresponding axis on the higher-level
control and if required, set it.
For communication with TM54F, the following applies:
- check any other messages/signals present for DRIVE-CLiQ communication with the TM54F and remove their cause.
- check the setting of p10010. All the drive objects controlled by the TM54F must be listed.
For communication with PROFIsafe F-Host, the following applies:
- check any other PROFIsafe communication messages/signals present and evaluate them.
- check the operating state of the F-Host.
- check the communication connection to the F Host.
- check the communication connection to the Motor Module/Hydraulic Module. It must be ensured that when the Control
Unit powers up, the Motor Module/Hydraulic Module is connected and at the latest is also switched-on with the Control Unit.
Otherwise, if the Motor Module/Hydraulic Module is subsequently inserted or switched on, a POWER ON must be performed
at the Control Unit.
Note:
STO: Safe Torque Off
See also: p9601, p9801, p10010
201797
<location>SI Motion P1 (CU): Axis not safely referenced
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The standstill position saved before switching off does not match the actual position determined at switch-on.
Message value (r9749, interpret decimal):
1: Axis not safely referenced.
2: User agreement missing.
Remedy:
If safe automatic referencing is not possible the user must issue a user agreement for the new position using the softkey.
This mean that this position is then designated as safety-relevant.
Note:
SI: Safety Integrated
201798
<location>SI Motion P1 (CU): Test stop for motion monitoring functions running
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The forced checking procedure (test stop) for the safe motion monitoring functions is currently in progress.
Remedy:
Not necessary.
The message is automatically withdrawn when the test stop has been completed.
Note:
SI: Safety Integrated
201799
<location>SI Motion P1 (CU): Acceptance test mode active
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Alarms
920
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The acceptance test mode is active.
This means the following:
- the setpoint velocity limiting is deactivated (r9733).
- the standard limit switches are deactivated during the acceptance test for function SLP (SE) (for EPOS internal, otherwise
via r10234).
- for safety functions with SINUMERIK, the following applies: The POWER ON signals of the safety-relevant motion
monitoring functions can be acknowledged during the acceptance test using the acknowledgment functions of the higher-
level control.
Remedy:
Not necessary.
The message is withdrawn when exiting the acceptance test mode.
Note:
SI: Safety Integrated
SLP: Safely-Limited Position / SE: Safe software limit switches
201800
<location>DRIVE-CLiQ: Hardware/configuration error
Drive object:
All objects
Message value:
%1
Reaction:
Infeed: NONE (OFF1, OFF2)
Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Vector: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Hla: NONE (OFF1, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
A DRIVE-CLiQ connection fault has occurred.
Fault value (r0949, interpret decimal):
100 ... 107:
Communication via DRIVE-CLiQ socket X100 ... X107 has not been switched to cyclic operation. The cause may be an
incorrect structure or a configuration that results in an impossible bus timing.
10:
Loss of the DRIVE-CLiQ connection. The cause may be, for example, that the DRIVE-CLiQ cable was withdrawn from the
Control Unit or as a result of a short-circuit for motors with DRIVE-CLiQ. This fault can only be acknowledged in cyclic
communication.
11:
Repeated faults when detecting the connection. This fault can only be acknowledged in cyclic communication.
12:
A connection was detected but the node ID exchange mechanism does not function. The reason is probably that the
component is defective. This fault can only be acknowledged in cyclic communication.
Remedy:
For fault value = 100 ... 107:
- ensure that the DRIVE-CLiQ components have the same firmware versions.
- avoid longer topologies for short current controller sampling times.
For fault value = 10:
- check the DRIVE-CLiQ cables at the Control Unit.
- remove any short-circuit for motors with DRIVE-CLiQ.
- carry out a POWER ON.
For fault value = 11:
- check the electrical cabinet design and cable routing for EMC compliance
For fault value = 12:
- replace the component involved.
201839
<location>DRIVE-CLiQ diagnostics: cable fault to the component
Drive object:
All objects
Message value:
Component number: %1
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
921
SINAMICS alarms
Reaction:
NONE
Acknowledge:
NONE
Cause:
The fault counter (r9936[0...199]) to monitor the DRIVE-CLiQ connections/cables has been incremented.
Alarm value (r2124, interpret decimal):
Component number.
Note:
The component number specifies the component whose feeder cable from the direction of the Control Unit is faulted.
The alarm is automatically withdrawn after 5 seconds, assuming that no other data transfer error has occurred.
See also: r9936 (DRIVE-CLiQ diagnostic error counter connection)
Remedy:
- check the corresponding DRIVE-CLiQ cables.
- check the electrical cabinet design and cable routing for EMC compliance
201840
<location>SMI: Component found without motor data
Drive object:
All objects
Message value:
Component number: %1
Reaction:
NONE
Acknowledge:
NONE
Cause:
An SMI/DQI without motor data has been found (e.g. SMI installed as replacement part).
Alarm value (r2124, interpret decimal):
Component number from target topology.
Remedy:
1. Download the SMI/DQI data (motor/encoder data) from the data backup again (p4690, p4691).
2. Carry out a POWER ON (switch-off/switch-on) for this component.
Note:
DQI: DRIVE-CLiQ Sensor Integrated
SMI: SINAMICS Sensor Module Integrated
See also: p4690 (SMI spare part component number), p4691 (SMI spare part save/download data)
201900
<location>PB/PN: Configuration telegram error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
%1
Reaction:
NONE
Acknowledge:
NONE
Alarms
922
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A controller attempts to establish a connection using an incorrect configuring telegram.
Alarm value (r2124, interpret decimal):
1:
Connection established to more drive objects than configured in the device. The drive objects for process data exchange and
their sequence are defined in p0978.
2:
Too many PZD data words for output or input to a drive object. The number of possible PZD items in a drive object is
determined by the number of indices in r2050/p2051.
3:
Uneven number of bytes for input or output.
4:
Setting data for synchronization not accepted. For more information, see A01902.
211:
Unknown parameterizing block.
223:
Clock synchronization for the PZD interface set in p8815[0] is not permissible.
More than one PZD interface is operated in clock synchronism.
253:
PN Shared Device: Illegal mixed configuration of PROFIsafe and PZD.
254:
PN Shared Device: Illegal double assignment of a slot/subslot.
255:
PN: Configured drive object and existing drive object do not match.
256:
PN: configured telegram cannot be set.
257:
PN Shared Device: Too many PZD data words for the output or input in the overall device.
500:
Illegal PROFIsafe configuration for the interface set in p8815[1].
More than one PZD interface is operated with PROFIsafe.
501:
PROFIsafe parameter error (e.g. F_dest).
502:
PROFIsafe telegram does not match.
503:
PROFIsafe connection is rejected as long as there is no isochronous connection (p8969).
Additional values:
Only for internal Siemens troubleshooting.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
923
SINAMICS alarms
Remedy:
Check the bus configuration on the master and the slave sides.
For alarm value = 1, 2:
- check the list of the drive objects with process data exchange (p0978).
Note:
With p0978[x] = 0, all of the following drive objects in the list are excluded from the process data exchange.
For alarm value = 2:
- check the number of data words for output and input to a drive object.
For alarm value = 211:
- Ensure offline version <= online version.
For alarm value = 223, 500:
- check the setting in p8839 and p8815.
- check for inserted but not configured CBE20.
- ensure that only one PZD interface is operated in clock synchronism or with PROFIsafe.
For alarm value = 255:
- check configured drive objects.
For alarm value = 256:
- check the configured telegram.
For alarm value = 257:
- check the number of data words for output and input to the complete device.
For alarm value = 501:
- check the set PROFIsafe address (p9610).
For alarm value = 502:
- check the set PROFIsafe telegram (p60022, p9611).
201902
<location>PB/PN: clock cycle synchronous operation parameterization not permissible
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Parameterization for isochronous operation is not permissible.
Alarm value (r2124, interpret decimal):
0: Bus cycle time Tdp < 0.5 ms.
1: Bus cycle time Tdp > 32 ms.
2: Bus cycle time Tdp is not an integer multiple of the current controller sampling time.
3: Instant of the actual value sensing Ti > Bus cycle time Tdp or Ti = 0.
4: Instant of the actual value sensing Ti is not an integer multiple of the current controller sampling time.
5: Instant of the setpoint acceptance To >= Bus cycle time Tdp or To = 0.
6: Instant of the setpoint acceptance To is not an integer multiple of the current controller sampling time.
7: Master application cycle time Tmapc is not an integer multiple of the speed controller sampling time.
8: Bus reserve bus cycle time Tdp - data exchange time Tdx less than two current controller sampling times.
10: Instant of the setpoint acceptance To <= data exchange time Tdx + current controller sampling time
11: Master application cycle time Tmapc > 14 x Tdp or Tmapc = 0.
12: PLL tolerance window Tpll_w > Tpll_w_max.
13: Bus cycle time Tdp is not a multiple of all basic clock cycles p0110[x].
16: For COMM BOARD, the instant in time for the actual value sensing Ti is less than two current controller sampling times.
Alarms
924
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- Adapt the bus parameterization Tdp, Ti, To.
- adapt the sampling time for the current controller or speed controller.
For alarm value = 10:
- reduce Tdx by using fewer bus participants or shorter telegrams.
Note:
PB: PROFIBUS
PN: PROFINET
201903
<location>COMM INT: Receive configuration data invalid
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_I_840, CU_LINK, CU_NX_840, 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:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The drive unit did not accept the receive configuration data.
Alarm value (r2124, interpret decimal):
Return value of the receive configuration data check.
1: Connection established to more drive objects than configured in the device. The drive objects for process data exchange
and their sequence are defined in p0978.
2: Too many PZD data words for output or input to a drive object. The number of possible PZD items in a drive object is
determined by the number of indices in r2050/p2051.
3: Uneven number of bytes for input or output.
4: Setting data for synchronization not accepted. For more information, see A01902.
5: Cyclic operation not active.
501: PROFIsafe parameter error (e.g. F_dest).
Additional values:
Only for internal Siemens troubleshooting.
Remedy:
Check the receive configuration data.
For alarm value = 1, 2:
Check the list of the drive objects with process data exchange (p0978). With p0978[x] = 0, all of the following drive objects
in the list are excluded from the process data exchange.
For alarm value = 2:
Check the number of data words for output and input to a drive object.
For alarm value = 501:
Check the set PROFIsafe address (p9610).
201910
<location>Fieldbus: setpoint timeout
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, TB30, TM120, TM150, TM15DI_DO, TM31, TM41, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF3 (IASC/DCBRK, NONE, OFF1, OFF2, STOP2)
Vector: OFF3 (IASC/DCBRK, NONE, OFF1, OFF2, STOP2)
Hla: OFF3 (NONE, OFF1, OFF2, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
The reception of setpoints from the fieldbus interface (onboard, PROFIBUS/PROFINET/USS) has been interrupted.
- bus connection interrupted.
- controller switched off.
- controller set into the STOP state.
See also: p2040, p2047
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
925
SINAMICS alarms
Remedy:
Restore the bus connection and set the controller to RUN.
Note regarding PROFIBUS slave redundancy:
For operation on a Y link, it must be ensured that "DP alarm mode = DPV1" is set in the slave parameterization.
201911
<location>PB/PN: clock cycle synchronous operation clock cycle failure
Drive object:
All objects
Message value:
-
Reaction:
Infeed: OFF1
Servo: OFF1 (OFF3)
Vector: OFF1 (OFF3)
Hla: OFF1 (OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The global control telegram to synchronize the clock cycles has failed - in cyclic operation - for several DP clock cycles or has
violated the time grid specified in the parameterizing telegram over several consecutive DP clock cycles (refer to the bus cycle
time, Tdp and Tpllw).
Remedy:
- check the physical bus configuration (cable, connector, terminating resistor, shielding, etc.).
- check whether communication was briefly or permanently interrupted.
- check the bus and controller for utilization level (e.g. bus cycle time Tdp was set too short).
Note:
PB: PROFIBUS
PN: PROFINET
201912
<location>PB/PN: clock cycle synchronous operation sign-of-life failure
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: OFF1
Servo: OFF1 (OFF3)
Vector: OFF1 (OFF3)
Hla: OFF1 (OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The maximum permissible number of errors in the controller sign-of-life (clock synchronous operation) has been exceeded
in cyclic operation.
Remedy:
- physically check the bus (cables, connectors, terminating resistor, shielding, etc.).
- correct the interconnection of the controller sign-of-life (p2045).
- check whether the controller correctly sends the sign-of-life (e.g. create a trace with STW2.12 ... STW2.15 and trigger signal
ZSW1.3).
- check the permissible telegram failure rate (p0925).
- check the bus and controller for utilization level (e.g. bus cycle time Tdp was set too short).
Note:
PB: PROFIBUS
PN: PROFINET
201913
<location>COMM INT: Monitoring time sign-of-life expired
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_I_840, CU_LINK, CU_NX_840, 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:
-
Alarms
926
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
Infeed: OFF1 (NONE, OFF2)
Servo: OFF1 (NONE, OFF2, OFF3)
Vector: OFF1 (NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The monitoring time for the sign-of-life counter has expired.
The connection between the drive and the higher-level control (SIMOTION, SINUMERIK) has been interrupted for the
following reasons:
- the control was reset.
- the data transfer to the control was interrupted.
Remedy:
- wait until the control has re-booted.
- restore data transfer to the control.
201914
<location>COMM INT: Monitoring time configuration expired
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_I_840, CU_LINK, CU_NX_840, 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:
%1
Reaction:
Infeed: NONE (OFF1, OFF2)
Servo: NONE (OFF1, OFF2, OFF3)
Vector: NONE (OFF1, OFF2, OFF3)
Hla: NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The monitoring time for the configuration has expired.
Fault value (r0949, interpret decimal):
0: The transfer time of the send configuration data has been exceeded.
1: The transfer time of the receive configuration data has been exceeded.
Remedy:
- acknowledge faults that are present.
- carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade firmware to later version.
- contact Technical Support.
201915
<location>PB/PN: clock cycle synchronous operation sign-of-life failure drive object 1
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
Group display for problems with the sign-of-life of the master (isochronous operation) on the drive object 1 (Control Unit).
For central measurements, synchronism with the central master is lost.
Remedy:
Note:
PB: PROFIBUS
PN: PROFINET
201920
<location>PROFIBUS: Interruption cyclic connection
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The cyclic connection to the PROFIBUS master is interrupted.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
927
SINAMICS alarms
Remedy:
Establish the PROFIBUS connection and activate the PROFIBUS master in the cyclic mode.
Note:
If there is no communication to a higher-level control system, then p2030 should be set = 0 to suppress this message.
See also: p2030 (Field bus interface protocol selection)
201921
<location>PROFIBUS: Receive setpoints after To
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
Output data of PROFIBUS master (setpoints) received at the incorrect instant in time within the PROFIBUS clock cycle.
Remedy:
- check bus configuration.
- check parameters for clock cycle synchronization (ensure To > Tdx).
Note:
To: Time of setpoint acceptance
Tdx: Data exchange time
201925
<location>Modbus TCP: connection interrupted
Drive object:
CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The Ethernet connection to the Modbus controller is interrupted.
Remedy:
- establish an Ethernet connection.
- activate the Modbus controller.
201930
<location>PB/PN: current controller sampling time clock cycle synch. not equal
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The current controller sampling time of all drives must be set the same for the clock cycle synchronous operation.
Alarm value (r2124, interpret decimal):
Number of the drive object with different current controller sampling time.
Remedy:
Set current controller sampling time to identical values (p0115[0]).
Note:
PB: PROFIBUS
PN: PROFINET
See also: p0115
201931
<location>PB/PN: speed controller sampling time clock cycle synch. not equal
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The speed controller sampling time of all drives must be set the same for the clock cycle synchronous operation.
Alarm value (r2124, interpret decimal):
Number of the drive object with the different speed controller sampling time.
Alarms
928
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
Set the speed controller sampling times to identical values (p0115[1]).
Note:
PB: PROFIBUS
PN: PROFINET
See also: p0115
201932
<location>PB/PN: clock cycle synchronization missing for DSC
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:
There is no clock synchronization or clock synchronous sign of life and DSC is selected.
Note:
DSC: Dynamic Servo Control
See also: p0922 (IF1 PROFIdrive PZD telegram selection), p1190 (DSC position deviation XERR), p1191 (DSC position
controller gain KPC)
Remedy:
Set clock synchronization across the bus configuration and transfer clock synchronous sign-of-life.
See also: r2064 (PB/PN diagnostics clock cycle synchronism)
201940
<location>PB/PN: clock cycle synchronism not reached
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing
telegram. It was not possible to synchronize to the clock cycle specified by the master.
- the master does not send a clock synchronous global control telegram although clock synchronous operation was selected
when configuring the bus.
- the master is using another clock synchronous DP clock cycle than was transferred to the slave in the parameterizing
telegram.
- at least one drive object has a pulse enable (also not controlled from PROFIBUS/PROFINET).
Remedy:
- check the master application and bus configuration.
- check the consistency between the clock cycle input when configuring the slave and clock cycle setting at the master.
- check that no drive object has a pulse enable. Only enable the pulses after synchronizing the PROFIBUS/PROFINET drives.
Note:
PB: PROFIBUS
PN: PROFINET
201941
<location>PB/PN: clock cycle signal missing when establishing bus communication
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing
telegram. The global control telegram for synchronization is not being received.
Remedy:
Check the master application and bus configuration.
Note:
PB: PROFIBUS
PN: PROFINET
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
929
SINAMICS alarms
201943
<location>PB/PN: clock cycle signal error when establishing bus communication
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram.
The global control telegram for synchronization is being irregularly received.
-.the master is sending an irregular global control telegram.
- the master is using another clock synchronous DP clock cycle than was transferred to the slave in the parameterizing
telegram.
Remedy:
- check the master application and bus configuration.
- check the consistency between the clock cycle input when configuring the slave and clock cycle setting at the master.
Note:
PB: PROFIBUS
PN: PROFINET
201944
<location>PB/PN: sign-of-life synchronism not reached
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 bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing telegram.
Synchronization with the master sign-of-life (STW2.12 ... STW2.15) could not be completed because the sign-of-life is
changing differently to how it was configured in the Tmapc time grid.
Remedy:
- ensure that the master correctly increments the sign-of-life in the master application clock cycle Tmapc.
- correct the interconnection of the master sign-of-life (p2045).
Note:
PB: PROFIBUS
PN: PROFINET
201945
<location>PROFIBUS: Connection to the Publisher failed
Drive object:
All objects
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Cause:
For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Publisher with address in r2077[0], connection failed.
Bit 15 = 1: Publisher with address in r2077[15], connection failed.
Remedy:
- check the PROFIBUS cables.
- carry out a first commissioning of the Publisher that has the failed connection.
See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)
201946
<location>PROFIBUS: Connection to the Publisher aborted
Drive object:
All objects
Message value:
Fault cause: %1 bin
Alarms
930
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
Infeed: OFF1 (NONE, OFF2)
Servo: OFF1 (NONE, OFF2, OFF3)
Vector: OFF1 (NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
At this drive object, the connection to at least one Publisher for PROFIBUS peer-to-peer data transfer in cyclic operation has
been aborted.
Fault value (r0949, interpret binary):
Bit 0 = 1: Publisher with address in r2077[0], connection aborted.
Bit 15 = 1: Publisher with address in r2077[15], connection aborted.
Remedy:
- check the PROFIBUS cables.
- check the state of the Publisher that has the aborted connection.
See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)
201950
<location>PB/PN: clock cycle synchronous operation synchronization unsuccessful
Drive object:
All objects
Message value:
-
Reaction:
OFF1 (NONE)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
Synchronization of the internal clock cycle to the global control telegram has failed. The internal clock cycle exhibits an
unexpected shift.
Remedy:
Only for internal Siemens troubleshooting.
Note:
PB: PROFIBUS
PN: PROFINET
201951
<location>CU SYNC: Synchronization application clock cycle missing
Drive object:
All objects
Message value:
%1
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
If DRIVE-CLiQ components with different application clock cycle are operated on a DRIVE-CLiQ port, this requires
synchronization with the Control Unit. This synchronization routine was unsuccessful.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy:
- carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade the software of the DRIVE-CLiQ components.
- upgrade the Control Unit software.
Note:
If a Controller Extension is being used (e.g. CX32, NX10), then the following applies:
Check whether the Controller Extension is issuing error messages, and if required, remove these.
201952
<location>CU DRIVE-CLiQ: Synchronization of component not supported
Drive object:
All objects
Message value:
%1
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
931
SINAMICS alarms
Cause:
The existing system configuration requires that the connected DRIVE-CLiQ components support the synchronization
between the basic clock cycle, DRIVE-CLiQ clock cycle and the application clock cycle.
However, not all DRIVE-CLiQ components have this functionality.
Fault value (r0949, interpret decimal):
Component number of the first faulty DRIVE-CLiQ component.
Remedy:
Upgrade the firmware of the component specified in the fault value.
Note:
If required, also upgrade additional components in the DRIVE-CLiQ line.
201953
<location>CU SYNC: Synchronization not completed
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
After the drive system is switched on, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and
application clock cycle was started but was not completed within the selected time tolerance.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy:
Carry out a POWER ON (switch-off/switch-on) for all components.
If the error occurs after the drive sampling times were changed, and if a Terminal Module 31 (TM31) is being used, the
sampling times (p0115, p4099) should be set as integer multiples to the drive clock cycles (p0115).
201954
<location>CU DRIVE-CLiQ: Synchronization unsuccessful
Drive object:
All objects
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
Synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started and was not
able to be successfully completed (e.g. after switch-on).
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy:
1. Remove the cause of a possible DRIVE-CLiQ fault.
2. Initiate a new synchronization, e.g. as follows:
- remove the PROFIBUS master and re-insert again.
- restart the PROFIBUS master.
- switch off the Control Unit and switch on again.
- carry out a Control Unit hardware reset (RESET button, p0972).
- carry out a parameter reset and download the saved parameters (p0009 = 30, p0976 = 2, 3).
201955
<location>CU DRIVE-CLiQ: Synchronization DO not completed
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
After the drive system is switched on, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and
application clock cycle was started but was not completed within the selected time tolerance.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy:
Carry out a POWER ON (switch-off/switch-on) for all components of the DO.
Alarms
932
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
201970
<location>CBExx: cyclic connection interrupted
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The cyclic connection to the PROFINET controller is interrupted.
See also: r8956 (CBExx cyclic connection state)
Remedy:
Establish the PROFINET connection and activate the PROFINET controller in the cyclic mode.
201971
<location>CBExx: maximum number of controllers exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
Info 1: %1, Info 2: %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
A controller attempts to establish a connection to the drive, and as a consequence exceeds the permitted number of
PROFINET connections.
The alarm is automatically withdrawn after approx. 30 seconds.
Alarm value (r2124, interpret hexadecimal):
yyyyxxxx hex: yyyy = info. 1, xxxx = info. 2
Info 1 = 0: number of RT connections exceeded
Info 1 > 0: number of IRT connections exceeded
Info 2: permitted number of connections
Remedy:
Check the configuration of the PROFINET controllers.
201977
<location>CBE41: overtemperature alarm
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The alarm threshold for the overtemperature of the Communication Board Ethernet 41 (CBE41) was reached.
See also: r8828 (CBE41 temperature)
Remedy:
- check the air intake for the Control Unit.
- check the Control Unit fan.
Note:
The alarm is automatically withdrawn once the limit value has been fallen below.
201978
<location>CBE41: overtemperature fault
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
-
Reaction:
Infeed: OFF2 (OFF1)
Servo: OFF3 (IASC/DCBRK, NONE, OFF1, OFF2, STOP2)
Vector: OFF3 (IASC/DCBRK, NONE, OFF1, OFF2, STOP2)
Hla: OFF3 (NONE, OFF1, OFF2, STOP2)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
933
SINAMICS alarms
Acknowledge:
POWER ON
Cause:
The shutdown threshold for the overtemperature of the Communication Board Ethernet 41 (CBE41) was reached.
Note:
This fault results in the component being shut down.
As a consequence, communication via CBE41 is no longer possible.
See also: r8828 (CBE41 temperature)
Remedy:
- Switch-off the Control Unit and after a wait time, switch-on again.
- check the air intake for the Control Unit.
- check the Control Unit fan.
- Replace the component if the fault occurs again.
201979
<location>CBExx: internal error for cyclic data transfer
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The cyclic actual values and/or setpoints were not transferred within the specified times.
Alarm value (r2124, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
Correctly set T_io_input or T_io_output.
201980
<location>PN: cyclic connection interrupted
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The cyclic connection to the PROFINET controller is interrupted.
See also: r8936 (Cyclic connection status)
Remedy:
Establish the PROFINET connection and activate the PROFINET controller in the cyclic mode.
201981
<location>PN: Maximum number of controllers exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
Info 1: %1, Info 2: %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
A controller attempts to establish a connection to the drive, and as a consequence exceeds the permitted number of
PROFINET connections.
The alarm is automatically withdrawn after approx. 30 seconds.
Alarm value (r2124, interpret hexadecimal):
yyyyxxxx hex: yyyy = info. 1, xxxx = info. 2
Info 1 = 0: number of RT connections exceeded
Info 1 > 0: number of IRT connections exceeded
Info 2: permitted number of connections
Remedy:
Check the configuration of the PROFINET controllers.
Alarms
934
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
201982
<location>PN: second controller missing
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
Connections to two PROFINET controllers are expected. However, only the connection to a PROFINET controller is available
or the controller is in the STOP state.
- system redundancy is activated.
Remedy:
Check the PROFINET controller.
201983
<location>PN: system redundancy switchover running
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The "PROFINET system redundancy" function is configured and the connection between the primary control and drive device
is interrupted. The backup controller assumes control of the drive device.
Remedy:
Not necessary.
This alarm is automatically withdrawn after switchover has been completed.
201989
<location>PN: internal cyclic data transfer error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The cyclic actual values and/or setpoints were not transferred within the specified times.
Alarm value (r2124, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
Correctly set T_io_input or T_io_output.
201990
<location>USS: PZD configuration error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The configuration of the process data (PZD) for the USS protocol is incorrect.
Alarm value (r2124, interpret decimal):
2: PZD amount (p2022) too great for the first drive object (p978[0]).
The number of possible PZD items in a drive object is determined by the number of indices in r2050/p2051.
Remedy:
For alarm value = 2:
Check the amount of USS PZD (p2022) and the maximum PZD amount (r2050/p2051) for the first drive object (p0978[0]).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
935
SINAMICS alarms
202000
<location>Function generator: Start not possible
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The function generator has already been started.
Remedy:
Stop the function generator and restart again if necessary.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4800 (Function generator control)
202005
<location>Function generator: Drive does not exist
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The drive object specified for connection does not exist.
See also: p4815 (Function generator drive number)
Remedy:
Use the existing drive object with the corresponding number.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4815 (Function generator drive number)
202006
<location>Function generator: No drive specified for connection
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
No drive specified for connection in p4815.
See also: p4815 (Function generator drive number)
Remedy:
At least one drive to be connected must be specified in p4815.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4815 (Function generator drive number)
202007
<location>Function generator: Drive not SERVO / VECTOR / DC_CTRL
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The drive object specified for connection is not a SERVO / VECTOR or DC_CTRL.
See also: p4815 (Function generator drive number)
Alarms
936
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
Use a SERVO / VECTOR / DC_CTRL drive object with the corresponding number.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
202008
<location>Function generator: Drive specified a multiple number of times
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The drive object specified for connection is already specified.
Alarm value (r2124, interpret decimal):
Drive object number of the drive object that is specified a multiple number of times.
Remedy:
Specify a different drive object.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
202009
<location>Function generator: Illegal mode
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The set operating mode (p1300) of the drive object is not permissible when using the function generator.
Alarm value (r2124, interpret decimal):
Number of the drive object involved.
Remedy:
Change the operating mode for this drive object to p1300 = 20 (encoderless speed control) or p1300 = 21 (speed control
with encoder).
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
202010
<location>Function generator: Speed setpoint from the drive is not zero
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The speed setpoint of a drive selected for connection is greater than the value for the standstill detection set using p1226.
Remedy:
For all of the drives specified for connection, set the speed setpoints to zero.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
937
SINAMICS alarms
202011
<location>Function generator: The actual drive speed is not zero
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_I_840, CU_LINK, CU_NX_840, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP,
CU_S120_PN, ENC, ENC_840, HLA, HLA_840, HUB, R_INF, S_INF, S_INF_840, TB30, TM120, TM15, TM150, TM15DI_DO,
TM17, TM31, TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The speed actual value of a drive selected for connection is greater than the value for the standstill detection set using p1226.
Remedy:
Set the relevant drives to zero speed before starting the function generator.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
202015
<location>Function generator: Drive enable signals missing
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The master control and/or enable signals are missing to connect to the specified drive.
See also: p4815 (Function generator drive number)
Remedy:
Fetch the master control to the specified drive object and set all enable signals.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
202016
<location>Function generator: Magnetizing running
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Magnetizing has not yet been completed on a drive object specified for connection.
Alarm value (r2124, interpret decimal):
Number of the drive object involved.
See also: p4815 (Function generator drive number)
Remedy:
Wait for magnetizing of the motor (r0056.4).
Note:
The alarm is reset as follows:
- restart the function generator.
See also: r0056 (Status word, closed-loop control)
202020
<location>Function generator: Parameter cannot be changed
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
This parameter setting cannot be changed when the function generator is active (p4800 = 1).
See also: p4810, p4812, p4813, p4815, p4820, p4821, p4822, p4823, p4824, p4825, p4826, p4827, p4828, p4829
Alarms
938
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- stop the function generator before parameterizing (p4800 = 0).
- if required, start the function generator (p4800 = 1).
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4800 (Function generator control)
202025
<location>Function generator: Period too short
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_I_840, CU_LINK, CU_NX_840, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP,
CU_S120_PN, ENC, ENC_840, HLA, HLA_840, HUB, R_INF, S_INF, S_INF_840, TB30, TM120, TM15, TM150, TM15DI_DO,
TM17, TM31, TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The value for the period is too short.
See also: p4821 (Function generator period)
Remedy:
Check and adapt the value for the period.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4821 (Function generator period)
202026
<location>Function generator: Pulse width too high
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The selected pulse width is too high.
The pulse width must be less than the period duration.
See also: p4822 (Function generator pulse width)
Remedy:
Reduce pulse width.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4821 (Function generator period), p4822 (Function generator pulse width)
202030
<location>Function generator: Physical address equals zero
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The specified physical address is zero.
See also: p4812 (Function generator physical address)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
939
SINAMICS alarms
Remedy:
Set a physical address with a value other than zero.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4812 (Function generator physical address)
202040
<location>Function generator: Illegal value for offset
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The value for the offset is higher than the value for the upper limit or lower than the value for the lower limit.
See also: p4826 (Function generator offset)
Remedy:
Adjust the offset value accordingly.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: p4826 (Function generator offset), p4828 (Function generator lower limit), p4829 (Function generator upper
limit)
202041
<location>Function generator: Illegal value for bandwidth
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The bandwidth referred to the time slice clock cycle of the function generator has either been set too low or too high.
Depending on the time slice clock cycle, the bandwidth is defined as follows:
Bandwidth_max = 1 / (2 x time slice clock cycle)
Bandwidth_min = Bandwidth_max / 100000
Example:
Assumption: p4830 = 125 µs
--> Bandwidth_max = 1 / (2 x 125 µs) = 4000 Hz
--> Bandwidth_min = 4000 Hz / 100000 = 0.04 Hz
Note:
p4823: Function generator bandwidth
p4830: Function generator time slice clock cycle
See also: p4823 (Function generator bandwidth), p4830 (Function generator time slice cycle)
Remedy:
Check the value for the bandwidth and adapt accordingly.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
202047
<location>Function generator: Time slice clock cycle invalid
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Alarms
940
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The time slice clock cycle selected does not match any of the existing time slices.
See also: p4830 (Function generator time slice cycle)
Remedy:
Enter an existing time slice clock cycle. The existing time slices can be read out via p7901.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
See also: r7901 (Sampling times)
202050
<location>Trace: Start not possible
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The trace has already been started.
See also: p4700 (Trace control)
Remedy:
Stop the trace and, if necessary, start again.
202051
<location>Trace: recording not possible as a result of know-how protection
Drive object:
All objects
Message value:
initiating recorder: %1, parameter %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
TRACE recording is not possible as at least one signal or trigger signal being used is under know-how protection.
Alarm value (r2124, interpret hexadecimal):
bbbbaaaa hex:
aaaa = 1: recorder 0
aaaa = 2: recorder 1
aaaa = 3: recorders 0 and 1
bbbb = parameter number (hexadecimal), that was not able to be written to.
See also: p4700, p4711, p4730, p4731, p4732, p4733, p4734, p4735, p4736, p4737
Remedy:
- Temporarily activate or deactivate know-how protection (p7766).
- include the signal in the OEM exception list (p7763, p7764).
- Where relevant do not record the signal.
See also: p7763, p7764
202055
<location>Trace: Recording time too short
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The trace duration is too short.
The minimum is twice the value of the trace clock cycle.
See also: p4721 (Trace recording time)
Remedy:
Check the selected recording time and, if necessary, adjust.
202056
<location>Trace: Recording cycle too short
Drive object:
All objects
Message value:
-
Reaction:
NONE
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
941
SINAMICS alarms
Acknowledge:
NONE
Cause:
The selected recording cycle is shorter than the selected basic clock cycle 0 (p0110[0]).
See also: p4720 (Trace recording cycle)
Remedy:
Increase the value for the trace cycle.
202057
<location>Trace: Time slice clock cycle invalid
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The time slice clock cycle selected does not match any of the existing time slices.
See also: p4723 (Trace time slice cycle)
Remedy:
Enter an existing time slice clock cycle. The existing time slices can be read out via p7901.
See also: r7901 (Sampling times)
202058
<location>Trace: Time slice clock cycle for endless trace not valid
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The selected time slice clock cycle cannot be used for the endless trace
See also: p4723 (Trace time slice cycle)
Remedy:
Enter the clock cycle of an existing time slice with a cycle time >= 2 ms for up to 4 recording channels or >= 4 ms from 5
recording channels per trace.
The existing time slices can be read out via p7901.
See also: r7901 (Sampling times)
202059
<location>Trace: Time slice clock cycle for 2 x 8 recording channels not valid
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The selected time slice clock cycle cannot be used for more than 4 recording channels.
See also: p4723 (Trace time slice cycle)
Remedy:
Enter the clock cycle of an existing time slice with a cycle time >= 4 ms or reduce the number of recording channels to 4 per
trace.
The existing time slices can be read out via p7901.
See also: p4702 (Trace recording channels count), r7901 (Sampling times)
202060
<location>Trace: Signal to be traced missing
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
- a signal to be traced was not specified.
- the specified signals are not valid.
See also: p4730, p4731, p4732, p4733
Remedy:
- specify the signal to be traced.
- check whether the relevant signal can be traced.
Alarms
942
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
202061
<location>Trace: Invalid signal
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_I_840, CU_LINK, CU_NX_840, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP,
CU_S120_PN, ENC, ENC_840, HLA, HLA_840, HUB, R_INF, S_INF, S_INF_840, TB30, TM120, TM15, TM150, TM15DI_DO,
TM17, TM31, TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
- the specified signal does not exist.
- the specified signal can no longer be traced (recorded).
See also: p4730, p4731, p4732, p4733
Remedy:
- specify the signal to be traced.
- check whether the relevant signal can be traced.
202062
<location>Trace: Invalid trigger signal
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
- a trigger signal was not specified.
- the specified signal does not exist.
- the specified signal is not a fixed-point signal.
- the specified signal cannot be used as a trigger signal for the trace.
See also: p4711 (Trace trigger signal)
Remedy:
Specify a valid trigger signal.
202063
<location>Trace: Invalid data type
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The specified data type to select a signal using a physical address is invalid.
See also: p4711, p4730, p4731, p4732, p4733
Remedy:
Use a valid data type.
202070
<location>Trace: Parameter cannot be changed
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The trace parameter settings cannot be changed when the trace is active.
See also: p4700, p4710, p4711, p4712, p4713, p4714, p4715, p4716, p4720, p4721, p4722, p4730, p4731, p4732,
p4733, p4780, p4781, p4782, p4783, p4789, p4795
Remedy:
- stop the trace before parameterization.
- if required, start the trace.
202075
<location>Trace: Pretrigger time too long
Drive object:
All objects
Message value:
-
Reaction:
NONE
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
943
SINAMICS alarms
Acknowledge:
NONE
Cause:
The selected pretrigger time must be shorter than the trace time.
See also: p4721 (Trace recording time), p4722 (Trace trigger delay)
Remedy:
Check the pretrigger time setting and change if necessary.
202080
<location>Trace: Parameterization deleted due to unit changeover
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The trace parameterization in the drive unit was deleted due to a unit changeover or a change in the reference parameters.
Remedy:
Restart trace.
202085
<location>Message function: Parameterization error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC
Message value:
parameter: %1, index:%2
Reaction:
NONE
Acknowledge:
NONE
Cause:
A parameterization error was identified when starting the variable message function.
Alarm value (r2124, interpret decimal):
yyxxxx dec: yy = index, xxxx = parameter
See also: p3290, p3291, p3292, p3293, r3294, p3295, p3296, p3297, p3298, p3299
Remedy:
Correct the parameter and restart.
Note:
The alarm is automatically withdrawn when stopping, or when successfully starting the variable message function.
202095
<location>MTrace 0: multiple trace cannot be activated
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 0):
- measuring function
- long-time trace
- trigger condition "immediate recording start" (IMMEDIATE)
- trigger condition "start with function generator" (FG_START)
Remedy:
- if required, deactivate the multiple trace (p4840[0] = 0).
- deactivate function or setting that is not permissible
See also: p4840 (MTrace cycle number setting)
202096
<location>MTrace 0: cannot be saved
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Alarms
944
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 0).
A multiple trace is not started or is canceled.
Alarm value (r2124, interpret decimal):
1: Memory card cannot be accessed.
- card is not inserted or is blocked by a mounted USB drive.
3: data save operation to slow.
- a second trace has been completed before the measurement results of the first trace were able to be saved.
- writing the measurement result files to the card is blocked by the parameter save.
4: Data save operation canceled.
- for instance, the file required for the data save operation was not able to be found.
See also: p4840 (MTrace cycle number setting)
Remedy:
- insert or remove the memory card.
- use a larger memory card.
- configure a longer trace time or use an endless trace.
- avoid saving parameters while a multiple trace is running.
- check whether other functions are presently accessing measurement result files.
202097
<location>MTrace 1: multiple trace cannot be activated
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The following functions or settings are not permissible in conjunction with a multiple trace (trace recorder 1):
- measuring function
- long-time trace
- trigger condition "immediate recording start" (IMMEDIATE)
- trigger condition "start with function generator" (FG_START)
Remedy:
- if required, deactivate the multiple trace (p4840[1] = 0).
- deactivate function or setting that is not permissible
See also: p4840 (MTrace cycle number setting)
202098
<location>MTrace 1: cannot be saved
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
It is not possible to save the measurement results of a multiple trace on the memory card (trace recorder 1).
A multiple trace is not started or is canceled.
Alarm value (r2124, interpret decimal):
1: Memory card cannot be accessed.
- card is not inserted or is blocked by a mounted USB drive.
3: data save operation to slow.
- a second trace has been completed before the measurement results of the first trace were able to be saved.
- writing the measurement result files to the card is blocked by the parameter save.
4: Data save operation canceled.
- for instance, the file required for the data save operation was not able to be found.
See also: p4840 (MTrace cycle number setting)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
945
SINAMICS alarms
Remedy:
- insert or remove the memory card.
- use a larger memory card.
- configure a longer trace time or use an endless trace.
- avoid saving parameters while a multiple trace is running.
- check whether other functions are presently accessing measurement result files.
202099
<location>Trace: Insufficient Control Unit memory
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The memory space still available on the Control Unit is no longer sufficient for the trace function.
Remedy:
Reduce the memory required, e.g. as follows:
- reduce the trace time.
- increase the trace clock cycle.
- reduce the number of signals to be traced.
See also: r4708 (Trace memory space required), r4799 (Trace memory location free)
202100
<location>Drive: Computing dead time current controller too short
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The value in p0118 produces a dead time of one clock cycle because it is prior to setpoint availability.
Possible causes:
- a parameter backup with a version higher than 4.3 was loaded to a version less than or equal to 4.3.
- the system properties after replacing a component no longer match the parameter assignment.
Alarm value (r2134, floating point):
Minimum value for p0118 where dead time no longer occurs.
Remedy:
- set p0118 to zero.
- set p0118 to a value greater than or equal to the alarm value (for p1810.11 = 1)
- set p0117 (from the device) to an automatic setting (p0117 = 1).
- check the firmware versions of the components involved.
See also: p0117, p0118
202150
<location>TEC: Technology Extension cannot be loaded
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The system was not able to load a Technology Extension.
Alarm value (r2124, interpret hexadecimal):
10 hex (16 dec):
The interface version in the DCB user library is not compatible to the DCC standard library that has been loaded.
12 hex (18 dec):
A technology package was not able to be downloaded to a Control Unit because the warm restart necessary was not able
to be performed.
Only for internal Siemens troubleshooting.
Alarms
946
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- carry out a warm restart (p0009 = 30, p0976 = 2, 3).
- carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade firmware to later version.
- contact Technical Support.
For alarm value = 10 hex (16 dec):
Load a compatible DCB user library (compatible to the interface of the DCC standard library).
For alarm value = 12 hex (18 dec):
Carry out a POWER ON (switch-off/switch-on) for all components.
Note:
DCB: Drive Control Block
DCC: Drive Control Chart
TEC: Technology Extension
See also: r4950, r4955, p4956, r4957
202151
<location>TEC: internal software error
Drive object:
All objects
Message value:
%1
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (NONE, OFF1, OFF3)
Vector: OFF2 (NONE, OFF1, OFF3)
Hla: OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
An internal software error has occurred within a Technology Extension.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
- carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade firmware to later version.
- contact Technical Support.
- replace the Control Unit.
Note:
TEC: Technology Extension
See also: r4950, r4955, p4956, r4957
202152
<location>TEC: insufficient memory
Drive object:
All objects
Message value:
%1
Reaction:
OFF1
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
Too many functions have been configured on this Control Unit (e.g. too many drives, function modules, data sets,
Technology Extensions, blocks, etc).
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy:
- change the configuration on this Control Unit (e.g. fewer drives, function modules, data sets, Technology Extensions,
blocks, etc).
- use an additional Control Unit.
Note:
TEC: Technology Extension
202153
<location>TEC: technology function does not exist
Drive object:
All objects
Message value:
-
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
947
SINAMICS alarms
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
A technology function (e.g. Technology Extension, DCB library) does not exist on the drive device.
When configuring, a technology function is activated, which does not exist on the drive device. This can occur when
downloading a project or when powering up.
Remedy:
- load the required technology function to the drive device.
- if required, deactivate the technology function not required in the configuration.
Note:
DCB: Drive Control Block
TEC: Technology Extension
203000
<location>NVRAM fault on action
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
A fault occurred during execution of action p7770 = 1 or 2 for the NVRAM data.
Fault value (r0949, interpret hexadecimal):
yyxx hex: yy = fault cause, xx = application ID
yy = 1:
The action p7770 = 1 is not supported by this version if Drive Control Chart (DCC) is activated for the drive object concerned.
yy = 2:
The data length of the specified application is not the same in the NVRAM and the backup.
yy = 3:
The data checksum in p7774 is not correct.
yy = 4:
No data available to load.
See also: p7770 (NVRAM action)
Remedy:
- Perform the remedy according to the results of the troubleshooting.
- if necessary, start the action again.
203001
<location>NVRAM checksum incorrect
Drive object:
All objects
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
A checksum error occurred when evaluating the non-volatile data (NVRAM) on the Control Unit.
The NVRAM data affected was deleted.
Remedy:
Carry out a POWER ON (switch-off/switch-on) for all components.
203500
<location>TM: Initialization
Drive object:
All objects
Message value:
%1
Reaction:
OFF1 (OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
948
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
When initializing the Terminal Modules, the terminals of the Control Unit or the Terminal Board 30, an internal software error
has occurred.
Fault value (r0949, interpret decimal):
yxxx dex
y = Only for internal Siemens troubleshooting
xxx = component number (p0151)
Remedy:
- switch-off/switch-on the power supply for the Control Unit.
- check the DRIVE-CLiQ connection.
- if required, replace the Terminal Module.
The Terminal Module should be directly connected to a DRIVE-CLiQ socket of the Control Unit.
If the fault occurs again, replace the Terminal Module.
203501
<location>TM: Sampling time change
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The sampling times of the inputs/outputs were changed.
This change only becomes valid after the next boot.
Remedy:
Carry out a POWER ON.
203505
<location>Analog input wire breakage
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, ENC, ENC_840, HLA, HLA_840, HUB, R_INF, S_INF, S_INF_840, SERVO, SERVO_840,
SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (NONE, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The wire-break monitoring for an analog input has responded.
Remedy:
Check the wiring for interruptions.
203505
<location>Analog input wire breakage
Drive object:
CU_LINK, CU_NX_840, TM120, TM150, TM54F_MA, TM54F_SL
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The wire-break monitoring for an analog input has responded.
The input value of the analog input has exceeded the threshold value parameterized in p4061[x].
Index x = 0: Analog input 0 (X521.1/X521.2)
Index x = 1: Analog input 1 (X521.3/X521.4)
Fault value (r0949, interpret decimal):
yxxx dec
y = analog input (0 = analog input 0 (AI 0), 1 = analog input 1 (AI 1))
xxx = component number (p0151)
Note:
For the following analog input type, the wire breakage monitoring is active:
p4056[x] = 3 (unipolar current input monitored (+4 ... +20 mA)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
949
SINAMICS alarms
Remedy:
- check the wiring for interruptions.
- check the magnitude of the injected current - it is possible that the infed signal is too low.
- check the load resistor (250 Ohm).
Note:
The input current measured by the Terminal Module can be read out from r4052[x].
For p4056[x] = 3 (unipolar current input monitored (+4 ... +20 mA)) the following applies:
A current less than 4 mA is not displayed in r4052[x] - but instead r4052[x] = 4 mA is output.
203505
<location>CU: Analog input wire breakage
Drive object:
CU_I_840, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The wire-break monitoring for an analog input has responded.
The input value of the analog input has exceeded the threshold value parameterized in p0761[0].
p0756[0]: analog input 0 (X131.7/X131.8)
Fault value (r0949, interpret decimal):
Note:
For the following analog input type, the wire breakage monitoring is active:
p0756[0] = 3 (4 ... 20 mA with monitoring)
Remedy:
- check the wiring to the signal source for interruptions.
- check the magnitude of the injected current - it is possible that the infed signal is too low.
- check the load resistor (250 Ohm).
Note:
The input current measured by the analog input can be read in r0752[0].
For p756[0] = 3 (unipolar current input monitored (+4 ... +20 mA)) the following applies:
A current less than 4 mA is not displayed in r752[0] - but instead r752[0] = 4 mA is output.
203505
<location>TB: Analog input wire breakage
Drive object:
TB30
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The wire-break monitoring for an analog input has responded.
Remedy:
Check the wiring for interruptions.
203505
<location>TM: Analog input wire breakage
Drive object:
TM15, TM15DI_DO, TM17, TM31
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
950
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The wire-break monitoring for an analog input has responded.
The input value of the analog input has exceeded the threshold value parameterized in p4061[x].
Index x = 0: Analog input 0 (X521.1/X521.2)
Index x = 1: Analog input 1 (X521.3/X521.4)
Fault value (r0949, interpret decimal):
yxxx dec
y = analog input (0 = analog input 0 (AI 0), 1 = analog input 1 (AI 1))
xxx = component number (p0151)
Note:
For the following analog input type, the wire breakage monitoring is active:
p4056[x] = 3 (unipolar current input monitored (+4 ... +20 mA)
Remedy:
- check the wiring for interruptions.
- check the magnitude of the injected current - it is possible that the infed signal is too low.
- check the load resistor (250 Ohm).
Note:
The input current measured by the Terminal Module can be read out from r4052[x].
For p4056[x] = 3 (unipolar current input monitored (+4 ... +20 mA)) the following applies:
A current less than 4 mA is not displayed in r4052[x] - but instead r4052[x] = 4 mA is output.
203505
<location>TM: Analog input wire breakage
Drive object:
TM41
Message value:
%1
Reaction:
OFF1 (NONE, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The wire-break monitoring for an analog input has responded.
The input value of the analog input has exceeded the threshold value parameterized in p4061[x].
Index x = 0: Analog input 0 (X522.1 to .3)
Index x = 1: Analog input 1 (X522.4 to .5)
Fault value (r0949, interpret decimal):
yxxx dec
y = analog input (0 = analog input 0 (AI 0), 1 = analog input 1 (AI 1))
xxx = component number (p0151)
Note:
For the following analog input type, the wire breakage monitoring is active:
p4056[x] = 3 (unipolar current input monitored (+4 ... +20 mA)
Remedy:
- check the wiring for interruptions.
- check the magnitude of the injected current - it is possible that the infed signal is too low.
- check the load resistor (250 Ohm).
Note:
The input current measured by the Terminal Module can be read out from r4052[x].
For p4056[x] = 3 (unipolar current input monitored (+4 ... +20 mA)) the following applies:
A current less than 4 mA is not displayed in r4052[x] - but instead r4052[x] = 4 mA is output.
203506
<location>24 V power supply missing
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_I_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, 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:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The 24 V power supply for the digital outputs (X124) is missing.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
951
SINAMICS alarms
Remedy:
Check the terminals for the power supply voltage (X124, L1+, M).
203507
<location>Digital output not set
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, TM41,
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Despite specification by the signal source the digital output has not been set.
Possible causes:
- power supply missing.
- the digital output is in current limiting (e.g. due to short-circuit).
- the digital output is being used for Safety Extended Functions.
- the control has authority to access the digital output by means of direct access (see also r0729).
Alarm value (r2124, interpret bitwise binary):
Digital output involved (structured the same as r0747).
Remedy:
- check the 24 V power supply (e.g. X131.7 for CU305, ground is X131.8).
- check the output terminals for short-circuits.
- reset the signal source of the digital output for use by Safety Extended Functions.
- carry out a POWER ON (switch-off/switch-on).
203507
<location>Digital output not set
Drive object:
CU_I_840, CU_LINK, CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN, ENC, ENC_840, HUB, TB30, TM120, TM15,
TM150, TM15DI_DO, TM17, TM31, TM54F_MA, TM54F_SL
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Despite specification by the signal source the digital output has not been set.
Possible causes:
- power supply missing.
- the digital output is in current limiting (e.g. due to short-circuit).
- the digital output is being used for Safety Extended Functions.
- the control has authority to access the digital output by means of direct access (see also r0729).
Alarm value (r2124, interpret bitwise binary):
Digital output involved (structured the same as r0747).
Remedy:
- check the 24 V power supply (e.g. X130.6 for CU310-2, ground is X130.5).
- check the output terminals for short-circuits.
- reset the signal source of the digital output for use by Safety Extended Functions.
- carry out a POWER ON (switch-off/switch-on).
203510
<location>Calibration data not plausible
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, CU_NX_840, ENC, ENC_840, HLA, HLA_840, HUB, R_INF, S_INF, S_INF_840,
SERVO, SERVO_840, SERVO_AC, TB30, TM41, TM54F_MA, TM54F_SL
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Alarms
952
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
During ramp-up, the Terminal Module 31 (TM31) calibration data is read in and checked for plausibility.
At least one calibration data point was determined to be invalid.
Alarm value (r2124, interpret binary):
Bit 1: 10 V value, analog input 0 invalid.
Bit 3: 10 V value, analog input 1 invalid.
Bit 4: Offset, analog output 0 invalid.
Bit 5: 10 V value, analog output 0 invalid.
Bit 6: Offset, analog output 1 invalid.
Bit 7: 10 V value, analog input 1 invalid.
Remedy:
- switch-off/switch-on the power supply for the Control Unit.
- check the DRIVE-CLiQ wiring.
Note:
If it reoccurs, then replace the module.
In principle, operation could continue.
The analog channel involved possibly does not achieve the specified accuracy.
203510
<location>CU: Calibration data not plausible
Drive object:
CU_I_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
During ramp-up, the Terminal Module 31 (TM31) calibration data is read in and checked for plausibility.
At least one calibration data point was determined to be invalid.
Alarm value (r2124, interpret binary):
Bit 1: 10 V value, analog input 0 invalid.
Bit 3: 10 V value, analog input 1 invalid.
Bit 4: Offset, analog output 0 invalid.
Bit 5: 10 V value, analog output 0 invalid.
Bit 6: Offset, analog output 1 invalid.
Bit 7: 10 V value, analog input 1 invalid.
Remedy:
- switch-off/switch-on the power supply for the Control Unit.
- check the DRIVE-CLiQ wiring.
Note:
If it reoccurs, then replace the module.
In principle, operation could continue.
The analog channel involved possibly does not achieve the specified accuracy.
203510
<location>CU: Calibration data not plausible
Drive object:
CU_S_AC_DP, CU_S_AC_PN, CU_S120_DP, CU_S120_PN
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
During booting, the calibration data for the analog inputs is read and checked with respect to plausibility.
At least one calibration data point was determined to be invalid.
Remedy:
- switch-off/switch-on the power supply for the Control Unit.
- check the DRIVE-CLiQ wiring.
Note:
If it reoccurs, then replace the module.
In principle, operation could continue.
The analog channel involved possibly does not achieve the specified accuracy.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
953
SINAMICS alarms
203510
<location>TM: Calibration data not plausible
Drive object:
TM120, TM15, TM150, TM15DI_DO, TM17, TM31
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
During ramp-up, the Terminal Module 31 (TM31) calibration data is read in and checked for plausibility.
At least one calibration data point was determined to be invalid.
Alarm value (r2124, interpret binary):
Bit 1: 10 V value, analog input 0 invalid.
Bit 3: 10 V value, analog input 1 invalid.
Bit 4: Offset, analog output 0 invalid.
Bit 5: 10 V value, analog output 0 invalid.
Bit 6: Offset, analog output 1 invalid.
Bit 7: 10 V value, analog input 1 invalid.
Remedy:
- switch-off/switch-on the power supply for the Control Unit.
- check the DRIVE-CLiQ wiring.
Note:
If it reoccurs, then replace the module.
In principle, operation could continue.
The analog channel involved possibly does not achieve the specified accuracy.
203510
<location>Calibration data not plausible
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
During booting, the calibration data for the analog inputs is read and checked with respect to plausibility.
At least one calibration data point was determined to be invalid.
Remedy:
- switch-off/switch-on the power supply for the Control Unit.
- check the DRIVE-CLiQ wiring.
Note:
If it reoccurs, then replace the module.
In principle, operation could continue.
The analog channel involved possibly does not achieve the specified accuracy.
203550
<location>TM: Speed setpoint filter natural frequency > Shannon frequency
Drive object:
All objects
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The natural filter frequency of the speed setpoint filter (p1417) is greater than or equal to the Shannon frequency.
The Shannon frequency is calculated according to the following formula:
0.5 / p4099[3]
See also: p1417
Remedy:
Reduce the natural frequency of the speed setpoint filter (PT2 low pass) (p1417).
203590
<location>TM: Module not ready
Drive object:
All objects
Message value:
%1
Alarms
954
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
Infeed: OFF2 (NONE)
Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Vector: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Hla: OFF2 (NONE)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The Terminal Module involved does not send a ready signal and no valid cyclic data.
Fault value (r0949, interpret decimal):
Drive object number of the Terminal Module involved.
Remedy:
- check the 24 V power supply.
- check the DRIVE-CLiQ wiring.
- check whether the sampling time of the drive object involved is not equal to zero (p4099[0]).
205000
<location>Power unit: Overtemperature heat sink AC inverter
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 alarm threshold for overtemperature at the inverter heat sink has been reached. The response is set using p0290.
If the heat sink temperature exceeds the value set in p0292[0], then fault F30004 is output.
Remedy:
Check the following:
- is the ambient temperature within the defined limit values?
- have the load conditions and the load duty cycle been appropriately dimensioned?
- has the cooling failed?
205001
<location>Power unit: Overtemperature depletion layer chip
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:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
Alarm threshold for overtemperature of the power semiconductor in the AC converter has been reached.
Note:
- the response is set using p0290.
- if the temperature of the barrier layer increases by the value set in p0292[1], then fault F30025 is initiated.
Remedy:
Check the following:
- is the ambient temperature within the defined limit values?
- have the load conditions and the load duty cycle been appropriately dimensioned?
- has the cooling failed?
- pulse frequency too high?
See also: r0037, p0290
205001
<location>Power unit: Overtemperature depletion layer chip
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
Alarm threshold for overtemperature of the power semiconductor in the AC converter has been reached.
Note:
- the response is set using p0290.
- if the temperature of the barrier layer increases by the value set in p0292[1], then fault F30025 is initiated.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
955
SINAMICS alarms
Remedy:
Check the following:
- is the ambient temperature within the defined limit values?
- have the load conditions and the load duty cycle been appropriately dimensioned?
- has the cooling failed?
- pulse frequency too high?
Note:
If the alarm occurs after reducing the current controller sampling time (p0115[0]) during the motor data identification
(standstill measurement), then it is recommended that this is initially performed using the standard sampling time and then
the sampling time should be subsequently changed over.
See also: r0037, p0290
205002
<location>Power unit: Air intake overtemperature
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 alarm threshold for the air intake overtemperature has been reached. For air-cooled power units, the threshold is 42 °C
(hysteresis 2 K). The response is set using p0290.
If the air intake temperature increases by an additional 13 K, then fault F30035 is output.
Remedy:
Check the following:
- is the ambient temperature within the defined limit values?
- has the fan failed? Check the direction of rotation.
205003
<location>Power unit: Internal overtemperature
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 alarm threshold for internal overtemperature has been reached.
If the temperature inside the power unit increases by an additional 5 K, then fault F30036 is triggered.
Remedy:
Check the following:
- is the ambient temperature within the defined limit values?
- has the fan failed? Check the direction of rotation.
205004
<location>Power unit: Rectifier overtemperature
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 alarm threshold for the overtemperature of the rectifier has been reached. The response is set using p0290.
If the temperature of the rectifier increases by an additional 5 K, then fault F30037 is triggered.
Remedy:
Check the following:
- is the ambient temperature within the defined limit values?
- have the load conditions and the load duty cycle been appropriately dimensioned?
- has the fan failed? Check the direction of rotation.
- has a phase of the line supply failed?
- is an arm of the supply (incoming) rectifier defective?
205005
<location>Cooling unit: Cooling medium flow rate too low
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
Alarms
956
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Cooling unit: Alarm - flow rate has fallen below the alarm value
Remedy:
- check the feedback signals and parameter assignment (p0260 ... p0267).
- check the coolant feed.
205006
<location>Power unit: Overtemperature thermal model
Drive object:
A_INF, A_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 temperature difference between the chip and heat sink has exceeded the permissible limit value (blocksize power units
only).
Depending on p0290, an appropriate overload response is initiated.
See also: r0037
Remedy:
Not necessary.
This alarm is automatically withdrawn once the limit value has been fallen below.
Note:
If the alarm is not automatically withdrawn and the temperature continues to rise, this can result in fault F30024.
See also: p0290 (Power unit overload response)
205007
<location>Power unit: Overtemperature thermal model (chassis PU)
Drive object:
A_INF, A_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 temperature difference between the chip and heat sink has exceeded the permissible limit value (r0293) (chassis power
units only).
Depending on p0290, an appropriate overload response is initiated.
See also: r0037, r0293
Remedy:
Not necessary.
This alarm is automatically withdrawn once the limit value has been fallen below.
See also: p0290 (Power unit overload response)
205050
<location>Parallel circuit: Pulse enable in spite of pulse inhibit
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
A power unit signals that the pulses are enabled although the pulses are inhibited.
Fault value (r0949, interpret decimal):
Number of the power unit involved.
Remedy:
The power unit is defective and must be replaced.
205051
<location>Parallel circuit: Power unit pulse enable 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:
%1
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
957
SINAMICS alarms
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
For one or several power units, the pulses were not able to be enabled.
Fault value (r0949, interpret decimal):
Number of the power unit involved.
Remedy:
- acknowledge power unit faults that are still present.
- inhibit the pulses of the power unit involved (p7001).
205052
<location>Parallel circuit: Illegal current asymmetry
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The deviation of the individual currents of the power units exceeds the alarm threshold specified in p7010.
Alarm value (r2124, interpret decimal):
1: Phase U.
2: Phase V.
3: Phase W.
Remedy:
- inhibit the pulses of the faulted power unit (p7001).
- check the connecting cables. Loose contacts can cause current spikes.
- the motor reactors are non-symmetrical or faulty and must be replaced.
- the CTs must be calibrated or replaced.
205053
<location>Parallel circuit: Inadmissible DC link voltage asymmetry
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:
NONE
Acknowledge:
NONE
Cause:
The deviation of the DC link voltage measured values exceeds the alarm threshold specified in p7011.
Remedy:
- inhibit the pulses of the faulted power unit (p7001).
- check the DC link connecting cables.
- the DC link voltage measurement is incorrect and must be calibrated or renewed.
205054
<location>Parallel circuit: Power unit deactivated
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:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
For the drive object involved, fewer power units connected in parallel are active than exist in the target topology. Operation
is only possible at reduced power (power derating).
Remedy:
Re-activate the deactivated power units if required.
See also: p0125, p0895, p0897
205055
<location>Parallel connection: Power units with illegal code numbers
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840
Message value:
Parameter: %1
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Alarms
958
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The code numbers of the power units are not permissible.
For parallel circuit configurations, only power units with identical power unit data may be used.
Possible causes:
- the code numbers of the power units do not match.
For booksize drive units, the following additionally applies:
- a parallel connection is not possible for the power units being used.
- there are too many power units being used in the parallel connection.
Fault value (r0949, interpret decimal):
Parameter in which the inadmissible power unit code number was detected.
Remedy:
- Use power units with the same code number.
For booksize drive units, the following additionally applies:
- use power units which are permitted for a parallel connection.
- reduce the number of power units being used in the parallel connection.
205055
<location>Parallel connection: Power units with illegal code numbers
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Parameter: %1
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
The code numbers of the power units do not match.
Fault value (r0949, interpret decimal):
Parameter in which the first different power unit code number was detected.
Remedy:
Use power units with the same code number.
For parallel circuit configurations, only power units with identical power unit data may be used.
205056
<location>Parallel circuit: Power unit EEPROM versions differ
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:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
The EEPROM versions of the power units do not match.
Fault value (r0949, interpret decimal):
Parameter in which the first different version number was detected.
Remedy:
Use power units with the same EEPROM version.
Note:
For parallel circuit configurations, only power units with identical EEPROM versions may be used.
205057
<location>Parallel circuit: Power unit firmware versions differ
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:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
The firmware versions of the power units connected in parallel do not match.
Fault value (r0949, interpret decimal):
Parameter in which the first different version number was detected.
Remedy:
Use power units with the same firmware version.
For parallel circuit configurations, only power units with identical firmware versions may be used.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
959
SINAMICS alarms
205058
<location>Parallel circuit: VSM EEPROM versions differ
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
Cause:
The EEPROM versions of the Voltage Sensing Modules (VSM) do not match.
Fault value (r0949, interpret decimal):
Parameter in which the first different version number was detected.
Remedy:
For parallel circuit configurations, only Voltage Sensing Modules (VSM) with identical EEPROM versions may be used.
205059
<location>Parallel circuit: VSM firmware versions differ
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
Cause:
The firmware versions of the Voltage Sensing Module (VSM) do not match.
Fault value (r0949, interpret decimal):
Parameter in which the first different version number was detected.
Remedy:
For parallel circuit configurations, only Voltage Sensing Modules (VSM) with identical firmware versions may be used.
205060
<location>Parallel circuit: Power unit firmware version does not match
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:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
Firmware from version V02.30.01.00 is required when connecting the power units in parallel.
Remedy:
Update the firmware of the power units (at least V02.30.01.00).
205061
<location>Infeed VSM count
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:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The number of active Voltage Sensing Modules (VSM) for the drive object infeed with chassis power units is not correct.
For A_Infeed, each active power unit must be assigned an active VSM also for a parallel circuit configuration.
For S_Infeed, the active drive object, must be assigned at least one active VSM.
Fault value (r0949, interpret decimal):
Number of VSMs that are currently assigned to the drive object.
Remedy:
Adapts the number of active Voltage Sensing Modules (VSM).
205064
<location>Parallel connection: Pulse synchronization error
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Infeed: OFF2 (OFF1)
Vector: OFF2 (OFF1, OFF3)
Acknowledge:
POWER ON (IMMEDIATELY)
Alarms
960
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The pulse synchronization of at least one of the power units connected in parallel is incorrect.
Remedy:
Restart the drive system.
205065
<location>Voltage measured values not plausible
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The voltage measurement does not supply any plausible values and is not used.
Alarm value (r2124, interpret bitwise binary):
Bit 1: Phase U
Bit 2: Phase V
Bit 3: Phase W
Remedy:
The following parameterization must be made in order to deactivate the alarm:
- Deactivate voltage measurement (p0247.0 = 0).
- Deactivate flying restart with voltage measurement (p0247.5 = 0) and deactivate fast flying restart (p1780.11 = 0).
205066
<location>Parallel connection: inadmissible asymmetry VSM voltage
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The deviation of the individual voltages of the Voltage Sensing Module (VSM) exceeds the alarm threshold set in p7324.
Alarm value (r2124, interpret decimal):
1: VSM voltage u1 - u2.
2: VSM voltage u2 - u3.
Remedy:
- Check alarm threshold p7324, and if required, adapt.
- Check the connecting cables. Loose contacts can cause voltage spikes.
- Check the line connections, line circuit breaker and bypass contactors.
- Check filter reactors and filter capacitances. All parallel line filters must be of the same type, and must not have faulty
reactors or capacitors.
- Deactivate the faulty Voltage Sensing Module (VSM) and faulty power unit (p7001), or if required, replace.
See also: p7001 (Par_circuit power units enable), p7324 (Par_connection VSM voltage asymmetry alarm threshold)
205118
<location>Precharging contactor simultaneity monitoring time exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
fault cause: %1, additional information: %2
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
961
SINAMICS alarms
Cause:
A feedback signal for the precharging contactor (ALM, SLM, BLM diode) or the line contactor (BLM thyristor) interconnected
and the simultaneity monitoring (p0255[4, 6]) activated.
After opening or closing a contactor of the parallel connection, after a monitoring time has elapsed, not all of the contactors
have assumed the same state.
Fault value (r0949, interpret binary):
yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause
Fault cause:
Bit 0 = 1: simultaneity error when closing the contactors.
Bit 1 = 1: simultaneity error when opening the contactors.
Supplementary information:
Bit 0 = 1: PDS0 contactor is closed.
Bit 1 = 1: PDS1 contactor is closed.
Bit 2 = 1: PDS2 contactor is closed.
Bit 3 = 1: PDS3 contactor is closed.
Bit 4 = 1: PDS4 contactor is closed.
Bit 5 = 1: PDS5 contactor is closed.
Bit 6 = 1: PDS6 contactor is closed.
Bit 7 = 1: PDS7 contactor is closed.
Note:
ALM: Active Line Module
BLM: Basic Line Module
PDS: Power unit Data Set
SLM: Smart Line Module
Remedy:
- check the monitoring time setting (p0255[4, 6]).
- check the wiring and control of the contactor.
- if required, replace the contactor.
See also: p0255 (Power unit contactor monitoring time)
205119
<location>Bypass contactor simultaneity monitoring time exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
fault cause: %1, additional information: %2
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
A feedback signal for the bypass contactor is interconnected and the simultaneity monitoring (p0255[5, 7]) activated.
After opening or closing a contactor of the parallel connection, after a monitoring time has elapsed, not all of the contactors
have assumed the same state.
Fault value (r0949, interpret binary):
yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause
Fault cause:
Bit 0 = 1: simultaneity error when closing the contactors.
Bit 1 = 1: simultaneity error when opening the contactors.
Supplementary information:
Bit 0 = 1: PDS0 contactor is closed.
Bit 1 = 1: PDS1 contactor is closed.
Bit 2 = 1: PDS2 contactor is closed.
Bit 3 = 1: PDS3 contactor is closed.
Bit 4 = 1: PDS4 contactor is closed.
Bit 5 = 1: PDS5 contactor is closed.
Bit 6 = 1: PDS6 contactor is closed.
Bit 7 = 1: PDS7 contactor is closed.
Note:
PDS: Power unit Data Set
Alarms
962
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- check the monitoring time setting (p0255[5, 7]).
- check the wiring and control of the contactor.
- if required, replace the contactor.
See also: p0255 (Power unit contactor monitoring time)
206000
<location>Infeed: Precharging monitoring time expired
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY
Cause:
After the line contactor closes the power unit does not signal the READY state within the monitoring time (p0857).
The end of the DC link precharging was not able to be completed for one of the following reasons:
1) There is no line supply voltage connected.
2) The line contactor/line side switch has not been closed.
3) The line supply voltage is too low.
4) Line supply voltage incorrectly set (p0210).
5) The precharging resistors are overheated as there were too many precharging operations per time unit.
6) The precharging resistors are overheated as the DC link capacitance is too high.
7) The precharging resistors are overheated because when there is no "ready for operation" (r0863.0) of the infeed unit,
power is taken from the DC link.
8) The precharging resistors are overheated as the line contactor was closed during the DC link fast discharge through the
Braking Module.
9) The DC link has either a ground fault or a short-circuit.
10) The precharging circuit is possibly defective (only for chassis units).
See also: p0210, p0857
Remedy:
In general:
- check the line supply voltage at the connecting terminals.
- check the line supply voltage setting (p0210).
- check the monitoring time and, if required, increase (p0857).
- where relevant, observe additional power unit messages/signals (e.g. F30027).
- the following applies to booksize units: Wait (approx. 8 min.) until the precharging resistors have cooled down. For this
purpose, preferably disconnect the infeed unit from the line supply.
For 5):
- carefully observe the permissible precharging frequency (refer to the appropriate Equipment Manual).
For 6):
- check the total capacitance of the DC link and reduce in accordance with the maximum permissible DC link capacitance if
necessary (refer to the appropriate Equipment Manual)
For 7):
- interconnect the ready-for-operation signal from the infeed unit (r0863.0) in the enable logic of the drives connected to
this DC link
For 8):
- check the connections of the external line contactor. The line contactor must be open during DC link fast discharge.
For 9):
- check the DC link for ground faults or short circuits.
206010
<location>Infeed: Power unit EP 24 V missing in operation
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
963
SINAMICS alarms
Cause:
In operation, the pulse enable via terminal EP at the Line Module (X21.3, X21.4) was withdrawn.
Note:
EP: Enable Pulses (pulse enable)
Remedy:
- do not open the line side switch in operation - only when the pulses are inhibited.
- check the wiring of terminal EP (X21.3, X21.4) at the Line Module to exclude any poor contacts.
206050
<location>Infeed: Smart Mode not supported
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
OFF2
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The power unit does not support the Smart Mode or pulse frequency wobbulation is activated (p1810).
Remedy:
- set the suitable sampling time 250 µs <= p0115[0] <= 400 µs (e.g. by setting p0112 and p0115 to the factory setting).
- upgrade the power unit software and/or hardware for the Smart Mode. The availability of the Smart Mode function is
displayed in r0192.
- when the software gating unit is activated (p1810.2 = 1 or p1810.13 = 1), then the Smart Mode is not permissible. Either
the Smart Mode must be deactivated (p3400.0 = 0) or the software gating unit must be deactivated.
- for A_INF the following applies: deactivate the Smart Mode using p3400.0 = 0, and activate closed-loop voltage control
with p3400.3 = 1. For booksize power units, it must be noted that for a supply voltage p0210 > 415 V only the Smart Mode
is possible in the presetting. If DC link voltages above 660 V are permissible in the application, then voltage-controlled
operation can be activated with p0280, p0210, p3400 and p3510. The information regarding p0210 should be carefully
noted.
See also: r0192
206052
<location>Infeed: Filter temperature evaluation not supported
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY
Cause:
The power unit does not support filter temperature evaluation.
This feature (r0192.11) is required when an Active Interface Module is used as a line filter (p0220 = 41 ... 45).
Remedy:
Upgrade the firmware for the power unit to a later version.
See also: r0192, p0220
206080
<location>Infeed: parameter error
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
Parameter: %1
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
An infeed parameter is incorrectly set.
Fault value (r0949, interpret decimal):
Number of the parameter involved.
See also: p0220, p3665, p3667, p3668
Remedy:
Appropriately change the parameter specified in the fault value.
See also: p0220, p3665, p3667, p3668
206100
<location>Infeed: Shutdown due to line supply undervoltage condition
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
OFF2 (OFF1)
Alarms
964
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The filtered (steady-state) value of the line supply voltage is less than the fault threshold (p0283).
Fault condition: Vrms < p0283 * p0210
Fault value (r0949, floating point):
Actual steady-state line supply voltage.
Note:
The occurrence of this fault is delayed by the time in p3492. If the fault is removed during this design time, then the power
unit is not tripped (shut down).
See also: p0283 (Line supply undervoltage shutdown (trip) threshold), p3492 (Infeed, line supply undervoltage delay time)
Remedy:
- check the line supply.
- check the line supply voltage (p0210).
- check the threshold value (p0283).
206105
<location>Infeed: Line supply undervoltage
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 filtered (steady-state) value of line supply voltage is lower than the alarm threshold (p0282).
Alarm condition: Vrms < p0282 * p0210
Alarm value (r2124, floating point):
Actual steady-state line supply voltage.
See also: p0282 (Line supply undervoltage alarm threshold)
Remedy:
- check the line supply.
- check the line supply voltage (p0210).
- check the alarm threshold (p0282).
206200
<location>Infeed: One or several line phases failed
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
Failure overvoltage in one or several line supply phases.
The fault can be output in two operating states:
1. During the switch-on phase of the infeed unit.
The measured line supply angle deviates from the regular characteristic for a 3-phase system - the PLL cannot be
synchronized.
The fault occurs immediately after switch-on if, when operating with a Voltage Sensing Module (VSM), the phase
assignment L1, L2, L3 at the VSM differs from the phase assignment at the power unit.
2. While the infeed is operational.
During an active line voltage alarm (A06205) or current symmetry alarm (A06206), an additional fault occurred, which
resulted in a shutdown. Alarm values A06205 and A06206 could provide additional information about the cause of the
shutdown.
Possible causes:
- voltage dip on the line side or phase failure or overvoltage lasting longer than 10 ms.
- overload condition on the load side with peak current.
- line reactor missing.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
965
SINAMICS alarms
Remedy:
- check the line supply, terminals and fuses.
- check the connection and size (rating) of the line line filter and/or the line commutating reactor.
- check and correct the phase assignment at the VSM (X521 or X522) and at the power unit.
- check the load.
- if failed in operation, carefully note the previous alarm messages A06205/A06206 with alarm values.
See also: p3463 (Infeed phase failure detection line supply angle change)
206205
<location>Infeed: Voltage dip in at least one line supply phase
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Voltage dip or overvoltage in one or several line supply phases has been detected in operation.
The event is displayed in status parameter r3405.2.
If nothing else is specified for the alarm values, then at the instant of the alarm, the pulses are inhibited for a minimum of
8 ms.
Also for alarm values with pulse inhibit, the operating signal of the infeed remains in r0863.0.
Alarm value (r2124, interpret bitwise binary):
Bit 0: Line angle deviation due to a line supply fault (limit value p3463).
Bit 2: Active current deviation.
Bit 3: Line frequency deviation (limit values: 115 % * p0284, 85 % * p0285).
Bit 4: Line overvoltage (limit value: 120 % * p0281 * p0210).
Bit 5: Line undervoltage (limit value: 20 % * p0210).
Bit 7: peak current event.
Bit 8: Line supply angle deviation identified in the Smart Mode (p3400.0 = 1). In addition, for Extended Smart Mode
(p3440.1 = 1) the following applies: pulses are not inhibited.
Bit 9: DC link voltage dip identified in the Smart Mode (p3400.0 = 1).
Bit 11: Line voltage detection error identified in the Smart Mode (p3400.0 = 1):
Bit 12: Line voltage deviation identified in the Extended Smart Mode (p3400.0 = 1, p3440.1 = 1). Pulses are not inhibited.
Bit 14: Recharging current fault.
Alarms
966
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
When the alarm occurs, the following always applies:
- check the line supply, terminals and fuses.
- check the line supply quality and system fault level.
- check the load.
Dependent on the alarm value in r2124, the following also applies:
For bit 0 = 1:
Line fault occurred or poor/incorrect controller setting. For poor line quality or frequent line supply changeover operations,
when required, limit value p3463 can be increased until the alarm value no longer occurs.
For bit 2 = 1:
Line fault occurred or poor/incorrect controller setting. - check the controller setting and load.
For bit 3 = 1:
Line fault occurred. For poor line quality or frequent line changeover operations, when required, limit values p0284 and
p0285 can be increased until the alarm value no longer occurs.
For bit 4 = 1:
Line interrupted or line overvoltage has occurred.
For bit 5 = 1:
Line interrupted or line undervoltage occurred.
For bit 7 = 1:
Peak current shutdown due to a line fault, overload or incorrect/missing line reactor.
For bit 8 = 1:
Line fault occurred.
For bit 9 = 1:
Line undervoltage or overload.
For bit 11 = 1:
Fault in at least one line phase.
For bit 12 = 1:
Voltage fault in at least one line phase. Check the settings in p3444[2, 3].
For bit 14 = 1:
Supply/infeed overload or a fault in at least one line phase.
See also: r3405, p3463 (Infeed phase failure detection line supply angle change)
206206
<location>Infeed: Line currents asymmetrical alarm
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The asymmetry of the three line currents at the terminals of the power unit exceeds the set alarm threshold (p3465).
Generally, the cause of current asymmetry is line voltage asymmetry or failure of a line phase (e.g. a fuse has ruptured or
a terminal connection has become loose). As a consequence, the message is also signaled as possible phase failure in status
parameter r3405.2.
Cyclic power fluctuations in the DC link with the line frequency can also result in unequal rms values of the line currents. For
this type of operating scenario, it is recommended that monitoring is deactivated (p3465[0, 3] = 0).
Alarm value (r2134, floating point):
Digits to the left of the decimal point:
Highest rms phase current in amps.
Decimal places:
Quotient of the lowest and highest rms phase current value.
Remedy:
- check the line supply, terminals and fuses.
- check the line supply quality and system fault level.
- check the load.
- check the settings in p3462 and p3465.
See also: r3405, p3465 (Infeed current symmetry monitoring thresholds)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
967
SINAMICS alarms
206207
<location>Infeed: Line currents asymmetrical
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
OFF1 (NONE, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The asymmetry of the line currents is continuously too high.
The most probable cause is failure of a line phase.
Fault value (r2133, floating point):
Digits to the left of the decimal point:
Highest rms phase current in amps.
Decimal places:
Quotient of the lowest and highest rms phase current value.
Remedy:
- check the previous alarm A06206 and the alarm value.
- check the line supply, terminals and fuses.
- check the settings in p3462 and p3465.
- check the connection and size (rating) of the line line filter and/or the line commutating reactor.
206208
<location>Infeed line: supply voltage asymmetrical
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
Asymmetry of the voltages in the line phase too high.
The most probable cause is failure of a line phase.
Note:
This message is only output when asymmetry monitoring is activated (p3640.1 = 1).
Remedy:
- check the line supply, terminals and fuses.
- check the setting values for the phase asymmetry (p3647[0, 1]).
206210
<location>Infeed: Summation current too high
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The smoothed total of the phase currents (i1 + i2 + i3) is greater than 4 % of the maximum power unit current (r0209).
Possible causes:
- the DC link has a ground fault that results in a high summation current (r0069.6). The DC component in the line currents
can damage/destroy the power unit, line reactor or line filter!
- the zero point calibration of the current measurement was not carried out (p3491, A06602).
- defective current measurement in the power unit.
Fault value (r0949, floating point):
Smoothed total of the phase currents.
Remedy:
- check the DC link for a low-ohmic or high-ohmic ground fault and if present, remove.
- increase the monitoring time of the current offset measurement (p3491).
- replace the power unit if necessary.
206211
<location>Infeed: Summation current impermissibly high
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
OFF2
Alarms
968
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The smoothed sum of the phase currents (i1 + i2 + i3) is impermissibly high. The summed current has exceeded the
parameterized threshold for the ground fault monitoring (p0287).
Possible causes:
- there is a ground fault that results in a high summation current (r0069.6). The DC component in the line currents can
damage/destroy the power unit, line reactor or line filter!
- the zero point calibration of the current measurement was not carried out (p3491, A06602).
- the current measurement in the power unit is defective.
Fault value (r0949, floating point):
Smoothed total of the phase currents (peak value).
Remedy:
- check the line supply for ground faults and remove any that are present.
- check the set threshold for the ground fault monitoring (p0287).
- if required, replace the power unit.
See also: p0287 (Ground fault monitoring shutdown threshold)
206211
<location>Summation current impermissibly high
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The smoothed sum of the phase currents (i1 + i2 + i3) is impermissibly high. The total current has exceeded the
parameterized threshold for the ground fault monitoring (p0287).
Possible causes:
- there is a ground fault that results in a high summation current (r0069.6). The DC component in the line currents can
damage/destroy the power unit, reactor, filter or motor!
- the current measurement in the power unit is defective.
Fault value (r0949, floating point):
Smoothed total of the phase currents.
Remedy:
- check the line supply for ground faults and remove any that are present.
- check the set threshold for the ground fault monitoring (p0287).
- if required, replace the power unit.
See also: p0287 (Ground fault monitoring shutdown threshold)
206215
<location>Infeed: Summation current too high
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The smoothed total of the phase currents (i1 + i2 + i3) is greater than 3 % of the maximum power unit current (r0209).
Possible causes:
- the DC link has a ground fault that results in a high summation current (r0069.6). The DC component in the line currents
can damage/destroy the power unit, line reactor or line filter!
- the zero point calibration of the current measurement was not carried out (p3491, A06602).
- defective current measurement in the power unit.
Alarm value (r2124, floating point):
Smoothed total of the phase currents.
Remedy:
- check the DC link for a low-ohmic or high-ohmic ground fault and if present, remove.
- increase the monitoring time of the current offset measurement (p3491).
- replace the power unit if necessary.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
969
SINAMICS alarms
206250
<location>Infeed: Defective capacitor(s) in at least one phase of line filter
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A change in the line filter capacitance was detected in at least one line phase.
The voltages and phase currents of the line filter, measured using a VSM, indicate a deviation of the filter capacitances from
the value parameterized in p0221.
A change or a defect of the line filter capacitors results in a shift of the resonant frequencies and can result in severe damage
to the drive system.
Alarm value (r2124, floating point):
The currently calculated capacitance in µF (rounded-off to an integer number).
Note:
The first decimal point specifies the number of the phase (1, 2, 3) where the capacitance deviates from the specified value.
Remedy:
- check the parameterized value of the filter capacitance (p0221).
- check the correct wiring of the VSM:
Differential voltages u12 and u23 must be available at the 100 V/690 V inputs of the VSM.
The phase currents of the line filter must be available at the 10 V inputs via a current-voltage transformer.
- check the alarm limits for the permissible filter capacitance deviation (p3676).
- check the scaling of the line supply voltage measurement using the VSM (p3660).
- check the scaling of the filter current measurement using the VSM (p3670).
- check the line filter capacitors and if required, replace the line filter.
For a parallel connection of power units, the following applies:
- parameter r3677[0...2] indicates the average value of all filter capacitances.
- parameters r7320[0...n], r7321[0...n] and r7322[0...n] indicate the capacitance of each individual filter. The defective
filter can be localized by the particular VSM.
Note:
VSM: Voltage Sensing Module
See also: p0221, p3660, p3670, p3676
206255
<location>Infeed: temperature threshold value not permissible
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
At least one temperature threshold value is set outside the permissible value range.
For sensor type KTY84 (p3665 = 2) or PT1000 (p3665 = 6), the value range from 181 °C to 300 °C is not permissible.
Fault value (r0949, interpret bitwise binary):
The bit number corresponds to the number of the Voltage Sensing Module (VSM) involved.
Bit 0:
The value in p3667/p3668 is outside the permissible value range.
For liquid-cooled Active Interface Modules (AIM, see p0220), the value range between 71 °C and 300 °C is also not
permissible.
Bit 1:
The value in p5467[0]/p5468[0] is outside the permissible value range.
Bit 2:
The value in p5467[1]/p5468[1] is outside the permissible value range.
See also: p3667, p3668, p5467, p5468
Remedy:
Set the temperature thresholds within the measuring range.
Alarms
970
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
206260
<location>Infeed: Temperature in the line filter too high
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The temperature monitoring in the line filter has responded.
If the temperature remains too high during the complete monitoring time, this results in fault F06261.
Note:
The temperature monitoring is only available for an Active Interface Module.
Remedy:
- check whether the line filter type set in p0220[0] matches the line filter that is actually connected. Ensure that the line filter
specified for the infeed being used is connected or correct the setting of the line filter type in p0220[0].
- temperature monitoring is mandatory for AIM line filters (refer to p0220). Ensure that the line filter temperature switch is
correctly and reliably connected to input X21 of the infeed.
- reduce the ambient temperature of the line filter.
- reduce the load on the infeed and the filter module.
- check the magnitude of the line supply voltage.
- the internal fan of the filter module is defective. Replace the fan if necessary.
- defective temperature switch of the filter module. Replace the filter module if necessary.
206261
<location>Infeed: Temperature in the line filter permanently too high
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY
Cause:
After the temperature monitoring responded, the temperature in the line filter was permanently exceeded.
Note:
The temperature monitoring is only available for an Active Interface Module (AIM).
Remedy:
- check whether the line filter type set in p0220[0] matches the line filter that is actually connected. Ensure that the line filter
specified for the infeed being used is connected or correct the setting of the line filter type in p0220[0].
- temperature monitoring is mandatory for AIM line filters (refer to p0220). Ensure that the temperature switch in the line
filter is correctly and reliably connected to input X21 of the infeed.
- reduce the ambient temperature of the line filter.
- reduce the load on the infeed and the line filter.
- check the magnitude of the line supply voltage.
- the internal fan of the line filter is defective. Replace the fan if necessary.
- defective temperature switch of the line filter. Replace the line filter if necessary.
206262
<location>Infeed: Temperature switch in the line filter open when switching on
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY
Cause:
When switching on the infeed, the temperature in the line filter is too high. Switching on is prevented.
Remedy:
- check whether the line filter type set in p0220[0] matches the line filter that is actually connected. Ensure that the line filter
specified for the infeed being used is connected or correct the setting of the line filter type in p0220[0].
- temperature monitoring is mandatory for AIM line filters (refer to p0220). Ensure that the temperature switch in the line
filter is correctly and reliably connected to input X21 of the infeed.
- the filter temperature is too high. Allow the system to cool down.
- the internal fan of the line filter is defective. Replace the fan if necessary.
- defective temperature switch of the line filter. Replace the line filter if necessary.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
971
SINAMICS alarms
206300
<location>Infeed: Line voltage too high at power on
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The RMS line supply voltage Vrms was so high when switching on that controlled operation is not possible without
exceeding the permissible maximum voltage in the DC link (p0280).
Fault condition: Vrms * 1.5 > p0280.
Fault value (r0949, floating point):
Lowest possible controlled DC link voltage for the line supply voltage presently connected.
See also: p0280 (DC link voltage maximum steady-state)
Remedy:
- check the line supply voltage
- check the maximum DC link voltage and if required, increase (p0280).
- check the line supply voltage and compare with the actual line supply voltage (p0210).
- check whether the power unit is dimensioned for the line supply voltage actually being used.
See also: p0210, p0280
206301
<location>Infeed: Line supply overvoltage
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
Line supply voltage: %1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The filtered (steady-state) value of the rms line supply voltage Vrms is higher than the alarm threshold (p0281).
Alarm condition: Vrms > p0281 * p0210.
Alarm value (r2124, floating point):
Actual steady-state line supply voltage.
See also: p0281 (Line supply overvoltage alarm threshold)
Remedy:
- check the line supply.
- check the line supply voltage (p0210).
- check the alarm threshold (p0281).
See also: p0210, p0281
206310
<location>Infeed: Supply voltage (p0210) incorrectly parameterized
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
Line supply voltage: %1
Reaction:
NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
After precharging was completed, the line supply voltage Vrms was calculated using the measured DC link voltage. This
voltage Vrms is not within the tolerance range of the supply voltage.
The following applies for the tolerance range: 85 % * p0210 < Vrms < 110 % * p0210
Fault value (r0949, floating point):
Line supply voltage Vrms present.
See also: p0210
Remedy:
- check the parameterized supply voltage and if required change (p0210).
- check the line supply voltage.
See also: p0210
206310
<location>Supply voltage (p0210) incorrectly parameterized
Drive object:
SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Alarms
972
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
For AC/AC drive units, the measured DC voltage lies outside the tolerance range after precharging has been completed.
The following applies for the tolerance range: 1.16 * p0210 < r0070 < 1.6 * p0210
Note:
The fault can only be acknowledged when the drive is switched off.
See also: p0210
Remedy:
- check the parameterized supply voltage and if required change (p0210).
- check the line supply voltage.
See also: p0210
206311
<location>Infeed: Supply voltage (p0210) incorrect
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
Line supply voltage: %1
Reaction:
OFF2 (OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The line voltage nominal value indicated in p0210 is outside the nominal voltage range of the power unit.
After precharging was completed, the actual line supply voltage Vrms was calculated using the measured DC link voltage.
This voltage Vrms does not lie within the extended tolerance range of the supply voltage set in p0210.
The following applies for the extended tolerance range: 75 % * p0210 < Vrms < 120 % * p0210
Alarm value (r2124, floating point):
Line supply voltage Vrms present.
See also: p0210
Remedy:
- check the parameterized supply voltage and if required change (p0210).
- check the line supply voltage.
See also: p0210
206320
<location>Master/slave: 4-channel multiplexer control not valid
Drive object:
A_INF, A_INF_840, R_INF
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
Values 0, 1, 2, and 3 are valid to control the 4-channel multiplexer via connector input p3572.
In this case, an invalid value was identified. The control remains effective with the previous value.
Fault value (r0949, interpret decimal):
Invalid value to control the multiplexer.
See also: p3572 (Master/slave active current setpoint multiplexer selection)
Remedy:
- check the interconnection to control the multiplexer (CI: p3572).
- check the signal source signal value of the BICO interconnection.
See also: p3572 (Master/slave active current setpoint multiplexer selection)
206321
<location>Master/slave: 6-channel multiplexer control not valid
Drive object:
A_INF, A_INF_840, R_INF
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
973
SINAMICS alarms
Cause:
For the 6-channel multiplexer control via connector input p3577 an invalid value was identified. Values of 0, 1, 2, 3, 4 and
5 are valid. The control remains effective with the previous value.
Fault value (r0949, interpret decimal):
Invalid value used to control the multiplexer.
See also: p3577 (Master/slave current distribution factor multiplexer selection)
Remedy:
- check the interconnection to control the multiplexer (CI: p3577).
- check the signal source signal value of the BICO interconnection.
206350
<location>Infeed: Measured line frequency too high
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
Line frequency: %1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The actual line frequency f_line is higher than the parameterized alarm threshold (f_line > p0211 * p0284).
The alarm can be output in two operating states:
1. During the switch-on phase of the infeed unit.
Consequence:
Synchronization of the infeed to the line supply is interrupted and is restarted.
The alarm is reissued if the line frequency remains higher than the parameterized alarm threshold.
2. While the infeed is operational.
Consequence:
The infeed still remains in the operating state, alarm A06350 is output. This signifies a critical operational fault.
Alarm value (r2124, floating point):
Actual line frequency determined.
See also: p0284 (Line supply frequency exceeded alarm threshold)
Remedy:
- check the parameterized line frequency and if required change (p0211).
- check the alarm threshold (p0284).
- check the line supply.
- check the line supply quality.
See also: p0211, p0284
206351
<location>Infeed: Measured line frequency too low
Drive object:
A_INF, A_INF_840, R_INF, S_INF, S_INF_840
Message value:
Line frequency: %1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The actual line frequency f_line is lower than the parameterized alarm threshold (f_line < p0211 * p0285).
The alarm can be output in two operating states:
1. During the switch-on phase of the infeed unit.
Consequence:
Synchronization of the infeed to the line supply is interrupted and is restarted.
The alarm is reissued if the line frequency remains less than the parameterized alarm threshold.
2. While the infeed is operational.
Consequence:
The infeed remains in the "operating" (run) state and alarm A06351 is output. This signifies a critical operational fault.
Alarm value (r2124, floating point):
Actual line frequency determined.
See also: p0285 (Line supply frequency undershot alarm threshold)
Alarms
974
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

 

 

 

 

 

 

 

Content      ..     39      40      41      42     ..