I have a CR1000 connected to a satellite internet modem via a NL115. I use this setup to remotely connect to and collect data from that CR1000 via Loggernet. This system has worked flawlessly for a couple of years. Recently, something happened with the system whereby I can no longer connect to the logger in Loggernet. I can successfully ping the logger on the IP address:port that I have it assigned to but get no further than that. I can successfully remotely connect to other TCP/IP devices that are connected to the same ethernet switch that the NL115 is connected to.
I do have periodic, limited, remote connection to this CR1000 via an iridium connection on the CS/IO port.
Can anyone enlighten me on any specific settings within the logger that I could try to manipulate to "force" or open up TCP/IP access other than just allowing for the ping responses I get back?
Thank you in advance!
Enabling and disabling the various IP functionalities of the dataloger are done through the Network Services group of settings on the datalogger.
I imagine nobody has changed these settings on the logger since it was set up.
When you are able to connect, I suggest looking at the CommsMemFree values in the Status table. It is a bit cryptic to understand so write them down. They indicate the number of memory buffers of various sizes available to the logger, see section 10.4.3 of the CR1000 manual. IP communications for downloading data use the medium and large buffers. Some older operating system versions had bugs which did not release buffers from IP connections. Over a course of time, often months, no buffers would be available for TCP connections.
If the buffer counts are low in CommsMemFree, contact technical support for assistance.
JDavis - Thanks for the response! This particular logger does indeed have an older OS on it and I need to upgrade it the next time I am onsite. Yes, you are correct that no one has changed the network services group of settings.
I will have a look at the CommsMemFree values as you suggest. Do you know off hand (maybe this is in the 10.4.3 section - I will look. If the buffers can be reset via the status/settings table in pakbus graph, numeric display or other?
If CommsMemFree is run out, it takes a program recompile to recover(usually from power cycle).