|recovered_host||nutnr_b_dcl_conc_instrument_recovered||Data Products||Report M2M Stats||Science|
|recovered_host||nutnr_b_dcl_dark_conc_instrument_recovered||Dark Sample Data Products||Report M2M Stats||Science|
|recovered_inst||nutnr_b_dark_instrument_recovered||Dark Sample Data Products||Report M2M Stats||Science|
|recovered_inst||nutnr_b_instrument_recovered||Data Products||Report M2M Stats||Science|
|telemetered||nutnr_b_dcl_conc_instrument||Data Products||Report M2M Stats||Science|
|telemetered||nutnr_b_dcl_dark_conc_instrument||Dark Sample Data Products||Report M2M Stats||Science|
|telemetered||nutnr_b_dcl_full_instrument||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
||5/14/16, 8:00 PM||4/14/17, 8:00 PM||
The NUTNR started to show signs of degraded performance, variable values spanning +- ranges, then completely failed.
||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
||10/2/17, 8:00 PM||3/2/18, 3:44 AM||
CAMDS not serviced by vendor in time for deployment
||12/17/17, 7:30 AM||
The Satlantic ISUS instrument has been discontinued, and all OOI ISUS units have been converted to the Sea-Bird SUNA model. A new data parser is in development, and any resulting data gaps will be filled once the parser has been delivered and the data are processed.
Id: 1411 By: lgarzio