
SERIAL AND UDP OUTPUT STRING FORMATS
Echotrac E20 Operator's Manual
p. 51 of 60
November 25, 2020
Version 8
Uncontrolled Technology Subject to Restrictions Contained on the Cover Page.
APPENDIX C – SERIAL AND UDP OUTPUT STRING FORMATS
C.1
Echotrac DBX (for Universal message)
o
The DBX is an ODOM-defined format that is like NMEA formats but not an NMEA compliant
format. Checksum is not included, and “DBX” is not registered by NMEA.
o
The representation [+]ddd.ddd (or [+]hh.hh) is a fixed point representation of a number.
o
The number of digits (d’s, h’s, or other letter) before and after the decimal point are fixed.
There may be leading zeros but not leading spaces.
o
A + designates that a sign is present. In that case it will display as – or +. Fields not prefixed
with + will have no sign.
o
DBX is sent per ping. If a channel (A or B) does not have detections for that ping or is not
enabled/pinging, its corresponding data fields in the message will be populated with zeroes.
Table 14: Echotrac DBX
Field Name
Format
Description
1
Prefix
string
$DBX
2
Date time UTC
YYYY-MM-DD
Thhmmss.sss
UTC time, current time (ISO8601-2:2019)
Notes:
Even if the UI is showing other time zones on its display, it is the UTC that is
synced to the SBES and the UTC that is contained in this message.
Although ISO8601 defines a range of formats, the only format available in
the DBX string is the one given here.
3
Time status
t
0 = UI PC, 2 = GPS with PPS, 3 = NTP server, 9 = not synchronizing at
the moment
4
Depth channel A ddddd.ddd
Depth below transducer (channel A)
5
Intensity A
+iii.ii
Intensity in dB at measured depth (channel A)
6
Draft A
+rr.rrr
Draft of transducer (channel A), always applied
7
Depth channel B ddddd.ddd
Depth below transducer (channel B)
8
Intensity B
+iii.ii
Intensity in dB at measured depth (channel B)
9
Draft B
+rr.rrr
Draft of transducer (channel B), always applied
10
Unit
u
Unit for all distance fields in the record:
1 = Meter, 2 = Feet
Note: This field defines the unit for the fields 4, 6, 7, 9, 11, 13.
11
Heave value
+hhh.hhh
Measured heave value
Note: If a heave sensor is not connected, measured heave is reported as zero.
12
Heave status
c
Heave correction: 0=off; 1=on
Note: When heave correction is on, heave is already applied to the depth fields.
13
Sound velocity
ssss.ss
Applied sound velocity
14
End of frame
<CR><LF>
Carriage return and line feed
Full string format:
$DBX,YYYY-MM-DDThhmmss.sss,t,ddddd.ddd,+iii.ii,rr.rrr,ddddd.ddd,+iii.ii,rr.rrr,u,
+hhh.hhh,c,ssss.ss<CR><LF>
Example:
$DBX,2019-09-30T205959.999,2,00123.999,-216.14,00.950,00124.321,-218.14,01.100,1,
-002.230,1,1435.98<CR><LF>
Example means:
30 Mar 2019 at 20:59:59.999 PPS synchronized, depth of 123.999m corrected for heave for channel A at -216.14dB and
0.950m draft, depth of 124.321m corrected for heave for channel B at -218.14dB and 1.100m draft, -2.230m heave,
sound velocity 1435.98m/s
Summary of Contents for Echotrac E20
Page 10: ......
Page 59: ......
Page 60: ...Echotrac E20 Operator s Manual Document Number OM19133 8 Part Number 1013460 ...