Digital Still Camera

Reference Designator
CE01ISSM-MFD37-06-CAMDSA000
Start Depth
25
End Depth
25
Location
Multi-Function Node
Current Status
Camera
Class
CAMDS (Digital Still Camera with Strobes)
Series
CAMDS-A
Science Discipline
Biological
Make
Kongsberg
Model
Modified OE14-408
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/CE01ISSM/MFD37/06-CAMDSA000/metadata

No streams found

Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
3 Review PS1506A 06/03/2015 10/07/2015 CGMCE-01ISSM-00003 CGINS-CAMDSA-00110 44.6583 -124.095 25 25
7 Review SKQ201704S 04/19/2017 10/12/2017 CGMCE-01ISSM-00007 CGINS-CAMDSA-00122 44.6563 -124.095 25 25
8 Review SKQ201715S 10/12/2017 04/01/2018 CGMCE-01ISSM-00008 CGINS-CAMDSA-00110 44.6597 -124.095 23 25
9 Review SKQ201808S 04/03/2018 CGMCE-01ISSM-00009 CGINS-CAMDSA-00113 44.6568 -124.096 23 25
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-MFD37-06-CAMDSA000
Deployment: 6
10/30/16 5/1/17

Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

By Mike Smith, on 10/25/16
Redmine Issue #11427

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-MFD37-06-CAMDSA000
Deployment: 8
Asset: CGINS-CAMDSA-00110
Status: Failed
10/14/17 4/2/18

CE01ISSM CAMDS stopped working

The CAMDS experienced some kind of failure wherein the sampling schedule suddenly changed from every 4 hours to approximately every 5 minutes. The camera stopped taking pictures 10/14 after either blowing through its batteries or disk space. This problem has not been seen before.

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

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

Metadata Start Date End Date Comment
CE01ISSM
4/16/14, 8:00 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