When rebooting the CtrlX IO of EtherCAT slave devices while the CtrlX Core is powered on, the IO modules transition into a non-operational (non-OP) state.
Currently, I can reset the EtherCAT communication in the CtrlX Core CPU by changing the EtherCAT master from "Init" to "OP" status via the EtherCAT library. However, this causes all slave devices to restart, which is not desired.
In the other system, there is a function available on slave devices called "ReInit after Communication Error," which automatically restores the slave devices to the operational (OP) state after a reboot or communication reconnection without additional programming.
How can I enable or configure this "ReInit after Communication Error" function in CtrlX Core?
Thank you.
Frank
