Post by imdatatas on Remote to PLC device in City-B from City-A ^{CODESYS Forge talk (Post)}
Hello, In an example scenario like below figure, can the developer in City-A connect to the device in City-B remotely using only "Codesys Automation Server" and "Edge Gateway" with the following structure? If no, what should be done with Automation Server for this remote connection requirement? If yes, how should it be configured for this remote connection requirement? Thank you in advance for your answers. Regards, Imdat
Last updated: 2025-02-04

Post by eschwellinger on Licensing info not available. ^{CODESYS Forge talk (Post)}
yes and no ... if you run the license server on the host (to serve licenses to the docker instances / vplcs then there is no runtime which could check the licenses on the host. Therefore you need the CODESYS WBM to activate or check the licenes or you could use in CODESYS IDE the licensemanager ( not the one for the device licenses) but you have the the IP of the license server that he know where to search for the licenses ..tool options i guess to add it, will add a screenshot later.
Last updated: 2025-10-01

Post by simone on Cannot connect to webvisu on localhost ^{CODESYS Forge talk (Post)}
As I wrote before on the title, I have difficulties to connect to see webvisu from localhost. The story: while waiting for the plc+hmi to arrive, I'm preparing the software, mainly the visual parts trough the control Win3 x64 (same version as the ide 3.5.20.10). The problem is that I can't see the webvisu with the installed webbrowser. I don't know if this is a problem, but I changed the port to 9001 (randomly "free") because 80, 8000, 8080, 8088, 3000 are all occupied by other projects (all on the Apache server). Is there something wrong with the config file? This is the url: localhost:9001/webvisu_app.htm and here the config file part "CmpWebServer". [CmpWebServer] ;The handling of startup/shutdown of the webserver: ;0->automatically start, shutdown only on shutdown of the runtime;1->automatically start, could be shutdown on demand ;2(default)->start/shutdown on demand;3->start on demand, shutdown only on shutdown of the runtime StartupType=0 ;The TCP port the webserver listens on WebServerPortNr=9001 LocalAddress=localhost ;LocalAdapterName=LAN-Connection LocalAdapterName=EthernetPCPLC ;LocalAdapterNameUnicode=L\00A\00N\00-\00C\00o\00n\00n\00e\00c\00t\00i\00o\00n\00 LocalAdapterNameUnicode=E\00t\00h\00e\00r\00n\00e\00t\00P\00C\00P\00L\00C\00 Thanks for all the help!
Last updated: 2024-07-11

Post by julianramirez on ModbusFB write update ^{CODESYS Forge talk (Post)}
Hello everyone, I am testing the ModbusFB library tcp server and so far I am able to create holding registers successfully, however, I am trying to identify after each write which registers got updated (i.e. function code, write value). I can even see the var udiNumWriteRequests, which increases with every write. I noticed that there is logging with the LogStatusInfo method. After I call it I am able to read in the console stuff that I want. Nevertheless, this is only available at the logs and is not easy to decode because it consists on several messages, I would like to know if there is a way for me to retrieve this information from the function itself with pointers or if there is any way to copy the logs messages (assuming that I can filter them with the LoggingOptions to only show what I need) inside the runtime code and not in the console. Thanks for your help :)
Last updated: 2024-09-16

Post by george32 on TCP Server ^{CODESYS Forge talk (Post)}
Thank you for your advice Rinie, I have tried to follow this example but found one problem.When I disconnect with Hercules the system does not acknowledge the lost of its connection this could result in critical errors. Because of this error I am trying to implement the Syssocket library. With this library I am having a problem which I could not solve. I have the following code: ip_adres : STRING :='0.0.0.0'; port : WORD := 5000; iStep : INT := 1; // Socket information Socket_handler : SysSocket_Interfaces.RTS_IEC_HANDLE; Socket_handler_result : SysSocket_Interfaces.RTS_IEC_RESULT; Socket_adress : SysSocket_Interfaces.SOCKADDRESS; Addres_Convert : SysSocket_Implementation.RTS_IEC_RESULT; // Bind information Bind_handler : SysSocket_Interfaces.RTS_IEC_RESULT; // Listener Information Listener_handler : SysSocket_Interfaces.RTS_IEC_RESULT; Addres_Convert := SysSocket_Implementation.SysSockInetAddr(szIPAddress:= ip_adres,pInAddr:= ADR(Socket_adress.sin_addr)); Socket_adress.sin_family:= SysSocket_Interfaces.SOCKET_AF_INET; Socket_adress.sin_port := SysSocket_Implementation.SysSockHtons(usHost:= port); CASE iStep OF 1: // Create Socket Socket_handler :=SysSockCreate( iAddressFamily :=SysSocket_Interfaces.SOCKET_AF_INET, diType:=SysSocket_Interfaces.SOCKET_STREAM, diProtocol:=SysSocket_Interfaces.SOCKET_IPPROTO_TCP, pResult:=ADR(Socket_handler_result)); IF Socket_handler = SysSocket_Interfaces.RTS_INVALID_HANDLE THEN iStep := 1; ELSE iStep := 2; END_IF 2: Bind_handler := SysSocket_Implementation.SysSockBind( hSocket:=Socket_handler, pSockAddr :=ADR(Socket_adress), diSockAddrSize:=SIZEOF(Socket_adress) ); 3: Listener_handler := SysSocket_Implementation.SysSockListen( hSocket :=Socket_handler, diMaxConnections :=1); END_CASE When I am trying to get this working, the SysSockBind function gives a value of 16#207 which means adress already in use. I find this weird because of the IP-adress of 0.0.0.0. I think I am converting the Ip-adress in the wrong way, but the code does not give a error arround this. So therefore I cannot find the solution to this problem. I hope someone could help me with this problem. Thanks in advance George
Last updated: 2025-02-20

