EtherCAT DC synchronisation gets lost (corrected from V3.15)

​Corrected from:
c300 controller V3.15
3200 C controller V3.15
p300 panel controller V3.15
p500 panel controller V3.15
 
Response of the new version:
The EtherCAT master of the controller synchronises microcontroller-based EtherCAT slaves (such as for EtherCAT modules >=V4.0 of the 9400 servo inverters) before reaching the 'Operational' EtherCAT state. The EtherCAT DC synchronisation is not lost during operation.
 
What happens?
The EtherCAT master in the controller reports the loss of the EtherCAT synchronisation with distributed clock (DC). Depending on the target system, this results in different reactions:
  • L-force Motion: Motion calculation is stopped.
  • FAST Motion: Cracking noises in the controlled axes.
When does this behaviour occur?
The behaviour occurs if an EtherCAT module of version V4 or higher is used in a 9400 HighLine under a controller of V3.14 (or older).
 
Which products are affected?
c300 controller from V3.8
3200C controller from V3.0
p300 panel controller from V3.8
p500 panel controller from V3.3
 
9400 servo inverter HighLine with EtherCAT module V4
 
Short-term measures:
Use EtherCAT module V3 when using a controller of version V3.14 (or older).
 
Evaluation/recommendations:
If a 9400 servo inverter HighLine is operated on a controller, make sure that an EtherCAT module V3 will not be replaced by an EtherCAT module V4 in the event of replacement.

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/201700209/1/
Meta data
Taxonomy: Controller p500 , Controller 3221 C , Controller 3231 C , Controller 3241 C , Controller 3251 C , Controller 3200 C , Controller c300 , Controller p300
AKB-ID: 201700209
Last update: 2023/09/09
Category: Version Informations

Lenze reserves the right to change information on this page at any time. Any liability for the accuracy of the information is excluded.
Contact form