CodeSys Control Win SysTray not starting ^{CODESYS Forge talk (Thread)}
CodeSys Control Win SysTray not starting
Last updated: 2021-01-08

Codesys Control WinV3 memory allocation ^{CODESYS Forge talk (Thread)}
Codesys Control WinV3 memory allocation
Last updated: 2013-11-07

Starting multiple instances of Control Win ^{CODESYS Forge talk (Thread)}
Starting multiple instances of Control Win
Last updated: 2022-07-21

Export for use with version control ^{CODESYS Forge talk (Thread)}
Export for use with version control
Last updated: 2020-01-23

Codesys Control log "eventbuffer full" ^{CODESYS Forge talk (Thread)}
Codesys Control log "eventbuffer full"
Last updated: 2024-01-17

Codesys Control for Win & WagoApp Bibliotheken ^{CODESYS Forge talk (Thread)}
Codesys Control for Win & WagoApp Bibliotheken
Last updated: 2024-02-06

CODESYS Control Standard S and Beaglebone ^{CODESYS Forge talk (Thread)}
CODESYS Control Standard S and Beaglebone
Last updated: 2024-05-11

Stepper motor control with (SM_Drive_RaspStepper_direct) ^{CODESYS Forge talk (Thread)}
Stepper motor control with (SM_Drive_RaspStepper_direct)
Last updated: 2025-11-11

Post by reinier-geers on License problem gateway ^{CODESYS Forge talk (Post)}
Epis doesnt want Softmotion. I thought it was about the price. If it was possible it would be working already and i dont need an extra licence. Thats the problem of codesys. The software is running but hangs on its license. Epis made it posible to see the stick. I can see the license. Softmotion is there from 3.5.14.Xx Like is said And Motion control is alrady posible 15 year ago. And i only need a Sync of 2 drives. I want a good solution not a refund. Dont point to the manufacturer. The software is made by 3s not by epis .
Last updated: 2024-04-29

Upgrading CODESYS runtime from v4.7 to v4.9 using a bash script leads to lose the licences stored in the soft container ^{CODESYS Forge talk (Thread)}
Upgrading CODESYS runtime from v4.7 to v4.9 using a bash script leads to lose the licences stored in the soft container
Last updated: 2023-09-19

Post by paulpotat on Can't open license manager with raspberry CM4 ^{CODESYS Forge talk (Post)}
Update : The solution I mentionned in a previous post does not always work. Some Raspberry Pi CM4 still won't create the license container. I will open a support ticket.
Last updated: 2024-10-18

Post by eschwellinger on Licensing info not available. ^{CODESYS Forge talk (Post)}
add the Container serial number this is usually 130-xxxxxxxx and last row the license ticketnumber which you got from the CODESYS Store order
Last updated: 2025-10-01

Post by alexgooi on Licensing info not available. ^{CODESYS Forge talk (Post)}
Dear Tim, This is the missing link for me. I was not aware of the fact that the docker container is claiming the smallest possible license. Now the serial number makes much more sense. Thank you
Last updated: 2025-10-02

Post by cavein on PFC100 Licensing fails ^{CODESYS Forge talk (Post)}
Hi, i have a similar problem. im using pfc200 4.5.0.0. There are two softcontainer and only one with license in it. every 1-2 hrs it will auto logoff. i tried the steps above but i dont find the /var/opt/codesys/.cmact_licenses i need help please.
Last updated: 2024-03-19

