Cumulus Support

Hi Steve,

My rainfall graphs have started displaying dates from 01/12/19 - 03/11/2091 (+ a further date which runs off the side).

I have had a look at dayfile.txt as suggested in your reply to andyjrb on 4th March, but can see nothing wrong with the dates there. I have also been through all the other .txt logs and ini files, but can not find any obvious errors.

I am running Cumulus v.1.9.2 (build 1020) on Windows Professional XP Version 2002 SP3 and was going to update this morning to build 1031, but would rather correct this error first.

Can you point me in the right direction please?

Many thanks
Pauline

If you zip up the diags folder and attach it with your dayfile.txt, I'll take a look.

Thanks Steve = files attached

Pauline

You have a spurious entry in dayfile.txt for 31/12/99:
Removing it should fix the graphs.

The cause of the entry was that your system clock apparently reverted to 1/1/2000 for a short period:

13/03/2012 10:15:00.468 : Writing today.ini, LastUpdateTime = 13/03/2012 10:15:00 raindaystart = 62.2000045776367 rain counter = 62.2000007629395
13/03/2012 10:20:00.531 : Writing today.ini, LastUpdateTime = 13/03/2012 10:20:00 raindaystart = 62.2000045776367 rain counter = 62.2000007629395
01/01/2000 00:00:00.889 : Midnight rain reset, count = 62.20 time = 01/01/2000
01/01/2000 00:00:00.920 : === Day reset, today = 1
01/01/2000 00:00:00.920 : === Day reset for 31/12/1999
13/03/2012 10:23:55.734 : Raintotal = 62.2000007629395 Raindaystart = 62.2000045776367
13/03/2012 10:23:55.734 : Rainyesterday (calibrated) set to -3.814697265625E-6
13/03/2012 10:23:57.312 : New month starting - 1
13/03/2012 10:23:57.312 : New year starting
13/03/2012 10:23:57.312 : New rain season starting

This may have caused some other issues in your data files (because the monthly and yearly reset was done).

I also see that you have your Davis logger set to 30 minutes, and Cumulus set to 5 minutes. This means that almost every time Cumulus starts, the station sends it the entire contents of its logger:

17/03/2012 10:08:19.062 : Last update time = 9:55
17/03/2012 10:08:19.062 : Log interval = 5
17/03/2012 10:08:19.062 : After rounding = 9:55
17/03/2012 10:08:19.062 : VP2: Downloading history from 17/03/2012 09:55:00
17/03/2012 10:08:19.062 : y=2012 m=3 d=17 h=9 m=55
17/03/2012 10:09:38.859 : VP2: DownloadData_V = 2559
17/03/2012 10:09:38.859 : VP2: GetNumberOfArchiveRecords_V = 2559
17/03/2012 10:09:38.859 : VP2: Number of history records = 2559
17/03/2012 10:09:38.859 : Logger entry zero: Y = 2012, M = 1, D = 24, H = 2, M = 0
17/03/2012 10:09:38.859 : VP2: Earliest timestamp 24/01/2012 02:00:00
17/03/2012 10:09:38.859 : VP2: Earliest timestamp is earlier than requested
17/03/2012 10:09:38.859 : VP2: Find first entry after 17/03/2012 09:55:00
17/03/2012 10:09:38.859 : VP2: Checking logger entry 0 Y = 2012, M = 1, D = 24 H = 2, M = 0
17/03/2012 10:09:38.859 : VP2: New earliest timestamp 24/01/2012 02:00:00
17/03/2012 10:09:38.859 : VP2: Checking logger entry 1 Y = 2012, M = 1, D = 24 H = 2, M = 30
17/03/2012 10:09:38.859 : VP2: New earliest timestamp 24/01/2012 02:30:00
17/03/2012 10:09:38.859 : VP2: Checking logger entry 2 Y = 2012, M = 1, D = 24 H = 3, M = 0
17/03/2012 10:09:38.859 : VP2: New earliest timestamp 24/01/2012 03:00:00

Cumulus tries to cope with this, but it's not ideal.

Thank you Steve - I will fix those now.

Best wishes
Pauline