Post by hezhikui on Codesys 3.5.21 fails to copy file to USB ^{CODESYS Forge talk (Post)}
Hi,Canplum,did you solved this problem?
Last updated: 2026-06-16

Post by blisk2000 on Scheduler ^{CODESYS Forge talk (Post)}
Hi, I am looking for a scheduler like attached picture. Is a scheduler like this already available in Codesys? Thank you! Best regards! Zdenko
Last updated: 2026-01-16

Post by wollvieh on Sysfile Konfiguration ^{CODESYS Forge talk (Post)}
Hier noch ein schönes Beispiel für $$PLCLogic$$. https://support.enovationcontrols.com/hc/en-us/articles/29453251586451-Codesys-Example-File-Storage
Last updated: 2026-01-20

Post by antonio011 on Request a dark mode for CODESYS ^{CODESYS Forge talk (Post)}
Any updates on this? A dark mode is in most IDE state of the art already.
Last updated: 2026-01-21

Post by eschwellinger on cm4 runtime problem ^{CODESYS Forge talk (Post)}
no - you need to update, smallest impakt is just to install the debiab package on target side. Nothing else ( no updates in CODESYS)
Last updated: 2026-02-02

Post by winki on Error in licence activation ^{CODESYS Forge talk (Post)}
I am using Codesys Control for linux ARM64 SL. Installed with the SL deployment tool
Last updated: 2026-02-03

Post by eschwellinger on Codesys ControlWinV3x64 with EtherCat Slave ^{CODESYS Forge talk (Post)}
please check the plclog for more information. sounds like NPCap does not work.
Last updated: 2026-02-04

Post by russells on Codesys ControlWinV3x64 with EtherCat Slave ^{CODESYS Forge talk (Post)}
Much thanks. I reinstalled NPCap and it is now working. Much thanks.
Last updated: 2026-02-05

Post by dosnova on *exception* [processorloadwatchdog] occurred in: app=[all], task=[all] ^{CODESYS Forge talk (Post)}
Weintek Codesys firmware update does not solve this problem..
Last updated: 2026-02-10

Post by nano on CODESYS and Github Copilot ^{CODESYS Forge talk (Post)}
your Project is allways written in st? then have a look at the FBS from PDE. schould solve parts of the job
Last updated: 2026-02-11

Post by eschwellinger on Control for Linux ARM64-User Management issue ^{CODESYS Forge talk (Post)}
guess you'll need to use latest CODESYS version to fix this.
Last updated: 2026-02-14

Post by heman on AI + Programming ^{CODESYS Forge talk (Post)}
have a look at www.plc-assist.com ...think it does what you are looking for
Last updated: 2026-04-27

