Post by janderson on OPC UA Server limitations, large array crashes runtime ^{CODESYS Forge talk (Post)}
What are the limitations of the OPC UA Server? I am trying to get data off my PLC that is acquired at high rates (~50k samples/s) so I am storing them in arrays and trying to get the arrays off the PLC. When I attempt to read a ~200k element array through OPC UA the server and runtime crashes (requiring tools -> update linux arm64 -> start runtime). Is there a better way to get highspeed data off? The ACDatalog library seems a bit irritating to use so I would prefer to go through OPC UA.
Last updated: 2023-08-23

Post by xiaolo on Raspberry Pi 5 ^{CODESYS Forge talk (Post)}
Does Ver. 4.12 support Raspberry Pi 5? I have three issues. The first issue is that Codesys cannot detect the RPI 5 when I want to download the runtime. When assigning the IP Address manually then I can download the runtime. The second issue is that I cannot connect to the RPI to download a program. Sometimes the window pops up and it ask for the user credentials, but it is still not connecting. The third issue is that I cannot connect to an ESP32 configured as a Modbus Slave with a Raspberry Pi 4B. I can connect to the ESP32 via a Radzio! Modbus Master Simulator. I am also missing the function Write Holding Registers in the setup of the slave. Are this known issues and when it will be solved?
Last updated: 2024-07-12

Post by pernockham on How to manage soft container licenses for (remote) multi units? ^{CODESYS Forge talk (Post)}
Using Codesys runtime for Linux and thinking of the process of preparing multiple such systems for my customer. I don't necessarily have physical access to these units, they can be (very) remote. The idea so far is to use an image to install the Linux OS and codesys runtime. Application updates can be done by distribution of the PlcLogic/Application/application.app and application.crc files. But whats the most practical way of managing the license for these units? Do each controller need to be physically connected to a License Manager instance or can licenses be distributed by means of a license file for each unit? I believe that the license should be stored in soft containers for each unit. Help and insights appreciated! Per
Last updated: 2025-04-04

Post by preimesbergert on Raspberry Pi 4 B HW 1.5 Codesys control 4.10.0 stopps after a few seconds ^{CODESYS Forge talk (Post)}
Wanted to play a bit with a raspberry Pi 4 Model B HW 1.5 and Codesys. Regardless of the image (tried 32bit / 64bit version from Raspberry Pi Imager) and with all tested Codesys Control versions (4.2.0, 4.8.0, 4.10.0) and regardless if single core / multicore / 64 bit variant, always is the runtime stopped after about 30sec with the nice message: ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-7, 0x00000BB8, 0xFFFFFFFB) Whats wrong with it?!?!? I read a lot about the issue in topics from 2020-2021 but it always was stated with new Codesys control version issue will be fixed (4.4 for example) but still it is there.
Last updated: 2023-12-21

Post by preimesbergert on Raspberry Pi 4 B HW 1.5 Codesys control 4.10.0 stopps after a few seconds ^{CODESYS Forge talk (Post)}
Wanted to play a bit with a raspberry Pi 4 Model B HW 1.5 and Codesys. Regardless of the image (tried 32bit / 64bit version from Raspberry Pi Imager) and with all tested Codesys Control versions (4.2.0, 4.8.0, 4.10.0) and regardless if single core / multicore / 64 bit variant, always is the runtime stopped after about 30sec with the nice message: ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-7, 0x00000BB8, 0xFFFFFFFB) Whats wrong with it?!?!? I read a lot about the issue in topics from 2020-2021 but it always was stated with new Codesys control version issue will be fixed (4.4 for example) but still it is there.
Last updated: 2023-12-21

Post by mondinmr on Shared Memory Access Issues ^{CODESYS Forge talk (Post)}
In Windows I need create shared memory in PC software and connect from CODESYS. If shm is not GLOBAL doesn't work due different users between runtime and PC software. PC software need admin privileges. Name need "Global\\" before key. Very unsafe!!! If CODESYS create shared I cannot find key PC side. In Linux I can create shared memory as standard user, bind in the runtime docker, use keys without any "Global\\". Much more safe!!! If CODESYS create shared you need play with permissions to use app as standard user. I prefer create form PC software as standard user.
Last updated: 2024-01-30