Post by bossjosh21 on Codesys Modbus RTU (Modbus_Slave_Com_Port Not Running) ^{CODESYS Forge talk (Post)}
Can someone help me about my problem of my Modbus_Slave_Com_Port Not Running. I am using RevPiConnect 4 and I connected my actuator to the RS485 of my RevPI.
Last updated: 2023-12-05

Post by dantheman on Connecting to SoftPLC Only Works By Turning Off Modbus Ethernet Port ^{CODESYS Forge talk (Post)}
It's all good btw, learned that the runtime doesn't isolate the networks that are involved so changing the ethernet subnets away from the Wi-Fi's subnet was all I needed (maybe some config file changes helped, can't say for certain)
Last updated: 2024-08-08

Post by esmith on OPTO22 Groov Epic PR2 Modbus Comms Dropping out every 2 hours and 4 Mins ^{CODESYS Forge talk (Post)}
I think I am having a similar issue. Have you found out what was causing this problem?
Last updated: 2024-09-10

Post by ben1 on How to write multiple coils (Modbus FC15) ^{CODESYS Forge talk (Post)}
Yeah that is odd - sometimes you have to do what you have to do unfortunately. Have you tried sending consecutive bits in the word instead - ie. instead of [0].0. [1].0, [2].0 etc, send [0].0,[0].1, [0].2 etc. ?
Last updated: 2024-11-17

Post by ph0010421 on Dynamically enabling/disabling Modbus slave devices in runtime (performance issue with timeouts) ^{CODESYS Forge talk (Post)}
Hello If you uncheck 'Auto restart Communication', it will try once and never again. You can manually reset the slave if needed : Slave.xReset (or something similar) Or I have a ModbusRTU library if you want to try it.
Last updated: 2025-08-12

Post by marekxc on Little endian to Float from Modbus RTU ^{CODESYS Forge talk (Post)}
Maybe try going back to step one and: Var Reg1: WORD; Reg2: WORD; Reg12: DWORD; Value: REAL; end_var // program Reg1:= 4096; Reg2:= 14884; Reg12:= (reg2 * 65536) + reg1; Value:= DWORD_TO_REAL(Reg12);
Last updated: 2023-12-28

Post by dim54 on MBChannel ^{CODESYS Forge talk (Post)}
Hello! I am interested in the Modbus Slave channel parameter uiReadLength to use in the ST-program (see picture). How to read the value of uiReadLength in a ST-program? Only Edwin the Great and Terrible can answer this question.
Last updated: 2024-01-22

Post by timvh on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
I'm not sure, but maybe you have to configure the 750-652 first with the WAGO-IO-CHECK software to set it in RS485 mode?
Last updated: 2024-02-27

Post by dawidr on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Did you manage to solve the problem with time out? I got the same issue and I've no idea what I'm doing wrong.
Last updated: 2024-04-07

Post by dawidr on Timeout Error in Modbus Communication with WAGO PFC200 and iEM2050 Meter using 750-652 Module ^{CODESYS Forge talk (Post)}
Did you manage to solve the problem with time out? I got the same issue and I've no idea what I'm doing wrong.
Last updated: 2024-04-07

Post by marcolim on Slow modbus digital input response ^{CODESYS Forge talk (Post)}
Hi francoinf, I've the similar problem and similar configuration. I did with an Arduino Board loaded by a ModbusRTUServer application on it. What I've notice is the slowly acquisition when release the digital signal (e.g. pin2) when it gets off. Anyone have suggestion?! Thanks
Last updated: 2024-04-13

