Post by mariussandu on OPC-UA ^{CODESYS Forge talk (Post)}
I updated the runtime to CODESYS Control for Raspberry Pi SL 4.22.0.0, SDK 3.5.22.30. Same outcome as before. Now I study if migrating to PFC100 is ok or to change to Siemens PLC because of this issue.
Last updated: 2026-09-07

Post by mariussandu on OPC-UA ^{CODESYS Forge talk (Post)}
I updated the runtime to CODESYS Control for Raspberry Pi SL 4.22.0.0, SDK 3.5.22.30. Same outcome as before. Now I study if migrating to PFC100 is ok or to change to Siemens PLC because of this issue.
Last updated: 2026-09-07

Post by caualima on AI + Programming ^{CODESYS Forge talk (Post)}
What do you think about having an AI Agent specialized in ST programming in Codesys? I see this saving hours and hours of work for those who program on a daily basis.
Last updated: 2026-01-24

Post by arpat on Error, visualisation property handling, VISU_USEPROPERTYINFO ^{CODESYS Forge talk (Post)}
For me going to Project -> Project Settings -> Visualisation -> check "Visible" and then check both "Activate property handling ..." and "Activate implicit checks ..." solved the problem.
Last updated: 2026-02-03

Post by altin on No source code available for this object ^{CODESYS Forge talk (Post)}
Hello, I get same error message but pointing at different library. The error appears when im trying to scroll an AlarmTable on a thouch screen (ifm CR1204). Anyone knows what causing this and how to procceed? Many thanks in advance,
Last updated: 2026-02-16

Post by eschwellinger on Unable to deploy "Control for Linux SL 4.18.0.0" ^{CODESYS Forge talk (Post)}
Hi could you check if this really exists in 4.19.0.0 deploy tool? In your case architecture is missing- see my configuration
Last updated: 2026-02-17

Post by eschwellinger on Unable to deploy "Control for Linux SL 4.18.0.0" ^{CODESYS Forge talk (Post)}
can you please check this: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_toubleshooting_deploytool2.html#UUID-b83dc01e-8cff-c574-7efe-8615b95a51ed_section-idm234790234401598
Last updated: 2026-02-19

Post by timvh on Unit testing support / libraries for EcoStruxure Machine Expert (CODESYS) ^{CODESYS Forge talk (Post)}
If the Professsional Developer Edition (which includes the Test Manager) is not supported by Schneider, then an option is to use the Open Source Unit test framework. See: https://forge.codesys.com/lib/counit/home/Home/
Last updated: 2026-02-20

Post by alexgooi on Codesys KNX implementation ^{CODESYS Forge talk (Post)}
Dear Forum, For anyone interested we have solved this problem. Before we were using a KNX TP/IP interface, now we are using a KNX TP/IP router, and it works like a charm now.
Last updated: 2026-03-04

Post by fpawlak on How to register own component - CMAddComponent() or CMAddComponent2() ^{CODESYS Forge talk (Post)}
Hi, so really oneone has no idea which way is correct one? Or maybe both are okey if they work for me?
Last updated: 2026-03-13

Post by nulltrace on How change Unity-ID in TCP Modbus Slave ^{CODESYS Forge talk (Post)}
Hey Husarz, thanks for your Message, now i understand your Problem, also able to reproduce that. Pls. give me a Short Time to Check some stuff on this, i'll come back to this Topic with news ASAP. Greetings
Last updated: 2026-04-03

Post by nulltrace on How change Unity-ID in TCP Modbus Slave ^{CODESYS Forge talk (Post)}
Hey, I also waiting for feedback from Mr. Schwellinger @eschwellinger, please send me an answer, i would appreciate it. The clue is, i know the solution, but have to check if it's allowed to share.
Last updated: 2026-04-14

Post by tvm on Generic Variables and FDB ^{CODESYS Forge talk (Post)}
I also ran into this, try using Coil<1> as the type in the FBD box. From what I understand, with VAR_GENERIC CONSTANT, the compiler creates separate data types for each different function block declaration.
Last updated: 2026-07-22