Post by valenting on Runtime not working on raspberry pi Bullseye ^{CODESYS Forge talk (Post)}
Hello I have a problem with Codesys on Raspberry pi with Bullseye The device is not recognized as a Raspberry pi, as I get this error : ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-18, 0x00000BB8, 0xFFFFFFFB) I'm running Codesys on a compute module 4S with Raspbian GNU/Linux 11 (bullseye), my kernel version is Linux 5.10.90-v7l+ Codesys version is the latest, released last week (4.11.0.0, CODESYS Control V3.5.19.61 for ARM-32Bit - build Feb 22 2024) I know it works on the same device if I use Raspbian 10 (Buster) with Linux 5.4.81-v7l+ kernel, but for some other reasons I have to use Bullseye. What can I do ?
Last updated: 2024-03-01

Post by valec on Connect local Asem HMI runtime to local Codesys Control Win V3 x64 ^{CODESYS Forge talk (Post)}
I have a project made on a PL700 PLC with Codesys and an Asem Premium HMI panel. I don't have access to the physical PLC right now, so I'm trying to use Codesys Control Win V3 x64. I created the application and loaded "Codesys Control Win V3 x64" without errors, then I activate "Start PLC" from the tray. Asem cannot connect. I tried to use "localhost" or the local IP address and it doesn't work (it's the "CoDeSys Soft PLC Communication Driver"). I need to connect my local Asem runtime to a virtual Codesys application on my PC. How can I do it?
Last updated: 2024-03-26

