Yes, this issue has been addressed to development team.
In the meantime, we could find a work around. Basically, after a while, Slave was going in "sleep mode". With some code, we keep it alive and avoid any communication failure (in my case, time-out):
By the way, Ethernet/IP scanner 188.8.131.52 must not be used sinced it leads to EtherCAT issue!!
My inputs on EtherCAT (from IO or EFC or CtrlX Drive stuck at value 0):
This is something also explained in another post:
... View more