Problems importing from Davis VP2 [Resolved]

So this has happened a few times recently

In all examples, I brought down WD gracefully. In some cases I even did a reboot (for other reasons)

When launching WD, the popup comes up showing the import from Davis VP2. It shows the correct time to begin the import (from where it left off). However,
above that where it does the actual import, it seems to be going back to the the oldest data from the VP2.

In the example from the screen shot, it should be retrieving data from today (7/21) @ 11:55. However, you can see above that its going back to 7/19 @ 16:25.

In the past I have just aborted and all was fine (missing 1-2 mins of data isn’t bad). However, the last few times this didn’t work. I had to relaunch WD and let it go all the way from the beginning to current

Thoughts???


Screen Shot 2019-07-21 at 11.00.13 AM.png

Looks like your logger is 1 hour behind…check that logger and console agree on time…

where are you getting that Dan

everything seems to match - logger, VP import screen and on WD itself

I just tried exiting and coming right back into WD - worked fine

Exited again and left WD off for a few mins to let some time lapse - i was able to reproduce the problem

Btw WD record count won’t start incrementing nor will data populate into WD until the import completes, which takes several minutes as it is going back to the beginning.

I am 1 version behind. I could update but don’t think that will help. (I will update though)

@ Brian, any thoughts?

Doesn’t happen all the time, but has happened more than once

what shows under view, debug info


Dan, thanks didn’t catch that.

I will check when home. But when I saw your first post I did check and believe it was all in syc

I would agree that would cause an issue

@ Brian I will also check program event log when home

@ Dan I think that could have easily been a typo on my part. Will test when home and verify plus check debug as brian suggested

So I got home.

Despite what I thought my time on the VP console was off - not an hour though but 20 mins.

I would bet this is the cause. I updated all to be the same

Of course it is pulling ALL the data. When it comes back I will re-test

Changed the time and it appears to be working now

I will let it run a bit and try agian to be sure

Any thoughts on how the VP console time could have been off 20 mins?

Tried another test, seems fine now

Just wondering why the VP console time would be off 20 mins

Thanks

the console is not very accurate for time and does tend to wander

Does the MAC version of WD have the same console time setting facility as the win version? I’ve always used that :slight_smile:

no…

Oops :oops:

Good catch Dan!!!