Hello Fraziersedge, the solution of Codesys might be to update your codesys to the lastest version but it was not possible for us. In our Codesys V3.5 SP9 patch 8 I was able to fix this bug. I change my ModbusTCP slave component version or one of the sub component version (ex: SysSocket). Look at the picture in attachement that's the receipe that have work for us. When I got the bug my version of ModbusTCP slave was 3.5.5.0 with SysSocket at 3.5.6.0 and I change to ModbusTCP slave 3.5.14.0 with same...
Hello, we have a customer that have a device that pool our ModbusServer (codesys component from library ModbusTCP Slave). When a device connect we saw the byClientConnections variable to augment by 1. If the device is connect and we lost the network connection the byClientConnections did not drop and when the customer reconnect the byClientConnections augment to 2. When we reach 16, if the connection is lost the server became unchreacheble . If we toggle TRUE/FALSE the xEnable or xReset variable...