Scott Mongrain

Yes. Connections (and thus, clients) are cheap; abandon them at the earliest sign of trouble. That means using Try...Catch where you should toss the connection in the Catch block as basically the only action (don't try to resolve anything, it's useless and more effort than it's worth), abandoning it after any latency longer than you'd like, also after a malformed response, etc. Basically just constantly remake clients/connections (they're more or less one and the same) and everything works perfectly....

Somehow managed to get myself logged out prior to posting those two replies, and didn't notice. The gist of the problem was "helicopter parenting" the connection, and mistakes in the interpretation of signed/unsigned integers. I also started using the FC03, 04, and 16 functions.

Hello! I am trying to use EasyModbusTCP v5.0 in my (fairly ambitious) project to connect to multiple slave devices and read/write values from/to them in a control loop as a Modbus master device. I'm writing the code in VisualBasic.NET. At present, I'm using your EasyModbusTCP Server Simulator v5.0 as my "slave device" under test before moving on to the real thing. Problem At the moment, I cannot get it to run for more than about 15-90 seconds continuously without throwing exceptions: Exception 1:...