-
To better manage the effect of the test on the system and its ground handling the test function may be divided into two groups:
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 50
Feb 01/05
R
CES
Examples of Main Menu
Figure 016
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 51
Feb 01/05 R CES
. BASIC TEST (OR SYSTEM TEST)
. COMPLEMENTARY TESTS.
This makes it possible to have at least one test available at
the terminal gate (the basic test) which is quickly to start-up
by a single technician, the other tests making it possible to
increase the global coverage level of the tests where useful
and possible.
All these tests are run on the ground from the MCDU using,
first of all, the CFDIU menu (SYSTEM REPORT/TEST) then the
system MENU.
*
Basic test or system test This test has no effect on the aircraft and does not require that any long or complex actions be performed by the operator. Consequently, this test may be initiated from the cockpit by a single operator whenever required during stopovers. All faults present on ground and actually detected by the system will be analyzed and reported by this test. Furthermore, it must be run before any other test to check the integrity of the computer housing the BITE.
*
Complementary tests (Ref. Fig. 017) These tests may affect the aircraft (and may require actions by the operator). In fact these tests send stimuli to various components such as actuators, valves, etc. For this reason, CAUTIONS may be displayed on the MCDU before activation of test. The wording of the cautions is in fact simply a reminder of the consequences on the aircraft following test activation. In fact, the safety procedures associated with these tests are in the AMM. Consequently, normally these tests are not performed during a short stopover. Test names are related to the tested parts.
These tests can also be menu-guided tests. The actions to be taken are displayed in plain language on the MCDU. (Description of the initial configuration, description of the actions, wording of the questions to which the operator must respond). Test names are related to the tested parts.
(b) Presentation of the test pages
-Certain information may require several pages. Each page is then numbered and the MCDU NEXT PAGE function key is used to run through the test
-In certain cases, the system waits until the operator has performed an action to continue the test. Then there is a limited time out so as not to stop in this configuration when the monitored signals are blocked. This implies that the operator action must be performed before this time out.
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 52
Feb 01/05
R
CES
Example of Caution
Figure 017
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 53
Feb 01/05 R CES
-A dash may be shown when data is not available. This does not necessarily mean that an effective failure is present. Only maintenance messages indicate possible failures.
(c)
Initial aircraft configuration for test activation The general configuration of the aircraft for test activation is basically as follows:
-aircraft on ground
-engines stopped
-all systems power supplied (ADIRS, FADEC may be off)
-pushbutton switches and switches in normal configuration. If a test calls for a different configuration, this configuration will be described in the AMM. To limit BITE complexity all these conditions are assumed to be correctly applied by the operator. Consequently, if a difference is detected by a system it is considered as a fault and therefore generates a maintenance message in the test results. In all cases, it is recommended to restart the tests indicating faults in the results to eliminate any possible disturbances or wrong initial conditions.
(d)
TEST IN PROGRESS When a test is run without any operator action being requested the TEST IN PROGRESS can be displayed on the MCDU.
(e)
Test results The result of a test is one of the following:
-
The mention TEST OK, PASS, NO FAULT, ...:
The test has not detected any faults
-
The display of maintenance messages on the MCDU: The test has detected at least one fault. In certain multiple fault cases, the test may only indicate the first fault encountered. In fact, certain faults prevent to run the test more extensively. Test re-running after repair of the fault is therefore always necessary to check whether there is another fault or not. Only the mention TEST OK, PASS, NO FAULT ... is proof that the test has not detected any other faults.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：A320 Trouble Shooting Manual 排故手册 介绍 2(17)
