Hello, I hope you are doing well,
I am having a problem when trying to connect to the CR1000X data logger using a cellular modem.
The station is located in a remote area so we used a cellular modem that is connected to the data logger using the Ethernet port. We use a SIM card with a dynamic IP address and in our office we have a public static IP address, which has been defined in the configuration of the logger. This IP address, associated with a specific port, is routed to the Loggernet PC through our own firewall.
The station can be connected from time to time but the connection is not stable and I often get this type of logs:
************************************************************************************
Failure: 21/04/2023 18:06:00.232
Forced to keep off-line","opening not permitted
Failure: 21/04/2023 18:06:00.233
delivery failure received","timed out or resource error
Failure: 21/04/2023 18:08:00.221
delivery failure received","timed out or resource error
Failure: 21/04/2023 18:08:00.221
Forced to keep off-line","opening not permitted
Failure: 21/04/2023 18:10:00.233
transaction failure","unreachable destination","table poll - Min1Table
Failure: 21/04/2023 18:10:00.233
transaction failure","unreachable destination","table poll - Min1Table_Debug
Failure: 21/04/2023 18:10:00.233
transaction failure","unreachable destination","table poll - Sec1Table
Failure: 21/04/2023 18:10:00.233
delivery failure received","timed out or resource error
Failure: 21/04/2023 18:10:00.233
Forced to keep off-line","opening not permitted
Failure: 21/04/2023 18:25:04.005
transaction failure","unreachable destination","check/set clock
Failure: 21/04/2023 18:25:04.005
delivery failure received","timed out or resource error
Failure: 21/04/2023 18:25:04.005
Forced to keep off-line","opening not permitted
Failure: 21/04/2023 18:06:00.232
Forced to keep off-line","opening not permitted
Failure: 21/04/2023 18:08:00.221
Forced to keep off-line","opening not permitted
Failure: 21/04/2023 18:10:00.233
Forced to keep off-line","opening not permitted
Failure: 21/04/2023 18:25:04.005
Forced to keep off-line","opening not permitted
************************************************************************************
Or this logs:
************************************************************************************
Failure: 21/04/2023 18:44:44.259
delivery failure received","timed out or resource error
Failure: 21/04/2023 18:44:44.538
delivery failure received","timed out or resource error
Failure: 21/04/2023 18:44:45.558
delivery failure received","timed out or resource error
Failure: 21/04/2023 18:44:46.564
delivery failure received","timed out or resource error
Failure: 21/04/2023 18:45:35.632
unexpected socket close
Failure: 21/04/2023 18:45:46.412
unexpected socket close
Failure: 21/04/2023 18:45:59.388
unexpected socket close
Failure: 21/04/2023 18:46:18.679
transaction failure","unreachable destination","check/set clock
Failure: 21/04/2023 18:46:18.679
transaction failure","unreachable destination","table poll - Inspection_Control
Failure: 21/04/2023 18:46:18.679
transaction failure","unreachable destination","table poll - Min10Avg
Failure: 21/04/2023 18:46:18.680
transaction failure","unreachable destination","table poll - MinAvg
Failure: 21/04/2023 18:46:18.680
unexpected socket close
Failure: 21/04/2023 18:45:35.632
unexpected socket close
Failure: 21/04/2023 18:45:46.412
unexpected socket close
Failure: 21/04/2023 18:45:59.388
unexpected socket close
Failure: 21/04/2023 18:46:18.680
unexpected socket close
************************************************************************************
I would be very grateful if you could possibly assist in resolving this issue.
Thank you very much.
Mounir
Turn PPP ON and OFF every hour (58 minutes ON and 2 minutes OFF) and during the 2 minutes with PPP OFF turn the modem OFF for a lot of seconds and turn ON again. It's an attempt to understand.
Smile
It looks like your configuration is reliant upon the datalogger (operating within a private network) making a connection to loggernet where loggernet's address is public. In this configuration, LoggerNet has to rely upon the datalogger having made the TCP connection before it can do anything on that link. LoggerNet in this context cannot make its own outgoing configuration. The messages that you are seeing are what happens when LoggerNet has a need to use the link (such as scheduled polling) but the datalogger has not made the link at that time. Probably the easiest thing to do is to set the "PakBus Always Open" flag for the PakBus port object in the setup screen as this will configure loggernet to hold onto the datalogger's TCP connection when it would otherwise hang it up.
Aplogies in advance if I'm not helpful as I'm not proficient in all the ways cellular modems can be setup to communicate but I do have several dataloggers with modems operating in my system. I have recently connected many of my modems to Campbell Scientific's Konect PakBus Router (https://www.campbellsci.com/start/pbrouter). I have LoggerNet setup to receive call-backs so that the remote sites can power up their modems when they are ready to send data and make a call-back to LoggerNet to retrieve the data. Loggernet always has a connected open with the PBRouter and the dataloggers make the connections when they need to.
It seems that your setup depends on the datalogger, operating within a private network, establishing a connection to loggernet, where loggernet's address is public. In this configuration, LoggerNet needs to wait for the datalogger to initiate the TCP connection before it can perform any actions on that link.
This post is under review.
This post is under review.