I have noticed for the last few months, if I have WD off for a while, when I go to update the data from the dataloger (using at Davis vantage pro 2 as source), the data load (I think) seems to go fairly quickly (currently uploading about 12 days of data at 10 min intervals, it takes about 1 minute to load a 10min lot of data) The problem is the actual loading into the WD program is very very slow. I have disabled WUHU uploads, didn’t speed it up. I think it has been slow since I have included solar readings, some time ago. It used to be fairly quick, in upgrading WD after the download from my Davis. I do run both weather link and WD but only upgrade one program at a time. The weather link uploads fairly quickly. But the old WD in upgrading/uploading the actual program is painfully slow, slower than what I think it should be.
Any ideas, I have the current upgrade for WD and as I said, it used to go probably as quick as weather link does now. I think it is something to do with the solar readings but I am not sure.
In the datalogger setup window, what frequency do you have set for checking data in WD? It’s recommended that it’s set at 1 minute for WD.
You say you’re using both WD & WL, is this through VVP? As VVP should enable both WD & WL to download the missing data at the same time because VVP will download from the datalogger and then make it available to the other software.
The fact that you’ve added a solar sensor shouldn’t effect the datalogger downloads. It seems that maybe the WD isn’t recording the time it was closed and thus is downloading everything that’s on the datalogger, hence the time it’s taking. Again, this may be solved by changing to the 1 minute download intervals.
it also may be slow because of a data check
Still doesn’t appear to be working as it should be. Data interval is set at 1 min. The data download from the console, via virtual vp is rapid, the upload into the program is taking about 2 seconds for each 1 minute of data. I seem to recall it being faster or is this about right??
which version/build of WD?
(that info should always be provided)
also maybe you have set to plot the max solar in the solar setup
I have a net pc, atom cpu
no problems with the speed of the data import
Latest version. I have no problem with the data import from the Davis, it is the process after, the actual importing/loading that data into the WD program that is painfully slow.
what speed pc?
how much memory?
3.2 ghz 16gb ram windows 8 64 bit
How does it run without using VVP to transfer the data?
Have WD collect the data direct from the logger, just as a test.
OK here’s what happens; I have VVP running, sending data to WD and Weatherlink, both work happily together at the same time, using virtual console tcp/ip setup. If I have had the computer off, I activate each program by itself initially, to up load data, via VVP, from the Davis VP2. I normally run WD first. I boot the program, the main WD display starts minimized, a small window opens up Davis VP History Data Extractor , the first action states it is retrieving data (from the Davis) and this goes fairly quickly. The second stage I assume it the history extractor writing the data to WD. I then will close down WD, open Weatherlink, extracts and loads the data in a flash, minimized Weatherlink, restart WD history data does its thing also in a flash (only downloading 1 to 2 minutes of data) and both programs happily work together.
Just as a check, I chanced the port program from VVE to VSPE, same result 1st stage data extraction nice and fast, 2nd stage “writing data”… painfully slow. I have attached my wdisplay ini, wdisplaybackup.ini files.
WDISPLAY.INI_0825.txt (53.9 KB)
WDISPLAY.INI_0825.txt (53.9 KB)
so its the actaul updating of the data/log files that is slow
i.e the 2nd part
how slow are you talking about?
did you see my post above about unsetting to plot max solar on the graph (i.e see if yo have that ticked)
Yes it is the 2nd part that is slow, about 1 minute update in 1 second. I do have that max plot ticked, have just unticked and testing, back shortly.
A marginal difference with that unticked, not really noticeable.
not sure then why you have this partciular problem
when did you notice the problem start
also check how much hard drive space you have left or similar
744gb free in hard drive. hard to say when it started, first would have been noticed after an extended down time and the slowness of the update of the program, sorry cant be more help there. Also using WD to update WUHU, but have tried it with WUHU turned off, still same result.
I was thinking of uninstalling WD completely, saving only the necessary data to see if that cleared it up? What do you think and what do I need to preserve?
I have not noticed any particular slowness with the history data updating myself (compared to where it normaly is)
and I done see other reports of a similar problem
maybe its your antivirus program or firwall
or a permissions problem
scratching my head here, sorry
Just sent an email Brian.
Ok, did a test install to a different folder, ran that test program, closed it down. Copied the current wd.ini file to the test folder. Waited 15 mins, (theory if the problem still exists, it will take 15 secs to download VP data and write to new program) Restarted the test program, the download from VP was as it was, fast. The 2nd stage … as it used to be, nice and fast, not 15 seconds. So proved the theory, uninstalled the original WD program as per directions. Uninstalled the test program, deleted registry files, copied over the original current ini file and also copied over the old data and all up and running. As per Brian, don’t know what caused it but seems to be all fixed now. the test will be tonight, I will shut it down overnight and see what the result is tomorrow morning. Watch this space.
Ok. All is good. Started up this morning, instead of taking 1 second for 1 minute during the 2nd stage of the data update, it took about 1 second for 10 minutes of data. The only thing I can think of is that the program had about 4 years worth of upgrades, data, registry changes etc and it needed a clean out ??? The 4 years of data is still there, but the registry is fresh.