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

SINAMICS alarms

Cause:

An error was detected when downloading a project using the commissioning software (e.g. incorrect parameter value). It

is possible that the parameter limits are dependent on other parameters.

The detailed cause of the fault can be determined using the fault value.

Fault value (r0949, interpret hexadecimal):

ccbbaaaa hex

aaaa = Parameter

bb = Index

cc = fault cause

0: Parameter number illegal.

1: Parameter value cannot be changed.

2: Lower or upper value limit exceeded.

3: Sub-index incorrect.

4: No array, no sub-index.

5: Data type incorrect.

6: Setting not permitted (only resetting).

7: Descriptive element cannot be changed.

9: Descriptive data not available.

11: No master control.

15: No text array available.

17: Task cannot be executed due to operating state.

20: Illegal value.

21: Response too long.

22: Parameter address illegal.

23: Format illegal.

24: Number of values not consistent.

25: Drive object does not exist.

101: Presently deactivated.

104: Illegal value.

107: Write access not permitted when controller enabled.

108: Unit unknown.

109: Write access only in the commissioning state, encoder (p0010 = 4).

110: Write access only in the commissioning state, motor (p0010 = 3).

111: Write access only in the commissioning state, power unit (p0010 = 2).

112: Write access only in the quick commissioning mode (p0010 = 1).

113: Write access only in the ready mode (p0010 = 0).

114: Write access only in the commissioning state, parameter reset (p0010 = 30).

115: Write access only in the Safety Integrated commissioning state (p0010 = 95).

116: Write access only in the commissioning state, technological application/units (p0010 = 5).

117: Write access only in the commissioning state (p0010 not equal to 0).

118: Write access only in the commissioning state, download (p0010 = 29).

119: Parameter may not be written in download.

120: Write access only in the commissioning state, drive basic configuration (device: p0009 = 3).

121: Write access only in the commissioning state, define drive type (device: p0009 = 2).

122: Write access only in the commissioning state, data set basic configuration (device: p0009 = 4).

123: Write access only in the commissioning state, device configuration (device: p0009 = 1).

124: Write access only in the commissioning state, device download (device: p0009 = 29).

125: Write access only in the commissioning state, device parameter reset (device: p0009 = 30).

126: Write access only in the commissioning state, device ready (device: p0009 = 0).

127: Write access only in the commissioning state, device (device: p0009 not equal to 0).

129: Parameter may not be written in download.

130: Transfer of the master control is inhibited via binector input p0806.

131: Required BICO interconnection not possible because BICO output does not supply floating value

Alarms

768

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

132: Free BICO interconnection inhibited via p0922.

133: Access method not defined.

200: Below the valid values.

201: Above the valid values.

202: Cannot be accessed from the Basic Operator Panel (BOP).

203: Cannot be read from the Basic Operator Panel (BOP).

204: Write access not permitted.

Remedy:

- correct the parameterization in the commissioning tool and download the project again.

- enter the correct value in the specified parameter.

- identify the parameter that restricts the limits of the specified parameter.

201043

<location>Fatal error at project download

Drive object:

All objects

Message value:

Fault cause: %1

Reaction:

Infeed: NONE (OFF1, OFF2)

Servo: NONE (OFF1, OFF2, OFF3)

Vector: NONE (OFF1, OFF2, OFF3)

Hla: NONE (OFF1, OFF2, OFF3)

Acknowledge:

IMMEDIATELY

Cause:

A fatal error was detected when downloading a project using the commissioning tool.

Fault value (r0949, interpret decimal):

1: Device status cannot be changed to Device Download (drive object ON?).

2: Incorrect drive object number.

3: A drive object that has already been deleted is deleted again.

4: Deleting a drive object that has already been registered for generation.

5: Deleting a drive object that does not exist.

6: Generating an undeleted drive object that already existed.

7: Regenerating a drive object already registered for generation.

8: Maximum number of drive objects that can be generated exceeded.

9: Error while generating a device drive object.

10: Error while generating target topology parameters (p9902 and p9903).

11: Error when generating a drive object (global component).

12: Error when generating a drive object (drive component).

13: Unknown drive object type.

14: Drive status cannot be changed to "ready for operation" (r0947 and r0949).

15: Drive status cannot be changed to drive download.

16: Device status cannot be changed to "ready for operation".

17: It is not possible to download the topology. The component wiring should be checked, taking into account the various

messages/signals.

18: A new download is only possible if the factory settings are restored for the drive unit.

19: The slot for the option module has been configured several times (e.g. CAN and COMM BOARD)

20: The configuration is inconsistent (e.g. CAN for Control Unit, however no CAN configured for drive objects A_INF, SERVO

or VECTOR).

21: Error when accepting the download parameters.

22: Software-internal download error.

23: download not possible when know-how protection is activated.

24: download not possible during a partial power up after inserting a component.

25: The configuration is inconsistent. Know-how protection is either not activated or only partially.

Additional values:

Only for internal Siemens troubleshooting.

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

769

SINAMICS alarms

Remedy:

- use the current version of the commissioning tool.

- modify the offline project and carry out a new download (e.g. compare the number of drive objects, motor, encoder, power

unit in the offline project and at the drive).

- change the drive state (is a drive rotating or is there a message/signal?).

- Observe additional active messages/signals and remove their cause (e.g. correct any incorrectly set parameters).

- automatically calculate the control parameters (p0340). Then set p0010 = 0.

- boot from previously saved files (switch-off/switch-on or p0976).

- before a new download, restore the factory setting if the know-how protection was not activated on all drive objects.

201044

<location>CU: Descriptive data error

Drive object:

All objects

Message value:

Reaction:

OFF2

Acknowledge:

POWER ON

Cause:

An error was detected when loading the descriptive data saved in the non-volatile memory.

Remedy:

Replace the memory card or Control Unit.

201045

<location>CU: Configuring data invalid

Drive object:

All objects

Message value:

Reaction:

NONE

Acknowledge:

NONE

Cause:

An error was detected when evaluating the parameter files PSxxxyyy.ACX, PTxxxyyy.ACX, CAxxxyyy.ACX, or CCxxxyyy.ACX

saved in the non-volatile memory. Because of this, under certain circumstances, several of the saved parameter values were

not able to be accepted.

Also see r9406 up to r9408.

Alarm value (r2124, interpret hexadecimal):

Only for internal Siemens troubleshooting.

Remedy:

- check the parameters displayed in r9406 up to r9408, and correct these if required.

- Restore the factory setting (p0976 = 1) and reload the project into the converter.

Then save the parameterization in STARTER using the function "Copy RAM to ROM" or with p0977 = 1. This overwrites the

incorrect parameter files in the non-volatile memory - and this alarm is withdrawn.

See also: p0097, r0098, p0099

201331

<location>Topology: At least one component not assigned to a drive object

Drive object:

All objects

Message value:

Component number: %1

Reaction:

NONE

Acknowledge:

NONE

Cause:

At least one component is not assigned to a drive object.

- when commissioning, a component was not able to be automatically assigned to a drive object.

- the parameters for the data sets are not correctly set.

Alarm value (r2124, interpret decimal):

Component number of the unassigned component.

Remedy:

This component is assigned to a drive object.

Check the parameters for the data sets.

Examples:

- power unit (p0121).

- motor (p0131, p0186).

- encoder interface (p0140, p0141, p0187 ... p0189).

- encoder (p0140, p0142, p0187 ... p0189).

- Terminal Module (p0151).

- option board (p0161).

201340

<location>Topology: Too many components on one line

Drive object:

All objects

Message value:

Component number or connection number: %1, fault cause: %2

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Alarms

794

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Cause:

For the selected communications clock cycle, too many DRIVE-CLiQ components are connected to one line of the Control

Unit.

Fault value (r0949, interpret hexadecimal):

xyy hex: x = fault cause, yy = component number or connection number.

1yy:

The communications clock cycle of the DRIVE-CLiQ connection on the Control Unit is not sufficient for all read transfers.

2yy:

The communications clock cycle of the DRIVE-CLiQ connection on the Control Unit is not sufficient for all write transfers.

