Post by sachem on Problem retain values Weidmuller UC20-WL2000 ^{CODESYS Forge talk (Post)}
Good afternoon. I am working with a weidmuller uc20-wl2000 controller, using a codesys license. We made a ladder code to control a process, and it works well, but we want some variables to remain stored even when the controller is turned off. We tried to use retain variables, but at the time of loading the program, when we went offline from the controller, the program was deleted, it did not remain in the controller, and in the same way if we turned off the controller. In addition to this, when we tried to program it again, the program would not stay loaded and began to present errors with the opc-ua communication. What could be causing this problem? How can we maintain the values of the variables without damaging the program or affecting the controller? thank you
Last updated: 2024-04-10

Post by r-niedermayer on Issue with WebVisu on Raspberry PI ^{CODESYS Forge talk (Post)}
Regarding to your application: When clicking in the web visualization, the boolean variable will be tapped for both buttons. The LED in the web visualization lights up as long as the variable is true The used variables should come from the GVL, ad/or thePLC_Prg. We see no difference or problem in both projects: You have created a visuelement Push button a a tapper, that is supposed to control the variable in this way as expected. This is also reflected (switching Bool from false to true) in the program code, as well as in the (GVL declared) variables. Wherever the misunderstanding comes from: no, this is not memory or license related. Our best guess: it is probably more of an applicative/conceptual implementation.
Last updated: 2024-04-11

Post by rossanoparis on After un upgrade of "CODESYS Control for Raspberry Pi MC SL" from v4.7 to v4.9 SysFileOpen function stopped working ^{CODESYS Forge talk (Post)}
For those who will step on this thread. Everything is fine, I had only to increase by 1 my place holders number. For sure the system is occupying the number 1 without being declared ... Below the modification I made to get my code working. [SysFile] PlaceholderFilePath.2=/home/pi/hpca/bin, $hpcabin$ PlaceholderFilePath.3=/home/pi/hpca/cfg, $hpcacfg$ PlaceholderFilePath.4=/home/pi/hpca/logs, $hpcalogs$ PlaceholderFilePath.5=/home/pi/hpca/resources, $hpcares$
Last updated: 2023-08-22

Post by rcaponi on Codesys 3.5 SP19 Patch 4. Trace context menu does not work ^{CODESYS Forge talk (Post)}
Hello, I'm using the new Codesys 3.5 SP19 Patch 4 version with CODESYS Control for Raspberry Pi MC SL v4.8. Compared to the Codesys 3.5 SP19 Patch 1 version, the context menu on a Trace object no longer works. So I can no longer run the Downloader Trace command. Do any options need to be enabled with the new version? Best regards Roberto Caponi
Last updated: 2023-10-24

Post by timvh on Management of a PLC network from a remote station ^{CODESYS Forge talk (Post)}
Maybe the CODESYS HMI is a good solution. https://store.codesys.com/en/codesys-hmi-sl-bundle.html Run this on the remote main control station. In the HMI application you can add the data source manager and to this manager you can add Data sources. A data source has a reference to the PLC you want to connect to and can get access to the variables of the PLC application. You can then use these variables in the visualization of the HMI application.
Last updated: 2023-12-04

Post by trusty-squire on How to adapt Codesys Control SL to custom board ^{CODESYS Forge talk (Post)}
For general usage, these links might help you out. If you are looking at using I2C interfaces, examples from the Raspberry Pi will probably be useful, even if your board isn't a Raspberry Pi. https://content.helpme-codesys.com/en/CODESYS%20Examples/_ex_rts_serial_com.html https://content.helpme-codesys.com/en/CODESYS%20Examples/_ex_raspberry.html If you're developing your own drivers, I can't help you there, although the link you provided will help. If you drill in deeper, the I2C page for example shows function block and method usage, etc. Good luck!
Last updated: 2024-08-09

Post by davidbo on RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Post)}
CODESYS Control for Raspberry Pi MC SL v4.4.0.0 CANopen_Manager 4.2.0.0 I did not call rm directly from my TASK-i2c, it was trough the attached python script. It is not always a problem happens, but sometimes a rm takes a long time. I reduced the amount of calls to logi2c.py but I don't understand why TASK-i2c sometimes can cause problems for TASK-CAN
Last updated: 2024-09-27

