R 1EFF : 151-199, 201-210, 1 31-36-00Page 73 1 1 Config-2 May 01/05 1 1 1CES 1R A321 Aircraft
R +-------------------------------------------------------------------------+ R | No | CFMI ENG Type | Program Discrete|| IAE ENG Type | Program Discrete| R | | | 4 | 5 | 6 || | 4 | 5 | 6 | R |----|---------------|-----|-----|-----||---------------|-----|-----|-----|
R | 1 | SPARE R | | R | 2 | SPARE R | | R | 3 | SPARE R | | R | 4 | SPARE R | | R | 5 | CFM 56-5-B1 R | | R | 6 | CFM 56-5-B2 R | | R | 7 | CFM 56-5-B3 R | | R | 8 | SPARE | 0 | 0 | 0 || SPARE | | | || | 1 | 0 | 0 || SPARE | | | || | 0 | 1 | 0 || SPARE | | | || | 1 | 1 | 0 || SPARE | | | || | 0 | 0 | 1 || V 2530-A5 | | | || | 1 | 0 | 1 || V 2533-A5 | | | || | 0 | 1 | 1 || SPARE | | | || | 1 | 1 | 1 || SPARE | 0 | 0 | 0 | | | | | | 1 | 0 | 0 | | | | | | 0 | 1 | 0 | | | | | | 1 | 1 | 0 | | | | | | 0 | 0 | 1 | | | | | | 1 | 0 | 1 | | | | | | 0 | 1 | 1 | | | | | | 1 | 1 | 1 |
R +-------------------------------------------------------------------------+
R (d) Identification of EVMU version R For A321 and A319 with CFMI engine, the DMU always apply the R definitions for the advanced EVMU. R For A320 with CFMI engine the DMU distinguish between two R different EVMU standards. When EVMU label 377 (3D.1.377.00) is R received from the DMU check if one of the following labels is R transmitted by the EVMU: R R Label 3D.1.230.00 R 3D.1.230.01 R 3D.1.230.10 R 3D.1.230.11 R R Label 3D.1.227.00 R 3D.1.227.11 R R Monitoring the above mentioned labels the SSM status is of no R importance. R When the DMU has detected one of these labels it means that an R advanced EVMU is installed and the DMU perform the advanced R engine vibration monitoring definition. If the DMU does not R receive anyone of these labels, it perform the report logics. R In case that the DMU recognize an EVMU failure (e.g. no EVMU R data) during the identification phase, the DMU works according
R 1EFF : 151-199, 201-210, 1 31-36-00Page 74 1 1 Config-2 May 01/05 1 1 1CES 1
R the programming from the last flight. If there is no programming
R from the last flight the DMU works with the advanced EVMU
R definition.
R
R (2) History Buffer
R (a) 20 Seconds History Buffer (For Print Reports)
R The history buffer for print reports is for 200 parameters with
R an average sampling rate of 4 per second. This buffer is intended
R to supply data for incorporation into print reports.
R
R (b) DAR History Buffer
R The DAR history buffer is programmable from 0 to 120 seconds and
R located in the airline specific module. To enable pre-event data
R recording on the DAR in case the event causes the DAR start a 120
R second history buffer. History buffer sizes are selectable in 4
R second increments.
R
R (c) Print Report Buffer
R A non-volatile print report buffer for 10 reports is provided.
R Each report is on the average 40 lines by 40 characters including
R header lines.
R
R (d) Short Time Buffer for Reports Generated by Manual Request
R For those reports which are generated by a manual request via the
R MCDU for printing or linking via ACARS a report buffer for 1
R report is provided. The length is 128 lines by 40 characters.
R
R (3) Parameter Label Call-Up
R Each parameter (ARINC 429 data word) transmitted on one of the
R connected data buses is selectable, you use: EQ, source system,
R label, SDI and number of data bits for display on the MCDU. The
R number of data bits can be omitted. The displayed parameters are
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：A320飞机维护手册 AMM 指示/记录系统 3(70)
