WD is corrupting data from WMR200 data logger

[SergeyKh]

@Meerkat post:49

No, no, no again … It has taken me a few days to analyze all 8 history files to come to this conclusion. WD is indeed corrupting the data.
It did not extract old data from the data logger.
I only received data from the WMR200 data logger for the 8 days the PC was off due to the lightning strike.
That’s why I bought the WMR200 with the data logger in case of a catastrophe like this.

I think that the receiving data from console accumulated there during period without connect to PC is just “get old data”

@Meerkat post:49

You wanted to know why I restarted WD 8 times?
It’s because I noticed that WD history extractor stopped after fetching around 24 hours of data only.
I immediately killed WD and restarted it. WD then continued extracting data from the WMR200 data logger from where it had stopped.
This had to be done 8 times before WD got all the data extracted for the 8 days.

Yes, I said about this. Similar problems discussed in http://discourse.weather-watch.com/t/37862

@Meerkat post:49

Having those I can now prove that WD and not the WMR200 is the culprit here.
Sorry, but you need to do a more in depth analysis of my data.

I agree with you. I analyzed your files and found:

1. under 1st start WD after repair of PC you have correct date in WDISPLAY.INI (11:55PM 22.01.2010) which more early than time of last received record

WD started to extract history data since 17:24 12Feb to about 19:20 13Feb. Here WD had failure, stopped process and started to receive curent data. You stopped WD

2. then you restart WD, but time in WDISPLAY.INI was 16:38 20Feb (!). I think that this time is derective for WD about received records from console and WD used this time for control and rejecting of repeated data.

In “2010-02-20 @ 16h40\wmr200history.txt” we see that WD start to receive the historical data from 19:24 13Feb and stopped on 05:15 15Feb. This show that data set in WMR200 buffer was full without gaps. But (!) this data were got to log file 22010lg.txt.

I think that is bug of WD, but this problem can be partly eliminate under CORRECT time in WDISPLAY.INI. If you change this time to 19:00 13Feb then all data from 19:24 13Feb to 05:15 15Feb were recorded to log file.

3. then situation repeated, WD received (or control) historical data from console, but didn’t write to log-files, only short fragments

4. during last restaring time in WDISPLAY.INI was correct (why?) - 06:44 20Feb. After this the data are good.