Post by davidbo on RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Post)}
CODESYS Control for Raspberry Pi MC SL v4.4.0.0 CANopen_Manager 4.2.0.0 I did not call rm directly from my TASK-i2c, it was trough the attached python script. It is not always a problem happens, but sometimes a rm takes a long time. I reduced the amount of calls to logi2c.py but I don't understand why TASK-i2c sometimes can cause problems for TASK-CAN
Last updated: 2024-09-27

Post by winki on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
Hello, Today I am able to test ma industrial computer in my test bench. I am able to do all the configuration throught my VPN, 100% remote. I can see the gateway & the Virtual PLC. Now I would like to do some Modbus TCP Client & Modbus RS485. But I am lost due to docker ! When I go to modbus TCP it only gave me the docker network, but not my eth0 & eth01 When I go to modbus rtu, how can I create the link between Com number & my /dev/ttyRS485 Loic,
Last updated: 2024-10-23

Post by mascara on TouchScreen does not work in Webvisualization. ^{CODESYS Forge talk (Post)}
I am configuring a Lenovo M900 computer with CODESYS Control RTE SL 3.5.20.30. I use an Aoc E2272pwut LED 21.5 monitor. The touchscreen works perfectly in the Windows 10 PRO environment but does not work in the WebVisualization environment (Window opened at PLC startup). Does anyone know if it is necessary to configure any drivers in Win RTE? I am at your disposal for any questions. Thank you.
Last updated: 2024-11-11

Post by jeroenaero on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
Finnaly i get it working. There was a line in the file that set the ADS1015 chip in /boot/firmware/config.txt which i removed and after that the ADS1115 has a green turning circle and i got values. i created a new component so it fits our ADS1015. see screenshot. It works also with Codesys Control for Raspberry Pi 64 SL after adding the ULINT_TO_UDINT conversion in the library. i think the chip was all the time in use by the Raspberry pi itself. Thanks for your help!
Last updated: 2024-11-12

Post by eschwellinger on CODESYS Control for Linux ARM SL (32 bit) on Moxa UC-3100 IPC ^{CODESYS Forge talk (Post)}
I would recommend to ask Moxa for a newer version of Debian. Debian 9 ("Stretch") has reached its end of life and is no longer receiving security updates from the official Debian Security Team as of June 30, 2022. This means any systems still running Debian 9 are vulnerable to security risks and should be upgraded to a newer, supported version of Debian like Debian 10 ("Buster") or Debian 11 ("Bullseye").
Last updated: 2025-07-14

Post by dhumphries on Control for Linux SL on Ubuntu Core ^{CODESYS Forge talk (Post)}
Try using a password instead of a public key to log into the controller. I have a video showing how to do this on a default installation of Ubuntu server, it should work the same for Ubuntu Core. https://youtu.be/rj0dOhgnGjs?si=352PmveEP7JXZnO- I sign in to the controller at about 6:40 in the video. I have never tried to remove the public key and revert to signing in using a password, but it looks pretty straightforward https://askubuntu.com/questions/745423/how-to-turn-off-password-less-login-for-ssh
Last updated: 2024-02-28

Post by schnepper on Error building Extension SDK Linux code ^{CODESYS Forge talk (Post)}
I'm installed the CODESYS Control for Linux SL package and am trying to use the Extension API to call a simple C function. When I get to the step to run "make all" on the Linux machine, I get the error: build interface header: out/CmpFirstTestItf.h from CmpFirstTestItf.m4 ERROR: This functionname does not contain _cext (this is mandatory, see help for details): DEF_API(void',CDECL',external_struct__fb_init',(external_struct_fb_init_struct *p)',1,0x1F77E075,0x00000001) Why does "Generate Runtime System Files" create a function that does not have cext in the name? What am I missing?
Last updated: 2024-04-01

Post by rabaggett on CODESYS control for Raspberry Pi 64 SL errors ^{CODESYS Forge talk (Post)}
Update: I started over. I saved progress at each step. all compiled zero errors, zero warnings. Pre-processor messages remain, but I can make progress. Until I try to re- load the project file in Codesys. Re-loaded files error as above when compiled, even though they compiled error-free immediately before saving. Is my installation borked? (Not easy to re-install due to IT madness...)
Last updated: 2024-05-03

