SAE AIR 6181-2011 Electronic Propulsion Control Aircraft Interface Control Documents《电子驱动力控制系统 飞机接口控制文件》.pdf

《SAE AIR 6181-2011 Electronic Propulsion Control Aircraft Interface Control Documents《电子驱动力控制系统 飞机接口控制文件》.pdf》由会员分享，可在线阅读，更多相关《SAE AIR 6181-2011 Electronic Propulsion Control Aircraft Interface Control Documents《电子驱动力控制系统 飞机接口控制文件》.pdf（17页珍藏版）》请在麦多课文档分享上搜索。

1、_ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there

2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions. Copyright 2011 SAE International All rights reserved. No part of this publication m

3、ay be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-4970 (outside U

4、SA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/AIR6181 AEROSPACE INFORMATION REPORT AIR6181 Issued 2011-08 Superseding ARP4874 Electronic Pr

5、opulsion Control System/Aircraft Interface Control Documents RATIONALE In response to a committee initiative, the revision of this document is intended to elaborate on the structure and content of an Interface Control Document for the Electronic Propulsion Control System, to be used by the airframe/

6、engine manufacturers. This document is based on the previously released ARP4874. It has been revised to reflect input collected as part of the 5-Year Review process. FOREWORD Electronic Propulsion Control systems have become established for a number of applications in the commercial field. Frequentl

7、y, a given aircraft can have engines from different engine manufacturers, and also a given engine type may be used in different aircraft. Without an accepted standard this multiplicity can lead to large resource expenditure in documenting the interfaces between the engine and the aircraft. As electr

8、onic propulsion control systems become more complex, with increased data and functional integration, this problem will be aggravated in the future and significant benefit will result from an accepted standard which can apply to all applications. TABLE OF CONTENTS 1. SCOPE 2 2. REFERENCES 2 2.1 Appli

9、cable Documents 2 2.2 Acronyms/Abbreviations . 2 3. INTERFACE DEFINITION OVERVIEW 2 3.1 Purpose . 2 3.2 Interface Definition Requirements 3 4. INTERFACE CONTROL DOCUMENT (ICD) . 3 4.1 Purpose . 3 4.2 ICD Preparation 3 4.3 ICD Format and Content . 4 4.4 Electronic Transfer of Documents 4 5. NOTES 5 F

10、IGURE 1 SUGGESTED INTERFACE CONTROL DOCUMENT OUTLINE. 5 APPENDIX A SUGGESTED CONTENT FOR INTERFACE CONTROL DOCUMENT 6 SAE AIR6181 Page 2 of 17 1. SCOPE This SAE Aerospace Information Report (AIR) provides guidelines to document the functional and physical interface requirements for the electrical sy

11、stems (including an EPCS and its components) between a given propulsion system and the aircraft on which the system is installed and the functionality pertinent to each interface. The scope includes civilian aircraft powered by turbofan, turboprop, and turboshaft engines equipped with electronic eng

12、ine controls. 2. REFERENCES 2.1 Applicable Documents The following publications form a part of this document to the extent specified herein. The latest issue of SAE publications shall apply. The applicable issue of the other publications shall be the issue in effect on the date of the purchase order

13、. In the event of conflict between the text of this document and references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained. 2.1.1 EASA Publications Available from Eu

14、ropean Aviation Safety Agency, Postfach 10 12 53, D-50452 Koeln, Germany, Tel: +49-221-8999-000, www.easa.eu.int. AMC 20-1 Certification of Aircraft Propulsion Systems Equipped with Electronic Controls 2.2 Acronyms/Abbreviations DFDR Digital Flight Data Recorder EEC Electronic Engine Control EECS El

15、ectronic Engine Control System EPCS Electronic Propulsion Control System EVMS Engine Vibration Monitoring System FADEC Full Authority Digital Engine Control ICD Interface Control Document LRU Line Replaceable Unit 3. INTERFACE DEFINITION OVERVIEW 3.1 Purpose The purpose of defining interfaces betwee

16、n powerplant controls and other airplane and powerplant systems is to ensure the powerplant controls, and the airplane as a whole, perform safely, effectively, predictably and reliably. The definition of the interfaces between a powerplant control system and the related aircraft systems is the physi

17、cal and functional relationship of one system to the other (i.e., how they fit and function together). In addition, identification of these interfaces is a necessary part of certifying an aircraft propulsion system equipped with electronic controls SAE AIR6181 Page 3 of 17 3.2 Interface Definition R

18、equirements Considerations to be addressed when determining and documenting interfaces include: a. Physical Interface Characteristics: These include electrical, mechanical, optical and environmental characteristics. b. Functional Interface Characteristics: The objectives of the functions performed a

19、nd the data exchanged between the aircraft and the electronic propulsion control systems involved that allow the engine and aircraft to operate as an integrated system. 4. INTERFACE CONTROL DOCUMENT (ICD) 4.1 Purpose The purpose of the ICD is to define the physical and functional interface for the e

20、lectrical systems, including the EEC, between a given propulsion system and a given aircraft. The ICD can be initially developed a source of high level system requirements, however it is a living document that captures the actual characteristics of the system, as it is implemented. The definition of

21、 physical and functional interface characteristics should embrace both normal and abnormal operating conditions together with appropriate fault detection, accommodation, and annunciation requirements. NOTE: This is not intended to make the ICD a failure modes and effects analysis report, but instead

22、 to describe and define the system functional requirements which are related to failures of aircraft and control system components/interfaces/data, which can be used as aircraft system design requirements. The functional definition will cover all operating modes including reversionary and get-you-ho

23、me modes (if implemented). The intended audience of the ICD will include the responsible design engineering organizations at both the engine manufacturer and at the aircraft manufacturer. The completed ICD is a useful resource document for certification substantiation, certification test procedure d

24、evelopment, for engine and aircraft manufacturers maintenance training organizations, for airline maintenance engineering organizations, and for manufacturers of flight and maintenance crew training simulators. Distribution of the ICD is sometimes constrained by proprietary data concerns or by gover

25、nment export license restrictions. These factors and the intended audience should be discussed before preparation of the document to ensure it fulfills its intended purpose. 4.2 ICD Preparation The ICD is one of several sources of engineering data which define the installation of the engine control

26、system in the aircraft. The complete definition of the installation generally includes, but may not be limited to: Engine installation drawing Engine Installation Manual Typically, the aircraft manufacturer and engine manufacturer will jointly define and agree on the development and configuration ma

27、nagement plan for the ICD, as a part of the engine specification and engine integration plan negotiation process, and complete it during the subsequent design phases for the propulsion system and engine. The means for controlling the configuration of the document needs to be agreed upon at the begin

28、ning of the program, because this may affect the structure of the document (see Paragraph 4.3). The plan for development of the ICD should be designed to recognize the existence of all sources of engineering data, including the previous drawings and manual, and avoid duplication of information. SAE

29、AIR6181 Page 4 of 17 During the developmental and mature program phases, a revision to the ICD should be made in accordance with the following criteria: software update to the EEC (or the aircraft electronic systems that interface with the EEC), when functional or interface requirements are impacted

30、. This will ensure accurate documentation of changes to the aircraft/engine interfaces or features which affect the engine control system. A well-maintained/accurate ICD is also an essential tool to avoid interface issues in mature programs undergoing retrofit upgrades, by providing tracking status

31、of interface changes which have occurred to the engine or aircraft. Where specific chapters of the ICD contain information / requirements concerning other manufacturers / suppliers to the Aircraft (i.e: Avionics, Landing Gear, Throttle Quadrant, etc), their information should be included within the

32、chapters with which they are involved. 4.3 ICD Format and Content A example of an outline structure for the ICD is shown in Figure 1. The specific section placement order and numbers shown for each topic are intended to be for reference only. However, specific sections, such as paragraphs discussing

33、 system description, functionality and functional interface requirements, should be expanded as necessary for a given application. In some applications, it may be of use to configure each section as a stand-alone item. For projects which require large documents, this approach allows the ICD to be di

34、vided into smaller, more manageable sections which may be configured and released separately as the design progresses. In this arrangement, each section would contain a detailed change history, table of contents, signature sheets, etc. A Master Summary document could be created to identify the lates

35、t version of each section. For configuration control purposes, it is suggested that the document defines the application, physical interface configuration and software version. The document will provide a description of the overall system, providing information and requirements on all aircraft and p

36、ropulsion system LRUs to which the electronic propulsion control system components interface. The detailed definition will cover the functional requirements and both the physical and functional characteristics of all data, signals and power associated with the aircraft to propulsion system interface

37、 and vice-versa. The use of data tables and high level flow / logic diagrams may be used to describe the functional requirements. Due to Export Control constraints of detailed logic diagrams which are used to create executable software code, it may be suggested not to include these logic diagrams in

38、 the ICD. It is highly suggested that the ICD documents the use of aircraft data in engine control functions and engine data in aircraft control functions. The data supplier should be made aware that their transmitted data is being used in a specific function and that no changes to the data format o

39、r characteristics should occur without proper and complete impact analysis by the receiver system. Appendix “A” presents additional, more specific details for suggested ICD content. Note that the suggested format incorporates all discussion of functional interface requirements in Section 8. Alternat

40、ively, individual functional requirements may be included in separate paragraphs, e.g., Section 8.2. Aircraft Provided Data Management, Section 8.5 Thrust/Power Management, etc. Aspects such as fault detection, accommodation, annunciation and dispatch criteria for each function may be included as su

41、bsections within the paragraph that discusses that function. 4.4 Electronic Transfer of Documents In preparing the plan for development of the ICD, consideration should be given to permit transfer of the document electronically between the engine manufacturer and the aircraft manufacturer. SAE AIR61

42、81 Page 5 of 17 FIGURE 1 - SUGGESTED INTERFACE CONTROL DOCUMENT OUTLINE 5. NOTES A change bar (|) located in the left margin is for the convenience of the user in locating areas where technical revisions, not editorial changes, have been made to the previous issue of this document. An (R) symbol to

43、the left of the document title indicates a complete revision of the document, including technical revisions. Change bars and (R) are not used in original publications, nor in documents that contain only editorial changes. PREPARED BY SAE COMMITTEE E-36, ELECTRONIC ENGINE CONTROLS SAE AIR6181 Page 6

44、of 17 APPENDIX A - SUGGESTED CONTENT FOR INTERFACE CONTROL DOCUMENT A.1 TABLE OF CONTENTS The table of contents should include items such as: a. Text b. List of figures c. List of tables d. Appendices A.2 REVISION HISTORY The revision history should allow document changes to be easily identified and

45、 be traceable to specific change requests. In addition, the revision history will provide the ability to identify all active pages of the document. A.3 SCOPE For each revision of the ICD, the scope section should: a. Define the airframe-engine application b. Define hardware configuration and softwar

46、e version for the electronic propulsion control system and interfacing aircraft systems (i.e: Avionics, etc), where it has impact on functionality. c. Provide the corresponding Power Management Deck reference d. Include a “CAVEATS” section which lists deviations or discrepancies to requirements exis

47、ting for a given hardware/software configuration. The Caveats may be separated into categories pertaining to Propulsion System software, Aircraft component (Avionics, etc) software or other interface items. A.4 REFERENCE DOCUMENTS The reference section of the ICD should include references, such as:

48、a. Applicable government regulations b. Applicable industry standards c. Aircraft manufacturer specifications d. Engine and/or component specifications e. Engine and/or component installation drawings Where appropriate, a precedence statement may be included for resolution of conflicting requirement

49、s. Agreed-upon deviations from reference documents may also be listed. SAE AIR6181 Page 7 of 17 A.5 SUPPLEMENTAL INFORMATION Supplemental information may include: A.5.1 Definitions This section will explain terms used in the ICD, including ARINC Format and other definitions which will help make the document fully comprehensive. A.5.2 Acronyms, Abbreviations This section provides explanation of the acronyms and abbreviations us