EtherCAT does not start after updating the boot project and restarting the controller (fixed from V3.18)

Corrected from:
Controller c300 V3.18
Controller 3200C V3.18
Panel Controller p300 V3.18
Panel Controller p500 V3.18

Response of the new version:
A change of the boot project with adaptations to the EtherCAT structure leads to an update of the associated EtherCAT configuration file in the controller. This makes the EtherCAT operational again after a restart of the controller.
 
What happens?
After a change of the boot project with adjustments to the EtherCAT structure, the EtherCAT bus does not become operational after a restart of the controller.
 
When does this behaviour occur?
The behaviour can occur if the boot project including the EtherCAT bus structure is changed for a controller. The associated EtherCAT configuration file may not be updated on the controller.
 
Which products are affected?
Controller c300 V3.8 and higher
Controller 3200C as of V3.0
Panel Controller p300 V3.8 and higher
Panel controller p500 as of V3.2
 
Short-term measures:
  1. Go online with the affected controller (menu command 'Online > Log in').
  2. execute the menu command 'Online > Reset origin'.
  3. Important: Restart the controller now.
  4. Transfer the PLC application again with the PLC Designer and create a boot application online (menu command 'Online > Create boot application for Lenze devices').
Evaluation/recommendations: 
After changing the boot project (the power-fail-safe PLC application), EtherCAT very sporadically does not change to the 'Operational' state. Short-term measures describe an application-based remedy.
 
Automatic Translation

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/201900030/1/
Kontaktformular