Table of Contents
Advertisement
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.
F01451
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.
F01470
Topology: Target topology ring connection
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
A ring-type connection was detected when writing into the target topology.
Fault value (r0949, hexadecimal):
Byte 1: Component number of a component included in the ring
Byte 2: Component class
Byte 3: Connection number
Note:
Component class and connection number are described in F01375.
Remedy:
Read-out the fault value and remove one of the specified connections.
Then, download the target topology again using the commissioning software.
F01475
Topology: Target topology duplicate connection between two components
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
When writing the target topology, a duplicate connection between two components was detected.
Fault value (r0949, hexadecimal):
Byte 1: Component number of one of the components connected twice
Byte 2: Component class
Byte 3: Connection number 1 of the duplicate connection
Byte 4: Connection number 2 of the duplicate connection
Note:
Component class and connection number are described in F01375.
Remedy:
Read-out the fault value and remove one of the two specified connections.
Then, download the target topology again using the commissioning software.
A01481
Topology: Comparison shows power module not present in the actual topology
Reaction:
NONE
Acknowledge:
NONE
Siemens AG 2004 All Rights Reserved
SINAMICS G List Manual, Edition 12.2004
Faults and Alarms
List of faults and alarms
3-533
Hide quick links:
Advertisement
Table of Contents
