Post by elayaraj on Codesys Soft PLC OPC UA server ^{CODESYS Forge talk (Post)}
Hi guys, I also facing the same issue on my project, trying to connect server (Codesys) to UA Expert but the connection keep failed(attached). Im running out of idea right now..please help!
Last updated: 2024-08-22

Post by damian177 on OPC UA Client ^{CODESYS Forge talk (Post)}
The OPC UA Client Example with webvisu is working. Now I would like to use Datasource to connect to OPC UA Server but some is wrong because nothing to do when I try list tags from server - please find in attachement
Last updated: 2024-09-03

Post by damian177 on Problem with downloading OPC UA tags by Data Source Manager ^{CODESYS Forge talk (Post)}
In my OPC UA Server is about 12 thousands tags. Can by possible that downloading tags from OPC UA Server lasts a long time , and when expires about 2 hours (demo license time) that downloading freezes ?
Last updated: 2024-09-04

Post by thn-power on Opaque NodeId in the OPC UA server ^{CODESYS Forge talk (Post)}
I'm wondering the same. Using the old symbol configurator opc ua server gave the node id using a string. Must be a way to specify this at build time?
Last updated: 2024-12-16

Post by winki on OPCUA Server With COntrol For Linux Arm64 ^{CODESYS Forge talk (Post)}
Hello, I am wondering if it is possible to have OPCua Server with Control for linux ARM64. Indeed I am not able to add symbol configuration.
Last updated: 2025-01-13

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 paulorb on STRUCT AT %MW1000 ^{CODESYS Forge talk (Post)}
Hi I am trying to use STRUCT to parse commands from Modbus/TCP, Modbus client will fill the bytes related to a specific command (type, parameters), then PLC (Codesys) will access the command parameters. A STRUCT will simplify a lot the process of parsing the data, so I don't need to parse byte per byte, address will be mapped to a struct and I can use it for parsing the data. From what I understood, the compiler does not allow me to specify the location of the struct for a %MW register. VAR_COMMAND AT %MW1002: structGenericModbusCommand; This will throw: Bad declaration, use '%ML' for 'structGenericModbusCommand' variable But If I change it to %ML, when you go online you see that it is actually allocating the struct in another memory address. When we go online, on GVL we can see: VAR_COMMAND. structGenericModbusCommand %ML1002 commandType COMMANDTYPE %MB8016 ... %MB8020 I am not specifying a pointer or a reference it is a struct type, why is it mapping to a %MW location (random one). How can I control where it is mapping to? I need a consistent way to map STRUCT to specific modbus address. Is it possible? Thanks, Paulo Note I am using a Codesys OEM: Schneider Machine Expert Logic Builder (M241)
Last updated: 2024-08-13

Post by dawidr on Best practices for querying multiple MODBUS devices ^{CODESYS Forge talk (Post)}
Hi! What are the best practices for querying multiple Modbus devices? Single PRG or maybe multiple PRG (so basically multiple thread) per each Modbus device. In my current implementation I'm using single PRG and I'm utilizing FbMbMasterMultiQuerySerial and WagoAppPlcModbus.FbDigitalTwinMbSlaveDevice in eCockpit with PFC200. I've the timer with 2 seconds delay there and it was working fine for single device. But now I have three Modbus devices and for two of them I need to run 2/3 queries to get data from all registers. I noticed that the delays for getting the data from the Modbus devices is much bigger right now.
Last updated: 2024-07-31

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 snhatton on OpC UA server on Raspberry Pi 64 SL runtime ^{CODESYS Forge talk (Post)}
Good afternoon, After changing the security settings to: CommunicationPolicy: POLICY_BASICSHA256SHA256 CommunicationMode: ALL Activation: Activated UserAuthentication: ENABLED Then generate a new certificate on the device for the OPC-UA server from Security Agent->Device->OPC UA Server. Restart the runtime using tools->Update Raspberry Pi->Stop->Start for the changes to take effect. It may take a minute for the runtime to start. Initiate the connection from the UA server side. You should see a pop-up asking you to trust the certificate. Click on the button 'Trust Server Certificate'. Next, you should see a certificate in the quarantined folder of the security agent in CODESYS. Click and drag this from quarantined to trusted and then try connecting from UA expert to the device. These steps worked for me and my setup and I hope they can help you!
Last updated: 2023-12-11

