All Third Part Ethercat bus couple stop update in ctrlX PLC if one of them pull out ethercat cable

[GP2]

Dear collguage;

We are testing Third Part Ethercat coe bus couple with one customer. The ctrlx X3 connect with 2 pcs of Ethercat bus couple. Now the commucation is ok, I can read and write the digital input output by ctrlX PLC.

We found that if one of them was pulled out ethercat cable (the last one),  all of the bus couple stop update their value in ctrlx PLC,

all the value reset to default. In my opinion, the other device connect to the core and still in OP shoule keep on working update values.

1. I want to know is there anyway settings in ctrlx to keep the bus couple who still stay in OP (connect to the core) keep on update values?
2. If the customer using our S20 Ethercat bus couple ,do they still face this question?
3. is this caused by the the third part device?

Thank you very much!

[cc2go · Accepted solution]

Hello GP2,

it’s a common Ethercat behavior. Devices which have a valid connection keep in OP state. But stop data exchange when at least one EC Slave is not in OP, it doesn’t matter Drive or IO. To get a more tolerant Ethercat system, each EC Slave device must be in its own SyncUnit or SyncUnit group. In a group all are affected.

Details can be found here: https://docs.automation.boschrexroth.com/doc/1996056935/syncunits/latest/en/

The S20-EC-BK AD1 must be switched manual to OP again, because of its local bus. In old versions AC1 was a bug, that the S20 bus coupler must be switched to Init first and then to OP (can be seen with flashing D-LED in OP of S20 local bus).

Hope this answers your observations.

[GP2]

Got it!  Thank you very much!