Table of Contents
Advertisement
B
2. Failure Processing
After each functional test or monitoring cycle is complete, the failures
detected are prioritized and logged in fault memory if the severity of the
fault allows. The fault memory will keep the three highest priority faults per
power cycle.
When a fault is detected that would cause the TAS Processor to declare
TAS inoperative or failed , the following responses, regardless of failure cat-
egory, will be initiated:
A. Set the 'TAS Valid Output' discrete to invalid.
B. Inhibit ATCRBS interrogations from TAS.
C. De-activate the 'normal' TAS display functions.
D. Cancel any TA voice message.
If a fault is detected that would invoke one of the above responses, then
that response will be accomplished within one second of detecting the fault.
3. Failure Categories
A. Catastrophic
The severity of a catastrophic failure will preclude any software from exe-
cuting.
B. Fatal
The severity of a fatal failure will preclude any TAS surveillance software
from executing.
C. Critical
The severity of a critical failure will force the system to run in a failed
state.
D. System
This type of failure is used for inputs from system sources external to the
TAS Processor.
3.1.13.3 EGPWS Self Test Input
Level 1 cockpit self-test will annunciate "System OK" when the system is
operating properly.
J10-121 GND_DISC_07 (Self Test)
Rev 3, August/2001
10609I03.CDL
KMH 880/KTA 870
Page 3- 11
Advertisement
Table of Contents