3yy:

Cyclic communication is fully utilized.

4yy:

The DRIVE-CLiQ cycle starts before the earliest end of the application. An additional dead time must be added to the control.

Sign-of-life errors can be expected.

The conditions of operation with a current controller sampling time of 31.25 µs have not been maintained.

5yy:

Internal buffer overflow for net data of a DRIVE-CLiQ connection.

6yy:

Internal buffer overflow for receive data of a DRIVE-CLiQ connection.

7yy:

Internal buffer overflow for send data of a DRIVE-CLiQ connection.

8yy:

The component clock cycles cannot be combined with one another

900:

The lowest common multiple of the clock cycles in the system is too high to be determined.

901:

The lowest common multiple of the clock cycles in the system cannot be generated with the hardware.

Remedy:

- check the DRIVE-CLiQ wiring.

- reduce the number of components on the DRIVE-CLiQ line involved and distribute these to other DRIVE-CLiQ sockets of the

Control Unit. This means that communication is uniformly distributed over several lines.

For fault value = 1yy - 4yy in addition:

- increase the sampling times (p0112, p0115, p4099). If necessary, for DCC or FBLOCKS, change the assignment of the

runtime group (p21000, p20000) so that the sampling time (r21001, r20001) is increased.

- if necessary, reduce the number of cyclically calculated blocks (DCC) and/or function blocks (FBLOCKS).

- reduce the function modules (r0108).

- establish the conditions for operation with a current controller sampling time of 31.25 µs (at the DRIVE-CLiQ line, only

operate Motor Modules and Sensor Modules with this sampling time and only use a permitted Sensor Module (e.g. SMC20,

this means a 3 at the last position of the Article No.)).

- For an NX, the corresponding Sensor Module for a possibly existing second measuring system should be connected to a

free DRIVE-CLiQ socket of the NX.

- for BSR Motor Modules, the following applies: If Safety Extended Functions is enabled, and 6 axes are operated on the

DRIVE-CLiQ line, then the clock cycle for the actual value sensing must be set as follows: p9511 >= 8 * current controller

sampling time (p0115[0]).

For fault value = 8yy in addition:

- check the clock cycles settings (p0112, p0115, p4099). Clock cycles on a DRIVE-CLiQ line must be perfect integer multiples

of one another. As clock cycle on a line, all clock cycles of all drive objects in the previously mentioned parameters apply,

which have components on the line involved.

For fault value = 9yy in addition:

- check the clock cycles settings (p0112, p0115, p4099). The lower the numerical value difference between two clock cycles,

the higher the lowest common multiple. This behavior has a significantly stronger influence, the higher the numerical

values of the clock cycles.

201341

<location>Topology: Maximum number of DRIVE-CLiQ components exceeded

Drive object:

All objects

Message value:

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

795

SINAMICS alarms

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Cause:

Too many DRIVE-CLiQ components were defined in the actual topology.

Note:

Pulse enable is withdrawn and prevented.

Remedy:

- check the DRIVE-CLiQ wiring.

- reduce the number components on the DRIVE-CLiQ line involved in order to maintain the maximum quantity structure.

201354

<location>Topology: Actual topology indicates an illegal component

Drive object:

All objects

Message value:

Fault cause: %1, component number: %2

Reaction:

OFF2

Acknowledge:

IMMEDIATELY

Cause:

The actual topology indicates at least one illegal component.

Fault value (r0949, interpret hexadecimal):

yyxx hex: yy = component number, xx = cause.

xx = 1: Component at this Control Unit not permissible.

xx = 2: Component in combination with another component not permissible.

Note:

Pulse enable is prevented.

Remedy:

Remove the illegal components and restart the system.

201355

<location>Topology: Actual topology changed

Drive object:

All objects

Message value:

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Cause:

The device target topology (p0099) does not correspond to the device actual topology (r0098).

The fault only occurs if the topology was commissioned using the automatic internal device mechanism and not using the

commissioning tool.

Fault value (r0949, interpret decimal):

Only for internal Siemens troubleshooting.

See also: r0098 (Actual device topology), p0099 (Device target topology)

Alarms

796

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Remedy:

One of the following counter-measures can be selected if no faults have occurred in the topology detection itself:

If commissioning is still not completed:

- carry out a self-commissioning routine (starting from p0009 = 1).

In general:

Set p0099 = r0098, set p0009 = 0; for existing Motor Modules, this results in servo drives being automatically generated

(p0107).

Generating servo drives: Set p0097 to 1, set p0009 to 0.

Generating vector drives: Set p0097 to 2, set p0009 to 0.

Generating vector drives with parallel connection: set p0097 to 12, set p0009 to 0.

In order to set configurations in p0108, before setting p0009 to 0, it is possible to first set p0009 to 2 and modify p0108. The

index corresponds to the drive object (p0107).

If commissioning has already been completed:

- re-establish the original connections and re-connect power to the Control Unit.

- restore the factory setting for the complete equipment (all of the drives) and allow automatic self-commissioning again.

- change the device parameterization to match the connections (this is only possible using the commissioning tool).

Notice:

Topology changes that result in this fault being generated cannot be accepted by the automatic function in the device, but

must be transferred using the commissioning tool and parameter download. The automatic function in the device only

allows constant topology to be used. Otherwise, when the topology is changed, all of the previous parameter settings are

lost and replaced by the factory setting.

See also: r0098 (Actual device topology)

201356

<location>Topology: There is a defective DRIVE-CLiQ component

Drive object:

All objects

Message value:

Fault cause: %1, Component number: %2, Connection number: %3

Reaction:

NONE (OFF2)

Acknowledge:

IMMEDIATELY

Cause:

The actual topology indicates at least one defective DRIVE-CLiQ component.

Fault value (r0949, interpret hexadecimal):

zzyyxx hex:

zz = connection number of the component at which the defective component is connected

yy = component number of the component at which the defective component is connected

xx = fault cause

xx = 1: Component at this Control Unit not permissible.

xx = 2: component with communication defect.

Note:

Pulse enable is withdrawn and prevented.

Remedy:

Replace the defective component and restart the system.

201357

<location>Topology: Two Control Units identified on the DRIVE-CLiQ line

Drive object:

All objects

Message value:

component number: %1, connection number: %2

Reaction:

NONE (OFF2)

Acknowledge:

IMMEDIATELY

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

797

SINAMICS alarms

Cause:

In the actual topology, 2 Control Units are connected with one another through DRIVE-CLiQ.

As standard, this is not permitted.

This is only permitted if the Technology Extension OALINK has already been installed on the two Control Units and has been

commissioned online.

Fault value (r0949, interpret hexadecimal):

yyxx hex:

yy = connection number of the Control Unit at which the second Control Unit is connected

xx = component number of the Control Unit at which the second Control Unit is connected

Note:

Pulse enable is withdrawn and prevented.

Remedy:

In general:

- remove the connection to the second Control Unit and restart.

- for the S120M component DRIVE-CLiQ extension, interchange the hybrid cable (IN/OUT).

When using OALINK:

- remove the DRIVE-CLiQ connection and restart the systems.

- install OALINK on both Control Units and activate.

- Check the configuration of the DRIVE-CLiQ sockets in OALINK.

201358

<location>Topology: Line termination not available

Drive object:

All objects

Message value:

CU connection number: %1, component number: %2, connection number: %3

Reaction:

NONE

Acknowledge:

NONE

Cause:

At least one line with distributed drives is not terminated. The last participant on the line must be terminated with a line

termination connector.

This therefore ensures the degree of protection of the distributed drives.

Alarm value (r2124, interpret hexadecimal):

zzyyxx hex:

zz = connection number of the distributed drive where there is no terminating connector

yy = component number

xx = CU connection number

Remedy:

Install the line terminating connector for the last distributed drive.

201359

<location>Topology: DRIVE-CLiQ performance not sufficient

Drive object:

All objects

Message value:

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Cause:

The DRIVE-CLiQ performance is not sufficient at one line in order to identify an inserted component.

Fault value (r0949, interpret hexadecimal):

