Refine Your Search

Search Results

Viewing 1 to 14 of 14
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

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

1996-04-01
HISTORICAL
AIR4886
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

MODULAR AVIONICS BACKPLANE FUNCTIONAL REQUIREMENTS AND CONSENSUS ITEMS (MABFRACI)

1996-11-01
HISTORICAL
AIR4980
The original purpose of this document was to establish interface requirements for modular avionics backplanes to be prototyped up to 1995. The document was issued as ARD50011 in September 1992. It is being reissued as an SAE Aerospace Information Report (AIR) in order to: a Preserve the requirements for more than 2 years b Support design of retrofits and avionics systems to be fielded in the years 1995 to 2000 c Provide a baseline for updating the requirements of future integrated systems These requirements were and are intended to promote standardization of modular avionic backplane interfaces. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms.
Standard

Modular Avionics Backplane Functional Requirements and Consensus Items (MABFRACI)

2012-05-03
CURRENT
AIR4980A
The original purpose of this document was to establish interface requirements for modular avionics backplanes to be prototyped up to 1995. The document was issued as ARD50011 in September 1992. It is being reissued as an SAE Aerospace Information Report (AIR) in order to: a Preserve the requirements for more than 2 years b Support design of retrofits and avionics systems to be fielded in the years 1995 to 2000 c Provide a baseline for updating the requirements of future integrated systems These requirements were and are intended to promote standardization of modular avionic backplane interfaces. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms.
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

Handbook of System Data Communications

1989-11-01
HISTORICAL
AIR4271
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

High Performance 1553 Research and Development

2007-02-21
HISTORICAL
AIR5683
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

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

Type E-1 Electrical Media Interface Characteristics

2004-10-14
HISTORICAL
AS4074/3A
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.
Standard

Linear Token Passing Multiplex Data Bus

2004-10-14
HISTORICAL
AS4074A
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

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

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

2005-12-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