Oregon Inshore Surface Mooring

Reference Designator
CE01ISSM
Array Name
Coastal Endurance
Description
A Surface Mooring is a type of mooring that contains a surface buoy floating on the sea surface and instruments located at fixed depths through the water column. The surface buoy provides a platform on which to secure surface instruments, allowing for the collection of data in the air and in the water, as well as an antenna to transmit data to shore via satellite.
Latitude
44.66
Longitude
-124.095
Min Depth
0
Max Depth
25
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 OC1404B 04/17/2014 08/16/2014 CGMCE-01ISSM-00001 44.6583 -124.096
2 OC1410A 10/10/2014 04/12/2015 CGMCE-01ISSM-00002 44.6583 -124.096
3 PS1506A 06/03/2015 10/07/2015 CGMCE-01ISSM-00003 44.6583 -124.095
4 OC1510A 10/08/2015 05/10/2016 CGMCE-01ISSM-00004 44.6601 -124.096
5 TN-342 05/18/2016 10/02/2016 CGMCE-01ISSM-00005 44.6583 -124.095
6 AT37-03 09/30/2016 04/17/2017 CGMCE-01ISSM-00006 44.6598 -124.095
7 SKQ201704S 04/19/2017 10/12/2017 CGMCE-01ISSM-00007 44.6563 -124.095
8 SKQ201715S 10/12/2017 CGMCE-01ISSM-00008 44.6597 -124.095
Metadata Start Date End Date Comment
CE01ISSM
4/17/14 10/1/16

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.

By Mike Smith, on 7/11/16
Redmine Issue #8151

CE01ISSM
8/8/16 10/4/16

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.

By Mike Smith, on 8/11/16
Redmine Issue #10922

CE01ISSM
Deployment: 6
12/12/16 5/31/17

On Monday, Mon Dec 12 15:30:00 2016, stopped receiving any data from CTDBP3. No indication as to possible cause.

By Mike Smith, on 1/3/17
Redmine Issue #11710

CE01ISSM
Deployment: 6
2/6/17 5/1/17

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)
FLORT
NUTNR (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)

By Mike Smith, on 3/9/17
Redmine Issue #11967

CE01ISSM
Deployment: 8
Asset: CGMCE-01ISSM-00008
Status: Failed
10/24/17 4/2/18

DSL on CE01ISSM stopped working

We experienced poor communications via the DSL to the MFN after hooking the system up on deck (10/12). While we were able to adjust the communication rate to correct for this, subsequently (10/18) there have been times when the surface buoy did not connect to the MFN via the DSL. This is how data from the MFN are telemetered to the buoy.

All sensors on the MFN appear to be working based on power consumption data, but science data transfers from the MFN are no longer working at all (10/24).

By Mike Smith, on 12/6/17
Redmine Issue #12958

New Note

No annotations yet.