Search Results

This document was prepared by the SAE AS-1A2 Committee to establish techniques for verifying that Network Controllers (NCs), Network Terminals (NTs), switches, cables, and connectors comply with the physical layer requirements specified in AS5653B. Note that this verification document only verifies the specific requirements from AS5653B and does not verify all of the requirements invoked by documents that are referenced by AS5653B. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653B and in this verification document.

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.

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.

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 slash sheet specifies the operational parameters and characteristics of a particular implementation of the SAE Linear, Token Passing Bus (LTPB) Interface Unit. This slash sheet defines the following: a The physical media interface: This slash sheet specifies the characteristics of the electrical interface to the physical bus media. b The minimum and maximum timing requirements for operation of this implementation of the LTPB. c The data coding used to encode and decode the data for transmission. d The default values to be loaded into the timers of the LTPB interface at power-up prior to intervention by the host processor.

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

This Aerospace Standard (AS) defines the test requirements for determining that bus monitors meet the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.

This Aerospace Standard (AS) defines the test requirements for determining that bus monitors meet the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.

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

This test plan is broken into two major sections for the production testing of remote terminals: Electrical and Protocol.

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 test plan is broken into two major sections for the production testing of remote terminals: Electrical and Protocol.

This AIR is applicable to SSPCs, EMPCs, and hybrid power controllers. It covers the control, status, BIT, etc., interfaces, other than electrical power. For the purpose of this document, a power controller shall have, as a minimum, the following characteristics: a Power switching function b Control input c Overload protection d Status feedback To accomplish the goals set forth in the Foreword, the interfaces are first categorized by function. Next, examples of actual implementations are given.

This SAE Aerospace Standard (AS) has been prepared by the Ring Implementation Task Group of the SAE AS-2 Committee. It is intended as a companion document to the SAE AS4075 High Speed Ring Bus Standard. While the Standard is intended to provide as complete a description as possible of an HSRB implementation, certain parameters are system-dependent and evolutionary. This document contains those parameters. The text through Table 1 is intended to provide definitions and descriptions applicable to all applications. Table 2 contains specific parameter values for one or more implementations. This table will change as new systems are implemented or new HSRB speed options are defined.