《ARINC-655-1999.pdf》由会员分享，可在线阅读，更多相关《ARINC-655-1999.pdf（65页珍藏版）》请在三一文库上搜索。
1、A REMOTE DATA CONCENTRATOR (RDC) GENERIC DESCRIPTION ARINC REPORT 655 PUBLISHED: APRIL 5, 1999 AN AA DOCUMENT Prepared by AIRLINES ELECTRONIC ENGINEERING COMMITTEE Published by AERONAUTICAL RADIO, INC. 2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401 This document is based on material submitted by various
2、participants during the drafting process. Neither AEEC nor ARINC has made any determination whether these materials could be subject to valid claims of patent, copyright or other proprietary rights by third parties, and no representation or warranty, expressed or implied is made in this regard. Any
3、use of or reliance on this document shall constitute an acceptance thereof “as is” and be subject to this disclaimer. Copyright 1999 by AERONAUTICAL RADIO, INC. 2551 Riva Road Annapolis, Maryland 21401-7465 USA ARINC REPORT 655 REMOTE DATA CONCENTRATOR (RDC) GENERIC DESCRIPTION Published: April 5, 1
4、999 Prepared by the Airlines Electronic Engineering Committee Report 655Adopted by the Airlines Electronic Engineering Committee:February 26, 1999 Report 655Adopted by the Industry: April 2, 1999 FOREWORD Activities of AERONAUTICAL RADIO, INC. (ARINC) and the Purpose of ARINC Reports and Specificati
5、ons Aeronautical Radio, Inc. is a corporation in which the United States scheduled airlines are the principal stockholders. Other stockholders include a variety of other air transport companies, aircraft manufacturers and non-U.S. airlines. Activities of ARINC include the operation of an extensive s
6、ystem of domestic and overseas aeronautical land radio stations, the fulfillment of systems requirements to accomplish ground and airborne compatibility, the allocation and assignment of frequencies to meet those needs, the coordination incident to standard airborne compatibility, the allocation and
7、 assignment of frequencies to meet those needs, the coordination incident to standard airborne communications and electronics systems and the exchange of technical information. ARINC sponsors the Airlines Electronic Engineering Committee (AEEC), composed of airline technical personnel. The AEEC form
8、ulates standards for electronic equipment and systems for the airlines. The establishment of Equipment Characteristics is a principal function of this Committee. It is desirable to reference certain general ARINC Specifications or Report which are applicable to more than one type of equipment. These
9、 general Specifications and Reports may be considered as supplementary to the Equipment Characteristics in which they are referenced. They are intended to set forth the desires of the airlines pertaining to components and general design, construction and test criteria, in order to insure satisfactor
10、y operation and the necessary interchangeability in airline service. The release of a Specification or Equipment Characteristics should not be construed to obligate ARINC or any airline insofar as the purchase of any components or equipment is concerned. An ARINC Report ( Specification or Characteri
11、stic) has a twofold purpose, which is: (1)To indicate to the prospective manufacturers of airline electronic equipment the considered opinion of the airline technical people, coordinated on an industry basis, concerning requisites of new equipment, and (2)To channel new equipment designs in a direct
12、ion which can result in the maximum possible standardization of those physical and electrical characteristics which influence interchangeability of equipment without seriously hampering engineering initiative. ii ARINC REPORT 655 TABLE OF CONTENTS ITEMSUBJECTPAGE 1.0INTRODUCTION1 1.1Purpose of this
13、Document1 1.2Generic Description1 1.3Interoperability1 1.4Relationship to ARINC 6511 1.5Reference Documents1 1.6Regulatory Approval2 2.0ARCHITECTURAL CONSIDERATIONS3 2.1Introduction3 2.2Equipment Interoperability3 2.3Architecture Considerations3 2.3.1Partitioning3 2.3.2Unit (RDC) Level3 2.3.3Cabinet
14、 Level3 2.3.4 System Level4 2.4Architecture Tradeoffs4 2.4.1Interface Capability4 2.4.2Synchronous Versus Asynchronous RDCs4 2.4.3RDC Functioning4 2.4.4Reconfiguration4 2.5Hardware Architecture4 2.5.1RDC Interfacing4 2.5.2Gateway Implementation4 2.5.3Data Loader Interface5 2.5.4Built-In Test5 2.5.5P
15、ower Input5 2.6Software Architecture5 3.0FUNCTIONAL CHARACTERISTICS9 3.1Introduction9 3.1.1General9 3.1.2Aircraft/RDC Configuration9 3.1.3Data Latency9 3.2Power Initialization and Interruption Handling9 3.3General Capabilities9 3.3.1ARINC 629 Data Bus Interface9 3.3.2ARINC 429 Interface9 3.3.3Test a
16、nd Maintenance (TM) Bus9 3.3.4Analog Signals9 3.3.5Digital Signals9 3.3.6Discrete Signals9 3.4Initialization9 4.0PHYSICAL ATTRIBUTES10 4.1Introduction10 4.2Environmental Conditions10 4.3Cooling10 4.4Type, Size and Weight10 4.5Connectors10 5.0ELECTRICAL INTERFACE11 5.1Introduction11 5.2Electrical Bon
17、ding and Grounding11 5.3Power11 5.4RDC Internal Discretes11 5.5Test and Maintenance Bus11 5.6Other Interfaces11 5.6.1Analog Inputs11 5.6.1.1Standard Fixed Frequency Analog Inputs11 5.6.1.2Low-Level Voltage Direct Current Inputs11 5.6.1.3Standard Low-Level Current Source Analog Inputs11 5.6.1.4Standa
18、rd Variable Frequency Analog Inputs12 iii -,-,- ARINC REPORT 655 TABLE OF CONTENTS ITEMSUBJECTPAGE 5.6.1.5Specific Analog Inputs12 5.6.1.6Analog Outputs12 5.6.1.6.1Low-Level Voltage Direct Current Outputs12 5.6.1.6.2Standard Monitored Current Analog Outputs12 5.6.1.6.3Application Specific Analog Out
19、puts12 5.6.2Digital Signals12 5.6.2.1ARINC 429, Mark 33 Digital Information Transfer System12 5.6.2.2ARINC 629, Multi-Transmitter Data Bus12 5.6.2.3Bus Interfaces12 5.6.3Discrete Signals12 5.6.3.1Discrete Input - Open/Ground12 5.6.3.2Discrete Input - Open/28V12 5.6.3.3Discrete Output - Open/Ground13
20、 5.6.3.3.1Low-Power Outputs13 5.6.3.3.2Medium-Power Outputs13 5.6.3.3.3High-Power Outputs13 5.6.3.4Discrete Output - Open/28 Volt13 5.6.3.4.1Low-Power Outputs13 5.6.3.4.2Medium-Power Outputs13 5.6.3.4.3High-Power Outputs13 5.7Standard Interwiring13 6.0DATA BUS AND I/O FUNCTIONAL INTERFACES16 6.1ARIN
21、C 629 Data Bus Interfaces16 6.2ARINC 429 Data Bus Interfaces16 6.3Discrete Input Resources Interface16 6.4Discrete Output Resources Interface16 6.5Analog Input Resources Interface16 6.6Analog Output Resources Interface16 7.0SUPPORTABILITY17 7.1Reliability17 7.2Maintainability17 7.3Testability17 7.3.
22、1Built-In Test Equipment (BITE)17 7.3.1.1Built-In Test Functions17 7.3.1.2Built-In Test Philosophy17 7.3.1.3BITE Interfaces17 7.3.2Health Monitoring17 7.3.3ATE Testing17 7.3.4Test and Maintenance Bus17 8.0SOFTWARE18 8.1Introduction18 8.2Software Development18 8.3Software Programming18 ATTACHMENTS 1R
23、DC - Interface Block Diagram19 2RDC - Configuration Examples20 APPENDICES ARDC Connector Definition29 BGlossary59 iv -,-,- ARINC REPORT 655 - Page 1 1.0 INTRODUCTION 1.1 Purpose of this Document This document provides guidance for the design and implementation of a Remote Data Concentrator (RDC) in
24、aircraft installations. It represents the consensus of airlines, airframe manufacturers and avionics suppliers involved in the preparation of this document. It is intended to provide a basis for manufacturers requirement specifications. This document describes specific electrical and mechanical inte
25、rfaces to a RDC. This document is applicable to a wide range of avionics architectures ranging from traditional federated architectures to highly integrated solutions. This document makes several references to ARINC Report 651, “Design Guidance for Integrated Modular Avionics”. 1.2 Generic Descripti
26、on The Remote Data Concentrator (RDC) is a component that translates electronic signals from various sources on the aircraft into standardized digital signals usable by avionics computing resources. It also converts data from the computing resources into formats desired by the various effectors and
27、actuators. It can be used as means to reduce and minimize long signal runs, thus reducing aircraft wiring. This document is intended as a top-level design guide for RDCs The document is conceptual in nature and covers broad subjects of operational objectives, fault tolerance, hardware components, so
28、ftware design and certification issues. In covering all these issues, the document attempts to be as inclusive as possible, while being general enough to be applicable to new and developing technologies. It includes design philosophy and recommended practices concerning the design of RDCs, and as su
29、ch, is expected to establish a starting point for the actual implementation by avionics manufacturers. Equipment manufacturers should note that this document encourages them to produce high-performance, maintenance-free, equipment rather than equipment of minimum weight and size. They are at liberty
30、 to accomplish this objective using the means and techniques they consider to be most appropriate. The airline customers are interested primarily in the end result, rather the means employed to achieve it. 1.3 Interoperability The primary purpose of this document is to specify the signal types and i
31、nterwiring characteristics necessary to ensure interoperability of any manufacturers RDC. Interoperability provides maximum flexibility for the airframe manufacturer to specify the RDC needed to satisfy his particular airframe installation. Interoperability assures the airline user that common signa
32、l types and common wiring will be used throughout the airplane. This document defines a set of interfaces interfaces to a family of RDCs. 1.4 Relationship to ARINC 651 This document is written in support of the guidelines set forth in ARINC Report 651, “Design Guidance for Integrated Modular Avionic
33、s”. In concept, the RDC is a remote Input/Output (I/O) module with the specific task of concentrating data from many sources. There are common electrical and system interface characteristics between the RDC and a generic I/O module. This document is intended to be used in conjunction with ARINC Repo
34、rt 651 and other documents prepared by the AEEC on this subject. 1.5 Reference Documents The latest revision of the following documents are pertinent to the design and development of a Remote Data Concentrator. This document does not preclude the use of other industry standards. ARINC Specification
35、429 - Mark 33 Digital Information Transfer System (DITS) ARINC Specification 600 Air Transport Avionics Equipment Interfaces ARINC Report 607 - Design Guidance for Avionic Equipment ARINC Specification 608A - Design Guidance for Avionics Test Equipment ARINC Report 609 - Design Guidance for Aircraft
36、 Electrical Power Systems ARINC Report 615 - Airborne Computer High Speed Data Loader ARINC Report 624 - Design Guidance for Onboard Maintenance System ARINC Specification 629 - Multi-Transmitter Data Bus ARINC Specification 650 - Integrated Modular Avionics Packaging and Interfaces ARINC Report 651
37、 - Design Guidance for Integrated Modular Avionics ARINC Report 652 - Guidance for Avionics Software Management ARINC Specification 653 - Avionics Application Software Standard Interface ARINC Report 654 - Environmental Design Guidelines for Integrated Modular Avionics IEEE Standard 1149.5 - Standar
38、d Module Test and Maintenance Bus (MTM) Bus Protocol RTCA DO-160/EUROCAE ED-14 - Environmental Conditions and Test Procedures for Airborne Equipment RTCA DO-178/EUROCAE ED-12 - Software Consider- ations in Airborne Systems and Equipment Certification SAE ARP 4754 - Certification Considerations for H
39、ighly- Integrated or Complex Aircraft Systems SAE ARP 4761 - Safety Assessment Process MIL-HDBK-217 - Reliability Prediction of Electronic Equipment MIL-STD-1629A - Failure Mode Effect and Criticality Analysis (FMECA) ARINC REPORT 655 - Page 2 1.0 INTRODUCTION (contd) MIL-STD-1344 - Test Methods for
40、 Electrical Connectors MIL-W-22759 - Wire, Electric, Fluoropolymer - Insulated, Copper or Copper Alloy MIL-W-81381 - Wire, Electric, Fluoropolymer - Insulated, Copper or Copper Alloy MIL-C-17 - Cables, Radio Frequency, Flexible and Semirigid, General Specification for 1.6 Regulatory Approval The RDC
41、 should meet all applicable Federal Aviation Administration (FAA), European Joint Aviation Authority (JAA), Federal Communication Commission (FCC), and other regulations. This document does not and cannot set forth the specific requirements that equipment must meet to assure approval. Such informati
42、on must be obtained from the respective regulatory agencies. -,-,- ARINC REPORT 655 - Page 3 2.0 ARCHITECTURAL CONSIDERATIONS 2.1 Introduction The Remote Data Concentrator (RDC) should provide the applicable avionics interface functions defined in this standard. It is an airline goal that interopera
43、bility be achieved among RDCs developed to this standard. It is the responsibility of the aircraft manufacturer to define the specific RDC configuration, using the common interfaces defined in this document. The RDC should provide the functions and capabilities necessary to interface defined aircraf
44、t signals to the computer processing resources on the airplane. The RDC should have the ability to interface with a combination of digital data buses, and analog and discrete signals used on the aircraft. The RDC may provide interfaces to a single type of signal or to some optimum mix of signals wit
45、h some software programmable or reconfigurable selection of signal interfaces. COMMENTARY It is the aim to minimize the number of specific I/O types on the airplane. 2.2 Equipment Interoperability The RDC should be designed independent of the avionics functions on the airplane. It should be designed
46、 for application to many foreseeable avionics equipment installations. Thus, system integrators are encouraged to be aware of the overall I/O requirements of the other systems, e.g., fuel, landing gear, flight controls. COMMENTARY Ideally, airlines would like interchangeability of avionics component
47、s among different airframe models. When interchangeability is achieved, it is an effective means to reduce avionics cost. However, interchangeability carries the burden of achieving identical form, fit, function and interface definition among all avionics suppliers. Some equipment such as VHF radios
48、 and primary navigation sensors have achieved this status. One of the enabling aspects for full interchangeability is the ability for the equipment to be defined independent of the specific airframe installation. A goal of this document is to define a set of functions and interfaces that an RDC shou
49、ld possess in order to be functionally interchangeable with other such units. The RDC should be characterized by similar behavior and be compatible with mechanical and electrical interfaces. It is of prime importance that the RDC designer comply with the form factor, mounting provisions, interwiring and input/output signal definitions specified in this document. In addressing avionics retrofit considerations, the equipment manufacturer should be aware of t