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 hanpekel on Reading request counter value from modbus server in application ^{CODESYS Forge talk (Post)}
Any way I can read the value of the 'request counter' (see screenshot) in my application. Amount of client connections is easily found using ModbusTCP_Slave_Device.uiClientConnections; But for request counter it does not seem to be that simple.
Last updated: 2024-10-16

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 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 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 esave on Softmotion Light Problem: The license is missing or invalid ^{CODESYS Forge talk (Post)}
Hello everybody I want to controll a stepper driver from Leadshine (EM3E-556E). The EtherCat slave is CiA 402 compatible. Because of this I bought the Softmotion Light Package from Codesys and implemented it in my project. I rightclicked the EtherCat slave and added the Softmotion Light axis. But now the error message shows: "The license is missing or invalid. The PLC runs in demo mode." What have i done wrong? I use Codesys 3.5.17. Is it possible that the stepper driver is not compatible with the Softmotion license? Thanks for all your help
Last updated: 2024-05-02

Post by jonasz on Device diagnosis ( EtherCAT IO card ) ^{CODESYS Forge talk (Post)}
Hi, I'll link to the topic not wanting to start a new one. In the application I am building, I wanted to use the diagnostics described in the CAA Device Diagnosis library. In principle, everything is ok, except for the elements related to ModbusTCP. Despite the fact that ModbusTCP is taken into account in the documentation, it is not recognised via the interfaces. FUNCTION_BLOCK NET_HW_DIAG VAR_INPUT END_VAR VAR_OUTPUT END_VAR VAR (* Referencja do struktury z danymi dla HMI ASTRAADA.*) Visu: REFERENCE TO VISU; (* Wskaźnik na mastera EtherCAT.*) pEtherCATMaster : POINTER TO IoDrvEtherCAT; (* Wskaźnik na slave EtherCAT.*) pEtherCATSlave : POINTER TO EtcSlave; (* Interfejs dla węzła w drzewie urządzeń.*) _itfNode: DED.INode; (* Ogólny interfejs magistrali. Zapewnia podstawowe informacje o magistrali polowej.*) _itfBus: DED.IBus; (* Interfejs urządzenia. Zapewnia rozszerzone informacje o urządzeniu (magistralowym).*) _itfDevice2: DED.IDevice2; (* Ogólny interfejs magistrali. Zapewnia podstawowe informacje o magistrali polowej.*) _itfStack: DED.IStack; (* Numer węzła w drzewie urządzeń.*) uiNodes: UINT; (* Operator jest rozszerzeniem normy IEC 61131-3. W czasie wykonywania operator wykonuje konwersję typu odwołania do interfejsu na inny typ. Operator zwraca wynik BOOL. Wartość TRUE oznacza, że CODESYS pomyślnie wykonał konwersję. *) xQueryResultBus: BOOL; xQueryResultDevice2: BOOL; xQueryResultStack: BOOL; (* Struktura danych dotyczących węzłów w drzewie urządzeń.*) NetHwDiag: NW_HW_STAT; ModbusTcpClientDeviceInfo: IoDrvModbusTCP.DED.DEVICE_INFO; ModbusTcpClientDeviceState: IoDrvModbusTCP.DED.DEVICE_STATE; ModbusTcpDeviceInfo: IoDrvModbusTCP.DED.DEVICE_INFO; ModbusTcpDeviceState: IoDrvModbusTCP.DED.DEVICE_STATE; END_VAR (* Pobranie wskaźników dla pierwszego mastera i pierwszego slave w sieci EtherCAT.*) pEtherCATMaster := g_pFirstMaster; pEtherCATSlave := pEtherCATMaster^.FirstSlave; (* Diagnostyka sieci EtherCAT.*) pEtherCATMaster := g_pFirstMaster; pEtherCATSlave := pEtherCATMaster^.FirstSlave; NetHwDiag.xConfigFinished := pEtherCATMaster^.xConfigFinished; NetHwDiag.xDistributedClockInSync := pEtherCATMaster^.xDistributedClockInSync; NetHwDiag.xError := pEtherCATMaster^.xError; NetHwDiag.xSyncInWindow := pEtherCATMaster^.xSyncInWindow; NetHwDiag.sLastMessage := pEtherCATMaster^.LastMessage; NetHwDiag.LastError := pEtherCATMaster^.LastError; (* Diagnostyka drzewa urządzeń.*) uiNodes := 0; _itfNode := DED.GetRoot(); REPEAT NetHwDiag.asDeviceName[uiNodes] := DED.GetDeviceNameString(itfNode := _itfNode); xQueryResultBus := __QUERYINTERFACE(_itfNode,_itfBus); IF xQueryResultBus THEN _itfBus.GetBusInfo(buiInfo := NetHwDiag.aBusInfo[uiNodes]); NetHwDiag.aBusState[uiNodes] := _itfBus.GetBusState(); END_IF xQueryResultDevice2 := __QUERYINTERFACE(_itfNode,_itfDevice2); IF xQueryResultDevice2 THEN _itfDevice2.GetDeviceInfo(deiInfo := NetHwDiag.aDeviceInfo[uiNodes]); NetHwDiag.aDeviceState[uiNodes] := _itfDevice2.GetDeviceState(); IF pEtherCATSlave <>0 THEN pEtherCATSlave^(); IF pEtherCATSlave^.SlaveAddr = NetHwDiag.aDeviceInfo[uiNodes].idSystem THEN NetHwDiag.aAlStatus[uiNodes] := pEtherCATSlave^.ALStatus; pEtherCATSlave := pEtherCATSlave^.NextInstance; END_IF END_IF ELSE xQueryResultStack := __QUERYINTERFACE(_itfNode,_itfStack); IF xQueryResultStack THEN _itfStack.GetDeviceInfo(deiInfo := NetHwDiag.aDeviceInfo[uiNodes]); NetHwDiag.aDeviceState[uiNodes] := _itfStack.GetDeviceState(); END_IF END_IF uiNodes := uiNodes + 1; _itfNode := DED.GetNextNode(_itfNode); UNTIL _itfNode = 0 END_REPEAT (* Diagnostyka Modbus.*) Modbus_TCP_Client.GetDeviceInfo(deiInfo := ModbusTcpClientDeviceInfo); ModbusTcpClientDeviceState := Modbus_TCP_Client.GetDeviceState(); PAC_3200T.GetDeviceInfo(deiInfo := ModbusTcpDeviceInfo); ModbusTcpDeviceState := PAC_3200T.GetDeviceState(); Of course, you can take the easy way out and refer directly to the devices, but I wanted a reusable component. Any constructive help is very welcome Best regards Jonasz
Last updated: 2025-07-15

