https://forge.codesys.com/forge/talk/Runtime/thread/d0bc07a7b8/2024-04-11T06:53:45.553000ZRecent posts to RevPi CONNECT+, CODESYS, EtherCAT master "Filedbus lost synchronicity"2024-04-11T06:53:45.553000Z2024-04-11T06:53:45.553000Zrossanoparishttps://forge.codesys.com/u/rossanoparis/https://forge.codesys.comb264c357af17d2a133c373dd7e97bf16deb4e259

<div class="markdown_content"><p>Hello <a class="user-mention" href="/u/rmaas/">@rmaas</a></p> <p>I assume, you've already verified and tuned everything regarding the EtherCAT network.</p> <p>In my case the problem was due to a wrong core assignement.<br/> I suggest to not use the core #0 for your EtherCAT task.<br/> The OS realtime patch, which is present on RevPi OS, uses the core #0 for its porpouses and it mustn't be used by any other task which requires realtime and deterministic features. </p> <p>regards<br/> Rossano</p></div>

2024-04-11T06:17:59.610000Z2024-04-11T06:17:59.610000Zrmaashttps://forge.codesys.com/u/rmaas/https://forge.codesys.com9899382809341aa68688b50ba5a77eb1f4de8052

<div class="markdown_content"><p>Hi Rossano,</p> <p>Did you ever find a solution to this issue? It seems i am facing the same issue but i do not use OPCUA...</p> <p>Best Regards,<br/> Rinie Maas</p></div>

2021-08-16T07:45:36.272000Z2021-08-16T07:45:36.272000Zrossanoparishttps://forge.codesys.com/u/rossanoparis/https://forge.codesys.com092afa5ed46fb5cab3918f259e0bc458b346b53a

<div class="markdown_content"><p>Good morning everybody.<br/> I want to share this issue I was facing during last weeks, now it is solved, but I'd like to receive some comments from CODESYS engineers, just for my knowledge.</p> <p><strong>My configuration</strong><br/> CODESYS V3.5 SP17 Patch 1 (64 bit)<br/> CODESYS EtherCAT 4.1.0.0<br/> CODESYS SoftMotion 4.10.0.0<br/> CODESYS Control for Raspberry PI 4.1.0.0<br/> Revolution PI Library for CODESYS 1.1.0.0<br/> Controller: RevPi KUNBUS CONNECT+</p> <p><strong>Issue description</strong><br/> Randomly, after minutes or even hours EtherCAT stop working.<br/> The message log error shown is: "Filedbus lost synchronicity"<br/> This kind of error apparently has nothing to do with the solution configuration and tasks cycling neither.<br/> The EtherCAT task execution time is always below the task cycle, and other tasks too.<br/> Furthermore, the EtherCAT task is executed in a separated processor core with priority value 0, the highest one.<br/> The master status counters don't highlight any error.</p> <p><strong>Solution</strong><br/> I've found the origin of the issue I was observing.<br/> It was due to OPCUA server or something related to.<br/> An application (bad implemented) instead of open the communication channel and keep it open for performing read/write actions on variables values, <strong>every one second</strong> the application opened the communication channel did actions on variables and closed the channel.<br/> This kind of behaviour led the EtherCAT master to lose sync.</p> <p>Currently the application with the unusual behaviour has been modified and the problem did not appear any more.<br/> Even though the problem was caused by this unusual use of OPCUA protocol, I'm not able to recognize a direct cause.</p> <p>Thank you for your time<br/> Best regards<br/> Rossano Paris</p></div>