Post by janber0206 on RPI is license server down ^{CODESYS Forge talk (Post)}
I had the same problem. Problem solved: all licences purchased before October 2022 must be updated by Codesys. To do so, simply contact the support in the Codesys Store.
Last updated: 2023-10-30

Post by janber0206 on Lizenz lässt sich nicht aktivieren für Revolution Pi ^{CODESYS Forge talk (Post)}
Problem gelöst: alle Lizenzen die vor Oktober 2022 gekauft wurden, müssen von Codesys aktualisiert werden. Dafür einfach den Support anschreiben im Codesys Store.
Last updated: 2023-10-30

Post by dasch on eCockpit - unable to start simulation ^{CODESYS Forge talk (Post)}
This is a known bug in e!Cockpit. See Release notes of V 1.11: 1 e!Cockpit Release Version 1.11 (2022-07) ATTENTION: If a library that uses asynchronous tasks (e.g. WagoAppConfigTool, WagoAppCloud or function modules such as Dali-Master) is dragged into the project, the simulation cannot be started. It is already sufficient to add the library to the project (an FB does not even have to be instantiated). I guess you are using one of these libraries/modules in your project. We e.G. often use PWM modules, these are also affected.
Last updated: 2023-09-05

Post by yongchaow on Can't connect to Device Raspberry Pi 4 from CODESYS IDE V3.5 SP19 ^{CODESYS Forge talk (Post)}
Hi, eschwellinger, I have the same problem, but I can not resolve the problem following this forum. There are my situation: pi@RevPiXXXX:~ $ uname -a Linux RevPiXXXX 5.10.120-rt70-v7l #1 SMP PREEMPT_RT Thu, 28 Jul 2022 10:36:48 +0200 armv7l GNU/Linux After "top": It looks like runtime is not running. One more piece of information to refer to, when I reboot the device it is possible to scan the device. Looking forward your reply.
Last updated: 2024-04-25

Post by thn-power on Codesys Communication Manger - Required information model version exists in the model repository but is not found ^{CODESYS Forge talk (Post)}
Hi. Thanks for the answer. I think I found your post on the Wago forum. I have tried installing all different nodeset versions of the opcfoundation.org/UA but neither work. Though I could not find the nodeset version called 15.09.2021 anywhere online. The opcfoundation repository only goes back to version 1.04.11 2022-03-29. Also wondering how I can generate a custom information model that only refrences the latest version of nodesets?
Last updated: 2024-09-19

Post by mp9876 on Problems with simulation in Window 10 ^{CODESYS Forge talk (Post)}
Hi Automa, it seems the solution you were bringing up on 2022-04-06 could really help me as I did not remember the password I initially set. My problem though is that I am using Codesys Control Win V3.5 SP19/60 (64 bit) and I cannot locate any of the files you listed up there. I have been looking inside folder: C:\Program Files\CODESYS 3.5.19.60\CODESYS\ and they appear not to be present at all neither in the CODESYS folder or any sub-folders. Uninstalling and re-installing unfortunately does not do the trick. Any idea how I could get out of the ditch on this issue ? Anyone else maybe ? Thanks
Last updated: 2024-03-18

Post by ricola on Change default node Id name on Raspberry Pi ^{CODESYS Forge talk (Post)}
EDIT : https://forge.codesys.com/forge/talk/Engineering/thread/cb5a492aa0/ hyplcmotion - 2022-12-16 Found out how! Needed to connect to PFC200 via Putty, and open CodesysControl.cfg with “sudo nano /etc/CODESYSControl.cfg”. Then adding following command to the end of file, and use the name you want, save/close CODESYSControl.cfg, and reboot your PLC. [CmpOPCUAProviderIecVarAccess] CustomNodeName= PFC200 Hi! , I'm digging up this issue cause we have still this long name within current versions on CodesysControl. Is it a lock for "demo" licences or can it be changed in some way ? This DeviceSet name is too way long with spaces inside, not easy to handle with string parsing... Cheers !
Last updated: 2024-10-10

Post by thn-power on Updating OPC UA Core Nodeset on PLS ^{CODESYS Forge talk (Post)}
Hi After much trail and error I think I found the root cause to my OPC UA problem. The problem is that I cannot manage to build and download a program with a a custom OPC UA Information model. We use a Weidmueller WL2000 PLS, but the problem also exsist on the Win V3 PLC. Our custom information model is based on the latest versions of the OPC UA Core Nodeset v 1.05.03 (2023-09-20) and UA/DI nodeset 1.04.0 (2022-11-03) Those nodesets are installed in the Codesys Information Model Repository (3.5.19.6) However, when trying to build I get the following error. [ERROR] Untitled1: Communication Manager [Device: PLC Logic: Application]: The information model http://opcfoundation.org/UA/ is required by http://bos.org/ with a minimal publication date from 15.12.2023 but the device has only a model from 15.09.2021 installed. Probably the information model from 15.09.2021 is missing in the information model repository. [ERROR] Untitled1: Communication Manager [Device: PLC Logic: Application]: The information model http://opcfoundation.org/UA/DI/ is required by http://bos.org/ with a minimal publication date from 03.11.2022 but the device has only a model from 09.03.2021 installed. Probably the information model from 09.03.2021 is missing in the information model repository. Build complete -- 2 errors, 1 warnings : No download possible I think the problem is that the UA Core nodeset is implemented in the PLC firmware (at least that in Siemens S7), and that only includes the "old" nodeset from 2021-09-21 etc. So the question is, how (or if?) can I transfer the new nodeset to the PLS? I have created separate Information models under Communication manager with the newer code nodesets (UA and DI). But it seems that the compiler does not recognize them being excising, neither in the Codesys IDE or on the PLC. Would have guessed that this is a common issue, sine many manufacturers use the latest versions of the OPC UA standard, and that it would be a solution to the problem.
Last updated: 2024-09-20

Sort by relevance or date