Dears, is it possible to increase the waiting time before the failed connection alert comes out?
I have remote loggers connected IP and then WIFI whose connection is made only after 2 or 3 attempts.
Every time a minute passes and I have to repeat the request.
The device configuration utility was originally designed to make the act of connecting to the selected device as simple as possible and, originally, we used the assumption that the link to the datalogger would be local (i.e. not a complex remote link type). This assumption allowed us to eliminate many of the settings required by LoggerNet which does support the more complex link types. Since then, devconfig was expanded to support TCP type links but the assumption of locality remains.
Another think to note is that both devconfig and LoggerNet depend upon the TCP/IP stack on the host computer to make and maintain TCP connections. I don't believe that there is anything in the windows sockets API that allows us to control the amount of time that the windows kernel will wait or the number of SYNC IP messages will be sent before the kernel times out the TCP socket. This may be adjustable in a global sense on the host computer (generally by tuning registry parameters) but it is not something that processes are allowed to change for their own connections. If the problem that you are encountering is due to a failed TCP connection, there is not much that can be done.