Caution: Data Loss (WMR200)->fixed ,latest update of WD

Archive Archived Weather Display Usage Questions
1

There’s a hangup problem in WD which results in data loss. I don’t know if it’s specific to the WMR200 or not. Users of other equipment might be able to verify this one.

It seems that when I do:
CONTROL PANEL >> DAYA LOGGER >> [CANCEL]
the WD display hangs up on me (vers 10.37h bld7).

  1. The clock below the Weather Icon stops ticking i.e. it
2

found and fixed that problem (a timer being turned off instead of on)
in this new .zip update:
http://www.weather-display.com/downloadfiles/WeatherD.zip

3

See what I mean … problem fixed within 30 minutes.

THANKS BRIAN … YOU’RE A STAR.

HAPPY NEW YEAR

4

Hi,

New to forum.

I’ve just purchased a full version WeatherD and installed (via) zip extraction Ver 37h to my WeatherD Directory. I’m currently running WMR200 Ver 2.8 Data Gatherer. From this thread it appears there’s a newer version: 3.1. Where do I find a copy on The main WeatherD site? Also what’s the cleanest (and easiest) way to keep WeatherD updated for all software upgrades applicable to to WMR200A installation?

Thanks

RiverRat

5

Download the latest versions here:

http://www.weather-display.com/downloadfiles/WeatherD.zip (version 10.37h build 7)
http://www.weather-display.com/downloadfiles/wmr200.zip (version 3.1)

Title bar of “WMR200 Data Gatherer” however still says Ver 2.8.
I’m sure Brian will have this one fixed soon.

Rainer

6

ops, I see that for the wmr200,I have it where the caption title is set in the code (to say wmr200), and I had not update that
but I had updated the file properties (right mouse click the wmr100.exe program) to 3.1
(included in the full install or .zip download)

7

Thanks Guys,

That solved it. Another Question. I’ve set the permissions in Vista Ultimate to run WeatherD.exe and WMR100.exe as “administrator” for all users but am still getting “unknown publisher” notification and “user control” notification at start up. Are there other programs that initialize at program start of WeatherD which require the same change. It’s a pain acknowledging the software everytime I boot it and allowing “user control” to run the application. And no, I don’t want to turn off user control except for WeatherDisplay related applications.

Thanks,

8

In what directory did you install it?

9

Niko,

It’s installed installed in the default directory, c:\program files\wdisplay.

Any Ideas? This is clearly a Vista issue; other than convincing Brian to get the software Microsoft certified.

No Rush Brian. :lol:

RiverRat

10

Vista seems happiest if WD is installed to c:\wdisplay

I am not sure how to get WD Microsoft certified
or to get it set to by pass the user access control
anyone know?

11

Brian,

I’ll research how to get you and WD “Windows Vista Certified” if you’ll tell me an easy way to migrate the application to c:\wdisplay without screwing up the Registry. I assume Vista Certification it’s largely bureaucratic bovine scat, which unfortunately, I’m good at.

Also, I prefer to keep my application data on a separate drive for back up purposes (in my case e:\ drive). It shortens the back up time on c:\ and spreads the risks. Do you have a pointer on the forum to instruct me how to do this?

Please remember in all of this I’m a user and not a programmer, although I’ve been around PCs for 20+ years and sometimes use “computerese” far in excess of my actual knowledge. :lol:

Cheers,

Tom the RiverRat

12

Hi
you should be able to copy over to the c:\wdisplay location OK
if you have set specifly to use a certain logile or datafile or webfiles or clientraw file location, then reset those though

13

27 12 2007 9 4 40.8 80 35.1 30.062 0 2 22 0.000 0.000 0.000 0.000 40.8
27 12 2007 9 5 41.2 78 34.8 30.062 0 1 68 0.000 0.000 0.000 0.000 41.2
27 12 2007 9 6 41.2 78 34.8 30.062 0 1 68 0.000 0.000 0.000 0.000 41.2
27 12 2007 9 7 41.2 78 34.8 30.062 0 1 68 0.000 0.000 0.000 0.000 41.2
27 12 2007 9 8 41.2 78 34.8 30.062 0 1 68 0.000 0.000 0.000 0.000 41.2
27 12 2007 9 10 27.7 78 21.7 30.062 0 2 33 0.000 0.000 0.000 0.000 27.7
27 12 2007 9 11 27.7 90 25.1 30.062 0 2 90 0.000 0.000 0.000 0.000 27.7
27 12 2007 9 12 36.0 82 31.1 30.062 0 3 103 0.000 0.000 0.000 0.000 36.0
27 12 2007 9 13 42.4 75 35.1 30.062 0 2 72 0.000 0.000 0.000 0.000 42.4
27 12 2007 9 14 42.4 75 35.1 30.062 0 2 28 0.000 0.000 0.000 0.000 42.4
27 12 2007 9 15 42.4 75 35.1 30.062 0 2 63 0.000 0.000 0.000 0.000 42.4

