Siemens SINUMERIK 840D sl Series Diagnostics Manual page 644

Overview of Alarms
Cause: The topology comparison has detected differences in the actual and target topologies in
relation to one component. A component was connected to another connection.
The different connections of a component are described in the alarm value:
Alarm value (r2124, hexadecimal):
Byte 1: Component number
Byte 2: Component class
Byte 3: Connection number in the actual topology
Byte 4: Connection number in the target topology
Note:
Component class and connection number are described in F01375.
The drive system run-up is stopped. In this state, the drive control (closed-loop) cannot be
enabled.
Remedy: Adapting the topologies:
- change over the actual topology to match the target topology.
- download the target topology that matches the actual topology (commissioning software).
- automatically remove the topology error (p9904).
See also: p9904
201429 <location>Topology: Comparison, connection is different for more than
component
Reaction: NONE
Acknowledge: NONE
Cause: A topology comparison has found differences between the actual and target topology for
several components. A component was connected to another connection.
The different connections of a component are described in the alarm value:
Alarm value (r2124, hexadecimal):
Byte 1: Component number
Byte 2: Component class
Byte 3: Connection number in the actual topology
Byte 4: Connection number in the target topology
Note:
Component class and connection number are described in F01375.
The drive system run-up is stopped. In this state, the drive control (closed-loop) cannot be
enabled.
Remedy: Adapting the topologies:
- change over the actual topology to match the target topology.
- download the target topology that matches the actual topology (commissioning software).
Note:
In the software, a double motor module behaves just like two separate DRIVE-CLiQ nodes.
If a double motor module is re-inserted, this can result in several differences in the actual
topology.
201451 <location>Topology: Target topology is invalid
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: An error has occurred when writing into the target topology.
The write operation was interrupted due to an invalid target topology.
Fault value (r0949, hexadecimal):
Only for internal Siemens troubleshooting.
Remedy: Reload the target topology using the commissioning software.
201470 <location>Topology: Target topology ring connection
Reaction: NONE
Acknowledge: IMMEDIATELY
2-644
SINUMERIK 840D sl/840D/840Di/810D Diagnostics Guide (DA), 08/2005 Edition
© Siemens AG, 2005. All rights reserved
08/2005