Post by reinier-geers on Data to server ^{CODESYS Forge talk (Post)}
HI, i want to copy data to a server of a costumor. Whats the easy way ? contoller is V20p5 but also 2 are V9.2
Last updated: 2025-11-11

Post by mariusz997 on Visualisation - internal error ^{CODESYS Forge talk (Post)}
Hi - problem solved. I had 3 version of codesys on system and they didn't like each other. After uninstall all and install again only one version now everything is OK
Last updated: 2025-11-12

Post by grepoo on DataSource CodesysApp V3 ^{CODESYS Forge talk (Post)}
Hi, trying to create a datasource in appV3 but it returns error code 259 (not nearer specified) everytime, no matter the device i am using. Any idea of what it might signify ?
Last updated: 2025-11-19

Post by seler on Custom button with output status ^{CODESYS Forge talk (Post)}
I did some work around by adding IN switch on top of OUT bulb picture(SwitchImage) and setting IN switch button to invisible but this is not quite elegant. How to combine it to one visu element?
Last updated: 2025-11-20

Post by bdschnapp on OPC-UA ApplicationUri / ProductUri ^{CODESYS Forge talk (Post)}
Were you able to figure out if it is possible to change the Application/Product URI of your server? I am having the same problem.
Last updated: 2026-03-16

Post by reinier-geers on Error ambigiusname ^{CODESYS Forge talk (Post)}
In visu i have a Led. I only changed the output. Then i get Ambigius use of name Tpara. But it doesnt show where. See screen shot
Last updated: 2026-01-20

Post by gatto on Two licenses have to be installed forgot to enable one license ^{CODESYS Forge talk (Post)}
Hi. What type of PLC do you have? What activation method do you use? What license ticket did you purchase and want to activate? Can you describe the process you followed step by step?
Last updated: 2026-02-02

Post by risele on AI + Programming ^{CODESYS Forge talk (Post)}
It's already fine to use, with help of exporting/importing as PLC_Open, at least CODEX is good in editing directly at XML and/or providing changes description separately.
Last updated: 2026-02-13

Post by pernockham on Gateway in China - "Gateway not connected" ^{CODESYS Forge talk (Post)}
Finally sorted (unit in China). The problem was related to dns-setting of the gateway/host. Connection (also inside china) tested/works.
Last updated: 2026-03-18

Post by reinier-geers on CODESYS crashes when adding standard OPC UA Information Model to Communication Manager ^{CODESYS Forge talk (Post)}
I only experiance a lot of problems with Version 20 and 21. Version 20 crashes at a online change Version 21 - 5 identical programms in one project. The frist runs. The thirt Crashes. NOt even a screen
Last updated: 2026-03-19

Post by reinier-geers on Resize and position Numpad/Keypad ^{CODESYS Forge talk (Post)}
HI, I download the scale dialog. But cant find were i can Set the size of the dialogs. only the position. I want the diolog bigger
Last updated: 2026-04-15

Post by skiper on Best practice to reduce CPU load ^{CODESYS Forge talk (Post)}
Hi ! I can't say exactly the best practice you can use to reduce your cpu load but you can use the codesys exemple. https://www.codesys.com/products/visualization/#c3876 Go to the midle of the page and you have a link to download an exemple.
Last updated: 2026-04-21

