Table of Contents
Advertisement
Faults and Alarms
List of faults and alarms
Cause:
PROFIBUS is in the data exchange state and clock synchronous operation has been selected using the parameter-
izing telegram. It was not possible to synchronize to the clock cycle specified by the master.
- the master doesn't send a clock synchronous global control telegram although the clock synchronous operation
was selected when configuring the bus.
- the master is using another clock synchronous DP clock cycle than was transferred to the slave in the parameter-
izing telegram.
Remedy:
- check the master application and bus configuration.
- check the consistency between the clock cycle input when configuring the slave and clock cycle setting at the mas-
ter.
A01941
PROFIBUS: Clock cycle signal missing when the bus is being established
Reaction:
NONE
Acknowledge:
NONE
Cause:
PROFIBUS is in the data exchange state and clock synchronous operation has been selected using the parameter-
izing telegram. The global control telegram for synchronization is not being received.
Remedy:
Check the master application and bus configuration.
A01943
PROFIBUS: Clock cycle signal error when the bus is being established
Reaction:
NONE
Acknowledge:
NONE
Cause:
PROFIBUS is in the data exchange state and clock synchronous operation has been selected using the parameter-
izing telegram. The global control telegram for synchronization is being irregularly received.
-.the master is sending an irregular global control telegram.
- the master is using another clock synchronous DP clock cycle than was transferred to the slave in the parameter-
izing telegram.
Remedy:
- check the master application and bus configuration.
- check the consistency between the clock cycle input when configuring the slave and clock cycle setting at the mas-
ter.
A01944
PROFIBUS: Sign-of-life synchronism not reached
Reaction:
NONE
Acknowledge:
NONE
Cause:
PROFIBUS is in the data exchange state and clock synchronous operation has been selected using the parameter-
izing telegram. Synchronization with the master sign-of-life (STW2 bits 12-15) could not be completed because the
sign-of-life is changing differently than configured in the Tmapc time grid.
Remedy:
- ensure that the master correctly increments the sign-of-life in the master application clock cycle.
- check the interconnection of the master sign-of-life (p2045).
F01950 (N, A)
PROFIBUS: Clock synchronous operation, synchronization unsuccessful
Reaction:
OFF1 (NONE)
Acknowledge:
IMMEDIATELY (power on)
Cause:
Synchronization of the internal clock cycle to the global control telegram has failed. The internal clock cycle exhibits
an unexpected shift.
Remedy:
Siemens-internal
Reaction upon N:
NONE
Acknowledge
NONE
upon N:
Reaction upon A:
NONE
Acknowledge
NONE
upon A:
F01951
CU DRIVE-CLiQ: Synchronization, application clock cycle missing
Reaction:
OFF2 (NONE)
Acknowledge:
IMMEDIATELY (power on)
3-548
Siemens AG 2004 All Rights Reserved
SINAMICS G List Manual, Edition 12.2004
Hide quick links:
Advertisement
Table of Contents
