I am new at this, setting up WD.
I have a dedicated computer for it, Dell laptop, Celeron2.2Ghz, 704Gb ram, WinXP SP3.
Station is Davis VP2, weatherlinkUSB (without the weatherlink software.)
At this time I merely have it running displaying the WD page and station data, it is not connected to the internet and I’ve done nothing at all yet with the internet/webcam portions of WD.
It will sit there and run for hours at 3-6% cpu usage. Then for no reason I can determine, goes to at least 30-50% constant use with spikes to 80-100% and won’t come back to normal on its own - If I restart WD it returns to normal operation. Yesterday it ran for 3 hours, then went haywire, I restarted it and it ran 12 hours with no problems. Today it ran 3 hours, has now gone to high CPU usage, and I’ve left it 2 hours to see what it will do, it’s staying at high usage.
Nothing else is running on the computer except WD and task manager.
I cannot figure out what causes this. I’ve run Ccleaner, I’ve shut down unneeded windows services, I’ve set the antivirus to not scan files as they write etc.
This is a real problem, I can’t imagine running a webcam and webpage too with this occurring.
This system will be installed in a remote location, no one will be there to restart WD every few hours, and I’m not going to drive a one hour round trip daily or more often to reset it.
I’ve searched the forum and followed up on every solution presented in the past, although most all of them have to do with FTP and webcam issues…
Any ideas?
it could be the USB data logger problem
try updating to the latest Si labs USB driver for the Davis USB data logger
(there is a thread about where to download that from)
what antivirus program?
also any errors under view , program event log, when this occurs?
Thx.
I have the SiLabs driver installed v6.3a
Avast av.
Program event log empty.
Restarted WD and it did not return to low CPU use has it has in the past. Hovering at 25-40% with spike to 80-100% every half minute or so. Task Manager shows it’s WD using the resources. Rebooting didn’t help either.
Had similar probs which I tracked down to avg. It has become so “bloated” that it was using so much cpu that on occasions wdftp at a peak time caused a freeze.
Since removing and substituting, have had no more cpu overload problems.
Yeah, I would try it with Avast disabled.
Thought of that too.
I have Avast disabled, no change, rebooted with it off as well, no change.
(since the machine is not connected to the 'net, can’t hurt!)
Hmmm, so much for that idea 
Is the main internet switch off ? That’s on Control Panel, FTP, Connections.
Are you sure you have all power saving options turned off? Those can be pretty sneaky on laptops.
What version of WD?
Internet is off. (I checked all intnernet network etc settings, all off or no accounts etc)
Power settings all essentially off (no sleep modes, power downs etc)
WD latest rev downloaded 3 days ago. ver 10.37Q build 38 (Until I see that this will do the job, I’ve not yet paid for it, but that shouldn’t matter)
Stumped.
Wish there was a way to see what WD is actually doing.
try as a test:
install WD to a new location (full install)
then create a file their called 2wd.txt
then start up WD there
it should start up like brand new, no settings, from there
then setup the station type and basic settings
and see how that runs
as a test
I did that. No difference.
But I think I figured it out, sort of. Don’t quite understand it.
Didn’t mess with it for a couple days, then fired it up and it was even worse. So slow the initial data load from the logger took 5-6 minutes then hung. Was using 100% of cpu cycles.
I restarted WD a couple times, still using 80-100%
Then, it was fine, back down to only 4-5% with small one seconds spikes.
I let it run 24 hours, no issues.
Next day, I shut down the computer, restarted, WD went back to using 80%+
Had a hunch, it acted to me like there was a conflict of some sort. First I went to turn off ‘start WD when windows starts’ and it wasn’t in the Startup folder.
Found it was in the startup.ini found by running msconfig. Disabled it there.
Then I experimented. Every combination of startup, repeat. Kept checking settings, disabling things, looking at logs etc.
Here’s the thing I’ve “discovered”: If I boot up the computer, let windows launch, and wait at least 5 minutes before starting WD, it works fine. Seems to work fine every time if I do it that way. If I start it too soon or let it autostart, it has the high cpu usage issues…
Now I’ll start turning on AVS and things and see how it goes. Hopefully it’s that simple.
(I tried to install and run WD and the Datalogger on my desktop pc for a test, but a couple months ago I had downloaded WD to check it out. Since the trial expired, it won’t let me… And I am not willing to risk putting it on the wife’s laptop.)
sounds like a slow to be loaded driver that is used or similar
There is a program wdstartdelay.exe and that can configure a delayed start to WD allowing all other drivers and processes to be complete. Put it in Startup group and ensure WD is not set to start on PC bootup.