Loosing connection to emulation running on Linux ^{CODESYS Forge talk (Thread)}
Loosing connection to emulation running on Linux
Last updated: 2024-09-20

Post by pierre on difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Post)}
I included the stub files of scriptengine (codesys python api) in a directory scriptengine of a project. I tried to include librarymanager like that: from scriptengine import librarymanager visual studio code detected an error. It said librarmanager could not be found. Indeed in the stub file, this was library_manager. But if I change it in my code, the plugin doesn t work anymore. I found an easy solution to this problem. I ve just changed the copied stub files.(library_manager -> librarymanager) But I think it would be better if you update it yourself in the future.
Last updated: 2024-09-20

Post by pierre on difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Post)}
I included the stub files of scriptengine (codesys python api) in a directory scriptengine of a project. I tried to include librarymanager like that: from scriptengine import librarymanager visual studio code detected an error. It said librarmanager could not be found. Indeed in the stub file, this was library_manager. But if I change it in my code, the plugin doesn t work anymore. I found an easy solution to this problem. I ve just changed the copied stub files.(library_manager -> librarymanager) But I think it would be better if you update it yourself in the future.
Last updated: 2024-09-20

difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Thread)}
difference between stub file and source file in scriptengine
Last updated: 2024-09-20

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

Updating OPC UA Core Nodeset on PLS ^{CODESYS Forge talk (Thread)}
Updating OPC UA Core Nodeset on PLS
Last updated: 2024-09-20

Post by timvh on Stack overflow with really simple function ^{CODESYS Forge talk (Post)}
You have declared the function block in a function and call the instance also from a function. This is not correct, because a function is initialised with every call. The http client function block should be declared as Global Variable if you want to cal it from a Function, but probably it is better to declare it in a Program and also call the instance of the http function block from the same Program.... The variables of a Program are not initialised with each call.
Last updated: 2024-09-20

How to change OPC NodeId IdentifierType ^{CODESYS Forge talk (Thread)}
How to change OPC NodeId IdentifierType
Last updated: 2024-09-20

Post by thn-power on How to change OPC NodeId IdentifierType ^{CODESYS Forge talk (Post)}
Hi Yet another OPC UA question. When setting up a OPC server using "Communcation manager" (Symbol set and information model) in Codesys the NodeId is always given as "opaque" type. At least when browsing using UAExpert. Other standard OPC objects use numeric (or string) identifier, but for some reason my variables seems to get opaque/binary type. See attached photo. How can I change this? I can't see that this is a parameter in the CodesysControl.cfg. Can this be specified in the information model nodeset? And is it possible to specify the exact numeric or string NodeId for each instance? And on a related topic, is there a way to export the OPC server nodeId's with variable name so that it can be imported in a OPC Client? The .xml files in the project folder does not seem to contain the NodeId.
Last updated: 2024-09-20

Post by fmbrew-rob on Licensing info not available. ^{CODESYS Forge talk (Post)}
Was there ever any resolution to this? I am using Virtual Control SL on a ProxMox setup, and I can't get the license installed. I get the same errors reported above.
Last updated: 2024-09-21

Automation Server + Pi Gateway + PLC w/ CAN ^{CODESYS Forge talk (Thread)}
Automation Server + Pi Gateway + PLC w/ CAN
Last updated: 2024-09-22

Post by danielbeers on Automation Server + Pi Gateway + PLC w/ CAN ^{CODESYS Forge talk (Post)}
Hello, I have a project using some EPEC PLC's. Some of them are programmable using Ethernet and some use CAN. We currently have a Raspberry Pi that is acting as a gateway to the Codesys Automation Server and is successfully working for the PLC's communicating over ethernet. I am trying to achieve a similar result for the PLC's that have only CAN access. I have PEAKCan drivers on the Pi, and can successfully send/receive messages. But the Gateway does not recognise the PLC when scanned from the Automation server online. Is there a library or service that exists to translate the CAN messaging, to the Edge Gateway, and be able to achieve remote access with the Automation Server? Or is this not possible without creating something custom? Cheers, Daniel
Last updated: 2024-09-22

Post by eschwellinger on Licensing info not available. ^{CODESYS Forge talk (Post)}
you need a license server on the host or on any system in your environment.
Last updated: 2024-09-23

