Refine Your Search

Search Results

Viewing 1 to 19 of 19
Standard

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

2011-11-15
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

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

Handbook for the Digital Time Division Command/Response Multiplex Data Bus Test Plans

2011-11-15
HISTORICAL
AIR4295
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.
Standard

Handbook for the Digital Time Division Command/Response Multiplex Data Bus Test Plans

2016-10-21
CURRENT
AIR4295A
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.
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

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

Digital Time Division Command/Response Multiplex Data Bus

2011-11-15
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

HIGH SPEED RING BUS (HSRB) STANDARD

1988-08-29
HISTORICAL
AS4075
A fault tolerant, real time high speed data communication standard is defined based on a ring topology and the use of a Token passing access method with distributed control. The requirements for the HSRB standard have been driven predominantly, but not exclusively, by military applications. Particular attention has been given to the need for low message latency, deterministic message priority and comprehensive reconfiguration capabilities. This document contains a definition of the semantics and protocol including delimiters, tokens, message priority, addressing, error detection and recovery schemes; and is written to be independent of bit rate and media. Parameters related to particular media and bit rates are defined in separate documents, the AS4075 slash sheets.
Standard

High Speed Ring Bus (HSRB) Standard

2012-05-03
CURRENT
AS4075A
A fault tolerant, real time high speed data communication standard is defined based on a ring topology and the use of a Token passing access method with distributed control. The requirements for the HSRB standard have been driven predominantly, but not exclusively, by military applications. Particular attention has been given to the need for low message latency, deterministic message priority and comprehensive reconfiguration capabilities. This document contains a definition of the semantics and protocol including delimiters, tokens, message priority, addressing, error detection and recovery schemes; and is written to be independent of bit rate and media. Parameters related to particular media and bit rates are defined in separate documents, the AS4075 slash sheets.
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

2011-11-15
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

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

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