While working at Aspen, Andy came by and said the communication link from
Willow was down. So I stopped the work at Aspen to go to Willow. At Willow
I found the Breezecom communication light was read not green. I recycled
power on the breezecom and that got it going. Back at the CUFF trailer I
rebooted cosmos to get it going.

After Gordon's investigation, I followed-up by replacing the 16db patch antenna
at willow with a 24db parabolic.  I didn't get a chance to run the Breezecom
diagnostic utility (could we install it on aster using VMware and run it 
remotely?), but pinging seemed solid.

To do this, powered down the entire cosmos box about 1730-1800.

cosmos, aircoa1 and aircoa3 have not been transmitting since
the evening of Friday, Sep 10.

Came to C1 and started up the DS-11 wireless ethernet software on
the Panasonic.  (hook the network cable into the extra port on the
DLink hub, labeled Tower 10.0.0.x, next to CU's Dell).

I could connect to both station adaptors and the access point from
the trailer, so it isn't a power problem at willow.  I could ping
and log into cosmos - it reported an uptime of 9 days.

The 802.11 connection to willow does not have good signal strength:

The Station adaptor at willow is the breezecom unit B, which
has address 10.0.0.199

The DS.11 software reports the following statistics for  unit B,
unit C (10.0.0.197) (which is at pine), and the access point
(10.0.0.200):

       Signal Qual    RSSI             FCS Error rate
B         38%          -85dBm (42)        19%
C         86%          -74dBm (48)        1%
AP                                        35%
FYI: the SNMP write community password is what Dorothy told her dog.
The ESSID is "default", and the read password is "pubic".

As a hack I changed the channel to 6 from 11 on the access point.
Unit B had been fixed on channel 11, and I changed it to scanning mode, 
with preferred channels 1,6,11.  (That was the setting of unit C).
That change didn't help, but I left it.

I checked the antenna connections at willow and was able to turn the 
connector at the antenna about another quarter turn, but it didn't help 
the signal strength.  The antenna is pointed well to the CU tower.

Reset aircos3 and got things running again, but wasn't able to
make any improvements to the signal strength.

/var/log/messages back on aster reports  DHCPREQUEST and DHCPACKs about every
20 seconds for 10.0.0.199 - which I believe is a symptom of the bad
signal strength.

Since HiCal was at 160 lbs yesterday, I've slowed the cal cycle to every 19 hrs,
rather than 9 hrs.  The cals are now 150s on each cylinder, and it appears that
it takes at least 100s to settle, so I hesitate to reduce the calibration 
duration.

8/20/04 ~15:00 local

Fan at 1m was missing it's blade...ie of no value.
Installed fan removed from pine 2m which appears
to work well enough.

~13:25 local
Installed Mote18 in place of #23.   This mote has proper calibrations
for lm20 strings and it's own vref value so the data should be OK.
SO changed id number in prep.config so it should be covared/etc.

Why in the world did i do this: wrapped foil around all tsoil mote
stand.  This site is so wet i doubt any self-respecting chipmonk
would go for these with exception of at #18.  That mote has most
of the wires exposed on the ground from the post to the dirt
entry point.  They need to be dug in later if possible.

~13:45 local
Distilled water used.
Note began raining within 45min or so afterwards so
the data may not show improved signal for a bit.

Even with the correct calibration coefficients, I need to subtract a bias of
90 W/m2 from Rnet and 2.9mmole/m^2 s to get Rnet and PAR to agree with the
other towers.  This must be coming in through the T/RH A/D, so we plan to change
these sensors on willow to a CR10x like pine and aspen.

about 20min ago, steve and I just changed the format of the windsonic from
spd,dir to u,v.  I'll change prep.config (I don't think channel config needs
to change) to the current value.  Note that this could necessitate a change
in ops, but I won't worry about this for the moment.

The previous entry played with the CO2 calibration of the 6251.

I should also document that the Tcell gain is simply a factor of 1/1000 to 
convert the 0.1mV output from the "serializer" to degC.

From the MPX4250AP pressure transducer data sheet, the output is:
Vout = Vs(Pcell*0.004 - 0.04), or
Pcell = [(Vout/Vs)+0.04]*250
I assume that I wired Vs to a regulator that produces 5.0V.

The li6251 at willow just reports mV*10 (11841 = 1.1841V).  Using the 2 points
at 1452 GMT on 5 Aug and assuming the nominal values for HiCal=389 and 
LoCal=336, I get: ppmv = li6251*0.0437 - 128.  I'm going ahead and putting
this in the new fun.hilosort(), but it should be revisited!

Using prep, I've gotten crude agreement between Rnet from w with p&a by 
multiplying by the gain of 8.57 (justified), but then subtracting 120W/m2
(not justified).  Presumably, this means that there is a voltage offset in
the TRH A/D at willow.

Similarly, I get crude agreement with PAR using a gain of 0.259, but an
offset of -3.3.  I note that there still is a lot of small noise in PAR.w
and it is not 0 at night (unlike p&w that are 0), but instead varies [though
not exactly like Rnet].

In addition, both w signals have huge spikes, but only during the day.

Clearly, we need to check out the data system on this T/RH.

- added a 4ch serial cable to bring up chans 212-215
- apparently the water killed channel 208.  The 17m sonic is now working in
  ch 213
- aircoa2 (destined for aspen) temporarily hooked up to ch 212 for comparison
- 214 will be for the 2-D gill (now mounted and hopefully to be connected soon)

- cycled power on the 6251 which brought it back alive
- aircoa1 still doesn't work on network.

About 0400 on jul 23 (Friday), TRH.1m.w started producing huge values.
I just rserial'd and did a "MR" reset, which brought the data back in line.

I just visited willow to try to fix this.  There is water in the cable and blue
corrosion at the breakout box (like we've seen before).  We need to replace this
cable and tape the barrel up the tower.  (But I don't have a cable or tower
climbing gear here now.)

Tom and I went to willow today to try to fix the 17m sonic,6m sonic, and
re-install the tsoil units. We also checked the krypton interface to the 2m
CSAT.
 The 17m sonic is backup and running. It is on logocal channel 208, physical
channel ttyS19. Physical channel ttyS12 needs to be checked out.
 The 6m sonic is working ok. The sonic was attached to port 200 as a test and itwas fine. The problem is with channel 204. Using rserial the output message is very cryptic. Maybe an incorrect baud rate. The channel_config and prep.config
look ok.
 The tsoils were installed. Unfortunately the Tsoil to the east could not be
because some creature decided to break the lid of the electronics box.
One of the Tsoil probes at the east site is out of the ground.
  The 2m krypton signal was good. A backup sonic was used and the krypton was
fine. When the original CSAT was attached the signal again looked ok. A test
was run by disconnecting the krypton and checking for a response change. That
test was successful. The interface cable between the krypton and CSAT was
changed because the original one was not potted. It may be the problem was
due to water in the original cable.
  Based on the cockpit display there is still a problem.

  Three tsoil sensors were removed to have voltage regulators added to the power system.

  This took place last Thursday afternoon.

The 2m krypton appears to be ok. I checked it with a DVM. The problem is either
the serializer or the connection to the the serializer. Unfortunately the
test cable with the DVM broke so I was not able to continue tests. Also the
adapter cable from the krypton to the sonic had not been potted. Water was in
the connector.

Thw 17m sonic at willow is down. Last Friday Steve O. and John found water in
the cable at the breakout box. They were not able to get the sonic going again. Today's tests show that the sonic is ok and the problem is on the Emerald board,
channel 208, (second board port 1). The best I was able to determine is the
cabling from the sonic to the data system was ok. The internal cable from the
interface board was ok. So the problem is either a bad 4 port serial cable
to the Emerald or the Emerald board.

Things I just did:
- cleaned krypton at 2m (forgot to bring the climbing harness, so couldn't go
higher)
- moved TRH.1m up closer to 1m (now still about 5cm below the sonic)
- bolted down the AC breakoutbox (I didn't have the hardware before)
- removed the power and mote for mote #23, that has been having problems

Kurt cycled power on cosmos, which brought it back up.  However, it went into a continous reboot cycle because I had left a definition for ch164 in channel_config.  Now that this is removed, cosmos appears to be stable.

However, the csat.17m now appears to be bad.

P.S. Following the aster configuration quick reference got the csat restarted.
I don't know if it will come up after another power cycle.

mote#23 has been dying over the last 2 days -- perhaps due to too much power.

at 03:31 GMT last night, channels 200-207 all died.  I also couldn't login to reboot.  Someone may have to hit the power.

Found that the AD coefs in the willow Tsfc were wrong.  Set by:
PM
AD
COFL 2 1 1e3
COFL 3 1 1e3
PC
CD

This done about 11:15 today.

Actual installation of the HiLo was from 10:30-12:30 on Thurs, 6/17, but
cosmos was acting up due to network problems.  Cosmos was restarted on Friday
afternoon and then started controling the HiLo.

Since our cal (and ref) gas cylinders have not yet been calibrated, we are
running in absolute mode with the reference cell scrubbed using the clip-on
MgCl-- + lime container.  We'll change this setup when the cylinders are
available.

P.S. It appears to be working!  The delay time is about 3sec -- there may be
some smearing.

The 2m csat sonic was running at 20hz.  Sent it the "Ad" command
to switch to 30hz.

Hi from Los Mochis, Sinaloa, Mexico!

Power was recycled at willow. This took place around 3:15 pm.

The wireless network link to willow is having problems.  It
ran poorly for about a day and a half then crapped out altogether.

Symptoms:  
  frequent dhcp requests from the Breezecom station adaptor
  at willow, often every 20 seconds!  Seen on aster:/var/log/messages.

  Network socket from willow data system shows many network
  temporarily not available errors, as seen with "ndaqstatus cosmos".

SteveS went to willow today to check things. He got it working again
but it is still showing the same symptoms.

Went to willow to change the 2m TRH, fix the Tsoil at site 20,
and finish breakuot box cabling for the 17m sensors.

I added the coefficients to the TRH, channel 209, collecting the
rnet and par data.
Rnet: 10.53 W/m^2/mv
Par: .22 Umoles/mv

The TRH at the 2m height is reading high temperatures.

Sensor IDs for willow site.

height		sensor		ID
17m		CSAT		538
17m		krypton		1391
17m		netrad		91096
17m		Licor Q		30629
17m		Tsurface	3577-1
17m		TRH
10m		ATI		980202
10m		TRH		001
6m		ATI		980302
6m		TRH		204
2m		CSAT		537
2m		krypton		1392
2m		TRH		003
2m		pressure	B6
1m		ATI		980303
1m		TRH		703

Work continued with the installation of instruments yesterday.
All met sensors have been installed along with the Tsoil array.
The CO2 system should be installed next next.
The Tsurface sensor is interfaced through the 10m TRH sensor.
The net and par are interfaced through the 17m TRH sensor.

NOTE: the TRH sensors are ~.5m below the desired height. This is
due to the mounting hardware.
Work to be done:
	(1) short DC-to-DC breakout box cable
	(2) long pressure port tubing
	(3) short 9 pin cable with adapter unit

.
Data system at willow is up and running as of 5:00 pm this afternoon.
2 TRH's and one barometer are running.
To be done: 

  move data system and transformer away from tower

  ground data system box

  move TRHs 1/2 meter up