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 test plan is broken into three major sections for the testing of bus controllers Electrical, Protocol and Noise 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 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 the production testing of bus controllers: Electrical tests and Protocol 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.

This test plan defines the requirements of data bus components which comply with the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.

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

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

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

The emphasis in this standard is the development of data word and message formats for AS15531 or MIL-STD-1553 data bus applications. This standard is intended as a guide for the designer to identify standard data words and messages for use in avionics systems and subsystems. These standard words and messages, as well as the documentation format for interface control document (ICD) sheets, provide the basis for defining 15531/1553 systems. Also provided in this standard is the method for developing additional data word formats and messages that may be required by a particular system but are not covered by the formats provided herein. It is essential that any new word formats or message formats that are developed for a 15531/1553 application follow the fundamental guidelines established in this standard in order to ease future standardization of these words and messages. The standard word formats presented represent a composite result of studies conducted by the U.S.

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.

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

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