|recovered_host||mopak_o_dcl_accel_recovered||Accelerometer Data||Report M2M||Engineering|
|recovered_host||mopak_o_dcl_rate_recovered||Rate Data||Report M2M||Engineering|
|telemetered||mopak_o_dcl_accel||Accelerometer Data||Report M2M||Engineering|
|telemetered||mopak_o_dcl_rate||Rate Data||Report M2M||Engineering|
|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|
||4/17/14, 4: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: 868 By: michaesm
||8/7/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.
||12/11/16, 7:00 PM||5/30/17, 8:00 PM||
On Monday, Mon Dec 12 15:30:00 2016, stopped receiving any data from CTDBP3. No indication as to possible cause.
||2/5/17, 7:00 PM||4/30/17, 8:00 PM||
The buoy and mfn battery voltages have been drawn down faster than expected. Have shutdown further power to DCL16, DCL17, CPM3, and DCL37 (DCL35 failed several weeks ago). This takes the following instruments offline:
|1/11/20, 1:45 PM||
During a large storm event on 2020-01-11, the surface buoy and NSIF broke free and went adrift. The buoy and NSIF were recovered from the beach the following mooring. No further data will be collected from these systems for the remainder of this deployment.