Post by timvh on PROFINET Controller SL: WRREC remains BUSY forever, no DCE/RPC packets transmitted (RevPi Connect 5 + NORD SK205E) ^{CODESYS Forge talk (Post)}
A customer of us had the same issue. They updated (at that time) to CODESYS 3.5.21.50 and Control for Linux SL versie 4.19.0.0. After that they couldn't reproduce the issue anymore. You might give this a try too.
Last updated: 2026-07-21

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 gatto on Two licenses have to be installed forgot to enable one license ^{CODESYS Forge talk (Post)}
Sorry, I've never used Raspy. Maybe someone else can help. From personal experience, I've had license activation issues, but it was caused by my company firewall, which was blocking traffic from the Codesys license server. So I found that the license was listed as activated on the server (and therefore used and no longer activable), but it wasn't present in the PLC. I solved the problem by using an unblocked internet connection when I needed to activate the purchased license ticket. Since then, the activation process has always worked, and I've never lost any licenses.
Last updated: 2026-02-03

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 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

Post by john-martin on Control SL Extension Package doubts ^{CODESYS Forge talk (Post)}
Hello everybody, I'm trying to understand the SL control extension package, more specifically, the external IODriver example, because C integration is very easy and I just made my first C component successfully. Ther External IODriver has no documentation and it's not clear how to proceed. Furthermore, there is no information on how to modify the device descriptor, which is necessary to import the device into the Codesys repository. Any advice ? Thank you in advance and best regards.
Last updated: 2024-02-28

Post by elektron785 on Dongle von Linux-Modul (ARM64) nicht erkannt ^{CODESYS Forge talk (Post)}
Die Ausgabe bei lsusb ist im ersten Post im Bild usb.png zu sehen - der Dongle wird als WIBU Systems CmStick erkannt. Um Codesys als Soft-PLC darauf zum laufen zu bekommen habe ich das Addon Codesys Control for Linux ARM SL installiert und mir einen Docker gebaut mit den Dateien: codesyscontrol_linuxarm64_4.10.0.0_arm64.deb und codemeter-lite_7.60.5625.503_arm64.deb Wenn ich den Docker ausführe sind die beiden Programme ja inbegriffen und Codemeter sollte eigentlich die Erkennung des Dongles sicherstellen. Gibt es eine Möglichkeit festzustellen, dass Codemeter korrekt ausgeführt wird?
Last updated: 2024-09-05

Post by eschwellinger on Changed Device of Rapberry Pi to MC SL instead of standard SL and cannot connect anymore ^{CODESYS Forge talk (Post)}
1) https://store.codesys.com/en/codesys-control-for-raspberry-pi-sl.html -> SL: Restrictions The combination of Raspberry Pi and a CODESYS Runtime is for private use, test and teaching purposes. Commercial use is not permitted. 2) you could switch between them by /etc/codesyscontrol/CODESYSControl_User.cfg [CmpRasPi] Architecture=armv7l for MC: armv7l for SC: armv6l for 64Bit: aarch64 or in the Deploytool:
Last updated: 2025-08-06

Post by manuknecht on Using an Axis of an Axis Group in Torque Conctrol ^{CODESYS Forge talk (Post)}
I don't seem to be able to use an axis, which is part of an Axis Group in torque control mode. I call the SMC_SetControllerMode FB to switch from position to torque control mode, followed by the SMC_SetTorque FB to set the desired torque. This works flawlessly for most axes, however if an axis is part of an axis group, switching the controller mode seems to work without any issues, but the desired torque is never set. SMC_SetTorque does not return an error, but fSetTorque of the axis is never changed. Disabling the axis group before does not change anything, but if I use MC_UngroupAllAxes before changing the controller mode, it all works as it should. Is there no way to control a single axis in torque control, if it is part of an axis group?
Last updated: 2025-07-17

Post by ranadheer on PHOENIX CONTACT Axioline PLCnext project in CodeSys SodftPLC ^{CODESYS Forge talk (Post)}
Thank you Pernockham, I am using Windows SoftPLC and the device is CODESYS Control Win V3 x64. In the above attached example, the file is Linux-based. This is an external add-on file in the CODESYS installer (CODESYS Control for PLCnext SL). I am trying to implement it without this add-on file.
Last updated: 2025-09-09

Post by dhumphries on Control Runtime Toolkit ^{CODESYS Forge talk (Post)}
I have a video demonstrating the procedure to install the runtime on a linux device. https://youtu.be/rj0dOhgnGjs?si=OJoA-kgc1saxIweR This demonstration shows how to install the runtime on a X86 based controller, it should be the same for an ARM based device, but you'll need to install the add-in for Codesys control for Linux ARM SL (or the 64 bit add-in.)
Last updated: 2023-12-30

