Seafloor Multi-Function Node (MFN)

Reference Designator
CE01ISSM-MFD35

No deployments found

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-MFD35
Deployment: 6
10/29/16 5/15/17

The file system on the SD card used by embedded Linux card comprising DCL35 became corrupted on Saturday, October 29, 2016. I have captured and attached a log of the boot messages below.

https://www.embeddedarm.com/blog/preventing-filesystem-corruption-in-embedded-linux/

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.

By Mike Smith, on 11/7/16

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-MFD35
Deployment: 7
Status: Unavailable
5/12/17 10/31/17

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)

- Chris Wingard

By Mike Smith, on 5/17/17
Redmine Issue #12356

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

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.