Post by toffeebonbon on Die richtige CODESYS-Runtime auf dem Raspberry Pi ausrollen (3.5 SP18) ^{CODESYS Forge talk (Post)}
Guten Morgen, wie der Titel verrät soll es hier um das Ausrollen der CODESYS Runtime auf einem Raspberry Pi gehen. Ob ein klassischer Raspberry Pi aus dem Consumer-Bereich oder ein Compute-Modul spielt in dem Fall keine Rolle. Ich möchte nur anderen Nutzern Hilfestellung geben, die vielleicht ein vergleichbares Problem haben wie ich: Auf Raspberry Pi lief bei mir eine Anwendung, die mit Lizenzen auf einem CODESYS-Dongle lizenziert waren (Multicore-Support und Softmotion). Nach einem Hardware-Defekt habe ich meinen Rasperry Pi gegen eine robustere Lösung getauscht. Ich wollte auf der neuen Hardware die Runtime ausrollen und habe ständig den Fehler gezeigt bekommen, dass die Target- oder Zielsystem-ID nicht stimmt. Für den Raspberry Pi gibt es ja drei verschiedene Optionen der Runtime: 32bit Singlecore (armv6l) 32bit Multicore (armv7l) 64bit Multicore (aarch64) Entscheidend dafür, ob die 32 oder 64 Bit Runtime benötigt wird ist das auf der dem Raspberry Pi installierte Betriebssystem. In meinem Fall hatte ich durch die neue Hardware auch ein aktuellen Betriebsystem-Image aufgespielt, weshalb sich da der Umstieg von 32 auf 64Bit eingeschlichen hatte. In der Entwicklungsumgebung kann über Tools -> Control SL ausrollen das Fenster geöffnet werden, um die richtige Laufzeitumgebung auf dem Steuerungsrechner zu installieren. Bei kleinen Bildschirmen (bei mir ein 15" Laptop) kann der rechte Bereich "abgeschnitten" und das Dropdown-Menü als solches nicht auf den ersten Blick erkennbar sein. Mein Fehler war, dass ich den Scrollbalken nicht gesehen habe! (Bild im Anhang mit freundlicher Genehmigung von Herrn Heberle vom CoDeSys-Support) Nach dem auswählen der jeweils passenden Version kann die Runtime installiert und das Programm wieder geladen werden. Die Lizenzen sind bei mir wieder korrekt erkannt worden und alles läuft wie vorher (nur mit neuer Hardware). Vielen Dank an der Stelle noch mal an die schnelle Hilfe vom Support. Das hat wirklich top funktioniert.
Last updated: 2025-02-27

Post by harryc on Soft Container License issue with ARM64 Linux ^{CODESYS Forge talk (Post)}
Hi, We are working to provide our customers with CODESYS operation on our hardware product ( https://elprotech.com/product/el-qe-e-quantum-edge-series/ ). I'm trying to enable a CODESYS license (Soft container) on our product running ARM64 linux. This problem am having looks similar to here: https://forge.codesys.com/forge/talk/Runtime/thread/6d29b6b4de/ and here: https://forge.codesys.com/forge/talk/Runtime/thread/a2d0c63375/; but I am not running docker, and I am not re-installing a license. This is first time install. I have CODESYS Control SL running on my device, as well as CodeMeter. I purchased a license, and installed it to the CODESYS Development system, (Tools >> License Repository) then tried to install to the device (Tools >> License Manager >> o Device >> o Soft container >> Remote [0001] >> OK. This gives me the "License Manager - Overview" dialog, and the message "Licensing info not available. There is no dongle attached to the device." Below shows the running applications, installed packages, and current content of /var/opt/codesys Also attached screenshots of the Development software as I go through the steps to install the license. # # ps | grep -e "code" -e "CodeMeter" 1391 daemon /usr/sbin/CodeMeterLin 1407 root /opt/codesys/bin/codesyscontrol.bin /etc/codesyscontrol/CODESYSControl.cfg 1442 root /opt/codesysedge/bin/codesysedge.bin /etc/codesysedge/Gateway.cfg 29229 root grep -e code -e CodeMeter # dpkg -l Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-=============-============-============================================================================================== ii codemeter-lite 8.20.6539.500 arm64 WIBU CodeMeter minimal runtime ii codesyscontrol 4.14.0.0 arm64 codesyscontrol based on SDK 3.5.20.40 , from Fri Nov 29 08:35:37 CET 2024 [265], Release build ii codesysedge 4.14.0.0 arm64 codesysedge based on SDK 3.5.20.40 , from Fri Nov 29 08:34:19 CET 2024 [265], Release build # ls -la /var/opt/codesys total 208 drwxr-xr-x 6 root root 4096 Nov 7 05:31 . drwxr-xr-x 1 root root 4096 Nov 6 08:33 .. -rw-r--r-- 1 root root 23515 Nov 7 07:26 .Audit.log -rw-r--r-- 1 root root 160 Nov 7 05:31 .GroupDatabase.csv -rw-r--r-- 1 root root 160 Nov 7 04:37 .GroupDatabase.csv_ -rw-r--r-- 1 root root 20736 Nov 29 2024 .SoftContainer_CmRuntime.wbb -rw-r--r-- 1 root root 1982 Nov 29 2024 .UFC_SoftContainer_CmRuntime.WibuCmLif -rw-r--r-- 1 root root 229 Nov 7 04:35 .UserDatabase.csv -rw-r--r-- 1 root root 229 Nov 7 04:35 .UserDatabase.csv_ -rw-r--r-- 1 root root 11807 Nov 7 05:30 .UserMgmtRightsDB.csv drwxr-xr-x 6 root root 4096 Nov 6 08:30 .pki drwxr-xr-x 3 root root 4096 Nov 6 08:30 OPCUAServer drwxr-xr-x 7 root root 4096 Nov 6 08:30 PlcLogic -rw-r--r-- 1 root root 13 Nov 6 08:30 SysFileMap.cfg -rw-r--r-- 1 root root 2640 Nov 29 2024 bacstac.ini drwxr-xr-x 4 root root 4096 Nov 6 08:30 cert -rw-r--r-- 1 root root 94105 Nov 7 07:25 codesyscontrol.log # # uname -a Linux Remote 6.1.22 #5 SMP PREEMPT Tue Nov 18 11:35:46 AEST 2025 aarch64 GNU/Linux #
Last updated: 2025-12-04

Post by sukrit on What licenses are required for runtime on raspberry pi cm4 ^{CODESYS Forge talk (Post)}
We have developed a project for 2 servo motors using raspberry pi computemodule 4 on ethercat master. we are using web visualization for display different screens. project is running well in demo. we want to implement it in production envoirment. being new still wondering which licences i need. Can We get this information in codesys devlopment software. code size is approx 5 mb, 1 instance of etharcat master and aproox 100 variables in visaualization.
Last updated: 2023-10-17

Post by fred on Rasperry Control Debian 12 ^{CODESYS Forge talk (Post)}
Hi, I have Proxmox running on a Rasperry 4 and have debian 12 ARM installed here. I wanted to install Codesys Control for Raspberry on it. According to the messages, the runtime environment and the gateway were installed successfully, but I can't find a device to downplay a program. The sudo service codesys start command fails. (see image) Does somebody has any idea? Thank you for your help! Greetings Fred
Last updated: 2023-11-22

Post by jeffg on License issue with visu tags ^{CODESYS Forge talk (Post)}
I seem to be having a problem with the license on ver 3.5.19 patch 5 The runtime keeps going into demo mode but it wont tell me the reason I looked at the license software metrics and the visu doesn't appear to be working I attached screen shots of the metrics screen and the license dongle that is plugged in to the windows PC Anyone have any ideas on how to fix this
Last updated: 2024-06-28

Post by andre-luis on Check if Codesys runtime is on 'Running' or 'Stopped' state? ^{CODESYS Forge talk (Post)}
Just to share, for those who as me are seeking for this and had found no information anywhere in this World: Every time I stop/start the PLC runtime ( turning into 'Stopped' or 'Running' state ) the 'CODESYSControlService' appears at the Taskmanager list, which could suggest a straight correlation. I was expecting a clever solution, but this one solves for while.
Last updated: 2024-07-02

Post by bfunk on Codesys 3.5 auf Wago 750-8101 ^{CODESYS Forge talk (Post)}
Moin, hat hier noch jemand das Problem, das die Codesysruntime (PFC100, Ver.4.11, projektiert mit Codesys 3.5.20sp1), auf der Steuerung nach kurzer Zeit mit einem AUSNAHMEFEHLER in STOP geht? Ich hatte das ganze schon am laufen, sollte dann ein Firmwareupdate durchfuehren (auf die neuste moegliche). Das Firmwareupdate konnte ich auf 03.10.08(22) ist sauber durchgelaufen, die Firmware laeuft auch noch wenn die runtime aufgegeben hat. bekomme die runtime nur dann wieder zum laufen, wenn ich den ganzen controller reboote.
Last updated: 2024-07-03

Post by nano on Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Post)}
in the codesyscontrol.cfg or codesyscontrol_user.cfg you have to declare whoch comport-ports from runtime are used. please tell us how the comport is called in linux an post the codesyscontrol.cfg files also write down here, which parameters are used in the python-script and what is parameteized in the modbus-master-comport of your codesys-application. mostly the errors occurs in ine of these areas
Last updated: 2024-07-11