Post by timvh on OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext ^{CODESYS Forge talk (Post)}
I never tried this, but maybe you need to create a certificate on the controller for this? See the menu View - Security Screen. Select the device and see if you need to create a certificate. And maybe you also need to accept the certificate of the other device. This can also be done in the security screen. PS, the CODESYS Runtime Control version must be greater than 3.5.21.0.
Last updated: 2026-06-26

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)}
Hi, I'm trying to run CODESYS Control for Raspberry Pi SL on a Raspberry Pi 5, and the runtime consistently fails to start with the following error when launched manually: ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-18, 0x00000BB8, 0xFFFFFFFB) Hardware: Raspberry Pi 5 Model B Rev 1.1 Revision code: d04171 CPU: aarch64, BCM2712 Serial number is correctly exposed via /proc/cpuinfo and /proc/device-tree/serial-number /proc/device-tree/model correctly reports "Raspberry Pi 5 Model B" What I've tried (all resulting in the same error): CODESYS Control for Raspberry Pi SL 4.11.0.0 (SDK 3.5.19.61) — the version that introduced Pi 5 support CODESYS Control for Raspberry Pi SL 4.21.0.0 (SDK 3.5.22.20) — latest available Raspberry Pi OS Bookworm (64-bit) with kernel 6.12.93+rpt-rpi-2712 (June 2026 build) Fresh install on Raspberry Pi OS Bookworm (64-bit) with an older image from November 24, 2025 — same error, ruling out a kernel-version regression Bootloader/EEPROM confirmed up to date (rpi-eeprom-update reports "up to date") Clean purge and reinstall of the codesyscontrol package each time (verified via dpkg -l, no leftover files) Verified /etc/codesyscontrol/3S.dat correctly symlinks to /etc/codesyscontrol/3S_aarch64.dat The service starts (systemctl status briefly shows active (running) with a real PID under /opt/codesys/bin/codesyscontrol.bin), but crashes shortly after and the process disappears — port 11740 never opens. Since this happens identically across two different runtime versions and two different OS images (5+ months apart), it doesn't seem to be a kernel/firmware timing issue. Could this be specific to the Rev 1.1 board revision, or is there a known issue with the hardware detection logic in the SL runtime that I should be aware of? Happy to provide full debug logs (-d flag output) or journalctl output if useful. Thanks in advance!
Last updated: 2026-08-10

Post by charly29160 on WebVisu scaling regression in V3.5.22 P2: frame size jumps when switching visualizations ^{CODESYS Forge talk (Post)}
Environment: - CODESYS V3.5.22 Patch 2 - CODESYS Control for Raspberry Pi MC SL - WebVisu in browser Problem: When switching between visualizations using a Register element (Registerkarten), the displayed frame size jumps incorrectly after returning to a previously viewed visualization. This behavior was introduced in V3.5.22 Patch 2. The same project worked correctly in V3.5.21 Patch 4. WebVisu settings in V3.5.21 (working): - Scaling: Isotropisch - Automatisch ermittelte Clientgröße verwenden: active - All visualizations: Automatisch erkannte Visualisierungsgröße Workaround?
Last updated: 2026-06-15

Post by alexgooi on No Bootproject possible ^{CODESYS Forge talk (Post)}
Dear Forum, When using a online-change I often get the following message: No Bootproject possible in this state: application out of memory. Perform full download first. I'm using Codesys virtual control for linux SL running on a docker server with plenty of memory available, therefore I’m not expecting a hardware limitation. Is there a setting available to for example reserve more memory, so the controller is not that quick out of memory? thank you in advance. Alex
Last updated: 2026-03-27

Post by timvh on HTML5 visualization controls disabled on CODESYS Control for Linux SL - overlay not supported? ^{CODESYS Forge talk (Post)}
I would suggest to install the latest visualization and visualization add-ons. Go to Tools - CODESYS installer to updates these add-ons (or just start the CODESYS installer through the Windows start menu). After installation, restart CODESYS SP22 and update the project to use this new visualization profile (you can update this through the menu Project - Project Environment - Visualization Profile).
Last updated: 2026-08-05

