Post by mos89p on CodeSysControlWinV3x64 ^{CODESYS Forge talk (Post)}
Hello Check: on the latest version the location change: If the PLC is started with the "CODESYS Control Win SysTray PLC Control", it runs in the Windows user account "LocalSystem" and therefore the effective working directory is "C:\Windows\system32\config\systemprofile\AppData\Roaming\CODESYS\" or "C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\CODESYS\". An administrator account is required to access these folders
Last updated: 2024-07-11

Post by nilanjan on I want to show the current recipe name in the visualization screen ^{CODESYS Forge talk (Post)}
I am having some trouble showing the current recipe name in visualization i am not using the RecipeManCommands i am using the inbuild visualization feature of Saving and Loading recipes. I need it so the user would have a track on which recipe is being used currently.
Last updated: 2025-08-24

Post by beavel on Opening and saving files with fileOpenSave dialog ^{CODESYS Forge talk (Post)}
1 + Replying in hopes of getting an answer here. I would also like to modify the look of the FileOpenSave Dialog. I have successfully adjusted the looks of the User management Dialogs but can not find a library file to adjust this particular one. Any help would be helpful. @thk @eschwellinger @sheberle .
Last updated: 2025-09-08

Post by alexgooi on How to protect library project? ^{CODESYS Forge talk (Post)}
Hi aniket-b, If you save the library as a compiled library you are not able to see the source code. When the end user tries to view inside the object, CODESYS will give a notification that the source code is missing, see attachment. In short if you don't send the source code, it will not show.
Last updated: 2024-01-25

Post by thomas-moba on "sudo"-Befehle über die Funktion "SysProcessExecuteCommand2" ^{CODESYS Forge talk (Post)}
Wir haben jetzt so ziemlich alles probiert. Ohne sudo mit sudo, den Aufruf in ein Script gepackt (.sh und .py) und sogar ein eigenes kleines Linux-Programm geschrieben, weil wir vermuteten das der sudo-Befehl nicht im Klartext ausgeführt werden darf. Es funktioniert einfach nicht. Daher dir Frage: muss die codesyscontrol als root ausgeführt werden? Momentan wird sie als user ausgeführt.
Last updated: 2024-02-02

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 antonz on Could not write options file at... ^{CODESYS Forge talk (Post)}
I ran into a similar issue, albeit not the exact same conditions nor the same file if I recall correctly. As a workaround I have used an elevated account to give my regular user account write access to the specific directory where the failure occurred. It is not pretty and I am not happy with it. It does work.
Last updated: 2026-09-07

Post by timvh on From target start Win OnScreenKeyboard ^{CODESYS Forge talk (Post)}
Check the CODESYS log. Do you see something like this?: 2026-10-28T14:27:50.602Z: Cmp=SysFile, Class=2, Error=39, Info=4, pszInfo=!!!! Access denied to 'C:/Windows/System32/osk.exe' due to ForceIecFilePath 2026-10-28T14:27:50.602Z: Cmp=SysFile, Class=1, Error=0, Info=0, pszInfo= To grant access, this path may be configured as a PlaceholderFilePath PS, if you give an irritating, or annoying or blaming answer, I will never try to help you again. Some additional info... do you run the Control Win as user, or as service. Test it first by running it as a user, else check the info that Claude gave me as suggestion (not tested): Watch out: the keyboard may not appear CODESYS Control Win normally runs as a Windows service. Windows keeps services in a separate, invisible session (session 0). The command then succeeds, but nobody sees the keyboard. You can check this in Task Manager: if osk.exe runs under the user SYSTEM, this is the cause. A reliable workaround uses the Windows Task Scheduler: Create a task named ShowOSK that starts C:\Windows\System32\osk.exe with “Run only when user is logged on” checked. That option makes it open on the user’s desktop. Have the PLC start that task instead of osk.exe: iecst sApp := 'C:\Windows\System32\schtasks.exe'; sArgs := 'schtasks /run /tn "ShowOSK"'; The command line usually repeats the program name as the first argument. 3. Whitelist it in the config: Command.1=C:\Windows\System32\schtasks.exe
Last updated: 2026-10-28

Post by elektron785 on GPIO mit Codesys Virtual Control for Linux ARM64 SL ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich möchte an einem Entwicklungsboard auf dem der i.MX 8M Plus von NXP aufgesteckt ist die vier zur Verfügung gestellten GPIOs als Ausgänge verwenden. Ich habe mir dazu die Readme-Datei des GPIO-Beispiels von "C:\Program Files\CODESYS 3.5.20.40\CODESYS\CODESYS Control SL Extension Package\4.14.0.0\Examples\GPIO" angeschaut Die Übersicht der verfügbaren GPIOs sieht folgendermaßen aus - wobei ich das auf die reduziert habe, die für mich von Interesse sind: gpiochip0: GPIOs 0-31, parent: platform/30200000.gpio, 30200000.gpio: gpio-0 (SODIMM206 ) gpio-1 (SODIMM208 ) gpio-2 ( ) gpio-3 ( ) gpio-4 ( |sd-vsel ) out hi gpio-5 (SODIMM210 ) gpio-6 (SODIMM212 ) gpio-7 (SODIMM216 ) gpio-8 (SODIMM218 ) gpio-9 ( ) gpio-10 ( ) gpio-11 (SODIMM16 ) gpio-12 (SODIMM155 |regulator-usb1-vbus ) out lo gpio-13 (SODIMM157 ) gpio-14 (SODIMM185 |regulator-usb2-vbus ) out hi gpio-15 (SODIMM91 )** Füge ich nun das GPIO (1 Bit)-Gerät in meinem Codesys-Programm hinzu funktioniert der Bus solange bis ich die Richtung in den GPIO-Parametern von "not used" auf "Output" stelle (siehe Bild gpio_parameter). Dann funktioniert nach Download der Bus nicht mehr. Gibt es noch eine andere Möglichkeit das zu steuern oder muss ich noch Einstellungen tätigen? Für die Zeile mit dem echo (export/unexport) aus dem Beispiel fehlen mir trotz sudo die Zugriffsrechte. "The Kernel Linux has deprecated GPIO user space SysFS. However, the kernel config CONFIGGPIOSYSFS is still enabled on Toradex's BSP to support customers using it in their legacy applications. You can check the configuration by running zcat /proc/config.gz | grep CONFIGGPIOSYSFS. For GPIO access from userspace, the new char device API, also known as libgpiod, must be used." Dies steht in der Verwendung der GPIOs - eine Ausführung des zcat-Kommandos liefert ein =y zurück.
Last updated: 2025-03-17

Post by snhatton on Alarm Management - latched variable represented as Text list ^{CODESYS Forge talk (Post)}
Hi There, For my understanding: are you trying to display the contents of a text list in an alarm message based on the id? For example, you could maintain a text list of common alarm messages, and then display based on which message is true?
Last updated: 2023-09-18

Post by manuknecht on Detect "Cancel" Press in FileOpenSave Dialog ^{CODESYS Forge talk (Post)}
Thanks for your response! It seems like the VisuElems library has updated functions to the ones you used but apparently these older ones still work, even if I couldn't find them in the library documentation and they are also not suggested automatically by Codesys (when using Ctrl + Space). However, its precisely what I was looking for and it works. Thanks!
Last updated: 2023-09-20

Sort by relevance or date