Specifications - SAE Mobilus

Items (363)
Find
Fuel Cell Vehicle TerminologyUSCAR47-1 (Current)6/18/2026
This SAE Information Report contains definitions for hydrogen fuel cell powered vehicle terminology. It is intended that this document be a resource for those writing other hydrogen fuel cell vehicle documents, specifically, Standards or Recommended Practices.
USCAR
Automation Title for Group Code D22PC-Auto-1780276282909 (Current)6/1/2026
Automation Abstract for Group Code D22
Airlines Electronic Engineering Committee
3526 specification arinc standard3526_specification (Current)3/5/2026
3526 specification arinc standard
Airlines Electronic Engineering Committee
2026 Arinc Automation Document - Standard Specificiation - PageCount 210 - 475KJH007-26 (Current)12/23/2025
2026 Arinc Automation Document - Standard Specificiation - PageCount 210 - 475
Airlines Electronic Engineering Committee
USCAR-29USCAR-29 (Current)12/4/2025
USCAR-29
USCAR
USCAR 11242025 TestUSCAR11242000000000000000000000-1 (Current)11/24/2025
USCAR 11242025 Test
USCAR
Automation Title for Group Code D22PC-Auto-1763086025899 (Current)11/14/2025
Automation Abstract for Group Code D22
Airlines Electronic Engineering Committee
Automation Title for Group Code D22PC-Auto-1752670240025 (Current)7/16/2025
Automation Abstract for Group Code D22
Airlines Electronic Engineering Committee
Arinc Automation Document - Standard Specificiation - PageCount 210 - 475KJH007 (Historical)12/19/2024
Arinc Automation Document - Standard Specificiation - PageCount 210 - 475
Airlines Electronic Engineering Committee
Arinc Automation Document - Standard Specificiation - PageCount Greater than 475KJH008 (Current)12/19/2024
Arinc Automation Document - Standard Specificiation - PageCount Greater than 475
Airlines Electronic Engineering Committee
test for kevin SAAS ingestionarinc-kjh (Current)11/1/2024
test
Aviation Maintenance Committee
Automation Title for Group Code D22PC-Auto-1715022197983 (Current)5/6/2024
Automation Abstract for Group Code D22
Automation Title for Group Code D22PC-Auto-1713447343633 (Current)4/18/2024
Automation Abstract for Group Code D22
Airlines Electronic Engineering Committee
specification test 3specification3 (Historical)3/12/2024
specification test 3
Airlines Electronic Engineering Committee
TEST - 800P1 Cabin Connectors and Cables, Part 1, Description and OverviewARINC800P1-CSP (Historical)2/23/2024
This document is the first of a multi-part specification that will provide a catalog of cabin connector and cables that may be used in ARINC Standard cabin systems, including In-Flight Entertainment. Part 1 describes connector and cable requirements and evaluation criteria for the interface components used in the integration of cabin systems. Future releases will define connectors, contacts, and termination methods in Part 2. Cables will be specified in Part 3.
Airlines Electronic Engineering Committee
AOC AIR-GROUND DATA AND MESSAGE EXCHANGE FORMATARINC633-4 (Current)11/30/2021
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.
Airlines Electronic Engineering Committee
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 3A CONFORMITY TEST SPECIFICATIONS FOR ARINC 653 REQUIRED SERVICESARINC653P3A-2 (Current)11/15/2021
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.
Airlines Electronic Engineering Committee
AVIONICS APPLICATION SOFTWARE STANDARD INTERFACE PART 0 OVERVIEW OF ARINC 653ARINC653P0-3 (Current)11/15/2021
This document provides an overview of the entire set of documents collectively referred to as ARINC 653. As this set of documents evolves, Part 0 has been adjusted to reflect technical changes made in Supplements to Parts 1 through 5 in conjunction with the technical changes 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 3A – Conformity Test Specification for ARINC 653 Required Services Part 3B – Conformity Test Specification for ARINC 653 Extended Services Part 4 – Subset Services Part 5 – Core Software Recommended Capabilities The term “this document” refers to Part 0 only, while the term “ARINC 653” or “the Specification” refers to the whole set of ARINC 653 documents, currently Parts 0 to 5. The primary objective of ARINC 653 is to define a general-purpose APplication/EXecutive (APEX) interface (API = Application Program Interface) between the Core Software (CSW) of an Avionics Computer Resource (ACR) and the application software. Included within ARINC 653 are the interface requirements between the application software and the CSW and the list of services which allow the application software to control the scheduling, communication, and status information of its internal processing elements.
Airlines Electronic Engineering Committee
DEFINITION OF STANDARD INTERFACES FOR GALLEY INSERT (GAIN) EQUIPMENT PHYSICAL INTERFACESARINC810-6 (Current)11/10/2021
ARINC 810 defines galley equipment physical attachments, envelopes, connections, and qualification guidelines for interchangeable galley equipment. Supplement 6 defines the new Extended Size 2, intended for oven installation and other equipment suited to this type of installation.
Airlines Electronic Engineering Committee
STANDARD DATA INTERFACE FOR GALLEY INSERT (GAIN) EQUIPMENT PART 1 CAN COMMUNICATIONSARINC812AP1-2 (Current)9/10/2021
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.
Airlines Electronic Engineering Committee
CABIN CONNECTORS AND CABLES PART 2 SPECIFICATION OF CONNECTORS, CONTACTS, AND BACKSHELLSARINC800P2-2 (Current)9/9/2021
This specification describes the general connectors, contacts, and backshells in their shape and characteristic for cabin systems for commercial aircrafts. ARINC 600, ARINC 404, and ARINC 801 connector specifications are published as independent standards.
Airlines Electronic Engineering Committee
Coaxial Cable Connector Interface - Square Outer ConducterUSCAR19-2 (Current)8/5/2021
This radio frequency (RF) connector interface specification is suited for unsealed automobile applications up to 2 GHz.Dimensional requirements are specified in this document to ensure interchangeability. This RF connector interface specification is intended for in-line, board mount, device mount, straight or angled applications. Performance requirements are specified in SAE/USCAR-2, and in SAE/USCAR-17.
USCAR
INTERNET PROTOCOL SUITE (IPS) FOR AERONAUTICAL SAFETY SERVICES PART 2 IPS GATEWAY AIR-GROUND INTEROPERABILITYARINC858P2 (Current)6/21/2021
ARINC 858 Part 2 provides aviation ground system gateway considerations necessary to transition to the Internet Protocol Suite (IPS). ARINC 858 Part 2 describes the principles of operation for an IPS gateway that enables ACARS application messages to be exchanged between an IPS aircraft and a ground ACARS host. ARINC 858 Part 2 also describes the principles of operation for an IPS gateway that enables OSI-based application messages to be exchanged between an IPS host and an OSI end system. This product was developed in coordination with ICAO WG-I, RTCA SC-223, and EUROCAE WG-108.
Airlines Electronic Engineering Committee
INTERNET PROTOCOL SUITE (IPS) FOR AERONAUTICAL SAFETY SERVICES PART 1 AIRBORNE IPS SYSTEM TECHNICAL REQUIREMENTSARINC858P1 (Current)6/21/2021
ARINC 858 Part 1 defines the airborne data communication network infrastructure for aviation safety services using the Internet Protocol Suite (IPS). ARINC 858 builds upon ICAO Doc 9896, Manual on the Aeronautical Telecommunication Network (ATN) using Internet Protocol Suite (IPS) Standards and Protocol. IPS will extend the useful life of data comm services presently used by operators, e.g., VDL, Inmarsat SBB, Iridium NEXT, and others. It represents the evolutionary path from ACARS and ATN/OSI to the end state: ATN/IPS. ARINC 858 includes advanced capabilities such as aviation security and mobility. This product was developed in coordination with ICAO WG-I, RTCA SC-223, and EUROCAE WG-108.
Airlines Electronic Engineering Committee
DIMENSIONAL AND PERFORMANCE SPECIFICATION FOR AFTER-MARKET GASOLINE ENGINE OIL FILTERSUSCAR36-1 (Current)5/13/2021
This specification defines the dimensional and performance requirements for aftermarket spin-on oil filters intended for use on gasoline engines. Filters meeting this specification may also be suitable for use on some diesel applications. Filters meeting these dimensional limits are intended to meet the oil filter fit and package requirements for engine and vehicle designs. Filters meeting the performance requirements are intended to maintain sufficient durability to support typical 10000 mile oil change intervals. Some OEM engines may require special filters for which this specification would not support. Filters that meet or exceed this specification requirements for both dimensional and performance can claim “Conformance to SAE/USCAR - 36 Specifications.” Filters that meet just the performance specifications (ie. may have different thread) can claim “Aligns to SAE/USCAR - 36 Performance Specifications.”
USCAR
ELECTRICAL CONNECTOR DESIGN REQUIREMENTSUSCAR12-6 (Current)1/20/2021
This document gives specific and measurable design requirements to be applied at a design review prior to tooling. The specification is formatted as a checklist to aid in its use. The requirements do not apply in all situations so engineering judgment must be used. This is a specification for design; applicable performance specifications (USCAR-2, etc.) must still be performed. Specific requirements in this document are grouped by component using a prefix as shown in Table 1 and are numbered by an item number following the prefix.
USCAR
PERFORMANCE SPECIFICATION FOR AUTOMOTIVE WIRE HARNESS RETAINER CLIPSUSCAR44-1 (Historical)1/20/2021
This specification describes a method and acceptance criteria for testing automotive wire harness retainer clips. Retainer clips are plastic parts that hold a wire harness or electrical connector in a specific position. Typical plastic retainers work by having a set of “branches” that can be inserted into a hole sized to be easy to install but provide acceptable retention. This specification tests retainer clips for mechanical retention when exposed to the mechanical and environmental stresses typically found in automotive applications over a 15-year service life. This specification has several test options to allow the test to match to the expected service conditions. The variability of applications typically arises from different ambient temperatures near the clip, different proximity to automotive fluids, different exposure to standing water or water spray, and different thicknesses of the holes that the clip is inserted into. Clips are typically inserted into sheet or rolled metal from 0.6 to 8 mm thick, so this specification focuses on that range. Outside of this range requires a custom test. The procedures described in this document have been evaluated for the design types shown in Table 2. Use of USCAR-44 for other than a design shown in Table 2 may or may not produce acceptable test correlation to actual experience, but USCAR has not reviewed any data. USCAR-44 can be used at all phases of development, production, and field analysis since it is a performance test and not a process validation or quality assessment. No retainer may be represented as having met USCAR/EWCAP specifications unless conformance to all applicable requirements of this specification have been verified and documented. All required verification and documentation must be provided by the supplier of the part. If testing is performed by another source, it does not relieve the primary supplier of responsibility for documentation (DVP&R) of all test results and for verification that all samples tested met all applicable acceptance criteria.
USCAR
ERGONOMICS SPECIFICATION FOR MANUALLY SEATED FASTENERSUSCAR47 (Historical)12/30/2020
This document describes the assembly force guidelines for manually seated push-pins, clips, and similar retention devices. For the purpose of this document, the term “clip” is used to reference all retention devices addressed within this document. Applicable retention devices must have force exerted directly to the clip using the finger/thumb and are hand seated independent of other fasteners. For a retention device to be manually installed and seated independent of other retention devices, it must be seated fully without any interaction with an adjacent fastener (i.e., multiple PIA clips on the back of a hard trim panel). This standard applies to contact surfaces angled at 90 degrees (±10 degrees) and/or perpendicular from the direction of force insertion. Mechanically installed fasteners (screws, rivets, etc.) are not included in this document. This standard does not apply to extraction/retention forces. Refer to USCAR-44 for additional guidelines for clips attached to wire harnesses. All possible design and applications could not be anticipated in creating this guideline. Pictures and examples are included throughout to assist. Where there are questions of adherence to the guideline, consult the responsible ergonomic departments or representatives.
USCAR
DEEMBRITTLEMENT VERIFICATION TESTUSCAR7-2 (Current)11/19/2020
This standard outlines test methods and practices which can detect embrittlement of steel parts. It is a process control or referee verification test. The risk of embrittlement of steel is minimized by using best practices in the finishing/coating process. One such practice is described in SAE/USCAR-5, Avoidance of Hydrogen Embrittlement of Steel.
USCAR
TORQUE-TENSION TESTING AND EVALUATION OF FASTENER FINISHESUSCAR11-2 (Current)11/19/2020
This standard provides a test method for determining the torque-tension relationship of a fastener finish as applied to a surrogate screw for the purpose of measuring the frictional characteristic of the fastener finish. The results obtained by this test shall be used as a process control attribute of the fastener finish and shall not be utilized for specific applications.
USCAR
TEST PROCEDURES FOR EVALUATING BOLT-LOAD RETENTION OF MAGNESIUM ALLOYSUSCAR35-1 (Current)11/19/2020
A bolt-load retention (BLR) test is a practical test to determine the bolt load of a fastener joint with time and at given temperatures. There are three types of BLR tests described in this standard, namely general-purpose test, design-purpose test, and screening material test. A general-purpose BLR test may be used for screening materials, while a design-purpose BLR test is usually used to verify the BLR behavior of a specific joint. The screening material test is an example of the general-purpose test for typical automotive applications.
USCAR
STANDARD FOR TIRE TRACEABILITY CONTENT AND FORMAT FOR THE RADIO-FREQUENCY IDENTIFICATION (RFID) TAG AND ASSOCIATED TIRE DATA SETUSCAR39-1 (Current)11/19/2020
This standard describes a requirement for automotive tire traceability. It includes a definition of the RFID tag and the associated tire data set that can be accessed using the RFID tag as an identifier. The standard describes a unique identification and the associated data set for each tire produced by the tire fabricator. This data will either be provided or transmitted at the time of shipment to retailers, wholesalers or original equipment vehicle manufacturers. Tire identification code and data may be used for error proofing, determining the tire specifications or supporting any inquiries that occur for the duration of its automotive life.
USCAR
Test for Evaluating the Torque-Tension Relationship of Both External and Internal Metric Threaded FastenersUSCAR10-3 (Current)11/19/2020
USCAR
STANDARD FOR IN-TANK ELECTRIC FUEL PUMPSUSCAR13-1 (Current)11/19/2020
This standard covers the operational characteristics, environment, durability procedures, and test procedures for in-tank electric fuel pumps for automotive gasoline applications. Specific performance and test criteria used in conjunction with this procedure are specified on the pump drawing. Particular sections of this document may be required for all applications. This standard is intended to evaluate specific characteristics as a supplement to normal material inspections, dimensional checking, and in-process controls, and should in no way adversely influence other inspection operations.
USCAR
NEW FINISH DEVELOPMENT DOCUMENTUSCAR32-1 (Current)11/19/2020
This standard lists variables that shall be investigated and reported as an initial investigation into new or revised surface finishes intended for use on fasteners. This standard provides instruction for producing a final report that will be used to determine if further investigation of a surface finish is justified. Further investigation may include tests and evaluations specific to an individual OEM prior to introduction/approval of the surface finish. The final report shall include the results, observations, and conclusions for all of the variables. The final report may be made up of several individual reports covering each variable. In all cases the laboratory performing the test, the test date and the report approver shall be included in the final report.
USCAR
STANDARD FOR D.C. BRUSH MOTOR - HVAC BLOWERSUSCAR6-1 (Current)11/19/2020
This standard sets forth the performance and durability requirements for 12-volt, D.C. brush-type electric motors used for automobile Heating, Ventilation, and Air Conditioning (HVAC) blowers and outlines Production Validation and Continuing Conformance testing.
USCAR
LEAD-FREE SOLDER VALIDATION TEST PLANUSCAR40-2 (Current)11/19/2020
This guideline is applicable to existing lead solder production products that will change to lead-free solder processes to meet the ELV Directive 2000/53/EC Annex II, exemption 8B requirements. This guideline is applicable to similar products used by multiple OEM's that have the same manufacturing processes / equipment. The intent is to streamline the supplier’s environmental testing via common qualification to reduce timing, quantities, and costs.
USCAR
LOGICAL SOFTWARE PART PACKAGING FOR TRANSPORTARINC641-1 (Current)11/16/2020
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.
Airlines Electronic Engineering Committee
COCKPIT DISPLAY SYSTEM INTERFACES TO USER SYSTEMS PART 1 AVIONICS INTERFACES, BASIC SYMBOLOGY, AND BEHAVIORARINC661P1-8 (Current)9/18/2020
ARINC 661 defines logical interfaces to Cockpit Display Systems (CDS) used in all types of aircraft 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. Supplement 8 adds numerous changes and additions. Eleven new widgets are added, all related to 3D Maps. Seven new widget extensions. Metadata definitions (XML) for all widgets, extensions, events, symbols, and associated data types.
Airlines Electronic Engineering Committee
439B Simulated Air Traffic Control Environments in Flight Simulation Training DevicesARINC439B (Current)8/31/2020
This document provides guidance on provision of SATCE systems in Flight Simulation Training Devices (FSTDs) for the benefit of flight crew training. This work builds upon that originally undertaken by International Air Transport Association (IATA) Flight Simulator Working Group in 2002, and further developed in the International Civil Aviation Organization (ICAO) Doc. 9625 Vol 1, Part 2, Editions 3 and 4. This document is intended to be a practical starting point that can serve as the basis for future developments of SATCE.
Flight Simulator Engineering and Maintenance Committee
COCKPIT DISPLAY SYSTEM INTERFACES TO USER SYSTEMS PART 2 USER INTERFACE MARKUP LANGUAGE (UIML)ARINC661P2 (Current)8/7/2020
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.
Airlines Electronic Engineering Committee
SPECIFICATION FOR TESTING AUTOMOTIVE LED MODULESUSCAR33-1 (Current)8/3/2020
This specification is a general level subsystem light source specification that establishes test requirements of light emitting diode (LED) components and modules for use in automotive lighting systems. The completed test data from this test specification is intended to be provided to the OEM by the Tier 1 lamp set maker as part of the lamp assembly PPAP. Re-testing shall be required if any portion of the approved LED module experiences a design, manufacturing, or component change. This document shall be applied to systems that meet the requirements for design, performance, and validation established by government standards. The LED module is defined as the LED devices and any electronics required to properly energize the LEDs using a vehicle electrical power system along with any associated electrical wiring, connectors, and thermal management system. Samples shall be tested as a subsystem and considered one test sample for the entire test sequence. A failure of any component in the test sample shall constitute a failure of the entire sample. NOTE: If other manufacturers’ components are intended to be approved for use in the LED modules, then those possible combinations of components shall be considered a new LED module and shall also be tested. Additional testing may be required by individual OEMs to meet specific EMC, quality, reliability, and durability objectives. The following tests are to be performed under the following conditions: New sample. Design or process change made to an existing module. Completion of one calendar year as noted in the annual tests table shown in Appendix E. (Note: Production process control data, collected at a shorter interval per an approved control plan, may be substituted if approved by customer’s responsible engineer and purchasing representative.)
USCAR
DATALINK GROUND SYSTEMS STANDARD AND INTERFACE SPECIFICATION (DGSS/IS)ARINC620-10 (Current)7/31/2020
ARINC Specification 620 defines the interfaces between the Datalink Service Provider (DSP) and the aircraft, other ground-based datalink services, and users. The datalink ground system standard definition supports traditional ACARS and AOA protocols, as well as Media Independent Aircraft Messaging (MIAM) as defined by ARINC Specification 841. MIAM messages can be much larger than ACARS messages (5 MB versus 3.3 kB per message). Supplement 10 improves Controller-Pilot Data Link Communications (CPDLC) by defining a “Deliver By (DB)” period that allows the DSP, that originated the message, to intercept and discard the message if it is not delivered by the specified time. Supplement 10 also adds a Media Advisory code for ACARS over IP (AoIP) indicating that an ACARS non Safety Services messages is being transferred over IP links. New Reason Codes are assigned for un-transmittable or undeliverable messages. ACARS Character set clarifications are also provided in Supplement 10.
Airlines Electronic Engineering Committee
CABIN EQUIPMENT INTERFACES PART 5 CABIN ELECTRICAL EQUIPMENT AND WIRING INSTALLATION GUIDELINESARINC628P5-4 (Current)7/24/2020
ARINC Specification 628, Cabin Equipment Interfaces (CEI) Part 5 Parts Selection, Wire Design and Installation Guidelines, provides design and mounting guidelines for electrical installations, mainly for supplier of cabin furnishing equipment. Part 5 addresses several aspects of installation and is divided into five sections: Introduction, Parts Selection, Electrical Wire Design Guidelines, Wire Installation Guidelines, and Documentation Guidelines. Guidelines regarding design, safety, and other subjects relevant to acceptance of the end item are addressed. Notes explaining the reason for setting a guideline or suggesting methods for performing the task are provided in commentary. The content of the document is designed to make it usable for reference by industry, particularly manufacturers of seats and equipment.
Airlines Electronic Engineering Committee
AIRCRAFT DATA INTERFACE FUNCTION (ADIF)ARINC834-8 (Current)7/21/2020
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.
Airlines Electronic Engineering Committee
VHF DIGITAL LINK (VDL) MODE 2 IMPLEMENTATION PROVISIONSARINC631-8 (Current)7/15/2020
This document describes the functions to be performed by airborne and ground components of the VDLM2 to successfully transfer messages from VHF ground networks to avionics systems on aircraft and vice versa where the data are encoded in a code and byte independent format. The compatibility of VDLM2 with OSI is established by defining a set of services and protocols that are in accordance with the OSI basic reference model. The compatibility with the ATN protocols is achieved by defining a set of interfaces between the VDLM2 subnetwork protocol specification and the Mobile Subnetwork Dependent Convergence Function (MSNDCF). The SNDCF is defined in the ICAO ATN SARPs.
Airlines Electronic Engineering Committee
CABIN CONNECTORS AND CABLES, PART 4, STANDARD TEST METHODOLOGYARINC800P4-1 (Current)7/13/2020
ARINC 800 is the first industry standard intended for characterization of aviation-grade high-speed (Gbps) Ethernet links. The test methods are based on realistic representation of cabin networks. The notional cabling architecture is based on IFE seat distribution using multiple intermediate disconnects. Sequential testing is supported by building up number of connectors in the link. Test guidelines for mixed intermediate cable lengths are provided.
Airlines Electronic Engineering Committee
485P1-4 Cabin Equipment Interfaces, Part 1, Head End Equipment ProtocolARINC485P1-4 (Current)6/30/2020
This standard defines the electrical characteristics, protocol and data content for a modified version of the EIA RS-485 data bus adapted for use with cabin electronics equipment. Specific cabin equipment interfaces are defined by ARINC 628.
Airlines Electronic Engineering Committee
485P2-5 Cabin Equipment Interfaces, Part 2, Physical Layer - In-Seat ProtocolARINC485P2-5 (Current)6/30/2020
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.
Airlines Electronic Engineering Committee
MEDIA INDEPENDENT SECURE OFFBOARD NETWORKARINC848 (Current)6/19/2020
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.
Airlines Electronic Engineering Committee
Items per page:
1 – 50 of 363