曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

R  - The FIDS detects CFDIU failure or absence by detecting 
R  non-refresh of the control word. 
R  - In this case, it uses for operation the GROUND/FLIGHT 
R  information given by the wired discrete NOSE GEAR PRESD 
R  which it receives directly: 
R  * on the ground : the FIDS sends a command to the BITEs 
R  requesting them not to record any more internal or external 
R  faults. 
R  * in flight : the FIDS sends the command DC1 to the BITEs 
R  (Ref. previous table).
 (b) Interpretation and execution of the FIDS commands by the FAC, FG
 and FM BITEs
 1_ Each BITE
 FAC 1 COM
 FAC 1 MON
 FAC 2 COM
 FAC 2 MON
 FG1  COM
 FG1  MON
 FG2  COM
 FG2  MON
 FM1
 FM2 
R  receives from the FIDS: - a control word 
R  - Date, UTC.
 2_ Interpretation and execution of the commands in the ground or
 flight area 
R  Each BITE stores a certain quantity of fault information (Ref. 
R  fault context) in the non-volatile memories.
 These memories are split into several areas: 
R  - Ground area: this area is capable of storing 3 faults and 
R  their context. It is cleared at each ground/flight
 transition. 
R  - Flight area: this area is capable of storing 30 faults and 
R  their context. 
R
 When the memories are full, the first-in fault is eliminated
 first. 
R  Each BITE executes these FIDS commands:

 

 - No fault recording
 - Fault recording in ground area
 - Fault recording in flight area 
R  - Fault confirmation request (Ref. 3rd phase analysis) 
R
 - Triggering variable re-initialization request (Ref. Fault
 Detection).
 3_ Use of DATE and UTC information
 This information is used by the BITEs to enhance their fault
 contexts. 
R  4_ Emergency operation in case of inoperative FIDS.
 - The BITEs detect absence or failure of the FIDS by detecting
 non-refresh of the control labels.
 - In this case, each BITE operates by using the ground/flight
 information given by the wired discrete NOSE GEAR PRESD
 which each FAC and FMGC receives directly.
 * on the ground : BITEs do not record faults.
 * in flight : BITEs record faults in flight area.
 (c) Fault detection at each BITE of the AFS
 1_  FAC, FG and FM BITEs
R  - Event trigger
 A triggering event detected by the BITE function of a
 computer corresponds to a change in state of a functional
 variable of the application software of this computer. 
R  This event triggers a fault isolation and storage process. 
R  In order not to report to the CFDIU too many transitory 
R  events which have no cockpit effect, the status change of 
R  each monitored variable must have a duration greater than a 
R  predetermined failure confirmation time. 
R 
R  Re-initialization purpose : 
R  In order to allow failure storage after CFDS phase change 
R  when the monitoring is extended (for example when changing 
R  from ground scanning to flight one, the AFS external 
R  failures must start to be monitored), the triggering 
R  variable detection within each BITE is reinitialised upon 
R  FIDS request. This allows to detect a failure already 
R  present before a phase change. 
R 
R  (Ref. Fig. 005)
 - Hierarchical configuration of the triggering events (only
 for FAC and FG)

 

R  Fault Detection Figure 005
 1EFF : 1 1 1CES  ALL  1 111 22-91-00 Page 13 Feb 01/05

 

 In order to trigger the fault isolation process, the BITE permanently scans a certain number of functional variables. These variables are hierarchically configured in order to take into account only the event with highest priority in the application software functional sense, i.e. the event whose appearance may cause other events.
R R R  2_ MCDU BITE The MCDU performs the following tests: - Processor test, - RAM test, - EPROM test, - EEPROM test, - Video monitoring, - Background monitoring. The RDY annunciator comes on (green) when the MCDU passes its long-term power- up or power-off reset test, after its BRT knob is turned to OFF. 
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：A320飛機維護手冊 AMM AUTO FLIGHT 自動飛行4(115)