Siemens SINAMICS Configuration Manual page 123

Monitoring telegram failure
When monitoring the telegram failure, SINAMICS differentiates between two cases:
● Telegram failure with a bus fault
After a telegram failure and the additional monitoring time has elapsed (p2047), bit r2043.0
is set to "1" and alarm A01920 is output. Binector output r2043.0 can be used for a quick
stop, for example.
Once the delay time p2044 has elapsed, fault F01910 is output. Fault F01910 triggers fault
response OFF2 (pulse inhibit) for the infeed and OFF3 (quick stop) for SERVO/VECTOR.
If no OFF response is to be triggered, the fault response can be reparameterized
accordingly.
Fault F01910 can be acknowledged immediately. The drive can then be operated even
without PROFIdrive.
Figure A-7
● Telegram failure with a CPU stop
After telegram failure, bit r2043.0 is set to "1". Binector output r2043.0 can be used for a
quick stop, for example.
Once the delay time p2044 has elapsed, fault F01910 is output. Fault F01910 triggers fault
response OFF2 (pulse inhibit) for the infeed and OFF3 (quick stop) for SERVO/VECTOR.
If no OFF response is to be triggered, the fault response can be reparameterized
accordingly.
Fault F01910 can be acknowledged immediately. The drive can then be operated even
without PROFIdrive.
Figure A-8
Industrial Security
Configuration Manual, 08/2017, A5E36912609A
Monitoring telegram failure with a bus fault
Monitoring telegram failure for a CPU stop
Communication
A.1 Communication
123