Refine Your Search

Topic

Search Results

Standard

STANDARD DATA INTERFACE FOR GALLEY INSERT (GAIN) EQUIPMENT PART 1 CAN COMMUNICATIONS

2021-09-10
CURRENT
ARINC812AP1-2
The purpose of this specification is to define the general Galley Insert (GAIN)standardization philosophy, provide comprehensive equipment interfaces, and disseminate the most current industry guidance. Part 1 covers the Controller Area Network (CAN) data interface attachments, envelopes, and data content to be considered between all galley equipment using a Galley Data Bus as described within this specification. This document is intended as the successor and replacement for ARINC Specification 812. This document contains significant improvements to CAN data interfaces.
Standard

LOGICAL SOFTWARE PART PACKAGING FOR TRANSPORT

2020-11-16
CURRENT
ARINC641-1
The purpose of this standard is to provide a method for packaging aircraft software parts for distribution using contemporary media or by electronic distribution. This project intends to standardize and provide guidance for the storage of floppy based software, currently packaged in media set parts. This standard format can be then stored or distributed on a single physical media member (CD-ROM), or by electronic crate. The obsolescence of floppy disks drive an urgent need for this guidance.
Standard

COCKPIT DISPLAY SYSTEM INTERFACES TO USER SYSTEMS PART 2 USER INTERFACE MARKUP LANGUAGE (UIML)

2020-08-07
CURRENT
ARINC661P2
This document defines the User Interface Markup Language (UIML) which allows developers to specify the interface, look, and behavior of any Graphical User Interface (GUI). The GUI consists of several components, from the simplest, called primitive components (such as rectangle, text, image, group), to more complex components built by the aggregation of several primitive components and by providing relational specific logic. Also defined is the execution model, which provides the rules to interpret the language so that the graphical user interface has a standardized and consistent behavior defined for any platform.
Standard

AIRCRAFT DATA INTERFACE FUNCTION (ADIF)

2020-07-21
CURRENT
ARINC834-8
This document defines an Aircraft Data Interface Function (ADIF) developed for aircraft installations that incorporate network components based on commercially available technologies. This document defines a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. A common set of services that may be used to access specific avionics parameters are described. The ADIF may be implemented as a generic network service, or it may be implemented as a dedicated service within an ARINC 759 Aircraft Interface Devices (AID) such as those used with an Electronic Flight Bag (EFB). Supplement 8 includes improvements in the Aviation Data Broadcast Protocol (ADBP), adds support for the Media Independent Aircraft Messaging (MIAM) protocol, and contains data security enhancements. It also includes notification and deprecation of the Generic Aircraft Parameter Service (GAPS) protocol that will be deleted in a future supplement.
Standard

CABIN EQUIPMENT INTERFACES PART 2 PHYSICAL LAYER - IN-SEAT PROTOCOL

2020-06-30
CURRENT
ARINC485P2-5
ARINC Specification 485, Part 2 specifies the ARINC 485-control protocol used by the LRUs described in ARINC Specification 628 Part 2. This document defines a multi-drop bus. The point-to-point configuration is also supported. The point-to-point bus is treated simply as a multi-drop bus with only one drop. There is one master LRU and one or more slave LRUs present on the bus. However; multiple buses may be connected in parallel, where each parallel bus operates independently from each other.
Standard

MEDIA INDEPENDENT SECURE OFFBOARD NETWORK

2020-06-19
CURRENT
ARINC848
ARINC Specification 848 is a functional standard based on a protocol specification profile for a secured network interface. The purpose is to define a common method of initiating a mutually authenticated tunnel between an aircraft service and its Enterprise service. ARINC Specification 848 defines a standard implementation for securing the communications between an onboard Local Area Network (LAN) and an Enterprise LAN on the ground. Various aircraft network architectures and various air to ground communication channels (aka media) are accommodated in this document. For example, L-band Satellite Communication (Satcom), Ku/Ka-band Satcom, Gatelink Cellular, and Gatelink are considered.
Standard

DATA LABELS

2019-01-21
CURRENT
ARINC429P1-19DL
This product is a Zip file that contains a subset of material in ARINC Specification 429, Part 1. Specifically: Attachment 1-1, Label Codes, in an Excel file; Attachment 1-2, Equipment Codes, in a Word file; Attachment 2A, Data Standards - BCD Data, in a Word file; and Attachment 2B, Data Standards - BNR Data, in a Word file.
Standard

GENERAL STANDARDIZATION OF CAN (CONTROLLER AREA NETWORK) BUS PROTOCOL FOR AIRBORNE USE

2018-09-25
CURRENT
ARINC825-4
This document defines a Controller Area Network (CAN) interface for current and future commercial aircraft applications. The latest version, Supplement 4, expands the document to include CAN Flexible Data rate also known as CAN FD. CAN FD has the potential to provide 4 Mbps of data transfer. Supplement 4 also introduces four new appendices on the topics of: ARINC 825 Compliance, Configuration of Bit Timing, Management Information Base (MIB) Counters, and CAN Bus Security Considerations.
Standard

ACARS PROTOCOLS FOR AVIONIC END SYSTEMS

