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.

CR1000 GPRS communication dies at Server crash


bep Jan 27, 2011 11:22 AM

Dear Campbell support and experienced users,

we communicate with many CR1000 loggers worldwide through the GPRS option. That means the Loggers establish a connection to our Loggernet 4.1 server through SC105, Wavecom Fastrack GPRS modem and Mobile phone network. Of course the modems have private dynamic IPs, so we can't initiate communication from home, but rely on incoming communication from the logger.

The current problem:
It has happened several times in the last weeks, that they just went offline after our server crashed (for unknown reason). We are waiting for the stations to come back online since days and last time it has only helped to give the logger a reset on site.

Can anybody explain why the stations don't come back online after a server crash?

Config details:
Loggernet Admin 4.1
Loggers CR1000 with OS19 or OS20

Best regards, Ben


Sam Jan 27, 2011 05:57 PM

bep,

Next time this happens, open your Comms$.log. Start at the bottom and search up. Look for "IPPort","F" and see if it corresponds to LoggerNet crashing or being brought back online.

If so, then LoggerNet is probably having trouble opening the IP port used for callback. Try a) restarting LoggerNet again, or b) try disabling "Call-back Enabled", hitting apply, and re-enabling it.

I do not know for sure if this will solve your issue. Just some thoughts.


Sam Jan 27, 2011 06:10 PM

bep,

Can you post your program? Re-reading your post makes me think that it is using the TCPOpen instruction and that TCPOpen is only being called at compile time.

Thanks,
Sam


aps Jan 27, 2011 10:32 PM

IF Sams suggestion regarding Loggernet does not work when you look at the coms log with the Logtool, please report what if it says a message like "IPPort_1","S","waiting for connection on port 1234", or if using a PakbusTCPServer, "waiting for connections",1234. If not are there error messages.

If all looks OK we would like you to confirm whether you are using using TCPOpen in your program as he requests OR if not whether you are using the automatic call-back where in the Net Service screen of the Device Configuration Program you put the Loggernet address as a Pakbus TCP/Client address?


bep Jan 28, 2011 10:01 AM

Hi all,

thanks for your suggestions. I tried out all of them, but the stations stay offline.

@ Sam:
- PPPOpen is called every couple minutes in a slow sequence of our program. TCPOpen is never called in our program.
- My CommLog shows frequently (I guess whenever Loggernet tries to connect to the Logger):
"IPPort","F","Forced to keep off-line","opening not permitted" and
"IPPort","S","waiting for connection on port 1234"

@ aps:
- We are not using TCPOpen, but we do as you say: Enter the Loggernet-IP in the Net Service Screen of Device ConfigUtility as "PakBus/TCP Client".

I would appreciate further help.

Please note, that some of the affected stations have been online for months and nothing has been changed in the stations when the Loggernet server crashed.

Best regards, Ben


aps Jan 28, 2011 01:54 PM

The IPPort, F message is most likely the result of you having a schedule running to collect data and it fails because there is no connection open for the call to go via.

The "S" message would indicate Loggernet is waiting for an IP connection OK.

Can you please check that after the PC crash its firewall settings for incoming traffic still allow the connections to come through, plus there are still holes and routing information in any router device you are using please.

There should be no need for the PPPOpen in your program as this is implicit in the auto-connection mode you have set in the Net Service screen.


bep Feb 4, 2011 09:49 AM

Hi all,

I appreciate your continued support.
Here come some new experiences:
1) restarting the Loggernet Service has helped sometimes to get some stations back online. This happened several times in the past days with stations in completely different countries and using different mobile phone providers.
2) The Loggernet service itself has no impact on our port forwarding or firewall settings.

I can send you LogFiles of the respective stations communication by email, if you wish. Status tables of the stations are also available from the respective last time of communications.

Best regards, Ben


aps Feb 4, 2011 02:31 PM

OK please send me the logs. My email is given is several recent posts. Please include the status files.

* Last updated by: aps on 2/4/2011 @ 7:31 AM *


bep Feb 4, 2011 03:26 PM

Logs have just been sent

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