RiverPro and RioPro ADCP Guide
October 2017
EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
Page 137
ALWAYS OUTPUT
HEADER
(6 BYTES + [2 x No. OF DATA TYPES])
FIXED LEADER DATA
(59 BYTES)
VARIABLE LEADER DATA
(65 BYTES)
PROFILE DATA
(as selected - cell size and number of cells is
dynamic)
WATER VELOCITY
(2 BYTES + 8 BYTES PER DEPTH CELL)
WATER CORRELATION MAGNITUDE
(2 BYTES + 4 BYTES PER DEPTH CELL)
WATER ECHO INTENSITY
(2 BYTES + 4 BYTES PER DEPTH CELL)
WATER PERCENT GOOD
(2 BYTES + 4 BYTES PER DEPTH CELL)
WATER STATUS
(2 BYTES + 4 BYTES PER DEPTH CELL)
BOTTOM TRACK
BOTTOM TRACK DATA
(89 BYTES)
SURFACE LAYER DATA
(as selected)
SURFACE LAYER LEADER
(7 BYTES)
SURFACE VELOCITY
(2 BYTES + 8 BYTES PER DEPTH CELL)
SURFACE CORRELATION MAGNITUDE
(2 BYTES + 4 BYTES PER DEPTH CELL)
SURFACE ECHO INTENSITY
(2 BYTES + 4 BYTES PER DEPTH CELL)
SURFACE PERCENT GOOD
(2 BYTES + 4 BYTES PER DEPTH CELL)
SURFACE STATUS
(2 BYTES + 4 BYTES PER DEPTH CELL)
AUTOMATIC WATER PROFILE (if selected)
AUTOMATIC MODE 3 SETUP DATA
(101 BYTES)
FIRMWARE STATUS
FIRMWARE STATUS DATA
(22 BYTES)
VERTICAL BEAM RANGE (RiverPro only)
VERTICAL BEAM RANGE
(9 BYTES)
VERTICAL BEAM
PROFILE DATA
(RiverPro only)
VERTICAL BEAM PROFILE LEADER
(40 BYTES)
VERTICAL BEAM WATER VELOCITY
(2 BYTES + 2 BYTES PER DEPTH CELL)
VERTICAL BEAM WATER CORRELATION MAGNITUDE
(2 BYTES + 1 BYTES PER DEPTH
CELL)
VERTICAL BEAM WATER ECHO INTENSITY
(2 BYTES + 1 BYTES PER DEPTH CELL)
VERTICAL BEAM WATER PERCENT GOOD
(2 BYTES + 1 BYTES PER DEPTH CELL)
VERTICAL BEAM WATER STATUS
(2 BYTES + 1 BYTES PER DEPTH CELL)
NMEA MESSAGES
NMEA GPS MESSAGES – if present
(15+ BYTES)
BEAM CORRECTION MATRIX (if selected)
BEAM CORRECTION MATRIX –
(34 BYTES)
ALWAYS OUTPUT
RESERVED
(2 BYTES)
CHECKSUM
(2 BYTES)
Figure 28.
PD0 Standard Output Data Buffer Format
The number of data cells output will depend on the depth during the ensemble and will vary from ensem-
ble to ensemble. Some data types will only appear in the output if enabled by command.
WinRiver II
may add additional bytes.
For example, WinRiver II does not add any bytes to the Bottom Track data, but does insert
data in place of other bytes. The Navigation NMEA strings (up to 275 bytes) are stored in the
*r.000 raw data between the Bottom Track data and the Reserved/Checksum data. WinRiver
II output data format is described in the WinRiver II User’s Guide.