other systems for the same fault. It will be the one retained by the
CFDIU (refer to the PFR). This message is called internal.
The other maintenance messages related to the same fault are called
external by the other systems. They have less accuracy, have not
priority and are not recorded in this case by the CFDIU. Only their
origins are memorized by the CFDIU as identifiers (refer to the PFR).
Therefore, each system has in memory an information linked to every
message transmitted to the CFDIU which defines its internal or
external attribute so that the CFDIU can give priority to the most
accurate one.
When no priority messages are received by the CFDIU for the same
event it is considered that the accuracy is equal for all messages
received. In this case the CFDIU retains the first one received.
Remark: as a general rule, the LRUs incriminated by the maintenance
messages shown in the PFR are part of the systems which generated the
internal messages.
Example:
(Ref. Fig. 014)
A fault of the ADM sensor is detected by the ADIRU.
The ADIRU sends a fault message (e.g. ADIRU1: NO ADM 19FP1 DATA) to
the CFDIU and invalidates some parameters on its output buses (e.g.
Airspeed). This fault message is coded as internal by the ADIRU.
The users of the ADIRU data (EIS, AFS, ECAM, FADEC, ...) detect the
loss of the airspeed parameter. They send fault messages to the
CFDIU, coded as external (e.g. EIS1: NO ADIRU1 DATA).
The CFDIU stores the fault message from the ADIRU and the name of the
systems which have detected the fault.
The PFR is:
SOURCE IDENTIFIERS
ADIRU1 : NO ADM19 FP1 DATA ADIRU1 EIS, AFS, ECAM FADEC
E. Maintenance functions
(1) First group: the PFR
(a) Description of the PFR A maintenance report on the last flight is automatically printed eighty knots plus thirty seconds after touch down. This document is the Post Flight Report (PFR). The PFR is a result of the CFDS automatic operating mode. This report is the main source of information used to initiate trouble shooting and to decide on the required maintenance actions.
(Ref. Fig. 015)
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 45
Feb 01/05
R
CES
Example of ADM Sensor Fault Detection
Figure 014
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 46
Feb 01/05 R CES
POST FLIGHT REPORT
Figure 015
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 47
Feb 01/05 R CES
A backup of the printed PFR is available on the MCDU. It should only be used if the printed PFR is not available as the information is less complete and the presentation is not so friendly. Conditional maintenance operations are carried out in response to the observations made by the flight crew in the LOG BOOK. This information represents a cockpit effect as previously defined.
The following data are recorded in the PFR:
-ECAM WARNING MESSAGES The ECAM WARNING MESSAGES contains:
-
the warning message available on the upper ECAM display unit
-
the Maintenance Status. These warning messages are associated with their ATA reference (aid for cross referencing with the maintenance message).
-FAULTS: Maintenance messages are listed in the PFR in the FAILURE MESSAGES part. Additional information is associated with each message.
-FLIGHT PHASE - GMT Flight operational phases (CLIMB, CRUISE, etc.) are indicated in coded form in the PFR in front of the warning message. The time (GMT) is also given in front of the warning message and the maintenance message. . FLIGHT PHASE decoding:
02 : Engine start + 3 mn up to TO Power
03 : TO Power up to 80 kts
04 : 80 kts up to lift off
05 : Climb
06 : Cruise
07 : Descent
08 : Touch down up to 80 kts
09 : 80 kts up to last engine shut down.
-ATA: This is the ATA chapter of the first suspected component. It is the entry point to the technical documentation. It may also be an aid in relation to the corresponding warning message and with the GMT.
-SOURCE: The source is the system (for system BITE) or the computer which generated the maintenance message retained by the CFDIU for this event and recorded in the PFR.
中國航空網(wǎng) www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：A320 Trouble Shooting Manual 排故手冊 介紹 2(15)
