Search Results

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.

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.

All electrical and electronic signals within an aircraft are potential candidates for multiplexing, although the determination of whether or not they are multiplexed is a matter for individual system consideration. However, those signals that are selected for multiplexing preferably should conform to the characteristics included in this AIR.

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.

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.

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.

This test plan consists of two major sections for the production testing of bus controllers: Electrical tests and Protocol tests.

This test plan consists of two major sections for the production testing of bus controllers: Electrical tests and Protocol tests.

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 S400 over copper medium over extended lengths. This document 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 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 refer to 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.

This SAE Aerospace Standard (AS) establishes guidelines for the use of 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 S400 over copper medium over extended lengths. This document 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 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.

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 test plan consists of two major sections for testing of MIL-STD-1553B data bus systems: Bus Network and System Integration Tests.

This test plan consists of two major sections for testing of MIL-STD-1553B data bus systems: Bus Network and System Integration Tests.

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.

This document establishes test plans/procedures for the AS5643/1 Slash Sheet. The AS5643/1 Slash Sheet establishes guidelines for the use of 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 S400 over copper medium over extended lengths.

This test plan is broken into three major sections for the testing of bus controllers Electrical, Protocol and Noise tests.

This test plan is broken into three major sections for the testing of bus controllers Electrical, Protocol and Noise tests.

This SAE Aerospace Standard (AS) contains a sample test plan for AS15531 or MIL-STD-1553B Remote Terminals (RT) that may serve several different purposes. This document is intended to be contractually binding when specifically called out in a specification, Statement of Work (SOW), or when required by a Data Item Description (DID). Any and all contractor changes, alterations, or testing deviations to this section shall be separately listed for easy review.