Only for internal Siemens troubleshooting.

Remedy:

- carry out a POWER ON (switch-off/switch-on).

- Distribute components across several DRIVE-CLiQ lines.

Note:

For this topology, do not withdraw and insert components in operation.

201360

<location>Topology: Actual topology not permissible

Drive object:

All objects

Message value:

Fault cause: %1, preliminary component number: %2

Reaction:

NONE

Alarms

798

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Acknowledge:

IMMEDIATELY

Cause:

The detected actual topology is not permissible.

Fault value (r0949, interpret hexadecimal):

ccccbbaa hex:

cccc = preliminary component number, bb = no significance, aa = fault cause

aa = 01 hex = 1 dec:

Too many components were detected at the Control Unit. A maximum of 199 components is permissible.

aa = 02 hex = 2 dec:

The component type of a component is not known.

aa = 03 hex = 3 dec:

It is illegal to combine ALM and BLM.

aa = 04 hex = 4 dec:

It is illegal to combine ALM and SLM.

aa = 05 hex = 5 dec:

It is illegal to combine BLM and SLM.

aa = 06 hex = 6 dec:

A CX32 was not directly connected to a permitted Control Unit.

aa = 07 hex = 7 dec:

An NX10 or NX15 was not directly connected to a permitted Control Unit.

aa = 08 hex = 8 dec:

A component was connected to a Control Unit that is not permitted for this purpose.

aa = 09 hex = 9 dec:

A component was connected to a Control Unit with out-of-date firmware.

aa = 0A hex = 10 dec:

Too many components of a particular type detected.

aa = 0B hex = 11 dec:

Too many components of a particular type detected on a single line.

Note:

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

For fault cause = 1:

Change the configuration. Connect less than 199 components to the Control Unit.

For fault cause = 2:

Remove the component with unknown component type.

For fault cause = 3, 4, 5:

Establish a valid combination.

For fault cause = 6, 7:

Connect the expansion module directly to a permitted Control Unit.

For fault cause = 8:

Remove component or use a permissible component.

For fault cause = 9:

Upgrade the firmware of the Control Unit to a later version.

For fault cause = 10, 11:

Reduce the number of components.

201361

<location>Topology: Actual topology contains SINUMERIK and SIMOTION components

Drive object:

All objects

Message value:

Reaction:

NONE

Acknowledge:

NONE

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

799

SINAMICS alarms

Cause:

The detected actual topology contains SINUMERIK and SIMOTION components.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex: cc = fault cause, bb = component class of the actual topology, aa = component number of the component

cc = 01 hex = 1 dec:

An NX10 or NX15 was connected to a SIMOTION control.

cc = 02 hex = 2 dec:

A CX32 was connected to a SINUMERIK control.

Remedy:

For alarm value = 1:

Replace all NX10 or NX15 by a CX32.

For alarm value = 2:

Replace all CX32 by an NX10 or NX15.

201362

<location>Topology: Topology rule(s) broken

Drive object:

All objects

Message value:

Reaction:

NONE

Acknowledge:

NONE

Alarms

800

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Cause:

At least one topology rule for the SINAMICS S120 Combi has been broken.

In the event of a fault, the ramping up of the drive system is aborted and closed-loop drive control is not enabled.

Alarm value (r2124, interpret decimal):

The alarm value indicates which rule has been violated.

1: The S120 Combi may only be wired via DRIVE-CLiQ socket X200 to X100 on the NCU.

2: In DRIVE-CLiQ socket X101 on the NCU, only one Single Motor Module (SMM) may be connected via X200, one Double

Motor Module (DMM) via X200, one Terminal Module 54F (TM54F) via X500 or one DRIVE-CLiQ Hub Module (DMC20,

DME20) via X500.

3: In DRIVE-CLiQ socket X102 on the NCU, only one Terminal Module 54F (TM54F) may be connected via X500, one DRIVE-

CLiQ Hub Module (Hub) via X500 or one NX15 via X100.

4: Only Sensor Modules may be connected to DRIVE-CLiQ sockets X201 up to X203 (3-axis) or X204 (4-axis) on the S120

Combi.

5: In DRIVE-CLiQ socket X205 (X204 is not available for 3 axes), only SMC / SME Sensor Modules and DRIVE-CLiQ encoders

may be connected.

6: In the case of a Single Motor Module as first expansion axis, only one additional Single Motor Module may be connected

in the DRIVE-CLiQ socket X201 via X200, one Terminal Module 54F (TM54F) via X500 or one DRIVE-CLiQ Hub Module

(DMC20, DME20) via X500.

7: Only Sensor Modules or DRIVE-CLiQ encoders may be connected in the DRIVE-CLiQ socket X202 on possibly available

Single Motor Modules.

8: For a second Single Motor Module or for a Double Motor Module, at X201 a 54F Terminal Module (TM54F) or a DRIVE-CLiQ

Hub Module (DMC 20, DME 20) may be connected via X500.

9: If a Double Motor Module is used as an expansion axis, only Sensor Modules may be connected to X202 and X203.

10: If a Terminal Module 54F (TM54F) is configured, only one DRIVE-CLiQ Hub Module (DMC20, DME20) may be connected

to X501 of the TM54F module via DRIVE-CLiQ socket X500. In this case, it is not permissible that an existing Hub Module is

connected elsewhere.

11: For DRIVE-CLiQ Hub Modules, only Sensor Modules (SMC, SME) and DRIVE-CLiQ encoders may be connected to X501

to X505.

12: Only certain Motor Modules may be used for expansion axes.

13: For an S120 Combi with 3 axes, nothing must be connected at the DRIVE-CLiQ Hub Module at X503.

14: A maximum of one Terminal Module 54F (TM54F) is permitted.

15: A maximum of one DRIVE-CLiQ Hub Module (DMC20, DME20) is permitted.

16: DRIVE-CLiQ socket X100 of NX15 must be connected with the NCU via X102.

17: The S120 Combi may only be connected to X101 of the NX15 via the DRIVE-CLiQ socket X200.

18: In DRIVE-CLiQ socket X102 on the NX15, only one Single Motor Module (SMM) may be connected via X200, one Double

Motor Module (DMM) via X200, one Terminal Module 54F (TM54F) via X500 or one DRIVE-CLiQ Hub Module (DMC20,

DME20) via X500.

19: It is not permissible that anything is connected at DRIVE-CLiQ socket X103 on the NX15.

Remedy:

Evaluate the alarm value and ensure compliance with the corresponding topology rule(s).

201375

<location>Topology: Connection duplicated between two components

Drive object:

All objects

Message value:

Component: %1, %2, connection: %3

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

801

SINAMICS alarms

Cause:

When checking the actual topology, a ring-type connection was detected.

The fault value describes a component contained in the ring.

Fault value (r0949, interpret hexadecimal):

ccbbaaaa hex:

cc = connection number (%3)

bb = component class (% 2)

aaaa = preliminary component number (%1)

Component class:

0: Component unknown.

1: Control Unit

2: Motor Module

3: Line Module

4: Sensor Module

5: Voltage Sensing Module

6: Terminal Module

7: DRIVE-CLiQ Hub Module

8: Controller Extension

9: Filter Module

10: Hydraulic Module.

49: DRIVE-CLiQ component

50: Option slot

60: Encoder

70: DRIVE-CLiQ motor

71: Hydraulic cylinder

72: Hydraulic valve

80: Motor

Connection number:

0: Port 0, 1: Port 1, 2: Port 2, 3: Port 3, 4: Port 4, 5: Port 5

10: X100, 11: X101, 12: X102, 13: X103, 14: X104, 15: X105

20: X200, 21: X201, 22: X202, 23: X203

50: X500, 51: X501, 52: X502, 53: X503, 54: X504, 55: X505

Remedy:

Output the fault value and remove the specified connection.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201380

<location>Topology: Actual topology EEPROM defective

Drive object:

All objects

Message value:

Preliminary component number: %1

Reaction:

NONE

Acknowledge:

POWER ON

Cause:

When detecting the actual topology, a component with a defective EEPROM was detected.

