I was looking through my charts when I found this odd blip on the charts.
This was recorded using a wireless Davis VP2 station hooked up via serial datalogger with weather-display running. Everything seemed to be working great except for this anomaly. RFI? people screwing with the sensors? ISS hiccup? Any ideas?
Thanks for any advice to track this down. 
That is strange. The blip is also in the barometer (located in the console) value which argues against RFI or other ISS issues.
http://weather.mgcjerry.net/curr72hourgraph.gif
Could be a bad import from the logger. My guess is you use offsets on your barometer, temp and humidity. Your WD was down for a short period of time and when WD imported the missing data the offset was not applied to the new data. Then live data resumed with the offset applied. The dip you see probably is equal to your offset amount for these readings.
As far as I know, I didnt set any offsets in WD.
I did go back to yesterdays graph (which shows problems too) and using WD I wanted to see the times in which these issues cropped up. I took a screenshot of WD with the anomaly…
The times one the outside of the dips is (9:04PM) and (9:29PM) However, when moving the cursor inside the dip, the time reads (2:34 AM to 2:40AM). No idea what happened there. The logging machine was accidentally restarted (bumped the hibernate button) last night after that time (about 10PM or so) so I’m not sure why this is happening.
The time in question is circled at the problem area…
You need to check the log file. Sounds like you have one/some records that are out of time sequence due to the hibernate boo boo, so those are valid values, but they are from a different time of day. There’s a recent thread on here about log file audit tool.
Well, I ran it through the log checker and got this…
WD Logfile Error Checker
Version 0.51 BETA
From WWW.WebsterWeatherLIVE.com
LogFile: E:\weather\weathe~1\logfiles\22009lg.txt
Date: 02-22-2009 at 18:27:55
DAY ORDER ON LINE: 2 Date/Time: 2/9 @ 21:8
PREVIOUS MIN ON LINE: 2930 Date/Time: 2/11 @ 22:0
CHECK TEMP ON LINE: 12093 Date/Time: 2/18 @ 18:32 Value Difference: 8.5
CHECK DEW ON LINE: 12093 Date/Time: 2/18 @ 18:32 Value Difference: 6
CHECK TEMP ON LINE: 12094 Date/Time: 2/18 @ 18:33 Value Difference: 8.5
CHECK DEW ON LINE: 12094 Date/Time: 2/18 @ 18:33 Value Difference: 5.2
PREVIOUS MIN ON LINE: 12109 Date/Time: 2/18 @ 7:1
CHECK TEMP ON LINE: 12109 Date/Time: 2/18 @ 7:1 Value Difference: -16.8
CHECK HUMIDITY ON LINE: 12109 Date/Time: 2/18 @ 7:1 Value Difference: 15
CHECK DEW ON LINE: 12109 Date/Time: 2/18 @ 7:1 Value Difference: -11
PREVIOUS MIN ON LINE: 12811 Date/Time: 2/18 @ 19:0
DAY ORDER ON LINE: 12827 Date/Time: 2/22 @ 18:26
CHECK TEMP ON LINE: 12827 Date/Time: 2/22 @ 18:26 Value Difference: -10.7
CHECK HUMIDITY ON LINE: 12827 Date/Time: 2/22 @ 18:26 Value Difference: -19
CHECK DEW ON LINE: 12827 Date/Time: 2/22 @ 18:26 Value Difference: -18.4
********** COMPLETED **********
LogFile: E:\weather\weathe~1\logfiles\22009V~1.txt
Date: 02-22-2009 at 18:27:59
********** COMPLETED **********
So would I delete these offending lines? but how would I update those graphs after correcting the data.?
maybe you have another copy of WD running…or you have set to use the clientraw as a data source or similar
Hehehe… I ended up clearing all my data, and wouldnt you know I updated my console firmware, and it happened again. This time I verified that I shut down WD and it wasnt running… updated the firmware, and restarted WD when I seen the console was back up and running, and this has happened again.
Is there a way to correct this data?