Users Manual Part 2
Table Of Contents
- SECTION 4 – SOFTWARE CONFIGURATION
- SECTION 5 – SYSTEM COMMISSIONING
- SECTION 6 – TROUBLESHOOTING
5 Each LRU has a LRU controller that:
Maintains the state of the LRU-
- Generates BITE events applicable to the LRU
- Sends relevant BITE events to the AES controller (for the AES
controller to make a decision on overall AES state, and for it to record
in its AES historical log).
- Record BITE event generated from the LRU.
6 The diagram that follows is a detailed description of how the AES
controller, the LRU controllers, the historical logs, and the means of access
to those logs interact. Refer to Figure 6-5.
Figure 6-5. AES and LRU Controller Interaction
7 The AES Controller resides in the Modman LRU.
8 Each LRU Controller monitors the LRU for BITE events. BITE events are
classified into two categories:
Faults: These are BITE events which have a SET state (occurring) or
CLEAR state (fault has disappeared).
-
- Events: These are BITE events which occur but do not have a set or
clear state.
Page 6-9
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