Red-Dave
Weather Geek
Senior Member

Offline
Posts: 80
|
 |
« on: March 02, 2012, 08:22:49 PM » |
|
So, help me out here. My VWS setup has been quite solid for a few years. I haven't changed anything in a long time. Then I noticed yesterday that all of the scales in my graphs were incorrect. For instance, the image you see here is for a graph that SHOULD be Indoor Temp for the previous 6 hours. That's what I am asking it to do, but this is what I now get. Not even sure where to start looking for this one because I don't think I've ever seen anything like this. More of this odd carnage can be seen on my site. I'll take any ideas! Thanks guys.
|
|
|
|
« Last Edit: March 02, 2012, 08:25:53 PM by Red-Dave »
|
Logged
|
|
|
|
|
stevebrtx
|
 |
« Reply #1 on: March 02, 2012, 09:13:14 PM » |
|
It appears that it's displaying 30 hours, right click on the graph and see how many hours it's set for. Don't know why it would change.
|
|
|
|
|
Logged
|
|
|
|
Red-Dave
Weather Geek
Senior Member

Offline
Posts: 80
|
 |
« Reply #2 on: March 02, 2012, 09:25:20 PM » |
|
It's set for 6 hours. But no matter what I set it for, it never snaps to what I am calling for.
|
|
|
|
|
Logged
|
|
|
|
kwikwater
Member
Offline
Posts: 5
|
 |
« Reply #3 on: March 02, 2012, 10:03:47 PM » |
|
I'm with ya!! Somebody figure this out!! Daylight savings time has always beatr up my system and now, I'm guessing it has to do with Leap Day. My database file and of course teh graphs all locked up at 22:10, 3-1-12, but shows it as 22:10, 3-2-12, which is still hours, from now. I've deleted, renamed and reformatted WAY too many things in the dbase.cxv file, that I may never recover!!! I'd consider Uninstalling VWS and reinstalling, but it will use the same dbase files..!!!! I'm on the HELP list!!! and the worst part is, it won't upload to WU correctly as they've cut me off. GGGrrrrr....
What brought it to my attention was that my graphs that I have set to 24 hours of records were displaying 48 hours and wouldn't change no matter how I approached them. Even Deleted and rebuilt a couple, so knew it was database driven. I usually get something like this when the db is getting full, which it is.
KW
|
|
|
|
« Last Edit: March 02, 2012, 10:10:28 PM by kwikwater »
|
Logged
|
|
|
|
kwikwater
Member
Offline
Posts: 5
|
 |
« Reply #4 on: March 02, 2012, 10:16:37 PM » |
|
Red Dave. On closer look you have exactly what I got! Do you upload to any websites? Is that working for you? Please post the cure when ya stumble into it!!
THX!!!!
|
|
|
|
|
Logged
|
|
|
|
|
|
Red-Dave
Weather Geek
Senior Member

Offline
Posts: 80
|
 |
« Reply #6 on: March 03, 2012, 12:22:20 AM » |
|
I did find one clue. I have a Davis WMII with WeatherLink and VWS. VWS runs 24/7 and opens WeatherLink once a day to clear the archive. I just noticed that the date on my station was 3/3. (Today is of course 3/2) So, I closed VWS, opened WeatherLink and when I tried to open a bulletin window it downloaded the station and asked me if I want to correct that data for Leap Year. I clicked yes and then used WeatherLink to continue on to resetting the improper date on my WMII. When I fired up VWS again all of my graphs were still funky, but I suspect it is because they are looking at data with an erroneous date stamp. It's my hope that after 24 hours progresses that the graphs will straighten out. We'll see...
Also I just dug into my "daily" folder where there is a txt file for each day and here's what I found. 2/29 looks fine (24 hrs of data stamped every 30 mins) 3/1 has 1 record in it from 11:30pm 3/2/ has records only from 7:00pm to 11:30pm then there is a 3/3 file which appears to have data in it recorded today- and it stops cold at 6:30pm which is when I started messing around with this.
I'm not sure if I sould try to right that or just let time pass. Again, we'll see...
|
|
|
|
« Last Edit: March 03, 2012, 12:49:17 AM by Red-Dave »
|
Logged
|
|
|
|
|
stevebrtx
|
 |
