Page 1 of 1

Rainfall after shut down period.

Posted: Mon 16 Sep 2013 2:38 pm
by XBower
Hi all.

Today at around 16:00 (after today's rainfall), when I fired up Cumulus after it's been shut down since last night, I noticed that the rain figures weren't updated.
Rate and Last Hour are 0 ,correct.
Today is also 0, not correct, should be 9.4.
Last 24 hours 11.6, could be correct.
Yesterday is 6.2, correct.
This month is 16.6, not correct.
This year is 357.8, not correct.

Does Cumulus not read Today's rain from the logger when fired up? Or when will it?
Or have I set it up somehow wrong?

I'm using 1.9.3 b1059

Regards

Re: Rainfall after shut down period.

Posted: Mon 16 Sep 2013 2:42 pm
by steve
Please zip up the diags folder and attach it.

Re: Rainfall after shut down period.

Posted: Mon 16 Sep 2013 2:51 pm
by XBower
steve wrote:Please zip up the diags folder and attach it.
Like a cobra...
Sorry, forgot that...
Here goes.

Re: Rainfall after shut down period.

Posted: Mon 16 Sep 2013 3:26 pm
by steve
Cumulus uses the annual rain total to maintain all of its rain data, except during logger download when the only figure available is the amount of rain that fell in that logger interval, so Cumulus updates its counter using that figure. There is a bug in the Davis DLL (or in the console firmware, I forget which) which means that the latest logger entry is never sent. To guard against the counter going out of step as a result, Cumulus reads the annual counter at the end of the logger download. It appears that sometimes with your station, this read fails:

2013-09-16 15:51:10.181 : VP2: Error reading current rain total from station

What Cumulus does then is to start the counter for the the day from that point. I have no idea why I did this, it doesn't seem very sensible. What it should do as a fallback is just to carry on with the counter it calculated for itself. The next time it reads the data it should get the counter anyway. I'll change this in the next build of 1.9.4.

You can correct today's figure using the 'today's rain' editor on the Edit menu. Restarting Cumulus will then correct the monthly and annual totals (assuming all of the daily totals in dayfile.txt are correct). Unfortunately, restarting might cause the rain counter to be reset again! I'll try to get the fix uploaded this evening.

Re: Rainfall after shut down period.

Posted: Mon 16 Sep 2013 4:26 pm
by XBower
steve wrote:Cumulus uses the annual rain total to maintain all of its rain data, except during logger download when the only figure available is the amount of rain that fell in that logger interval, so Cumulus updates its counter using that figure. There is a bug in the Davis DLL (or in the console firmware, I forget which) which means that the latest logger entry is never sent. To guard against the counter going out of step as a result, Cumulus reads the annual counter at the end of the logger download. It appears that sometimes with your station, this read fails:

2013-09-16 15:51:10.181 : VP2: Error reading current rain total from station

What Cumulus does then is to start the counter for the the day from that point. I have no idea why I did this, it doesn't seem very sensible. What it should do as a fallback is just to carry on with the counter it calculated for itself. The next time it reads the data it should get the counter anyway. I'll change this in the next build of 1.9.4.

You can correct today's figure using the 'today's rain' editor on the Edit menu. Restarting Cumulus will then correct the monthly and annual totals (assuming all of the daily totals in dayfile.txt are correct). Unfortunately, restarting might cause the rain counter to be reset again! I'll try to get the fix uploaded this evening.

Hi, thanks.

Would something like this be avoided by maybe running Cumulus 24/7 or perhaps downloading on a "not rainy day"?
Or install 1.9.4?

Re: Rainfall after shut down period.

Posted: Mon 16 Sep 2013 4:36 pm
by steve
XBower wrote:Would something like this be avoided by maybe running Cumulus 24/7 or perhaps downloading on a "not rainy day"?
Yes, either of those would avoid the chance of this occurring.
Or install 1.9.4?
Yes, with the fix I've just uploaded.