CuPIDO: Site 6 Messages, 17 Entries..

The Rnet desiccant tube was replaced at 00:20 GMT.

One test tip was done to the rain gauge at 8:52 MST.

The Rnet dome was cleaned at 8:48, it was then removed from 9:00-9:11 to remove 
condensation buildup. The screw were put in through the bottom, put them throughthe top.

A.J.I and Steve O. arrived at the site at 8:47 MST and left at 9:14

Activities:
- Cleaned Rnet at 8:48 MST
- 1 test tip done at 8:52 MST
- Removed Rnet dome to remove condensation buildup, screw were in through the 
bottom, put them through the top. This was done during 9:00-9:11

At 5:23 tonight, station 6 died.  We realized this at 7:30 from the Inn, and
did a late-dusk scramble up the hill to check up on it.  The data system 
processes had stopped for a reason we were not able to determine.  We ended
up just rebooting the station and all seemed fine.  Perhaps the crash was
due to a different type of 512Mb memory stick?  (Though Gordon is sure that
this stick has been used elsewhere.)

A mystery...we'll keep an eye on it.

1 test tip at site 6 at 11:40.

Just for fun (and to show me for the first time), Gordon and I did a standard
visit to site 6 from about 11:20-11:45 this morning.

Activities:
- swapped usb
- installed new software
- restarted data system -- noted no logger data [stupid me!]
- manually changed logger /ttys5 to /ttys6 in /root/.../cupido.xml
- restarted data system -- now all okay
- poured 1 tip of water into gauge at 11:40
- inspected Rnet domes and decided not to clean
- attached a ground strap to a T-stake at the logger
- took photos

See entry 191.  The rain gauge at this site was plugged.

Unplugged gauge.  Tested gauge with 3 tips.

Logger variables (Rnet, rain, Vbatt.rad) have been out since 00:00 MST
7/28 at this site.

Arrived 12:30 MST

More than 1 inch of standing water in rain gauge.
Drain tube was plugged with small piece of blue plastic.
This may have effected all rain data from this site up
to this date.

Logger getting power (14.5 V), multiplexer ticking.
Some water inside logger.  Taped over a bulkhead amp
connector that had open holes, with no pins.

Determined that port 0 on the emerald serial card (ttyS5)
was bad. Switched logger to ttyS6.

Considered grounding the logger, but decided
it would create a ground loop between the data system
ground and the logger ground.

Rnet clean - did not wipe.

Swapped USB disk, installed new nidas software (has
GOES status).

Rain test, 3 tips at 13:15.

Left 13:35

I cleaned the net radiometer domes at station 6 this morning, although they 
appeared clean.

Gordon rewired the CR10X multiplexer bypass with 22 gauge wire and amp pins
between the bulkhead connecter and the CR10X patch panel:

Rnet Amp pin
4 		clear -> AM16 shield
1		grey -> CR10 differential port 2H
2		green -> CR10 differential port 2L

Kept shield through original  cable

I duct-taped the lid of the GOES cooler and swapped the USB disk.

st6 Visit: Rnet / logger outage

20jul06 7:40-9:15

Purpose: Bad Rnet since station zapped 2 nights ago.

Logger readings were kaput for the installed rnet as well as the spare, known
good sensor.   Upon a power cycle the readings momentarily looked good but
steadily setting into pegged out values.

Rather than change the software (a temporary until power cycle fix) to determine
whether the bad component was the am416 mux or the cr10 adc (batt voltage was
still good), SteveS recommended directly wiring the rnet to the mux input 
channel on the cr10.  That worked because there is only 1 sensor here.  
I had to 'twist wires' together to cobble a jumper to have them long enough 
to reach the adc-diff channel 2 input.   This worked and the readings began 
to appear reasonable however, the security of the connection needs to be 
improved to ensure it remains good.

19Jul06 8:30-9:30

Purpose: Station reporting went down last night during Tstorm.

DAQ down upon arrival although station power and the Viper was up and running.
The usbdisk was 'dead' to the system.
Basically minimal log files since 4z.

Some small amount of water in the bottom of the goes box.

Halted data system and powered down.

Goes pvc elbows installed to improve ventillation.

Booted and everything went ok.  Discovered the usbstick data is there but
stopped ~18jul06 21:40, thus we lost data overnight.

Stopped adam, swapped usbstick,
ck_goes was good.
Restart and everything looks ok.

Conclusion:
	I believe the station took a lightning surge and 'burped'.
	Decided not to reinstall the software just to see if it'd recover
	without that even though the 'zap' probably fouled it's dynamic
	memory if not other.
	Grounding here has always been a concern.  We installed 2 rods
	roughly 25' away but i'm thinking that the ground strap from the 
	elec box to mast lug should be removed with a hunch that ground
	strokes could be putting a surge on the ground.

Rnet:  I tried to clean it although it appeared basically clean.
	When doing so, i noticed water vapor condense briefly inside the dome.
	Didn't think much of it other than perhaps we need to change dessicant.
	However..
	when i looked at rserial i thought the values were 350-ish and ok,
	but since it's been back online the rnet data has been bad.
	returning with spare sensor.....

The data system went offline, perhaps due to the USB stick going offline) at 
2145Z or so 18 July during the day's monsoon 
storms. It is unclear if the storms were the cause but grounding issues are 
being investigated. The power was up at the system and the aspirator and other
systems were running. The GOES was fine as well (although it had nothing to 
send). The system was returned to functionality after the investigation.

13Jul06 13:10-14:15

Purpose: Station plots had been down...ie goes down.

DAQ on arrival was ok, still recording.
This site still had the old version software, so suspecting that being the
usual 'slow sensor into stats-proc problem' and just for giggles i rebooted
and watched the logs.  1st xmit ok, 2nd/3rd missing and no indication in
either log file.   as expected.

Installed new software.  Retrieved local storage
Reboot.
everything ok with continuous goes 10W messages
This time with Gordon's new code it did provide an expected error message:
"statsproc Late Message TimeTag 20:47:30 expected"
and later looking at the data plots we are seeing holes in the 'slow logger'
values occassionally.  The logger messages were coming in nevertheless to
local storage.

Footnote: Rnet was clean and level,  RainGauge ditto.

The rain guage was found to be tilted approximately 25 degrees due to a loose ball joint. It was leveled and reset. This resulted in some false tips during the hour of 1300-1400 3 July. These should be eliminated from the record.

The RMY boom angle was confirmed at 4 degrees. This value has been in the system since the previous visit.June 27.

The net radiation sensor was leveled further during this visit. Leveling should be checked at all sites.

3Jul06 11:50 - 

Purpose: station was 'down'

In reality the station was still recording data but the goes transmitter was
locked up.  The adam.log showed that it had stopped transmittion at 0530UTC (consistent with the 1030pm web plot stoppage).

GOES came back up when power cycled.
Surge protection was added to the system to protect against this potential cause of the disruption.

The 512 Mb Cruzer usbstick (unnumbered) was replaced with 512Mb Cruzer #2 and data was uploaded to aster.