Post by dvmaris on Control for Linux ARM64-User Management issue ^{CODESYS Forge talk (Post)}
I'm trying to work with Codesys Control for Linux ARM64 SL 4.18.0.0 on a Toradex Verdin NXP iMX8MP. I have the runtime installed and operational as well as Codemeter lite 8.40.7141.503 (arm64). I'm running 3.5.20.60 and when "Scan Network" I see the Verdin popup. When I try to connect to it, the "mandatory use of the user management" popup shows...which makes sense. I click YES and enter user information and click OK. It immediately displays a "No device is responding to the scan request" popup. The IDE can see the Verdin in the scan...so this popup does not make sense to me. I thought maybe it was a read only issue but I've made all partitions and paths RW. Has anyone experienced this? Can anyone tell me where it is trying to write user data?
Last updated: 2026-02-11

Post by jvfred on CodesysHMI.exe: Start Error ^{CODESYS Forge talk (Post)}
I have used Codesys HMI SL on several projects. Today I turned my PC on to start building another project and received the following error message when I tried to start my device: "CodesysHMI.exe: Start Error One of the following licenses is required: CodeMeter 101597:13 Failure reason: CmContainer Entry not found, Error 200 CodeMeterAct 5000304:13 Failure reasons: CmContainer Entry not found, Error 200" I have tried reloading HMI SL and even updated to the current version with no success. I am using HMI SL version V3.5.20.10. Any help would be greatly appreciated.
Last updated: 2024-11-01

Post by jvfred on CodesysHMI.exe: Start Error ^{CODESYS Forge talk (Post)}
I have used Codesys HMI SL on several projects. Today I turned my PC on to start building another project and received the following error message when I tried to start my device: "CodesysHMI.exe: Start Error One of the following licenses is required: CodeMeter 101597:13 Failure reason: CmContainer Entry not found, Error 200 CodeMeterAct 5000304:13 Failure reasons: CmContainer Entry not found, Error 200" I have tried reloading HMI SL and even updated to the current version with no success. I am using HMI SL version V3.5.20.10. Any help would be greatly appreciated.
Last updated: 2024-11-01

Post by ranadheer on Request to share documents about SoftPLC Extension SL ^{CODESYS Forge talk (Post)}
Hello Everyone Our team is planning to begin an industrial automation project and we are currently evaluating the use of SoftPLC Extension SL as a potential solution. As we are in the early stages and have yet to start the implementation, we kindly request access to official reference documents, technical manuals, and datasheets relating to SoftPLC Extension SL. Thank you very much for your assistance. We look forward to your response.
Last updated: 2025-10-18

Post by rossanoparis on After un upgrade of "CODESYS Control for Raspberry Pi MC SL" from v4.7 to v4.9 SysFileOpen function stopped working ^{CODESYS Forge talk (Post)}
Hello at all. After un upgrade of "CODESYS Control for Raspberry Pi MC SL" from v4.7 to v4.9 SysFileOpen function stopped working. I'm not able to read or write files from the PLC application. Before this upgrade all worked fine. I've read this thread [ https://forge.codesys.com/forge/talk/Engineering/thread/3da9ded84e/ ] Despite I followed that indications I couldn't get my code working again. Perhaps I'm missing something or I didn't understand how to use placeholders at all. Is there a different syntax to use for "SysFileOpen" in order to use placeholders? Thanks in advance for your help. Information Compiler: CODESYS V3.5 SP19 Patch 2 Runtime: codesyscontrol 4.9.0 HW: KUNBUS RevPi Connect S Below the paths I want to access (The entire CODESYSControl_User.cfg file is attached) [SysFile] PlaceholderFilePath.1=/home/pi/hpca/bin, $hpcabin$ PlaceholderFilePath.2=/home/pi/hpca/cfg, $hpcacfg$ PlaceholderFilePath.3=/home/pi/hpca/logs, $hpcalogs$ PlaceholderFilePath.4=/home/pi/hpca/resources, $hpcares$
Last updated: 2023-08-22

Sort by relevance or date