Post by eschwellinger on Application based license problem - Modbus TCP ^{CODESYS Forge talk (Post)}
Which versions exactly are involved? Runtime on PI? CODESYS Version and compilerversion?
Last updated: 2023-12-18

Post by eschwellinger on Application based license problem - Modbus TCP ^{CODESYS Forge talk (Post)}
you could sent the projectarchive to 'my question' in the CODESYS store
Last updated: 2023-12-18

Post by solidlogicguy on Little endian to Float from Modbus RTU ^{CODESYS Forge talk (Post)}
Just tried and returns the same value but in scientific notation.
Last updated: 2024-01-08

Post by bfunk on Wago 750-8101 (mit Codesys V3) als Profinet device ^{CODESYS Forge talk (Post)}
Moin, ich habe da ein Problem und komme einfach nicht weiter... Ich moechte eine Wago 750-8101 (mit Codesys V3) zu einem ModBus TCP Slave und einem Profinet slave machen. ModBus habe ich hinbekommen, Profinet bekomme ich einfach nicht hin. habt ihr das evtl. einen hilfreichen Tip fuer mich? Programmiert wird mit Codesys V3.5 SP19 Patch 2 Auf dem Zielsystem (PFC100) ist die Zielsystemversion 4.6.0.0 Das es nicht optimal ist PN und ModBus TCP auf einer Schnittstelle zu haben ist mir bewusst. Wollte aber erstmal ModBus und Profinet zum laufen bekommen bevor ich das Profinet auf die 2. Ethernet-Schnittstelle bringe. /etc/CODESYSControl_User.cfg [SysSocket] Adapter.0.Name="br0" Adapter.0.EnableSetIpAndMask=1 Adapter.1.Name="br1" Adapter.1.EnableSetIpAndMask=1 ist eingetragen. so sieht der Status fuer das PN-device aus. Anbei ein Screenshot.
Last updated: 2024-01-16

Post by jbarrio on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
Also, this solution is not valid for the RTU, I imagine that this bug should be a high priority...
Last updated: 2024-01-22

Post by rh-pk on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
Hi, i found a solution for me. I had installed a 'old' version of CoDeSys (3.5.18 P5). I tried to add channels there, which works fine. I created a new project, added an Ethernet-Port, added a Modbus-Master and then I copied the ModBus-Slave from my working project to the new project. Now I could add more channels. I add the channels 10 and 11. Then I deleted (please make a backup before :-) the original ModBus-Slave in my working project and copied the extended Slave back to my working project. Surprisingly it is now possible to add new channels. Maybe this will help you.
Last updated: 2024-02-14

Post by tokamk on Dynamic setting of the modbus tcp/ip slave ip address ^{CODESYS Forge talk (Post)}
Hello, I'm working on a project which includes Panel-PC which communicates with a PLC through Modbus TCP/IP. On the PLC I have a CODESYS code which has Modbus slave objects. The Modbus slave objects have to have manually set IP address in order for them to work properly and the Ip address has to be the PC-Panels's IP. This project is going to a customer and they're using their own IP address realm. So, my question is that is it possible to configure these slaves in some other way, so that the customer doesn't need to modify the CODESYS project? I was thinking that would it be possible to set the IP address of these slaves from external source?
Last updated: 2024-02-15

Post by tomast on Siemens V20 Frequenzumrichter über Modbus RTU ^{CODESYS Forge talk (Post)}
Hi Tim, Have you sorted out your problem because i have also problems with i?
Last updated: 2024-03-21

Post by dawidr on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Last updated: 2024-04-07

Post by csanderson on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
I am also having this same issue after upgrading to 3.5.20.0. Any help Codesys?
Last updated: 2024-04-17

Post by santana on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
I'm having this same issue. I upgraded to 3.5.20.0 from 3.5.19.20. Now I have the precompile errors shown above.
Last updated: 2024-04-17

Post by eschwellinger on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
error need to be solved by CODESYS. hopefully next release
Last updated: 2024-05-01

Post by zer0g on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, Thank you for your suggestion but the problem is fixed after I disabled and enabled the network adapter from Windows settings.
Last updated: 2024-05-30

Post by eschwellinger on Modbus TLS Kommunikation ^{CODESYS Forge talk (Post)}
hi, das geht leider nicht mit aktivierter Verschlüsselung , sorry - denke aktuell bleibt dir nur auf Slave Seite die Verschlüsselung zu deaktivieren.
Last updated: 2025-11-09

Post by dafalin-codesys on Transparent wireless serial bridge for Modbus RTU – experience with LoRa/WiFi RS-485 link to CODESYS runtime ^{CODESYS Forge talk (Post)}
Last updated: 2026-03-18

Post by eschwellinger on Codesys MODBUS RTU devices ^{CODESYS Forge talk (Post)}
On which plc you want to add this your screenshot show that it would work on Control Win ?
Last updated: 2026-07-14

Post by nehaltrivedi96 on Modbus connection via Qronox PCD3 M6893 ^{CODESYS Forge talk (Post)}
Thank you for your suggestions, based on it I will modify the code
Last updated: 2026-02-18

Post by husarz17 on How change Unity-ID in TCP Modbus Slave ^{CODESYS Forge talk (Post)}
Hi nulltrace, Thanks for the info. I'm waiting to hear back from you. Take care!
Last updated: 2026-04-13

