Post by alexgooi on Codesys KNX implementation
CODESYS Forge
talk
(Post)
Dear forum, We are currently doing some research on the Codesys KNX implementation (https://store.codesys.com/en/codesys-knx-sl.html). We almost have it working but we are missing the last part. The setup: We have a Codesys virtual control container running on docker (4.17.0.0), the I/O is running over an Ethernet IP coupler (Weidmüller), and this is running fine. As far as I’m concerned this tells me that the ethernet device is working properly (the container has access to the outside world, including multicast). Underneath this ethernet adapter the KNX module is added (see picture). In the KNX device (Codesys) 2 input variables are added (see picture), and these are exported to ETS (ETS 5). In ETS A Codesys KNX device has been imported and the Codesys export was imported, afterwards the group addresses are attached to the variables (see picture). Afterwards this configuration is downloaded to the Codesys controller (Container) via ETS. ETS asks for the pressing of the programming button, when the virtual programming button is pressed the download starts and finishes without any errors. This tells me that ETS is communicating with the Codesys controller, and that the download process is ok (so far so good). Now the part where we are struggling with, somehow we need to convert the KNX TP to KNX IP. For this we have the following interface: Zenio KIPI SC (https://www.zennio.com/product/kipi-sc/) this is a KNX TP to IP interface. We have the following setup for this device (see picture) (an IP in the same subnet is used). We tried multiple combinations of IP addresses but the TP devices are simply not communicating to the Codesys container. Does anyone has any advice on what to try next. To make the question more explicit how can we link the TP bus to the Codesys device? Kind Regards Alex
Last updated: 2026-01-05
Post by shabroz-gill on Unable to load boot application on ARMv7 device restart
CODESYS Forge
talk
(Post)
I download an application to an ARMv7 32 bit device. I start the applicatin and it all works fine. But when i restart the device the boot app is not able to start. I have to redownload the application from the development environment to get to run again. I get the following error messages in the log on the restart
Last updated: 2023-11-30
Post by cakar16 on Looking for BL20-PG-EN-V3, V3.5.11.20 Device Driver
CODESYS Forge
talk
(Post)
Hi Everyone, I am Karnadi I am looking for device driver for the following Turk devices and version: - BL20-PG-EN-V3, V3.5.11.20 (Turk) - BL20-2RFID-S, V1.1.3.0 (Turk) - BL20-1RS485/422, V1.1.3.0 (Turk) - BL20-4DO-24VDC-0.5A-P, V1.1.3.0 (Turk) - Ethernet, 3.5.11.20 (Turk) Appreciate if anyone of you can share the device driver (config package) above Thanks and Regards Karnadi
Last updated: 2024-10-04
Post by eschwellinger on Scan Network on gateway created with Control Sl
CODESYS Forge
talk
(Post)
it seems that the device you scan, is not the same type which you have added to the project in CODESYS. Virtual Control is Arm 64 SL so please select this type in CODESYS when you generate a new Application..or right click to the device- update device - virtual Control Arm 64 SL
Last updated: 2024-10-16
Post by arjunk on How to correctly create a device descriptor (.devdesc.xml) for a custom Linux ARM64 PLC in CODESYS 3.5.21.20?
CODESYS Forge
talk
(Post)
Hi, I’m evaluating CODESYS for our devices. If I buy a standard runtime and the Toolkit, can I create a custom device descriptor so users can select my device (instead of just “CODESYS Control for Linux ARM64 SL”) when starting a new project? Has anyone done this or know if it’s possible? Thanks!
Last updated: 2025-10-07
Post by idir93dz on Identifier 'IoDrvGPIO' not defined
CODESYS Forge
talk
(Post)
Hello, After installing the pi runtime and creating a pi project, I get these errors: [ERROR] Untitled3: Application [Device: PLC Logic]: C0046: Identifier 'IoDrvGPIO' not defined [ERROR] Untitled3: Application [Device: PLC Logic]: C0080: Function block 'IoDrvGPIO' must be instantiated to be accessed [ERROR] Untitled3: Application [Device: PLC Logic]: C0004: 'IoDrvGPIO' is no component of 'IoDrvGPIO'
Last updated: 2024-04-10
Post by ph0010421 on Deploy Codesys Control SL to a 'secure' device
CODESYS Forge
talk
(Post)
Hello I'm trying to get Codesys onto a 'Secure' edge device (Linux) The device doesn't support 'sudo' so the connection doesn't complete properly. Is this the same as not allowing root access? Anyway, the screen shot shows where I am. What options do I have?
Last updated: 2026-05-01
Post by mozed on Connection to device closed
CODESYS Forge
talk
(Post)
i found this error in /opt/CoDeSysControl/Files
Last updated: 2023-08-25
Post by timvh on gateway problem
CODESYS Forge
talk
(Post)
Maybe select the local gateway instead of the gateway on the remote device?
Last updated: 2023-08-31
Post by davidbo on RPI How to login for a copy of the SD image
CODESYS Forge
talk
(Post)
I had one RPI device where I could login. I copied the SD-flash over to another SC-flash. This new SD-flash was inserted in the new device. I can boot the new device but I cannot login why? How can I install an application on this new device? Control 4.4.0.0 cat os-release PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Last updated: 2023-10-18
Post by kimcuong on Profinet Deivce SL
CODESYS Forge
talk
(Post)
How to get license trial Profinet Device SL in Codesys for beckhoff
Last updated: 2024-07-05
Post by egau on Hard shutdown: no code on device after power on
CODESYS Forge
talk
(Post)
Excellent merci pour ton aide!
Last updated: 2024-10-03
Post by eschwellinger on Ethercat Slave - Load PDO From Device
CODESYS Forge
talk
(Post)
Which CODESYS Version and which EtherCAT Master version?
Last updated: 2024-10-23
Post by jeroenaero on CodeSys Raspberry pi I2C driver not found
CODESYS Forge
talk
(Post)
I succeed to change the device to PI_SL but still the same problem of the I2C device switching between running and not running. the only difference with your project is that yo use I2C_master device version 4.7.0 and i 4.7.13, for GPIO i also use the 4.7.13 version and you the 4.7.0. Can you send me the older version of the Raspberry PI pheripals library, because i cannot choose lower version then 4.7.10 for the GPIO and I2C_master device
Last updated: 2024-11-11
Post by eschwellinger on The application does not exist on "device"
CODESYS Forge
talk
(Post)
please check the plc logger for more details
Last updated: 2024-12-17
Post by eschwellinger on Ethernet/IP Scanner Exception
CODESYS Forge
talk
(Post)
which runtime version and dies this device has an realtime kernel?
Last updated: 2024-12-28
Post by timvh on password policy
CODESYS Forge
talk
(Post)
On your device, change the setting in CODESYSControl_User.cfg: [CmpUserMgr] SECURITY.UserMgmt.PasswordPolicy=DISABLED
Last updated: 2025-09-10
Post by snhatton on Add device greyed out
CODESYS Forge
talk
(Post)
What type of PLC are you using?
Last updated: 2023-12-19
Post by ph0010421 on Add device greyed out
CODESYS Forge
talk
(Post)
Click on NET in the project tree and add it there.
Last updated: 2023-12-19
Post by snhatton on Add device greyed out
CODESYS Forge
talk
(Post)
What type of PLC are you using?
Last updated: 2023-12-19
Post by eschwellinger on Licensing info not available.
CODESYS Forge
talk
(Post)
check on cli on your device 'cmu -x'
Last updated: 2024-03-19
Post by eschwellinger on cmDongle Raspberry Pi issue
CODESYS Forge
talk
(Post)
should work for sure as HID device.
Last updated: 2024-04-22
Post by jkessler on IoDrvModbusTCP_Diag not defined when using MODBUS
CODESYS Forge
talk
(Post)
Hi, Same for me ! Works in Codesys 3.5.19 but not in 3.5.20. I'm currenly using with a WAGO PLC200 [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'IoDrvModbusTCP_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'IoDrvModbusTCP_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlave_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlave_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlaveUnit_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlaveUnit_Diag' n’est pas un composant de 'IoDrvModbusTCP' Thanks in advance
Last updated: 2024-05-29
Post by jkessler on IoDrvModbusTCP_Diag not defined when using MODBUS
CODESYS Forge
talk
(Post)
Hi, Same for me ! Works in Codesys 3.5.19 but not in 3.5.20. I'm currenly using with a WAGO PLC200 [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'IoDrvModbusTCP_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'IoDrvModbusTCP_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlave_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlave_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlaveUnit_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlaveUnit_Diag' n’est pas un composant de 'IoDrvModbusTCP' Thanks in advance
Last updated: 2024-05-29
Post by jkessler on IoDrvModbusTCP_Diag not defined when using MODBUS
CODESYS Forge
talk
(Post)
Hi, Same for me ! Works in Codesys 3.5.19 but not in 3.5.20. I'm currenly using with a WAGO PLC200 [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'IoDrvModbusTCP_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'IoDrvModbusTCP_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlave_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlave_Diag' n’est pas un composant de 'IoDrvModbusTCP' [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0046: Identificateur 'ModbusTCPSlaveUnit_Diag' non défini [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0080: Le bloc fonctionnel 'IoDrvModbusTCP' doit être instancié pour permettre l’accès [ERREUR] EmPlcProgram: Application [Device: Logique API]: C0004: 'ModbusTCPSlaveUnit_Diag' n’est pas un composant de 'IoDrvModbusTCP' Thanks in advance
Last updated: 2024-05-29
To search for an exact phrase, put it in quotes. Example: "getting started docs"
To exclude a word or phrase, put a dash in front of it. Example: docs -help
To search on specific fields, use these field names instead of a general text search. You can group with AND or OR.