Siemens SINUMERIK 840D sl Series Diagnostics Manual page 669

08/2005
201931 <location>PROFIBUS: Speed controller clock cycle for clock
synchronous operation, not the same
Reaction: NONE
Acknowledge: NONE
Cause: The speed controller clock cycle of all drives must be set the same for the clock
synchronous PROFIBUS.
Alarm value (r2124, decimal):
Number of the drive object with the different speed controller clock cycle.
Remedy: - set the speed controller clock cycles the same (p0115[1]).
See also: p0115
201940 <location>PROFIBUS: Clock synchronism still not reached
Reaction: NONE
Acknowledge: NONE
Cause: PROFIBUS is in the data exchange state and clock synchronous operation has been
selected using the parameterizing telegram. It was not possible to synchronize to the clock
cycle specified by the master.
- the master 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 parameterizing telegram.
- at least on DO (that is not controlled from Profibus) has a pulse enable.
Remedy: - check the master application and bus configuration.
- check the consistency between the clock cycle input when configuring the slave and clock
cycle setting at the master.
- ensure that the DOs not controlled by Profibus, have their pulses inhibited. Only enable
the pulses after synchronizing the Profibus drives.
201941 <location>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 parameterizing telegram. The global control telegram for
synchronization is not being received.
Remedy: Check the master application and bus configuration.
201943 <location>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 parameterizing telegram. The global control telegram for
synchronization is being irregularly received.
-.the master is sending an irregular global control telegram.
- the master is using another clock synchronous DP clock cycle than was transferred to the
slave in the parameterizing telegram.
Remedy: - check the master application and bus configuration.
- check the consistency between the clock cycle input when configuring the slave and clock
cycle setting at the master.
201944 <location>PROFIBUS: Sign-of-life synchronism not reached
Reaction: NONE
Acknowledge: NONE
© Siemens AG, 2005. All rights reserved
SINUMERIK 840D sl/840D/840Di/810D Diagnostics Guide (DA), 08/2005 Edition
Overview of Alarms
2-669