You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Connect to a tcp slave modbus device with a non infinite read timeout
TCPClient (to test I connect to a tcp terminal, so that is no response to
queries)
2. Send a readHoldingRegister message
3. Wait timeout
What is the expected output? What do you see instead?
Expected: Exception - read timeout.
Received: Exception - Operation Invalid. Connection closed.
What version of the product are you using? On what operating system?
NModbus_net-3.5_1.11.0.0-source on Windows 7 Pro x64
Please provide any additional information below.
Looking at the code, I discovered that the retry mechanism catches the
exception timeout and repeat the operation, but on the second attempt the TCP
connection is closed for some reason and another exception is generated,
masking the first one.
Original issue reported on code.google.com by [email protected] on 5 Feb 2014 at 7:22
The text was updated successfully, but these errors were encountered:
I resolved closing Tcp connection and disposing the ModbusIpMaster object.
At next ping success, if you create new ModbusIpMaster object you will restore
the connection to the device
Original issue reported on code.google.com by
[email protected]
on 5 Feb 2014 at 7:22The text was updated successfully, but these errors were encountered: