FLATLAND96: Site 3 Messages, 93 Entries..

Site Visitation Log Entry
=========================

Tech: JM
Weather: indoors
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Bench Test and Station Configuration Loading

Station #3
I put in the 'correct' configuration and started the EVE running.
GOES transmit is up.
No logger / radiation stuff, or TRH for now.
FreeWave seems to be sluggish, but is working.
jm

Yesterday, 6/9,96,
Kurt & I went to station 3 to finish some of the setup.
During the visit we were unable to talk to EVE with the Compaq.
It appeared that the Compaq wasn't transmitting to EVE so i cycled
power on EVE to observe the bootup sequence.  At first that went OK,
however because the Compaq still wasn't sending to EVE, i tried it
again.  On the second power cycle of EVE, it died with only the
boot message:	adding 3 symbols to the table.
given instead of the entire bootup sequence of EVE.

We brought the box back to the trailer and apparently 'fixed' the problem
by removing the DCOM 3V battery (which read 3.15V) and letting it 'flush'
the non-volatile.  We then were able to download a config file and run
'properly.'   The box was powered down overnight, powered up today to 
verify operation and then.

Today, 6/10/96, the box was installed back on the station.
At that point it was working, but when Kurt went into 'entersys' - 'goes' 
- 'self-test' it once again died.   The symptom was that all files in the
non-volatile got erased, including the config.dat.

Later, we went back to the station during a lull in the rain and i was
able to download a correct config from the Toshiba and restart normally.
HOWEVER, we decided to replace the VME power supply in hopes that is where 
the problem may be.   Upon power up, the boot sequence was wrong.  It turned
out that the config.dat was corrupted but only slightly.  i copied the
backup sta003.dat to config and restarted: that worked.

Conclusion: DCOM332 has problems or much less likely the software.  We'll 
buy some new 3V batteries and replace the existing ones in hopes that'll help
the problem.

the prop vane boom was aligned, and the boom azimuth was set to a nominal of
135.0 deg.
the prop has a slight bend to the shaft, but performance seems to be OK
the ATI sonic was zeroed, and leveled to better then a 10th of a degree.
a problem exists with the tsfc sensor, but it was left on the station
to see if it would "dry out" and come back.

Work at station #3:

Moved radiation stand several feet north to avoid shadow of PAM
mast in late afternoon.
Installed Licor pyranometer S/N 7121.
Noted REBS Q7 net radiometer is S/N 94197.
Leveled both radiometers.

Installed bph #40, but data looks bad.

Lowered PAM mast to remove inoperative Everest IRT and cable.
Checked sonic levels (ok to < 0.1 deg) after raising mast.

