Users Manual

ALL
EFFECTIVITY
© Honeywell International Inc. Do not copy without express permission of Honeywell.
Page 6-18
22 Apr 2019
23-15-49
SYSTEM DESCRIPTION, INSTALLATION, AND MAINTENANCE MANUAL
ASPIRE-400
the Modes of Operation and individual processor sections of this document. CBITE
executes during the normal operation of the SDU. It monitors health in a non-intrusive
manner so as to not adversely affect normal SDU and SATCOM operations. It determines
the health of the SDU the SATCOM system and the interfaces to other externally
connected systems. Some continuous mode monitoring does not have a predictable
period as it is only possible when a specific function is active (e.g. VSWR can only occur
when RF transmission occurs).
(4) As well as its own fault detection, the ACD is responsible for the management of fault
detection done by the APP processor, the Channel cards, and the external SATCOM
LRUs.
I. Fault and Event Annunciation
(1) The ACD annunciates the presence of one or more confirmed faults internal to the SDU
via the:
(a) Front panel Fault LED
(b) Web GUI
(c) Applicable Pilot Control and Display schemas.
NOTE: Not all pilot control and display schemas feature fault reporting.
(2) The ACD annunciates the presence of one or more confirmed interface faults, or external
LRU faults on the following interfaces:
(a) Web GUI
(b) Applicable Pilot Control and Display schemas.
NOTE: There is no intent to encode the source of the fault nor to indicate the
presence of environmental or interface faults on the LED.
J. POST Fault and Event Monitoring
(1) POST refers to tests that are executed at the power on of the system but not
continuously. Commanded self-test when permitted can cause a re-execution.
K. SDU POST Monitoring
(1) The SDU records POST faults and events related to:
(a) Configuration strapping including:
(b) Unsupported strapping
(c) Strapped identity (i.e. SDU#1 or SDU#2).
(2) The SDU records POST Operational events for:
(a) SDU SW configuration
(b) SDU HW configuration.
(3) The ACD records POST Security events related to:
(a) The unsigned hash or similar data as calculated for the part or file as part of the
system power-up process, for the software parts and files stored in non- volatile
memory, and protected from intentional corruption through the use of digital
signatures or similar mechanisms.
1 This only applies to software parts or files that persist across multiple
powercycles.
DRAFT
3rd rvw Draft as of:
29 January, 2020