17-Oct-12
personnel: JohnM, TomH.
Weather / Ops:
Clear but rather windy from the west. Probably not a good day for what the science needs.
Sensor Status / Issues:
Overall the network is doing very well. Everything has been staying up. The Flux computer died again this morning and had to be rebooted but that only effects our ability to monitor data; Gully is ingesting/archiving just fine.
a17: The comms/dsm has been intermittent this day. Best guess is that it's the comm/blue-tooth. Checked on this in afternoon and indeed it's been the source. Possibly the cable: connections ok but I dressed the cable a bit to reduce 'wiggling in the wind.' Need to watch this.....
a2: 1m CSAT is having a diag bit set (4, bit 2) but the values uvwtc all look good. The CSAT manual says that bit 2 indicates "poor signal lock", which may be caused by an obstruction in one of the paths. That was not the case. I tried shielding it from the strong wind and make a 'sweat-shirt' zero chamber which helped. Probably signal strength/sensativity settings, need to swap.
TRH's: see other entry about speeding up the data rate on the serial versions, stns 1,2,3,5,6,c20,m21,m22
c20: TRH 1.5m outage ~9:00-10:00MST (15-16Z). When reprogramming the sensor sampling rate the little devil didn't come back up. DSM power cycling 'eio 7 0' and 'eio 7 1' did not work (need to check that the jumpers are set on that port for the remote power cycle method), so a manual power cycling was done. 2.5m trh was coated/greased completing the basic protection.
a8: TRH's intermittent this morning. This appears to be the 'mote \r\n' software bug. Need to fix and reprogram today.....
To Do:
- Swap CSAT at A2
- Swap A17 BTradio/cable.
- Fix mote \r\n bug and reprogram A8's mote