« Reply #7 on: March 03, 2012, 09:00:40 AM » |
|
I'm on p46 and have graphs with 24 and 120 hour cycles and no problems. I do run 24/7 and do not (yet) have Weatherlink so those may be the differences. But VWS handled leap day with no problem.
|
|
|
|
|
Logged
|
|
|
|
|
racenet
|
 |
« Reply #8 on: March 03, 2012, 09:22:34 AM » |
|
Once the date on the station is corrected to match the date on the computer (which I assume is correct), give VWS at least 24 hours to right itself.
|
|
|
|
|
Logged
|
|
|
|
Red-Dave
Weather Geek
Senior Member

Offline
Posts: 80
|
 |
« Reply #9 on: March 03, 2012, 10:27:31 AM » |
|
It's now been 9 hours since I resset all the dates and my graphs seem to be stuck. They haven't progressed at all. The station was the only thing that was wrong. The computer date was correct and in turn VWS was too. 
|
|
|
|
|
Logged
|
|
|
|
|
stevebrtx
|
 |
« Reply #10 on: March 03, 2012, 03:13:43 PM » |
|
24 hours? When I make changes they snap almost immediately. I'm on p46, you might want to step back a bit and see if the problem persists.
When I shut down and make changes to the dbase.csv and restart, as soon as it picks up the sensors it builds new graphs, I've never seen anything take longer than an hour and that's only when you correct the rain amount for the day.
|
|
|
|
|
Logged
|
|
|
|
Red-Dave
Weather Geek
Senior Member

Offline
Posts: 80
|
 |
« Reply #11 on: March 03, 2012, 10:34:01 PM » |
|
I did figure out that the reason my graphs weren't advancing was because somehow they were looking into the future because of whatever the problem was (maybe I even caused it). As of this morning they all were stopped at 6:30 this evening. Once 6:30 today passed, they began to advance again. What a mess data wise. I won't even try to clean that up. I think the leap year hiccup, or my attempted adjutments caused the database to have an extra day in it. So, the graphs weren't advancing because yesterday (3/2/12) before I strated "fixing" things there were entries in the database mistakenly marked 3/3/12 and timestamped all the way up to 6:30pm (the time I adjusted the clock on my WMII). Those data points remained there because I never figured out where they were located. But once "real time" advanced past that point, it began tracking again. You can see the reamins of it for another day or so on my site. Look at 6:30 where it picks up again. That might not solve your problem kwikwater, but perhaps there are at least clues in there?! 
|
|
|
|
|
Logged
|
|
|
|
|
racenet
|
 |
« Reply #12 on: March 04, 2012, 09:51:31 AM » |
|
I did figure out that the reason my graphs weren't advancing was because somehow they were looking into the future because of whatever the problem was (maybe I even caused it). As of this morning they all were stopped at 6:30 this evening. Once 6:30 today passed, they began to advance again. What a mess data wise. I won't even try to clean that up. I think the leap year hiccup, or my attempted adjutments caused the database to have an extra day in it. So, the graphs weren't advancing because yesterday (3/2/12) before I strated "fixing" things there were entries in the database mistakenly marked 3/3/12 and timestamped all the way up to 6:30pm (the time I adjusted the clock on my WMII). Those data points remained there because I never figured out where they were located. But once "real time" advanced past that point, it began tracking again. You can see the reamins of it for another day or so on my site. Look at 6:30 where it picks up again. That might not solve your problem kwikwater, but perhaps there are at least clues in there?!  There is your 24 hrs. 
|
|
|
|
|
Logged
|
|
|
|
|
|
|