Post by eschwellinger on Ladder editor bug with 3.5.21.20 ^{CODESYS Forge talk (Post)}
Hi, could you please update to Ladder 1.2.0.0 via CODESYS Installer and check if this is still in?
Last updated: 2026-06-01

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 struccc on Application failing to boot after system reboot ^{CODESYS Forge talk (Post)}
I started to experience the same issue, after upgrading to 3.5.19 , and still persists with 3.5.20.3 , using CodesysControlWinV3 x64 on Windows. Unfortunately, this is a live application, normally it is running for months without interruption - so it was a surprise at the last cold start... It was not possible to go online with the original version, so I couldn't see the application, or system status, just the log message. First time I manually clean the Application from the PlcLogic directory (there was no coredump file in there), then I could start the runtime service, and do a fresh download, and set the bootproject. I could not try a cold system reboot - it's in a 24/7 production environment, and I was under heavy pressure to start... What I did, I have created a backup from the * complete * runtime directory, from the failed, and fixed version - before and after download. This directory in my case C:\ProgramData\CODESYS\CODESYSControlWinV3x64\55096128 - At the next shutdown, it was sufficient to copy back this backup completely, and could start the runtime service afterwards. Ugly, but local staff with some skills can do it without programming tool... I don't store any live data, configuration, log files, persistent data in this directory - the only reason I need this is to edit the CodesysControl... .cfg file.... And to see the logfiles in emergencies like this. The application concerned doesn't use any retain area. - exactly for these reasons - Maybe that is causing the problem with the newer runtime versions As far as I see, this problem occurs only if the power of the Windows PLC is interrupted without a proper shutdown. Unfortunately, this can happen sometimes. The newer versions, seems tp modify CodesysControl.cfg on the fly, and register the applications, and bootproject information after download. (I don't really see CodesysControl.cfg a proper location for this... but that's just my feeling) So now I had a look at CodesysCotrol.cfg on my laptop and I found: [CmpRetain] ;Retain.SRAM.Size=0x200200 ;Retain.SRAM.Address=0xFA3C5776 ;SimulateSRAM=1 [CmpApp] ;Bootproject.CreateOnDownload=0 ;Bootproject.StoreOnlyOnDownload=0 ;Bootproject.InvalidateByRename=1 ;Bootproject.InvalidateBySetting=1 ;Bootproject.InvalidateNever=0 ;PersistentForce=0 ;RetainType.Applications=InSRAM ;RetainType.Applications=OnPowerfail ;RetainType.Applications=None ;Exception.Hardware.GlobalStop=1 Application.1=MyTestAppNoRetain The last line appeared after download and boot project creation. Maybe... Should set RetainType.Applications=None? I wonder about all these settings, but... Will write separately about it. I hope this helps a little...
Last updated: 2024-11-21

Post by clarenced on ERROR: Calling the program "AlarmStorage_Prg" is not allowed from multiple tasks ^{CODESYS Forge talk (Post)}
Using codesys v3.5 SP21 Patch 1. We are using Visualization to display alarms. Other then the automatically created AlarmManagerTask, there is no code written to call AlarmStorage_Prg. Any ideas why we would be seeing this error in the log? The runtime actually shutdown. Not sure if that was caused by this error or not. 2025-08-03T02:45:35.444Z, 0x00001012, 4, 0, 0, * ERROR: Calling the program "AlarmStorage_Prg" is not allowed from multiple tasks. 2025-08-03T03:48:15.294Z, 0x00001012, 4, 0, 0, * ERROR: Calling the program "AlarmStorage_Prg" is not allowed from multiple tasks. 2025-08-03T04:38:11.557Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state * We recommend a reboot of the controller now! * 2025-08-03T04:38:11.576Z, 0x0000010f, 8, 1, 0, #### Exception: SysSemEnter - Semaphore deadlock detected - owner thread died [tid:726740] - system may be in an inconsistent state. 2025-08-03T04:38:11.576Z, 0x00000103, 65544, 1, 0, runtime received SIGABRT - system may be in an inconsistent state * We recommend a reboot of the controller now! 2025-08-03T04:38:11.576Z, 0x00000001, 8, 260, 3, #### Exception: HANDLED EXCPT* <excpt>NonContinuable</excpt> in CH_COMM_CYCLE 2025-08-03T04:40:12.308Z, 0x00000001, 1, 0, 35, CODESYS Control shutdown... 2025-08-03T04:40:13.436Z, 0x00000071, 1, 0, 13, Webserver stopped 2025-08-03T04:40:13.437Z, 0x00000114, 2, 1, 0, !!!! Warning: task_signalhandler_exit [MainTask] lost cycles: 14809 2025-08-03T04:40:13.497Z, 0x00000001, 1, 0, 10, [UNLOADED] IEC|Dynamic: <cmp>IecVarAccess</cmp>, <id>0x00001007</id> <ver>3.5.3.64</ver> 2025-08-03T04:40:13.506Z, 0x00000001, 1, 0, 10, [UNLOADED] IEC|Dynamic: <cmp>AlarmMgr</cmp>, <id>0x00001012</id> <ver>4.7.0.0</ver> 2025-08-03T04:40:13.513Z, 0x00000071, 2, 0, 14, !!!! Warning: Unbalanced calls to WebServerRequestRunning/WebServerReleaseRunning 2025-08-03T04:40:13.513Z, 0x00000001, 1, 0, 10, [UNLOADED] IEC|Dynamic: <cmp>IECVisualization</cmp>, <id>0x0000100c</id> <ver>4.7.0.0</ver> 2025-08-03T04:40:13.611Z, 0x00000124, 1, 0, 0, Provider 'AddressSpaceFragment Provider' (version 0x3051500) unregisterd at the OPC UA server. 2025-08-03T04:40:13.611Z, 0x00000124, 1, 0, 0, Provider 'OPC UA for IEC-61131-3' (version 0x3051500) unregisterd at the OPC UA server. 2025-08-03T04:50:17.708Z, 0x00000001, 1, 0, 36, CODESYS Control shutdown done
Last updated: 2025-08-04

