Posts Tagged ‘davis vantage pro2’

From console to envoy to crisis (resolved)

Saturday, May 24th, 2008

On Wednesday I installed Weatherlink and connected it to the Vantage Pro2 console. Actually, this didn’t accomplish much except allow me to see what functionality Weatherlink provided. I think I hoped to download and export the historical data which sits on the console (e.g. high/low totals since Feb 2007) but I couldn’t see a way to accomplish this. I’ll probably experiment with afedit and do this manually.

My next task was to configure the Weather Envoy so that I could restore the console to its rightful place in the living room. This was easily done via Weatherlink (and could equally have been configured via wview). I opted for an archive interval of 15 minutes.

Initially, I had configured wview to put archive data into a mysql database. However, I am not convinced that, in the longer term, the slug will cope with wview+lighttp+mysql so I reconfigured wview without the mysql option (actually, this was probably unnecessary since I could simply have switched off mysql via the wviewconfig utility — I did want to upgrade wview to the latest version at the same time but this also failed, probably because I needed to reconfigure radlib without mysql too; it was getting late…).

Restarting wview with the new envoy worked very smoothly. However, a new, more serious problem developed. Having followed the instructions for unplugging the data logger from the console in order to connect it to the envoy, I discovered, on replacing the batteries, that a full quarter of the console screen was blank! There was nothing where there should have been a wind gauge, outside/indoor temperature, and there was also character corruption in the ticker area. My first fear was that in disconnecting the data logger (especially prising out the batteries, which is not easy) I had accidentally damaged the screen.

I sent an email to Davis Instruments and Tom replied next day with some very helpful advice: remove the batteries and any other power source; leave the console without power overnight to fully discharge the screen; and then power it up again. It worked!

Next tasks are to deal with historical data and look at customising the html templates.

Slug update

Monday, May 19th, 2008

Clearly I’m not a blogger at heart. I actually installed Debian on my NSLU2 on 30 March (using the cookbook at http://www.cyrius.com/debian/nslu2/install.html). Connected to a 500gb MyBook everything worked fine. I installed wview and configured it to use the in-built simulator (for testing). That worked fine too (with Apache serving up the results). Well, it worked ok for four days and then I started to get broken pipe errors from one of the radlib message queues. No matter, the concept had been proven.

Then both the Davis data logger and the wireless envoy arrived. Thus I spent yesterday updating Debian (especially openssl); replacing apache with lighttpd; and reinstalling wview to work with the Vantage Pro weather station rather than a simulator.  In the first instance I’ve connected the VP2 console to the Slug. This also seemed to work as it should and I even managed to set the archive interval rate on the console via the slug command line.

So the basic setup is complete (http://slug.begbroke.org/). Next steps are to:

  • Retrieve historical graph data from the VP2 (seemingly easiest to do with the WeatherLink software, so must find working Windows system…);
  • Connect wireless envoy and put the console back where it should be.
  • Start customising the wview html templates.

I have a feeling I will have problems with historical data and archive intervals…

Vantage Pro2

Monday, March 24th, 2008

The Davis Vantage Pro2 weather station has been in operation for just over a year. Only I can see the console and access the data on rainfall, barometric pressure, temperature, wind etc that it’s been collecting and displaying. Hopefully, that will change soon. My intention is to connect a console to a Linksys NSLU2 with (probably) Unslung and wview installed. All the bits, including the datalogger and NSLU2 are on order.