September
2017
Sentinel V SC and RT Operation Manual
Page 246
EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
Comparing Sentinel V PD0 to Work-
Horse PD0
The WorkHorse
PD0
(pd zero, not the letter o) data (Figure 100, page 246) is not exactly the same as the
Sentinel V
PD0
output data (Figure 101, page 247);
•
The WorkHorse ADCP and Sentinel V Real-Time uses a command file to configure the ADCP us-
ing a two-character command. For example, the WS command is used to set the water profile cell
size in WorkHorse ADCPs. The Sentinel V Self-Contained ADCPs use ReadyV to configure the
ADCP. There are no equivalent commands between WorkHorse/Sentinel V RT and Sentinel V SC
ADCPs.
•
The Sentinel V ADCPs have additional data formats to include the vertical beam data and fea-
tures.
•
The Sentinel V ADCPs
PD0
output is always in binary format.
•
The Sentinel V ADCPs
PD0
output can be read by TRDI’s WinADCP and Velocity software only.
Always Output
HEADER
(6 BYTES + [2 x No. OF DATA TYPES])
FIXED LEADER DATA
(59 BYTES)
VARIABLE LEADER DATA
(65 BYTES)
WorkHorse WD command
WorkHorse WP command
VELOCITY
(2 BYTES + 8 BYTES PER DEPTH CELL)
CORRELATION MAGNITUDE
(2 BYTES + 4 BYTES PER DEPTH CELL)
ECHO INTENSITY
(2 BYTES + 4 BYTES PER DEPTH CELL)
PERCENT GOOD
(2 BYTES + 4 BYTES PER DEPTH CELL)
STATUS
(2 BYTES + 4 BYTES PER DEPTH CELL)
WorkHorse BP command
BOTTOM TRACK DATA
(85 BYTES)
Always Output
RESERVED
(2 BYTES)
CHECKSUM
(2 BYTES)
Figure 100.
WorkHorse ADCP PD0 Standard Output Data Buffer Format
For details on the WorkHorse Output Data Format, see the WorkHorse Commands and
Output Data Format Guide. This guide can be downloaded our online customer portal at
http://www.teledynemarine.com/rdi