Post by danp1406 on Question about Demo License limitations for Modbus TCP communication and Fieldbus Instances ^{CODESYS Forge talk (Post)}
Hello everyone, I am currently working with CODESYS Virtual Control for Linux running in Docker on a Debian virtual machine. I am deploying my application using Deploy Control SL, and in my project I am using the ModbusFB library to implement Modbus TCP communication. My setup is the following: I am trying to establish a Modbus TCP connection between a virtual PLC (CODESYS acting as Modbus TCP Client/Master) and a Siemens S7-1200 PLC acting as a Modbus TCP Server. From the Debian VM, I can successfully ping the S7-1200 and verify that port 502 is open using tools like nc. Network-wise, everything appears to be correct. However, when running the application in CODESYS, I receive messages such as “Demo mode for Modbus/TCP Master started. Will expire and stop!” and socket errors like “ClientSocket.UpdateStatus socket error 111 disconnecting.” The ClientTCP block from the ModbusFB library attempts to connect, but the connection does not remain stable. My main question is whether the CODESYS demo license explicitly limits or interrupts Modbus TCP Master communication. Is it expected that in demo mode the runtime will automatically close sockets after some time or prevent stable Modbus TCP connections? I would like to confirm whether this behavior is normal when using ModbusFB in demo mode, or if I should continue troubleshooting the configuration. Additionally, I would like clarification regarding the “fieldbus instances” mentioned in CODESYS licensing options (for example, 2, 4, or 16 instances). What exactly is considered one fieldbus instance? Does one Modbus TCP Client block count as one instance? Does each active connection to a different device count separately? Do Modbus TCP Master and Server count independently toward the total number of instances? Finally, I would appreciate clarification on any other practical limitations of demo mode when using industrial communication libraries such as ModbusFB. Are there limits on the number of connections, number of requests, or communication duration? I am trying to determine whether demo mode is sufficient for testing a virtual PLC communicating with a Siemens S7-1200 over Modbus TCP, or whether a full license is required even for this kind of validation scenario. Thank you in advance for any guidance.
Last updated: 2026-02-25

Post by ahuckphin on Issues with Modbus Slave with Raspberry Pi ^{CODESYS Forge talk (Post)}
codesyscontrol_user.cfg [SysCom] Linux.Devicefile.1 = /dev/ttyUSB0 portnum:=COM.SysCom.SYS_COMPORT1; **parameters are used in the python-script ** method: "rtu" port: "COM8" baudrate: 9600 stopbits: 1 bytesize: 8 parity: 'N' timeout: 1 register address for humidity: 0x000 register address for temperature: 0x001 unit ID: 1 **parameteized in the modbus-master-comport ** see attached files
Last updated: 2024-07-11

Post by nltheves on Raspberry PI4 Serial Port ^{CODESYS Forge talk (Post)}
Hi Ricardo. I was having the same problem with Codesys and a Raspberry Pi 2W while using the GPIO uart. Your post helped me a lot. Thanks! But could not understand why MODBUS parity bit makes Codesys MODBUS COM driver stopping to work after first request transmission. Did you see this @eschwellinger ? Regards, Nelson
Last updated: 2024-07-18

Post by oymyakon on Modbus Lockup ^{CODESYS Forge talk (Post)}
Hi i have a project where i am communicating with many modbus devices using TCP to serial. This is all working extremely well except when i turn one of the remote devices off. If i leave the auto reconnect on it still doesn't talk to the rmianing devices and if i turn Auto reconnect off it locks up. Any help would be appreciated. Paul.
Last updated: 2024-08-07

Post by oymyakon on Modbus Lockup ^{CODESYS Forge talk (Post)}
Hi i have a project where i am communicating with many modbus devices using TCP to serial. This is all working extremely well except when i turn one of the remote devices off. If i leave the auto reconnect on it still doesn't talk to the rmianing devices and if i turn Auto reconnect off it locks up. Any help would be appreciated. Paul.
Last updated: 2024-08-07

Post by fmon on Modbus TCP client reconnection problem ^{CODESYS Forge talk (Post)}
Hello, I am using codesys Modbus TCP client (4.4.0.0) to communicate with a python modbus server (package pyModbusTCP). I first start my python server on the distant machine. After a fresh codesys compilation, a plc connection/transfer and a PLC run, the modbus connection is OK. Every time in this context the connection is created correctly. When I shut down the server, the modbus connection falls, that is normal. When I restart the python server, impossible to recreate the modbus connexion. With the client autoreconnection, I see on my server that the client tries to connect but unsuccesfully. I have the following message : DEBUG:pyModbusTCP.server:accept new connection from ClientInfo(address='192.168.1.20', port=33476) DEBUG:pyModbusTCP.server:Exception during request handling: NetworkError('recv return null') I tried to stop the codesys client and to restart it with these commands : Modbus_TCP_Client.xStop := True; // Or False Modbus_TCP_Client.Enable := True; // Or False Modbus_TCP_Server.Enable := True; // Or False I tried to confirm the error manually to force reconnection with: Modbus_TCP_Server_Motors.xConfirmError := TRUE; I tried also this command to STOP/RESET/START client and server (codesys side) but nothing happens : status_client := Modbus_TCP_Client.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.STOP); // .RESET & .START The answer of this function when executed is "status_client = NOT_SUPPORTED". Is it normal ? It seems that is a socket problem, but I do not understand if it is on the client or server side. I tried a modbus simulator called "ananas.exe" and the result is the same. Impossible to get a modbus client reconnection. What is different at the first client connection and at a reconnection attempt ? Thanks for your help
Last updated: 2025-03-17

Post by sking on ModbusTCP/slave ^{CODESYS Forge talk (Post)}
i can not find the solution, i have 2 modbus tcp slave and i want to know how to do when one is activated the other one is desactivated. that means when i run the project, with a bouton click on my web visu i can choose wich modbus slave i want to activate. can someone have a solution plz ? thank you :)
Last updated: 2025-04-01

Sort by relevance or date