|recovered_host||vel3d_cd_dcl_data_header_recovered||Header Data||Report M2M||Engineering|
|recovered_host||vel3d_cd_dcl_hardware_configuration_recovered||Hardware Configuration Data||Report M2M||Engineering|
|recovered_host||vel3d_cd_dcl_head_configuration_recovered||Header Configuration Data||Report M2M||Engineering|
|recovered_host||vel3d_cd_dcl_system_data_recovered||System Data||Report M2M||Engineering|
|recovered_host||vel3d_cd_dcl_user_configuration_recovered||Configuration Data||Report M2M||Engineering|
|recovered_host||vel3d_cd_dcl_velocity_data_recovered||Data Products||Report M2M Stats||Science|
|recovered_inst||vel3d_cd_dcl_data_header_recovered||Header Data||Report M2M||Engineering|
|recovered_inst||vel3d_cd_dcl_hardware_configuration_recovered||Hardware Configuration Data||Report M2M||Engineering|
|recovered_inst||vel3d_cd_dcl_head_configuration_recovered||Header Configuration Data||Report M2M||Engineering|
|recovered_inst||vel3d_cd_dcl_system_data_recovered||System Data||Report M2M||Engineering|
|recovered_inst||vel3d_cd_dcl_user_configuration_recovered||Configuration Data||Report M2M||Engineering|
|recovered_inst||vel3d_cd_dcl_velocity_data_recovered||Data Products||Report M2M Stats||Science|
|telemetered||vel3d_cd_dcl_data_header||Header Data||Report M2M||Engineering|
|telemetered||vel3d_cd_dcl_hardware_configuration||Hardware Configuration Data||Report M2M||Engineering|
|telemetered||vel3d_cd_dcl_head_configuration||Header Configuration Data||Report M2M||Engineering|
|telemetered||vel3d_cd_dcl_system_data||System Data||Report M2M||Engineering|
|telemetered||vel3d_cd_dcl_user_configuration||User Configuration Data||Report M2M||Engineering|
|telemetered||vel3d_cd_dcl_velocity_data||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|
||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.
||10/28/16, 8:00 PM||5/14/17, 8:00 PM||
The file system on the SD card used by embedded Linux card comprising DCL35 became corrupted on Saturday, October 29, 2016. Affected instruments are: [ADCPT, PCO2W, PHSEN, PRESF, VEL3D]. All instruments are set to log internally. Will not receive telemetered data, but do not anticipate complete loss of data.
||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:
||5/11/17, 8:00 PM||10/30/17, 8:00 PM||
Lost communication with DCL35, on the MFN of CE01ISSM sometime after 2017/05/12 04:32:31.744. Reason unknown. Attempted to log into the system and establish both an ssh connection and a minicom session with no success. Minicom session showed zero activity, suggesting the system is completely offline. 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 (status unknown)]
|4/2/18, 8:00 PM||
No data from this instrument is being logged or telemetered to shore. It's possible that the serial port on either the VEL3D or DCL has failed and/or is incorrectly setup or the driver software on the DCL has somehow failed.