Post by aliazzz on Unable to deploy Virtual Control SL on ARM64 (Raspberry Pi5) ^{CODESYS Forge talk (Post)}
An interesting remark for CODESYS Support. I found this after looking through the Runtime Deploy Tool messages when I connect to an AMD64 architecture Successfully Connected to Target ( {MyIP} - AMD64 ) when I connect to an ARM64 architecture (Raspberry Pi5) Successfully Connected to Target ( {MyIP} - ) As clearly seen in the attached .png, the AMD64 target is detected, while the ARM64 target architecture is not detected (displayed). I assume that this is the reason why the pulldown menu isn't populated correctly.
Last updated: 2024-07-28

Post by paulpotat on Can't open license manager with raspberry CM4 ^{CODESYS Forge talk (Post)}
Hello, I have a problem when opening the license manager for my raspberry pi (CM4 model) with runtime 4.13.0.0. I select "Device" --> "Soft Container" and click on my device in the scan window but I get this error message : Licensing info not available. There is no dongle attached to this device. I can't install licenses anymore, and I don't understand why is CodeSys looking for a dongle when I specified I wanted to use a Soft Container. Can somebody help me please ? Best regards
Last updated: 2024-10-04

Post by vincentger on using ADS1115 ^{CODESYS Forge talk (Post)}
Any reason the ADS1115 wouldnt work with SP20.1 and Runtime 10.0.0.0 on the Raspberry Pi . Using Bullseye or Buster i run into the same issue: Libary and integration works in general as described above BUT i am seeing "bleeding" between the analog inputs . Specifically consecutive ones: So sometimes the raw from AI1 shows on AI2, AI2 on AI3, .. AI4 on AI1. Even with filtering i cant smoothen that out properly and i feel like something is wrong. Almost like the bus is stumbling over itself, or the request from Codesys to the device.
Last updated: 2024-10-28

