Function extension:
Telegram failure for synchronised operation with EtherCAT communication (selection for control interface C4010 = 2).
The telegram failure monitoring responds if at least two telegram failures have occurred in a row when communicating via EtherCAT (operating status: Operational).
In default setting the fault response Fail-QSP (fault number 3425) is triggered when the telegram failure monitoring responds.
Display: (EtherCAT-Err) PDO telegram failure.
The following setting can be selected under code C4279 '(EtherCAT-Err) Response PDO telegram data failure':
- Trip, message, warning, off, Fail-QSP (Default: Fail-QSP)
Display code C4277 EtherCAT number of telegram failures:
In order to diagnose the transmission quality of the EtherCAT communication the number of telegram failures occurred is displayed under code C4277. The internal counter is started with zero after every mains connection (initialisation).
Important:
In order to ensure a trouble-free operation of the ECS Motion axes with EtherCAT communication telegram failures must not occur at all if possible. If telegram failures are registered under C4277 or even the monitoring responds this may indicate an interruption of the EtherCAT connection, increased noise interferences, bad shielding, unfavourable cable routing or other EtherCAT communication problems.
The faulty EtherCAT communication is to be checked and corrected. It is useless to simply deactivate the monitoring.
Included in which products/versions?
ECS Motion from V3.0 onwards
only with operating software from V8.3 onwards (presumably available as of end of 2010)
Applications:
Operating the ECS Motion at a higher-level control with communication via EtherCAT
Published in Service Message No. 2010/xx
