Data Concentrator Logger (DCL)

Reference Designator
CE01ISSM-MFD37-00-DCLENG000
Start Depth
25
End Depth
25
Location
Current Status
Engineering
Class
DCLEN (Data Concentrator Logger (DCL))
Series
DCLEN-G
Science Discipline
Make
WHOI
Model
Data Concentrator Logger
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/CE01ISSM/MFD37/00-DCLENG000/metadata
Method Data Stream Content Type
recovered_host cg_dcl_eng_dcl_cpu_uptime_recovered CPU Uptime Data Report M2M Engineering
recovered_host cg_dcl_eng_dcl_dlog_aarm_recovered Accelerometer Data Report M2M Engineering
recovered_host cg_dcl_eng_dcl_dlog_mgr_recovered Data Log Manager Report M2M Engineering
recovered_host cg_dcl_eng_dcl_dlog_status_recovered Data Logger Status Report M2M Engineering
recovered_host cg_dcl_eng_dcl_error_recovered Error Data Report M2M Engineering
recovered_host cg_dcl_eng_dcl_gps_recovered GPS Data Report M2M Engineering
recovered_host cg_dcl_eng_dcl_msg_counts_recovered Message Counts Data Report M2M Engineering
recovered_host cg_dcl_eng_dcl_pps_recovered Pulse Data Report M2M Engineering
recovered_host cg_dcl_eng_dcl_status_recovered Status Data Report M2M Engineering
recovered_host cg_dcl_eng_dcl_superv_recovered Leak Detect Data Report M2M Engineering
telemetered cg_dcl_eng_dcl_cpu_uptime CPU Uptime Data Report M2M Engineering
telemetered cg_dcl_eng_dcl_dlog_aarm Accelerometer Data Report M2M Engineering
telemetered cg_dcl_eng_dcl_dlog_mgr Data Log Manager Report M2M Engineering
telemetered cg_dcl_eng_dcl_dlog_status Data Logger Status Report M2M Engineering
telemetered cg_dcl_eng_dcl_error Error Data Report M2M Engineering
telemetered cg_dcl_eng_dcl_gps GPS Data Report M2M Engineering
telemetered cg_dcl_eng_dcl_msg_counts Message Counts Data Report M2M Engineering
telemetered cg_dcl_eng_dcl_pps Pulse Data Report M2M Engineering
telemetered cg_dcl_eng_dcl_status Status Data Report M2M Engineering
telemetered cg_dcl_eng_dcl_superv Leak Detect Data Report M2M Engineering
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 Review OC1404B 04/17/2014 08/16/2014 CGMCE-01ISSM-00001 CGCON-MDCL37-00001 44.6583 -124.096 25 25
2 Review OC1410A 10/10/2014 04/12/2015 CGMCE-01ISSM-00002 CGCON-MDCL37-00001 44.6583 -124.096 25 25
3 Review PS1506A 06/03/2015 10/07/2015 CGMCE-01ISSM-00003 CGCON-MDCL37-00011 44.6583 -124.095 25 25
6 Review AT37-03 09/30/2016 04/17/2017 CGMCE-01ISSM-00006 CGCON-MDCL37-00001 44.6598 -124.095 25 25
7 Review SKQ201704S 04/19/2017 10/12/2017 CGMCE-01ISSM-00007 CGCON-MDCL37-00014 44.6563 -124.095 25 25
8 Review SKQ201715S 10/12/2017 04/01/2018 CGMCE-01ISSM-00008 CGCON-MDCL37-00011 44.6597 -124.095 25 25
9 Review SKQ201808S 04/03/2018 09/30/2018 CGMCE-01ISSM-00009 CGCON-MDCL37-00016 44.6568 -124.096 25 25
10 Review SR1813 09/29/2018 04/27/2019 CGMCE-01ISSM-00010 CGCON-MDCL37-00011 44.6598 -124.095 25 25
11 Review SKQ201910S 04/20/2019 10/22/2019 CGMCE-01ISSM-00011 CGCON-MDCL37-00020 44.6568 -124.095 25 25
12 Review SKQ201921S 10/20/2019 CGMCE-01ISSM-00012 CGCON-MDCL37-00003 44.6598 -124.095 25 25

No notes yet.

New Note

Metadata Start Date End Date Comment
CE01ISSM
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

CE01ISSM
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.

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

CE01ISSM
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.

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

CE01ISSM
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:
DCL16
CTDBP + DOSTA (probably internally recording)
FLORTNUTNR (probably internally recording)
PHSEN (probably internally recording)
PCO2W (probably internally recording)
OPTAA
SPKIR
VELPT (probably internally recording)

DCL17
MOPAK
CTDBP + FLORT
VELPT (probably internally recording)
ACOMM
DCL35
ADCPT (probably internally recording)
PCO2W (probably internally recording)
PHSEN (probably internally recording)
PRESF (probably internally recording)
VEL3D (probably internally recording)
DCL37
CTDBP + DOSTA (probably internally recording)
OPTAA
ZPLSC (probably internally recording)

Id: 871 By: michaesm
Flag: not_available Exclude: No

CE01ISSM-MFD37
Method: telemetered
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. As a result, telemetry from the data loggers and instrumentation on the seafloor platform has ceased. We expect the system to continue autonomous operations and hope to download data from the data loggers and instruments after the seafloor platform is recoverd in the spring of 2020.

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