September 2017
Diagnostic Structures
The Sentinel V –Diagnostic Structures refers to the dynamic ADCP data associated with fault handling
and diagnostics.
Sentinel V Event Log
Sentinel V Event Log output is included only in systems configured with 47.xx firmware.
A new data type has been added to the PD0 to report events including faults. It is a variable length message
with entries for each active fault. Faults will only be reported if they are active when the ensemble is sent.
BYTE
7
1
2
3
4
5
6
7
8
4(N-1)+5
4(N-1)+6
Table 55.
Sentinel V Event Log Format
Binary
Field
Byte
1,2
ID Code
3,4
Fault Count Number of faults reported, max 255
5-6
Fault Entry
ID #1
7
Status
Code
8
Diagnostics
Code
4(N-1)+5,
Fault Entry
4(N-1)+6
ID #N
Page 286
EAR-Controlled Technology Subject to Restrictions Contained on the Cover Page.
BIT POSITIONS
6
5
4
SENTINEL V – EVENT LOG DATA ID (0x7004)
NUMBER OF FAULTS
FAULT ENTRY ID #1
STATUS CODE (FOR FAULT ENTRY ID #1)
DIAGNOSTICS CODE (FOR FAULT ENTRY ID #1)
FAULT ENTRY ID #N
(Repeat Status and Diagnostic Code fields #N ... )
Figure 118.
Sentinel V Event Log Configuration
Description
Stores the Sentinel V Event Log 7004 (70 04h). LSB is sent first.
Word containing fault code defined by Fault Code structure for Fault ID #1.
Byte containing status code defined by Fault Status structure for Fault ID #1
Byte containing event specific diagnostics info. For Fault ID #1
Word containing fault code defined by Fault Code structure for Fault ID #N
Sentinel V SC and RT Operation Manual
3
2
1
0
04h
70h
LSB
MSB
LSB
MSB
Need help?
Do you have a question about the SENTINEL V SELF-CONTAINED and is the answer not in the manual?