The next message in this topic is offered as a possible FAQ to help people set up WD to read data from Meteohub using the ‘Logging Protocol’.
If it’s okay, perhaps one of the moderators could move it to the WD FAQs section?
Thank you. 
You’re welcome, thank you for creating it 
yes, thanks skyewright
Thanks for this FAQ, followed it and it works fine. Running for about a week with this configuration. Just one glitch where I started the PC and WD up today and it only collected about the last 30 minutes of data even though it had been switched of all night. Other that tha it’s been working very well. Just need to add a large battery to the Alix.1D now to make sure it carries on logging when the power fails… every other day for about 30 seconds to 2 hours near Ross On Wye!!! Bet you get more reliable power on the Isle of Skye!
Many thanks. Just got to sort my WDL now.
If the data is in Meteohub you ought to be able to get it into WD by careful manipulation of the [Davis Download] values, but it you also collect data that is already in WD you’d get duplication in the log files which would need to be cleared up, so the ideal would be to revert to a backup first then bring that up to date (I’d also take a backup of what you already have before doing anything!).
Since a new overhead line was installed about 14 years ago we get less powercuts, but being a very long way from the power stations and near the end of a 15 mile ‘spur’ on the grid we get a very variable supply. All my computer gear (and most of the weather stuff counts as computer gear) is on UPS’s!
I found that even on an APC “Back-UPS” the (very simple) standard ALIX-1D PSU was not able to withstand the line fluctuations. The fluctuations caused the ALIX-1D to crash (lock up) intermittently (nothing else I have exhibits the same problem on the Back-UPS’s). I initially solved that by moving the ALIX-1D on to an APC “Smart-UPS”, but have now replaced the standard PSU with a better one which is quite happy on a “Back-UPS”.
N.B. With that PSU you also need a DC plug adapter to suit the ALIX-1D.
I will be looking here as I just purchased the ethernet weatherhub so I dont have to keep this thing attached to my computer. I wanted a wireless one but could not find one…is there such a thing so I don’t have to use ethernet?
More questions about WD and Meteohub. I just recently setup a Meteohub v4.2a system using an ALIX 3D2 with a Vantage Pro2 Plus station. Everything for the most part seems to be working fairly well. I have a WD Live site setup and a PWS on Weather Underground. My ultimate goal is to be able to feed data to my home PC to WD software. Now I’ve setup my WD software as described in this forum and the archived data started downloading. I’m not sure what’s going on from here because some strange things are happening. If I read the data correctly when the downloading takes place it appears that the dates shown are in the future. For example, 20090421xxxxxx, etc. Isn’t this format YYYYMMDDHHMMSS? The downloads will run until WD shuts down as described. Another thing I notice is that the download repeats itself. The same dates are being downloaded everytime I start WD. I have the correct date and time set on both Meteohub and the weather station. Once the download of the archived data is complete does the WD main screen display data in near real time? I might also metion that I am using two copies of WD on the same computer. They are on different drives and have different folder names. Any help or assistance would be greatly appreciated. Thank you.
Yes. It is a UTC date stamp.
That an example just grabbed from my Meteohub. Local time is 17:29 on 3rd April 2009. The time stamp is 16:29 and 28 second UTC on 3rd April 2009.
So if your timestamp is correct it is showing 21st April! :?
WD should only be asking for data from before “now”.
If the clock was wrong on the WD computer and it asked for “future” data I’d normally expect Meteohub to respond that it was a future time/date (unless of course its clock was wrong too).
You can generate a sample like the above, showing the “latest” sensor reading on the Meteohub using a url like this in a browser:
http://192.168.0.78/meteolog.cgi?mode=data&type=xml
Just replace 192.168.0.78 with the IP of your Meteohub.
I suggest checking the value in the [Davis Download] section of WDISPLAY.INI
That sets the time and date (in local time) that WD starts looking from when it starts up. When you have just shut WD down from a normal running state it ought to be set to within a minute of when you shut down.
Multiple copies should not be a problem as such. I used to do that (with one connected to a WMR200, the other connected to Meteohub) before moving fully to Meteohub.
If the above doesn’t give clues that lead to a solution, a copy & paste from WD => View => WS2010-13/WS2500 data logger setup/info saved as a text file and attached to a message might help with diagnosis.
N.B. Grabbing the text to the clipboard can be tricky. [Ctrl][A] doesn’t seem to work, so what I do is [RightClick][Select All] then [Crtl][C]. As soon as WD writes text to the wind the Select All is lost so you might need to try several times before you grab a goo copy.
What version of WD?
I am using 10.37N build 20. I’ll have to try experimenting a little when I get home to my PC. I’m at the location where my VP station is at right now. I can access my home PC using UltraVNC but that sometimes gets a little frustrating when the connection is slow. Thanks for the info.
Michael
I attached a txt file of the data that is being downloaded from Meteohub. I aborted the forever continuing archive download and viewed the data that is being downloaded using WD => View => WS2010-13/WS2500 data logger setup/info. It does appear that data is being downloaded. How do I view this information on the main screen or is that possible? Thank you.
Michael
meteohub data.txt (1.46 KB)
Which includes lines like:
increase time 1770 getting missed data 20090407090400 20090407090500Which is (as you observed earlier) is requesting future data!
Is there anything different to that right up at the start of the text?
Maybe I have some long forgotten debug setting ticked, but I see far more detail than that.
Attached is a sample just collected on my ‘test bed’ setup using the latest build of WD (10.37N build 22) and v2.4a of Meteohub.
Take a look in the folder:
wdisplay\logfiles
In there you’ll find 42009lg.txt
If the data has been collected, there should be evidence in there.
What did you find when you took a look in WDISPLAY.INI?
Something else to check…
Are you 100% sure that the IP and port set in
WD => Control Panel => COM Port => TCP/IP connect on to Davis VP IP/VVP/Meteohub
are correct?
i.e. if you use those values as part of a URL like
http://192.168.0.78:80/meteolog.cgi?mode=data&type=xml
in a browser, do they produce a sensible result?
ITS WORKING! I finally got it working. Your last suggestion I think was the clue. I know I was able to access Meteohub remotely because I kept on checking the setup to make sure everything was where was suppose to be. My WD live site was working fine along with my PWS on Weather Underground. When I tried looking at data with the URL you suggested but using my IP I just kept getting an error message. I did some reading in the Meteohub manual and saw something about data ports. I believe there are 4 or 5 ports for data starting at 5500 and going to 5558. I thought if I access the router and open those ports it just might work. The hard part is that the station, router and Meteohub setup are a 175 miles from my home so if something goes wrong its a long drive to fix it. I decided to take the gamble. I opened the ports and rebooted the router. After a few minutes agonizing minutes I was able to access the router and Meteohub. I then started WD and changed the port setting in the TCP/IP setting from 80 to 5500 then all of a sudden readings started popping up. I opened up my WD live site and the readings were the same as I was getting on WD. Now all I have to do is get WD configured the way I want and start building a website. Thanks for all your help. These forums are great!
Glad to hear it!
I thought it might…
While testing a new facility yesterday I accidentally recreated the same sort of feedback text that you were reporting, so that gave me the clue!
An odd choice, because port 5500 is normally a serial-to-ethernet-bridge reflection of the actual feed from your weather station (strictly speaking, weather station 0, since with Meteohub v4 and above you may have more than one connected).
The logging prototcol talks to Meteohub’s web server with is usually on Meteohub’s port 80 or port 7777.
Most likely the difference is somehow down to the way a router is configured at some point?
If it works that’s the main thing!
Indeed!
This topic has drifted a long way from its original purpose as a mechanism for adding an FAQ, so I’m now locking it.
If you have questions about using WD and Meteohub together you are very welcome to ask, starting a fresh topic in WD Questions.