EtherCat communication disturbed

[Babar]

Hello All community members,

We have a single and a double axis drive with ctrlX core integrate. Our EtherCat communication got disturbed after being left the system idle for few hours, if we keep the drives in operation, everything works fine, but if we leave the drives idle for few hours, the ethercat buss got disturbed somehow and i get status of ethercat that the drives are not connected. After a restart everything works fine again. anybody knows what can be the reason?

Regards

Babar

[CodeShepherd]

Could you point out what is meant by "Drives in operation" and "idle"? Do you mean Ab and AF?

[Babar]

Idle means, the axis are standstill for a longer period of time. i attached the parameterfiles as well

[Babar]

I double check with the customer. The drives looses the communication while in Ab, In Standstill or in AF they dont have any issue.

[Drives_Uwe · Accepted solution]

If looking to the diagnostic trace of the double axes drive one sees that error F8105 and/or F8844 is present. that in this error case the communication fails is normal. See components used and traces of the two axes:

But what causes the drive to show error F8105 and/or F8844 is unfortunately not really clear. Follow the manual:

As remedy you may use the latest firmware AXS-V-0308N-NN.04 attached.

[Babar]

I updated the firmware but i did not solve the problem 😕

I am using 1.12 on the core, shall i try to upgrade that as well?

[CodeShepherd]

1.12 is the correct ctrlX CORE version for that use case. A later control version would need other drive runtime e.g. 1.20 needs 04V02.

[CodeShepherd]

@Babar Are there any news? Is this still an issue or can this topic be closed?