Post by somlioy on Beckhoff ESI import german text ^{CODESYS Forge talk (Post)}
Solved. Had to explicitly select English inside CODESYS as language instead of system default, which for my case is norwegian... Open Tools → Options → International Settings Set the development-system language to English Restart codesys
Last updated: 2026-07-28

Post by axberry on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
when is the releaseof the 4.2.0.0
Last updated: 2026-08-10

Post by eschwellinger on CAN TX regression in Control for Raspberry Pi 4.21.0.0 with CAN API library (RX works, TX silently fails) ^{CODESYS Forge talk (Post)}
seems to be an accident but there is a workaround in the Configfile: [CmpSocketCanDrv] AsyncSend=1 and will be solved with 4.22.0.0 Release
Last updated: 2026-08-17

Post by reinier-geers on Read own network device name ^{CODESYS Forge talk (Post)}
Hi. When i scan for devices on the network i get names of the devices. Is there a command to get device name in my programm ? i found : DED.GetDeviceNameString( DED.GetRoot() ); but then i get his name in the programm. not his name in the network.
Last updated: 2026-09-17

Post by wollvieh on Raspberry Pi Runtime 4.22.0.0 vs. 4.20.0.0 I2C Bus not running... ^{CODESYS Forge talk (Post)}
... the stars needed? --> yes! [CmpCharDevice] PermittedPath.0=/dev/i2c* PermittedPath.1=/dev/spidev0.0 PermittedPath.2=/sys/class/gpio/* PermittedPath.3=/dev/gpiochip* For me it worked with this additional settings in the file /etc/codesyscontrol/CODESYSControl_User.cfg.
Last updated: 2026-10-16

Post by danp1406 on Question about Demo License limitations for Modbus TCP communication and Fieldbus Instances ^{CODESYS Forge talk (Post)}
Hello everyone, I am currently working with CODESYS Virtual Control for Linux running in Docker on a Debian virtual machine. I am deploying my application using Deploy Control SL, and in my project I am using the ModbusFB library to implement Modbus TCP communication. My setup is the following: I am trying to establish a Modbus TCP connection between a virtual PLC (CODESYS acting as Modbus TCP Client/Master) and a Siemens S7-1200 PLC acting as a Modbus TCP Server. From the Debian VM, I can successfully ping the S7-1200 and verify that port 502 is open using tools like nc. Network-wise, everything appears to be correct. However, when running the application in CODESYS, I receive messages such as “Demo mode for Modbus/TCP Master started. Will expire and stop!” and socket errors like “ClientSocket.UpdateStatus socket error 111 disconnecting.” The ClientTCP block from the ModbusFB library attempts to connect, but the connection does not remain stable. My main question is whether the CODESYS demo license explicitly limits or interrupts Modbus TCP Master communication. Is it expected that in demo mode the runtime will automatically close sockets after some time or prevent stable Modbus TCP connections? I would like to confirm whether this behavior is normal when using ModbusFB in demo mode, or if I should continue troubleshooting the configuration. Additionally, I would like clarification regarding the “fieldbus instances” mentioned in CODESYS licensing options (for example, 2, 4, or 16 instances). What exactly is considered one fieldbus instance? Does one Modbus TCP Client block count as one instance? Does each active connection to a different device count separately? Do Modbus TCP Master and Server count independently toward the total number of instances? Finally, I would appreciate clarification on any other practical limitations of demo mode when using industrial communication libraries such as ModbusFB. Are there limits on the number of connections, number of requests, or communication duration? I am trying to determine whether demo mode is sufficient for testing a virtual PLC communicating with a Siemens S7-1200 over Modbus TCP, or whether a full license is required even for this kind of validation scenario. Thank you in advance for any guidance.
Last updated: 2026-02-25

Post by mubeta on Some 'pathetic' errors in SoftMotion program ^{CODESYS Forge talk (Post)}
Thank you for your interest. Your answers are in line with what I knew, so at least it comforts me that I did not misinterpret the situation. However, I don't have an exact match as, for this project over the past few days I have: 1) I have gone back to leaving the various FBs of the motion always called, all of them, and in the state machine I use a boolean to activate the various useful Execute. (But in the future I want to go back and try the programming technique with which I wanted to develop this project); 2) For the occasional error: SMC_FB_WASNT_CALLED_DURING_MOTION perhaps it was due to the fact that I had set the Ethercat bus synchronism only at the CAN master level, but not at the level of individual drives. I have now also activated it for the individual drives and it does indeed seem to have been resolved, but having also adopted the programming technique mentioned in point 1), I cannot say whether this was the solution to the problem, or instead the previous point. Is there an error ‘regulator or start not set’ in the device log before the error ‘motion generating FB wasn't called for at least one cycle’? I can't answer that right now. By now the machine is running and I am no longer there, at this one. Also, I seem to remember that the 'fbeFBerror' drive structure (5-element array), does not cycle, BUT ONCE THE 5 EVENTS AFTER SWITCHING ON, IT DOES NOT UPDATE ANYMORE (but that's another issue), so diagnostics were not easy.
Last updated: 2024-07-24

Post by gunstr on CODESYS control on RPi starts, shortly runs, then exits ^{CODESYS Forge talk (Post)}
Thank you very much for the quick answer! The RPi hw were delivered last week so it's probably a resent version. I found an old scrapped board (2 years or so) with a broken GPIO that I tested with the same SD card image and with that board Codeys can run for the full 2h demo period without issues. Then I went back the the new board to test the 4.17.0.0 release but the installation fails... [INFORMATION] Standard output: create and install daemon [INFORMATION] Standard output: codesyscontrol started [WARNING] Unable to detect Raspberry Pi Architecture. Setting armv6l as default, you can change this through the settings panel. [INFORMATION] Standard output: codesyscontrol stopped [ERROR] Expected exit value of command failed: expected 0, received 1 [WARNING] Error setting the Raspberry Pi Architecture [ERROR] Error installing codesyscontrol Do you have any idea what could be the reason? I'm using an OS image including Python drivers for LCD and some I/O:s from last year to keep things stable, but also after upgrading with sudo apt update && sudo apt upgrade I still get the same error Reverting back to 4.15.00 works fine: [INFORMATION] Standard output: create and install daemon [INFORMATION] Standard output: codesysedge started [INFORMATION] Successfully installed codesyscontrol [INFORMATION] Successfully started CODESYS Edge Gateway for Linux [INFORMATION] Successfully started CODESYS Control for Raspberry Pi SL but as before the Codesys services stops after 30 seconds. And I noticed that the Codesys control stops and is not reachable also if I have no application loaded.
Last updated: 2025-09-02

Post by tk096 on High Cycle Times for SoftMotion_PlanningTask when using AxisGroup ^{CODESYS Forge talk (Post)}
Hi, under this circumstances the performance of a Raspberry Pi 4 should be sufficient to run a Softmotion robotics application. A closer look at the project would be required. Maybe you could contact the codesys support? Usually it is recommended to run the planning task cyclically every 2ms with task priority of 0 on a dedicated core. In the task configuration you can have a look at the average and maximum execution time of the planning task. You could use the function block SMC_TuneCPKernel (https://content.helpme-codesys.com/en/libs/SM3_Robotics/Current/SM3_Robotics/POUs/AdministrativeConfiguration/Computation/SMC_TuneCPKernel.html) to define suitable values for the parameters 'fSyncBufferDuration' and 'fPlanningInterval'. However, as previously mentioned, the performance of a Raspberry Pi 4 with realtime patch should be sufficient. The 'fPlanningInterval' parameter specifies the maximum planning step width in seconds. The cycle time of the planning task should not permanently exceed this value. A higher value reduces the computational effort, but can lead to a violation or no full utilization of the set limit values for velocity, acceleration and jerk. From a starting value of 0.016 seconds, the value should be increased gradually until the performance is acceptable. The parameter 'fSyncBufferDuration' specifies the size (in seconds) of the buffer between the planning and fieldbus task. The cycle time of the planning task must not exceed this value at peak times (this will lead to the error SMC_CP_QUEUE_UNDERRUN). A higher value can compensate for peaks in the cycle time of the planning task. At the same time, however, this also increases the latency for executing interrupts and aborting movements.
Last updated: 2024-03-22

Post by mondinmr on Patched Wine packages for Ubuntu and CODESYS 3.5 ^{CODESYS Forge talk (Post)}
I have now published Ubuntu amd64 packages of my patched Wine build for CODESYS, targeting Ubuntu 22.04, 24.04, 26.04 and 26.10. The packages are based on Wine 11.20 and include all five compatibility patches covering NCrypt, thread suspension, security tokens, service tokens and local WMI marshalling. Both 32-bit and 64-bit Windows applications are supported through WoW64. In my working environment, CODESYS 3.5 SP21 successfully compiled and went online with a very complex project containing hundreds of thousands of lines of code and extensive use of polymorphism. PPA and installation All four binary builds have completed successfully and are now published and available through APT. Wine ADV for CODESYS PPA sudo add-apt-repository ppa:mondinmr/wine-adv sudo apt update sudo apt install wine-adv The runtime installs under /opt/wine-adv and provides dedicated commands, allowing it to coexist with your existing Wine installation. For example, to launch CODESYS from an existing dedicated prefix: WINEPREFIX="$HOME/.wine.codesys" wine-adv \ 'C:\Program Files\CODESYS 3.5.21.30\CODESYS\Common\CODESYS.exe' Adjust the executable path to match your installed version. Use the same WINEPREFIX when running the CODESYS installer or installing its prerequisites. The package contains the patched Wine runtime. CODESYS and its required Microsoft .NET components must be installed separately inside the prefix. Source code, patches and packaging are available on the project page. This is an experimental community build. Feedback and test results from other users are welcome! CODESYS Installer and CodeMeter licensing are also working in my setup. For CodeMeter, I use the native Linux CodeMeter runtime, while the Windows applications run under the patched Wine build.
Last updated: 2026-10-31

Post by dclements on Feature Request: Read-Only References / Pointer-to-Const Support ^{CODESYS Forge talk (Post)}
I would like to suggest adding support for persistent read-only references or pointers in CODESYS, similar to a C++ pointer-to-const (const T*). For example, something conceptually similar to: POINTER TO CONSTANT ST_MyData or REFERENCE TO CONSTANT ST_MyData The important distinction is that the reference itself may still be passed around or reassigned, but the referenced object cannot be modified through that reference. CODESYS currently supports VAR_IN_OUT CONSTANT, which provides read-only reference semantics for parameters, but there does not appear to be an equivalent type that can be stored in a variable or returned from a method. A practical use case is a registry that owns long-lived definitions. The registry needs to retain ownership of the data while downstream systems maintain persistent references to it. Currently, the main options are: Return the struct by value, which loses reference semantics and requires a copy. Return POINTER TO ST_Definition, which allows consumers to modify registry-owned data. Convert the structure into a Function Block and expose a getter-only interface, which provides the desired encapsulation but introduces more complexity and memory overhead. A read-only reference/pointer type would allow libraries to expose persistent, zero-copy access to internally owned data while preserving encapsulation. This would be particularly useful for library APIs and object-oriented CODESYS architectures where ownership of data should remain with one component while other components are allowed to observe it. Similar requests for constant references/pointers have been discussed on CODESYS Forge previously, so this appears to be a recurring use case rather than something specific to one application.
Last updated: 2026-09-01

Sort by relevance or date