Post by patrik on Wish: CODESYSControl.cfg - again ^{CODESYS Forge talk (Post)}
Really good post. I hope that it gets seen by CoDeSys staff. I often find the documentation lacking when it comes to using CoDeSys in more complex ways. If using standard "basic PLC functionality", then it's fine and functions are documented in a sufficient way. Once you go outside of that bubble then I find the documentation not enough. CODESYSControl.cfg is a good example of this. And why isn't more of this integrated in the IDE. like changing port of the webserver. Why is it hidden in this file and not accessible through the IDE. It feels like a layer of complexity purposely left in so you don't change it if you don't know what you are doing. Like the argument is if you have the know-how to find the file you have the know-how to edit it. I find the documentation lacking when it comes to more complex libraries too. Like the element collections library. there is parameters I still don't quite know what they do. I can't find any documentation about them. There is an example project to download from CoDeSys so you can see how you are supposed to set your factories up. I leave some parameters like it is in the example. Should I? I don't know. Does it work. Yes. But I could perhaps create memory leaks if I get something wrong and I don't see that until way later. In the create method of your element factory you have a function called __vfinit and you just have to accept that it works. Why can't I get insight in what it does through documentation? Don't CoDeSys want us to know how these work so we can't use them to accidentally break something? I find the error logging lacking too. I've had the CoDeSys service crash but it doesn't say why. I've seen windows noticing the crash but no error code was sent or error message. Also in my current issue where the application fails to start after power outage. I can see in the log that it fails to load retain in the application as one log entry and application failing to start as another. But why? Why does loading the retain fail? give me more information! Is it just a skill issue with me? I don't know. If it is then I'd still want CoDeSys to step up their game when it comes to documentation. I'm sorry if a lot of frustration comes though in this post. I really like the product and what I can do with it compared to other PLC brands.
Last updated: 2024-11-21

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 edvard-munch on How I can get "Done flag" for "Modbus Slave Channel"? ^{CODESYS Forge talk (Post)}
This is from 10 years ago, I know. But I have been using (SLAVE_DEVICE.iChannelIndex = CHANNEL_NUMBER) AND (SLAVE_DEVICE.xDone) I suppose that it shows xDone for the channel that shows up in the iChannelIndex at the same cycle? It seems to be working properly for two devices that I have been using it before But now I have another device and using two write channels, for one register each. One channel works properly and returns DONE flag When another channel is triggered, I see that it shows up in iChannelIndex, but flag DONE not received, but no Error for the channel. Also, when i check the register in the device it's evident that data has been transferred. Is this could happen sometimes with CODESYS, so DONE flag not received? Or this is a problem with a given device? With this certain register
Last updated: 2024-12-19

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 jeindhoven on Deploying to raspberry pi 5 hangs ^{CODESYS Forge talk (Post)}
Hi CoDeSys support forum, hope that this is the correct place to ask this. Might be double as i am new to Codesys and dont know all terminology. I am trying to test Codesys with a virtual plc on a raspberry pi 5. Already figured that i need Tools -> Deploy Control SL, enter Communication parameters. Codesys says "Connected". Then tab "Deployment", there i select "CODESYS Control for Raspberri Pi SL" and "4.16.0.0 (all)". Click "Install" and the gui turns grey and unresponsive. The titlebar says "Untitled1.project - CODESYS (Not Responding)" as well. Restarting Codesys and checking shows no package was installed. How to deploy the runtime? Thank you in advance for your time. Edit: After some patience, an error showed up: "Error when sending ssh heartbeat: Session operation has timed out" "Error installing codesyscontrol" Any pointers to what remote command might have failed, or log of some sort, would be welcome. Software versions: Codesys version 3.5.21.10 Raspberry pi 5 (deployment machine): $ uname -a Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye $ apt list --installed | grep openssh-server openssh-server/oldstable,now 1:8.4p1-5+deb11u3 arm64 Development machine: $ uname -a Linux 2B 6.1.0-35-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.137-1 (2025-05-07) x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm VirtualBox Version 7.0.26 r168464 (Qt5.15.8) Virtual OS: Windows 10 Pro 64-bit (10.0, Build 19045) .NET version 4.0.30319.42000
Last updated: 2025-06-22

