Siemens SINAMICS S Series - A01940 IF1: PB;PN clock cycle synchronism not reached; A01941 IF1: PB;PN clock cycle signal missing when establishing the bus; A01943 IF1: PB;PN clock cycle signal faulted when establishing the bus; A01944 IF1: PB;PN sign-of-life synchronism not reached

Faults and Alarms
List of faults and alarms
3-1500
© Siemens AG 2007 All Rights Reserved
SINAMICS S List Manual (LH1), 07/2007
A01940 IF1: PB/PN clock cycle synchronism not reached
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The bus 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 parameter-
izing telegram.
- at least one drive object (that is not controlled from PROFIBUS/PROFINET) 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 mas-
ter.
- ensure that the pulses of drive objects, not controlled from PROFIBUS/PROFINET, are not enabled. Only enable
the pulses after synchronizing the PROFIBUS/PROFINET drives.
Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
A01941 IF1: PB/PN clock cycle signal missing when establishing the bus
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The bus 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.
Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
A01943 IF1: PB/PN clock cycle signal faulted when establishing the bus
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The bus 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 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.
Note:
IF1: Interface 1
PB: PROFIBUS
PN: PROFINET
A01944 IF1: PB/PN sign-of-life synchronism not reached
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing
telegram. Synchronization with the master sign-of-life (STW2.12 ... STW2.15) could not be completed because the
sign-of-life is changing differently than configured in the Tmapc time grid.