I am still having problems with this. When I got to the office this morning and turned my screen on, WD was open on the desktop (not a good sign). I have a Win 7 (64bit) machine that runs 24/7. I checked my web site and saw that WD had restarted spontaneously at 5:02. However, my extremes did not reset.
Brian… any ideas why I’m having this problem. If I force a restart, it still keeps the old data.
Help!
Steve
make sure to set WeatherD.exe to run as administrator on W7 or Vista
I use W7 64 bit and do not have the problem you describe
also turn off windows auto updates (you can still manually do updates and it will prompt for important updates)
also make sure power saving options are turned off
Thanks for the reply Brian.
I have checked to run as Admin. and will see if that makes a difference. I already had auto update off, and the only power savings is the monitor.
This is a relatively new problem for me. I’ve gone for over a month without any problems at all sometimes, but now, having problems with the Extreme Conditions.
Will see if it changes anything.
Steve
I just restarted WD and Max avg (wind) and max temp and min temp all have reading from … I don’t know where. Certainly not since 0 hrs. Is there an error log file I can send to help you… help me??
Thanks again, Brian.
Steve
not very much information to go on…
what period of time was WD not running?
what is the data logger interval ?
is the time/date on the VP the same as the PC?
which version of WD (and build)?
the more information you can provide the better
I am using the latest version 10.37Q Build 02. WD hadn’t stopped running, I just closed the program and then reopened it to see if that would reset the max/min, which it didn’t. My program has been running non-stop since yesterday morning and the wind extremes seem ok, but both Temps are off.
Data logging is at 1 min. intervals. The time on the computer and my VP2 display are the same.
Sorry… just not sure what info to give you.
Thanks again, Brian.
Steve
that screen shot is unreadable, sorry
any error under view, program event log (after WD has gone through the reset hour you have set in the units setup)?
I’m sorry about the screen shot, not sure to insert one.
Here is my event log:
Unable to write to C:\wdisplay\WDISPLAY.INI
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 3:00:01 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 4:00:00 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 5:00:00 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 6:00:00 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 7:00:00 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 8:00:00 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 9:00:00 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 10:00:01 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 11:00:01 PM 11/24/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 12:00:01 AM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 12:01:01 AM 11/25/10
Unable to write to C:\wdisplay\WDISPLAY.INI
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 1:00:00 AM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 2:00:00 AM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 3:00:01 AM 11/25/10
Unable to write to C:\wdisplay\WDISPLAY.INI
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 4:00:00 AM 11/25/10
Unable to write to C:\wdisplay\WDISPLAY.INI
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 5:00:01 AM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 6:00:00 AM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 7:00:00 AM 11/25/10
Unable to write to C:\wdisplay\WDISPLAY.INI
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 8:00:00 AM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 8:14:58 AM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 8:26:56 AM 11/25/10
Unable to write to C:\wdisplay\WDISPLAY.INI
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 9:00:01 AM 11/25/10
Unable to write to C:\wdisplay\WDISPLAY.INI
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 10:00:00 AM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 12:00:01 PM 11/25/10
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 12:01:31 PM 11/25/10
Unable to write to C:\wdisplay\WDISPLAY.INI
As you can see… I guess there are lots of problems… every hour on the hr. ?? My reset time is set for 0 hrs.
Not sure why.
Thanks again Brian…
Steve
I am still having problems with WD not resetting my rain total at midnight, nor does my temp reset. For some reason almost every night, WD quits working but usually restarts, but the totals don’t reset.
Any help? Starting to get really frustrating for me… 
Thank you.
Steve
I am still having problems with this. When I got to the office this morning, there were 3 instances of WD up on my monitor. One was functioning and the other 2 were hung up at the VP extraction point. I have checked my start up using various ways, and there is only 1 instance of WD running or set to start when the computer starts. My computer runs 24/7. I’ve gotten used to having several versions of WD running (it doesn’t happen every morning), but it’s the not resetting some of my reading to 0 at midnight.
Here is a screen shot showing what it is now. The wind shows an afternoon time-stamp (it’s still morning) and there has been no rain today.
HELP!
Thanks.
Steve
ps… if this makes a difference here is my event log
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 8:02:34 AM 05/16/11
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 9:00:01 AM 05/16/11
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 10:00:01 AM 05/16/11
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 11:00:00 AM 05/16/11
ERROR: Unable to write to C:\wdisplay\WDISPLAY.INI at time/date 11:02:03 AM 05/16/11
are you using startwatch or WD’s wdwatch ?
maybe turn those off if you are
also makes sure to set your antivirus program to not scan the WD folder (and more especially the wdisplay.ini file)
I do not have this problem here
Thanks, Brian. I do (did) have wdwatch running and I am sure that’s why multiple instances of WD were up and running. So I turned that off and made my antivirus not scan the WD folder.
However, that doesn’t explain why my extremes are not resetting at midnight. Here’s this morning’s screen shot showing the max temp for 4:28pm and it’s not quite 9AM here. Still perplexed on that issue.
Here is my screen shot.
what shows under view, program event log and under view, WS2010/WS2500 data setup?
what speed pc and how much memory on the PC?
Hi Brian,
Under the event log:
Unable to write to C:\wdisplay\WDISPLAY.INI
Unable to write to C:\wdisplay\WDISPLAY.INI
and under WS2010/2500:
Normal daily resetting wind/temperature daily value , day: 27
Normal daily resetting rain daily value , day: 27 rain today 2.5 mm
Resetting warmest day values 6:00:31 AM 05/27/11
Resetting warmest day values 6:01:31 AM 05/27/11
Setting VP time auto daily 6:06:00 AM 05/27/11
found CR
sending SETTIME to VP console
sending time to VP console
setting station type to VP
Doing checking of time zone calculation
Daylight saving in use
found time to release com port
re connecting the comport
Doing checking of time zone calculation
Daylight saving in use
The 2 attachments are Eurekalogs for the last 2 errors I got.(shows my computer config too.)
Thanks.
Steve
ps. had a 56mph wind gust last night… and then no reading after that… got to the office this morning, cups are gone! What the heck!
eurekalog6.txt (7.39 KB)
eurekalog7.txt (7.4 KB)
will be interesting to see if the special version I have got you to test fixes this problem for you
Brian,
Well so far so good. The extremes reset last night, where the high temp had not been resetting. So… we’ll see. Excellent so far.
Steve