Post by otbeka on CAA File Handling: "Read only" error ^{CODESYS Forge talk (Post)}
Hi, On CODESYS V3.5.19.50 I am using the latest 3S File Access library (CAA File & CAA Types) to save and retrieve configuration data from the User Data section of an SD card, via file called config.txt. The application reads the file to memory once upon initialisation, and then the only other operation is overwriting the file with the updated configuration whenever the user changes the settings. An issue is ocurring, seemingly randomly, where the config.txt file, and all surrounding directories, cannot be written to by the unit, returning a READ_ONLY_CAA error upon file open. This sometimes does not clear even after power-cycling the PLC several times, yet checking the file permissions with ls -l shows normal read, write, and execute access. I am wondering if this is caused by the PLC itself or by an issue in my application. I have included my CAA File handler function block (SD_Card_Bin(FB).txt) and any associated types/calls below: TYPE ConfigData : STRUCT Config : ARRAY[0..256] OF STRING(64); NumberOfStrings : UDINT; END_STRUCT END_TYPE TYPE Buffer : STRUCT Data : ARRAY[0..SIZEOF(ConfigData)] OF BYTE; DataLength : UDINT; END_STRUCT END_TYPE A case within my MAIN PRG: mode.WriteConfigDataToFile: VisuElems.CURRENTVISU := 'Screen_Write'; IF xModeHasChanged THEN iErrorCount := 0; iRoute := 0; END_IF CASE iRoute OF 0: inBuffer := ConfigData_To_Buffer(GVL.UnitData); xConfigError := FALSE; xDataConfigured := FALSE; iRoute := 1; 1 : //Read Data from Card SD_Card_Bin.strFileName :=FileName; SD_Card_Bin.iFileOperation := 2; SD_Card_Bin(xExecute :=TRUE, WriteBuffer := inBuffer, xDone =>xDataConfigured, xError=>xConfigError, strErrorCodes=>strError); IF xDataConfigured THEN SD_Card_Bin(xExecute :=FALSE); IF xConfigError THEN iRoute := 32767; ELSE iRoute :=100; END_IF END_IF 100: // The end bCurMode := mode.DisplayProcessVariables; 32767: // Config error iErrorCount := iErrorCount + 1; IF iErrorCount > 2 THEN // Repeats 3 times, if no progress abandons and returns error bCurMode := mode.WriteError; ELSE iRoute := 0; // Try again END_IF END_CASE I'd like to rule out my application as the cause of this bug - help via comments or criticism would be greatly appreciated.
Last updated: 2025-03-19

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 vamsi on How to configure gateway for programming RPi 2B using Codesys ^{CODESYS Forge talk (Post)}
I am using a Raspberry Pi 2B. Installed Codesys V3.5.20.1 64-bit and installed 'CODESYS Control for Raspberry PI 4.12.0.0' I am able to install the packages using the 'Update Raspberry Pi' option, but when I try to log into the RPi, in the Device tab it says 'Sacn fail. Please checl that the gateway is running and that its settings are correct'. My setup looks like this. I connected my RPi to my company LAN and also my laptop to company LAN (using HP Docking station). This setup worked when I installed 'CODESYS Control for Raspberry PI', but now I donot know how to configure the gateway. Could anyone please help me in finding what I have to enter in the gateway configuration? Thanks, Vamsi.
Last updated: 2024-07-10

Post by rmaas on TargetVisu for Linux SL not starting ^{CODESYS Forge talk (Post)}
Hello, I am trying to get TargetVisu for Linux working but i am having some troubles. The problem is that after installation it is not starting automatically on boot and i cannot start it from the update Targetvisu tool. When i try i get the following error (see attached screenshot) The file /opt/codesysvisualization/scripts/codesysvisualization_start.sh is missing... Steps performed: - installed fresh Debian 12.7 on virtual machine - installed all required libraries as described here: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_target_visu_for_linux.html - then installed the TargetVisu for Linux SL 4.13.0.0 using the Codesys IDE Does someone know how i can fix this? Best Regards, Rinie
Last updated: 2024-10-02

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 gatto on CAA File open Problems ^{CODESYS Forge talk (Post)}
Ciao, here same question https://forge.codesys.com/forge/talk/Engineering/thread/2538729618/ in this post https://forge.codesys.com/forge/talk/Engineering/thread/4586a90290/?limit=25#d531 i find : keep in mind that all files which are generated / or read should be exist in the iecfilepath this means: for Windows (Control Win as example) c:\ProgramData\CODESYS\CODESYSControlWinV3x64\268E8ADF\PlcLogic for Linux /var/opt/codesys/PlcLogic I never use codesys on windows but im sure on linux we can manipulate file only inside /var/opt/codesys/Plc Logic. Or you need to modify the file codesyscontrol.cfg for change path permission, but this is another history Buone feste !
Last updated: 2024-12-21

Post by jeroenaero on Targetvisualisation full screen with CmpTargetVisu settings ^{CODESYS Forge talk (Post)}
Hi, How can i display targetvisualization in full screen on the target device? I installed Targetvisu For Linux SL 4.16.0.0 on target device which contains Raspberry PI 64bit PIXEL desktop. When i connect my PLC program to the remote targetvisu, the targetvisu displays for 60% horizontally. We contacted CODESYS and they said it is a bug. they had a workaround, and with the settings below added to the file /etc/codesysvisualization/CODESYSVisualizationTV.cfg, the targetvisualization display for 100%, but with the taskbar at the top. VisuClient.BestFit=1 ;VisuClient.ScaleTypeIsotropic=0 VisuClient.FillWholeBackground=1 [CmpTargetVisu] WindowPositionX=0 WindowPositionY=0 WindowSizeWidth=1280 WindowSizeHeight=800 WindowType=2 How can we let it display fullscreen without taskbar?
Last updated: 2025-07-24

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

Sort by relevance or date