Post by nguyenvinh85 on J1939 Problems ^{CODESYS Forge talk (Post)}
Can you help me J1939 with ECU Cummins? thanks!
Last updated: 2024-09-23

Dongle von Linux-Modul (ARM64) nicht erkannt ^{CODESYS Forge talk (Thread)}
Dongle von Linux-Modul (ARM64) nicht erkannt
Last updated: 2024-09-23

J1939 Problems ^{CODESYS Forge talk (Thread)}
J1939 Problems
Last updated: 2024-09-23

Post by elektron785 on Dongle von Linux-Modul (ARM64) nicht erkannt ^{CODESYS Forge talk (Post)}
Ich hatte noch einmal Zeit das mit der Lizenz zu probieren und habe dazu über den Codesys Installer das Virtual Control SL runtergeladen und ausprobiert, aber leider ohne Erfolg. Zunächst habe ich "Docker_codesyscontrol_virtuallinuxarm64_4.13.0.0_arm64.tar.gz" aufs Board geladen und das Image mit docker load geladen. Mit dem Befehl docker run --rm -dt --name codesys --network host -v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ --device-cgroup-rule='c 13: rmw' --privileged 470a708f17a2 hab ich dies dann ausgeführt, aber das Problem, dass ich das Board im Netzwerk dann nicht finden konnte. Damit ich die Verbindung herstellen konnte, habe ich die Datei "DockerRuntimeStart.sh" so verändert, dass ich den Teil: -p 11740:11740/tcp \ -p 443:443/tcp \ -p 8080:8080/tcp \ -p 4840:4840/tcp \ gegen --net host \ ersetzt habe. Das Skript habe ich dann aufs Board geladen und bash DockerRuntimeStart.sh -i codesyscontrolvirtuallinuxarm64:4.13.0.0 -c codesys -H verdin-imx8mp- ausgeführt. Nun konnte ich in Codesys wieder eine Verbindung zu dem Board aufbauen, aber der Dongle wird leider immer noch nicht im Lizenz-Manager erkannt. Wie kann ich denn prüfen, dass auf den USB-Stick vom Container aus zugegriffen werden kann?
Last updated: 2024-09-23

Post by rossanoparis on Clarifications regarding the appropriate runtime system to use ^{CODESYS Forge talk (Post)}
Hallo all I would appreciate some clarifications regarding the appropriate runtime system to use. I've been using 'KUNBUS CPUs' and 'CODESYS Control for Raspberry Pi MC SL' for the last 4 years. Recently, there have been some changes in the CODESYS licensing policy. [ https://store.codesys.com/en/howto_applicationbasedlicenses ] My questions are mainly two: 1) If I need to start a new project using 'KUNBUS CPUs', which is the correct runtime system to use. 2) Old projects built using 'CODESYS Control for Raspberry Pi MC SL' should be updated to another RT system? Current RT systems ... a)CODESYS Control for Raspberry Pi MC SL b)CODESYS Control for Linux ARM SL c)CODESYS Virtual Control SL May I count on receiving an explanation to understand the differences among the runtime systems listed above? A detailed and well-organized answer would be greatly appreciated. Kind regards Rossano
Last updated: 2024-09-23

Post by tobthi on Ethernet/IP ^{CODESYS Forge talk (Post)}
Hello, I have a Cognex camera that I would like to add to my Codesys program. Communication should work via Ethernet/IP. However, I always get the following error message, which is why I can't add the camera.
Last updated: 2024-09-23

Post by pierre on difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Post)}
same situation for DeviceID. In the stubfile this is Deviceid
Last updated: 2024-09-23

Stack overflow with really simple function ^{CODESYS Forge talk (Thread)}
Stack overflow with really simple function
Last updated: 2024-09-23

Post by opineiro on Ethernet/IP ^{CODESYS Forge talk (Post)}
Hi Tobthi, Do you have the eds file of the camera? I usually load first the eds file and then add the device to the Ethernet/IP scanner.
Last updated: 2024-09-23

Post by opineiro on Stack overflow with really simple function ^{CODESYS Forge talk (Post)}
Thanks, I'm going to rework everything with this in mind.
Last updated: 2024-09-23

Post by pierre on difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Post)}
Last updated: 2024-09-23

difference between stub file and source file in scriptengine ^{CODESYS Forge talk (Thread)}
difference between stub file and source file in scriptengine
Last updated: 2024-09-23

Sort by relevance or date