Bio-acoustic Sonar (Coastal)

Reference Designator
Review Status
Will Not Review
Not Delivered Via uFrame
ZPLSC (Bio-acoustic Sonar (Coastal))
Make / Model
ASL Environmental Sciences / AZFP

Dataset Reviews Last processed:

QC Check Info
Dep. Preferred Method Stream DD FD SG EG Gaps GD TS Rate (s) Pressure Comp. Time Order Valid Data Missing Data Data Comp. Missing Coords. Review
3 telemetered zplsc_c_instrument / Todo
4 telemetered zplsc_c_instrument / Todo
5 telemetered zplsc_c_instrument / Todo
6 telemetered zplsc_c_instrument / Todo
7 telemetered zplsc_c_instrument / Todo
8 telemetered zplsc_c_instrument / Todo
9 telemetered zplsc_c_instrument / Todo
Data Ranges Review Images

Test Notes

All good!

System Annotations

Metadata Start Date End Date Comment
4/17/14, 4:45 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

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

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

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:
CTDBP + DOSTA (probably internally recording)
FLORTNUTNR (probably internally recording)
PHSEN (probably internally recording)
PCO2W (probably internally recording)
VELPT (probably internally recording)

VELPT (probably internally recording)
ADCPT (probably internally recording)
PCO2W (probably internally recording)
PHSEN (probably internally recording)
PRESF (probably internally recording)
VEL3D (probably internally recording)
CTDBP + DOSTA (probably internally recording)
ZPLSC (probably internally recording)

Id: 871 By: michaesm
Flag: not_available Exclude: No

6/7/19, 10:40 AM 10/22/19, 7:57 PM

The instrument operates on an internally controlled schedule. Due to an instability of the internal instrument clock as a function of temperature, the instrument's operating schedule will drift out of alignment with the limited window allowed by the datalogger schedule. The result is a loss of telemetered data. The instrument should continue to sample and record internally. Comparisons between the instrument clock and the datalogger clock (GPS based) while telemetry was active will permit characterization of the internal instrument clock offset and drift (generally fairly linear).

Id: 1678 By: wingardc
Flag: not_available Exclude: No

Method: telemetered
12/6/19, 1:30 PM

The ZPLSC internal clock has drifted out of the sampling window, resulting in a loss of telemetered data.

Id: 1838 By: wingardc
Flag: not_available Exclude: No

Method: telemetered
1/11/20, 1:45 PM

During a large storm event on 2020-01-11, the surface buoy and NSIF broke free and went adrift. As a result, telemetry from the data loggers and instrumentation on the seafloor platform has ceased. We expect the system to continue autonomous operations and hope to download data from the data loggers and instruments after the seafloor platform is recoverd in the spring of 2020.

Id: 1896 By: wingardc
Flag: not_available Exclude: No

Review Notes

Metadata Start Date End Date Comment
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
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

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
Redmine Issue #11809

New Note