Shot angle of prop-vane boom (138 deg 25' 07") and entered into
prop-vane (138.6).

Shot angle of sonic "v" axis at 140 deg 11' 50".

Installed soil sensors to ENE of rain gauge, between two E/W rows of
soybeans.  Soil heat flux plate is at 5 cm depth and soil moisture
probe is installed with its rods horizontal at a depth of 2.5 cm.  Soil
temperature probe was inserted at an angle between the surface and
roughly 5 cm depth.

Soil heat flux plate is S/N 943147.
Soil temperature probe is S/N 94016.
Soil moisture sensor is CS615 S/N 002.
ETI Precip Gauge:	S/N 051 (9/15/94)
ATI:

Removed bolt in bottom surface of sonic electronics box to allow water
to drain out.  Mopped up water from bottom of interior.

Site Visitation Log Entry
=========================

Tech: rei
Weather: sunny
Set Clock: Y
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: reinstalled tsfc sensor (was checked out OK at station 1)  sensor
 was fine` for a few minutes, then went back to neg 12 deg readings. 
 problem must be in A/D

reinstalled Tsfc sensor on station 3 on lower crossarm.
saw 2 "good" readings, installed sensor, and then received only
-12 deg readings.
removed BPH to see if it would work on station 2

Site Visitation Log Entry
=========================

Tech: KK
Weather: 
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: 

The prop-vane wind direction at station #3 looked incorrect, so
John checked the boom direction parameter on the prop-vane and
found it to be equal to zero.  John entered the correct value,
138.5 degrees.  John recall entering a nominal value of 135.0
when he and Kurt aligned the prop-vane to the boom, so it is 
likely that the prop has also forgotten this alignment value of
the optical encoder.

The BPH s/n #40 was installed on the station and the earlier problem
was fixed.
The problem was 2-fold:
	- ATI A/D connector's power ground pin was pushed up (and was
	  a bitch to get down without the proper tool).
	- The Limo connector on the BPH housing appears to also to be
	  making poor contact.  A little bit of reseating and wiggling
	  seemed to do it.

I cannot say for sure whether or not the BPH will stay up.  The readings
when we left were consistent with the TRH, but not exact: about 5% higher
in RH.

Because the malcontent Tsfc seemed to work for awhile on station 1 this
morning, Kurt put it back on 3 later on, however, it was still showing
bad values.

We diagnosed the EVE A/D using a 1.3V battery on a 16-pin amp connector
for the tsfc pins, and swapped the battery box output to the AD1 port,
plus tried the Tsfc on channel 0 (AD0 port).  The EVE AD channel 4 is OK
with both the batt, and power box inputs as determined by the EVE ad
monitoring routine.  The Tsfc sensor was still bad, and appeared to be
having stray capacitance that was charging/discharging. 

We'll need to try to isolate this problem tomorrow on station 1 by
lowering the mast and trying to determine whether its the cable of the
sensor. 

The wind direction at site 3 for the period 0000-1400 GMT, June 15,
matches the wind direction at site 2 very well.  This suggests that 
the boom alignment parameter in the prop-vane is okay.

Thus we will not make a special site visit to check the boom alignment
at site 3, but we will check it next time we lower the mast at that
site.

The u axis on the ATI was bad on the mornings of June 14 and 15.  The
signal appeared to improve significantly around sunrise, suggesting a
temperature or humidity problem.

I visited the site between about 1130 and 1230 CDT.  The electronics
enclosure was dry inside.  Looking at the received signals with the
'scope, it was evident that the u axis was noisier than v and w.  I
tried loosening and retightening the transducers on the u axis, but
this had no effect.  I swapped the u and w receive boards and the noise
followed the board.  I replaced the the u and w boards in their proper
slots and reduced the amplitude on the u receive board about 1 full
turn of the pot.  This made the signal look a lot cleaner.  I also
reduced the amplitude on v a little, so that all 3 boards have the
first negative wave at an amplitude of about 4-5 V.

I could not rezero the u (or v) axis, because I did not have a
field terminal to determine the temperature and humidity.  However,
I suspect that my adjustment made little change in the zero.  We will
rezero on a subsequent visit.

Site Visitation Log Entry
=========================

Tech: .
Weather: 
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Yet another Tsfc test.  Blown fuse for aux power but no spares.
  Check ATI glitches: bad u board, needs replacement.  digital photos
 taken.  began  painting rad stand

Visited station #3 on June 16, between 1400 and 1500 CDT.

Measured sonic height to be 3.21 m

Looked at signals with scopemeter and saw intermittent noise preceding
received pulse on the u axis.  Tried to adjust the capacitor to reduce 
noise, but this only made it worse.  On my previous visit it was 
apparent that this is a problem with the board, and the daily plots
suggested a temperature-dependent problem.

Visit to station #3 on the afternoon of June 16, about 1400-1500 CDT.

Lowered the mast in order to replace the Everest on the 10m crossarm
(pointing down to the NW at 45 degrees).  John found a blown fuse
in the line providing power to the Everest, so this was part of the
problem.  The fuse will be replaced, hopefully today.

Temporarily disconnected the bandpass hygrometer because the cable
interferred with lowering the mast.  Reconnected it to eliminate the
interference.

While the mast was lowered we checked the alignment of the prop-vane
by holding it paralled to the crossarm and looking at the output.  It
appears to be correct.

See a separate entry regarding work on the sonic anemometer.

John touched up the radiation stand with black paint.

Site Visitation Log Entry
=========================

Tech: .
Weather: 
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Download data.   ATI s/n 920202 Model SWS-211/3KL.  Soil sample
 for moisture.

Sonic at station 3 continues to have spiking at the 1% level on 
the u axis, particularly after sunset.  There is also sporadic
spiking on the v axis and spiking on the w axis.

The sonics at stations 1 and 2 appear to be operating okay.

bph at station 3 reporting bad data during the daytime, June 17.
This sensor already appears to be more sensitive to radiative
heating than stations 1 and 2, but from 1500-2100 gmt, June 17,
the temperature was about 10 degC too high.  From 1400-1600, the
RH was 90-100%, while the other sensors reported 70-80%.

bph at station 1 has a tendency to saturate around 98% RH at night.
This occured on the nights of June 16 and 17.

ATI shipped a new Receive amplifier board for the sonic at site 3.
I visited the station to replace the board around 20:30 - 21:00 gmt.

Before replacing the board, I looked again at the signals with the
scopemeter and confirmed that the noise followed the board when I
interchanged the u and v boards.  Then I swapped the boards back and
replaced the u axis board with the new board from ATI.  The signals
look a lot better with the new board.  After running with the new board
overnight, I will send the old board back to ATI for inspection and
(hopefully) repair.

I zeroed the u axis after confirming with the scopemeter that the
signals had the proper amplitude (first positive wave < 0.5V, next
positive wave ~13V).  The zero is probably only good to no better than
0.5 m/s since the wind was blowing parallel to the u axis and the
zero-wind tube is pretty leaky.  After zeroing, I looked with the
Toshiba at the sonic output and it was on the order of 0.5 m/s and
fluctuating by several tenths of a m/s.  Will need to rezero when the
wind is lighter.

I dried up a little water in the bottom of the electronics box and
resealed the edges of the door with electrical tape.  The hole appears
to be limiting the water depth as intended.

The w axis was quite noisy, generating spike flags for as much as
10% of the data, from 0800 to 1900 CST, which appears to coincide with 
daytime heating (temperatures exceeding 24 degC).

The new board on the u axis continues to perform well.

Site Visitation Log Entry
=========================

Tech: JM
Weather: Clr, Hot, Calm
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Remove old Freewave.  Download Data.  Zero u-component and other
 sonic work to chcek boards.  Another boot failure!  Bad config.dat and
 it's ramdisk backup, also rtc was dumped.  Fortunately /card had a good
 copy.  Do we need to replace the cpu batt

Station Visit ~17:30-18:45 GMT, 96/06/20

Removed old Freewave Radio

Offloaded Data

Sonic Work: see other message.

NOTE: EVE Temperature related CPU problem Again:
Same box as before.
After removing the freewave, the CPU failed to boot
properly...another temp. problem no doubt because it
was quite warm.
On the first go around it halted at: "loading 3 symbols..."
I then did a reset on the CPU and it booted but failed to
load a good config.   The RTC had bombed as well as the 
config.dat file.  I set the clock and copied the config from
/card, rebooted and everything was hunkey dorey.

The flags plot for site 3 has shown spiking at the 1% level on the w
axis, particularly during the daytime, and the zero level appears to be
wrong on the u axis.  Between about 1200-1300 CST on June 20, I swapped
the u and w receive boards to isolate the cause of the problem.
However, I could not see any problems on the scopemeter with either
signal.  I adjusted the levels of the signals (not much adjustment
required) and then we zeroed these two channels.

Looking at the current plots for June 20-21, it is obvious that this
change eliminated almost all of the flags on the w axis, but now there
are continuous flags (both night and day) on the u axis at about the 
0.3% level.  The rezeroing has fixed the offset problem on the u axis.

The Zimmermans will ship the refurbished Receive board back to us
today, but Gary could not find much wrong with it.  I will try
replacing the bad w board with the refurbished board.  Meanwhile I will
leave the new board in the w channel and the old w board in the u
channel.

The bandpass hygrometer temperature at site 3 appears to be about 1
degC too high during the day, as though it had a radiation heating 
problem.  Steve suggests checking the whether the inner shield is
properly recessed (about 1 inch) relative to the outer shield or
whether the prt is touching the gaurd.  The temperatures at sites
1 and 2 appear to have the expected diurnal cycle relative to the
hygrothermometers which are at 2m compared to (3.2, 4.5, 3.2)m for
the bandpass hygrometers.

We also think that we have the wrong coefficients loaded for the
bandpass RH calibrations at all three sites.

Site Visitation Log Entry
=========================

Tech: JM
Weather: Hot, w-Brz, Pcldy
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Freewave installed.  New EPROM, New config with correct BP-RH
 coef.

I visited site 3 to look at the sonic signals.  They look fine on the
oscilloscope, but I hoped to detect enough errors looking at the flags
in order to perhaps readjust the sonic.  However the number of flags 
was on the order of 0.1%, so no luck.

Gary Zimmerman has suggested that we may have the gain too high on
the Receive boards so that the "true" first wave is at 10V rather 
than 0.5V.  I tried reducing the gain all the way, but this did not
reduce my "second" pulse below 1 V.  I returned the gain to the 
previous setting, but did not rezero the sonic.

I noted in the dailyplots that this sonic was very different from sites
1 and 2 yesterday:  u:u, w:w and u* were all lower at this site, but
sigma_w/u* looks about right.  Also tc:tc and w:tc were higher than at
the other sites and w:rh20 was also lower.  This was the one of the few
times that the wind was blowing from the field to the south with no
growth, so perhaps this was the cause.  Also, this field was recently
planted, so this also may have changed its albedo, etc.  Looking at
the data from today, it is quite obvious that this site is different
when the wind has a southerly component and a fetch with no vegetation, 
but matches the other sites when the wind has a northerly component 
and has a fetch over the growing soybeans.

Station 3 Visit:  20:20-21:40Z, 96/06/22,  JD174

Installed Upgraded FreeWave Radio  #560-0560

New EVE EPROM Installed:

Checked BPH Sensor:
The position of the inner tube is OK...ie approx. 1" inside the outter tube,
and the transducer is centered  We did not examine the sensor for dirt.

New Config Loaded:
Incorporates the correct fast rate BPH RH coefficients.
Also has the proper CREATE statement for the BandPass stuff.
Also has the 'new' MESG output for ATI.

35mm Photos Taken (hopefully 360-deg shots)

ATI sent back the "u" board from station 3 that I asked them to
repair.  Gary Zimmerman said that he could not reproduce the problem
that I saw in the field.  However, he did "change a couple of things
that might be a problem."

I replaced the "w" board, which had been operating in the "u" channel,
with the refurbished board.  I could not see any problem in the signal
with the oscilloscope, either before or after the swap.  However, I
did monitor the sonic spikes in the field.  

Before the swap, with a leaky zero-wind tube on the u axis:

sample count = 2900, u spikes = 7, v spikes = 0, w spikes = 18
sample count = 2953, u spikes = 4, v spikes = 0, w spikes = 28

Replaced refurbished u card in u channel: 

sample count = 2997, u spikes = 0, v spikes = 0, w spikes = 6
sample count = 2970, u spikes = 1, v spikes = 0, w spikes = 10

John also changed the charge controller in the battery box:

sample count = 2945, u spikes = 0, v spikes = 0, w spikes = 14
sample count = 2991, u spikes = 1, v spikes = 0, w spikes = 4

This suggest better performance with the refurbished board, but no
dependence on the battery charge controller.  Note that I have left the
new ATI board in the w channel.

I tried to rezero the u axis, but the wind was blowing moderately 
from the west, so the zero is probably not too accurate.

John is swapping the bandpass hygrometers at stations 1 and 3 today,
in order to isolate the problem with the bph at station 3.  He removed
the bph at station 1 (#23) and we mounted it at station 3, entering
the appropriate calibration coefficients in EVE.  

At that time we found the inner shield of the hygrothermometer
extending about 1.5" below the beehive.  John replaced it, but found
that one or more of the screws that hold it in place had stripped their
threads in the Delrin outer cylinder.

John disassembled the bph from station 3 (#40) and looked at the
sensing elements of the 50Y, but there was no apparent problem.

John will install #40 on station 1 later this afternoon.

Station 3 Visit: 16:15-18:00Z, 96/06/24, JD176

Monitored Power System:
There was noise coming in from the battery box.  It was about 300mV peak-to-peak
at about 300hz.  This was from the Prostar PWM charging characteristics of
pulsing the battery.  I don't know if this noise is causing any problems with
the ATI, or ETI, or elsewhere.  The actual battery level was about 12.8

Swapped BPH:  s/n#40 out, s/n#23 in
new coefficients installed using config: sta003a.dat

Swapped VME power supply
High efficiency unit installed.

Swapped Battery Boxes
Put in the Flexcharge unit.
Removed the Prostar unit.  It was the prostar box that was showing the sawtooth
on the battery voltage monitor via EVE.
Monitor of Power system w/Flexcharge:
It also uses PWM, and that appeared to be about 600mV at 1-second long pulses
(at maybe .25 Hz).  The amplitude varied considerably with the sunshine vs
cloudy charge levels.  Again, i don't know if this noise will effect any of the
systems: unlikely.

TRH Problem:
Noticed that the inner metal tube of the shield had dropped down by about 1.5"
Tom has logged this elsewhere also.  2/3 of the nylon set screws holding the
shield in place have stripped.  A better mechanical design is needed.

Site Visitation Log Entry
=========================

Tech: JM
Weather: clr, n-wind 5-7ms
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Removed BPH #23 to put back on sta1.  35mm- 360 photos.  Soil
 Sample.  ETI test.

Oops.  When i openned the door of the precip gauge to look at the logger the
Licor BNC cable got jostled and the conductor, which had tenuous connection to
begin with, decided to make itself totally broken of at the connector.  I'll
need to repair or replace the cable tomorrow.

Station 3 Visit: 20:00-21:00 Z, 96/06/25, JD177

BPH #23 Removed
Test is over.  The problem followed sensor #40 and it is being taken back
to Boulder for checkout/repair.  #23 will be put back into station 1.
I re-installed the config for BPH #40, even though that'll proably change
when it is returned.

Soil Sample Taken.

35mm 360-degree photos Taken.

ETI check: see other message, it didn't lose it's coefficients here!
but....

Sol_dn Killed
When i opened the ETI housing and moved around the logger and cables, the
sol_dn BNC connector on the extension cable basically fell apart.  I didn't have
anything to fix it with and will need to do that on 6/26.

Unable to Zero ATI-U
winds were too high.

Beginning 96/06/25, 14-local, 19Z (exactly the moment when Tom left for the
airport!) the v-component at station 3 began glitching well above 1%, and
as much as 10%.

I visited the station later in the day, about 21Z, but didn't look at the
signals.   I had tried to establish a good zero for the U component and had 
climbed on the tower, but didn't notice anything unusual at the time.

I'll check the site this morning....

Site Visitation Log Entry
=========================

Tech: JM
Weather: 
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Sol_dn cable repair.  Zero ATI-U.  Check glitching on ATI-V

U Component zeroed.

V Component
Everything appeared OK upon arrival, both inside the electronics box and on the
sonic head assy.
EVE at the time was only showing 1-2 spikes on V.
I went ahead and zeroed u, then put the chamber on V.  For the most part the 
spikes were few and far between, but once i saw a burst of 35.

Signal quality on scope meter appeared OK, but i wonder if it's being
overdriven although i'm not sure.  The initial rize not only was less than 1v
but it was probably .1v on both the V and W, perhaps .3-.4 on U.
During this period i saw spike counts on W that actually were greater than on 
the V

Ground: i tried to re-establish the ground for the electronics box and found it was about .4ohms.  I also reseated the U,V,W boards and cycled power on the box.

The glitches for the most part over an extended period appeared to be
distributed among the 3 components, mostly on V/W with W possibly being worse.
So I decided not to swap the V/W boards, however, looking at the plots
this morning (Thurs, 6/27) the V spikes are by far worse, even though there
was some terrible spiking on W from about 17Z-0Z (ie when i was there).
I now wish i'd replaced and re-adjusted the 2 boards and will probably do that 
today.

The Soldn was rewired in at about 19:40Z, 96/06/26

I was unable to repair the RG58 BNC, so instead i moved the millivolt adaptor
to the sawhorse and soldered an extension from it to the Campbell.  the new
cable is about 50' long perhaps, so it'll be interesting to see if it effects
the voltage measurement.  It probably should be changed back at some point
because i only taped the mV adaptor and soldered wires as a water seal.

Station 3 Visit 17:55-20:15Z, 96/06/26, JD178

Soldn fixed: logged elsewhere

Sonic Work: logged elsewhere

Site Visitation Log Entry
=========================

Tech: JM
Weather: 
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Sonic Work / Checkout.  V board has been glitching a lot.  Swapped
 "v" board into u slot and "u" board into v slot.  Adjusted and zeroed
 all 3 signals.  Damped them down so they wouldn't saturate on the 2nd
 peak.

Station 3 Visit: 17:05-20:55Z, 96/06/27, JD179

This ATI has been having fits since the beginning.  In particular the V
is continuing to spike and the W did yesterday when i was there as well.
Today, I came out to look at the signals and swap the currently worst board (V)
with the currently best board (U).

3 Changes:
	- Replaced the V Transducers
	- Swapped the "V" and "U" boards
	- Adjusted and zeroed all of the signals

I believe the situation is better now, primarily from the adjustments that
were made, however, the "V" board was still showing a few spikes when i left.
Meanwhile, i'm trying to examine the data to determine whether things have
improved according to the data.
By adjusting/damping the signals down in the 3 axis, i hope that the
spiking will clean itself up.  I definitely noticed 'jumping' in the
signals on the 1st peak that supposed to be below .5V, but after i made the
pot adjustments i didn't see very much of that. (except on the "V" board,
but those all seemed to remain below the .5V level at least).

Note: Zero Chamber now in use does let in a bit of wind so some of the
'signal glitches' i observed may have been related to that.  The winds
varied during the visit from about 5-6ms to calm.

I continuously monitored EVE for spike flags and the Fluke Scopemeter.  This
is what i saw/did:


	Sample	     Spike Accum.	
~Time	Cnt	U   V   W	Comments
12:12	1373	    1		Things appear roughly normal even though i know
				lots of spiking is going on.
12:14	2880	1   1		Saw some noise on the v board even with
			 	the zero chamber.  also some waveform that
				could have been some wind.  The 1st peak was
				seeming to jump as high as .8-1V
12:30				Reseated V transducers.
				Still seeing lots of glitching on V
12:35				Replaced Transducers with spare
				Still seeing glitching on V
12:39	730	   131		Yuk.
12:40				Swapped boards "V" board is now on 'U' slot
				and the "U" board is now in the 'V' position.
				Monitoring "V" board:..still seeing front
				end noise.
12:46	492	1   5
12:47	1138	5   5
12:49	2373	13  5		Noise may be better than before but still
				see a few pulses before 1st peak and it's
				still occassionally over 1V...too
				much. zero looks close.
12:52	910	7		Begin adjusting pot counter clockwise to
				damp the signal a bit.
12:58	1853	3
12:59	2783	4		Signal looks better, maybe a few burps to
				.4-.5 V on the 1st peak.  Tweaking pot a
				bit more.
13:01	900	0   0   0
13:03	1933	3   0   0	First peak is barely perceptible and not
				going above .5V.   The 2nd peak is no
				longer saturating, but is hanging around
				11V more like what the manual indicates.
13:05				Zeroing "V" board in 'U' slot: 30-deg 34%RH
13:11	924	0   0   0	Monitoring "U" board in 'V' slot: signal
				looks pretty reasonable.  The 2nd peak
				is just saturating at 12, the 1st peak is
				hanging around .3, but occassionally burps
				to .5
13:13	2151	0   0   0	Adjust pot CCW a bit. 2nd peak now hanging
				in about 10-12 but not saturating.  1st is
				stable at .1-.3
13:19	2362	3   0   0	Zeroing "U" board in 'V' slot:  30-deg 32%RH
				Trouble with getting wind inside the
				tube...
13:27	1135	2   0   0	Rezeroing "U" board: 30-deg, 37%RH..better.

				Monitoring "W" board.
				1st peak is .3-.7, 2nd is saturating.
				Adjusting pot CCW to get 1st peak to
				.1-.35, 2nd peak 10-12V now.  Otherwise
				this board looks pretty clean even though
				we've had spiking the last few days.
13:30				Zeroing "W": 30-deg 34%RH, relatively calm now.
13:38	1530	0   0   0	Need to Rezero "V" board in 'U' slot
				30-deg, 32%RH
13:47	505	0   0   0
13:49	1684	0   0   0
13:50	2130	0   0   0

Judging by the daily plots, the "V" board that i put in the 'U' position
yesterday is still bad.

However, it appears that the adjustment of the U/W seems to have helped the 
spiking there.  I'll keep the fingers crossed.  Other differences in the
sonic data between this site and 1/2 may be attributable to different field
types and conditions.

Site Visitation Log Entry
=========================

Tech: JM
Weather: hot. clr. lt brz
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Hygrothermometer inner tube has fallen down again.  Sonic work:

Station 3 Visit: 20:25-21:45Z, 96/06/28 JD180

Reason:	The "V" board that was put into the 'U' slot yesterday was still
	spiking heavily.  I called ATI about this and... 

ATI Hints per Gary Zimmerman
	Regarding the problem with the "V" board, Gary 
	is sending another board overnight if he has a chance to finish
	going over it.  It is one of those sent back earlier.

	Internal ATI Slash / Filter Commands, not in the manual (Apx A)
	/SM	Median Filter
	/SA	Averaging Filter
	The median filter may work better to remove spiking and Gary
	recommended going to it instead of the normal 'averaging mode'.

	Signal Settings:
	The actual trigger threshold is at 2.5V
	We should not oversaturate the signal, as evidenced by the '2nd' peak
	getting all the way up to 12.  Gary said that it really is better for
	it to go anywhere from 8-12.  Absolute min. is 6V. 
	The filter cap also can be tweaked a bit to get the signal down.

	'W' component board can be attenuated more than the others, so a 'bad'
	or oversensative board can be put into that axis and tweaked down to
	help minimize spiking.

Major Changes to ATI Include:
	Set Sonic to /SM filter mode
	Swapped "W" board into 'U' slot
	Swapped "V" board from 'U' slot and put it in 'W' slot
	Adjusted signals as best i could.
	Zeroed more or less.  NOTE the chamber is really letting in too much
		wind .

Signal Quality
	I saw some of the 'phantom' noise signals on the "V" board in 'U' slot.
	These were generally less than 1V, but occassionally more.  The period
	was about the same as the trigger pulse.  The overall signal also was
	quite irregular but this may be attributed to wind getting through
	the zero chamber.   This board was pretty easy to adjust when it got
	to the 'W' slot, and the Signal looked a bit jumpy.

	I had a devil of a time adjusting the "W" board once it got into the
	'U' slot and played around quite a bit.   I still saw phantom signals
	on it, but i think i finally adjusted them out.  EVE was still getting
	spike hits though, but never > 1%

Conclusion:
	I believe we'll still see spikes in the 'U' data overnight even
	with the "W" board there.   That board had been spiking 2 days ago
	until i adjusted it in it's original 'W' slot.
	Need to watch both...

	Cnt	U   V   W	   
15:44				Swapped "W" into U.  "V" into 'W' slot
				Seeing lots of junk on W as well.
15:46	948	1   0   0		
15:48	2038	2   0   0	Attenuated "W" pot CCW.  2nd peak is now 8-10V
				Now the ghosts seem to be gone.  But i'm still
				seeing spike hits on EVE and the signal itself
				looks crummy.
15:51				Setting "V" board in 'W' slot.
				2nd peak is 8-10V.
				Zeroing "V" board in W,  34-deg, 27%
				Should be OK
16:20	2718	3   0   0	"W" board in 'U' slot.  Still seeing jumps
				in 1st peak up to 1.5V 
				and a bit of a 'phantom'
16:24	2692	7   0   0	Still adjusting signal.
16:40				Finally throwing up my hands, have done the
				best adjustment on the "W" board in 'U' slot i
				can.  Zeroed, etc.

Station 3 Visit:   20:25-21:45Z, 96/06/28, JD180

TRH inner shield had dropped down about 1.5" since yesterday's visit.
I removed the shield and pushed it back as best i could, but it needs to have
larger screws put in the stripped housing.

Unbelievable!
Judging from the overnight plots, the sonic spiking at station 3 has greatly
improved to almost having nothing at all....wow.

So now, was it the /SM median filter mode, or the board swap, or the board
signal adjustment, or the big question: will it last?

Site Visitation Log Entry
=========================

Tech: SS
Weather: hot and windy
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Added BPH #40, campbell proms, fix internal TRH tube, upload
 data, and ETI test. ETI rain test good, start with 2 counts ended with
 47 counts.

Station 3 Visit: 20:35-21:35Z, 96/06/29, JD181

New Campbell Prom installed.

ETI Cal. Coef. were verified to be remaining programmed with this older s/n
ETI Test: logged elsewhere

Uploaded Data.

TRH inner shield tube was secured better than what had been done yesterday.

  The BPH temperature at station 3 is still high.
The fan showed no obvious signs of problems. I will
replace the fan with a new one. I may run a comparison
test with the BPH mounted next to the TRH.

Site Visitation Log Entry
=========================

Tech: SS
Weather: hot and humid
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Play with "U" on sonic. Moved BPH down to TRH crossarm. Replaced
 "U" driver board. Zeroed sonic.

Site Visitation Log Entry
=========================

Tech: SS
Weather: overcast
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Replace fan in BPH, signals look much better. I also taped humitter
 to lemo connector since ther were exposed wires. This may have been a
 factor. Replace U transducers, looks better, re-zeroed.

  Station vist around 20:00 - 20:45 GMT

I chnaged the driver board for the "u" axis at station 3.
The board was adjusted, with zero chamber on, such that the peak
of the first wave was below .250 mv and the second wave was around 
9 volts. I did a zero calibration on all 3 vectors.

  station visit 20:00 - 20:45 GMT

I moved the BPH down to the TRH crossarm. The sensor
is looking into the beehive about 12" away. At this time
it does not look like anything has been gained. I will change
the fan tomorrow.

  visit time: 15:00 - 16:00 GMT

 The BPH at station 3 is much better. I replaced the fan and
taped up the connection between the 50Y and the limo. There were
exposed wires. The BPH was then mounted at the 2m height and
monitored for awhile. The temperature readings were about 0.3
degrees lower than the TRH. The sensor was then mounted on the
ATI boom.
 I am not totally convinced the problem was the fan. If time
permits I may put the orginal fan back to try an isolate the
source of the problem.

   visit time:  15:00 - 16:00 GMT

 Spent time working on the "u" vector. After checking the
signals using the scope and the zero chamber I decided to change
the transducers because the trailing end of the received signal
was dropping off quickly. The length of the signal improved some.
The sonic was zeroed. Will monitor.

Site Visitation Log Entry
=========================

Tech: SS
Weather: wind from north
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: I adjusted the gain on the U vector down such that the pick
 level on the second pulse in light winds was about 5-6 volts. I monitored
 out for a while. Spike count of < 3 over 10 minute period. Winds around
 3 m/s

	visit time:  22:30 - 23:00 GMT

  I decided to try something different at station 3. So
I tuned down the gain so in light winds the peak of the second
pulse was between 5 and 6 volts. I monitored the spike count in
EVE for about ten minutes. The average count was < 3 for vector
U. The others were zero. Maybe this will be a solution.

  The sonic continues to be a problem. There were
a number of spikes on "u" throughout the night. In addition
"w" went down at 9:00 GMT this morning. I guess I'll just
spend the day at site 3!

Site Visitation Log Entry
=========================

Tech: apr
Weather: partly cloudy, windy
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: W showed alot of spikes via EVE thru terminal. On the scope
 the signal looked ok. Reset EVE, all was fine!  I monitored thru EVE
 for 50 minutes. The maximum number of spikes in 5 minute block was 3.

		visit time: 17:30 - 18:30 GMT

  The first thing was to look at the "w" vector. I hooked up
the scope and the signal looked fine. The peak level of the
2nd pulse was above 8 volts. Using EVE, it was seeing spikes
at a 10hz rate!  So I reset EVE. The sonic response, thru EVE,
now looked fine. So something happened in the EVE firmware.

  With respect to the "u" vector, I turned the gain back up
so the second pulse was above 8 volts. This was done with winds
around 3 m/s. I then spent the next 45 minutes monitoring the spike
count thru EVE. Over this time period I did not see a 5 minute
count greater than 3. 

  At this point I decided not to play with anything and let the
system run for another 24 hours.

  The u vector is looking much better today. There were
a number of spikes in the very early morning.

Site Visitation Log Entry
=========================

Tech: srs
Weather: partly cloudy
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: 

Site Visitation Log Entry
=========================

Tech: srs
Weather: partly cloudy
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: IC taken, T 0.3C high, RH 1.5% high. crop along fetch=.1m at
 station=.25m

		visit time: 18:00 - 18:30 GMT

  I did a temperature IC using the ASSMAN. The data
was recorded on the compact pc. Overall the temperature
was about 0.3 degrees high and the humidity was around 1.5%
high compared to the ASSMAN.

Site Visitation Log Entry
=========================

Tech: srs
Weather: clear skys
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: change driver board on u vector. Set second pulse to 10 volts,
 zeroed "u"

		visit time: 19:40 - 20:00 GMT

  Replaced the driver board for the u vector. The
board removed was the new one I got from ATI. Will monitor
performance. The majority of spikes are below 0.01; however,
this is the only vector showing any problems. It would be
nice to find the source of the problem.
NOTE: the u vector was zeroed.

		visit time: 17:15 - 17:45 GMT

  Soil and crop height measurement were made.
Refer to logbook entries 35 and 39.

Site Visitation Log Entry
=========================

Tech: srs
Weather: cloudy and winds
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Switched driver boards U and V. U and V zeroed.

		visit time: 17:45 - 18:15 GMT

  Switched driver board "u" with driver board "v" to see
if problem on "u" vector was board related. Both "u" and
"v" werer zeroed.

Site Visitation Log Entry
=========================

Tech: srs
Weather: cool, windy,clouds
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Switched transducers in "u" and "v" components. Download data
 from 186 on.

		visit time: 16:30 - 17:00 GMT

  I decided to continue searching for the problem on the
"u" component. There was no major improvements after
switching the "u" and "v" driver boards. So I switched the
transducers. All three axis were zeroed.

Site Visitation Log Entry
=========================

Tech: srs
Weather: 
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Sonic box replaced with #1 box. All axis zeroed.

Site Visitation Log Entry
=========================

Tech: srs
Weather: 
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: replace sonic box with one from station 3, sonic box #2. Signal
 level adjusted but not zeroed. Note: moved some internal power cables
 away from incoming signal cable.

Site Visitation Log Entry
=========================

Tech: spo
Weather: sct Cu, breezy
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: T comparison exactly agreed - we didn't cheat!  RHstation 2.5%
 high

Site Visitation Log Entry
=========================

Tech: spo
Weather: overcast, wind SW
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Came to get some data and move the sonic box to the ground under
 the PAM box. Hope this will reduce spikes due to heating. Slight adjustment
 on v and w. Zeroed all axis.

		visit time: 15:00 - 16:00 GMT

  Based on the last few days, the sonic at 3 has been spiking
due to changes in temperature (refer to earlier logbook entry).
This may not have been noticed at station 2, when the electronic
box was there, because the box was shaded by the corn. We moved
the sonic such that it is now on the ground under the PAM electronic
box. A 2' x 2' metal plate was put on top of the box for added
shielding. The sonic was zeroed on all axis.

Site Visitation Log Entry
=========================

Tech: srs
Weather: winds from west
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Switched driver boards u and w. Adjusted and zeroed U and W.

Site Visitation Log Entry
=========================

Tech: spo
Weather: SCT CU,NW@light
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: Also did Assman IC`- T 0.2 high, RH ~2% high

I forgot to note that, during my data download visit of all the sites 2 days
ago, the beans to the north of PAM3 were starting to get flowers, and thus
entering "R1".  The beans to the south still were in V3.

I got the ati at PAM3 running also.  I knocked THE drop of water off 
and cycled power about 2045 Z.

P.S. PAM2 apparently revived itself about 2130.

Site Visitation Log Entry
=========================

Tech: MM
Weather: cloudy, cool
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: emptied ETI, did Assman IC, retrieved data  fan dead on trh-read
 about 1 deg C too high

Site visit to station 3 this p.m.

Offloaded jd201--207.

Did Assman I.C.  See Compaq or future I.C log entry for results.
Assman read about 1 deg C lower.  Fan was dead on the Trh sensor.

Emptied rain gauge.  Reset power on gauge.  Mouse nest and mouse turds are filling the bottom of the ETI.  Looks like some cables are getting slightly nawed.

Site Visitation Log Entry
=========================

Tech: spo
Weather: clr,N@light
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: raised sonic, changed fan (a spare Trh sensor would be nice).
  Did assman IC

We finally moved the sonic at PAM3 to 4.00m.  We didn't measure this new
distance, but did move it up by 0.80m from the previous location.  This
is about 3.7m above the canopy to the south and 3.5m above the canopy to
the north, so it should be okay for a while.

Matt noticed yesterday that the fan wasn't going on this sensor - it had a
corroded (and now broken) lead.  We just replaced the fan.

P.S. fun.Tddiff.plot() shows that the fan died about 10Z on 23 July, so it
was bad (with readings high by about 1.5 C) for about 3 days.

station 3 had the sonic despiker stuck for the period of jd 215 from
10:00Z to jd 216 05:00Z.

Site Visitation Log Entry
=========================

Tech: MM
Weather: breezy, harzy
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: got data jd212-217

The battery voltage at station 3 has been abnormally high while
charging in the daytime.  Yesterday, the voltage looked OK for awhile,
and then it popped up to 17V.  See the attached plots.

Site Visitation Log Entry
=========================

Tech: MM
Weather: cool breezy
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: got data jd 217-222

Site Visitation Log Entry
=========================

Tech: MM
Weather: south winds
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: got data from jd222-227

Site Visitation Log Entry
=========================

Tech: MM
Weather: sunny humid
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: soil sample, crop height, photos.   dropped mast and cleaned
 band pass 50y probe.  Assman IC.  downloaded jd 227-232 data.

Site Visitation Log Entry
=========================

Tech: MM
Weather: bloody hot and humid
Set Clock: N
Trh  IC: N
Baro IC: N
Rain IC: N

 Coments: downloaded jd232-234 data.

Station 3 removed yesterday at 19:30Z.  Removal was exceptionally
strenuous due to inability to use motorized vehicle in bean field.
Suggest that in future deployments, the use of a vehicle for station
removal is requested of land owner in advance of station installation.