User's Manual Part 6

Page 7-10
3 Mar 2017
23-15-29
SYSTEM DESCRIPTION AND INSTALLATION MANUAL
JetWave™ System
© Honeywell International Inc. Do not copy without express permission of Honeywell.
11 The AES controller has a sub-part called the AES controller fault and event handler
which is in charge of responding to BITE events reported by the AES controller or
a LRU controller.
12 The AES controller has its own historical logs which allow it to record events about
the whole system.
13 Included on the diagram are the Secure File Transport Protocol (SFTP) services
and the GUI services which allow the users to access the AES and LRU historical
logs.
• AES controller logs are available from the Modman LRU GUI or SFTP
ser
vice, accessible through one of the Ethernet connections on the
Modman.
• Modman LRU logs are available from the Modman LRU SFTP service,
accessible
through one of the Ethernet connections on the Modman.
• KANDU LRU Logs and KRFU LRU Logs are available from the KANDU LRU
SFTP ser
vice, accessible through one of the Ethernet connections on the
Modman.
• TMA/FMA LRU Logs are available from the TMA/FMA LRU SFTP service,
accessible
through one of the Ethernet connections on the Modman.
14 The LRU and AES remember information about BITE events that have occurred, in
both non-volatile memory and volatile memory.
15 The historical logs are kept by the LRU and AES controller.
16 Each BITE event is described by an LRU code, encoded in three numbers (L1, L2
and L3) to uniquely identify the event.
17 Section 5 has more details on the format of this LRU code system.
18 The BITE events themselves have a description of the L1 thru L3 code and the
additional text to be used for that event.
19 Each BITE event is also associated with a reaction table which describes the
confirmation actions, and event actions, the LRU should take when this BITE event
occurs. For events that are reported to the AES controller, there is a reaction table
describing what the AES controller should do when the event is reported to it.
(a) Status Memory
1 The AES Controller remembers the following information:
• The AES Controller maintains an overall mode of operational state, of
UNKNO
WN (Default), DATA LOAD, CRITICAL FAULT, COMMANDED
MODE, OPERATIONAL MODE.
• The AES controller maintains an overall service state, of A
VAILABLE
(default) or UNAVAILABLE. This service state, when set to UNAVAILABLE,
disables user service and transmission.
Draft as of 31 May 2017