September
2017
Sentinel V SC and RT Operation Manual
Page 264
EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
Binary
Byte
Field
Description
5
Depth Cell 1,
Field 3
Stores correlation magnitude data for depth cell #1, beam #3. See above.
6
Depth Cell 1,
Field 4
Stores correlation magnitude data for depth cell #1, beam #4. See above.
7 – max
Cells 2 – max.
These fields store correlation magnitude data for depth cells 2 through maximum #
cells (depending on the ReadyV setting) for all four beams. These fields follow the
same format as listed above for depth cell 1.
The echo intensity scale factor is about 0.45 dB per ADCP count. The Sentinel V ADCP does not directly
check for the validity of echo intensity data.
Table 41:
Echo Intensity Data Format
Binary
Byte
Field
Description
1,2
ID Code
Stores the echo intensity data identification word (00 03h).
3
Depth Cell 1,
Field 1
Stores echo intensity data for depth cell #1, beam #1. See above.
4
Depth Cell 1,
Field 2
Stores echo intensity data for depth cell #1, beam #2. See above.
5
Depth Cell 1,
Field 3
Stores echo intensity data for depth cell #1, beam #3. See above.
6
Depth Cell 1,
Field 4
Stores echo intensity data for depth cell #1, beam #4. See above.
7 – max
Cells 2 – max
These fields store echo intensity data for depth cells 2 through maximum # of cells
(depending on the ReadyV Setting) for all four beams. These fields follow the same
format as listed above for depth cell 1.
The Sentinel V ADCP always collects single ping data; therefore, raw data output from the Sentinel V
ADCP will not contain % good data. However, the average
PD0
files created by Velocity will have % good
data. The percent-good data field is a data-quality indicator that reports the percentage (0 to 100) of good
data collected for each depth cell of the velocity profile. The setting of the Coordinate Transformation (de-
fault coordinate system is beam) determines how the Sentinel V references percent-good data as shown
below.
EX command
Coord. Sys
Velocity 1
Velocity 2
Velocity 3
Velocity 4
Percentage Of Good Pings For:
Beam 1
BEAM 2
BEAM 3
BEAM 4
xxx00xxx
Beam
Percentage Of:
xxx01xxx
Instrument
3-Beam Transformations
(note 1)
Transformations Rejected
(note 2)
More Than One
Beam Bad In Bin
4-Beam
Transformations
xxx10xxx
Ship
xxx11xxx
Earth
Note 1. Because profile data did not exceed correlation threshold.
Note 2. Because the error velocity threshold was exceeded.