Post by aliazzz on Runtime licenses not detected => DEMO Mode 2hour ^{CODESYS Forge talk (Post)}
Hi! After upgrading all my licensed runtimes to V4.14.0.0 (= RaspberryPi SL, LinuxSL and ControlWin x64 SL) I found out via the logfiles they all defaulted back into DEMO mode while all runtimes have a USB dongle inserted. So, my main question is how I can get the Dongle license detected? I use License Server 4.14.0.0 and Edge Gateway 4.14.0.0 on all platforms Any suggestions are welcome.
Last updated: 2024-12-15

Post by aliazzz on Raspberry Pi 3: Linux/ARMHFv7 unknown container technology ^{CODESYS Forge talk (Post)}
Hi CODESYS team! It seems Podman for Raspberry Pi 3 is not detected correctly in the latest "Deploy Control SL 4.14.0.0" : Linux/ARMHFv7 unknown container technology. 1) The Communication Tab, device information section shows podman technology as DETECTED. 2) The Runtime Deployment menu message says: "unknown container architecture" 3) The pulldown window under the deployment tab doesn't show the options for ARMHF Virtual Edge SL and ARMHF Virtual Control SL. I hope you can fix this soon and keep up the great work!
Last updated: 2024-12-15

Post by atone on Set DeviceID of an IO-Link Sensor at Runtime ^{CODESYS Forge talk (Post)}
I need to be able to change (set) the DeviceID of an IO-Link sensor (see DeviceID.png) at runtime. I tried with both ProfinetCommon.PN_PortConfiguration and ProfinetCommon.IOL_PortConfiguration, but I get an error for both when I try to read the port configuration (see PN_PortConfiguration.png). Does one of those FBs is the right one for my purpose? Do I possibly make a mistake when assigning the parameter IOLD_ID/IOLM_ID?
Last updated: 2025-03-19

Post by fschuler on No connection to Raspberry at runtime installation ^{CODESYS Forge talk (Post)}
Hi, I try to install the Codesys realtime in a Raspberry PI 3B+. When I click on the installation button I get always the message No connection to device: An established connection was aborted by the server. Raspberry 3B+ with newest raspberry PI OS. Codesys 3.5.15 Patch 1 Codesys Runtime Package 3.5.16.20 SSH is activated. I can login with Putty Ping is possible IP address search is possible Just the installation is not started.
Last updated: 2025-07-23

Post by eschwellinger on Licensing info not available. ^{CODESYS Forge talk (Post)}
yes and no ... if you run the license server on the host (to serve licenses to the docker instances / vplcs then there is no runtime which could check the licenses on the host. Therefore you need the CODESYS WBM to activate or check the licenes or you could use in CODESYS IDE the licensemanager ( not the one for the device licenses) but you have the the IP of the license server that he know where to search for the licenses ..tool options i guess to add it, will add a screenshot later.
Last updated: 2025-10-01

Post by toby on Codesys Control Raspberry PI 4.10.0 - missing 'Update Raspberry PI' option ^{CODESYS Forge talk (Post)}
Hi Edwin, Thanks for the message. My apologies I should have researched this more thoroughly before posting on here. I found a solution to my issue on this post: https://forge.codesys.com/forge/talk/Runtime/thread/6455efaa17/ I needed to run the 'CODESYS Installer' as an Admin, then install the RPi package v4.10.0 in to my package (v3.5 SP19 Patch 5). Thanks, hope you have a good day. Toby
Last updated: 2024-01-09

Sort by relevance or date