Velocity Profiler (75 kHz)

Reference Designator
GP03FLMA-RIM01-02-ADCPSL003
Start Depth
500
End Depth
500
Location
ADCP Float
Current Status
Not Operational
Class
ADCPS (Velocity Profiler (long range))
Series
ADCPS-L
Science Discipline
Physical
Make
Teledyne RDI
Model
WorkHorse LongRanger Sentinel 75khz - inductive
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/GP03FLMA/RIM01/02-ADCPSL003/metadata
Method Data Stream Content Type
recovered_host adcps_jln_sio_mule_instrument Data Products Report M2M Stats Science
recovered_inst adcp_config Configuration Data Report M2M Engineering
recovered_inst adcp_engineering Engineering Data Report M2M Engineering
recovered_inst adcp_velocity_earth Earth Coordinates Data Products Report M2M Stats Science
telemetered adcps_jln_sio_mule_instrument Data Products Report M2M Stats Science
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 MV-1309 07/21/2013 06/15/2014 CGMGP-03FLMA-00001 CGINS-ADCPSL-18351 49.9795 -144.254 500 4127
2 MV-1404 06/17/2014 06/05/2015 CGMGP-03FLMA-00002 CGINS-ADCPSL-20502 49.9775 -144.246 500 4237
3 TN-323 06/06/2015 06/28/2016 CGMGP-03FLMA-00003 CGINS-ADCPSL-21393 49.9767 -144.246 520 4127
4 RB-16-05 07/01/2016 07/18/2017 CGMGP-03FLMA-00004 CGINS-ADCPSL-18260 49.9743 -144.24 4127
5 SR17-10 07/13/2017 CGMGP-03FLMA-00005 CGINS-ADCPSL-23380 50.0229 -144.361 4096
Metadata Start Date End Date Comment
GP03FLMA
Deployment: 4
7/4/16

Glider 365 deployed at Papa is failing to retrieve very much data from GP03FLMA-00004. The volume of data acquired from the mooring has been consistently low, seldom more than a few thousand bytes per attempt. The glider has recovered more data from GP02HYPM-D00004, so we think the glider modem is functioning properly. The glider is able to range successfully to the mooring from a number of ranges and orientations, however acoustic requests results in very small data files. UPDATE 11/15/2016: Data telemetry from FLMA-D00004 continues to be very poor for unknown reasons. There are multiple failed attempts. The glider modem configuration was inspected and the S4 shift register has been changed from S4=4 to S4=5 and back again with no measurable improvement in performance. The glider is able to range to the mooring multiple times. The error rates in the log file appear to be relatively high but there is no obvious reason for it.

By Lori Garzio, on 11/7/16

New Note

Metadata Start Date End Date Comment
GP03FLMA
7/21/13, 6:44 PM 6/14/14, 8:00 PM

Deployment 1: Mooring was deployed 10-15m shallower than planned. Telemetered data are not available for this deployment.

Id: 150 By: lgarzio

GP03FLMA
6/17/14, 2:00 AM 6/4/15, 8:00 PM

Deployment 2: Mooring was deployed 15-20m shallower than planned. Upon recovery of platform, biofouling was apparent on shallow CTDs.

Id: 151 By: lgarzio

GP03FLMA
6/6/15, 6:40 PM 6/28/16, 3:10 PM

Deployment 3: Mooring was deployed 10-15m deeper than planned.

Id: 152 By: lgarzio

GP03FLMA
6/30/16, 9:07 PM 7/18/17, 11:13 AM

Deployment 4: Mooring was deployed 10-15m deeper than planned.

Id: 153 By: lgarzio

GP03FLMA
7/13/17, 7:00 PM

Deployment 5: No data will be available via satellite telemetry. Data will be available when the mooring is recovered.

Id: 141 By: lgarzio