wviewweather.com

THogland · Joined: 26 Sep 2005 Posts: 33

Perhaps not the correct way to phrase it, but...

When stopping and restarting wview, wvwunderd doesn't upload any missed uploads. For example, I had a flaky end on my cable between the console and server. I shut wview down at 9:30, re-spliced all the ends, and restarted wview just before 10:30. wvwunderd doesn't seem to recognize that it's last upload was at 9:30, so it waited until 10:30 and uploaded the next current block, leaving an hour's gap in the station data.

I'd like to see it use a marker, so if it found that entry it would upload any data collected since the marker was written. Perhaps a config file entry, or maybe even just have it touch something so it knows the last upload time...

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

This is not possible. Why you ask...

The values submitted to weather underground (and CWOP, this is the same methodology basically) include values not provided by an archive record. They are only present in the LOOP and HILOW packets. So why does that matter?

Suppose you turn off your wview system for 1 day. A day's worth of archive records accumulate in the data logger. But no LOOP packets are being received or "saved" because no wview is running. Then you fire up wview. It will download all of the archive records since the last one it stored in the flat file database (.WLK file) because it does keep a "marker" - really it just looks in the archive file for the last record date and time and uses that.

But you would want wview to send wunderground (and CWOP I guess) update records for the day you had wview turned off, one for every archive record it downloads from the VP data logger, right? What would it use for the day rain as of the archive record it would correspond to - make a guess? You see, that information is not in the archive record so it is lost because you were not running wview. Therefore it is not possible to "back" update wunderground or CWOP because that data is not saved for us in the archive records while you have wview turned off...

I definitely considered this when implementing CWOP (it came before wunderground) and realized it was not possible.

Moral of the story: don't turn off wview, and if you have to, keep the time to a minimum.

BTW, wvcwopd and wvwunderd do not have any intelligence really other than their respective protocols and physical interface methods - the intelligence of what values to send and when it's done belongs to the wviewd daemon based on when he receives a new archive record.

Hope this clears it up...

Mark