Search Results

Define IEEE-1394 Beta PHY Enhancements that drive faster 1394 port connects and increased robustness. These enhancements include Detect loss of descrambler synchronization, Fast-ReTrain, Fast Power-on Re-connect, Fast Connection Tone Debounce and Programmable invalidCount.

This SAE Aerospace Standard (AS) establishes guidelines for the use of IEEE-1394-2008 Beta (formerly IEEE-1394b) as a data bus network in military and aerospace vehicles. It encompasses the data bus cable and its interface electronics for a system utilizing S200 over copper medium over extended lengths. This document contains extensions/restrictions to AS5643/1 to support S200 data rate. This document does not identify specific environmental requirements (electromagnetic compatibility, temperature, vibration, etc.); such requirements will be vehicle-specific and even LRU-specific. However, the hardware requirements and examples contained herein do address many of the environmental conditions that military and aerospace vehicles may experience. One should reference the appropriate sections of MIL-STD-461E for their particular LRU, and utilize handbooks such as MIL-HDBK-454A and MIL-HDBK-5400 for guidance.

Fibre Channel is the primary avionics bus on many modern military aircraft. It is also the defined High-Speed bus for MIL-STD-1760E weapons applications. Profiled Ethernet networks are the primary avionics bus in many commercial aircraft and Commercial Ethernet is an ever increasing presence in modern military aircraft as well. This network standard is a convergence of Fibre Channel and Ethernet into a unified network standard which will provide a seamless approach to integrating end systems from either technology into a merged network structure. This work is based upon the commercial data storage market industry’s work on the Converged Data Storage Network or FCoE (Fibre Channel over Ethernet). This effort will look at profiling the FCoE work done in the commercial industry and adding information where necessary to affect a networking standard that will seamlessly integrate end systems from Commercial Ethernet, Fibre Channel, or FCoE enhanced devices.

Develop a profile of the TSN set of standards that is applicable to Avionics use cases, including AS6509 CAIN

This standard defines a broadband time division command/response multiplex data bus that co-exists and permits concurrent operation with a MIL-STD-1553 Data Bus and MIL-STD-1760 Appendix C. This standard allows utilization of legacy MIL-STD-1553 wiring and bus coupling.

This ARP establishes guidelines for the use of IEEE-802.3 as a data bus network in military and aerospace vehicles. It encompasses the data cable and its connections for a system utilizing 10Base-T, 100Base-T, 1000BASE-T and 10GBASE-T over copper medium dependent interfaces (MDI). This document contains extensions/restrictions to “off-the-shelf” IEEE-802.3 standards, and assumes that the reader already has a working knowledge of IEEE-802.3.

The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards.

The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards.

This document is intended to explain, in detail, the rationale behind the features and functions of the AS4074, Linear, Token-passing, Bus (LTPB). The discussions also address the considerations which a system designer should take into account when designing a system using this bus. Other information can be found in these related documents: AIR4271 - Handbook of System Data Communication AS4290 - Validation Test Plan for AS4074

This document is intended to explain, in detail, the rationale behind the features and functions of the AS4074, Linear, Token-passing, Bus (LTPB). The discussions also address the considerations which a system designer should take into account when designing a system using this bus. Other information can be found in these related documents:

This section defines the scope of the document, provides a brief history of the Pi-Bus, discusses key features of the Pi-Bus, and provides an overview of the operation of the Pi-Bus. This document is a handbook intended to accompany AS4710 Pi-Bus standard. The purpose of this document is to provide information to aid users of the Pi-Bus, whether they be implementors of Pi-Bus controllers, architects of systems considering using the Pi-Bus, or programmers who must develop applications in a system which uses the Pi-Bus as the backplane communications bus. This document also provides rationale for many of the Pi-Bus requirements as defined in AS4710 and a discussion of potential enhancements that are being considered for the Pi-Bus.

This section defines the scope of the document, provides a brief history of the Pi-Bus, discusses key features of the Pi-Bus, and provides an overview of the operation of the Pi-Bus. This document is a handbook intended to accompany AS4710 Pi-Bus standard. The purpose of this document is to provide information to aid users of the Pi-Bus, whether they be implementors of Pi-Bus controllers, architects of systems considering using the Pi-Bus, or programmers who must develop applications in a system which uses the Pi-Bus as the backplane communications bus. This document also provides rationale for many of the Pi-Bus requirements as defined in AS4710 and a discussion of potential enhancements that are being considered for the Pi-Bus.

