sorry .... I'm sorry I told the false about the errors .... I did not realize that the change of number takes place even when everything works as well as this morning ... to be precise, I report today's dmsg that everything is fine:
about network card .... i have six I210 Gigabit on my pc ... "lspci" give my that response:
Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
from "ERROR" situations and "normal" situations I can see only two row of messages differences:
Code:
[color=red][ 254.436885] EtherCAT 0: Domain 0: 3 working counter changes - now 18/21.[/color]
[ 257.697493] EtherCAT 0: Domain 0: Working counter changed to 21/21.
because two slave not go to OP state .... but not see other interesting messages .... so I can assume as you say a problem on the ethernet card side, but also a power problem .... they are drives that are ready to be STO even if they do not have the specific function. My drive have logical power everytime ON and motor-power ON only when a breaker is on. Breaker is commanded from "halui.machine.is-on". I begin to assume that a delay in activating the power of the motor-power does not allow it to go to OP. If try with twincat to put my derive in OP state wit motor-power off the drive not go to OP state. However, I do not find the way to verify this so that it remains only a hypothesis (twincat not give a specific messages and drive the same). What happens with my_pyvcp.hal file is this:
Code:
net out1 halui.machine.is-on => pyvcp.led-01 lcec.0.7.dout-0
dout-0 command my breaker.
But for first is my.hal file that is read so:
Code:
net ec-slaves-responding <= lcec.slaves-responding
net ec-link-up <= lcec.link-up
net ec-all-op <= lcec.all-op
net ec_up lcec.state-op => iocontrol.0.emc-enable-in lcec.0.0.driverControl-0 lcec.0.1.driverControl-0 lcec.0.2.driverControl-0
Code on my.hal file is read and executed a little bit first and code on my_pyvcp.hal file is read and executed a little bit after ... so it maybe that OP state is commanded first but power line is powered with a little delay .... so some drive not go to OP because not powered yet.
On the other hand the halui commands are executed, in a theoretical temporal sequence, always after the motion commands so that my dout-0 should find a better parent than halui.machine.is-on to be activated.
@db1981 do you find this a sensible theory? How could i do to put my dout-0 in the correct sequence?
regards
bkt
