Pb/Pn Clock Cycle Signal Missing When Establishing Bus Communication; Pb/Pn Clock Cycle Signal Error When Establishing Bus Communication; Profibus: Connection To The Publisher Failed - Siemens SINAMICS DCM List Manual

4 Faults and alarms
4.2 List of faults and alarms
- the master does not send a clock synchronous global control telegram although 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 one drive object has a pulse enable (not controlled from PROFIBUS/PROFINET either).
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.
- check that no drive object has a pulse enable. Only enable the pulses after synchronizing the
PROFIBUS/PROFINET drives.
Note:
PB: PROFIBUS
PN: PROFINET
A01941

PB/PN clock cycle signal missing when establishing bus communication

Message value: -
Message class: Communication error to the higher-level control system (9)
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:
PB: PROFIBUS
PN: PROFINET
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
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
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
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.
926
List Manual (LH8), 02/2015, 6RX1800-0ED76
SINAMICS DCM