This document contains guidance for using SAE publications, AS4112 through AS4117 (MIL-STD-1553 related Test Plans). Included herein are the referenced test plan paragraphs numbers and titles, the purpose of the test, the associated MIL-STD-1553 paragraph, commentary concerning test methods and rationale, and instrumentation requirements.

This document contains guidance for using SAE publications, AS4112 through AS4117 (MIL-STD-1553 related Test Plans). Included herein are the referenced test plan paragraphs numbers and titles, the purpose of the test, the associated MIL-STD-1553 paragraph, commentary concerning test methods and rationale, and instrumentation requirements.

The emphasis in this standard is the development of data word and message formats for AS15531 or MIL-STD-1553 data bus applications. This standard is intended as a guide for the designer to identify standard data words and messages for use in avionics systems and subsystems. These standard words and messages, as well as the documentation format for interface control document (ICD) sheets, provide the basis for defining 15531/1553 systems. Also provided in this standard is the method for developing additional data word formats and messages that may be required by a particular system but are not covered by the formats provided herein. It is essential that any new word formats or message formats that are developed for a 15531/1553 application follow the fundamental guidelines established in this standard in order to ease future standardization of these words and messages. The standard word formats presented represent a composite result of studies conducted by the U.S.

The emphasis in this standard is the development of data word and message formats for AS15531 or MIL-STD-1553 data bus applications. This standard is intended as a guide for the designer to identify standard data words and messages for use in avionics systems and subsystems. These standard words and messages, as well as the documentation format for interface control document (ICD) sheets, provide the basis for defining 15531/1553 systems. Also provided in this standard is the method for developing additional data word formats and messages that may be required by a particular system but are not covered by the formats provided herein. It is essential that any new word formats or message formats that are developed for a 15531/1553 application follow the fundamental guidelines established in this standard in order to ease future standardization of these words and messages. The standard word formats presented represent a composite result of studies conducted by the U.S.

This Handbook has been prepared by the Ring Implementation Task Group of the SAE AS-2 Committee, and is intended to support AS4075 by providing explanation of the standard itself and guidance on its use. The principal objective in the preparation of a standard is to provide a statement of operational and performance requirements, and an unambiguous definition of the functions to be realized in any implementation, primarily from the view point of interoperability. While efforts have been made within the AS4075 standard to provide a readable general description of the HSRB, detailed explanations, rationale and guidance to the use are incompatible with the purpose and, indeed, the format of a standard. Accordingly, this Handbook contains a paragraph-by-paragraph explanation of the main sections of the standard, and a discussion of application and implementation issues.

This Handbook has been prepared by the Ring Implementation Task Group of the SAE AS-2 Committee, and is intended to support AS4075 by providing explanation of the standard itself and guidance on its use. The principal objective in the preparation of a standard is to provide a statement of operational and performance requirements, and an unambiguous definition of the functions to be realized in any implementation, primarily from the view point of interoperability. While efforts have been made within the AS4075 standard to provide a readable general description of the HSRB, detailed explanations, rationale and guidance to the use are incompatible with the purpose and, indeed, the format of a standard. Accordingly, this Handbook contains a paragraph-by-paragraph explanation of the main sections of the standard, and a discussion of application and implementation issues.

The original purpose of this document was to establish interface requirements for modular avionics backplanes to be prototyped up to 1995. The document was issued as ARD50011 in September 1992. It is being reissued as an SAE Aerospace Information Report (AIR) in order to: a Preserve the requirements for more than 2 years b Support design of retrofits and avionics systems to be fielded in the years 1995 to 2000 c Provide a baseline for updating the requirements of future integrated systems These requirements were and are intended to promote standardization of modular avionic backplane interfaces. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms.

The original purpose of this document was to establish interface requirements for modular avionics backplanes to be prototyped up to 1995. The document was issued as ARD50011 in September 1992. It is being reissued as an SAE Aerospace Information Report (AIR) in order to: a Preserve the requirements for more than 2 years b Support design of retrofits and avionics systems to be fielded in the years 1995 to 2000 c Provide a baseline for updating the requirements of future integrated systems These requirements were and are intended to promote standardization of modular avionic backplane interfaces. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms.