TCP/IP Communication: Problem with response data ^{CODESYS Forge talk (Thread)}
TCP/IP Communication: Problem with response data
Last updated: 2023-06-30

TLS TCP Communication using 3.5.16 NBS Library ^{CODESYS Forge talk (Thread)}
TLS TCP Communication using 3.5.16 NBS Library
Last updated: 2021-05-12

CAA Net Base Services - TCP Keep-Alive ^{CODESYS Forge talk (Thread)}
CAA Net Base Services - TCP Keep-Alive
Last updated: 2019-12-13

Write/Read JSON data to communicate by TCP/IP ^{CODESYS Forge talk (Thread)}
Write/Read JSON data to communicate by TCP/IP
Last updated: 2018-02-08

Komplette Datei (G-Code/ Textdatei) über TCP/UDP empfangen/senden ^{CODESYS Forge talk (Thread)}
Komplette Datei (G-Code/ Textdatei) über TCP/UDP empfangen/senden
Last updated: 2022-05-25

Convert STRING to DWORD for TCP/IP client ^{CODESYS Forge talk (Thread)}
Convert STRING to DWORD for TCP/IP client
Last updated: 2022-06-11

TCP Kommunikation Master Slave Anfänger braucht Hilfe. ^{CODESYS Forge talk (Thread)}
TCP Kommunikation Master Slave Anfänger braucht Hilfe.
Last updated: 2010-06-22

TCP/IP Anbindung Touchpanel an die SPS ^{CODESYS Forge talk (Thread)}
TCP/IP Anbindung Touchpanel an die SPS
Last updated: 2006-06-26

TCP Verbindung zu Drucker in Codesys 3.5 ^{CODESYS Forge talk (Thread)}
TCP Verbindung zu Drucker in Codesys 3.5
Last updated: 2021-02-10

TCP/IP Connection monitoring based on Network 3.5.7.0 Library ^{CODESYS Forge talk (Thread)}
TCP/IP Connection monitoring based on Network 3.5.7.0 Library
Last updated: 2020-09-18

monitoring mulitple PLC's via TCP/IP ^{CODESYS Forge talk (Thread)}
monitoring mulitple PLC's via TCP/IP
Last updated: 2012-03-15

Aufbau einer TCP/IP-Kommunikation zwischen 2 Controllern ^{CODESYS Forge talk (Thread)}
Aufbau einer TCP/IP-Kommunikation zwischen 2 Controllern
Last updated: 2010-10-15

Modubus TCP connection affecting EtherCAT running. ^{CODESYS Forge talk (Thread)}
Modubus TCP connection affecting EtherCAT running.
Last updated: 2013-08-25

mobus tcp slave device. read/write holdings with 2 variables. ^{CODESYS Forge talk (Thread)}
mobus tcp slave device. read/write holdings with 2 variables.
Last updated: 2024-03-20

Post by thysonfury on OPTO22 Groov Epic PR2 Modbus Comms Dropping out every 2 hours and 4 Mins ^{CODESYS Forge talk (Post)}
Hi after some assistance with an error on a Groov PR2 PLC. We have a few different communications set up as shown below: One Modbus TCP Slave Connection - ( Sending / Receiving Data from a PC ) Two Modbus TCP Master Connection - ( Reading Data from a UPS Panel and Reading Data Gas Chromatograph) One Modbus RTU Slave Connection 485 - (Reading Data from a fire and gas panel) One Modbus RTU Master Connection 485 - (Sending Data to a Telemetry Unit) All Licenses have been installed as per OPTO22 suggestions of the order below: Modbus TCP Master Modbus TCP Slave Modbus RTU Master Modbus RTU Slave When I check on License manager the RTU Master license seems to disappear on installing the RTU. (What ever reason I’ve been told this is “normal”). If I use Device License Read It will successfully read all the licenses correctly. Now the issue is every 2 hours and between 4. For what ever reason the communications seems to end and lock up for about 20 seconds. During this time even if I was logged into the PLC it would kick me off and I’d have to re type the password to enter. Most of the devices can handle this however the RTU flags up a communications failure at the SCADA and is raising alarms every 2 hours and 4 mins. We’ve had multiple people go through the code to check for anything obvious. Does anyone have any ideas?
Last updated: 2024-04-15

