RE: Berkeley Windtalker Update

From: rossb@WellsFargo.COM-DeleteThis
Date: Mon Jun 28 1999 - 13:32:02 PDT


Received: from opus.hpl.hp.com by jr.hpl.hp.com with ESMTP (1.37.109.24/15.5+ECS 3.3+HPL1.1) id AA296812454; Mon, 28 Jun 1999 13:40:54 -0700
Return-Path: <rossb@WellsFargo.COM-DeleteThis>
Received: from hplms26.hpl.hp.com by opus.hpl.hp.com with ESMTP (1.37.109.24/15.5+ECS 3.3+HPL1.1) id AA238482453; Mon, 28 Jun 1999 13:40:53 -0700
Received: from kim.wellsfargo.com (kim.wellsfargo.com [192.246.108.37]) by hplms26.hpl.hp.com (8.9.1a/HPL-PA Relay) with ESMTP id NAA23527 for <wind_talk@opus.hpl.hp.com-DeleteThis>; Mon, 28 Jun 1999 13:40:48 -0700 (PDT)
From: rossb@WellsFargo.COM-DeleteThis
Received: from unixm2.WellsFargo.COM (unixm2.wellsfargo.com [10.26.5.254]) by kim.wellsfargo.com (8.8.8/8.8.8) with ESMTP id NAA05000 for <wind_talk@opus.hpl.hp.com-DeleteThis>; Mon, 28 Jun 1999 13:29:20 -0700 (PDT)
Received: from xcgi-aztem-01.wellsfargo.com (imc3.wellsfargo.com [10.27.114.253]) by unixm2.WellsFargo.COM (8.9.3/8.9.1a-19981215) with ESMTP id NAA07464 for <wind_talk@opus.hpl.hp.com-DeleteThis>; Mon, 28 Jun 1999 13:32:10 -0700 (PDT)
Received: by imc3.wellsfargo.com with Internet Mail Service (5.5.2516.0) id <MFP1G88J>; Mon, 28 Jun 1999 13:32:10 -0700
Message-Id: <970292C22686D2118A410001FA7E02C60237FF98@xcem-casfo-09.wellsfargo.com-DeleteThis>
To: wind_talk@opus.hpl.hp.com-DeleteThis
Subject: RE: Berkeley Windtalker Update
Date: Mon, 28 Jun 1999 13:32:02 -0700
X-Mailer: Internet Mail Service (5.5.2516.0)
Content-Type: text/plain; charset="iso-8859-1"

Those trees of which Dave writes have grown considerably since we put up the
sensor. In years past it consistently read two mph below call-of-the-wind.
Last year it seemed to read lower.

-----Original Message-----
From: David R. Fielder [mailto:dfielder@cooper.cpmc.org-DeleteThis]
Sent: Monday, June 28, 1999 11:28 AM
To: Multiple recipients of list
Subject: Berkeley Windtalker Update

Stopped in at the Berkeley Yacht Club on Sunday, waiting for wind to
appear. Met Serge and saw that the anemometer seemed to be actually
stopping spinning frequently (as noted by Jay, too), compared to the
adjacent unit (yacht club's, better location), perhaps explaining the
frequent "zero mph" low end readings. Got up on roof, but not clear how to
dismantle/clean the sensor head, so took a chance and sprayed some WD-40
into the mechanism. My perception was that it started spinning faster,
with fewer, if any, complete stops. Also, when I got home, it was reading
1-13, instead of 0-13.

Also, inquired with Serge (yacht club live-in maintenance guy) and another
member regarding if relocation of the sensor unit would be possible.
Current location may be partially affected by large tree to immediate SE.
Certainly, we all know that SE winds cannot be read by it. However, with
any barrier behind the unit, wind from in front may also be affected. I'd
like to explore mounting unit above the second floor penthouse (where Serge
lives), which might improve readings from all bearings. Would be
questions, including what length of signal wire unit will support. Also,
from a past career, I know there are fairly simple yardsticks about how to
locate wind gauges vs. obstructions, which I'd want to evaluate.

Finally, it may be time to consider replacing the sensor head, if not whole
unit (computer, etc.). Does SFBA support such activity? How would
decision be made?

In closing, I then made mistake of rigging and launching in the gusts
around 4:45PM or so. Got halfway to Emeryville on nice plane and then swam
most of the way home, with a partial sailboat tow..... :(
When will I ever learn.

                David
=========================================================
"Rig for the Moment" DRF's Statistics:
  USWA Member #US212 185 lbs/6'6"
  Berkeley-His Lordships Bic Veloce 278 XLS
  Marina Bay & Wherever Windwings 7.5/6.7/6.5race/5.8/4.9
=========================================================



This archive was generated by hypermail 2b29 : Mon Dec 10 2001 - 02:35:45 PST