CODESYS Modbus Channels ^{CODESYS Forge talk (Thread)}
CODESYS Modbus Channels
Last updated: 2021-08-11

Alarmmanagement Modbus Zugriff ^{CODESYS Forge talk (Thread)}
Alarmmanagement Modbus Zugriff
Last updated: 2011-08-08

Modbus FC6 ^{CODESYS Forge talk (Thread)}
Modbus FC6
Last updated: 2010-03-21

Modbus RTU RS485 ^{CODESYS Forge talk (Thread)}
Modbus RTU RS485
Last updated: 2020-03-07

Modbus Master Lizenz ^{CODESYS Forge talk (Thread)}
Modbus Master Lizenz
Last updated: 2018-01-21

Modbus RTU RS485 ^{CODESYS Forge talk (Thread)}
Modbus RTU RS485
Last updated: 2014-10-21

Modbus RTU - Dynamics channels ^{CODESYS Forge talk (Thread)}
Modbus RTU - Dynamics channels
Last updated: 2017-07-27

Problem with simulation Modbus ^{CODESYS Forge talk (Thread)}
Problem with simulation Modbus
Last updated: 2024-03-22

Modbus TLS Kommunikation ^{CODESYS Forge talk (Thread)}
Modbus TLS Kommunikation
Last updated: 2025-11-06

22kW Wallbox mit Modbus ^{CODESYS Forge talk (Thread)}
22kW Wallbox mit Modbus
Last updated: 2025-11-17

runtime dynamic modbus devices ^{CODESYS Forge talk (Thread)}
runtime dynamic modbus devices
Last updated: 2025-11-21

Post by bruno-roth on 22kW Wallbox mit Modbus ^{CODESYS Forge talk (Post)}
Hallo, das ist wohl das falsche Forum für Wallboxen :-) Aber ich empfehle dir Die GO-E-Charger die hat eine sehr offene Schnittstelle und API auch mit Modbus TCP https://github.com/goecharger/go-eCharger-API-v2/blob/main/modbus-de.md
Last updated: 2025-11-17

Post by mil581 on Modbus TCP Server connection is ESTABLISHED but all holding registers are value 0? ^{CODESYS Forge talk (Post)}
Hello everyone! I'm facing a weird issue with CODESYS Control Win V3 x64 on a fresh Windows install. The situation is as follows: CODESYS Modbus TCP Server (Slave) is running and I can see live values in the mapping display of Modbus settings: GVL (e.g., 32, 42, 50). Port 502 is LISTENING according to netstat. When connecting via Modbus Poll or Node-RED, the connection status changes to ESTABLISHED and everything reports as fine. The Problem: Despite the successful connection, all holding registers return 0 no matter what. It's like the OS accepts the TCP handshake, the request counter goes up but the data payload never reaches Modbus Client (in this case Node-RED or Modbus Poll). Quick Stats: Firewall: Completely OFF. Unit ID: Verified & Matching. IP: Tried 127.0.0.1 and 192.168.0.1. Interface: Correctly bound in Ethernet Device settings. I already tried absolutely everything from changing IP address, subnet, port, deleting the project and starting new one and even nuking my old Windows install. Since I am near completion of my bachelor thesis only thing left for me to do is connect SoftPLC to NodeRED via Modbus but this issue is driving me crazy for weeks. I do not know what to do anymore.
Last updated: 2025-12-25

Post by hagroth on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
Today I was struggling with the same problem. in search for a solution i found this thread. Then i tried some things. It doesn't seem to be just a libraries' fault. In addition to 3.5.19, we also have a 3.5.18 version installed, the library versions of Modbus_TCP_Master and Modbus_TCP_Slave are the same, but more than 10 slave channels can be added in 3.5.18
Last updated: 2024-02-02

Post by em1681 on Modbus RTU over 750-652 ^{CODESYS Forge talk (Post)}
Hi, It's my first time operating in Codesys 2.3, but I have done a good amount of Codesys programming, so I'm a little familiar. I haven't done a lot of RTU, but a lot of Modbus TCP. I don't have the PLC in my reach at the moment, but I'm trying to be a little ahead. We're adding the 750-652 module to read energy from a flowmeter over RTU. There will only be 1 slave. I attached pictures of my current hardware, PLC code, the register datasheet from the slave and the only modbus serial library I seem to have available. I'm uncertain if this will work. Any help or clarification on how things work will be greatly appreciated. Thanks in advance.
Last updated: 2025-09-01

Post by sonnh on How to use more 4 instances of CANopen/Profibus/Modbus with The application-based license CODESYS Control ^{CODESYS Forge talk (Post)}
The codesys application license allows the use of up to 4 fieldbus instances (eg Modbus). I need to use more instances than that. Can I use the Modbus library instead? Does this usage require a license? Similar to other libraries such as CanOpen, Modbus TCP...
Last updated: 2023-11-02

Post by fmon on Modbus TCP client reconnection problem ^{CODESYS Forge talk (Post)}
Problem solved The client modbus cycle time was linked to a task at 500ms. Whereas the channel modbus was at 200ms. Certainly problem of packages synchronisation. I let the client modbus cycle time to be handled by itself (See attachement) --> "Use the bus cyle time parameters" (traduce from french) See attachement
Last updated: 2025-03-18

Endianness Problem in TCP Communication ^{CODESYS Forge talk (Thread)}
Endianness Problem in TCP Communication
Last updated: 2022-09-11

HTTP Client TCP Init Error ^{CODESYS Forge talk (Thread)}
HTTP Client TCP Init Error
Last updated: 2024-07-04

Bootproject, TCP Server and booting ^{CODESYS Forge talk (Thread)}
Bootproject, TCP Server and booting
Last updated: 2017-01-13

Indralogic 1 Networking TCP/IP ^{CODESYS Forge talk (Thread)}
Indralogic 1 Networking TCP/IP
Last updated: 2015-11-27

TCP/IP communication between PLCs ^{CODESYS Forge talk (Thread)}
TCP/IP communication between PLCs
Last updated: 2014-06-20

Telegram communication - TCP/IP ^{CODESYS Forge talk (Thread)}
Telegram communication - TCP/IP
Last updated: 2010-06-15

error with raspberry tcp socket ^{CODESYS Forge talk (Thread)}
error with raspberry tcp socket
Last updated: 2018-01-29

sps per tcp/ip verbinden ^{CODESYS Forge talk (Thread)}
sps per tcp/ip verbinden
Last updated: 2005-08-25

Sort by relevance or date