Fault value (r0949, interpret hexadecimal):

bbbbaaaa hex:

bbbb = reserved

aaaa = preliminary component number of the defective components

Remedy:

Output the fault value and remove the defected component.

201381

<location>Topology: Line Module incorrectly inserted

Drive object:

A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840

Message value:

Component: %1, to %2, %3, connection: %4

Alarms

802

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a Line Module in the actual topology that has been incorrectly inserted with respect

to the target technology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201381

<location>Topology: power unit incorrectly inserted

Drive object:

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, TB30, TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM54F_MA, TM54F_SL

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a power unit in the actual topology that has been incorrectly inserted.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201381

<location>Topology: Motor Module incorrectly inserted

Drive object:

SERVO, SERVO_840, SERVO_AC, TM41, VECTOR, VECTOR_AC

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

803

SINAMICS alarms

Acknowledge:

NONE

Cause:

The topology comparison has detected a Motor Module in the actual topology that has been incorrectly inserted with

respect to the target technology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201382

<location>Topology: Sensor Module incorrectly inserted

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a Sensor Module in the actual topology that has been incorrectly inserted with

respect to the target technology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201383

<location>Topology: Terminal Module incorrectly inserted

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Alarms

804

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Cause:

The topology comparison has detected a Terminal Module in the actual topology that has been incorrectly inserted with

respect to the target technology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201384

<location>Topology: DRIVE-CLiQ Hub Module incorrectly inserted

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a DRIVE-CLiQ Hub Module in the actual topology that has been incorrectly inserted

with respect to the target topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201385

<location>Topology: Controller Extension incorrectly inserted

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

805

SINAMICS alarms

Cause:

The topology comparison has detected a controller extension 32 (CX32) in the actual topology that has been incorrectly

inserted with respect to the target topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201386

<location>Topology: DRIVE-CLiQ component incorrectly inserted

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a DRIVE-CLiQ component in the actual topology that has been incorrectly inserted

with respect to the target topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201389

<location>Topology: Motor with DRIVE-CLiQ incorrectly inserted

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Alarms

806

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Cause:

The topology comparison has detected a motor with DRIVE-CLiQ in the actual topology that has been incorrectly inserted

with respect to the target topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the incorrectly inserted component (% 1)

Note:

The component is described in dd, cc and bb, where the component involved is incorrectly inserted.

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201416

<location>Topology: Component additionally inserted

Drive object:

All objects

Message value:

%1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has found a component in the actual topology which is not specified in the target topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = component class (% 2)

cc = connection number (%4)

bb = component class of the additional component (%1)

aa = component number (%3)

Note:

The component class of the additional component is contained in bb.

