7
7.3
List of faults and warnings
7-664
Siemens AG 2005 All Rights Reserved
SIMODRIVE 611 universal Description of Functions (FBU) – 04.05 Edition
595
Fieldbus: Cyclic data transfer was interrupted
Cause
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”.
Remedy
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.
Acknowledgement RESET FAULT MEMORY
Stop response
STOP II
596
PROFIBUS: Connection to the publisher \%u inter-
rupted
Cause
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
Remedy
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.
Acknowledgement RESET FAULT MEMORY
Stop response
STOP II
7 Fault Handling/Diagnostics
01.99
04.05
