This Technical Specification defines the standard test method to assess the operating mechanical endurance of a set of connectors without electrical loadEngine and Airframe Technical Standards Committee (TSC)
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. Supplement 1 adds numerous additions and changes: Scripting Language Definition Creation of A661P2_StringType Addition of Color property to the Image Primitive Addition of color Standard Library. Correction of ColorMatrix Datatype Addition of Private Library schema Constraints on max array size and max string size Rectangle primitive clarification Function Library functionAirlines Electronic Engineering Committee
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 9 adds numerous changes and additions: Restructuring of the document for ease of use Addition of GpVertexBuffer and GpVertexRender Widgets Formalization of the Super Layer concept Generalization of input device text Timeout values for things like popups Extended BlockAirlines Electronic Engineering Committee
The purpose of ARINC 633 is to specify the format and exchange of Aeronautical Operational Control (AOC) communications. Examples of ARINC 633 AOC Structures/Messages include: Flight Plans, 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 enables the development of applications shared by numerous airlines on different aircraft types. Benefits include improved dispatchability and reduce operator cost. ARINC 633 is a complete definition of AOC message sets used in commercial aviation with XML schema definitions includedAirlines Electronic Engineering Committee
This specification covers the requirements for forged bolts in DTD5638, EN 2952, EN 3219 or AMS5662 material with rolled underhead radii. The bolts will develop a minimum tensile strength of 1275 MPa (185,000 lbf/in²) at room temperature and 1000 MPa (145,000 lbf/in²) at 650°CEngine and Airframe Technical Standards Committee (TSC)
This specification defines test methods and performance criteria for ultrasonically welded wire-to-terminal bonds as shown in Figure 1. This specification subjects parts to environmental exposures to simulate a lifetime of field exposure for a road vehicle. Exposures referenced in this specification include thermal shock, temperature humidity cycling, and mechanical stress. This specification is intended to evaluate the strength and performance of the interface between wires and the electrical terminal pad. The graphics used are specific to the linear weld type of process equipment. Validation of the terminal is a separate task (refer to a component validation test such as SAE/USCAR-2). If the weld under test (WUT) is different than described in this section or is subjected to conditions beyond what is typical of automotive use, the test sequence may not be applicable. Ensure that parts used in other conditions are validated for the actual conditions encountered. Vehicle and productUSCAR
The provisions of this document, attachments, and supplements apply to the creation of a universal methodology for data communication, machine language, and reporting to and from manufacturing devices in the automotive production (Smart Manufacturing) environment. Universal connectivity is one of the foundational technologies enabling data sharing among participating components of an Industrial Internet of Things (IIoT) system. Connectivity provides the ability to exchange data among participants within a functional domain, across functional domains within a system, and across systems. The data exchanged may include sensor updates, events, alarms, status changes, commands, and configuration updates. Connectivity is a crosscutting function in the Industrial Internet Reference Architecture. It provides the ability to exchange data between participants within and across functional domains (control, operations, information, applications, and businessUSCAR
This test procedure is intended to evaluate and/or validate electrical ground schemes for use on the body or chassis. There are two classes based on the expected environmental conditions. Exposed Grounds can be located anywhere in the vehicle (except on the powertrain) and is the class for which most schemes should be tested. Unexposed Grounds can only be used in the passenger compartment or trunk and as such are special cases. This procedure as written is not intended for testing powertrain grounds where high temperatures and vibration levels may be encountered. These situations may require modifications to this procedure and are left to the Responsible Engineer to determine. This specification does not specifically address validation of terminal to wire electrical crimps. Crimps are tested to SAE/USCAR-21USCAR
This document is a supplement to SAE/USCAR 17 and is intended to give recommended usages for one and two-way RF connectors and dimensional requirements for 2-way RF connectors and hybrid (RF & DC power) connectors which are not currently specified elsewhere. The radio frequency (RF) connector interface specified herein is suited for unsealed and sealed automobile applications up to 6 GHz and is intended for in-line, board mount, device mount, straight or angled applications. Dimensional requirements are specified in this document to ensure interchangeability. Compliance with the dimensional requirements of this specification will not guarantee interoperability between different suppliers mating connectors. It is the supplier responsibility to ensure RF performance requirements are met with other suppliers mating connectors. Performance requirements are specified in SAE/USCAR-2, and in SAE/USCAR-17USCAR
Procedures included within this specification are intended to cover performance testing at all phases of development, production, and field analysis of any USB cable assemblies and associated connections that constitute the electrical connection systems between the consumer peripheral interface and the USB computer source in road vehicle applications. These procedures are only applicable to the USB connector and the cable. Unless otherwise specified, all of the tests listed in this specification are for both consumer and nonconsumer interface connectorsUSCAR
This document defines system architectural philosophy and specific design guidance for the design and interface of various cabin related components. System performance parameters are described for connectors, electrical interfaces, operational mode control/protocols, BITE reporting, reliability, environmental conditions, and software data loading. Supplement 8 defines an IEEE 802.11n compliant Cabin Wireless Access Point (CWAP) suitable for installation in a wide variety of cabins. It provides an update to the digital overhead monitor mounting provisions and connectors for compatibility with the CWAP definition. Supplement 8 includes new generation implementation solutions for Cabin Wireless Access Points (CWAP) and Cabin Cell Modems (CCM). The description and interface definitions for an HD cabin and cargo video surveillance system is added. Finally, it includes the component definition and network specificationsAirlines Electronic Engineering Committee
ARINC 858 Part 3 defines a Common IPS Radio Interface (CIRI) protocol for conveying radio status information and transferring digital data between the Airborne IPS System and Airborne Radios. This standard includes the functional description of the protocol, including applicable use cases, protocol message formats, and protocol operation for both control plane and data plane exchanges. The protocol is intended to operate over a variety of on-aircraft communication means, including, but not limited to, ethernet-based and ARINC 664-based aircraft networks. The reader should also reference ARINC 858 Part 1 and Part 2. This product was developed in coordination with ICAO WG-I, RTCA SC-223, and EUROCAE WG-108Airlines Electronic Engineering Committee
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 interfacesAirlines Electronic Engineering Committee
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 metalUSCAR
SAE/USCAR-46 defines test methods and outputs for engine oil pump bench testing. Performance and durability testing are the primary focus of this standard. This is written to specifically address testing of electronically controlled variable displacement pumps but can be adapted to mechanically controlled pumps and other pump technologies as needed. This standard outlines critical inputs and outputs in order to perform the testing and report results, but does not specifically set the acceptance standards or pass/fail criteria. Acceptance criteria must be set by the customernull, null
This standard will define the Secure Open Data and Avionics Services (SODAS), the transport layers, and the suggested security mechanisms to enable communication between aircraft systems and an Electronic Flight Bag (EFB). Herein is the definition of a set of protocols and services for the exchange of aircraft avionics data across aircraft networks. The purpose is to define a common set of services to be used to access specific avionics data that will enhance EFB applicationsAirlines Electronic Engineering Committee
Procedures included within this specification are intended to cover performance testing at all phases of development, production, and field analysis of any USB cable assemblies and associated connections that constitute the electrical connection systems between the consumer peripheral interface and the USB computer source in road vehicle applications. These procedures are only applicable to the USB connector and the cable. Unless otherwise specified, all of the tests listed in this specification are for both consumer and nonconsumer interface connectorsUSCAR
This specification covers performance testing at all phases of development, production, and field analysis of electrical terminals, connectors, and components that constitute the electrical connection systems in road vehicle applications that are: low voltage (0 to 20 VDC) or Coaxial. Incomplete (mechanical) specifications for jacketed twisted pair connectors are also provided. These procedures are only applicable to terminals used for In-Line, Header, and Device Connector systems. They are not applicable to Edge Board connector systems, twist-lock connector systems, >20 VAC or DC, or to eyelet terminals. No electrical connector, terminal, or related component may be represented as having met USCAR specifications unless conformance to all applicable requirements of this specification have been verified and documented. All required verification and documentation must be done by the supplier of the part or parts. If testing is performed by another source, it does not relieve the primaryUSCAR
This document contains procedures for performance testing of electrical terminals, connectors, and components for coaxial-style cable with an outside cable diameter of 3.6mm and smaller. These are often called “Mini Coax connector systems.” This specification applies to coaxial cable connection systems that operate at frequencies from DC to 9 GHz and are intended for road vehicles. The characteristic impedance of the Mini-Coax connection system described here is 50 ohms, however nothing excludes the use of these connectors in systems with a different characteristic impedance. This specification applies only to connection systems using coaxial cableUSCAR
This standard provides a data base comprising standards used for the preparation of a navigation system data base. This data may be used with the operational flight software in a wide range of navigational equipmentAirlines Electronic Engineering Committee
The procedures contained in this specification cover the laboratory testing of replaceable halogen incandescent bulbs for use in automotive road illumination. The following tests are intended to be run under the following conditions. New bulb design Design or process change made to an existing bulb, which could affect the outcome of the test The completion of one calendar year, accept as noted in the following Test Schedule Table. Test Title Yearly Physical Dimensions X Mean Spherical Candela (MSCD) X External Visual Examination X Color X Leak/Sealability Through Terminals and Seals X Deflection X Fluid Compatibility Terminal Retention X Resonant Frequencies Aged Resonant Frequency Salt Spray Outgassing Temperatures Requirement Laboratory Life at 14.0 VDC X Luminous Intensity Maintenance X Vibration Durability Shock Aged Vibration Durability Terminal Requirements DRL (SAE J2087USCAR
The procedures contained in this specification cover the laboratory testing of miniature incandescent bulbs for use in automotive illumination and signaling applications. The following tests shall be run whenever the following occurs: New bulb design Design or process change made to an existing bulb, which could affect the outcome of the test. The completion of one calendar year as noted in the following Test Schedule Table. Process control data is acceptable. Test Title Yearly Physical Dimensions X Mean Spherical Candela X External Visual Examination X Crush X Thermal Shock X Bayonet Base Retention X Pin Removal X Wedge Base Retention X Lead Wire Bend X Lead Wire Pull X Natural Amber Color X Coated Amber Color Integrated Color Visual Color Point Color Color Maintenance and Coating Durability Amber Coating Chemical Resistance X X X Resonant Frequency Aged Resonant Frequency Salt Spray Wire Loop Pull X Outgassing/Heat Laboratory Life Accelerated Life X Luminous Intensity Maintenance XUSCAR
The procedures contained in this specification cover the laboratory testing of Exterior Lamps for use in automotive road illumination. The following tests are intended to be run under the following conditions. This document shall be applied to systems that meet the requirements for design, performance and validation established by government standards. If other manufacture’s components are intended to be approved for use in the lamp assembly, then those possible combinations of components shall be considered a new lamp assembly and shall also be testedUSCAR
This life test for underhood/passenger/trunk connector systems may be used in place of Section 5.9.6, Connection System Electrical Table of SAE/USCAR-2. All other requirements of SAE/USCAR-2 remain applicable even when this test is used. Refer to SAE/USCAR-2 and Connector/Terminal Supplier for appropriate power rating and current cycle TestingUSCAR
This document specifies dimensional, functional and visual requirements for Automotive grade coaxial cable. This material will be designated AG for general-purpose automotive applications or AG LL for low loss applications. It is the responsibility of the user of this cable to verify the suitability of the selected product (based on dimensional, mechanical, electrical and environmental requirements) for its intended application. It is the responsibility of the supplier to retain and maintain records as evidence of compliance to the requirements detailed in this standardUSCAR
This specification is a general level subsystem light source specification that establishes test requirements of a Gas Discharge Light Source (GDLS) subsystem for use on passenger vehicles. The completed test data to this test specification is intended to be provided to the OEM by the Tier one lamp set maker as part of the lamp assembly PPAP. Re-testing shall be required if any portion of the approved GDLS 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 subsystem is defined as the ballast, igniter and light source and 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. Substitution or replacement of only the light source shall be allowed during testing. Failure of the light source more than once inUSCAR
This test procedure is intended to evaluate and/or validate electrical ground schemes for use on the body or chassis. There are two classes based on the expected environmental conditions. Exposed Grounds can be located anywhere in the vehicle (except on the powertrain) and is the class for which most schemes should be tested. Unexposed Grounds can only be used in the passenger compartment or trunk and as such are special cases. This procedure as written is not intended for testing powertrain grounds where high temperatures and vibration levels may be encountered. These situations may require modifications to this procedure and are left to the Responsible Engineer to determine. This specification does not specifically address validation of terminal to wire electrical crimps. Crimps are tested to SAE/USCAR-21USCAR
The purpose of ARINC 633 is to specify the format and exchange of Aeronautical Operational Control (AOC) communications. Examples of ARINC 633 AOC Structures/Messages include: Flight Plans, 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 enables the development of applications shared by numerous airlines on different aircraft types. Benefits include improved dispatchability and reduce operator cost. ARINC 633 is a complete definition of AOC message sets used in commercial aviation with XML schema definitions includedAirlines Electronic Engineering Committee
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 SoftwareAirlines Electronic Engineering Committee
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 1Airlines Electronic Engineering Committee
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 standardsAirlines Electronic Engineering Committee
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-17USCAR
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-108Airlines Electronic Engineering Committee
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-108Airlines Electronic Engineering Committee
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 SpecificationsUSCAR
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 prefixUSCAR
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 metalUSCAR
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 harnessesUSCAR