Siemens SIMODRIVE 611 universal Function Manual page 664

7 Fault Handling/Diagnostics
7.3 List of faults and warnings
595
Cause
Remedy
Acknowledgement
Stop response
596
Cause
Remedy
Acknowledgement
Stop response
7-664
Fieldbus: Cyclic data transfer was interrupted
The cyclic data transfer between the master and slave was interrupted
due to the fact that cyclic frames were missing, or due to the reception
of a parameterizing or configuring frame.
Examples:
– Bus connection interrupted
– Master runs up again
– Master has changed into the 'Clear' state
For a passive axis, fault cannot be acknowledged using "RESET
FAULT MEMORY".
Check the master and bus connection to the master. As soon as cyclic
data transfer runs again, the fault can be acknowledged.
Set P0875 to 0 in the passive axis.
RESET FAULT MEMORY
STOP II
PROFIBUS: Connection to the publisher \%u inter-
rupted
Cyclic data transfer between this slave and a slave-to-slave commu-
nications publisher was interrupted as cyclic telegrams were missing.
Examples:
– Bus connection interrupted
– Publisher failure
– Master runs up again
– The response monitoring (Watchdog) for this slave was de-activated
via the parameterizing telegram (SetPrm) (Diagnostics: P1783:1 bit 3 =
0).
Supplementary info: PROFIBUS address of the publisher
Check the publisher and bus connections to the publisher, to the
master and between the master and publisher. If the watchdog is de-
activated, activate the response monitoring for this slave via Drive ES.
As soon as cyclic data transfer runs again, the fault can be acknowl-
edged.
RESET FAULT MEMORY
STOP II
SIMODRIVE 611 universal Description of Functions (FBU) – 04.05 Edition
E Siemens AG 2005 All Rights Reserved
04.05 01.99