Users Manual Part 2
Table Of Contents
- SECTION 4 – SOFTWARE CONFIGURATION
- SECTION 5 – SYSTEM COMMISSIONING
- SECTION 6 – TROUBLESHOOTING
9 The LRU records the BITE event into a specific LRU log, dependent on
the type of fault or event.
NOTE: Not all BITE events indicate an error situation. BITE events
are also used for storing significant events in the historical
logs, either on the LRU or in the AES controller, or for
informing the AES controller of important system wide
information.
10 BITE events are sent to the AES controller. The AES controller may react
to an event by changing the overall state of the AES system. Actions
include disabling the system, rebooting the system, etc.
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
service, 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 BUC-HPA LRU Logs are available from the
KANDU LRU SFTP service, accessible through one of the Ethernet
connections on the Modman.
- FMA LRU Logs are available from the 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.
Page 6-10
23-15-84
EFFECTIVITY
ALL
11 Nov 2020
© Honeywell International Inc. Do not copy without express permission of Honeywell.
SYSTEM DESCRIPTION, INSTALLATION, AND MAINTENANCE MANUAL
JetWave™ MCS-8562 Terminal