Possibly been asked before, but do you have the “Data Logger” turned on in the Control Panel?
The most useful file to attach would be wmr200history.txt - you will probably need to zip it up to make it small enough to attach.
N.B. As you probably already know, wmr200history.txt is created fresh each time WD is started, so if you have closed and reopened WD since then, the evidence is lost.
Data logger is turned on in control panel, tbh didn’t know the history file is lost each time wd is closed so indeed evidence is lost only history file I have correlates with the data file I attached although should there not be a file that holds all the data much like the one I attached
The file you attached tells us what was actually recorded.
The wmr200history.txt file (in the wdisplay folder) shows loads of detail about the actual collection of data from the WMR200 data logger and can be very useful for diagnosing problems with that collection - indeed it is pretty much essential for diagnosis.
Especially if you are collecting several days worth of data the file can be very large, hence the need to zip it up before attaching.
Zipped version is too large to upload, the station console is going back today for testing having done a further master reset and re-install I’ve had enough! History file shows all the data however there are no log files apart from for the period the console was attached to the pc. Supplier is not being much help and have had no response to 2 emails from Brian a bit dissapointed
The WMR200 is storing the sensor readings from all of its sensors every minute, so not quite sure what was meant by “summary record”.
Using WD’s WDMySQL uploader I copy that data to an online MySQL DB where there is a query page for it on my weather site www.sandcmills.co.uk/flying/weather.htm. I created that query page because a weather student at one of the UK universities wanted to be able to analyse statistics and I have stats going back to the Tsunami. The page lets the reader say what sensors/data fields they are interested in, specify value ranges if required (either Min/Max/Range) and a date range and the page will return all of that data and offer to download it as .CSV.
One can readily see there that all of the sensor readings are being recorded.
I’ve recently switched my weather station and its base to a 24/7 server so can’t comment on the loss of data issue.
Kind Regards
Steve
What does it say right at the top of the history file - say the first 100 lines or so?
Also maybe the 50-100 lines above ‘Finished, updating wmr200 log files’ and/or ‘Station ready’.
I’m using this system for the first time having struggled with WD10.37N trial version and the WMR200 for a week or two. Like a previous writer, I can’t get sensible graphs because the plots only seem to include data logged whilst the PC is connected, or there is masses of missing data when the WMR200 indicates 290 days storage left.
All I want to do is to be able to plug in the PC, download the data and plot a graph on a linear time scale and then print it out. At present the graph time scale only seems to use the times when the PC is connected to the WMR200.
Also I notice that the rain gauge “Last hour” result looks like the Last days rain, the “Today” reading looks like the last week. “Yesterday” is always zero, and the Last Month figure looks right.
Clearly I cannot justify buying this software unless I can get some help to make it work like the last weather station I had (ELV) which plotted graphs beautifully until the hardware failed.
The same general advice as given to that writer will apply - especially the bit about attaching a sample wmr200history.txt.
If we are to help we need detail to work on.
Which would suggest 10 minute logging interval and an empty data buffer.
1 minute logging would allow 29 days worth of memory. If that is likely to be enough it would give you much more detailed data (once you have it working).
There is usually lots of help available on this Forum.
The author is usually around too, but he’s moving house at the moment so his Forum time is probably more limited than usual.
Thanks for the helpful reply! I reduced the interval to 2 mins and I’ve attached the wmr200history.txt and hope this helps.
I can’t make much sense of the file so look forward to hearing your thoughts.
Best wishes, Calvin
wmr200history.txt (98.1 KB)
From the top:
Looking for data from 23:19:00 23/01/09
This says that WD believes that it should be looking for data records from 23:19 on 23rd January 2009.
That choice will be based on the value that is in the [Davis download] section of WDISPLAY.INI as WD starts up.
WD updates that figure while it is running, so when it is restarted it can start picking up data from where it left off.
Next, here’s the first data collected from the data logger
**Current actual data D1
**Current actual data D2 31 16 13 17 01 09 00 00 00 00 15 00 CB 00 28 0A 0D 0C 08 0D 0C 0A B0 00 00 20 00 D3 43 D6 33 01 00 C0 00 2B 3C 00 00 01 20 00 51 0A 00 00 36 07
D2 31 16 13 17 01 09 00 00 00 00 15 00 CB 00 28 0A 0D 0C 08 0D 0C 0A B0 00 00 20 00 D3 43 D6 33 01 00 C0 00 2B 3C 00 00 01 20 00 51 0A 00 00 36 07
Decoding missed data now
Time from decode 01/23/2009 19:22:00
baro check 982.0
indoor temp check 19.2
indoor hum check 43
missed data time: 19:22 date: 23/1/9
Missed data Acumulate Rain= 51.97
time from data 19:22:00 looking from 23:19:00 current time 08:13:28
number of sensor = 1
Current Channel # =1
missed outdoor temp =3.2
missed outdoor hum =81
The important bit there is that this data was from 19:22, which is before 23:19, thus the data will be ignored.
Similar things continue happening (i.e. data from before 23:19) until here:
**Current actual data D2 31 16 17 17 01 09 00 00 00 00 15 00 CB 00 28 0A 0D 0C 08 05 0C 00 00 00 00 20 00 D2 23 D5 33 01 00 BE 00 2B 3C 00 00 01 17 80 5D 28 80 00 75 07
D2 31 16 17 17 01 09 00 00 00 00 15 00 CB 00 28 0A 0D 0C 08 05 0C 00 00 00 00 20 00 D2 23 D5 33 01 00 BE 00 2B 3C 00 00 01 17 80 5D 28 80 00 75 07
Decoding missed data now
Time from decode 01/23/2009 23:22:00
baro check 981.0
indoor temp check 19.0
indoor hum check 43
missed data time: 23:22 date: 23/1/9
Missed data Acumulate Rain= 51.97
time from data 23:22:00 looking from 23:19:00 current time 08:13:40
Difference in rain =0.0
number of sensor = 1
Current Channel # =1
missed outdoor temp =-2.3
missed outdoor hum =93
*****updating data 23:22:00 23/01/09
The important bit there is that this data was from 23:22, which is after 23:19, thus the data is relevant. The “*****updating data” bit tells us that WD is saving the data to its records.
Similar things continue happening (i.e. data from after 23:19) until here:
No more missed data, finishing up, WMR200
*** updating data arrived during history data ** 07:53:00
*** updating data arrived during history data ** 07:54:00
*** updating data arrived during history data ** 07:55:00
*** updating data arrived during history data ** 07:56:00
*** updating data arrived during history data ** 07:57:00
*Finished*, updating wmr200 log files
Station ready
No more data is being sent from the datalogger, so WD records ‘live’ data that arrived while data was arriving form the datalogger.
At this point operation changes over to normal collecting of ‘live’ data.
Does that make sense?
Which OS?
Do you by any chance allow the computer to “Hibernate” or “Suspend”?
Interesting analysis of the previous posters history files, as per my ongoing problems I have attached exerts of my hisyory file.
Looking for data from 19:48:00 20/01/09
USB port opened OK
**Current actual data D2 31 28 0D 11 01 09 00 00 00 00 00 00 00 00 00 0C 01 01 07 00 0C 0C 10 01 00 20 FF EA 03 EA
D2 31 28 0D 11 01 09 00 00 00 00 00 00 00 00 00 0C 01 01 07 00 0C 0C 10 01 00 20 FF EA 03 EA
Decoding missed data now
Time from decode 01/17/2009 13:40:00
baro check 1002.0
indoor temp check 0.0
indoor hum check 0
**Current actual data 33 01 00 D8 00 2C 5A 00 00 01 65 00 36 0A 00 00 BF 06 D2 31 29 0D 11 01 09 00 00 00 00 00 00 00 00 00 0C 01 01 07 0A 0C 0C F0 00 00 20 FF EA 03 EA 33 01 00 D7 00 2C 5A 00 00 01 65 00 36 0A 00 00 A8 07
found extra D2 13 41 17 1 9 ** 29 0D 11 01 09
checking to use extra found D2
time/date in extra found D2 01/17/2009 13:41:00
**Current actual data D2 31 2A 0D 11 01 09 00 00 00 00 00 00 00 00 00 0C 01 01 07 07 0C 11 30 01 00 20 FF EA 03 EA 33 01 00 D6 00 2C 5A 00 00 01 65 00 36 0A 00 00 EB 06
D2 31 2A 0D 11 01 09 00 00 00 00 00 00 00 00 00 0C 01 01 07 07 0C 11 30 01 00 20 FF EA 03 EA 33 01 00 D6 00 2C 5A 00 00 01 65 00 36 0A 00 00 EB 06
Decoding missed data now
Time from decode 01/17/2009 13:42:00
baro check 1002.0
indoor temp check 21.4
indoor hum check 44
missed data time: 13:42 date: 17/1/9
Missed data Acumulate Rain= 0.00
time from data 13:42:00 looking from 19:48:00 current time 19:48:24
number of sensor = 1
Current Channel # =1
missed outdoor temp =10.1
missed outdoor hum =54
**Current actual data D2 31 2B 0D 11 01 09 00 00 00 00 00 00 00 00 00 0C 01 01 07 0F 0C 0D F0 00 00 20 FF EA 03 EA 33 01 00 D5 00 2C 5A 00 00 01 65 00 36 0A 00 00 AE 07
D2 31 2B 0D 11 01 09 00 00 00 00 00 00 00 00 00 0C 01 01 07 0F 0C 0D F0 00 00 20 FF EA 03 EA 33 01 00 D5 00 2C 5A 00 00 01 65 00 36 0A 00 00 AE 07
This is from my most recent attempt, prior to expoting this data I had done a full master reset of the console and a full unistall and reg edit to remove all traces of WD I am running windows xp sp 2 and have power management settings on the pc that prevent hibernation or closure of usb ports.
History file then continus until this point in time:
time from data 19:46:00 looking from 19:48:00 current time 20:28:22
number of sensor = 1
Current Channel # =1
missed outdoor temp =2.6
missed outdoor hum =94
No more missed data count 1
**Current actual data D3 10 1C 14 14 01 09 05 0C 00 00 00 00 20 62 01
**Current actual data D7 10 1C 14 14 01 09 40 D6 00 2C 5A 00 00 D1 02 D6 0D 1C 14 14 01 09 DD 43 E7 33 6B 03
No more missed data count 2
No more missed data count 3
**Current actual data D7 10 1C 14 14 01 09 40 D6 00 2C 5A 00 00 D1 02
No more missed data count 4
**Current actual data D4 16 1C 14 14 01 09 00 00 00 00 04 00 53 00 00 0C 01 01 07 A4 01
**Current actual data D3 10
**Current actual data 1C 14 14 01 09 05 0C 00 00 00 00 20 62 01
**Current actual data D3 10 1C 14 14 01 09 05 0C 00 00 00 00 20 62 01 D7 10 1C 14 14 01 09 01 1A 00 5E 14 00 00 C2 01
No more missed data count 5
**Current actual data D7 10 1C 14 14 01 09 40 D6 00 2C 5A 00 00 D1 02
No more missed data count 6
No more missed data count 7
No more missed data, finishing up, WMR200
**Current actual data D7 10 1C 14 14 01 09 40 D6 00 2C 5A 00 00 D1 02 D9 08 00 00 00 00 E1 00 D7 10 1D 14 14 01 09 40 D6 00 2C 5A 00 00 D2 02
found extra D2 26 1 0 94 20 ** 01 1A 00 5E 14
*** updating data arrived during history data ** 19:47:00
*** updating data arrived during history data ** 19:48:00
*** updating data arrived during history data ** 19:49:00
**Current actual data D7 10 1D 14 14 01 09 40 D6 00 2C 5A 00 00 D2 02
*** updating data arrived during history data ** 19:50:00
*** updating data arrived during history data ** 19:51:00
*** updating data arrived during history data ** 19:52:00
*** updating data arrived during history data ** 19:53:00
*** updating data arrived during history data ** 19:54:00
*** updating data arrived during history data ** 19:55:00
*** updating data arrived during history data ** 19:56:00
*** updating data arrived during history data ** 19:57:00
*** updating data arrived during history data ** 19:58:00
*** updating data arrived during history data ** 19:59:00
*** updating data arrived during history data ** 20:00:00
*** updating data arrived during history data ** 20:01:00
*** updating data arrived during history data ** 20:02:00
*** updating data arrived during history data ** 20:03:00
*** updating data arrived during history data ** 20:04:00
*** updating data arrived during history data ** 20:05:00
*** updating data arrived during history data ** 20:06:00
*** updating data arrived during history data ** 20:07:00
*** updating data arrived during history data ** 20:08:00
*** updating data arrived during history data ** 20:09:00
*** updating data arrived during history data ** 20:10:00
*** updating data arrived during history data ** 20:11:00
*** updating data arrived during history data ** 20:12:00
*** updating data arrived during history data ** 20:13:00
*** updating data arrived during history data ** 20:14:00
*** updating data arrived during history data ** 20:15:00
*** updating data arrived during history data ** 20:16:00
*** updating data arrived during history data ** 20:17:00
*** updating data arrived during history data ** 20:18:00
*** updating data arrived during history data ** 20:19:00
*** updating data arrived during history data ** 20:20:00
*** updating data arrived during history data ** 20:21:00
*** updating data arrived during history data ** 20:22:00
*** updating data arrived during history data ** 20:23:00
*** updating data arrived during history data ** 20:24:00
*** updating data arrived during history data ** 20:25:00
*** updating data arrived during history data ** 20:26:00
*** updating data arrived during history data ** 20:27:00
*** updating data arrived during history data ** 20:28:00
*** updating data arrived during history data ** 20:29:00
*** updating data arrived during history data ** 20:30:00
Finished, updating wmr200 log files
So it appears that despite re-installation that WD is only looking for data from when the console was first connected and is ignoring all the data in the data logger. The full files are too big to attach any suggestions
Exactly as expected since you removed all traces of WD then reinstalled.
When you started WD there will have been no prior value in the [Davis download] section, so it will have defaulted to the current date and time and have ignored all data from before that point. 
If you knew how far back the dataloggger had data, what you could have done is to “seed” appropriate values into the [Davis download] section of WDISPLAY.INI. That would have changed the “Looking for data from” value and should have caused WD to collect the data that in the above sample case was ignored for being too early to be relevant.
Does that make more sense now?
Thanks again! I am using Win XP Pro, and I do hibernate it or standby overnight. Any further thoughts?
Cheers! Calvin
Do you close WD before you hibernate/standby?
If not then that is probably the root of the problem.
Standby/hibernate will cut the USB to the console, which puts it into datalogging mode, but it doesn’t ‘close’ WD, so the right clue doesn’t get written into the [Davis download] section ready for when you next start WD and pick up logged data.
If you make a point of closing WD before you go into standby/hibernate you should find that things work better.
Many thanks for your help, its back with the supplier now will have to see what they say as there are other issues that need resolving
That was indeed the case! Nice graphs plotting now that I shut WD down before closing the laptop lid. However there will be times when I forget to do this and the plots will be spoiled as a result. Isn’t this problem correctable in a future update?
Any thoughts on why the Last Day’s Rain box only shows the Last months rain?
Once again - thanks for all your help!
Best wishes
Calvin
I can’t speak for Brian, and I’ve never studied hibernation from a programming point of view. I think the application is simply snap-shotted and stopped in full flight, then on return from hibernation is resumed in exactly the same state, but I could be wrong. I suspect that the short answer is probably that real time data processing applications such as WD don’t co-exist well with hibernation so the solution is to not hibernate?
I can’t be certain, but I suspect a knock on from the hibernation effect - e.g. maybe after hibernation when the application is suddenly running again it is well past the change over time but the application has no knowledge that it wasn’t running at that time and so doesn’t realise that the end of period processing hasn’t been done?
From playing around with WD connected to two different WMR200’s, I am pretty confident that each of SKYEWRIGHT’s various thoughts in this discussion on the WMR200 are correct. In brief, hibernating the computer with WD still operating will cause endless problems. This would be the same for most weather software - do not do it. I sure there must be a windows solution to force WD to shut down fully at hibernation to solve this problem.
I think the most important comment provided in the discussion is about the ‘Davis Download’ setting when WD reads data stored on the station. This is potentially big problem where people set-up the station and start recording data before they even think about software. Most people probably have no experience with WD at this time and would have no idea about the need to fix a date in the WDISPLAY.INI file. My inlaws station had over 20 days data when connected to WD for the first time. It took over 6 hours to download, which whilst a little frustrating, it gave a lot of confidence that all was well. It wasn’t until a couple of weeks later (and after my last comment in this discussion) that we realised none of the data had been recorded in the WD data files. The comments provided suggest a possible cause.
If this is the case it would be helpful when installing WD to have a little pop-up screen somewhere when selecting the WMR200 station (and others, where relevant) that identifies this potential issue and gives the opportunity to enter a possible date going back to when the station was started.
Otherwise, I have learnt many valuable lessions with how WD works and all is now good with both stations and the WD software. I have even managed to import over 3 years of VMS data recorded with a midnight reset that I modified in excel to make WD automatically provide correct daily, monthly and yearly rainfall values for a 9 am reset 
(my wife wants a divorce through :oops: #-o).
I’m happy to report that since not hibernating the computer with WD running, all aspects of WD seem to be working as advertised.
I assume a complete set of data still resides in the datalogger of the WMR 200. Is there any way of getting this out to fill in the gaps left by the hibernation problem?
With my last station, the ELV system with the WS300 datalogger, I was able to connect the datalogger to the computer once a week and download (which cleared out the memory), plot and print out the graphs. Can the WD system be operated like this if all you want is the hardcopy?
Best wishes to all, and thanks again.
Calvin