Search Results

Define IEEE-1394 Beta PHY Enhancements that drive faster 1394 port connects and increased robustness. These enhancements include Detect loss of descrambler synchronization, Fast-ReTrain, Fast Power-on Re-connect, Fast Connection Tone Debounce and Programmable invalidCount.

This SAE Aerospace Standard (AS) establishes guidelines for the use of IEEE-1394-2008 Beta (formerly 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 S200 over copper medium over extended lengths. This document contains extensions/restrictions to AS5643/1 to support S200 data rate. 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.

This document establishes test plans/procedures for the AS5643/1 Slash Sheet. The AS5643/1 Slash Sheet establishes guidelines for the use of IEEE Std 1394-2008 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.

Develop a profile of the TSN set of standards that is applicable to Avionics use cases, including AS6509 CAIN

This Handbook is intended to accompany or incorporate AS5643, AS5643/1, AS5657, AS5706, and ARD5708. In addition, full understanding of this Handbook also requires knowledge of IEEE-1394-1995, IEEE-1394a, and IEEE-1394b standards. This Handbook contains detailed explanations and architecture analysis on AS5643, bus timing and scheduling considerations, system redundancy design considerations, suggestions on AS5643-based system configurations, cable selection guidance, and lessons learned on failure modes.

This standard defines a broadband time division command/response multiplex data bus that co-exists and permits concurrent operation with a MIL-STD-1553 Data Bus and MIL-STD-1760 Appendix C. This standard allows utilization of legacy MIL-STD-1553 wiring and bus coupling.

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 ARP establishes guidelines for the use of IEEE-802.3 as a data bus network in military and aerospace vehicles. It encompasses the data cable and its connections for a system utilizing 10Base-T, 100Base-T, 1000BASE-T and 10GBASE-T over copper medium dependent interfaces (MDI). This document contains extensions/restrictions to “off-the-shelf” IEEE-802.3 standards, and assumes that the reader already has a working knowledge of IEEE-802.3.

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.