I have a WMR200A and I'm using it with the VWS software. I frequently have a problem where the connection the the WMR is working fine. Then, when I re-boot my computer for whatever reason and suddenly the VWS software won't connect to the sensors. It won't re-connect no matter what I do. Cycle the USB connection, reboot/reset the WMR display, re-boot the computer, etc. The sensor communications window says that it is connected to the Display, and the blinking LED connection works.
However, none of the sensors connect. The sensors are fully connected to the display unit, the VWS software just doesn't recognize the fact. I can connect to the display and see all sensors using Weather OS 200Pro software. Of course tech support for OSI and AmbientWeather are no help.
I have an Oregon Scientific WMR200CA (console only) equipped with three remote TEMP/RH sensors operating in standalone mode; no internet connection available in my WX-room. Howver, unfortunately, the WeatherOS software that OSI provides with the WMR200A seems to ONLY operate if connected to the internet so that it can 'call home' for instructions and additional data.which, with my standalone system, doesn't work for me. Does ANYBODY know of any 'download only' software that'll just retrieve the.CSV data from the WMR200A and nothing else? I came across a Mr.
Partick Holkenbrink who.used. to have something similar called MATHEL Data Reader, but his website 'date' stopped back in 2009!?!?
Any suggestions, ideas or comments are welcomed! I've been searching around, looking at different data logging systems. River flows in you sheet music. The one that seems to work well for me on Windows is WSDL - I'm using it with a WMR-100 system and it's working fine. The Mathel stuff is available in source code form, so you'll need to spend a couple hundred dollars for software you'll use once.
I don't do Windows development anymore (so I don't have the software) but if you have a friend or relative that does computer stuff, they may be able to hook you up with a copy of the program, ready to use. The USB protocol is 'pretty much' the same for the 100, 200, and 88, from what I've been seeing on the Interweb. Converting your old database to the new database (or getting the new data into your old database) may be a challenge, but that's working. If you were willing to make the switch, wview could be a contender. For me, it's a problem because all of my servers run NetBSD, which isn't supported (because of libusb1.0 support requirements).
It's available for everything but Windows.sorry, but I'm more than a little jaded, so as a genuine 'newbie' to this site, I made no assumptions; hence, my specific restatement of what was needed.and, in this world of 'acronyms-r-us' there are simply too many four-letter acronyms-such as WSDL-to trust GOOGLE or other search engines. So, I simply 'asked' you what you meant.I was not trying to upset or rile you.I thank you for you information. I will now lookup Weather Station Data Logger (WSDL) to see what features and requirements it has. WSDL does produce a simple CSV file with readings - I was able to get that to 'sort of' work.
It's stuck in me 'My Documents' directory and is unavailable to the server, but it is there. I did find a program that looks amazingly like what you are looking for - but it is seriously DIY and I have no idea how you'd implement it on a Windows platform.
It looks like, with a little tweaking, it should do what I need.HOWEVER. (on my system) it compiles, runs, and then fails to find the station. The code is all there, but there's something hinky in the interface that is eluding me right now. This, by the way, is as close as I've gotten to getting something working the way I want it to work.
I'll continue the search and keep you posted.I have a dedicated, standalone, computer that is 'on' only when needed, for TEMP/RH data collection (downloads typically done daily, but always sometime within a week). It's NOT a 'weather' station-I collect data to analyze how well (or not) our evaporative cooler is working.I've used to working with raw.CSV data files, and then transferring them into Excel for analysis, display and archiving. What's that 'template' that you're talking about? Sounds like a structured component of a database or something.I appreciate your answers. Are you familiar with the software named 'DataRecord' that LaCrosse provided for their WS-8610 model wireless, datalogging station?
That's what I've been using. Clicking on the DataRecorder icon pops up a display of previously uploaded values, indexed by a rolling 0-XXXX number. Click on the IMPORT button and any new data in the WS-8610 is uploaded and appended onto the end of the previous data file (.drf), growing its total length. When upload is complete; click on the EXPORT button and a pop-up asks you to select a named.txt file to save the data to. Wordpress content pop-up. I then import that.txt file into Excel.
Freewx
That's the process I'm familiar with.been doing it almost daily for over six years now. What is the process needed to do the same/similar thing using WUHU? The WS-8610U. I had one of those about 4 years ago before I moved up to my WMR100. I too imported the data everyday, but sometimes I found this to be inconveinent. At least with the WMR100, the data automatically goes to the program. Datarecorder didn't offer graphing except with Excell, but the 7 year old computer I was using then, didn't have excell on it.
Besides loading the data, I kept losing my self in it all. I found the program really cheaply made. But that was short lived after the sensor died a week before the console/reciever died. By then I had my WMR100.
For a year I used Weather Display Basic, which was free with 8/10th's of it's features striped. Then when I finally upgraded to Windows 7. I started using WSDL. I've been using them for almost 2 years.
Cumulus reciently added support for the WMR-3.0 series, so I'm now using that. But have WSDL as back up.
I find my self missing WSDL, but I like the high's and lows along with a more readable data file. But WSDL proved more than reliable, so WSDL and Cumulus are both at the top of my recommendation list. Yes, the WS-8610 is a 'bitch' to reprogram every time one of the sensors has its batteries replaced. Definitely NOT user-friendly programming!
Plus it only handled three sensors. Curiously, my first WS-8610U actually displayed 'numbers' for four external sensors, but only three worked. My second (and third) WS-8610 units just displayed three 'numbers.' That's.one. of the reasons why I looked at the OSI stations, I liked their switch-selected programmability of each sensor. Set it once and forget it!
But, I don't care much for their poor RH-sensor accuracy.it's lousey below 25%RH and above 80%RH. AZ CWOP DW6988 (inactive).