Deployment 1 - PAR ball bent upon recovery of the glider

By Lori Garzio, on 9/1/16

> Plots of the pH data for CE02SHSM indicate that unit may be experiencing biofouling, causing increased variability in the data signal.

Whatever was causing the spiky signal appears to have cleared and resolved itself. Signal looks good for now.

By Mike Smith, on 10/14/16

pH data was looking really good until 2016-10-14 10:30 UTC. Possible fouling, although also possible system was damaged during large storm event.

Will need to monitor to seeing if fouling clears.

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

Controller stopped telemetering on 8/29/2016. Issue is under investigation.

By Lori Garzio, on 10/20/16
Redmine Issue #11394

The Power System Controller on CE07SHSM indicates the power connection to the MFN short-circuited on 2016-08-12 at 23:30 UTC. Failure is indicated by decreased voltage (70 VDC instead of 380 VDC) and increased current draw (1900 mA instead of 120 mA) to the CVT. This symptom is indicative of a short-circuit in the power lines of either the stretch hose (most likely) or EM Chain. In the past, this failure has been associated with a failed stretch hose.

Have disabled all further power and communications with the MFN. Therefore, there is no telemetered data for this reference designator.

By Mike Smith, on 10/20/16
Redmine Issue #10988

The Power System Controller on CE07SHSM indicates the power connection to the MFN short-circuited on 2016-08-12 at 23:30 UTC. Failure is indicated by decreased voltage (70 VDC instead of 380 VDC) and increased current draw (1900 mA instead of 120 mA) to the CVT. This symptom is indicative of a short-circuit in the power lines of either the stretch hose (most likely) or EM Chain. In the past, this failure has been associated with a failed stretch hose.

Have disabled all further power and communications with the MFN. This means no more telemetered data from:

ADCPT2
VEL3D
CTDBP2 + DOSTA
PRESF
PCO2W
PHSEN2
OPTAA2
ZPLSC

By Mike Smith, on 10/20/16
Redmine Issue #10988

For no apparent reason, the CAMDS stopped reporting data on Friday October 21 at 12:30 UTC. Do not know if the system is continuing autonomously.

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

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

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

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

Deployment 2 - The inductive modem connected to this instrument stopped responding to requests for data after 11/17/2015 22:06 UTC, data status unknown.

By Lori Garzio, on 7/21/16

Deployment 1 - glider deployed on 06/27/2016 and recovered on 07/5/2016 due to a leak in the forward compartment.

By Lori Garzio, on 8/1/16
Redmine Issue #10848

Deployment 4 - instrument not telemetering data. Issue under investigation. UPDATE 11/15/2016: Either this instrument is having issues, or the entire secondary controller is malfunction. There are multiple low battery warnings that appear to originate from the SSIOC. The issue is under investigation.

By Lori Garzio, on 8/1/16
Redmine Issue #10853

The ZPLSC scheduled sample time has shifted out alignment with the DCL sampling window. Last sample was on 2016/09/26 17:36. Sent new mission file changing the sample window on 2016-10-13, but that did not correct the issue. Will send new mission file with broader sample window.

Have attempted to expand sample window. Will see if that corrects issue

By Mike Smith, on 10/20/16
Redmine Issue #11404

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 drift is accounted for. But, should be good for now.

There will be a data gap of about 7 days in the telemetered data. The recovered data will have the full record.

By Mike Smith, on 11/16/16

Instrument stopped sending valid data

By Lori Garzio, on 1/27/17
Redmine Issue #11856

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 profiles rather than condensed). If left uncorrected, the recovered instrument data could be out of alignment with co-located sampling.

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

Instrument is not sending valid data records via telemetry.

By Lori Garzio, on 2/1/17
Redmine Issue #11857

Instrument is not sending valid data records via telemetry.

By Lori Garzio, on 3/13/17
Redmine Issue #11857

The PAR (PARAD) and ECO triplet (FLORT) was later turned off on 2017-03-02 to further prolong battery life to recovery date.

By Mike Smith, on 3/15/17