Post by charly29160 on CmpCharDevice blocks gpiochip access on Raspberry Pi 5 since update from SP18 to SP21 ^{CODESYS Forge talk (Post)}
Hi, after updating CODESYS Control for Raspberry Pi SL from patch level 18 to 21 (currently 4.21.0.0), the IoDrvGPIO driver ("GPIOs B+/Pi2") can no longer open any GPIO chip on a Raspberry Pi 5. Log output on login: Could not open GPIOChip0. Access to path /dev/gpiochip0 not allowed. Add /dev/gpiochip0 to permitted paths in configuration file if required Could not open GPIOChip4. Trying to open GPIOChip0 Access to path /dev/gpiochip4 not allowed. Add /dev/gpiochip4 to permitted paths in configuration file if required Could not open any GPIOChip. System details: Raspberry Pi 5, 32-bit Raspberry Pi OS (armv7l), kernel 6.12.47+rpt-rpi gpiodetect correctly shows gpiochip0 [pinctrl-rp1] (54 lines) as the RP1 GPIO controller Runtime: CODESYS Control for Raspberry Pi SL 4.21.0.0, Runtime Toolkit SP21+ This worked without issues before the update to SP21. I've tried adding the following to CODESYSControl_User.cfg without success: ini[CmpCharDevice] Linux.DevicePath.1=/dev/gpiochip0 Linux.DevicePath.2=/dev/gpiochip4 Could you tell me the correct section/key to whitelist /dev/gpiochip0 (and /dev/gpiochip4) for CmpCharDevice? I suspect this is part of the general security hardening introduced around SP21 (similar to ForceIecFilePath for SysFile, or the new Gateway "accept local clients only" default), but I couldn't find it documented anywhere. Thanks in advance!
Last updated: 2026-07-19

Post by dekelec on Codesys 2.3 & Peak PCAN ^{CODESYS Forge talk (Post)}
I use Peak USB adapter daily to download from CoDeSys 2.3 and 3.5 to IFM, EPEC and other controllers. The process: - First you need to install the appropriate driver. Link: https://www.peak-system.com/Drivers.523.0.html?&L=1 - Restart the computer - Start the CoDeSys application - Change the name of the adapter in Communication parameters, as mentioned in previous comment. Write the name exactly as written "Peak_USB", as it could also be case sensitive (defines which .dll file to use). If this doesn't work I would contact the vendor of the controller to find out the procedure. In the attachment I've added a FAQ document from IFM regarding using PCAN USB. P.S. I've noticed in your picture of communication parameters a channel via TCP/IP is mentioned. In this case a USB to CAN connection is not being used. First you should change the channel/gateway to connect via CANbus or connect using an Ethernet cable.
Last updated: 2024-07-09

Post by karel-bas on Loosing connection to emulation running on Linux ^{CODESYS Forge talk (Post)}
Hello, I am trying to emulate my code but for some reason my Codesys IDE keeps loosing connection to the emulator. I am constantly pinging virtual machine on which its running and its running fine, but codesys refuses to reconect to it, and is not able to rediscover it. Codesys 3.5 SP20 Patch 1 I have linux installed like image in attachment.(using version 4.12) Linux VM is set up to use up to 4 cores and 8gb of ram, with nothing else runing on it. I dont have a license so I am aware that the emulation shouldnt run for more then 120 minutes I am able to, login, get sysinfo, reboot etc from codesys IDE for certain period of time (5minutes) then my connection gets lost, sometimes I can login again, but sometimes i have to reboot the VM. Any suggestions what might be the issue ?
Last updated: 2024-09-19

Post by macman on Codesys 3.5 OPC UA Client to Kepware OPC UA Server ^{CODESYS Forge talk (Post)}
Hi, I have problem with connecting Wago PLC WAGO 750-8212/0025-0002 configured as OPC UA client to Kepware OPC UA Server. I am using Codesys 3.5.19.70. What I did so far. To the Codesys project I added object Data Source Manager and configured connection OPC UA like below: pic 1 Then I can browse the OPC server tags in “Variables” tab after prior trust on the server side of the client certificate created in the “Communication” tab: pic 2 Additionally second certificate has been created in Codesys for runtime process in “Security screen” as well as the server certificate was approved here: pic 3 But when I compiled project, downloaded it to PLC and go to RUN I can’t read selected in “Variables” tab, OPC Server tags. I am getting such error (ID: 7001): pic 4 All two PLC certificates has been trusted in OPC server (Kepware) side: pic 5 and Kepware server configuration look like this: pic 6 I can easily connect using third party OPC UA client UaExpert to Kepware server without problem. In attachment I added also log from Kepware OPC UA server. pic # - this specifies the number of a concrete graphic from one of the collective in attachment
Last updated: 2025-04-02

