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.

FTP data pull being interrupted


BenEvans Nov 14, 2012 02:57 PM

We're running a number of CR1000s with FasTrack modems in the UK. We have been pulling data from the stations via Loggernet (connected by IP) for a couple of months and it performs well (if frustratingly slowly). We can access files on the loggers by FTP and can download small files without problems. Some of our files are about 500kb and take a while to download over Loggernet. When we attempt to pull these files over FTP the process runs for a few minutes then stops and gives the error message 'remote server closed the connection'. I've spoken to Campbell here in the UK and they say there is no hardware reason for this, but I was wondering whether anyone has any experience of a similar problem or suggestions as to why FTP might not be working properly?

Many thanks

Ben


thinkitcodeit Nov 14, 2012 03:12 PM

Hi Ben,

Can you detail how your are pulling these files over FTP?

Thanks

Simon


BenEvans Nov 14, 2012 03:21 PM

I personally am using Ipswitch WS_FTP12 as my client on Windows and am just dragging files across to the appropriate folder on my machine. Our computer officer is also trying on a Linux machine and is trying to write a cron script to automate the download.

The files are .dat files written by the logger at regular intervals.


aps Nov 16, 2012 09:09 AM

I checked into this and there was a timeout of 120 seconds for the ftp server in logger operating systems prior to version 24.

If you upgrade the operating system to the latest (now 25) from www.campbellsci.com/downloads, the will find timeout on a connection has been removed although there are still similar timeouts on periods of inactivity.


BenEvans Nov 16, 2012 09:24 AM

Thanks. We're running OS 24, is that timeout up to 24 or up to and including 24? It sounds like a probable cause if it is a feature of OS24.


aps Nov 16, 2012 10:07 AM

The timeout was removed in OS24 onwards, so you should have that fix.

Can you look at the status table of the logger and see if the logger has incremented the watchdog counter (non-zero) and if the low battery count is non-zero too.

OS25 had other fixes to TCP/IP functionality to solve problems that could cause the logger to reset if it was using a bad TCP/IP connection.


BenEvans Nov 16, 2012 11:27 AM

The watchdog counter, 12V low and 5V low counters are all zero still.

Are there any other diagnostics that might help?


aps Nov 16, 2012 01:26 PM

If you have access to the logger directly you could collect some low level log information whilst trying to collect data via ftp. Is this possible?

One other question for you - what exact model of modem are you using?

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