Post by alexgooi on Modbus TCP interface get stuck ^{CODESYS Forge talk (Post)}
Dear Forum, I'm currently experimenting with Modbus interfaces in combination with a virtual controller. I have the following setup (Modbus_Setup.png): I have an IPC with Debian installed on it (Debian 13). On this Debian machine I have installed a docker server and on this docker server a Codesys runtime container is deployed (Codesys_image.png). The Modbus scanner makes connection with and IO coupler and this works well. But when I physically disconnect the ethernet connection between the IPC and the IO coupler the Modbus interface gets stuck in a state where it gets stuck in the busy state (Modbus_Stuck.png). When I plug the cable back in, the IO coupler isn't communicating until the xBusy variable is manually set to False, after this action is performed the communication goes back to normal. I have tried to set the container network to host and bridge (Network.png), but both version gives the same result (stuck scanner). I would expect that the Modbus interface is generating a timeout after 1 sec, because this is how it is setup (Modbus_settings.png), but this is not what happens. I have thought to write a piece of code that writes xBusy to false when it is stuck but because it is an output I'm not able to write to it. I have tried this with another PC (different CPU/motherboard) but this gives the same outcome. I tried updating to the latest version of Virtual control (4.20) but this gives the same result. I also tried to do the same thing with an ethernet IP scanner, and this gives an error after the timeout is expired (so this works well). I have tried to connect to the IO coupler using the Modbus_FB lib (Modbus_FB.png) the FB's are giving the correct errors and behaving as expected. At last I have tried to use a Scanner on a Codesys controller (no IPC) and here the scanner behaves as expected (an alarm is triggered after the timeout has been expired). The version of the Codesys components are listed in the picture Versions.png Is there anyone that can give me a push in the right direction? Kind regards Alex
Last updated: 2026-04-14

Problems working with IScriptModuleRepository.add_reference_instance Method ^{CODESYS Forge talk (Thread)}
Problems working with IScriptModuleRepository.add_reference_instance Method
Last updated: 2023-08-17

wed visu im IFM display CR1077 ^{CODESYS Forge talk (Thread)}
wed visu im IFM display CR1077
Last updated: 2023-08-18

Sorting array of any-sized structure ^{CODESYS Forge talk (Thread)}
Sorting array of any-sized structure
Last updated: 2023-08-18

Find index based on values ^{CODESYS Forge talk (Thread)}
Find index based on values
Last updated: 2023-08-20

Find index based on values ^{CODESYS Forge talk (Thread)}
Find index based on values
Last updated: 2023-08-20

Post by hugob on Start Control Win Softmotion Runtime ^{CODESYS Forge talk (Post)}
Last updated: 2023-08-23

Start Control Win Softmotion Runtime ^{CODESYS Forge talk (Thread)}
Start Control Win Softmotion Runtime
Last updated: 2023-08-23

Warnung C0373 / Dialog nicht instanziert ^{CODESYS Forge talk (Thread)}
Warnung C0373 / Dialog nicht instanziert
Last updated: 2023-08-29

Sort by relevance or date