The component is described in dd, cc and aa, where the additional component is inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- remove the additional component (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201420

<location>Topology: Component different

Drive object:

All objects

Message value:

Component: %1, target: %2, actual: %3, difference: %4

Reaction:

NONE

Acknowledge:

NONE

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

807

SINAMICS alarms

Cause:

The topology comparison has detected differences in the actual topology and target topologies in the electronic rating plate.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex: aa = component number (%1), bb = component class of the target topology (%2), cc = component class of

the actual topology (%3), dd = difference (%4)

dd = 01 hex = 1 dec:

Different component type.

dd = 02 hex = 2 dec:

Different article number.

dd = 03 hex = 3 dec:

Different manufacturer.

dd = 04 hex = 4 dec:

For a multi-component slave, the incorrect subcomponent (index) is connected (e.g. Double Motor Module X201 instead

of X200) - or only a part of a multi-component slave is set to "deactivate and not available".

dd = 05 hex = 5 dec:

NX10 or NX15 used instead of CX32.

dd = 06 hex = 6 dec:

NX10 or NX15 used instead of CX32.

dd = 07 hex = 7 dec:

Different number of connections.

Note:

The component class is described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- connect the expected component (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Topology comparison - if required, adapt the comparison level:

- parameterize the topology comparison of all components (p9906).

- parameterize the topology comparison of one components (p9907, p9908).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201425

<location>Topology: Serial number different

Drive object:

All objects

Message value:

Component: %1, %2, differences: %3

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected differences in the actual and target topologies in relation to one component. The

serial number is different.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = reserved

cc = number of differences (%3)

bb = component class (% 2)

aa = component number (%1)

Note:

The component class is described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Alarms

808

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Remedy:

Adapting topologies:

- change over the actual topology to match the target topology.

- load the target topology that matches the actual topology (commissioning tool).

For byte cc:

cc = 1 --> can be acknowledged using p9904 or p9905.

cc > 1 --> can be acknowledged using p9905 and can be deactivated using p9906 or p9907/p9908.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

See also: p9904, p9905, p9906, p9907, p9908

201428

<location>Topology: Incorrect connection used

Drive object:

All objects

Message value:

Component: %1, %2, connection (actual): %3, connection (target): %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected differences in the actual and target topologies in relation to one component. For a

component, another connection was used.

The different connections of a component are described in the alarm value.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number of the target topology (%4)

cc = connection number of the actual topology (%3)

bb = component class (% 2)

aa = component number (%1)

Note:

Component class and connection number are described in F01375.

The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

Remedy:

Adapting topologies:

- reinsert the DRIVE-CLiQ cable to the component (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

- automatically remove the topology error (p9904).

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

See also: p9904 (Topology comparison acknowledge differences)

201451

<location>Topology: Target topology is invalid

Drive object:

All objects

Message value:

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

809

SINAMICS alarms

Cause:

An error was detected in the target topology.

The target topology is invalid.

Fault value (r0949, interpret hexadecimal):

ccccbbaa hex: cccc = index error, bb = component number, aa = fault cause

aa = 1B hex = 27 dec: Error not specified.

aa = 1C hex = 28 dec: Value illegal.

aa = 1D hex = 29 dec: Incorrect ID.

aa = 1E hex = 30 dec: Incorrect ID length.

aa = 1F hex = 31 dec: Too few indices left.

aa = 20 hex = 32 dec: component not connected to Control Unit.

Remedy:

Download the target topology again using the commissioning tool.

201481

<location>Topology: power unit not connected

Drive object:

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, TB30, TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM54F_MA, TM54F_SL

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a power unit that is missing in the actual topology with respect to the target topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201481

<location>Topology: Line Module not connected

Drive object:

A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Alarms

810

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Cause:

The topology comparison has detected a Line Module that is missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201481

<location>Topology: Motor Module not connected

Drive object:

SERVO, SERVO_840, SERVO_AC, TM41, VECTOR, VECTOR_AC

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a Motor Module that is missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201482

<location>Topology: Sensor Module not connected

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

811

SINAMICS alarms

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a Sensor Module that is missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201483

<location>Topology: Terminal Module not connected

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a Terminal Module that is missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

Alarms

812

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

201484

<location>Topology: DRIVE-CLiQ Hub Module not connected

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a DRIVE-CLiQ Hub Module missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201485

<location>Topology: Controller Extension not connected

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a Control Extension (CX32) missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

813

SINAMICS alarms

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201486

<location>Topology: DRIVE-CLiQ component not connected

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a DRIVE-CLiQ component missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201487

<location>Topology: Option slot component not inserted

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Alarms

814

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Cause:

The topology comparison has detected an option slot component missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201489

<location>Topology: motor with DRIVE-CLiQ not connected

Drive object:

All objects

Message value:

Component: %1, to %2, %3, connection: %4

Reaction:

NONE

Acknowledge:

NONE

Cause:

The topology comparison has detected a motor with DRIVE-CLiQ missing in the actual topology with respect to the target

topology.

Alarm value (r2124, interpret hexadecimal):

ddccbbaa hex:

dd = connection number (%4)

cc = component number (%3)

bb = component class (% 2)

aa = component number of the component that has not been inserted (% 1)

Note:

The component is described in dd, cc and bb, where the component has not been inserted.

Component class and connection number are described in F01375.

Remedy:

Adapting topologies:

- insert the components involved at the right connection (correct the actual topology).

- adapt the project/parameterizing in the commissioning tool (correct the target topology).

Check the hardware:

- check the 24 V supply voltage.

- check DRIVE-CLiQ cables for interruption and contact problems.

- check that the component is working properly.

Note:

Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.

setpoint/actual value comparison).

201507

<location>BICO: Interconnections to inactive objects present

Drive object:

All objects

Message value:

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

815

SINAMICS alarms

Reaction:

NONE

Acknowledge:

NONE

Cause:

There are BICO interconnections to an inactive/inoperable drive object.

The BI/CI parameters involved are listed in r9498.

The associated BO/CO parameters are listed in r9499.

The list of the BICO interconnections to other drive objects is displayed in r9491 and r9492 of the deactivated drive object.

Note:

r9498 and r9499 are only written to, if p9495 is not set to 0.

Alarm value (r2124, interpret decimal):

Number of BICO interconnections found to inactive drive objects.

Remedy:

- set all open BICO interconnections centrally to the factory setting with p9495 = 2.

- make the non-operational drive object active/operational again (re-insert or activate components).

201508

<location>BICO: Interconnections to inactive objects exceeded

Drive object:

All objects

Message value:

Reaction:

NONE

Acknowledge:

NONE

Cause:

The maximum number of BICO interconnections (signal sinks) when deactivating a drive object was exceeded.

When deactivating a drive object, all BICO interconnections (signal sinks) are listed in the following parameters:

- r9498[0...29]: List of the BI/CI parameters involved.

- r9499[0...29]: List of the associated BO/CO parameters.

Remedy:

Not necessary.

This alarm is automatically withdrawn as soon as no BICO interconnection is entered in r9498[29] and r9499[29] (value =

0).

Notice:

When re-activating the drive object, all BICO interconnections should be checked and if required, re-established.

201510

<location>BICO: Signal source is not float type

Drive object:

All objects

Message value:

Parameter: %1

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Cause:

The requested connector output does not have the correct data type. This interconnection is not established.

Fault value (r0949, interpret decimal):

Parameter number to which an interconnection should be made (connector output).

Remedy:

Interconnect this connector input with a connector output having a float data type.

201511

<location>BICO: Interconnection with different scalings

Drive object:

All objects

Message value:

Parameter: %1

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Alarms

816

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Cause:

The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO

input using the reference values.

- the BICO output has different normalized units than the BICO input.

- message only for interconnections within a drive object.

Example:

The BICO output has, as normalized unit, voltage and the BICO input has current.

This means that the factor p2002/p2001 is calculated between the BICO output and the BICO input.

p2002: contains the reference value for current

p2001: contains the reference value for voltage

Fault value (r0949, interpret decimal):

Parameter number of the BICO input (signal sink).

Remedy:

Not necessary.

201512

<location>BICO: No scaling available

Drive object:

All objects

Message value:

Reaction:

Infeed: OFF2 (OFF1)

Servo: OFF2

Vector: OFF2

Hla: OFF2

Acknowledge:

POWER ON

Cause:

An attempt was made to determine a conversion factor for a scaling that does not exist.

Fault value (r0949, interpret decimal):

Unit (e.g. corresponding to SPEED) for which an attempt was made to determine a factor.

Remedy:

Apply scaling or check the transfer value.

201513

<location>BICO: Interconnection cross DO with different scalings

Drive object:

All objects

Message value:

Parameter: %1

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Cause:

The requested BICO interconnection was established. However, a conversion is made between the BICO output and BICO

input using the reference values.

An interconnection is made between different drive objects and the BICO output has different normalized units than the

BICO input or the normalized units are the same but the reference values are different.

Example 1:

BICO output with voltage normalized unit, BICO input with current normalized unit, BICO output and BICO input lie in

different drive objects. This means that the factor p2002/p2001 is calculated between the BICO output and the BICO input.

p2002: contains the reference value for current

p2001: contains the reference value for voltage

Example 2:

BICO output with voltage normalized unit in drive object 1 (DO1), BICO input with voltage normalized unit in drive object

2 (DO2). The reference values for voltage (p2001) of the two drive objects have different values. This means that the factor

p2001(DO1)/p2001(DO2) is calculated between the BICO output and the BICO input.

p2001: contains the reference value for voltage, drive objects 1, 2

Fault value (r0949, interpret decimal):

Parameter number of the BICO input (signal sink).

Remedy:

Not necessary.

201514

<location>BICO: Error when writing during a reconnect

Drive object:

All objects

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

817

SINAMICS alarms

Message value:

Parameter: %1

Reaction:

NONE

Acknowledge:

NONE

Cause:

During a reconnect operation (e.g. while booting or downloading - but can also occur in normal operation) a parameter was

not able to be written to.

Example:

When writing to BICO input with double word format (DWORD), in the second index, the memory areas overlap (e.g. p8861).

The parameter is then reset to the factory setting.

Alarm value (r2124, interpret decimal):

Parameter number of the BICO input (signal sink).

Remedy:

Not necessary.

201515

<location>BICO: Writing to parameter not permitted as the master control is active

Drive object:

All objects

Message value:

Reaction:

NONE

Acknowledge:

IMMEDIATELY

Cause:

When changing the number of CDS or when copying from CDS, the master control is active.

Remedy:

If required, return the master control and repeat the operation.

201590

<location>Drive: Motor maintenance interval expired

Drive object:

All objects

Message value:

Fault cause: %1 bin

Reaction:

NONE

Acknowledge:

NONE

Cause:

The selected service/maintenance interval for this motor was reached.

Alarm value (r2124, interpret decimal):

Motor data set number.

See also: p0650 (Actual motor operating hours), p0651 (Motor operating hours maintenance interval)

Remedy:

carry out service/maintenance and reset the service/maintenance interval (p0651).

201600

<location>SI P1 (CU): STOP A initiated

Drive object:

HLA, HLA_840

Message value:

Reaction:

OFF2

Acknowledge:

IMMEDIATELY (POWER ON)

Cause:

The drive-integrated "Safety Integrated" function on the Control Unit (CU) has detected a fault and initiated a STOP A (STO

via the safety switch-off signal path of the Control Unit).

- forced checking procedure (test stop) of the safety switch-off signal path of the Control Unit unsuccessful.

- subsequent response to fault F01611 (defect in a monitoring channel).

Fault value (r0949, interpret decimal):

0: Stop request from monitoring channel 2.

1005: STO active although STO not selected and there is no internal STOP A present.

1010: STO inactive although STO is selected or an internal STOP A is present.

9999: Subsequent response to fault F01611.

Alarms

818

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Remedy:

- select Safe Torque Off and deselect again.

- replace Hydraulic Module involved.

For fault value = 9999:

- carry out diagnostics for fault F01611.

Note:

CU: Control Unit

SI: Safety Integrated

STO: Safe Torque Off / SH: Safe standstill

201600

<location>SI P1 (CU): STOP A initiated

Drive object:

SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC

Message value:

Reaction:

OFF2

Acknowledge:

IMMEDIATELY (POWER ON)

Cause:

The drive-integrated "Safety Integrated" function on the Control Unit (CU) has detected a fault and initiated a STOP A (STO

via the safety switch-off signal path of the Control Unit).

- forced checking procedure (test stop) of the safety switch-off signal path of the Control Unit unsuccessful.

- subsequent response to fault F01611 (defect in a monitoring channel).

Fault value (r0949, interpret decimal):

0: Stop request from monitoring channel 2.

1005:

- STO active, although STO not selected and there is no internal STOP A active.

- For a Power Module with "STO via terminals at the Power Module" (STO_A/STO_B), these terminals are active (DIP switch

to "ON"). However, the "STO via terminals at the Power Module" function has not been enabled (p9601.7 = p9801.7 = 0).

1010: STO inactive although STO is selected or an internal STOP A is present.

1015: Feedback signal of STO for Motor Modules connected in parallel are different.

9999: Subsequent response to fault F01611.

Remedy:

- select Safe Torque Off and deselect again.

- replace the Motor Module involved.

For fault value = 1005:

- deactivate terminals STO_A/STO_B on the Power Module (set both DIP-switches to "OFF") or enable the "STO via terminals

at the Power Module" function.

For fault value = 9999:

- carry out diagnostics for fault F01611.

Note:

CU: Control Unit

MM: Motor Module

SI: Safety Integrated

STO: Safe Torque Off / SH: Safe standstill

201611

<location>SI P1 (CU): Defect in a monitoring channel

Drive object:

HLA, HLA_840

Message value:

Reaction:

NONE (OFF1, OFF2, OFF3)

Acknowledge:

IMMEDIATELY (POWER ON)

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

819

SINAMICS alarms

Cause:

The drive-integrated "Safety Integrated" function on processor 1 has detected a fault in the data cross-check between the

two monitoring channels and has initiated a STOP F.

As a result of this fault, after the parameterized transition has expired (p9658), fault F01600 (SI CU: STOP A initiated) is

output.

Fault value (r0949, interpret decimal):

0: Stop request from another monitoring channel.

1 ... 999:

Number of the cross-compared data that resulted in this fault. This number is also displayed in r9795.

1: SI monitoring clock cycle (r9780, r9880).

2: SI enable safety functions (p9601, p9801). Crosswise data comparison is only carried out for the supported bits.

3: SI SGE changeover discrepancy time (p9650, p9850).

4: SI transition period STOP F to STOP A (p9658, p9858).

6: SI Motion enable, safety-relevant functions (p9501, internal value).

7: SI delay time of STO for Safe Stop 1 (p9652, p9852).

8: SI PROFIsafe address (p9610, p9810).

9: SI debounce time for STO/SBC/SS1 (p9651, p9851).

10: SI delay time for initiating STO for ESR (p9697, p9897).

11: SI HLA shutoff valve feedback signal contact configuration (p9626, p9826).

12: SI HLA shutoff valve wait time switch-on (p9625[0], p9825[0]).

13: SI HLA shutoff valve wait time switch-off (p9625[1], p9825[1]).

14: SI PROFIsafe telegram selection (p9611, p9811).

15: SI PROFIsafe bus failure response (p9612, p9812).

1000: Watchdog timer has expired.

Within the time of approx. 5 x p9650, alternatively, the following was defined:

- the signal at terminal STO of the Hydraulic Module continually changed with time intervals less than or equal to the

discrepancy time (p9650/p9850).

- via PROFIsafe/TM54F, STO (also as subsequent response) was continually selected and deselected with time intervals less

than or equal to the discrepancy time (p9650/p9850).

1001, 1002: Initialization error, change timer / check timer.

1900: CRC error in the SAFETY sector.

1901: CRC error in the ITCM sector.

1902: Overloading in the ITCM sector has occurred in operation.

1903: Internal parameterizing error for CRC calculation.

1950: Module temperature outside the permissible temperature range.

1951: Module temperature not plausible.

2000: Status of the STO selection for both monitoring channels different.

2001: Feedback signal of STO shutdown for both monitoring channels different.

2002: Status of the delay timer SS1 for both monitoring channels different (status of the timer in p9650/p9850).

2003: Status of the STO terminal for both monitoring channels different.

6000 ... 6999:

Error in the PROFIsafe control.

For these fault values, the failsafe control signals (Failsafe Values) are transferred to the safety functions. If "STOP B after

failure of the PROFIsafe communication" (p9612) is parameterized, the transfer of the Failsafe Values is delayed.

6000: A fatal PROFIsafe communication error has occurred.

6064 ... 6071: error when evaluating the F parameter. The values of the transferred F parameters do not match the expected

values in the PROFIsafe driver.

6064: Destination address and PROFIsafe address are different (F_Dest_Add).

6065: Destination address not valid (F_Dest_Add).

6066: Source address not valid (F_Source_Add).

6067: Watchdog time not valid (F_WD_Time).

6068: Incorrect SIL level (F_SIL).

6069: Incorrect F-CRC length (F_CRC_Length).

6070: Incorrect F parameter version (F_Par_Version).

Alarms

820

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Remedy:

For fault value = 1 ... 5 and 7 ... 999:

- check the cross data comparison that resulted in a STOP F.

- carry out a POWER ON (switch-off/switch-on) for all components.

- upgrade the Hydraulic Module software.

- upgrade the Control Unit software.

For fault value = 6:

- carry out a POWER ON (switch-off/switch-on) for all components.

- upgrade the Hydraulic Module software.

- upgrade the Control Unit software.

For fault value = 1000:

- check the STO terminal at the Hydraulic Module (contact problems).

- PROFIsafe: Remove contact problems/faults at the PROFIBUS master/PROFINET controller.

- check the wiring of the failsafe inputs at the TM54F (contact problems).

- check the discrepancy time, and if required, increase the value (p9650/p9850).

For fault value = 1001, 1002:

- carry out a POWER ON (switch-off/switch-on) for all components.

- upgrade the Hydraulic Module software.

- upgrade the Control Unit software.

For fault value = 1900, 1901, 1902:

- carry out a POWER ON (switch-off/switch-on) for all components.

- upgrade the Control Unit software.

- replace Control Unit.

For fault value = 2000, 2001, 2002, 2003:

- check the discrepancy time, and if required, increase the value (p9650/p9850, p9652/p9852).

- check the wiring of the safety-relevant inputs (SGE) (contact problems).

- check the causes of the STO selection in r9772. When the SMM functions are active (p9501 = 1), STO can also be selected

using these functions.

- replace Hydraulic Module involved.

Note:

This fault can be acknowledged after removing the cause of the error and after correct selection/deselection of STO.

For fault value = 6000:

- carry out a POWER ON (switch-off/switch-on) for all components.

- check whether there is a DRIVE-CLiQ communication error between the two monitoring channels and, if required, carry out

a diagnostics routine for the faults identified.

- increase the monitoring cycle clock settings (p9500, p9511).

- upgrade firmware to later version.

- contact Technical Support.

- replace the Control Unit.

For fault value = 6064:

- check the setting of the value in the F parameter F_Dest_Add at the PROFIsafe slave.

- check the setting of the PROFIsafe address of the Control Unit (p9610) and that of the hydraulic module (p9810).

For fault value = 6065:

- check the setting of the value in the F parameter F_Dest_Add at the PROFIsafe slave. It is not permissible for the destination

address to be either 0 or FFFF!

For fault value = 6066:

- check the setting of the value in the F parameter F_Source_Add at the PROFIsafe slave. It is not permissible for the source

address to be either 0 or FFFF!

For fault value = 6067:

- check the setting of the value in the F parameter F_WD_Time at the PROFIsafe slave. It is not permissible for the watch time

to be 0!

For fault value = 6068:

- check the setting of the value in the F parameter F_SIL at the PROFIsafe slave. The SIL level must correspond to SIL2!

For fault value = 6069:

Alarms

822

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

- check the setting of the value in the F parameter F_CRC_Length at the PROFIsafe slave. The setting of the CRC2 length is

2-byte CRC in the V1 mode and 3-byte CRC in the V2 mode!

For fault value = 6070:

- check the setting of the value in the F parameter F_Par_Version at the PROFIsafe slave. The value for the F parameter version

is 0 in the V1 mode and 1 in the V2 mode!

For fault value = 6071:

- check the settings of the values of the F parameters and the F parameter CRC (CRC1) calculated from these at the PROFIsafe

slave and, if required, update.

For fault value = 6072:

- check the settings of the values for the F parameters and, if required, correct.

The following combinations are permissible for F parameters F_CRC_Length and F_Par_Version:

F_CRC_Length = 2-byte CRC and F_Par_Version = 0

F_CRC_Length = 3-byte CRC and F_Par_Version = 1

For fault value = 6165:

- if the fault occurs after powering up the Control Unit or after plugging in the PROFIBUS/PROFINET cable, acknowledge the

fault.

- check the configuration and communication at the PROFIsafe slave.

- check the setting of the value for F parameter F_WD_Time on the PROFIsafe slave and increase if necessary.

- check whether there is a DRIVE-CLiQ communication error between the two monitoring channels and, if required, carry out

a diagnostics routine for the faults identified.

- check whether all F parameters of the drive match the F parameters of the F host.

For fault value = 6166:

- check the configuration and communication at the PROFIsafe slave.

- check the setting of the value for F parameter F_WD_Time on the PROFIsafe slave and increase if necessary.

- evaluate diagnostic information in the F host.

- check PROFIsafe connection.

- check whether all F parameters of the drive match the F parameters of the F host.

Note:

CU: Control Unit

EP: Enable Pulses (pulse enable)

ESR: Extended Stop and Retract

MM: Motor Module

SGE: Safety-relevant input

SI: Safety Integrated

SMM: Safe Motion Monitoring

SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)

STO: Safe Torque Off / SH: Safe standstill

201611

<location>SI P1 (CU): Defect in a monitoring channel

Drive object:

SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC

Message value:

Reaction:

NONE (OFF1, OFF2, OFF3)

Acknowledge:

IMMEDIATELY (POWER ON)

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

823

SINAMICS alarms

Cause:

The drive-integrated "Safety Integrated" function on processor 1 has detected a fault in the data cross-check between the

two monitoring channels and has initiated a STOP F.

As a result of this fault, after the parameterized transition has expired (p9658), fault F01600 (SI CU: STOP A initiated) is

output.

Fault value (r0949, interpret decimal):

0: Stop request from another monitoring channel.

1 ... 999:

Number of the cross-compared data that resulted in this fault. This number is also displayed in r9795.

1: SI monitoring clock cycle (r9780, r9880).

2: SI enable safety functions (p9601, p9801). Crosswise data comparison is only carried out for the supported bits.

3: SI SGE changeover discrepancy time (p9650, p9850).

4: SI transition period STOP F to STOP A (p9658, p9858).

5: SI enable Safe Brake Control (p9602, p9802).

6: SI Motion enable, safety-relevant functions (p9501, internal value).

7: SI delay time of STO for Safe Stop 1 (p9652, p9852).

8: SI PROFIsafe address (p9610, p9810).

9: SI debounce time for STO/SBC/SS1 (p9651, p9851).

10: SI delay time for initiating STO for ESR (p9697, p9897).

11: SI Safe Brake Adapter mode, BICO interconnection (p9621, p9821).

12: SI Safe Brake Adapter relay ON time (p9622[0], p9822[0]).

13: SI Safe Brake Adapter relay OFF time (p9622[1], p9822[1]).

14: SI PROFIsafe telegram selection (p9611, p9811).

15: SI PROFIsafe bus failure response (p9612, p9812).

1000: Watchdog timer has expired.

Within the time of approx. 5 x p9650, alternatively, the following was defined:

- the signal at terminal EP of the Motor Module continually changed with time intervals less than or equal to the discrepancy

time (p9650/p9850).

- via PROFIsafe/TM54F, STO (also as subsequent response) was continually selected and deselected with time intervals less

than or equal to the discrepancy time (p9650/p9850).

- safe pulse cancellation (r9723.9 - also as subsequent response) was continually selected and deselected with time intervals

less than or equal to the discrepancy time (p9650/p9850).

1001, 1002: Initialization error, change timer / check timer.

1900: CRC error in the SAFETY sector.

1901: CRC error in the ITCM sector.

1902: Overloading in the ITCM sector has occurred in operation.

1903: Internal parameterizing error for CRC calculation.

1950: Module temperature outside the permissible temperature range.

1951: Module temperature not plausible.

2000: Status of the STO selection for both monitoring channels different.

2001: Feedback signal of STO shutdown for both monitoring channels different. This value can also subsequently occur as

a result of other faults.

2002: Status of the delay timer SS1 for both monitoring channels different (status of the timer in p9650/p9850).

2003: Status of the STO terminal for both monitoring channels different.

2004: Status of the STO selection for Motor Modules connected in parallel different.

2005: Feedback signal of the safe pulse suppression on the Control Unit and Motor Modules connected in parallel different.

6000 ... 6999:

Error in the PROFIsafe control.

For these fault values, the failsafe control signals (Failsafe Values) are transferred to the safety functions. If "STOP B after

failure of the PROFIsafe communication" (p9612) is parameterized, the transfer of the Failsafe Values is delayed.

6000: A fatal PROFIsafe communication error has occurred.

6064 ... 6071: error when evaluating the F parameter. The values of the transferred F parameters do not match the expected

values in the PROFIsafe driver.

6064: Destination address and PROFIsafe address are different (F_Dest_Add).

6065: Destination address not valid (F_Dest_Add).

Alarms

824

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

6066: Source address not valid (F_Source_Add).

6067: Watchdog time not valid (F_WD_Time).

6068: Incorrect SIL level (F_SIL).

6069: Incorrect F-CRC length (F_CRC_Length).

6070: Incorrect F parameter version (F_Par_Version).

6071: CRC error for the F parameters (CRC1). The transferred CRC value of the F parameters does not match the value

calculated in the PROFIsafe driver.

6072: F parameterization is inconsistent.

6165: A communications error was identified when receiving the PROFIsafe telegram. The fault may also occur if an

inconsistent or out-of-date PROFIsafe telegram has been received after switching the Control Unit off and on or after

plugging in the PROFIBUS/PROFINET cable.

6166: A time monitoring error (timeout) was identified when receiving the PROFIsafe telegram.

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

825

SINAMICS alarms

Remedy:

For fault value = 1 ... 5 and 7 ... 999:

- check the cross data comparison that resulted in a STOP F.

- carry out a POWER ON (switch-off/switch-on) for all components.

- upgrade the Motor Module software.

- upgrade the Control Unit software.

For fault value = 6:

- carry out a POWER ON (switch-off/switch-on) for all components.

- upgrade the Motor Module software.

- upgrade the Control Unit software.

For fault value = 1000:

- check the EP terminal at the Motor Module (contact problems).

- PROFIsafe: Remove contact problems/faults at the PROFIBUS master/PROFINET controller.

- check the wiring of the failsafe inputs at the TM54F (contact problems).

- check the discrepancy time, and if required, increase the value (p9650/p9850).

For fault value = 1001, 1002:

- carry out a POWER ON (switch-off/switch-on) for all components.

- upgrade the Motor Module software.

- upgrade the Control Unit software.

For fault value = 1900, 1901, 1902:

- carry out a POWER ON (switch-off/switch-on) for all components.

- upgrade the Control Unit software.

- replace Control Unit.

For fault value = 2000, 2001, 2002, 2003, 2004, 2005:

- check the discrepancy time, and if required, increase the value (p9650/p9850, p9652/p9852).

- check the wiring of the safety-relevant inputs (SGE) (contact problems).

- check the causes of the STO selection in r9772. When the SMM functions are active (p9501 = 1), STO can also be selected

using these functions.

- replace the Motor Module involved.

- diagnose the other active faults and resolve the causes.

Note:

This fault can be acknowledged after removing the cause of the error and after correct selection/deselection of STO.

For fault value = 6000:

- carry out a POWER ON (switch-off/switch-on) for all components.

- check whether there is a DRIVE-CLiQ communication error between the two monitoring channels and, if required, carry out

a diagnostics routine for the faults identified.

- increase the monitoring cycle clock settings (p9500, p9511).

- upgrade firmware to later version.

- contact Technical Support.

- replace the Control Unit.

For fault value = 6064:

- check the setting of the value in the F parameter F_Dest_Add at the PROFIsafe slave.

- check the setting of the PROFIsafe address of the Control Unit (p9610) and that of the Motor Module (p9810).

For fault value = 6065:

- check the setting of the value in the F parameter F_Dest_Add at the PROFIsafe slave. It is not permissible for the destination

address to be either 0 or FFFF!

For fault value = 6066:

- check the setting of the value in the F parameter F_Source_Add at the PROFIsafe slave. It is not permissible for the source

address to be either 0 or FFFF!

For fault value = 6067:

- check the setting of the value in the F parameter F_WD_Time at the PROFIsafe slave. It is not permissible for the watch time

to be 0!

For fault value = 6068:

- check the setting of the value in the F parameter F_SIL at the PROFIsafe slave. The SIL level must correspond to SIL2!

Alarms

826

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

For fault value = 6069:

- check the setting of the value in the F parameter F_CRC_Length at the PROFIsafe slave. The setting of the CRC2 length is

2-byte CRC in the V1 mode and 3-byte CRC in the V2 mode!

For fault value = 6070:

- check the setting of the value in the F parameter F_Par_Version at the PROFIsafe slave. The value for the F parameter version

is 0 in the V1 mode and 1 in the V2 mode!

For fault value = 6071:

- check the settings of the values of the F parameters and the F parameter CRC (CRC1) calculated from these at the PROFIsafe

slave and, if required, update.

For fault value = 6072:

- check the settings of the values for the F parameters and, if required, correct.

The following combinations are permissible for F parameters F_CRC_Length and F_Par_Version:

F_CRC_Length = 2-byte CRC and F_Par_Version = 0

F_CRC_Length = 3-byte CRC and F_Par_Version = 1

For fault value = 6165:

- if the fault occurs after powering up the Control Unit or after plugging in the PROFIBUS/PROFINET cable, acknowledge the

fault.

- check the configuration and communication at the PROFIsafe slave.

- check the setting of the value for F parameter F_WD_Time on the PROFIsafe slave and increase if necessary.

- check whether there is a DRIVE-CLiQ communication error between the two monitoring channels and, if required, carry out

a diagnostics routine for the faults identified.

- check whether all F parameters of the drive match the F parameters of the F host.

For fault value = 6166:

- check the configuration and communication at the PROFIsafe slave.

- check the setting of the value for F parameter F_WD_Time on the PROFIsafe slave and increase if necessary.

- evaluate diagnostic information in the F host.

- check PROFIsafe connection.

- check whether all F parameters of the drive match the F parameters of the F host.

Note:

CU: Control Unit

EP: Enable Pulses (pulse enable)

ESR: Extended Stop and Retract

MM: Motor Module

SGE: Safety-relevant input

SI: Safety Integrated

SMM: Safe Motion Monitoring

SS1: Safe Stop 1

STO: Safe Torque Off / SH: Safe standstill

201612

<location>SI P1 (CU): STO inputs for power units connected in parallel different

Drive object:

SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC

Message value:

Fault cause: %1 bin

Reaction:

NONE (OFF1, OFF2, OFF3)

Acknowledge:

IMMEDIATELY (POWER ON)

Cause:

The drive-integrated "Safety Integrated" function on the Control Unit (CU) has identified different states of the AND'ed STO

inputs for power units connected in parallel and has initiated a STOP F.

As a result of this fault, after the parameterized transition has expired (p9658), fault F01600 (SI CU: STOP A initiated) is

output.

Fault value (r0949, interpret binary):

Binary image of the digital inputs of the Control Unit that are used as signal source for the function "Safe Torque Off".

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

827

SINAMICS alarms

Remedy:

- check the tolerance time SGE changeover and if required, increase the value (p9650).

- check the wiring of the safety-relevant inputs (SGE) (contact problems).

Note:

CU: Control Unit

SGE: Safety-relevant input

SI: Safety Integrated

STO: Safe Torque Off / SH: Safe standstill

201620

<location>SI P1 (CU): Safe Torque Off active

Drive object:

HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC

Message value:

Reaction:

NONE

Acknowledge:

NONE

Cause:

The "Safe Torque Off" (STO) function of the basic functions has been selected on the Control Unit (CU) using the input

terminal and is active.

Note:

- this message does not result in a safety stop response.

- this message is not output when STO is selected using the Extended Functions.

Remedy:

Not necessary.

Note:

CU: Control Unit

SI: Safety Integrated

STO: Safe Torque Off / SH: Safe standstill

201621

<location>SI P1 (CU): Safe Stop 1 active

Drive object:

HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC

Message value:

Reaction:

NONE

Acknowledge:

NONE

Cause:

The "Safe Stop 1" (SS1) function has been selected on the Control Unit (CU) and is active.

Note:

This message does not result in a safety stop response.

Remedy:

Not necessary.

Note:

CU: Control Unit

SI: Safety Integrated

SS1: Safe Stop 1

201625

<location>SI P1 (CU): Sign-of-life error in safety data

Drive object:

HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC

Message value:

Reaction:

OFF2

Acknowledge:

IMMEDIATELY (POWER ON)

Cause:

The drive-integrated "Safety Integrated" function on the Control Unit (CU) has detected an error in the sign-of-life of the

safety data between the two monitoring channels and has initiated a STOP A.

- there is either a DRIVE-CLiQ communication error or communication has failed.

- a time slice overflow of the safety software has occurred.

Fault value (r0949, interpret decimal):

Only for internal Siemens troubleshooting.

Alarms

828

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

SINAMICS alarms

Remedy:

- select STO and then deselect again.

- carry out a POWER ON (switch-off/switch-on) for all components.

- check whether there is a DRIVE-CLiQ communication error between the two monitoring channels and, if required, carry out

a diagnostics routine for the faults identified.

- deselect all drive functions that are not absolutely necessary.

- reduce the number of drives.

- check the electrical cabinet design and cable routing for EMC compliance

Note:

CU: Control Unit

MM: Motor Module

SI: Safety Integrated

STO: Safe Torque Off

201630

<location>SI P1 (CU): Brake control error

Drive object:

SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC

Message value:

Reaction:

OFF2

Acknowledge:

IMMEDIATELY (POWER ON)

Cause:

The drive-integrated "Safety Integrated" function on the Control Unit (CU) has detected a brake control fault and initiated

a STOP A.

- motor cable is not shielded correctly.

- defect in the brake control circuit of the Motor Module.

Fault value (r0949, interpret decimal):

10, 11:

Fault in "open holding brake" operation.

- parameter p1278 incorrectly set.

- no brake connected or wire breakage (check whether brake releases for p1278 = 1 and p9602/p9802 = 0 (SBC

deactivated)).

- ground fault in brake cable.

20:

Fault in "brake open" state.

- short-circuit in brake winding.

30, 31:

Fault in "close holding brake" operation.

- no brake connected or wire breakage (check whether brake releases for p1278 = 1 and p9602/p9802 = 0 (SBC

deactivated)).

- short-circuit in brake winding.

40:

Fault in "brake closed" state.

50:

Fault in the brake control circuit of the Control Unit or communication fault between the Control Unit and Motor Module

(brake control diagnostics).

80:

Safe Brake Adapter.

Fault in the brake control circuit of the Control Unit or communication fault between the Control Unit and Motor Module

(brake control diagnostics).

90:

Brake released for service purposes (X4).

Alarms

Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

829

SINAMICS alarms

Remedy:

- check parameter p1278 (for SBC, only p1278 = 0 is permissible).

- for a parallel connection, check the setting of the power unit data set to control the holding brake (p7015).

- select Safe Torque Off and deselect again.

- check the motor holding brake connection.

- check the function of the motor holding brake.

- 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.

- check that the electrical cabinet design and cable routing are in compliance with EMC regulations (e.g. shield of the motor

cable and brake conductors are connected with the shield connecting plate and the motor connectors are tightly screwed

to the housing).

- replace the Motor Module involved.

Operation with Safe Brake Module or Safe Brake Adapter:

- check the Safe Brake Module or Safe Brake Adapter connection.

- Replace the Safe Brake Module or Safe Brake Adapter.

Note:

CU: Control Unit

SBC: Safe Brake Control

SI: Safety Integrated

201631

<location>SI P1 (CU): motor holding brake/SBC configuration not practical

Drive object:

SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC

Message value:

Reaction:

NONE

Acknowledge:

NONE

Cause:

A configuration of motor holding brake and SBC was detected that is not practical.

The following configurations can result in this message:

- "No motor holding brake available" (p1215 = 0) and "SBC" enabled (p9602 = 1).

- "Motor holding brake just like the sequence control, connection via BICO" (p1215 = 3) and "SBC" enabled (p9602 = 1).

Remedy:

Check the parameterization of the motor holding brake and SBC and correct.

Note:

SBC: Safe Brake Control

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