Siemens SINAMICS G130, List Manual, Page: 1494 / 1976

4 Faults and alarms
4.2 List of faults and alarms
SINAMICS G130/G150
1494
List Manual (LH2), 07/2016, A5E03263479A
A01943 PB/PN: clock cycle signal error when establishing bus communication
Message value: -
Message class: Communication error to the higher-level control system (9)
Drive object: All objects
Component: None Propagation: LOCAL
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
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.
Note:
PB: PROFIBUS
PN: PROFINET
A01944 PB/PN: sign-of-life synchronism not reached
Message value: -
Message class: Communication error to the higher-level control system (9)
Drive object: B_INF, ENC, VECTOR_G
Component: None Propagation: LOCAL
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 to how it was configured in the Tmapc time grid.
Remedy: - ensure that the master correctly increments the sign-of-life in the master application clock cycle Tmapc.
- correct the interconnection of the master sign-of-life (p2045).
Note:
PB: PROFIBUS
PN: PROFINET
A01945 PROFIBUS: Connection to the Publisher failed
Message value: Fault cause: %1 bin
Message class: Communication error to the higher-level control system (9)
Drive object: All objects
Component: None Propagation: LOCAL
Reaction: NONE
Acknowledge: NONE
Cause: For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Publisher with address in r2077[0], connection failed.
...
Bit 15 = 1: Publisher with address in r2077[15], connection failed.
Remedy: - check the PROFIBUS cables.
- carry out a first commissioning of the Publisher that has the failed connection.
See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)