CoDeSys OPC DA SL won't install on Windows Server 2012 R2 ^{CODESYS Forge talk (Thread)}
CoDeSys OPC DA SL won't install on Windows Server 2012 R2
Last updated: 2020-11-03

CODESYS development system integration with MQTT broker through IIoT libraries SL ^{CODESYS Forge talk (Thread)}
CODESYS development system integration with MQTT broker through IIoT libraries SL
Last updated: 2020-09-10

[HELP] Connecting Codesys v2.3 program with a Codesys HMI SL project in V3 ^{CODESYS Forge talk (Thread)}
[HELP] Connecting Codesys v2.3 program with a Codesys HMI SL project in V3
Last updated: 2021-10-18

Raspi SL MC: Which core is used by OPC-UA server ^{CODESYS Forge talk (Thread)}
Raspi SL MC: Which core is used by OPC-UA server
Last updated: 2020-12-16

Codesys for linux SL AMD64 and last update of UBUNTU 22.04 ^{CODESYS Forge talk (Thread)}
Codesys for linux SL AMD64 and last update of UBUNTU 22.04
Last updated: 2023-02-06

Post by eschwellinger on Only single ehternet ip drive is communicating ^{CODESYS Forge talk (Post)}
which versions EIP & Runtime and which plc is this? Does it work if they are connected to one network interface?
Last updated: 2024-03-09

Post by trycyclepower on Only single ehternet ip drive is communicating ^{CODESYS Forge talk (Post)}
I had them inserted separately, now under one Ethernet tree they are working.
Last updated: 2024-03-11

Post by eschwellinger on cmDongle Raspberry Pi issue ^{CODESYS Forge talk (Post)}
use Arm64 SL or Arm SL instead of the PI package - this will work
Last updated: 2024-04-24

Establishing TLS Connection with MQTT Broker using MQTT Client SL Package ^{CODESYS Forge talk (Thread)}
Establishing TLS Connection with MQTT Broker using MQTT Client SL Package
Last updated: 2024-06-20

Post by mos89p on Codesys Soft PLC OPC UA server ^{CODESYS Forge talk (Post)}
Hi did you check the log of OPCUA expert Client?
Last updated: 2024-06-27

OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext ^{CODESYS Forge talk (Thread)}
OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext
Last updated: 4 days ago

OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext ^{CODESYS Forge talk (Thread)}
OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext
Last updated: 2026-06-22

Post by cfam on Codesys Control for PLCnext SL, Bus not running ^{CODESYS Forge talk (Post)}
Good day I would appreciate it if you can give me some advice on how to fix my "Bus Not Running Error". I am Using Codesys 3.5 SP20 and Codesys Control PLCnext SL V4.12.0.0. Codesys control was installed on the device and I can log into it but it seems that it does not pick up the PLC or the IO attached (Please see attached Image). The Bus Cycle Task of the AXL F 2152 is set to Main Task and the "Always update Variable" is Enabled on each IO Module. My Main Task interval is set to 100ms and Priority is set to 0. I have tried other options and none seem to work. Your response to this issue will be highly appreciated.
Last updated: 2024-08-12

Post by cfam on Codesys Control for PLCnext SL, Bus not running ^{CODESYS Forge talk (Post)}
Good day I would appreciate it if you can give me some advice on how to fix my "Bus Not Running Error". I am Using Codesys 3.5 SP20 and Codesys Control PLCnext SL V4.12.0.0. Codesys control was installed on the device and I can log into it but it seems that it does not pick up the PLC or the IO attached (Please see attached Image). The Bus Cycle Task of the AXL F 2152 is set to Main Task and the "Always update Variable" is Enabled on each IO Module. My Main Task interval is set to 100ms and Priority is set to 0. I have tried other options and none seem to work. Your response to this issue will be highly appreciated.
Last updated: 2024-08-12

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by pernockham on Control for linux SL, 4.14.0.0 -> 4.15.0.0 breaks web page access. URL requires authentication ^{CODESYS Forge talk (Post)}
I have a problem which I have identified with a device-update from 4.14.0.0 to (4.15.0.0-4.17.0.0) where the newer versions will stop any local access to the internal web page with the browser responding "The requested URL requires authentication". Setting the device back to 4.14.0.0. the web page will respond. Access to web page through Automation server is possible also for the newer version, but not "local" access. Runtime (Codesys control for linux SL) is on 4.17.0.0. I have tried to manipulate settings for 'Access-Control-Allow-Origin' '*' always; through nginx (normally a proxy_pass to localhost:8080). Also tested bypassing nginx by accessing 8080 directly with the same result.
Last updated: 2025-09-08

Post by preimesbergert on Raspberry Pi 4 B HW 1.5 Codesys control 4.10.0 stopps after a few seconds ^{CODESYS Forge talk (Post)}
Wanted to play a bit with a raspberry Pi 4 Model B HW 1.5 and Codesys. Regardless of the image (tried 32bit / 64bit version from Raspberry Pi Imager) and with all tested Codesys Control versions (4.2.0, 4.8.0, 4.10.0) and regardless if single core / multicore / 64 bit variant, always is the runtime stopped after about 30sec with the nice message: ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-7, 0x00000BB8, 0xFFFFFFFB) Whats wrong with it?!?!? I read a lot about the issue in topics from 2020-2021 but it always was stated with new Codesys control version issue will be fixed (4.4 for example) but still it is there.
Last updated: 2023-12-21

Post by preimesbergert on Raspberry Pi 4 B HW 1.5 Codesys control 4.10.0 stopps after a few seconds ^{CODESYS Forge talk (Post)}
Wanted to play a bit with a raspberry Pi 4 Model B HW 1.5 and Codesys. Regardless of the image (tried 32bit / 64bit version from Raspberry Pi Imager) and with all tested Codesys Control versions (4.2.0, 4.8.0, 4.10.0) and regardless if single core / multicore / 64 bit variant, always is the runtime stopped after about 30sec with the nice message: ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-7, 0x00000BB8, 0xFFFFFFFB) Whats wrong with it?!?!? I read a lot about the issue in topics from 2020-2021 but it always was stated with new Codesys control version issue will be fixed (4.4 for example) but still it is there.
Last updated: 2023-12-21

Post by valec on Connect local Asem HMI runtime to local Codesys Control Win V3 x64 ^{CODESYS Forge talk (Post)}
I have a project made on a PL700 PLC with Codesys and an Asem Premium HMI panel. I don't have access to the physical PLC right now, so I'm trying to use Codesys Control Win V3 x64. I created the application and loaded "Codesys Control Win V3 x64" without errors, then I activate "Start PLC" from the tray. Asem cannot connect. I tried to use "localhost" or the local IP address and it doesn't work (it's the "CoDeSys Soft PLC Communication Driver"). I need to connect my local Asem runtime to a virtual Codesys application on my PC. How can I do it?
Last updated: 2024-03-26

Sort by relevance or date