Post by eschwellinger on CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Post)}
this is probably: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_linux_dedicated_user.html ..switch back from rootless mode due GPIO will not work.
Last updated: 2026-07-19

Post by charly29160 on CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Post)}
wird nicht mit kopiert - sorry: PermittedPath.0=/dev/i2c PermittedPath.1=/dev/spidev PermittedPath.2=/sys/class/gpio/ PermittedPath.3=/dev/gpiochip
Last updated: 2026-07-20

Post by charly29160 on CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Post)}
Problem gefunden und erledigt => in CODESYSControl_User.cfg ergänzt: [CmpCharDevice] PermittedPath.0=/dev/i2c PermittedPath.1=/dev/spidev PermittedPath.2=/sys/class/gpio/ PermittedPath.3=/dev/gpiochip Dann funktioniert es wieder Gruß Karl Schuler
Last updated: 2026-07-20

Post by charly29160 on CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Post)}
Noch eine Info dazu: als Version der Pi MC SL wird mir 4.21.0.0 angezeigt. In der log steht jedoch für IoDrvGPIO: 4.17.0.0 was ist das Problem?
Last updated: 2026-07-20

Post by nixola on CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Post)}
Hi, I added the following lines to /etc/codesyscontrol/CODESYSControl_User.cfg: [CmpCharDevice] PermittedPath.0=/dev/i2c* PermittedPath.1=/dev/spidev* PermittedPath.2=/sys/class/gpio/* PermittedPath.3=/dev/gpiochip* However, I'm still unable to read or control GPIO pins from any CODESYS application. Specifically, setting the pin direction (and, thus, the IoDrvGpioSysfs driver configuration) fails, with a rather non-descript error in the logs: Description Component Setting direction failed for GPIO pin 586 IEC Update configuration failed from driver IoDrvGPIOSysfs CmpIoMgr I'm running CODESYS Control for Linux ARM64 SL version 4.21.0.0; it's running in rootless mode, as the codesyscontrol user, but said user is in the gpio group and can otherwise normally interact with GPIO, both via gpioset/gpioget and via the sysfs driver in /sys/class/gpio/. The system is a custom 64-bit Raspberry OS based distro, running on a Raspberry Pi CM5 on kernel 6.18.34 with PREEMPT_RT scheduling.
Last updated: 2026-07-21

Post by eschwellinger on CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Post)}
yes, this is a known issue which will be fixed with 3.5.23.0 .. soll will take some time. You need to switch back the runtime running not as dedicated user, like it was before 4.21.0.0 How to switch back you'll find here. ('Change service user' in the deploy tool) https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_linux_dedicated_user.html to sumerize both problems: 1. missing entries in CODESYSControl_Usr.cfg was the problem on Raspberry PI Runtime 2. Arm64 SL is running rootless by default since 4.21.0.0 ( Pi not by default you need to switch manually if needed due this GPIO restriction)
Last updated: 2026-07-22

CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Thread)}
CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21
Last updated: 2026-07-22

KOP & FUP in Sp21P6 nicht vorhanden ^{CODESYS Forge talk (Thread)}
KOP & FUP in Sp21P6 nicht vorhanden
Last updated: 2026-07-24

Fehlermeldung bei Onlinechange ^{CODESYS Forge talk (Thread)}
Fehlermeldung bei Onlinechange
Last updated: 2026-07-27

Post by radar17892 on Fehlermeldung bei Onlinechange ^{CODESYS Forge talk (Post)}
Hallo, kann mir jemand was zu dieser Fehlermeldung sagen: Mitteilung vom Gerät: “Alarm online change executed but license for Online Configuration Change not aviable!” Habe erst letzte Woche noch auf dieser Steuerung (PFC300, FW30) eine Programmänderung gemacht und hat alles funktioniert. Die Meldung kommt am Schluss, wenn ich einen Online change gemacht habe. Dann geht die Steuerung mit Ausnahmefehler auf Stop.
Last updated: 2026-07-27

Post by thomas-k on SysTimeRtcHighResGet --> Millisekunden mit Zeitzone verrechnet ^{CODESYS Forge talk (Post)}
SysTimeRtc.SysTimeRtcHighResGet(pTimestamp := lstActualIPCUnixTime_ms); SysTimeRtc. SysTimeRtcConvertHighResToLocal(lstActualIPCUnixTime_ms,lstActualIPCUnixTimeLocal_ms); SysTimeRtc.SysTimeRtcConvertLocalToHighRes(lstActualIPCUnixTimeLocal_ms,lstActualTime_ms); F30_SysTimeRtcHighResGetLocal:= TO_ULINT(lstActualTime_ms); Dies hat immer die selbe Zeit in UTC. Wie bekomme ich eine HIGHRes Zeit in Millisekunden. Und diese Zeit nicht in UTC sondern mit der Zeitzone verrechnet..... Und reicht es die Zeitzone mit "SysTimeRtcSetTimezone" zu setzen oder muss die Zeitzone im Linux (PC) gesetzt werden ?
Last updated: 2026-07-31

Post by lzml on HTML5 visualization controls disabled on CODESYS Control for Linux SL - overlay not supported? ^{CODESYS Forge talk (Post)}
Hello, I'm developing a custom HTML5 visualization control (via the HTML5 Control Editor / Tools > Visualization Element Repository) and I'm running into what looks like a target-device limitation when trying to deploy it to CODESYS Control for Linux SL. I'd like to understand whether this is a known/expected limitation or something in my setup. Environment - CODESYS Development System: V3.5.22.0 - Target runtime: CODESYS Control for Linux SL, package version 4.15.0.0 (installed together with CODESYS Edge Gateway for Linux 4.15.0.0) - Visu system libraries (VisuElems, VisuElemsAlarm, VisuInputs, VisuNativeControl, etc.): version 4.7.0.0 - Host OS: Debian RT (minimal/base installation) - We only use WebVisu, not TargetVisu. What I did 1. Built a custom HTML5 control following the official HTML5-API-Examples pattern (.html5control.xml manifest + ElementWrapper.js + CSS), installed it successfully via the HTML5 Control Editor ("Save and Install") into the Visualization Element Repository. 2. In the Visualization Manager, enabled "Support client animations and overlay of native elements" (documented as required for HTML5 controls to work at all). 3. With the project's Device set to CODESYS Control for Linux SL, compiling/downloading fails with: "Overlay is not supported for your target visualization device." (Visualization Manager) Build stops with 1 error, download not possible. Isolating the cause - The Visualization Element Repository confirms the control is correctly installed. - With the project Device set to a Windows-based device, the HTML5 control appears and is enabled in the Toolbox as expected. - With the project Device set to CODESYS Control for Linux SL, the HTML5 control is disabled/missing from the Toolbox entirely, even though it's installed in the repository. This points to the Linux SL device description simply not declaring overlay/HTML5 support, rather than a missing package or Debian-side dependency (WebVisu itself already works fine for standard/native visualization elements on this same target). Questions 1. Does CODESYS Control for Linux SL currently support WebVisu overlay (and therefore custom HTML5 controls)? I found documentation stating overlay support for target visualizations (Windows and Linux) was added starting with CODESYS Development System V3.5.17.0, but that seems to refer to TargetVisu, and our case is WebVisu-only on a Linux runtime. 2. If not currently supported, is this on a roadmap, or is there a different Linux runtime package/edition that does support WebVisu overlay for HTML5 controls? 3. Is there any Linux-side configuration or package needed to enable this (given the check appears to happen against a static device capability declaration rather than a live server check), or is this purely a matter of the device description bundled with the current Control for Linux SL package? Thanks in advance for any pointers.
Last updated: 2026-08-05

Post by antony on Assertion Failed ^{CODESYS Forge talk (Post)}
Hi, I am facing the same “Assertion failed” error while downloading the code.
Last updated: 2026-08-07

Assertion Failed ^{CODESYS Forge talk (Thread)}
Assertion Failed
Last updated: 2026-08-07

Post by dhumphries on codesys installer deletes itself instead of updating ^{CODESYS Forge talk (Post)}
I've installed multiple versions of codesys from a download, both the .exe and .zip, the installation goes okay but when I open the codesys installer with admin privelages it immediately starts downloading an update, then starts to install the update, but it doesn't complete the installation, it just deletes the installer files in c:\program files (x86)\codesys\apinstaller and never installs a new version. I've ran a repair from the downloaded installer and I can get it to work as long as I don't give admin permissions. I've done this on my workstation, I've also setup 2 different virtual machines thinking maybe there is some lingering config file, it does it no matter how sanitized the OS is. I've tried running with security software disabled and enabled, it's the same no matter what. It's been probably 4 months since I used the codesys installer, but it didn't do this back then. Is there a way to set the installer to a certain version and disable updates, or something I can do so the update does what it should?
Last updated: 2026-08-10

CODESYS Download Issue ^{CODESYS Forge talk (Thread)}
CODESYS Download Issue
Last updated: 2026-08-10

Post by dhumphries on Deploy Codesys Control SL to a 'secure' device ^{CODESYS Forge talk (Post)}
I have the same problem on a setup where I'm trying to load control SL onto a fresh installation of ubuntu server 22.04 (with sudo privileges,) I've done this in the past several times but only with codesys 3.5.19.x since updating to the new versions I'm having inconsistencies, either I can load the runtime but not login or I can't load the runtime at all. I appreciate there are new releases frequently, but it would be nice if there was a LTS version with some kind of documentation. I'm currently building a VM so I can install version 3.5.19.4 since this was the last version that worked for me. Adding additional versions through codesys installer has been unsuccessful, hopefully a fresh install on a virgin OS will be more successful.
Last updated: 2026-08-10

Post by dhumphries on CODESYS Download Issue ^{CODESYS Forge talk (Post)}
I had an issue when my organization installed some security software that blocked scripts. The installer would silently hang at the same point every time. I had to get a network admin to make some change to security software that wasn't immediately visible to me as a user to allow the installation script to run.
Last updated: 2026-08-10

Post by timvh on codesys installer deletes itself instead of updating ^{CODESYS Forge talk (Post)}
Do you use 32bit versions of CODESYS? Why not 64bit? And just use the installer to manage your various versions and add-ons. Optionally use separate repositories to prevent possible library conflicts.
Last updated: 2026-08-10

Post by timvh on Deploy Codesys Control SL to a 'secure' device ^{CODESYS Forge talk (Post)}
Runtime version SP22 is an LTS version.
Last updated: 2026-08-10

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 lmarmonti on Login problem with FileTransfer on Raspberry Pi 5 ^{CODESYS Forge talk (Post)}
Hello everyone, I have the same problem. I have a Linux-based system with CODESYS 3.6.22.20, and I need to download some files from the external web panel. I have enabled: [CmpWebServerHandlerV3] AllowFileTransferServices=1 In this case, I can see the login page when the web panel connects to the device. I can't disable the device user management access because I need to prevent software modifications. Do you have any ideas? Regards,
Last updated: 2026-08-14

SBOM ^{CODESYS Forge talk (Thread)}
SBOM
Last updated: 2026-08-21

Post by automa on SBOM ^{CODESYS Forge talk (Post)}
Hi, How do you create your SBOM in Codesys. I have been searching for this topic but couldn't find any useful information. I am referring to making an export list or all libraries used in the project. I have developed a python script that exports them, but I am open for ideas of beast practice
Last updated: 2026-08-21

SBOM ^{CODESYS Forge talk (Thread)}
SBOM
Last updated: 2026-08-21

Sort by relevance or date