Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE01ISSM-MFD37-06-CAMDSA000 Deployment: 8 Asset: CGINS-CAMDSA-00110 Status: Failed |
10/14/17, 12:00 AM | 4/2/18, 12:00 AM |
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
|
CE09OSSM-MFC31 Deployment: 4 |
1/22/17, 12:00 AM | 4/15/17, 12:00 AM |
The high voltage lines providing power to the MFN via the CVT for CE09OSSM-00004 shorted out yesterday 2017-01-22 at 08:31 UTC: <snip from 20170122.pwrsys.log> Sea state was high, but not unusual for this time of year (see attached plot). Have disabled future power scheduling to the MFN and applied an override to disable the CVT. No further data will be logged from the instruments on the MFN. This affects: On DCL35:
By Mike Smith,
on 3/23/17
|
CE05MOAS-GL327-02-FLORTM000 Deployment: 4 Status: Unavailable |
3/2/17, 12:00 AM | 3/8/17, 12:00 AM |
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 |
CE01ISSM-MFD37-07-ZPLSCC000 Deployment: 6 |
1/1/17, 12:00 AM | 4/23/17, 12:00 AM |
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
|
CE01ISSM-MFD37-07-ZPLSCC000 Deployment: 6 |
11/15/16, 12:00 AM |
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 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 |
|
CE09OSSM-MFD37-07-ZPLSCC000 Deployment: 4 |
9/26/16, 12:00 AM | 5/15/17, 12:00 AM |
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
|
CE01ISSM-MFD37-06-CAMDSA000 Deployment: 6 |
10/30/16, 12:00 AM | 5/1/17, 12:00 AM |
Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.
By Mike Smith,
on 10/25/16
|
CE06ISSM-MFD37-06-CAMDSA000 Deployment: 5 |
9/27/16, 12:00 AM | 5/1/17, 12:00 AM |
Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.
By Mike Smith,
on 10/25/16
|
CE09OSSM-MFD37-06-CAMDSA000 Deployment: 4 |
9/21/16, 12:00 AM | 5/1/16, 12:00 AM |
Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.
By Mike Smith,
on 10/25/16
|
CE07SHSM-MFD37-06-CAMDSA000 Deployment: 4 |
10/21/16, 12:00 AM | 5/31/17, 12:00 AM |
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
|
CE07SHSM-MFC31 Deployment: 3 |
8/12/16, 12:00 AM | 9/27/16, 12:00 AM |
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
By Mike Smith,
on 10/20/16
|
CE07SHSM-MFD37-07-ZPLSCC000 Deployment: 3 |
8/12/16, 12:00 AM | 9/27/16, 12:00 AM |
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
|
CE04OSSM-RID26-06-PHSEND000 |
10/14/16, 12:00 AM |
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
|
|
CE02SHSM-RID26-06-PHSEND000 Deployment: 3 |
8/1/16, 12:00 AM | 8/8/16, 12:00 AM |
> 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 |
GP05MOAS-PG575-06-PARADM000 Deployment: 1 |
|||
GP05MOAS-PG575-06-PARADM000 Deployment: 1 |
99% of the sci_bsipar_par values for deployment 1 are outside of global ranges. sci_bsipar_par is the unscaled L0 PAR data product. The global ranges for this parameter are the same as for the scaled L1 PAR data product [0.0, 2500.0]. The global range for sci_bsipar_par should be reviewed. By Lori Garzio, on 3/19/20 |
||
GP05MOAS-PG575-04-FLORTO000 Deployment: 1 |
The arrays for the following variables are all NaNs: sci_bb3slo_b470_units, flort_o_bback_b470_total, flort_o_bback_b532_total, sci_bb3slo_b660_units, flort_o_bback_b660_total. According to the provenance.json (attached), the following cal values are missing: CC_1_dark_counts_volume_scatter, CC_1_scale_factor_volume_scatter, CC_1_measurement_wavelength, CC_2_dark_counts_volume_scatter, CC_2_scale_factor_volume_scatter, CC_2_measurement_wavelength, CC_3_dark_counts_volume_scatter, CC_3_scale_factor_volume_scatter, and CC_3_measurement_wavelength. By Lori Garzio, on 3/19/20 |
||
GP05MOAS-PG575-04-FLORTO000 Deployment: 1 |
There are no global ranges in the system for sci_bb3slo_b470_units, flort_o_bback_b470_total, flort_o_bback_b532_total, sci_bb3slo_b660_units, and flort_o_bback_b660_total. By Lori Garzio, on 3/19/20 |
||
GP05MOAS-PG575-01-CTDGVM000 Deployment: 1 |
25% of deployment 1 sci_seawater_density values are NaNs, and some data missing from recovered_host stream are found in the telemetered stream (Redmine 14654) By Lori Garzio, on 3/19/20 |
||
GP05MOAS-PG515-06-PARADM000 Deployment: 2 |
99% of the sci_bsipar_par values for deployment 2 are outside of global ranges. sci_bsipar_par is the unscaled L0 PAR data product. The global ranges for this parameter are the same as for the scaled L1 PAR data product [0.0, 2500.0]. The global range for sci_bsipar_par should be reviewed. By Lori Garzio, on 3/19/20 |