Post by bschraud on Code erzeugen mit kryptischer Fehlermeldung mit GVL_Io_dd05d808 ^{CODESYS Forge talk (Post)}
Hallo, beim Codeerzeugen bekomme ich wiederholt Fehlermeldungen, bei denen nicht mit einem Klick in das betroffene Modul gewechselt werden kann. Die Fehlermeldung tritt allerdings nach "Gerät aktualisieren" nicht mehr auf. Wenn ich das Projekt speichere, Codesys schließe, anschließend Codesys wieder starte und Code erzeugen will, tritt der Fehler wieder auf: ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... [FEHLER] PAC: C0032: Typ 'Unbekannter Typ: 'ADR(GVL_Io_dd05d808_33e6_4f6b_ba3a_6ba1d0dcc882_HPS_7.Io_dd05d808_33e6_4f6b_ba3a_6ba1d0dcc882_HPS_7)'' kann nicht in Typ 'POINTER TO IoConfigParameter' konvertiert werden [FEHLER] PAC: C0077: Unbekannter Typ: 'GVL_Io_dd05d808_33e6_4f6b_ba3a_6ba1d0dcc882_HPS_7.Io_dd05d808_33e6_4f6b_ba3a_6ba1d0dcc882_HPS_7' [FEHLER] PAC: C0046: Bezeichner 'GVL_Io_dd05d808_33e6_4f6b_ba3a_6ba1d0dcc882_HPS_7' nicht definiert Kompilierung abgeschlossen -- 3 Fehler, 1 Warnungen Übersetzung abgeschlossen -- 3 Fehler, 1 Warnungen : Kein Download möglich Die Recherche nach der Bedeutung von "HPS_7" oder "GVL_Io_dd05d808" verlief leider ergebnislos. Ich habe nur einen ähnlich erscheinenden Thread gefunden, der aber nicht gelöst wurde: https://forge.codesys.com/forge/talk/Engineering/thread/0666dce94f/ Ich verwende Codesys 3.5 SP20 (64bit) mit CODESYS Control for Raspberry Pi MC SL 4.11.0.0. Alle anderen Geräte sowie die Projektumgebung sind frisch aktualisiert. Kennt jemand die Bedeutung dieser Fehler bzw. wie man sie beheben kann? Vielen Dank für die Hilfe
Last updated: 2024-05-16

CoDeSys libraries for BECKHOFF EL7332/EL7342 ^{CODESYS Forge talk (Thread)}
CoDeSys libraries for BECKHOFF EL7332/EL7342
Last updated: 2023-08-25

Import RsLogix 5000 project to Codesys ^{CODESYS Forge talk (Thread)}
Import RsLogix 5000 project to Codesys
Last updated: 2023-09-07

Codesys Control RTE V3. Remote Control ^{CODESYS Forge talk (Thread)}
Codesys Control RTE V3. Remote Control
Last updated: 2023-09-22

Recommended Specification for running CodeSys ^{CODESYS Forge talk (Thread)}
Recommended Specification for running CodeSys
Last updated: 2013-11-14

Kommunikationsunterbrechung zwischen CODESYS und RPi 3 ^{CODESYS Forge talk (Thread)}
Kommunikationsunterbrechung zwischen CODESYS und RPi 3
Last updated: 2017-02-20

CODESYS Development System V3.5.18.30 Installation Error ^{CODESYS Forge talk (Thread)}
CODESYS Development System V3.5.18.30 Installation Error
Last updated: 2022-12-07

CoDeSys OPC server with SIMULATION3 interface ^{CODESYS Forge talk (Thread)}
CoDeSys OPC server with SIMULATION3 interface
Last updated: 2016-02-24

Neues Forum zur CoDeSys OPC Anbindung ^{CODESYS Forge talk (Thread)}
Neues Forum zur CoDeSys OPC Anbindung
Last updated: 2011-04-14

Modbus übertragung von CodeSys nach Excel ^{CODESYS Forge talk (Thread)}
Modbus übertragung von CodeSys nach Excel
Last updated: 2010-08-01

CoDeSys V3 mit Raspberry Pi Kamera ^{CODESYS Forge talk (Thread)}
CoDeSys V3 mit Raspberry Pi Kamera
Last updated: 2016-05-05

Codesys Projekt läst sich nicht öffnen ^{CODESYS Forge talk (Thread)}
Codesys Projekt läst sich nicht öffnen
Last updated: 2017-12-10

CODESYS on RPI - tcpip socket ^{CODESYS Forge talk (Thread)}
CODESYS on RPI - tcpip socket
Last updated: 2022-07-14

Codesys V3 and Enron Modbus ^{CODESYS Forge talk (Thread)}
Codesys V3 and Enron Modbus
Last updated: 2022-11-09

PY Script aus CoDeSys Programm ausführen ^{CODESYS Forge talk (Thread)}
PY Script aus CoDeSys Programm ausführen
Last updated: 2017-01-25

CoDeSys 3 auf dem STM32 ^{CODESYS Forge talk (Thread)}
CoDeSys 3 auf dem STM32
Last updated: 2009-03-03

CODESYS + Funktionale Sicherheit SIL3/PLe ^{CODESYS Forge talk (Thread)}
CODESYS + Funktionale Sicherheit SIL3/PLe
Last updated: 2020-05-28

Codesys on Beaglebone Green Wireless? ^{CODESYS Forge talk (Thread)}
Codesys on Beaglebone Green Wireless?
Last updated: 2019-07-04

Codesys V3.5 SP17 P3 Statusanzeige ^{CODESYS Forge talk (Thread)}
Codesys V3.5 SP17 P3 Statusanzeige
Last updated: 2022-04-14

CoDeSys Testmanager commenting out Test Cases ^{CODESYS Forge talk (Thread)}
CoDeSys Testmanager commenting out Test Cases
Last updated: 2022-04-05

More COM port in Linux Codesys ^{CODESYS Forge talk (Thread)}
More COM port in Linux Codesys
Last updated: 2022-03-28

Sort by relevance or date