Post by ph0010421 on TCP/IP client ^{CODESYS Forge talk (Post)}
Hello TCIS_Send needs to be longer than 4 bytes because idata is 28 bytes long. There may be other ways, but I would make a UNION with string/array of bytes. Write your STRING into the AsString part then copy the AsBytes part into TCIS_Send (Elements [3] to [30]) then 252 would be in [31] (I've assumed the idata is always the same length)
Last updated: 2023-12-19

Post by andreag0 on How to access to variable value through symbolic string name ^{CODESYS Forge talk (Post)}
Hello, anyone know how to get valiable value using a symbolic string name? For example: - send string to runtime using TCP/IP contains "GVL.TestINT" and get back the value. I need function that will translate the string to symbolic variable. Thank you. Andrea
Last updated: 2024-06-13

Post by nano on Cant login to Rpi4 but can see it in codesys communications settings. ^{CODESYS Forge talk (Post)}
which ports in detail are configured. the search of the rts works via broadcast-messages, programming with tcp-port on p2p-connection woth port-hopping, handled by runtime after siccesfully handshake. look at this entry on forge https://forge.codesys.com/forge/talk/Runtime/thread/4078a2ed28/
Last updated: 2024-06-23

Post by simotion on Variable indicating axis pending gearing or camming ^{CODESYS Forge talk (Post)}
Is there a variable indicating that a gearing or camming operation is pending? For instance MC_Gearin has beeen triggered, but starting point of master axis to start the sychronisation movement is not reached yet, so the slave axis is just waiting for this. I should be able to differ between a pending and active gearing or camming
Last updated: 2023-11-28

Post by charleskentyfz on (no subject) ^{CODESYS Forge talk (Post)}
I have created an EtherCAT slave code and fixed two slaves (IDs written in the 0xF050 object dictionary). The module IDs are 0x1 and 0x101, respectively. It can be scanned normally in TwinCAT, but when scanning in CODESYS, it reports an error. Why is this happening？text in the second pic means 'device cannot be found in repository'
Last updated: 2024-07-07

Post by mrrobot on No source code available for this object ^{CODESYS Forge talk (Post)}
Hello, I have this strange error while I am adding an axis to my slave: "No source code available for this object because it is in the compiled library 'sm3_drive_etc_ds402_cyclic' ..... I looked on google/chatgpt but i cannot find a solution for this issue Any help is welcome ! Thanks in advance Mrrobot
Last updated: 2024-07-15

Post by mrrobot on No source code available for this object ^{CODESYS Forge talk (Post)}
Hello, I have this strange error while I am adding an axis to my slave: "No source code available for this object because it is in the compiled library 'sm3_drive_etc_ds402_cyclic' ..... I looked on google/chatgpt but i cannot find a solution for this issue Any help is welcome ! Thanks in advance Mrrobot
Last updated: 2024-07-15

Post by atone on Change IO-Link Device Interface connected to a Profinet-Slave at Runtime ^{CODESYS Forge talk (Post)}
OK, I figured out that I can simply define all the sensors as 16 bytes IN/OUT, even if they are not all used. EDIT: The negative effect is that each bit is taken into account as an I/O for the license, even if not used.
Last updated: 2025-04-28

Sort by relevance or date