Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
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 the byClientConnections did not reset to 0. The customer told us that after 1 month he was unable to reach our server. I reproduce a similar problem by connecting the ModbusServer with qModMaster, query the server, disonnect the network cable for 20 seconds, reconnect the cable , disconnect and reconnect.
We would like to know if there is a way to reset the server.
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 the byClientConnections did not reset to 0. The customer told us that after 1 month he was unable to reach our server. I reproduce a similar problem by connecting the ModbusServer with qModMaster, query the server, disonnect the network cable for 20 seconds, reconnect the cable , disconnect and reconnect.
We would like to know if there is a way to reset the server.
Regards,
FrΓ©dΓ©ric Ruel (OEM customer)