Refine Your Search

Date

Date

Topic

Topic

Oxygen Exhaust emissions Technical review AS-1A Avionic Networks Committee Materials Tests and Testing

Search Results

Viewing 1 to 20 of 46
123Next >Last >>
Sort by published
Standard

Verification Methods for AS5653 Network Terminal
2019-04-24
CURRENT
AS6088
This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Terminal (NT) complies with the NT requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all the requirements invoked by documents that are referenced by AS5653. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653 and in this verification document.
Standard

Verification Methods for AS5653 Network Controller, Network Terminal, and Switch Physical Layer
2018-08-13
CURRENT
AS6260
This document was prepared by the SAE AS-1A2 Committee to establish techniques for verifying that Network Controllers (NCs), Network Terminals (NTs), switches, cables, and connectors comply with the physical layer requirements specified in AS5653B. Note that this verification document only verifies the specific requirements from AS5653B and does not verify all of the requirements invoked by documents that are referenced by AS5653B. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653B and in this verification document.
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

Verification Methods for AS5653 Network Controller
2017-10-11
CURRENT
AS6089
This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Controller (NC) complies with the NC requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all of the requirements invoked by documents that are referenced by AS5653. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653 and in this verification document.
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

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

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

Type F-2 Fiber Optic Media Interface Characteristics
2016-10-21
CURRENT
AS4074/2B
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.
Standard

Type F-1 Fiber Optic Media Interface Characteristics
2016-10-21
CURRENT
AS4074/1B
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.
Standard

IEEE-1394b Interface Requirements for Military and Aerospace Vehicle Applications
2016-04-04
CURRENT
AS5643B
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.
Standard

High Speed Network for MIL-STD-1760
2014-01-03
CURRENT
AS5653B
AS5653 may be applied to Air Vehicles and Stores implementing MIL-STD-1760 Interface Standard for Aircraft/Store Electrical Interconnection System.
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.
123Next >Last >>
X