All of the inshore surface moorings suffer from an issue called the 'top of the day problem.' A race condition exists in the CPM firmware when transferring daily log files harvested from the various sub-components in a buoy system (e.g. DCL16, CPM3, DCL35, etc) over the Iridium RUDICS connection. The primary CPM rsync's data files from the various sub-components to a central data directory. The first time a daily file is created/copied into that directory (usually shortly after midnight), a compressed copy of the file is created and that compressed file is queued up in a separate text file for transmission to shore. The transfer routine reads that text file and processes the files from that list in order from top to bottom. Once that compressed file is transferred to shore, no further updates for that file are sent to shore. Meanwhile, the CPM continues to rsync data from the different sub-components, updating the original daily log file. The net result is that data is accumulating in the daily log file for an instrument, but we may see only one record (or none) depending on when the rsync job occurred and the compressed file was created and staged for transfer to shore. This affects telemetered data only.

Id: 897 By: michaesm

Battery on CTDBP1 has been depleted. Unit is no longer recording data.

Id: 402 By: michaesm
Flag: not_operational Exclude: No

Correcting the iridium data telemetry issues, permitting full telemetry of data files, resulting in greater power consumption than anticipated. Result is power level of the battery pack has dropped below operational limits and subsystems can no longer power instruments. Shutting the mooring down, and placing in a low power maintenance mode. 11 instruments offline.

Id: 898 By: michaesm
Flag: not_operational Exclude: No

The buoy main battery voltage is being drawn down faster than expected. Have shutdown further power to DCL17 and to the OPTAA on DCL16. This takes the following instruments offline:
DCL17
MOPAK
CTDBP (with attached FLORT)
VELPT
ACOMM
OPTAA
Have had to power off DCL17 and DCL16 and reduce call in frequency to 12 hours. Will still (at least should) receive data from MFN. Instruments affected are:
DCL17 (Buoy)
MOPAK
CTDBP3 (with FLORT)
VELPT1
UCSPP (aka ACOMM)
DCL16 (NSIF)
CTDBP1 (with DOSTA) (should internally log)
FLORT
PCO2W1 (should internally log)
PHSEN1 (should internally log)
OPTAA1
NUTNR (should internally log)
SPKIR
VELPT2 (should internally log)

Id: 899 By: michaesm

CAMDS not serviced by vendor in time for deployment

Id: 1236 By: michaesm
Flag: not_operational Exclude: No

The conductivity measurement was near zero/flatlined at the start of the deployment. Over the course of the next ~2 months the measurements stepped up until they fell into agreement with the data from the surface and near-bottom CTDs. Review of the time series suggests the conductivity cell was plugged at the start of the deployment, with the blockage clearing over the course of the next few weeks.

Id: 1547 By: wingardc
Flag: fail Exclude: No

Reduced battery power on the mooring (unforeseen delay of mooring recovery well past the originally scheduled date) has resulted in the decision to reduce the operational schedule for this sensor for. Data, at a reduced sample rate, will be collected and telemetered to shore for as long as possible.

Id: 2198 By: wingardc

Reduced battery power on the mooring (unforeseen delay of mooring recovery well past the originally scheduled date) has resulted in the decision to power off the data logger port for this sensor for the remainder of the deployment. No further data will be telemetered from this instrument, though recovered instrument data should be available after the mooring is recovered.

Id: 2201 By: wingardc
Flag: not_available Exclude: No