Brian,

Please note above from just a few minutes ago. This is copied from 122007lg.txt and occurred at program start “27 12 2007 9 8” temp and hum are spurious. these were not the current reading on WMR200. The data above the 3 entries are from the datalogger catchup for the down time, which in total was about 4 hours. The data after the 3 spurious entries is consistent with the WMR readings at the time. Appears something is still not right during the transition from logged to current data during start up.

Let us know what you find. It’s causing the charts to spike wildly.

Thanks

RiverRat

14

I still have spikes as well.
What is happening here is that when the WMR200 Data Gatherer needs to catch up a couple of hours of missed data from the Data Logger there is “Live Data” streaming in from the WMR200 Console as well. Brian somehow is still not processing this live data correctly.

Your 3 bold lines is probably the live data streaming in during the missed data catchup process. It almost certainly always happens with to me after a startup.

I also still have the following problem at startup:
I

15

[quote author=katropa link=topic=28634.msg227889#msg227889 date=1198778835]
I still have spikes as well.
What is happening here is that when the WMR200 Data Gatherer needs to catch up a couple of hours of missed data from the Data Logger there is “Live Data” streaming in from the WMR200 Console as well. Brian somehow is still not processing this live data correctly.

Your 3 bold lines is probably the live data streaming in during the missed data catchup process. It almost certainly always happens with to me after a startup.

I also still have the following problem at startup:
I

16

It’s fact. I analyzed the wmr200history.txt file and I can see live data arriving during the “missed data” pickup process. The spurious spikes always occur in the 1st few minutes just after startup.

I also had Vista going to “Sleep” and have switched it off as I thought that that might be the cause of WD (wmr100.exe) hanging up on me and subsequently loosing data when restarted. Since then I’ve not had any hang-up issues and/or data loss. What might be happening here is that wmr100.exe is “sleeping” and when you wake your machine it resumes from time of “wake up call” as if nothing has happened. The sleeping data is lost. One would expect that the WMR200 Data Logger would still have the data … it doesn’t … which must mean that it got picked up by wmr100.exe during the sleeping process (catch 22).

Does the “WMR200 Data Gatherer” need to be shut down independently from WD? I don’t know … I have not had any concrete reply to that on this forum yet. If so, I would suspect you’d have to do that before you shut down WD.

Can the “WMR200 Data Gatherer” run independently from WD? If the above is true then that would not be possible. I’d also like to know that one.

Rainer

17

Thanks Rainer,

It sure would be nice if we could put Vista to “Sleep” and “Wake it up” without losing data in the process and avoid the spike at start up. I guess we’ll to wait and see what Brian can do to sort this out.

Anyone else using a WMR200 have any ideas?

Tom the RiverRat

18

if the wmr200.exe is still sending data requests to the wmr200 console, then the wmr200 console will not be storing any data
i.e when you close WD you also need to close the wmr200.exe program ( i guess I better force a close of that when you exit WD)

19

Conclusion:

  1. Always shut down the “WMR200 Data Gatherer” FIRST before you shut down WD (or else you’ll lose data).
  2. The “WMR200 Data Gatherer” CAN NOT run on its own although it’s an independent process.
  3. If the “WMR200 Data Gatherer” runs on it’s own it WILL NOT store any data.
  4. The “WMR200 Data Gatherer” CAN NOT collect data while VISTA is sleeping.
20

Are you sure on that?
Even if separately stopped is it possible that the ‘WMR200 Data Gatherer’ could have just requested, but not yet received some data?
Perhaps Brian could comment?

Would it be possible for WD while closing to take measures to ensure that the data gatherer has had time to shut down properly?

It looks to me as though WD tells the data gatherer to close. Maybe it could then wait for the data gatherer to send a signal which indicated that it had tidied up its connections and was about to really close and thus it is safe for WD to complete its shutdown?

Just a thought…