H. Trouble Shooting Summary
(Ref. Fig. 011)
The various possibilities for using the TSM are summarized in the flow
chart in the following figure.
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 34
Feb 01/05
R
CES
INTENTIONALLY BLANK
R ∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 35
Feb 01/05
CES R Trouble Shooting Flow R Figure 011 (SHEET 1)
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 36
Feb 01/05 CES
R Trouble Shooting Flow R Figure 011 (SHEET 2)
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 37
Feb 01/05 CES
4. How to Use the CFDS
___________________
A. Types of systems
Systems have been divided into three categories in order to limit the complexity:
-
type 1
-
type 2
-
type 3 depending on the type of interface that they may have with the CFDIU. This system organization in three types essentially remains transparent for the operator as the CFDIU manages any differences. Nonetheless, their definitions make it possible to understand why certain menus are simplified.
(1) Type 1 systems
These systems are characterized by an input/output interface with the CFDIU of the ARINC 429 bus/ARINC 429 bus type. Most systems are provided with this type of interface. This type of system enables: - output: permanent transmission to the CFDIU of maintenance messages
generated during the current flight or during the last flight
-input: an operator to dialog on the ground with the BITEs and therefore have access to complementary information (test, ground report, etc.).
(2) Type 2 systems
These systems are characterized by an input/output interface with the
CFDIU of the discrete/ARINC 429 bus type.
This type of system enables:
- output: permanent transmission to the CFDIU of maintenance messages
generated during the current flight or during the last flight as well as permanent transmission while on the ground of maintenance messages generated on the ground
-input: an operator to launch on the ground the system test and to obtain the results via the output bus.
(3) Type 3 systems
These systems are characterized by an input/output interface with the
CFDIU of the discrete/discrete type.
This type of system enables:
- output: permanent transmission of the operating status (OK, not OK)
-input: an operator to launch on the ground the system test and to
obtain the result (OK, or not OK) via the discrete output. The CFDIU codes the corresponding maintenance message in plain language.
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 38
Feb 01/05
R
CES B. System BITE
(Ref. Fig. 012) When a system includes several computers, one of the computers collects the maintenance information and provides the link between the system and the CFDIU. It then realises the BITE function and therefore reports on behalf of all system computers. This architecture provides for a better targeted diagnosis by correlating data between system computers as well as reducing bus links with the CFDIU. For the operator, the resulting consequences are minor:
-it is the maintenance message itself which identifies, where necessary, the message source in the system example: source = ECAM1; message = SDAC1 : NO DATA FROM BMC1. The SDAC which is part of the Flight Warning System has generated the message.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址:A320 Trouble Shooting Manual 排故手册 介绍 2(12)