[etherlab-users] Slave goes to OP mode after Master starts

Hi, We have a Elmo Solo Twitter drive connected to the Ethercat master on 3 different systems (Ubuntu machine with RT kernel, OpenSuse machine with RT kernel and Beaglebone Black with RT kernel) and see different behaviour between the systems as soon as the master is started. An application is

Re: [etherlab-users] Slave goes to OP mode after Master starts

In the current stable branch, the slave selected as the reference clock (which is the first slave that has a DC clock, by default) and also any EoE slaves, are forced to OP mode even when the application is not active. I assume that this is a misunderstanding about their requirements to provide