Refine Your Search

Topic

Search Results

Standard

IEEE-1394 Beta PHY Enhancements

2022-05-25
WIP
AS5643/3
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.
Standard

S200 Copper Media Interface Characteristics Over Extended Distances

2022-05-25
WIP
AS5643/2
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.
Standard

Aerospace TSN Profile

2019-10-24
WIP
AS6675
Develop a profile of the TSN set of standards that is applicable to Avionics use cases, including AS6509 CAIN
Standard

IEEE-1394b for Military and Aerospace Vehicles - Applications Handbook

2019-08-12
CURRENT
AIR5654A
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.
Standard

Verification Methods for AS5653 Network Terminal

2019-04-24
CURRENT
AS6088
This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Terminal (NT) complies with the NT requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all the requirements invoked by documents that are referenced by AS5653. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653 and in this verification document.
Standard

Broadband 1553

2018-05-22
WIP
AS8774
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.
Standard

10 Megabit/sec Network Configuration Digital Time Division Command/Response Multiplex Data Bus

2018-01-18
CURRENT
AS5652A
This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration that is functionally similar to MIL-STD-1553B with Notice 2 but with a star topology and some deleted functionality. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.
Standard

Verification Methods for AS5653 Network Controller

2017-10-11
CURRENT
AS6089
This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Controller (NC) complies with the NC requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all of the requirements invoked by documents that are referenced by AS5653. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653 and in this verification document.
Standard

Guidelines for Ethernet Physical Layer on Military and Aerospace Vehicle Applications

2017-08-01
WIP
ARP7208
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.
Standard

Digital Time Division Command/Response Multiplex Data Bus

2017-03-21
CURRENT
AS15531A
This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration, that is functionally equivalent to MIL-STD-1553B with Notice 2. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.
Standard

Linear Token Passing Multiplex Data Bus

2017-02-21
CURRENT
AS4074B
This standard specifies the characteristics of the SAE Linear Token Passing Bus (LTPB) Interface Unit. The LTPB provides a high reliability, high bandwidth, low latency serial interconnection network suitable for utilization in real time military and commercial applications. Multiple redundant data paths can be implemented to enhance reliability and survivability in those applications which require these attributes. The token passing and data exchange protocols are optimized to provide low latency and fast failure detection and correction. Physical configurations with bus lengths up to 1000 m can be accommodated.
Standard

Statement on Requirements for Real-Time Communication Protocols (RTCP)

2016-10-21
CURRENT
AIR4886A
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.
Standard

Handbook of System Data Communications

2016-10-21
CURRENT
AIR4271A
This Aerospace Information Report (AIR) has been prepared by the Systems Applications and Requirements Subcommittee of SAE Committee AS-2. It is intended to provide guidance primarily, but not exclusively, for specifiers and designers of data communication systems for real time military avionics applications within a platform. The subject of high speed data transmission is addressed from two standpoints: (1) the influence of developments in technology on avionics architectures as a whole and (2) the way in which specific problems, such as video, voice, closed loop control, and security may be handled. While the material has been prepared against a background of experience within SAE AS-2 relating to the development of a family of high speed interconnect standards, reference to specific standards and interconnect systems is minimized.
Standard

High Performance 1553 Research and Development

2016-10-21
CURRENT
AIR5683A
MIL-STD-1553 establishes requirements for digital command/response time division multiplexing (TDM) techniques on military vehicles, especially aircraft. The existing MIL-STD-1553 network operates at a bit rate of 1 Mbps and is limited by the protocol to a maximum data payload capacity of approximately 700 kilobits per second. The limited capacity of MIL-STD-1553 buses coupled with emerging data rich applications for avionics platforms plus the expense involved with changing or adding wires to thousands of aircraft in the fleet has driven the need for expanding the data carrying capacity of the existing MIL-STD-1553 infrastructure.
Standard

IEEE-1394b Interface Requirements for Military and Aerospace Vehicle Applications

2016-04-04
CURRENT
AS5643B
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.
Standard

Converged Aerospace Integrated Network (CAIN)

2015-04-14
WIP
AS6509
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.
Standard

Serial Hi-Rel Ring Network for Aerospace Applications (RingNet)

2014-10-08
CURRENT
AS1393
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.
Standard

10 Megabit/sec Network Configuration Digital Time Division Command/Response Multiplex Data Bus

2013-04-29
HISTORICAL
AS5652
This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration that is functionally similar to MIL-STD-1553B with Notice 2 but with a star topology and some deleted functionality. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.
X