Thank you for the answer.

Reinstalling the Codesys and installing the components from the imported colleague's configuration file solved the issue. Thanks! [ { "Key": { "Id2": "CODESYS.Application Composer", "Id": "68d4dade-c077-4640-8947-403028a81dcd" }, "Version":...

Hello Giuseppe,

the problem also occurs in the example projects. The wrong device order is not the problem here.



Best regards.

Hello, I am trying out the new CODESYS Library 'Revolution Pi Library for CODESYS 1.3.0.0' I have followed the instructions in the tutorial and in the CODESYS checklist. I have installed the CODESYS Control for Raspberry PI 4.6.0.0 package and the Revolution Pi Library for CODESYS 1.3.0.0. I am usin...

Hello Ulrich, we updated the controllers to MC SL version of the runtime. Also, we put some more controllers to our testing environment, installed the CODESYS Control for Raspberry Pi MC SL runtime, and licensed them with the propriate license. Also, we have done everything the provided Codesys chec...

https://forge.codesys.com/forge/talk/Ru ... it=25#4ad8

Some useful information in the link in the comment of this post ^^

https://forge.codesys.com/forge/talk/Ru ... it=25#4ad8

Some useful information in the link in the comment of this post ^^

viewtopic.php?t=3855

Here is some more discussion about the Standard or Multicore Runtime.

Hello Ulrich, thank you for your response. I must ask, how can I be sure that the license is the cause of this behavior? I don't see any indication in the logs that there is a problem with the license. Since I have bought licenses, I would not want it to happen that I buy them again, more expensivel...

Hello, I have a few RevPi PLC controllers licensed with 'CODESYS Control for Raspberry Pi SL'. CODESYS runtime randomly stops working on the controllers - Modbus server is stops being reachable and I don't see the controllers when I scan network with CODESYS. Controllers are working properly, and th...