Brian, I am beginning to find out just how much of a problem it is to have to shutdown WD for about 8 hours at night. Today we had rainfall during the early hours before I started up WD and while in some log files it has captured the data the total rainfall for the day is missing the nightime rain. I’m also not sure if any max wind speed or barometer maxima etc during the night is properly displayed if it is a max for the day. Later in the year this will also be a problem for sunshine hours. As you already know any data captured at start up is also not written to the database.
If you could see your way to adding an option to get WD to do all its normal processing for each record captured at start up just as it does each minute I would much appreciate it. I realise that it will slow start up which is why I suggest it as an option for those like me who have to run this way.
Unfortunately running my PC with WD 24/7 is not an option for me.
do you have the data logger set to 1 minute logging?
that should work OK, and wD should get the data OK …
also check the davis stations time and date are set OK
I have the logger set to 1 minute, the date and time are also correct and in sync with VP console and PC.
WD does indeed download the archive records as the progress screen at start up shows but yesterday it showed only 0.12 in of rain for the day where the VP console showed 0.13, not much of a difference I know but looking at the records the extra 0.01in happened before I started WD. I do not have the ignore first rain of the day set either. I have also just noticed that this morning %ystdyrain% on my web page reads 0.0in not 0.13in which is what we had.
On looking through the log files I have found that all of the .csv files have gaps where there is no data stored if WD was down (except the 122004extralog.csv which has no gaps), however all of the .txt files do have all of the archive data stored from when WD was down.
the difference in rain …maybe what is happening is wd misses the very first rain reading from the downloaded data…
but, though,also, was wd and the console in agreement for the rain total when you shut down wd?
Yesterday the console was reading the extra 0.01in all day when compared to WD, so no at shutdown at the end of yesterday there was still a difference.
I think I misunderstood you, when I shut down on Tuesday night there had been no rain at all and both console and WD said 0.00in of rain. When I started up WD on wdnesday the console already had recorded rain although I can’t remember how much exactly, but then later I noticed that there was this 0.01in difference between the two so at the end of wednesday when I shutdown WD the console said 0.13 and WD said 0.12.
All were these did not update with archive data from when WD was shutdown
dailylogcsv.csv
indoorlogcsv.csv
122004vantagelogcsv.csv
122004lgcsv.csv
122004lgcsv.csv
and 122004extralog.csv was the only one which had all the archive data
I believe all the .txt files have the archive data OK.
Just to cover all the bases something to check is that there is a setting on Control Panel, Units/other settings to change the hour at which the daily rain total resets. Has been the cause of some rain total confusion in other cases.
I think I have got to the bottom of this. The program seems to store all its data as metric, but I use inches for rainfalll. If you do the maths then 0.13in of rain converts to 3.302mm of rain which WD stores as 3mm, when you convert 3mm back to inces you get 0.11811in which WD displays as 0.12in of rain. So by doing a double conversion you double the error and lose 0.01in of rain. Probably not significant but confusing when setting up a new station like me and it is the first rain you have to work with.
So if anything needs sorting here it would be to remove the conversion and store in the selected units, or don’t round up and down, or at least store 2 or 3 dec places which will significantly reduce any errors (3.302mm converts to 0.013in!). If you are working in hundredths of an inch you will need more than integer values for mm.
However the csv file problem still does exist and needs looking at…
in 10.20v, WD now auto updates the mysql with any missed data (you need to use the new wdmysql.exe program),and also wunderground with the missed data (the time is even sent correctly from back in time, but strangely wunderground reports the time as
when the data was actualy updated, so , so much for that…