Notes

Sort by:
  • Reference Designator  
  • First Name
  • Created
  • Modified
  • 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),...

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

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

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

    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: 8
    Asset ID: 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...

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

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

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

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

    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-MFD35-01-VEL3DD000
    Deployment: 6
    9/30/16 5/31/17 The VEL3D scheduled sampling time has shifted out of the logging time window used by the DCL. Instrument recorded data the first time it ran at 17:30, but not since then. This is a recurring problem with the VEL3D. Fairly confident that the unit is still recording data, just it's schedule has shifted to 34 minutes after the hour. Will need to recover and download instrument data

    By Mike Smith, on 10/19/16
    Redmine Issue #11387

    CE01ISSM-MFD37-01-OPTAAD000
    Status: Not Operational
    10/2/17 4/2/18 MFN OPTAA not deployed OPTAA on MFN not deployed because instruments were not serviced in time by the vendor. We prioritized the NSIF OPTAAs over the MFN ones because of greater phytoplankton concentrations at the NSIF depth

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

    CE01ISSM-MFD37-01-OPTAAD000
    Deployment: 6
    10/1/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-MFD37-03-DOSTAD000
    Deployment: 8
    Asset ID: CGINS-DOSTAD-00483
    Status: Open Issue
    10/12/17 4/15/18 A recent routine control check of the O2 reference sensors, used for multipoint calibration of oxygen Optodes by the manufacturer, revealed a deviation with respect to accuracy. Regrettably this led us to conclude that all new and newly repaired multipoint calibrated oxygen optodes delivered from Aanderaa Norway between January 4th 2017 and October 20th 2017 are outside of specification. 3 Endurance DOSTAs are affected, two have been deployed. 478 - in inventory, will be sent back to...

    By Mike Smith, on 1/18/18
    Redmine Issue #13080

    CE01ISSM-MFD37-06-CAMDSA000
    Deployment: 8
    Asset ID: 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-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-MFD37-07-ZPLSCC000
    Deployment: 6
    11/15/16 The ZPLSC clock has drifted approximately 45 seconds, putting it outside of the original sample window. Sent a new mission file yesterday to change the time window. Went a little too far and have backed it back today. DCL37 will now turn on the ZPLSC port at 35 minutes after the hour and leave it on for 2 minutes. ZPLSC is reporting it's first condensed profile at ~36 minutes and 13 seconds after the hour. Will need to monitor over the course of the deployment to make sure any further clock...

    By Mike Smith, on 11/16/16

    CE01ISSM-MFD37-07-ZPLSCC000
    Deployment: 6
    1/1/17 4/23/17 The ZPLSC internal clock on CE01ISSM is slowly drifting out of alignment with GPS time. On two occasions now, I have had to shift the sampling window on the DCL to catch the reported condensed profile. Most recent data shows and estimated offset of approximately 1 minute 6 seconds. CI needs to develop methods for correcting internal instrument clock data when working with recovered instrument data for cases where the recovered instrument data provides more information (e.g. full acoustic...

    By Mike Smith, on 1/30/17
    Redmine Issue #11809

    CE01ISSM-RID16-01-OPTAAD000
    Deployment: 5
    7/28/16 10/2/16 Port was overcurrenting, so mission file changed to disable instrument.

    By Mike Smith, on 10/13/16
    Resolved: 10/25/16

    CE01ISSM-RID16-01-OPTAAD000
    Deployment: 8
    Asset ID: CGINS-OPTAAD-00149
    Status: Failed
    9/30/17 12/6/17 CE01ISSM NSIF OPTAA stopped working CE01ISSM NSIF OPTAA port stopped recording full data records in the last few days of October. This problem got worse over the week until no data were coming through. On 11/6 the OPTAA port was turned off.

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

    CE01ISSM-RID16-01-OPTAAD000
    Deployment: 6
    10/1/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-RID16-05-PCO2WB000
    Deployment: 6
    9/30/16 The PCO2W1 on the CE01ISSM-00006 NSIF failed immediately upon deployment. No data recorded.

    By Mike Smith, on 10/18/16
    Redmine Issue #11386

    1 of 11