RevPi CONNECT+, CODESYS, EtherCAT master "Filedbus lost synchronicity"
Posted: 31 Jul 2021, 10:43
Dear All
I'm facing a frustrating issue using the following configuration for my motion project.
- EtherCAT as field bus
Six axis plus a remote I/O node
- RevPi CONNECT+ 8GB as controller
with the original, even though updated, OS version
- CODESYS as automation SW solution
CODESYS V3.5 SP17 Patch 1 (64 bit)
CODESYS EtherCAT 4.1.0.0
CODESYS SoftMotion 4.10.0.0
CODESYS Control for Raspberry PI 4.1.0.0
Revolution PI Library for CODESYS 1.1.0.0
The EtherCAT lan is connected to the port eth1 which hasn't got any special configuration about IP address, it is in DHCP mode.
Issue description
Randomly, after minutes or even hours EtherCAT stop working.
The message log error shown is: "Filedbus lost synchronicity"
This kind of error apparently has nothing to do with the solution configuration and tasks cycling neither.
The EtherCAT task execution time is always below the task cycle, and other tasks too.
Furthermore, the EtherCAT task is executed in a separated processor core with priority value 0, the highest one.
The master status counters don't highlight any error.
The attached images shown the entire configuration.
Thank you in advance for your time.
Any suggestion will be very appreciated.
Best regards
Rossano
I'm facing a frustrating issue using the following configuration for my motion project.
- EtherCAT as field bus
Six axis plus a remote I/O node
- RevPi CONNECT+ 8GB as controller
with the original, even though updated, OS version
- CODESYS as automation SW solution
CODESYS V3.5 SP17 Patch 1 (64 bit)
CODESYS EtherCAT 4.1.0.0
CODESYS SoftMotion 4.10.0.0
CODESYS Control for Raspberry PI 4.1.0.0
Revolution PI Library for CODESYS 1.1.0.0
The EtherCAT lan is connected to the port eth1 which hasn't got any special configuration about IP address, it is in DHCP mode.
Issue description
Randomly, after minutes or even hours EtherCAT stop working.
The message log error shown is: "Filedbus lost synchronicity"
This kind of error apparently has nothing to do with the solution configuration and tasks cycling neither.
The EtherCAT task execution time is always below the task cycle, and other tasks too.
Furthermore, the EtherCAT task is executed in a separated processor core with priority value 0, the highest one.
The master status counters don't highlight any error.
The attached images shown the entire configuration.
Thank you in advance for your time.
Any suggestion will be very appreciated.
Best regards
Rossano