This is a little convoluted - so please bear with me…
I owned a WMR100 - it worked flawlessly with Weather Display - so I bought the full version to be able to send data to the web. Loved it. Then one day the wind sensor on the WMR100 dies - so I got a new station - the WMR200.
I hooked up the WMR200 with no issues - and started up Weather Display after upgrading to 10.37j Build 09.
In the Control Panel I changed my station type to WMR200.
After a little bit of fiddling around with the USB plug - all the sudden the wrm100.exe program fired back up and I started seeing data… and that was when I started seeing strange things too.
First thing that was “odd” is the barometer reading on the unit was 29.38… the “recorded” entry in WD was 28.86 (or something - the point is the values were different) - so - I fixed this with an offset in WD… but not sure WHY I had to do that (besides this is trivial).
The next thing I notices was bad - after a few hours - all my data in WD was flat-lined - nothing new… but the WMR200 base unit continued to record data. The only thing that seems to “fix” that is an unplug - re-plug in of the usb along with a (or several) restarts of the WD software including wmr100.exe…
The only thing I can say for sure - since I have not sat at the pc and waited for the event to happen - when I come back (if I left the PC with wmr100.exe open and watching the data stream by) - it is ALWAYS closed (as if it crashed and restarted) and there are only 2 lines at the top:
USB opened OK
send PC ready result 1
Nothing in the forums offers me much hope - nor in the bug tracker…
Thoughts and suggestions will be greatly appreciated.
I don’t think the WMR100.exe should be running with the WMR200.
Go into the station setup page. On the OS WMR100/200 page select “none selected”. Press OK.
The go back into the page again and re-select the WMR200, press OK.
Then click on Save & Exit to close WD and restart it again.
If this doesn’t work then do the same again but instead of re-selecting the WMR200, select “Stationless” and restart WD.
Once WD has restarted go back into the station setup page and select “none selected” on the Stationless page, go into the WMR100/200 page and select the WMR200 again and click OK.
With a bit of luck the WMR100.exe won’t start and you should get readings from the WMR200.
Did all you said - and different patterns of it - with full system reboots after the first go-around…
One thing WAS different - after going from no-station, stationless to clicking the WMR200 radio button - a screen I hadn’t seen before poped open and downloaded a bunch of historical data from the WMR200… And then the window closed and all looked good…
BUT - wmr100.exe is running - and I see data going by when I open it. When I put the mouse over it down in the systray it does have a context box that says “WMR200” - but it is wmr100.exe running.
I’ll have to get back to you on whether or not this fixes the issue with the dtat stream going silent after several hours.
wmr100 needs to be running to get the data to WD. When you first start WD wmr100 starts and collects the missed data (logged data) then it closes and reopens to collect the live data stream from the console. What you are seeing is normal.
S
Yes wmr100.exe is a normal thing to expect in the systray when using a WMR200 but, to clarify, its role is only in collection of live data after ‘missed data’ has completed, i.e. don’t expect to see wmr100.exe running during ‘missed data’.
N.B. I realise you said that you left wmr100.exe open in this case - but if you ever want to hide that window after opening it be careful to use the ‘Minimise to Systray’ arrow rather than the “Close”. If you use “Close” you will halt collection of data from the console (and the console will start logging). If this happens and you are quick you can just restart live collection it by running wmr100.exe - but if there has been a delay you might be better to close WD and pick up the ‘missed data’.
The problem still exists #-o - things ran for several hours last night after performing the above procedures - then all of the sudden a few minutes after 11pm EST the software stops receiving a signal and all my readings flat line at their last values. It then takes several software restarts - and USB plugging / unplugging to get data flowing again.
And yes - I have been careful to send the wmr100.exe to the systray - NOT close it. (learned that long ago).
My point is - when the data is NOT flowing anymore and I return to the PC to discover that - When I left wmr100.exe was open and things were scrolling past… when I get back t the PC it’s in the systray and only contains the 2 lines posted earlier.
It appears as if it crashes then restarts and buggers up the USB connection.
Also - after restarting this morning - I did not get the missed data window - but it did seem to pull old data because the high/low data since midnight displayed…
Just a thought, but it might be useful to know that the wmr100.exe gatherer restarts itself regularly (see Brian’s comments under thread ‘wmr100.exe restarting?’).
So it may not be crashing, it might be restarting but then not be re-establishing the USB connection. It restarts just after the hour, once every few (~4) hours. You say the data stopped just after 11pm EST so that would tie in.
Glowingsheep -
That thread certainly could be it - I’m at 3.6 however… But that would very easily explain what I’m seeing… so then the question becomes - why can’t it re-establish the USB connection to the WRM200 when it worked great with the WRM100?
P.S. - looking back over the last several “stops” in data collection - they are all shortly after the start of a new hour.
Aye, sounds like it’s related to the restarting then.
But did you say you’re on data gatherer (wmr100.exe) version 3.6 ?
If I double-click the icon in the system tray, it says I’m on version 3.8.
(Although, just noticed the file properties, version tab says 3.3.0.0 :?)
Anyway, looks like your gatherer, wmr100.exe, may be out of date; the file has got out of sync somehow. So I think you should try grabbing the latest .zip (ie ‘Weather Display zip of the main .exe file’ - the 3rd listed download - from the downloads page), stop WD and slap those files into your wdisplay directory and have another go. Make sure the gatherer says version 3.8.
Did exactly this - and it says version 3.6 after restarting - also on file copy it was the same date on the file… so I’m not sure where your version 3.8 comes from!
Just checked. Mine shows 3.6 in the title bar too! If the exe is dated 14th April then should be the latest one, regardless of what the version number says.
The data gatherer is the green disc with a lightning flash in the systray.
Double click to open.
Version number is in the title bar.
N.B. As mentioned earlier, when you are done viewing the window, use the arrow to minimise rather than the X to close!
Sorry to report - it still does it… at about 10:30 last night - it just stopped getting data from the base station… the same symptom too - the wmr100.exe just has those 2 lines in it.
Closing the app (and wmr100.exe) unplugging and replugging in the USB, then restarting the app… seems to be the only fix.
This stinks. It worked so well with the WRM100 station.
Try changing your USB connection. I had this problem, when I changed my connection which was through a hub it disappeared. I now use a usb connection thats directly connected to the motherboard. Also be careful with how the cable is routed if its near high voltage cables it may be getting interference. If this doesn’t work try a different cable.
S
I’ll give this suggestion a try when I get home tonight - the cable routes the same way as it did for the WMR100 - and it’s the same cable - but it DOES go past speakers (magnets) and the power strip - and I suppose different things could have different tolerances to interference.
Here’s another data point for troubleshooting… very odd one I might add…
Like I said last night the unit appeared to stop communicating a around 10:30PM… here’s a snip of the data captured (sent) to WUnderground…
00:31 59.2
OK - I have moved USB cables around - different cable too - directly into the PC - no hubs or anything else in the way… it seems to happen “less” - but that’s a pure observational datapoint…
Someone had mentioned that wmr100.exe restarts after the top of the hour - and I’m seeing lockups in other times than shortly after the hour rolls… is there a log entry somewhere that will show me WHEN wmr100.exe restarts - I’m thinking that would be a good thing to correlate against the data I’m seeing.