Post by wold on CodeMeter Network Server: Keep runtime dongle local-only and export only a second CmStick ^{CODESYS Forge talk (Post)}
Hello, I am running a CODESYS Control Runtime on a Raspberry Pi. Two CmSticks are connected to the same system: CmStick A - Runtime license - MultiCore license - KNX license CmStick B - Engineering / Developer licenses My goal is: The runtime on the Raspberry Pi shall use CmStick A locally. Licenses from CmStick A shall NOT be provided by the CodeMeter Network Server. Only licenses from CmStick B shall be available to remote network clients. During troubleshooting I observed that the CodeMeter Network Server collects licenses from both CmSticks. The KNX license appears to be local-only, but the runtime and multicore licenses of the same dongle are still visible through the server. I would like to know if a supported configuration exists for the following scenario: One CmStick remains strictly local to the runtime. A second CmStick on the same machine is exported through the CodeMeter Network Server. Questions: Is it possible to exclude a specific CmStick from being exported by the CodeMeter Network Server? Can this be configured via License Access Permissions (ACL), WebAdmin, or another mechanism? Can export rules be applied per CmStick, per Firm Code, or per Product Code? If supported, could you provide a configuration example or a reference to the relevant documentation? The reason for asking is that after removing a separately installed CodeMeter server component and returning to a local-only setup, the runtime licensing behaviour became stable again. Therefore I am looking for the officially supported way to keep the runtime dongle local while still providing engineering licenses from a second dongle over the network. Thank you.
Last updated: 2026-08-02

Post by dhumphries on install codesys runtime on linux ^{CODESYS Forge talk (Post)}
Adding the command worked. I was able to deploy the runtime on an ubuntu server installation. Thanks!
Last updated: 2023-11-04

Post by eschwellinger on TargetVisu on Raspberry? ^{CODESYS Forge talk (Post)}
install this: https://store.codesys.com/de/codesys-targetvisu-for-linux.html via CODESYS Installer and deploy it by update command
Last updated: 2024-07-26

Post by eschwellinger on Update Raspberry Pi option is missing under Tools menu ^{CODESYS Forge talk (Post)}
The new Deploy Tool 4.14.0.0 contains all devices. Raspberry PI virtual plc etc.
Last updated: 2024-12-13

Post by eschwellinger on No Visu on RasPi ^{CODESYS Forge talk (Post)}
..on 4.12.0.0 release there it will be possible to deploy RemoteTargetvisu which is what you expect now. (next week)
Last updated: 2024-06-20

Post by eschwellinger on search runtime 4.9.0.0 for pi 3 ^{CODESYS Forge talk (Post)}
runtime could always be in latest version. just keep everything in CODESYS stable and deploy the latest runtime. This will work.
Last updated: 2025-10-25

Post by arj3090 on Linux ARM64 Deploy Fail - Index out of range ^{CODESYS Forge talk (Post)}
This is the version shown in the CodeSys Installer.
Last updated: 2026-07-01

Post by chris12345 on IO-Link Lizenz ^{CODESYS Forge talk (Post)}
Moin, IO-Link läuft nur 30 Minuten im Demo Modus. In meinem Fall, brauch ich zusätzlich zur "CODESYS Control for Raspberry Pi MC SL" diese Lizenz :- https://store.codesys.com/de/codesys-io-link-master-for-el6224-sl.html Gruß Chris
Last updated: 2023-10-11

Post by eschwellinger on Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2" ^{CODESYS Forge talk (Post)}
Ich fürchte fast, das musst du mal an den Wago Support adressieren.. oder vielleicht ließ hier einer mit?
Last updated: 2023-11-17

Post by ggis on Rasperry Control Debian 12 ^{CODESYS Forge talk (Post)}
From bash I usually see codesyscontrol.service as the runtime service. Taking a step back, I guess you used Tool > Update RaspberryPi SL interface to install the runtime: what does the info popup window tells you about your destination system?
Last updated: 2023-11-26

Post by damian177 on Codesys Control for Linux SL ^{CODESYS Forge talk (Post)}
In /etc/CODESYSControl.cfg I only added: [SysCom] Linux.Devicefile=/dev/ttyS Is ok ? Now in Codesys I should have mapping like below : COM1 - ttyS0 COM2 - ttyS1 ?
Last updated: 2024-09-08

Sort by relevance or date