EtherCAT bus becomes operational, although parameters could not be written during the initialization phase (corrected)

Corrected from:
Controller 3200C V3.20
Panel Controller p500 V3.20
Controller c300 V3.20
Panel Controller p300 V3.20
Controller c520 V1.5
Controller c550 V1.5
Controller c750 V1.5

Response of the new version:
If during the initialization phase of EtherCAT the parameters defined in the PLC project cannot all be written successfully, EtherCAT will not become 'Operational'.
This can happen especially when an EtherCAT slave is replaced by an identical device with an older firmware version.
 
What happens? 
During the start of the controller or during the initialization phase of the EtherCAT master, parameter values are automatically transferred from the controller to all EtherCAT slaves of the types i550, i700, i950 CiA and EPM-S130. If error messages occur when writing the parameters, they are stored in the logbook, but EtherCAT still becomes 'operational'.

When does the behaviour occur?
The behavior can occur if a new device description is used in the PLC Designer project but the version of the real EtherCAT slave is older. In this case it may happen that the newer device description contains parameters which were not known in the older version. Describing these parameters leads to error messages which are entered in the logbook of the controller. Independent of these error messages the EtherCAT bus becomes 'Operational'.
In later operation this can lead to malfunctions.
 
Which products are affected? 
Controller 3200C
Panel Controller p500
Controller c300
Panel Controller p300
Controller c520
Controller c550
Controller c750

Short-term measures:
During commissioning or after a device exchange, check the logbook of the controller whether all parameters have been written successfully after the initialization phase of the EtherCAT bus.

Evaluation/Recommendations:
If error messages occur after power-on of the controller during initial parameter set download to the connected EtherCAT slaves, EtherCAT will still become 'Operational'. This can lead to malfunctions in later operation, because the function in the EtherCAT slave was either not parameterized correctly or the slave does not support this function at all.

Automatic Translation

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