Cumulus Support

Got the green New Record Highest minimum temp of 24.1c for yesterday August 14, 2010. When checking the console's Yesterday Min temp on console it shows 24.1c at 00:35 and Max temp shows 24.5c at 00.00. Both of these are incorrect and the actuals for yesterday should be Min temp 20.5c and Max 28.6c (from the Aug10log file as well as from Weatherlink).

I have checked the dayfile.txt file and found a few days have a 2nd data line (16 since starting Cumulus in November 18, 2008) and August 14 is one. In then checking the Jun10log, Jul10log and Aug10log 2010 files found that there is a 2nd data entry line at 1:00 am the following day (logging every 30 minutes).

Jun 5 2010 dayfile.txt has 2nd data line with all different data
Jun10log file for Jun 6 has 2nd data line at 1:00 am with all the same data except Wind dir, Total rainfall today so far, Current gust

Jul 17 2010 dayfile.txt has 2nd data line with all different data
Jul10log file for Jul 18 has 2nd data line at 1:00 am with all the same data except Pressure

Jul 24 2010 dayfile.txt has 2nd data line with all different data
Jul10log file for Jul 25 has 2nd data line at 1:00 am with all the same data except Pressure

Aug 14 2010 dayfile.txt has 2nd data line with all different data
Aug10log file for Aug 15 has 2nd data line at 1:00 am with all the same data

I can correct the All time high info.
Is there any issue with deleting the 2nd data lines in the dayfile.txt file? (I would need to look and see which one I should keep)
Is there any issue with deleting the 2nd 1:00 am data lines in each of the monthly log files? I can determine which one to keep.

Anything else I should do, and any thoughts what might be the cause? This is a dedicated weather computer and there is nothing that I am aware of that happens automatically on the computer around those times, or at any other time except AVG scan once a week at noon.

Thanks for your help.
Paul

PaulMy wrote:Is there any issue with deleting the 2nd data lines in the dayfile.txt file? (I would need to look and see which one I should keep)
Is there any issue with deleting the 2nd 1:00 am data lines in each of the monthly log files? I can determine which one to keep.

There's no problem with deleting completely duplicate lines. You'll need to look carefully at the dayfile.txt lines to see if they actually need merging, although I suspect you probably need to keep just the first one.

Does your PC clock get set by something once a week - those dates you have listed are all Saturdays. It looks to me like something is setting your clock and not catering for Daylight Savings - I assume you are on DST at the moment? So at 0100 on a Saturday, your clock gets set back to midnight and Cumulus thinks it has to do the daily rollover again.

If you zip up the diags folder and attach it, I'll see if I can see what might be going on.

Steve, thanks for the quick reply.

You are correct, all dayfile.txt duplicates, except 1 in July 2009, are since Cumulus installed on this new computer Dec 2009 and are all on Saturdays, not every Saturday but some in consecutive Saturdays. The MonXXlog files duplicates are then all on the following Sunday. Have checked my scheduled tasks and found that SynchroizeTime and WinSAT are both scheduled for every Sunday at 1:00 a.m. and these likely would have been set up automatically with the new computer. Should I remove these scheduled tasks or change the time or any other suggestion?

Much appreciated,
Paul

Edit. Forgot to confirm I am on Daylight Savings Time. Will upload the log if still needed, but looks like you helped find the culprit. Thanks,

PaulMy wrote:SynchroizeTime and WinSAT are both scheduled for every Sunday at 1:00 a.m. and these likely would have been set up automatically with the new computer. Should I remove these scheduled tasks or change the time or any other suggestion?

You can keep them if you want them - SynchronizeTime is presumably the built-in Windows internet time synchronisation? But I think you have a problem with your daylight savings settings somewhere. If the time is being set at 0100 and it is causing Cumulus to do a second day rollover, that suggests that your clock is being set back an hour to midnight. You could perhaps change the setting to 0200 and see what effect that has; at least you shouldn't then get the duplicate day rollover.