3-D Single Point Velocity Meter

Reference Designator
CE06ISSM-MFD35-01-VEL3DD000
Start Depth
29
End Depth
29
Location
Multi-Function Node
Current Status
Unknown
Class
VEL3D (3-D Single Point Velocity Meter)
Series
VEL3D-D
Science Discipline
Physical
Make
Nortek
Model
VECTOR
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/CE06ISSM/MFD35/01-VEL3DD000/metadata
Method Data Stream Content Type
recovered_host vel3d_cd_dcl_data_header_recovered Header Data Report M2M Engineering
recovered_host vel3d_cd_dcl_hardware_configuration_recovered Hardware Configuration Data Report M2M Engineering
recovered_host vel3d_cd_dcl_head_configuration_recovered Header Configuration Data Report M2M Engineering
recovered_host vel3d_cd_dcl_system_data_recovered System Data Report M2M Engineering
recovered_host vel3d_cd_dcl_user_configuration_recovered Configuration Data Report M2M Engineering
recovered_host vel3d_cd_dcl_velocity_data_recovered Data Products Report M2M Stats Science
recovered_inst vel3d_cd_dcl_data_header_recovered Header Data Report M2M Engineering
recovered_inst vel3d_cd_dcl_hardware_configuration_recovered Hardware Configuration Data Report M2M Engineering
recovered_inst vel3d_cd_dcl_head_configuration_recovered Header Configuration Data Report M2M Engineering
recovered_inst vel3d_cd_dcl_system_data_recovered System Data Report M2M Engineering
recovered_inst vel3d_cd_dcl_user_configuration_recovered Configuration Data Report M2M Engineering
recovered_inst vel3d_cd_dcl_velocity_data_recovered Data Products Report M2M Stats Science
telemetered vel3d_cd_dcl_data_header Header Data Report M2M Engineering
telemetered vel3d_cd_dcl_hardware_configuration Hardware Configuration Data Report M2M Engineering
telemetered vel3d_cd_dcl_head_configuration Header Configuration Data Report M2M Engineering
telemetered vel3d_cd_dcl_system_data System Data Report M2M Engineering
telemetered vel3d_cd_dcl_user_configuration User Configuration Data Report M2M Engineering
telemetered vel3d_cd_dcl_velocity_data 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 Review OC1410A 10/07/2014 04/10/2015 CGMCE-06ISSM-00001 CGINS-VEL3DD-11084 47.1167 -124.268 30 30
2 Review OC1503D 04/10/2015 10/13/2015 CGMCE-06ISSM-00002 CGINS-VEL3DD-09668 47.1311 -124.272 29 29
3 Review OC1510A 10/13/2015 05/06/2016 CGMCE-06ISSM-00003 CGINS-VEL3DD-11084 47.1333 -124.271 29 29
4 Review TN-342 05/06/2016 09/24/2016 CGMCE-06ISSM-00004 CGINS-VEL3DD-09668 47.135 -124.273 29 29
5 Review AT37-03 09/27/2016 04/15/2017 CGMCE-06ISSM-00005 CGINS-VEL3DD-12264 47.1336 -124.272 29 29
6 Review SKQ201704S 04/13/2017 10/05/2017 CGMCE-06ISSM-00006 CGINS-VEL3DD-11707 47.1341 -124.272 29 29
7 Review SKQ201715S 10/05/2017 03/28/2018 CGMCE-06ISSM-00007 CGINS-VEL3DD-12264 47.1346 -124.272 29 29
8 Review SKQ201808S 03/28/2018 09/20/2018 CGMCE-06ISSM-00008 CGINS-VEL3DD-12604 47.1336 -124.269 29 29
9 Review SR1813 09/24/2018 CGMCE-06ISSM-00009 CGINS-VEL3DD-11710 47.1348 -124.271 29 29

No notes yet.

New Note

Metadata Start Date End Date Comment
CE06ISSM
10/7/14, 3: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: 897 By: michaesm

CE06ISSM
7/26/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. 11 instruments offline.

Id: 898 By: michaesm
Flag: not_operational Exclude: No

CE06ISSM-MFD35-01-VEL3DD000
9/26/16, 8:00 PM 4/14/17, 8:00 PM

Instrument recorded data the first time it ran, 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.

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

CE06ISSM
12/31/16, 7:00 PM 4/22/17, 8:00 PM

The buoy main battery voltage is being drawn down faster than expected. Have shutdown further power to DCL17 and to the OPTAA on DCL16. This takes the following instruments offline:
DCL17
MOPAK
CTDBP (with attached FLORT)
VELPT
ACOMM
OPTAA
Have had to power off DCL17 and DCL16 and reduce call in frequency to 12 hours. Will still (at least should) receive data from MFN. Instruments affected are:
DCL17 (Buoy)
MOPAK
CTDBP3 (with FLORT)
VELPT1
UCSPP (aka ACOMM)
DCL16 (NSIF)
CTDBP1 (with DOSTA) (should internally log)
FLORT
PCO2W1 (should internally log)
PHSEN1 (should internally log)
OPTAA1
NUTNR (should internally log)
SPKIR
VELPT2 (should internally log)

Id: 899 By: michaesm

CE06ISSM-MFD35
5/10/17, 8:00 PM 10/30/17, 8:00 PM

Lost communication with DCL35, on the MFN of CE06ISSM sometime after 2017/05/11 12:32:17.552. Suspect failed/corrupted SD card based on results of minicom session with DCL35 (see attached). 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 (recording internally), PHSEN (recording internally), VEL3D (offline)

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

CE06ISSM
10/2/17, 8:00 PM 3/2/18, 3:44 AM

CAMDS not serviced by vendor in time for deployment

Id: 1236 By: michaesm
Flag: not_operational Exclude: No