2017-11-29
CURRENT
ARINC619-5
The purpose of this document is to delineate, in an organized fashion, the protocols used by Aircraft Communication Addressing and Reporting System (ACARS) Management Units (MU) defined in ARINC Characteristic 724B and Communications Management Unit (CMU) defined in ARINC Characteristic 758, in their interactions with other onboard avionics equipment. The purpose of this document is to delineate, in an organized fashion, the protocols used by Aircraft Communication Addressing and Reporting System (ACARS) Management Units (MU) defined in ARINC Characteristic 724B and Communications Management Unit (CMU) defined in ARINC Characteristic 758, in their interactions with other onboard avionics equipment.
Standard

USERS GUIDE FOR ARINC 616 AVIONICS SUBSET OF ATLAS

2017-11-29
CURRENT
ARINC605
This guide has been written as an applications manual for writing avionics test specifications that conform to ARINC Specification 616. It provides advice for converting ATLAS test specifications into ATLAS test programs and implementing them on Automatic Test Equipment (ATE).This guide has been written as an applications manual for writing avionics test specifications that conform to ARINC Specification 616. It provides advice for converting ATLAS test specifications into ATLAS test programs and implementing them on Automatic Test Equipment (ATE).
Standard

AVIONICS REFRIGERATION COOLING SYSTEM

2017-10-27
CURRENT
ARINC728
This standard provides standards for the in accordance with which aircraft operators and manufacturers can order avionics refrigeration units and can design installations for an ARCS.
Standard

ATS DATA LINK APPLICATIONS OVER ACARS AIR-GROUND NETWORK

2017-08-23
CURRENT
ARINC622-5
This standard specifies ATS applications that enhance the functionality of the ACARS system. It provides design guidance to developers in order to ensure interoperability between the implementations of these applications.
Standard

AIRCRAFT DATA INTERFACE FUNCTION (ADIF)

2017-08-09
CURRENT
ARINC834-7
This document defines an Aircraft Data Interface Function (ADIF) developed for aircraft installations that incorporate network components that are based on commercially available technologies. This document defines a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. The goal is to provide a common set of services that may be used to access specific avionics parameters. The ADIF may be implemented as a generic network service, or it may be implemented as a dedicated service within an ARINC 759 Aircraft Interface Devices (AID) such as those used with an Electronic Flight Bag (EFB).
Standard

DATA LOADING SPECIFICATIONS FOR AIRCRAFT COMPONENTS

2017-07-06
CURRENT
ARINC849
This document defines information required to load data into aircraft components while not installed aboard an aircraft. The objective is to address all levels of data loading processes as related to component maintenance and repair within a shop environment.
Standard

EMBEDDED INTERCHANGE FORMAT FOR AIRPORT MAPPING DATABASE

2016-08-31
CURRENT
ARINC816-3
This document defines an open encoding format for airport databases which are loaded in airborne systems. This format, when designed and implemented, will enable a quick, economic, and efficient use of AMDB. However, since industry does not require applications to be standardized, data interpretation is not addressed in this document.
Standard

GUIDANCE FOR TARGET HARDWARE DESIGN PART 2 AIRBORNE HIGH SPEED DATA LOADER (ARINC REPORT 615-4)

2016-07-29
CURRENT
ARINC844P2
ARINC Specification 844, prepared in two parts, defines the requirements of a Target Data Loader (TDL) from the target hardware point of view. Both parts are based on two data loading standards: Part 1 clarifies ARINC Report 615-3: Airborne Computer High Speed Data Loader, Part 2 clarifies ARINC Report 615-4: Airborne Computer High Speed Data Loader. ARINC Report 615 was originally written from the data loader point of view. It is important that a target designer have a general understanding of the operation of a data loader in its modern implementation. Equally important is the need for data loader manufacturers to understand the standardized implementation requirements and supported subset of ARINC 615 features that are defined in ARINC 844, Parts 1 and 2. Therefore, ARINC Specification 844 is expected to provide value to both data loader and target implementers.
Standard

MEDIA INDEPENDENT AIRCRAFT MESSAGING (MIAM)

2016-07-20
CURRENT
ARINC841-3
The purpose of this document is to provide an industry standard for Media Independent Aircraft Messaging (MIAM) which permits the exchange of a large volume of data over Aircraft Communications Addressing and Reporting System (ACARS) subnetworks or broadband Internet Protocol (IP) subnetworks.
Standard

LOADABLE SOFTWARE STANDARDS

2016-07-14
CURRENT
ARINC665-4
This document defines the aircraft industry's standards for Loadable Software Parts (LSPs) and Media 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. It includes part numbering, content, labeling, and formatting of an LSP, and a Media Set containing LSPs.
Standard

ON-GROUND AIRCRAFT WIRELESS COMMUNICATION

2016-07-14
CURRENT
ARINC822A
This specification describes the functionality and interfaces of an Internet Protocol (IP)-based wireless communications system between an aircraft on the ground and a ground-based network using Wireless Local Area Network (WLAN) and/or cellular radios and protocols. The ground-based network will be primarily used to provide connectivity to an airline's back office or to its back-end maintenance systems although other uses are also possible when there is a need to transfer data to or from the aircraft's applications while it is taxiing or parked. Gatelink is the accepted industry term for this type of connection. This document is a major revision to ARINC Specification 822 released in 2008.
X