Post by marcolim on Slow modbus digital input response ^{CODESYS Forge talk (Post)}
[Update]. My issue's solved, I applied the resistors in Pull-down configuration on each digital input. In thus configuration never happened "floating or delaying" acquisition on SoftPLC/Arduino Board.
Last updated: 2024-04-15

Post by timvh on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
Most likely related to the Device Diagnostics functionality. Double click on your device (PLC), go to the tab "PLC settings". Enable the advanced option "Enable diagnosis for devices". Build your application again.
Last updated: 2024-04-15

Post by mbmik on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
Thanks alot for your time and help! I quickly tested the suggestion, as it makes a lot of sense. Unfortunately the erros still appear as before. The settings was already set before, and i tried turning it off.. no effect..
Last updated: 2024-04-16

Post by hyet on IoDrvModbusTCP_Diag not defined when using MODBUS ^{CODESYS Forge talk (Post)}
Currently seeing the same issue here, with a project moved from 3.5.19. Diving into it too to see if i can find the cause
Last updated: 2024-05-01

Post by guilhermeleao on How to communicate 2 pcs that are using CODESYS ^{CODESYS Forge talk (Post)}
I need to connect 2 computers on the same network that are running codesys, so that they can receive and change variable values from each other. This connection must preferably be made using Modbus.
Last updated: 2024-05-06

Post by zer0g on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, I have the same problem as the guys above. Any solution or hint in the right direction is appreciated. Codesys version 3.5.19.2, Lib version: 4.4.0.0. Thank you!
Last updated: 2024-05-29

Post by salvatorethomas on Port instantiation of serial interface in WAGO PLC using Modb_L05.lib in CoDeSys v2.3 ^{CODESYS Forge talk (Post)}
Hi — good description of the problem. A few suggestions / questions that might help narrow this down: Since your first serial port (COM2) works fine but the second (COM4 + MODBUS_EXT_MASTER) never opens, check whether the two ports are truly independent — some WAGO modules share internal resources, so COM4 might conflict with other functions or modules. Make sure that the physical wiring and module configuration for the second port (baud rate, flow control, RS-485 vs RS-422, etc.) exactly match what the library expects — a mismatch in flow control or wiring could prevent port opening even if the LED signals seem OK. Try using a plain SERIAL_INTERFACE on COM4 first (like you did for COM2) without Modbus logic — if that opens, you know the hardware + port config is fine, so the issue is more likely with modb_L05.lib. If the port opens but Modbus still fails, enable debug/logging (if available) to inspect whether the port opening fails or the subsequent Modbus negotiation fails. If you like — I can share a minimal example project I used with WAGO + COM4 + Modbus that worked; you could adapt that to test your setup. Wacky Flip
Last updated: 2025-12-01

Post by risele on Modbus connection via Qronox PCD3 M6893 ^{CODESYS Forge talk (Post)}
First, if you don't need to change conversion rules in runtime, take a look at "Unit conversion" module (Application -> add object -> UnitConversion). You can specify there biderectional conversion with different units, limits and so on. Second, since MODBUS don't have "real" types but only general 16-bit registers and Real is 32-bit, generally you need a byte-was conversion Real <> two Words. Note, that depending on the devices on both sides, there are two options: Real-> Word1, Word2 or Real-> Word2, Word1, where Word1 is minor register in Modbus register pair and Word2 is major. You can use simple union: TYPE u_Real : UNION rVal:REAL; wVal:ARRAY[0..1] OF WORD; dwVAL:DWORD; //same as previous, may be easier to specify the MB register END_UNION END_TYPE and convert it as following: VAR myUnion:u_Real; rValue_TO_SEND:REAL; rValue_TO_GET:REAL; END_VAR myUnion.rVal:=rValue_TO_SEND; rValue_TO_GET:=myUnion.rVal; Note, that WORD-order should be properly set in MODBUS registers, otherwise you will get strange values. This tool is helpful: https://www.scadacore.com/tools/programming-calculators/online-hex-converter/ Alternative, you can use functions as REAL_TO_DW and DW_TO_REAL from OSCAT_BASIC, for example.
Last updated: 2026-02-19

Post by janderson on OPC UA Server limitations, large array crashes runtime ^{CODESYS Forge talk (Post)}
when using an array of structs, the runtime crashes. but when using an array of LREALS, it'll do 100k at least
Last updated: 2023-08-23

Sort by relevance or date