600 Series ARINC Specifications and Reports define enabling technologies that provide a design foundation for equipment specified per the ARINC 700 Series of digital avionics systems. Among the topics covered by Specifications are data link protocols.
The purpose of this document is to provide an introduction and overview of the ARINC 628 series o...f Specifications. ARINC 628 defines equipment and installation standards for cabin equipment, which is generally defined as communication and entertainment equipment designed for passenger use. Part 0 provides the concepts and overview of ARINC 628 and descriptions of each individual part. Appendix B is written in briefing chart format to facilitate the understanding of high-level objectives. Supplement 4 represents a summary of recent changes to Parts 1 through 9 of ARINC Specification 628.
The purpose of ARNC 633 is to specify the format and exchange of Aeronautical Operational Control... (AOC) communications. Examples of ARINC 633 AOC Structures/Messages include: Flight Plan, Load Planning (i.e., Weight and Balance and Cargo Planning Load Sheets), NOTAMs, Airport and Route Weather data, Minimum Equipment Lists (MEL) messages, etc. The standardization of AOC messages enable the development of applications shared by numerous airlines on different aircraft types. Benefits include improved dispatchability and reduce operator cost.
This document provides airlines, airframe manufacturers, aircraft equipment suppliers, and others... with information that is specific to data, software, and ground tools used in aviation configuration and data management.
This report defines the requirements and recommended practices for production testing of aircraft... passenger seats and seat groups. Production testing is performed at the seat manufacturers' facilities prior to the shipment of the seats to the airframe manufacturers, Maintenance, Repair, and Overhaul (MRO), or airlines/operators for installation in the aircraft. Using this guidance, rework is minimized and schedules remain minimally affected.
This document provides an overview of the entire set of documents collectively referred to as ARI...NC 653. As this set of documents evolves, Supplements to Part 0 will be made more consistent with Parts 1 through 5 in conjunction with the technical changes expected to be made in the evolution of ARINC 653. A summary of the ARINC 653 documents follows: Part 0 - Overview of ARINC 653, Part 1 - Required Services, Part 2 - Extended Services, Part 3 - Conformity Test Specification, Part 4 - Subset Services, and Part 5 - Core Software Required Capabilities. Supplement 1 reflects the introduction of multicore processor support in Parts 1 and 2.
This standard defines a general-purpose Application/Executive (APEX) software interface between t...he Operating System of an avionics computer and the application software. The interface requirements between the application software and operating system services are defined in a manner that enables the application software to control the scheduling, communication, and status of internal processing elements. Supplement 5 adds multicore processor service capabilities.
As avionics software continues to evolve, so does ARINC Specification 653. ARINC 653 Part 2 speci...fies extensions (i.e., optional services) to the required Application Program Interfaces (APIs) described in ARINC 653 Part 1. Supplement 4 adds optional multicore services capabilities.
ARINC 653, Part 3A is the Compliance Test Specification for ARINC 653 Required Services presently... defined in ARINC 653 Part 1. The document specifies a set of stimuli and the expected responses. Future work on the ARINC 653 document set includes an effort to define Operating System services for multi-core processor environments. The Compliance Test Specification is expected to be updated in step with ARINC 653, Part 1.
ARINC 653, Part 3B is the Compliance Test Specification for ARINC 653 Extended Services presently... defined in ARINC 653 Part 2. The document specifies a set of stimuli and the expected responses. Future work on the ARINC 653 document set includes an effort to define Operating System services for multi-core processor environments. The Compliance Test Specification is expected to be updated in step with ARINC 653, Part 2.
Part 5 defines additional ARINC 653 core software capabilities to ease integration on a variety o...f Integrated Modular Avionics (IMA) hardware platforms by allowing platform suppliers to extend and customize it for use with their unique hardware platform. Supplement 1 expands the guidance provided on resource profiling and execution profiling pertinent to the use of mulicore processors in avionics.
ARINC 661 defines logical interfaces to Cockpit Display Systems (CDS) used in all types of aircra...ft installations. The CDS provides graphical and interactive services to user applications within the flight deck environment. When combined with data from user applications, it displays graphical images to the flight deck crew. The document emphasizes the need for independence between aircraft systems and the CDS. This document defines the interface between the avionics equipment and display system graphics generators. This document does not specify the "look and feel" of any graphical information, and as such does not address human factors issues. These are defined by the airline flight operations community.
The purpose of this document is to establish guidelines that should be observed during initial de...sign, production, and maintenance of aircraft components, and to present short-term and long-term strategies to minimize the costs and impacts associated with decreasing availability of components.
The purpose of this document is to provide an overview of data networking standards recommended f...or use in commercial aircraft installations. These standards provide a means to adapt commercially defined networking standards to an aircraft environment. It refers to devices such as bridges, switches, routers and hubs and their use in an aircraft environment. This equipment, when installed in a network topology, can optimize data transfer and overall avionics performance.
This specification provides Ethernet physical parameters and data link layer specifications for u...se in a commercial aircraft environment. This specification provides general and specific guidelines for the use of IEEE 802.3 compliant Ethernet, 2000 edition. Physical layer and Medium Access Control (MAC) sub-layers are expected to comply with the Open System Interconnection (OSI) Reference Model to enable maximal utilization of off-the-shelf components, both hardware and software, for aviation use. The Ethernet Physical layer specification defines the electrical and optical parameters for the 10BASE-T, 100BASE-TX, and 100BASE-FX Ethernet implementations. This specification references ARINC Specification 600: Air Transport Avionics Equipment Interfaces for definition of copper-based implementations of the Ethernet Physical layer.
This document defines the aircraft industry's standards for Loadable Software Parts (LSPs) and Me...dia Set Parts (MSPs). It describes the common principles and rules to be applied to any part of a data load system to ensure compatibility and inter-operability of software parts. It includes part numbering, content, labeling, and formatting of an LSP, and a Media Set containing LSPs. Supplement 5 refers to a companion document, ARINC Report 645: Common Terminology and Functions for Software Distribution and Loading.
This document describes the technical requirements, architectural options, and recommended interf...ace standards to support an Autonomous Distress Tracking (ADT) System intended to meet global regulatory requirements for locating aircraft in distress situations and after an accident. This document is prepared in response to International Civil Aviation Organization (ICAO) and individual Civil Aviation Authorities (CAAs) initiatives.
AEEC, AMC, and FSEMC are aviation industry activities organized by ARINC Industry Activities, an industry program of SAE Industry Technologies Consortia (SAE ITC)®, to establish consensus technical standards, known globally as ARINC Standards, and develop shared technical solutions that no one organization could accomplish independently.