Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

IP connections sometimes getting stuck without making errors on COMM HISTORY


ndonso Nov 2, 2016 02:36 PM

Dear,

I have IP connections (3G or GPRS with IP public and dynamic using dyndns) to 3 types of datalogger (CR1000, CR10X and CR300) downloading data from these stations sometimes getting stuck without making errors on COMM HISTORY and to reset the connection just click on Collectnow (STATUS MONITOR).

LoggerNet configuration of one of these stations is:

Extra Time response: 10s
Max online time: 0h 0m 0s
Base Date: 01/01/1990
Normal Schedule: 0d 0h 30m 0s 0ms
Primary Retry Count: 3
Secondary Retry Schedule: 1d 0h 0m 0s 0 ms

If someone could give me any advice to prevent paralyzes the connection would appreciate.

regards


DaneMedhurst Jan 23, 2024 05:30 PM

Some possible causes and solutions for the connection paralyzes are:


The IP address of the datalogger changes due to the dynamic DNS service. This might cause the LoggerNet server to lose track of the datalogger and fail to connect suika game. You can try to use a static IP address for your datalogger or update the DNS settings in the LoggerNet server.


The network signal or bandwidth is weak or unstable due to the 3G or GPRS connection. This might cause the connection to drop or timeout. You can try to use a more reliable network connection, such as Ethernet or Wi-Fi, or increase the response time and retry count settings in the LoggerNet server.


The datalogger is busy or overloaded with other tasks or programs. This might cause the datalogger to ignore or delay the connection requests from the LoggerNet server. You can try to reduce the load on the datalogger by optimizing the program, reducing the scan rate, or disabling unnecessary functions.

Log in or register to post/reply in the forum.