Post by expertplas on No connection to opc server from codesys opc client ^{CODESYS Forge talk (Post)}
Hello, we have aproblen to connect our CODESYS OPC Client to the OPC Server. We installed the client according the CODESYS manual. We can browse the server and variables can be linked to the PLC. I created a self signed certificate for the CmpOPCUAClent as described. The server has a cerificate also. I copied the certificates to the trusted zone of server and client. But when it comes to data exchange we get an error message. "Communication error in data source OPC UA Library. Error ID : 7001 German : "Kommunikatinsfehler inder Datenquelle OPC UA -Bibiothek. Es wurde kein genauer Fehler angegeben. Fehler ID : 7001" It semms that there is no cerificate exchange. We are working with CODESYS 3.5 SP19 Patch 5. Can anyone here say something about this error or has an idea for a solution? Thanks.
Last updated: 2024-08-19

Post by sigurdrb on OPC server in "Communication manager" ^{CODESYS Forge talk (Post)}
Hi! I was thinking of switching the OPC server config from "Symbol Configuration" to the "Communication manager" in the device tree. I Have a lot of arrays of structs that I have previously declared in the "Persistent Variable" object in the device tree. It seems as it is not supported to directly expose persistant variables to the OPC server like the "older" way of doing it in the symbol config. Is this correct? Do you recommend to just do it the old fashioned way, or should I edit the structure of the global variable list / persistant data / OPC server and set up the OPC server from the "Communication manager" object?
Last updated: 2025-01-20

Post by simover on TCP/IP client ^{CODESYS Forge talk (Post)}
HELLO thank for you answer!! I'm a beginner can you give me an example?
Last updated: 2023-12-19

Post by timl on BacNet Server ^{CODESYS Forge talk (Post)}
Hallo, für einen BacNet2 Server lassen sich mit zwei Ethernet Schnittstellen auch zwei Bacnet 2 IP Datalinks anlegen. Einen Datalink nutze ich für den UDP Port 47808 und einen für den UDP Port 47809. Dadurch ist der Server aus beiden Netzwerken erreichbar, was so gewollt ist. Allerdings verbindet er die beiden Netze auch miteinander, was zu Kommunikationsproblemen führt, da in beiden Netzwerken bereits gleiche Device ID's vergeben sind und diese sich dann doppeln. Lässt sich diese Verbindung der beiden Netze abschalten? Gruß Tim
Last updated: 2024-02-20

Post by miodusy on File transfer via visu and codesys automation server ^{CODESYS Forge talk (Post)}
I have a problem with the file transfer library. Namely, it does not work via the codesys server. (error 5; overtime, and visualization resets). They operate mostly in local chains. I tested different browsers and VPN from the router. It works everywhere, except through access from the codesys automation server. The client, having many machines under one account, prefers to keep it that way rather than use an individual VPN just to download a backup. Does anyone have an idea what the problem is? Sylwester M.
Last updated: 2024-03-07

Post by kuegerls on OpC UA server on Raspberry Pi MC SL - Certificate Issue ^{CODESYS Forge talk (Post)}
Hello, I have set up an OPC UA server following several guides, including this one: https://revolutionpi.com/documentation/tutorials/opc-ua-codesys-nodered/. The license for the runtime is installed on the device. However, I am unable to create a certificate for the OPC UA server in the security screen. I always get the error message: "The certificate has not been created by the device." Does anyone have an idea what might be causing this issue? Any help would be greatly appreciated! Thanks in advance! Best regards, Stefan
Last updated: 2025-04-02

Post by yannickasselin on codesys VLAN tagging ^{CODESYS Forge talk (Post)}
I ordered a cheap managed switch and tested it as soon as I received the switch. It works great! I even went a bit further. As you can see in the screenshot, I created 2 Codesys containers. Each one having 2 fieldbuses. The first one has EtherCAT and EtherNet/IP and the second one has EtherCAT and Modbus/TCP. All going through the same ethernet port from the PC to the switch. The switch splits it up into 4 different networks. The hardest part was to figure out how to configure the switch. @eschwellinger, thank you very much.
Last updated: 2024-09-17

Post by timvh on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
It seems you have 2 network interfaces. Did you try eth1? Did you already configure the IP address for this interface in Linux? If yes, then maybe undo this. - or only set eth0 in the Nic configuration without anything else (so no IP address, because this is already set in Linux). For more information about the Nic settings, see (probably already read it?): https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_obj_deploy_control_sl_configuration.html PS, if you only want to run CODESYS Control SL, you don't necessarily need the Virtual PLC variant. You could also install and run the CODESYS Control SL Runtime in the Host operating system. This way you should also be able to access the serial port and directly access all ethernet ports. Maybe this is easier?
Last updated: 2024-10-23

Sort by relevance or date