Instrumentation at t01010

99/04:19:
SSB cu reported failure excessive error velocity (FEEV)
indications. 

99/04/08: VSKY has been spewing bad data from the ADCP sporadically.
 This is similar to the problem we had not long ago.  That ADCP is
still at RDI for check-out.  We don't yet know what the problem is.
Might it be a bad cable or connector?

99/02/26: 
The ADCP at the Skyway was replaced today and is back up and running.
Replacement system:

RDI Workhorse Monitor 1200 KHz ADCP, S/N 0134

98/12/22: DCB reconfigured PacComm, which had lost its
settings. Installed new battery.

98/10/26:

Geoffrey French wrote:
> The tilts at Skyway look just fine (less than 1 degree).
> The heading does show some variability between 30 and 34 degrees.
> Looking at all bins, it looks like the first obviously bad speeds occurred 10/23 1400gmt.
> There is no obvious indication in the other header data, tilts, heading, BIT, etc.
> The data remained flaky until 10/23 2057gmt. No flaky data since then.
>
> There is a file on the DAS, /tmp/t01010.stat that contains the
> data for all bins in a spread sheet style.
>
> There is also a file on the DAS, /tmp/t01010.cu that contains
> the PUFF style data, which includes all the data for each bin.
>
> Bins 1 and 2 appear to have stayed good, with 100% four beam
> solutions. By bin 6, it indicates 0% 4 beam, 98% rejected.
>
>                                         Geoffrey French
>                                         National Ocean Service
>                                         geoff.french@noaa.gov


98/10/01: VSKY is still having the same intermittent problem with bad
chksums.  WHG has a fix for that but we have been waiting until we
re-install the Egmont Channel system to install the fix.

98/6/18: investigated bad ADCP communications. Cable weaknesses were
taped up, but don't expect them to hold up.  Visibility sensor cleaned
and dessicant placed in signal protection box and rsm enclosure.

98/5/12: Workhorse ADCP reinstalled.

Back