Post by thysonfury on OPTO22 Groov Epic PR2 Modbus Comms Dropping out every 2 hours and 4 Mins ^{CODESYS Forge talk (Post)}
Hi after some assistance with an error on a Groov PR2 PLC. We have a few different communications set up as shown below: One Modbus TCP Slave Connection - ( Sending / Receiving Data from a PC ) Two Modbus TCP Master Connection - ( Reading Data from a UPS Panel and Reading Data Gas Chromatograph) One Modbus RTU Slave Connection 485 - (Reading Data from a fire and gas panel) One Modbus RTU Master Connection 485 - (Sending Data to a Telemetry Unit) All Licenses have been installed as per OPTO22 suggestions of the order below: Modbus TCP Master Modbus TCP Slave Modbus RTU Master Modbus RTU Slave When I check on License manager the RTU Master license seems to disappear on installing the RTU. (What ever reason I’ve been told this is “normal”). If I use Device License Read It will successfully read all the licenses correctly. Now the issue is every 2 hours and between 4. For what ever reason the communications seems to end and lock up for about 20 seconds. During this time even if I was logged into the PLC it would kick me off and I’d have to re type the password to enter. Most of the devices can handle this however the RTU flags up a communications failure at the SCADA and is raising alarms every 2 hours and 4 mins. We’ve had multiple people go through the code to check for anything obvious. Does anyone have any ideas?
Last updated: 2024-04-15

Post by thysonfury on OPTO22 Groov Epic PR2 Modbus Comms Dropping out every 2 hours and 4 Mins ^{CODESYS Forge talk (Post)}
Hi after some assistance with an error on a Groov PR2 PLC. We have a few different communications set up as shown below: One Modbus TCP Slave Connection - ( Sending / Receiving Data from a PC ) Two Modbus TCP Master Connection - ( Reading Data from a UPS Panel and Reading Data Gas Chromatograph) One Modbus RTU Slave Connection 485 - (Reading Data from a fire and gas panel) One Modbus RTU Master Connection 485 - (Sending Data to a Telemetry Unit) All Licenses have been installed as per OPTO22 suggestions of the order below: Modbus TCP Master Modbus TCP Slave Modbus RTU Master Modbus RTU Slave When I check on License manager the RTU Master license seems to disappear on installing the RTU. (What ever reason I’ve been told this is “normal”). If I use Device License Read It will successfully read all the licenses correctly. Now the issue is every 2 hours and between 4. For what ever reason the communications seems to end and lock up for about 20 seconds. During this time even if I was logged into the PLC it would kick me off and I’d have to re type the password to enter. Most of the devices can handle this however the RTU flags up a communications failure at the SCADA and is raising alarms every 2 hours and 4 mins. We’ve had multiple people go through the code to check for anything obvious. Does anyone have any ideas?
Last updated: 2024-04-15

Post by garrian on How to write multiple coils (Modbus FC15) ^{CODESYS Forge talk (Post)}
Thanks for your reply. I belive it is contiguous, I'm writing to adress 0 to 4. Or, do you mean something else? Well, something is happening. If I on the client set adress 1,2,3 to true, only 1 is set to true on the server side. On the client side, the data is array of word. But on the server side, the coils are array of bool. Holding register is array of word on server side. Can this be a problem? Attached screenshot of how it looks at the server side.
Last updated: 2024-11-17

Post by joanm on Programmatically change the IP addresses of the Modbus TCP slave devices ^{CODESYS Forge talk (Post)}
Hello all, I am working in a project in which there are multiple Modbus TCP slaves. I need to be able to change the IP addresses of those devices from the HMI and I was planning to use the process depicted here: https://faq.codesys.com/display/CDSFAQ/Modbus+TCP+Slave%3A+Dynamic+Setting+of+the+IP+Address I can see the port number is what is used to specify which slave device we want to modify the IP address of. This said, can I freely set arbitrary port numbers to each device? I mean, can I set the first device to be at port 502, the second one at port 503... Any drawback or restriction? Is there any other way to reference to the device without having to change the port numbers? Thank you all in advance.
Last updated: 2024-01-04

