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 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.

This standard establishes the design requirements for a fiber optic serial interconnect protocol, topology, and media. The application target for this standard is the interconnection of multiple aerospace sensors, processing resources, bulk storage resources and communications resources onboard aerospace platforms. The standard is for subsystem interconnection, as opposed to intra-backplane connection.

This document establishes test plans/procedures for the AS5643 Standard that by itself defines guidelines for the use of IEEE-1394b as a data bus network in military and aerospace vehicles. This test specification defines procedures and criteria for testing device compliance with the AS5643 Standard.

This document is a result of the desire for interoperability of modules on a Pi-Bus. This standard is a stand alone document that used the Very High Speed Integrated Circuit (VHSIC) Phase 2, Interoperability Standard PI-Bus Specification 2.2, as a starting point.

This document is a result of the desire for interoperability of modules on a Pi-Bus. This standard is a stand alone document that used the Very High Speed Integrated Circuit (VHSIC) Phase 2, Interoperability Standard Pi-Bus Specification 2.2, as a starting point.

A fault tolerant, real time high speed data communication standard is defined based on a ring topology and the use of a Token passing access method with distributed control. The requirements for the HSRB standard have been driven predominantly, but not exclusively, by military applications. Particular attention has been given to the need for low message latency, deterministic message priority and comprehensive reconfiguration capabilities. This document contains a definition of the semantics and protocol including delimiters, tokens, message priority, addressing, error detection and recovery schemes; and is written to be independent of bit rate and media. Parameters related to particular media and bit rates are defined in separate documents, the AS4075 slash sheets.

A fault tolerant, real time high speed data communication standard is defined based on a ring topology and the use of a Token passing access method with distributed control. The requirements for the HSRB standard have been driven predominantly, but not exclusively, by military applications. Particular attention has been given to the need for low message latency, deterministic message priority and comprehensive reconfiguration capabilities. This document contains a definition of the semantics and protocol including delimiters, tokens, message priority, addressing, error detection and recovery schemes; and is written to be independent of bit rate and media. Parameters related to particular media and bit rates are defined in separate documents, the AS4075 slash sheets.

This Handbook is intended to accompany or incorporate AS5643, AS5643/1, AS5657, AS5706, and ARD5708. In addition, full understanding of this Handbook also requires knowledge of IEEE-1394-1995, IEEE-1394a, and IEEE-1394b standards. This Handbook contains detailed explanations and architecture analysis on AS5643, bus timing and scheduling considerations, system redundancy design considerations, suggestions on AS5643-based system configurations, cable selection guidance, and lessons learned on failure modes.

This document establishes test plans/procedures for the AS5643/1 Slash Sheet. The AS5643/1 Slash Sheet establishes guidelines for the use of IEEE Std 1394-2008 as a data bus network in military and aerospace vehicles. It encompasses the data bus cable and its interface electronics for a system utilizing S400β over copper medium over extended lengths.

IEEE-1394b, Interface Requirements for Military and Aerospace Vehicle Applications, establishes the requirements for the use of IEEE Std 1394™-2008 as a data bus network in military and aerospace vehicles. The portion of IEEE Std 1394™-2008 standard used by AS5643 is referred to as IEEE-1394 Beta (formerly referred to as IEEE-1394b.) It defines the concept of operations and information flow on the network. As discussed in 1.4, this specification contains extensions/restrictions to “off-the-shelf” IEEE-1394 standards and assumes the reader already has a working knowledge of IEEE-1394. This document is referred to as the “base” specification, containing the generic requirements that specify data bus characteristics, data formats, and node operation.

This SAE Aerospace Standard (AS) establishes the requirements for the use of IEEE-1394b as a data bus network in military and aerospace vehicles. It defines the concept of operations and information flow on the network. As discussed in 1.4, this specification contains extensions/restrictions to “off-the-shelf” IEEE-1394 standards, and assumes that the reader already has a working knowledge of IEEE-1394. This document is referred to as the “base” specification, containing the generic requirements that specify data bus characteristics, data formats and node operation. It is important to note that this specification is not stand-alone - several requirements provide only example implementations and delegate the actual implementation to be specified by the network architect/integrator for a particular vehicle application. This information is typically contained in a “network profile” slash sheet that is subservient to this base specification.