September
2017
Sentinel V SC and RT Operation Manual
Page 248
EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
Only the averaged PD0 files created by
Velocity
will have Percent Good data.
PD0 Output Data Format
The following description is for the Sentinel V
PD0
output data format. The binary output data formats are
composed of at least one data type, i.e. a group of bytes all related by their dynamic or field. For instance
in the
PD0
data format, variables that do not change during the deployment are stored in the
data type of leader ID 0000h, whereas the dynamic variables, except velocities, which dynamically change
during the deployment are stored under the
data type of leader ID 8000h. This distinc-
tion is based on the dynamic; other distinctions are present such as velocity types such as data type of
leader ID 0001h which groups all the
data. The ADCP sends all the data for a given
type for all depth cells and all beams before the next data type begins.
The advantage of using the leader ID is that one can simply scan for them as the binary data is received in
real time on the serial lines and then use the output data format description table to jump directly to the
desired data. The
PD0
Header ID is 7F7Fh, which makes it easy to detect. In the
PD0
Header are the num-
ber of bytes in the ensemble, the number of data types and the offset respective to each data type location
in the binary ensemble. This gives you the choice between jumping down to the data type using the offsets
or detecting the data type ID after you have detected the header ID.
PD0
binary output data format provides a
that describes the data included in the ensemble since
some data type presence in the
PD0
output are dependent on ReadyV or Plan parameters. For example, if
the vertical beam is not activated, then there will be no vertical beam data type in the ensemble.
