Cumulus Support

Hello,

Posting this message for my father running cumulus 1.9.4 build 1097. Weather station Vantage Pro 2 IP

Program has been flawless for him (and me) for past six months.

Usually he turns the computer off at night and back on in the morning and it downloads the nightly data just fine.

My father left for three days, made sure he turned cumulus off and then the computer before leaving and when he came back everything was flatlined (graphs, values). It looks like it only downloaded rain cumulated and a wind gust. Oh and it did currently download last nights data as if their wasn't a problem..

I took some screenshots you can find here:

http://195.154.91.108/sdfqdsjioiazefpoiq/

Private server, his values are on the right mine are on the left in the screenshots, we live pretty close so values should be very approximately the same.

I have included diags folder.

Would you have any ideas why this happened and how to prevent it?

Regards,

Tim

When Cumulus started up at 18:13 on the 4th, it asked the Davis DLL to download the data that it needed to fill in the gap from when it closed down, and the DLL said that there was no archive data available, hence there is a gap in the Cumulus data.

04/11/2014 18:13:12.655 : VP2: Downloading history from 30/10/2014 08:05:00
04/11/2014 18:13:12.655 : y=2014 m=10 d=30 h=8 m=5
04/11/2014 18:13:26.225 : VP2: DownloadData_V = -32701
04/11/2014 18:13:26.225 : VP2: GetNumberOfArchiveRecords_V = -1
04/11/2014 18:13:26.225 : VP2: No history records to process

Looking at the data from the later successful download, it's clear that the logger interval is set to one minute. This gives a total logging period of just under 42 hours, less than two days. So there would not have been enough data in the logger to fill in the gap from 08:05 on the 30th to 18:13 on the 4th (a period of five and a half days, or 130 hours) even if the download had been successful. You might expect that the DLL/logger combination would at least have downloaded the last 42 hours of data, but it appears that what happens in this situation is that it just gives up and says that it doesn't have the requested data (as it only has a small part of the data available). There would still have been a significant gap in the Cumulus data.

The station's logger interval needs to be set so that the capacity of the logger will fully cover any periods when Cumulus isn't running.

Thank you Steve for quick response, I suspected we had filled the datalogger with too much data. So if he ever leaves again essentially we should calculate how long and at what intervals it logs by setting this through weatherlink ip AND in cumulus am I correct?

Tim

Yes, but be aware that changing the logger interval clears the logger memory.

Ok perfect, thank you again Steve. Great Work