TCP timeout

[Chris_12345]

A TCP reference that I have created (using TCP Open Connection) becomes non-functional after 300 seconds of inactivity.  The timeout input to the TCP Open Connection subVI is unrelated to this 300 seconds.

Is there someplace where the 300 seconds can be adjusted? I have been unable to find where it is.

Thanks for your help,

Chris

[tst]

I can't say I've heard of this, but it would probably be part of the OS, since that's responsible for handling the TCP communication. In Windows, you might have a registry setting for this.

I prefer writing a sort of automatic "ping" into my code (where applicable) so that if nothing was done for N seconds, a message is sent just to make sure that the connection is still there. Then, I have a running counter for timeout errors which is reset whenever any message is received. If the counter reaches a certain limit, it means that no message was received for X time and we would want to do something about it. The main reason is that any number of things can cause the connection to break (like someone accidentally pulling out a cable) and you would like to know about as soon as possible.

[Lorielle P]

Hello Chris!  Thanks for posting.

tst is correct in that this may be an Operating System issue.  This KB explains TCP time-out issues and also contains some helpful TCP links.  If you are getting other error codes or have other questions, please post back.