(f) Creation and save of the fault context in the BITE memories
- Composition of the fault context:
-------------------------------------------------------------------------------
| NFIDS | NLRU |
|-----------------------------------------------------------------------------|
| FLIGHT LEG |
|-----------------------------------------------------------------------------|
| UTC |
|-----------------------------------------------------------------------------|
| DATE |
|-----------------------------------------------------------------------------|
| RESANA |
|-----------------------------------------------------------------------------|
| RESANAC (not available for FM BITE) |
|-----------------------------------------------------------------------------|
| RESANAM (not available for FM BITE) |
|-----------------------------------------------------------------------------|
R | SNAPSHOT (80 variables displayed in five 16-bit words: W1, W2, W3, W4, W5) |
-------------------------------------------------------------------------------
R * NFIDS: Number generated by the FIDS to manage the fault context
R * NLRU: Fault number
* FLIGHT LEG
* UTC
* DATE
R * RESANA: filled in from COMMAND side only
R * RESANAC: filled in from COMMAND side only
R * RESANAM: filled in from MONITOR side and recopied on COMMAND
R side
* Snapshot
- Make-up of the fault context
R * All information, except for NFIDS, making up the fault
R context is stored in the context at the end of the analysis at
R BITE level.
R * As the NFIDS is generated by the FIDS, this fault context
R area is only filled in after reception, by the FIDS, of a
R malfunction report sent by the COMMAND side of the FAC or the
R FG, which detected the failure, or by the FM.
R * For the FM, RESANAC and RESANAM areas do not exist.
- Save of fault context.
This context is saved in the non-volatile memories.
1EFF : ALL 1 22-91-00Page 18 1 1 Feb 01/05 1 1 1CES 1
(g) Creation and transmission of the anomaly report
R R R R R * At the end of the analysis, a malfunction report is sent to the FIDS by the computer which detected the fault. * This malfunction report is composed of the RESANA (C/M result of analysis within TSD) and the two LRU codes (described above) corresponding to the suspected LRUs.
------------------------------------------------------
| | | RESANA | | | |-----------------------|----------------------------| | LRU 2 CODE | LRU 1 CODE | ------------------------------------------------------
(h) Management of the malfunction reports by the FIDS
R R R R R 1_ On reception of a malfunction report, the FIDS generates and sends, to the BITE of the computer which recorded the fault, either a clearing command if the failure occurs within a phase in which the storage of the failure is not required, or an NFIDS management number. This number will be used to retreive the fault. The FIDS then records this malfunction report in the non-volatile memories.
R R 2_ Management of identical malfunction reports:- 2 malfunction reports are considered as identical when the following three conditions are met: . their two error code areas are identical
. they come from the same computer . they occurred during the same flight. In this case, only the first malfunction report received by the FIDS is recorded and each time a new identical
R malfunction report is received, an event counter, linked to the recorded report, is incremented (from 1 to 4). (Ref. Fig. 004)
(i) Consolidation of the malfunction reports by the FIDS, 3rd phase analysis
R R R R R 1_ The FIDS sends to the CFDIU a message comprising: - an initial word including the following information: . OF (Origin of the Failure): set to 1 when the fault is internal to the AFS system . FW (Failure Witness): set to 1 as long as fault is present . CFF (Current Fault Flag): set to 1 as long as the system is affected by at least one internal or external fault
1EFF : ALL 1 22-91-00Page 19 1 1 Feb 01/05 1 1 1CES 1 1EFF : ALL 1 22-91-00Page 20 1 1 Feb 01/05 1 1 1CES 1 1EFF : ALL 1 22-91-00Page 21 1 1 Feb 01/05 1 1 1CES 1 1EFF : ALL 1 22-91-00Page 22 1 1 Feb 01/05 1 1 1CES 1
R . BHF (BITE History Flag): Set to 1 as soon as the BITE
R memory is loaded by the detection of an internal or external
failure on the last 63 flights.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：A320飞机维护手册 AMM AUTO FLIGHT 自动飞行4(117)
