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 consists of two major sections for the production testing of bus controllers: Electrical tests and Protocol tests.

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 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 document is intended to explain, in detail, the rationale behind the features and functions of the AS4074, Linear, Token-passing, Bus (LTPB). The discussions also address the considerations which a system designer should take into account when designing a system using this bus. Other information can be found in these related documents: AIR4271 - Handbook of System Data Communication AS4290 - Validation Test Plan for AS4074

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 Handbook has been prepared by the Ring Implementation Task Group of the SAE AS-2 Committee, and is intended to support AS4075 by providing explanation of the standard itself and guidance on its use. The principal objective in the preparation of a standard is to provide a statement of operational and performance requirements, and an unambiguous definition of the functions to be realized in any implementation, primarily from the view point of interoperability. While efforts have been made within the AS4075 standard to provide a readable general description of the HSRB, detailed explanations, rationale and guidance to the use are incompatible with the purpose and, indeed, the format of a standard. Accordingly, this Handbook contains a paragraph-by-paragraph explanation of the main sections of the standard, and a discussion of application and implementation issues.

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.

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.

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.

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

This test plan consists of two major sections for the production testing of bus controllers: Electrical tests and Protocol tests.

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.

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.

This document is intended to explain, in detail, the rationale behind the features and functions of the AS4074, Linear, Token-passing, Bus (LTPB). The discussions also address the considerations which a system designer should take into account when designing a system using this bus. Other information can be found in these related documents:

This Handbook has been prepared by the Ring Implementation Task Group of the SAE AS-2 Committee, and is intended to support AS4075 by providing explanation of the standard itself and guidance on its use. The principal objective in the preparation of a standard is to provide a statement of operational and performance requirements, and an unambiguous definition of the functions to be realized in any implementation, primarily from the view point of interoperability. While efforts have been made within the AS4075 standard to provide a readable general description of the HSRB, detailed explanations, rationale and guidance to the use are incompatible with the purpose and, indeed, the format of a standard. Accordingly, this Handbook contains a paragraph-by-paragraph explanation of the main sections of the standard, and a discussion of application and implementation issues.

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.