How can I decode the status code in the telemetry data?
FollowWhen setting up your Signature or Generation 2 Aquadopp or AWAC for telemetry, a status code is always included in the telemetered data. This code provides useful information about the instrument's operational state and is presented in hexadecimal format. The status code is a 32-bit word, so to decode it, you must convert the hexadecimal number to binary. This can for example be done using the programmer mode in the calculator on most computers.
Note that binary bit positions are counted from right to left, starting at zero, so the rightmost bit is bit 0. Below is an example of how to decode a status code and a description of what each bit field represents.
For a full overview of the different data formats, please refer to the instrument-specific integrator's guide. The status code is the same as in the raw binary data, and is described in the Binary Data Formats chapter. The bit definitions are also summarized below.
Example
Suppose telemetry data reports the status code 2A480000. Converting this to binary gives the following 32-bit word: 0010 1010 0100 1000 0000 0000 0000 0000. See the figure below for an overview of the different bits and what they represent:
Bit 31-28: Wake up state
These bits indicate the wakeup state of the instrument. There are four different ways that can cause a wakeup of the instrument:
0 - Bad power: Input voltage too low for normal operation; the instrument is held in reset until voltage recovers (often caused by faulty cables or power supply).
1 - Power applied: Power was reapplied to the instrument after being removed for at least a few seconds.
2 - Break: A break signal was received via the communication port (e.g., during online measurement).
3 - RTC alarm: The internal real-time clock (RTC) woke the instrument. To reduce the power consumption the instruments enters sleep mode between measurements for most setups and the internal RTC will ensure that the instrument wakes up at the appropriate time.
Convert the four-bit word from binary to decimal to interpret the code (e.g. 0011 in binary is 3 in decimal, indicating that the wake up state is RTC alarm).
Bit 27-25: Orientation
These bits give you the orientation of the instrument.
0 - XUP: Instrument x-axis points up, heading reference axis is Z positive
1 - XDOWN: Instrument x-axis points down, heading reference axis is Z positive
2 - YUP: Instrument y-axis points up, heading reference axis is Z positive
3 - YDOWN: Instrument y-axis points down, heading reference axis is Z positive
4 - ZUP: Instrument z-axis points up, heading reference axis is X positive
5 - ZDOWN: Instrument z-axis points down, heading reference axis is X positive
7 - AHRS: AHRS reports orientation any way it points.
Convert the three-bit word from binary to decimal to interpret the code (e.g. 0101 in binary is 5 in decimal, indicating that the instrument is oriented with the z-axis pointing downward).
Bit 24-22: Auto orientation
These bits indicate how the instrument is detecting it's orientation.
0 - Fixed
1 - Auto
3 - AHRS3D
Bit 21-18: Previous wake up state
Same interpretation as bits 31–28, but indicating the previous wake-up reason.
Bit 17: Previous measurement skipped due to low voltage
0 - Normal operation
1 - Last measurement was skipped due to low input voltage.
Bit 16: Active configuration
0 - Settings for PLAN are active
1 - Settings for PLAN1 are active
Bit 15-12: Echosounder frequency index
Only relevant when using echosounder functionality. Valid numbers are 0, 1, and 2 (0000, 0001, and 0010 in binary) referring to frequencies 1, 2, or 3 as used in SET-/GETECHO.
Bit 11: Telemetry data
This bit indicates if telemetry is activated
Bit 10: Boost
This bit indicates if the boost is running
Bit 9-5: Echosounder frequency bin
Used only on the Signature100 which supports up to 5 packages pr frequency index.
Bit 1: Blanking distance scaling in cm
This bit indicates the scaling of the blanking distance in the raw binary data.
0 - Blanking distance is given in mm
1 - Blanking distance is given in cm
Comments
0 comments
Article is closed for comments.