Data Concentrator Logger (DCL)

Reference Designator
CE06ISSM-MFD37-00-DCLENG000
Start Depth
29
End Depth
29
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/CE06ISSM/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 OC1410A 10/07/2014 04/10/2015 CGMCE-06ISSM-00001 R00006 47.1334 -124.268 30 30
2 Review OC1503D 04/10/2015 10/13/2015 CGMCE-06ISSM-00002 CGCON-MDCL37-00010 47.1311 -124.272 29 29
4 Review TN-342 05/06/2016 09/24/2016 CGMCE-06ISSM-00004 CGCON-MDCL37-00004 47.135 -124.273 29 29
6 Review SKQ201704S 04/13/2017 10/05/2017 CGMCE-06ISSM-00006 CGCON-MDCL37-00016 47.1341 -124.272 29 29
7 Review SKQ201715S 10/05/2017 03/28/2018 CGMCE-06ISSM-00007 CGCON-MDCL37-00001 47.1346 -124.272 29 29
8 Review SKQ201808S 03/28/2018 09/20/2018 CGMCE-06ISSM-00008 CGCON-MDCL37-00019 47.1336 -124.269 29 29
9 Review SR1813 09/24/2018 04/25/2019 CGMCE-06ISSM-00009 CGCON-MDCL37-00001 47.1348 -124.271 29 29
10 Review SKQ201910S 04/25/2019 10/12/2019 CGMCE-06ISSM-00010 CGCON-MDCL37-00004 47.1347 -124.271 29 29
11 Review SKQ201921S 10/12/2019 CGMCE-06ISSM-00011 CGCON-MDCL37-00010 47.1344 -124.271 29 29

No notes yet.

New Note

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

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

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

CE06ISSM
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:
DCL17
MOPAK
CTDBP (with attached FLORT)
VELPT
ACOMM
OPTAA
Have had to power off DCL17 and DCL16 and reduce call in frequency to 12 hours. Will still (at least should) receive data from MFN. Instruments affected are:
DCL17 (Buoy)
MOPAK
CTDBP3 (with FLORT)
VELPT1
UCSPP (aka ACOMM)
DCL16 (NSIF)
CTDBP1 (with DOSTA) (should internally log)
FLORT
PCO2W1 (should internally log)
PHSEN1 (should internally log)
OPTAA1
NUTNR (should internally log)
SPKIR
VELPT2 (should internally log)

Id: 899 By: michaesm

CE06ISSM
10/2/17, 8:00 PM 3/2/18, 3:44 AM

CAMDS not serviced by vendor in time for deployment

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

CE06ISSM-MFD37
Method: telemetered
10/17/19, 12:45 AM 5/23/20, 8:00 PM

Updated, 2020-05-24: Between 2019-10-17 and 2020-05-24, the clock on CPM3 was off by approximately 27 minutes. Communications between the buoy and the MFN were out of sync during this time period. The clock was automatically updated during routine operations on May 24, 2020 to the correct time, allowing communications and normal operations on the MFN to resume. *Communications to the seafloor sensors failed. Status of the instrumentation and data loggers is unknown. With the exception of the VEL3D and OPTAA, the sensors on the seafloor platform should continue to autonomously sample for the remainder of deployment. Until we recover and redeploy the mooring in the spring of 2020, no further telemetered data will be available from the seafloor sensors.

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