Problem Loading From VP2 USB Logget

Hi:

I had my weather W11 PC down for several hours to upgrade memory and run memtest98. WD v1037S build 143. I have spent most of the day thrashing about trying to load the missing data from the VP2 USB logger. I have had to restore the datafiles and logfiles from the backup several times, which fortunately was taken right before I began the memory modifications. I need to figure this out because W11 will update and reboot automatically and it cannot restart WD in administrator mode until I authorize it.

The last valid entry in 72022lg.txt was 7:55. I am doing the following:

  • Control Panel / Data Logger - set “Time/Date to Get The Data From” to 7:56 and click [Set]
  • Shutdown WD
    [li]Edit these log files to remove entries later than 7:55
    72022lg.txt
    72022extralog.txt
    72022vantagelog.txt[/li]
  • Restart WD
  • Log Loading dialog shows loading data starting at 17:45
  • Action / Convert Log files To Data Files

The data in the log files jumps from 7:55 to 17:45 and so do the graphs.
It did not download 7:56 to 17:44
Once, while I was thrashing around, it did download all the data, but I don’t know why.

Any advice is apreciated,
Steve

I discovered my Windows11 WX mini-PC had auto-rebooted overnight.
When I logged in, WD was not running.
I started it up this morning, forgetting to start it in administrator mode, and after a few seconds, data for the entire night appeared to be present in the graphs.

Does anybody know if WD automatically fetches data from the Davis Logger in a situation like this?

Steve

It should do, as long as it hasn’t run out of onboard memory in the datalogger, in which case the datalogger will over-write the oldest data.

When WD is restarted, it should have a record of the last data capture time (can’t remember if it’s in the .ini file or if it looks at the logfile). It then tries to download from that time and will automatically apply the new data to the graphs etc.
The only thing that will be missing on the graphs is the average wind.

That will be a windows update reboot