EtherCAT Slaves remain in the Init state on startup

[MateuszGrudzien]

I have a problem with the EtherCAT network. On startup, all participants (apart from the master) remain in the Init state. The only error displayed is as in the photo below. When I press the "OP" button all slaves go to OP state without any issues. What can be locking devices in the Init state on startup? Is there a way to automate going into OP state so I don't have to do it each time via a web browser? My CtrlX Core FW version is 2.4.0.

I've found a similar post linked below, but disabling EoE for the EFC, unfortunately, didn't solve my issue: https://developer.community.boschrexroth.com/t5/Communication/EtherCAT-Slave-remains-in-Pre-OP/m-p/9...

[CodeShepherd]

In ctrlX IO Engineering there is a setting that Slaves need to reach master state. You could use this to prevent the fieldbus states from drifting apart.

Could you add information about EFCs firmwares and MEP firmware? Was it switched on with 24V or with Mains?

[MateuszGrudzien · Accepted solution]

Thank you for your answer. Unfortunately, the machine had to be shipped to the customer, so I cannot provide the data you requested, but I managed to find a solution. The issue was resolved after I updated the FW of CtrlX Core from 2.4 to 2.6.