Post by rafaelbrito on Licensing info not available. ^{CODESYS Forge talk (Post)}
Hello, I'm having the same problem. I'm trying to license Codesys running in a Linux container, which I downloaded from the following link (https://hub.docker.com/r/hilschernetiotedge/codesys_control_sl_linux). The same error that you mentioned appears. Is there any solution?
Last updated: 2024-05-22

Post by dhumphries on install codesys runtime on linux ^{CODESYS Forge talk (Post)}
I'm running the 3.5.18.20 IDE, installed the control for linux SL package from the installer. Following the directions here: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_install_runtime_on_controller.html it says: Installing the runtime package with CODESYS on the Linux device Click Tools → Update CODESYS Control for <device> SL.</device> I don't have the update option in my tools menu. I've tried it without opening a project, as well as with a project open that uses the control for linux SL as a device. I have found the update device option by right clicking on the device in the device tree, but this only lets me change the device the project is using not load the runtime on the linux computer. Is there an updated instruction somewhere, or do I need to do some further preparation like install additional packages?
Last updated: 2023-11-04

Post by timvh on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
It seems you have 2 network interfaces. Did you try eth1? Did you already configure the IP address for this interface in Linux? If yes, then maybe undo this. - or only set eth0 in the Nic configuration without anything else (so no IP address, because this is already set in Linux). For more information about the Nic settings, see (probably already read it?): https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_obj_deploy_control_sl_configuration.html PS, if you only want to run CODESYS Control SL, you don't necessarily need the Virtual PLC variant. You could also install and run the CODESYS Control SL Runtime in the Host operating system. This way you should also be able to access the serial port and directly access all ethernet ports. Maybe this is easier?
Last updated: 2024-10-23

Post by talhaali on Is a Reset possible for the CoDeSys soft PLC? ^{CODESYS Forge talk (Post)}
Hi, I have got a solution. Go to local disk C. (There will be an option View on top. Click View>Show>hidden items.) go to following path:C:\ProgramData\CODESYS\CODESYSControlWinV3x64 there will be one or two files. delete it and run control win again. issue will be resolved.
Last updated: 2024-01-18

Post by alexgooi on Licensing info not available. ^{CODESYS Forge talk (Post)}
Thank you for the response, The empty softcontainer does not become visible unfortunately, but I think I can get that back to working. I think I'm misunderstanding something. You are pointing to the Softcontainer number and the ticket code, I thought that I needed to fill in the virtual control containers serial code is this a misunderstanding? And if this is indeed the case, how is the link between the server (softcontainer) and the Codesys control docker container made? If I have multiple Codesys docker containers running on the same docker server, how is the correct license distributed to the correct Codesys runtime container?
Last updated: 2025-10-02

Post by rajatdas2005 on Codesys Virtual control SL ^{CODESYS Forge talk (Post)}
Dear All, This is regarding Codesys Virtual control SL demo version. I am facing one issue. First I will describe the steps what I have followed till now. 1. In a PC I have Windows OS. Here Codesys IDE is installed, and also using the installer option of IDE I have also installed Codesys Virtual control SL. 2. A edge-gateway is also running in the same windows PC as local host. 3. Next I have a seperate PC with Ubuntu OS with docker installed. This machine is in the same network. 4. Now I have created a project in Windows machine using device "Codesys Virtual control SL". 5. In the Ubuntu machine I am running the Codesys Virtual control SL as docker and it is using the ubuntu machine network only. 6. Next using the localhost edge-gateway when I am searching the virtual control SL docker it is able to detect it. (screenshot attached) 7. But after creating the creadentials it is telling No Device is responding. 8. I have also checked the wireshark logs and able to see that in destination port 11740 data is coming. 9. From windows PC telnet ip 11740 is also working. 10. Ping is also working ===========================================LOGS ========================= sudo ss -tlnp | grep -E "(443|1217|4840|8080|11740)" LISTEN 0 10 10.135.114.142:4840 0.0.0.0: users:(("codesyscontrol.",pid=41864,fd=21)) LISTEN 0 10 172.18.0.1:4840 0.0.0.0: users:(("codesyscontrol.",pid=41864,fd=24)) LISTEN 0 10 172.17.0.1:4840 0.0.0.0: users:(("codesyscontrol.",pid=41864,fd=23)) LISTEN 0 10 127.0.0.1:4840 0.0.0.0: users:(("codesyscontrol.",pid=41864,fd=26)) LISTEN 0 10 192.168.122.1:4840 0.0.0.0: users:(("codesyscontrol.",pid=41864,fd=22)) LISTEN 0 5 0.0.0.0:11740 0.0.0.0: users:(("codesyscontrol.",pid=41864,fd=20)) LISTEN 0 128 0.0.0.0:8080 0.0.0.0: users:(("python3",pid=1280,fd=4)) LISTEN 0 10 172.19.0.1:4840 0.0.0.0: users:(("codesyscontrol.",pid=41864,fd=25))
Last updated: 2025-08-06

Post by srouse on Adding a Softmotion License to a Weintek HMI ^{CODESYS Forge talk (Post)}
I am trying to add a Softmotion license to my Weintek HMI. The HMI is already licensed for Codesys and I have already purchased a Softmotion license as well. When using the License Manager I get an error saying the licensing info is not available. I am fairly new to working with Codesys so I am at a bit of a loss and there seems very little information online about troubleshooting this specific issue. I have attached the error message below. If there are any ideas of how to troubleshoot this better I would be happy to hear them.
Last updated: 2025-01-09

Post by alexgooi on Codesys licensing explanation ^{CODESYS Forge talk (Post)}
Dear Forum, We are currently switching to a native Codesys controller, and I'm currently trying to determine the correct license. I have a question regarding the Modbus instances. With the Standard S license this is set to 4 (See picture). In our projects we are using a lot of communications to Modbus servers using a Codesys Controller, for this communication I'm using the ModbusFB library (supplied by 3S) (see picture). In my project I would like to use more than 4 instances of the ClientTCP FB. My question is, is this now capped at 4 possible connections with the standard S license. Or do these function blocks have a different relation with the license? Some clarity on this topic would be very welcome. Thank you in advance
Last updated: 2024-02-15

Post by aseitzinger on CODESYS Control for Linux SL on virtual machine? ^{CODESYS Forge talk (Post)}
Hello, there in different information available regarding the possibility to run CODESYS Control for Linux SL on a virtual machine. https://forge.codesys.com/trg/linux-sl/home/Home/ says CODESYS Control for Linux SL is a runtime system, which can run on any Debian based X86 PC, VM or Cloud container... https://store.codesys.com/media/n98_media_assets/files/2302000005/3/CODESYS%20Control%20for%20Linux%20SL_de.pdf says CODESYS Control for Linux SL can not be used on virtual hardware Currently I run the package mentioned on a virtualized debian machine running in PROXMOX Virtual Environment 7.4-17 and apart from huge jitter it runs without problems. The CODESYS key is passed as a USB defice to the VM. I wonder why there are different statements regarding the suitability in virtual machines and if the jitter would be reduced by installing CODESYS runtime on the host installing CDS runtime on the host and using a preemptive kernel (if available for the PROXMOX installation leaving CDS runtime where it is (on the virtualized debian machine) and install a preemptive kernel on the host and on the guest... Any advice is appreciated. Greets Arno
Last updated: 2024-01-08

Post by winki on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
For small project, I would like to use my industrial computer as a PLC + Industrial Computer. Like that I can save the cost of one PLC. That why I am using Codesys on Linux. With the nic it is not working. I already set the IP adress with /etc/network/interfaces. Can it comes from there ? looking to "Control Linux SL" docuemntation it should work with rtu.
Last updated: 2024-10-23

Post by paulpotat on Can't find the safety manual in the documentation ^{CODESYS Forge talk (Post)}
Hello, I was browsing the "CODESYS Virtual Safe Control for Linux SL" documentation page, and it says the following : For more information about the development of safety-critical applications with CODESYS, see: * Safety Manual H1 – SafetyManual.pdf, which is stored in the directory ../<user>/CODESYS Virtual Safe Control Linux SL/Delivery/Manuals</user> What does this path refers to ? I can't find it in CODESYS installation directories. Best regards
Last updated: 2025-01-23

Sort by relevance or date