Fixed as of:
-
Behavior of the new version:
-
Description of the behavior:
In an EtherCAT HotConnect configuration, a Lenze controller from the C430/C5xx series with an activated EtherCAT slave interface is operated within a HotConnect group.
If the HotConnect group is de-energized during operation and then re-energized, the group is successfully detected and integrated by the EtherCAT master; however, the C430/C5xx slave contained within it does not start up properly. The slave typically remains in the INIT or Pre-Operational state and does not reach the operational state.
In this context, error entries such as "PDI Error" or "WorkingCounter Error" may appear in the log.
Conditions under which the behavior occurs:
See above
Affected products:
c430/c5xx EtherCAT-master and c430/c5xx EtherCAT-slave
Short-term measures, recommendations, assessment:
First, apply power to the HotConnect group and allow it to boot up completely. Only then should you establish the connection to the EtherCAT bus or register the HotConnect group on the EtherCAT network. This will prevent the erroneous boot-up behavior.
[Automatic Translation]
