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 thierry-b on CODESYS device discovery performance in large networks (/16) ^{CODESYS Forge talk (Post)}
Hello, We are using CODESYS 3.5 SP19.70 in an educational environment with several WAGO PFC200 controllers (CODESYS Runtime). Our campus network is currently configured as a /16, which creates a very large broadcast domain. We observe slow device discovery and long scan times when opening the network view. Before restructuring our architecture, we would like to know the recommended network practices for CODESYS: Recommended broadcast domain size for device discovery Possible impact of large networks (/16) on scan performance Usual recommendations (VLANs, /24 segmentation, etc.) Known limitations or points of attention in extended networks Any guidance or official recommendations would be very helpful. Thank you.
Last updated: 2026-03-29

Post by cd-tt on cannot connect ot linux runtime: device does not answer the scanrequest ^{CODESYS Forge talk (Post)}
I have the following setup: Proxmox PC with a debian 13 VM running CODESYS Control Linux SL and Edge Gateway. Installation method was through the Deploy Control SL and went rather smoothly. In my Device Tab I find the gateway and when scanning my network I also find my runtime. I want to connect and get promted that I should add a user. After setting up the user I get an error saying, that the device is not responding my scanrequest. Deploy Control SL Operation saying everythings up and running. I can confirm that from the terminal on the VM with "systemctl status codesyscontrol" and "systemctl status codesysgateway". I am running out of ideas how to fix that issue. Can anybody help? Screenshots attached.
Last updated: 2026-06-11

Post by eschwellinger on Connection to device closed ^{CODESYS Forge talk (Post)}
is there a way to check the plclog on Opus A3 by using cmd line under Linux? This log is what you need to check for the disconnection problem
Last updated: 2023-08-24

Post by chris12345 on FILE_OPERATION_DENIED ^{CODESYS Forge talk (Post)}
Hello everyone, I am using SP19 patch 2 on a Kunbus device with runtime package 4.9.0.0. I am having the same problem as mentioned above. With the FB File.open I get the FILE_OPERATION_DENIED error. I have also tried the path /var/opt/codesys/PlcLogic. Any advice? Chris
Last updated: 2023-10-17

Post by totorovic on Hard shutdown: no code on device after power on ^{CODESYS Forge talk (Post)}
Hi, Runtime goes in exception before the shutdown ? Do you have a .err file which is created ? (located in the folder of the .app and .crc)
Last updated: 2024-10-03

Post by timvh on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
Most likely your IP address is set to 172.... because you use a VPN connection to your device. Probably best to use the other Ethernet interface for your modbus communication.
Last updated: 2024-10-24

Post by zatalian on Beckhoff EL7037 softmotion ^{CODESYS Forge talk (Post)}
Hi, Is the Beckhoff EL7037 supported by codesys with softmotion? Where can I find a device descriptor that includes the drive object for the EL7037?
Last updated: 2024-11-25

Post by gatto on library ModbusTCP Slave 4.1.0.0 - function block ModbusServer ^{CODESYS Forge talk (Post)}
Hi, again after spending a lot of time finding more information with no results, by chance I changed the device ID from 1 to 255 and the transmission works. Unfortunately the documentation is very very poor.
Last updated: 2024-11-28

Post by teichhei on The selected container ... does not fit your ticket ^{CODESYS Forge talk (Post)}
Don't I need a browser on the device for web depot? Could work on the Pi but not the Wago controller. Maximum I have is SSH.
Last updated: 2025-01-08

Post by romrot on Trying to connect Codesys OPC server to Ignition ^{CODESYS Forge talk (Post)}
Does the OPC UA server have a generic username and password? It doesn't seem to be the same as the device username and password.
Last updated: 2025-01-22

Post by romrot on Trying to connect Codesys OPC server to Ignition ^{CODESYS Forge talk (Post)}
Does the OPC UA server have a generic username and password? It doesn't seem to be the same as the device username and password.
Last updated: 2025-01-22

Post by ojz0r on Multiple applications on one device sharing variables. ^{CODESYS Forge talk (Post)}
One thing you could do is create an object with the variable as field with a function and procedure to get the variable (read) and set the variable (write). These are then called from your program and the vizualization.
Last updated: 2025-02-20

Post by felipemsgarcia on Axis EtherCAT address ^{CODESYS Forge talk (Post)}
Hello, I'd like to write some parameters to axes from inside a function block where I passed axis by reference, using ETC_CO_SdoWrite. Is it possible to get the device address from inside the function block? Please see example below. Thank you!
Last updated: 2025-03-06

Post by mariacugnier on Reading Devices ComState ^{CODESYS Forge talk (Post)}
Does anyone know how to access the ModbusTCPSlave_Diag.ComState without declaring each one by the device name? I attached them to an array but since I may have dozens of devices this is still a bad solution.
Last updated: 2025-05-22

Post by mariacugnier on Reading Devices ComState ^{CODESYS Forge talk (Post)}
Does anyone know how to access the ModbusTCPSlave_Diag.ComState without declaring each one by the device name? I attached them to an array but since I may have dozens of devices this is still a bad solution.
Last updated: 2025-05-22

Post by timothyzalusky on Missing Device Descriptions in Repository ^{CODESYS Forge talk (Post)}
For reference this is fixed by installing the new codesys install with a separate repository folder. Completely resolved. If anyone else sees this. I would like to know why the persistent devices repository folder does not properly retain between installs though.
Last updated: 2025-06-12

Post by timothyzalusky on Missing Device Descriptions in Repository ^{CODESYS Forge talk (Post)}
For reference this is fixed by installing the new codesys install with a separate repository folder. Completely resolved. If anyone else sees this. I would like to know why the persistent devices repository folder does not properly retain between installs though.
Last updated: 2025-06-12

Post by timothyzalusky on Missing Device Descriptions in Repository ^{CODESYS Forge talk (Post)}
For reference this is fixed by installing the new codesys install with a separate repository folder. Completely resolved. If anyone else sees this. I would like to know why the persistent devices repository folder does not properly retain between installs though.
Last updated: 2025-06-12

Post by pernockham on PHOENIX CONTACT Axioline PLCnext project in CodeSys SodftPLC ^{CODESYS Forge talk (Post)}
You should use PLCnext if your device-hw is a PLCnext-un it. As I understand it you are using "CODESYS Control Win V3 x64".
Last updated: 2025-09-09

Post by timvh on Codesys Control for PLCnext (PLC - AXL F 2152) ^{CODESYS Forge talk (Post)}
Do not filter on Phoenix devices. First add an Ethernet device (from CODESYS). Then add a Profinet Controller (from CODESYS). Then add your Phoenix devices to this CODESYS Profinet Controller.
Last updated: 2025-09-09

Sort by relevance or date