I am using a davis VP here at the new house now.
The data extraction at start up works great, especialy once i discovered and fixed where it doesnt try to get the data if the program has only been not running for 2 minutes or less (verison 10.12x).
Its great…I can stop wd, do some testing, etc, restart 10 minutes later, and no data loss…
just make sure the console time matches the pc time (and date)
and you use 1 minute data recording interval.
i am getting a solar sensor, so i will be testing that out when i get that
i really recommend the davis VP to anyone
ok, costs more, but you only live once, right?
I have been experimenting with your upgrades with my Davis and things are looking very fine. i am going out of town for a few days, so I will be interested on how it works with a lot of stored data. i am going to reset my archive interval to accomodate the number of days I will be off line, and then I will see how well it works.
Wife won’t get into the crate, so it might take a while more. :roll:
its just the europeans now…
maybe i need to set my windows regional settings to what they have…
what do you europeans have set for time and date format in your windows regional settings?
Brian,
Glad to hear you will be installing a solar sensor. I finally decided to go all the way and have a UV and a Solar Sensor sitting on the workbench, along with a solar powered fan aspirator. Now to find the time to upgrade the hardware and the pole mount (raise it up an additional 10 feet) add proper grounding (I don’t need to us my mast as a lightning detector). Now, when I have questions on setting it up, I’ll know where to go… :lol:
BTW - version z looks good. And you are right, the datalogger startup looks pretty reliable. Do you recommend clearing it daily? Does that function work ok now? I remember there were spikes on my graphs at that point in time when it clears. I think it was around 10 something in the am?
Brian,
Yes, it is working fine. I’m new to Davis Vantage Pro as I replaced my WMR968 . The extraction is working very well, and quick. I had gotten it just before you started working on the extraction routine and it was a little confusing until the fix was put into place. I agree, it may cost more and we live only once, enjoy it while you can!!!
Still problems for us europeans and our metric system!
On restarting after stopping wd, the time of the last data input shows up as being correct, the window stays open for a few seconds then closes.
On checking the log files, there is still a gap.
One thing which may or may not be of significance is that the date always appears on the Davis Console in mm/dd format, but in dd/mm/yy format in the weatherlink software.
Settings in regional options are as follows:-
English (united Kingdom)
Number 123.456,789.00
Currency
i have the date as (in windows regional settings, under control panel):
dd/MM/yy
too…
and its ok for me…
the console shows month/day…i did not change that…
time i have has :
h:mm:ss tt
with : as the separator
thats the other thing to check on too
Asking for archived data download
re starting download
Asking for archived data download
Retrieving data from day 17 month 6 year 2004
Retrieving data from hour 12 minute 19 sending OK after requesting time or after 5 blocks of data*
All data downloaded or did not sync correct!
Weather station type number 31
And finally teh vptemlog is empty, as is the vpdonloaddata
hi
ok, then that sounds like it cant find the time/date in the data logger to start the download from
is the date /time correct on the console (double check that)
i wonder if the date format on the console is to blame…
i have left mine as US type date, i.e month then day …
maybe try that??
how long a period of time do you have wd not running for , for testing?
what i will have to do is add more debug code to show what it is and not doing for you…
but i am away over the weekend…
My wd can be shut down for any duration with no data uploaded when wd restarts. It knows when the last data was received because the time shows up, but no data from the switch off is updated, but it immediately starts to upload current data. I still can’t get my head around why it reads the current data no problem, but not the stored data. The only error in the log is the intitial error I get which is a memory access violation as mentioned a while ago. Dates on the VP console are the same as yours.
I have a Davis VP too. With the latest WD, I have no problems with reading the datalogger.
Try shutting down WD and running the Davis Weatherlink software and see if it is able to read the logger. It will not clear it so you won’t loose any of the recorded history. I used that method to verify that I was able to read the logged history from the VP console.
I have not had to restart WD for a while, and when I do, it is only a couple of minutes. I haven’t really seen the problem I used to have with it reading the correct data and then going off the deep end reading all kinds of crazy dates and times. That was a problem with the full datalogger.
