|recovered_host||presf_abc_dcl_tide_measurement_recovered||Tide Measurement Data Products||Report M2M Stats||Science|
|recovered_host||presf_abc_dcl_wave_burst_recovered||Wave Burst Data Products||Report M2M Stats||Science|
|recovered_inst||presf_abc_tide_measurement_recovered||Wave Burst Data Products||Report M2M Stats||Science|
|recovered_inst||presf_abc_wave_burst_recovered||Wave Burst Data Products||Report M2M Stats||Science|
|telemetered||presf_abc_dcl_tide_measurement||Tide Measurement Data Products||Report M2M Stats||Science|
|telemetered||presf_abc_dcl_wave_burst||Wave Burst Data Products||Report M2M Stats||Science|
|Deployment||Cruise||Start Date||Stop Date||Mooring Asset||Node Asset||Sensor Asset||Latitude||Longitude||Deployment Depth||Water Depth|
No notes yet.
|Metadata||Start Date||End Date||Comment|
||10/7/14, 3:45 PM||9/30/16, 8:00 PM||
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
||7/26/16, 8:00 PM||10/3/16, 8:00 PM||
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.
||12/31/16, 7:00 PM||4/22/17, 8:00 PM||
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:
Id: 899 By: michaesm
||5/10/17, 8:00 PM||10/30/17, 8:00 PM||
Lost communication with DCL35, on the MFN of CE06ISSM sometime after 2017/05/11 12:32:17.552. Suspect failed/corrupted SD card based on results of minicom session with DCL35 (see attached). With the exception of the VEL3D, all instruments hosted by DCL35 are autonomous. No further data should be expected from: ADCPT (recording internally), PRESF (recording internally), PC02W (recording internally), PHSEN (recording internally), VEL3D (offline)
||10/2/17, 8:00 PM||3/2/18, 3:44 AM||
CAMDS not serviced by vendor in time for deployment