Lenze E84AYCET EtherCAT MCI module - Manual (Page 83)

Lenze · E84AYCET communication module (EtherCAT) · Communication Manual · DMS 5.0 EN · 05/2013 · TD17
83
10 Monitoring
10.2 Sync frame failure detection
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
10.2 Sync frame failure detection
During the Synchronisation with "Distributed Clocks" (DC) ( 37) , this monitoring checks whether an
EtherCAT PDO telegram (Sync Manager 2 Event) has arrived between two signals.
For this purpose, the communication module comes with an internal EtherCAT telegram failure
error counter. The telegram failure error counter is incremented by the value '3' in case of a telegram
failure. For each PDO received correctly, the counter is decremented by ’1’. If the internal telegram
failure error counter reaches a threshold adjustable in CoE object 0x10F1.2, a change to "Safe-
Operational" takes place and the " Sync telegram failure [0x01bc8700] " error message is output.
In the standard setting, monitoring is deactivated (0x10F1.2 = 0). A sensible setting is a value > ’5’
in order that an error will only be triggered in the inverter when a second telegram fails.
An error response can be set via code
C13880/2 ("0: No response" is preset here).
10.3 Interruption of internal communication
The response to a communication error between the communication module and the standard
device can be set in the standard device code C01501 (module in the MCI slot).
An externally supplied communication module reports a connection abort to the standard device
via an emergency telegram to the master and changes to the "Safe-operational" state.
The error message "
Lost connection to 8400 [0x01bc3100] " ( 93) is output.