Post by ahuckphin on Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Post)}
I have a DFRobot RS485 temperature & humidity sensor (SEN0438) connected to my Raspberry Pi via a USB to RS485 adapter. I am able to connect and read the sensor data when running a python code locally. However in Codesys, I encounter this error "A bus error has occurred." and "There was no response in time". Could this be because of Modbus Server Channel and Modbus Server Init configuration on my part? Admittedly I am new to Codesys. To get to this stage, I: 1. added some lines to CODESYSControl_User.cfg 2. added "Modbus_COM" in Codesys and set "Serial Port Configuration" under "General" 3. added "Modbus_Master_COM_Port" in Codesys and checked transmission mode is set to "RTU" 4. added "Modbus_Slave_COM_Port" in Codesys and checked server address is set to 1 (also set 1 in my sensor) 5. added 1 channel and 1 init for "Modbus_Slave_COM_Port" under "Modbus Server Channel" and "Modbus Server Init"
Last updated: 2024-07-10

Post by ofey on Device parameter - ‘ModbusTCP Configuration’ ^{CODESYS Forge talk (Post)}
Hi! Do anybody know how I can add and enable the parameter 'Default Modbus TCP slave' on a device? I am currently writing a program where the PLC shall be set up as a Modbus TCP client, but I dont know how to add parameters to devices in codesys. I'm pretty new to the codesys environment. The picture in the attachment is on a similar PLC project where I have not written the code. my goal is to add this parameter in another project.
Last updated: 2023-10-04

Post by winki on Modbus TCP Client ^{CODESYS Forge talk (Post)}
Hello, I am new on CODESYS env. I would like to do some Modbus TCP, but I am wondering If using codesys you must use the device "Modbus_TCP_Client" & "Modbus_TCP_Server". I would like to do it without device, only using ST. Is that possible ? I try the example : MODBUS_master_example, but it is not working. If it is possible to dot it without any Device I will show my code. Thx a lot
Last updated: 2024-10-25

Post by gabrielarffa on Modbus TCP/IP having problems with global variables ^{CODESYS Forge talk (Post)}
I'm using Modbus TCP/IP to communicate Codesys with Elipse E3 as the master for a college project. I have made a list of global variables to organize the programming in two different POUs. The problem is, when I try to do the mapping of variables, the program informs me of an error due to the identifiers having a "." on their names. Do I have to reorganize my code to make it an unified block or is there a way to declare their names without changing all the code structure?
Last updated: 2025-05-20

Post by gabrielarffa on Modbus TCP/IP having problems with global variables ^{CODESYS Forge talk (Post)}
I'm using Modbus TCP/IP to communicate Codesys with Elipse E3 as the master for a college project. I have made a list of global variables to organize the programming in two different POUs. The problem is, when I try to do the mapping of variables, the program informs me of an error due to the identifiers having a "." on their names. Do I have to reorganize my code to make it an unified block or is there a way to declare their names without changing all the code structure?
Last updated: 2025-05-20

Post by wbj0t on Global variable access by Programms and Modbus Devices (attach device to bus) ^{CODESYS Forge talk (Post)}
Hi everyone. I use Raspberry Pi 4, one core codesys SL. I have a question about global variable access via programm when I glued the same variable to MODBUS SERIAL/TCP DEVICE holding register. So, the question: what behavior of this modifying? When I set "Always update variables (in bus cycle)" and set some task as bus for the Device, then in another task I cant change this varible (can, but immediatly the old value setted again). But the same things works with MODBUS SLAVE: again "Always update..." and master attached to some task, then I change variable in another task and all works. I cant set up my variables from retains file at PrepareStart event because of this behavior with MODBUS SERIAL/TCP DEVICE. Thanks, wbj0t.
Last updated: 2024-07-18

Sort by relevance or date