Refine Your Search

Search Results

Standard

POWER CONTROLLERS: SIGNAL INTERFACE APPLICATIONS AND CONSIDERATIONS

1991-09-03
HISTORICAL
AIR4272
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.
Standard

Digital Time Division Command/Response Multiplex Data Bus

1995-11-01
HISTORICAL
AS15531
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

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

Validation Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Remote Terminals

2017-08-10
CURRENT
AS4111A
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.
Standard

Validation Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Remote Terminals

1998-10-01
HISTORICAL
AS4111
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.
Standard

Verification Methods for AS5653 Network Controller, Network Terminal, and Switch Physical Layer

2018-08-13
CURRENT
AS6260
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.
Standard

High Speed Network for MIL-STD-1760

2008-01-16
HISTORICAL
AS5653
AS5653 may be applied to Air Vehicles and Stores implementing MIL-STD-1760 Interface Standard for Aircraft/Store Electrical Interconnection System.
Standard

High Speed Network for MIL-STD-1760

2012-07-25
HISTORICAL
AS5653A
AS5653 may be applied to Air Vehicles and Stores implementing MIL-STD-1760 Interface Standard for Aircraft/Store Electrical Interconnection System.
Standard

High Speed Network for MIL-STD-1760

2014-01-03
CURRENT
AS5653B
AS5653 may be applied to Air Vehicles and Stores implementing MIL-STD-1760 Interface Standard for Aircraft/Store Electrical Interconnection System.
Standard

S400 Copper Media Interface Characteristics Over Extended Distances

2004-12-30
CURRENT
AS5643/1
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.
Standard

OPTICAL IMPLEMENTATION RELATING TO THE HIGH SPEED RING BUS (HSRB) STANDARD

1995-01-01
HISTORICAL
AS4075/1
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.
Standard

Optical Implementation Relating to the High Speed Ring Bus (HSRB) Standard

2012-05-03
CURRENT
AS4075/1A
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.
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.
X