Refine Your Search

Topic

Search Results

Standard

Validation Methods for MIL-STD-1760C Aircraft Station Interfaces

2004-06-17
HISTORICAL
AS47642
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760C. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies. For validation of aircraft designed to MIL-STD-1760B Notice 3 AS47641 Issued 1999-08 applies.
Standard

Validation Methods for MIL-STD-1760C Aircraft Station Interfaces

2012-07-12
HISTORICAL
AS47642A
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760C. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies. For validation of aircraft designed to MIL-STD-1760B Notice 3 AS47641 Issued 1999-08 applies.
Standard

Validation Methods for MIL-STD-1760C Aircraft Station Interfaces

2017-06-28
CURRENT
AS47642B
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760C. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies. For validation of aircraft designed to MIL-STD-1760B Notice 3 AS47641 Issued 1999-08 applies.
Standard

Validation Methods for MIL-STD-1760B Aircraft Station Interfaces

2012-07-12
HISTORICAL
AS47641
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760B Notice 3. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies.
Standard

Validation Methods for MIL-STD-1760B Aircraft Station Interfaces

2017-06-28
CURRENT
AS47641A
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760B Notice 3. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies.
Standard

Multiplex Data Bus Networks for MIL-STD-1760 Stores

2012-08-22
CURRENT
AIR4013C
This SAE Aerospace Information Report (AIR) will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.
Standard

Multiplex Data Bus Networks for MIL-STD-1760 Stores

2005-09-29
HISTORICAL
AIR4013B
This SAE Aerospace Information Report (AIR) will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.
Standard

Multiplex Data Bus Networks for MIL-STD-1760 Stores

1998-01-01
HISTORICAL
AIR4013A
This SAE Aerospace Information Report (AIR) will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.
Standard

MULTIPLEX DATA BUS NETWORKS FOR MIL-STD-1760A STORES

2011-08-10
HISTORICAL
AIR4013
This document will examine network aspects of open and shorted stubs, line reflections and bus loading due to network changes. Single network level is assumed, that is, no carriage store hierarchical levels. However, two passive network coupling variants called "branched bus" and "branched stub" will be introduced that possibly could be used in a stores management network. This report assumes familiarity with MIL-STD-1553B.
Standard

Generic Aircraft-Store Interface Framework (GASIF)

2003-06-06
HISTORICAL
AIR5532
This SAE Aerospace Information Report (AIR) defines a Generic Aircraft-Store Interface Framework (GASIF). This is a common framework for modeling and specifying aircraft-store logical interfaces. GASIF complies with the OSI Basic Reference Model (ITU-T Rec. X.200 | ISO/IEC 7498-1) in that it describes operations and mechanisms which are assignable to layers as specified in the OSI Basic Reference Model. This AIR provides a mapping of the Interface Standard for Aircraft-store Electrical Interconnection System (AEIS), MIL-STD-1760, in Appendix C.
Standard

Generic Aircraft-Store Interface Framework (GASIF)

2012-08-22
CURRENT
AIR5532A
This SAE Aerospace Information Report (AIR) defines a Generic Aircraft-Store Interface Framework (GASIF). This is a common framework for modeling and specifying aircraft-store logical interfaces. GASIF complies with the OSI Basic Reference Model (ITU-T Rec. X.200 | ISO/IEC 7498-1) in that it describes operations and mechanisms which are assignable to layers as specified in the OSI Basic Reference Model. This AIR provides a mapping of the Interface Standard for Aircraft-store Electrical Interconnection System (AEIS), MIL-STD-1760, in Appendix C.
Standard

Standard Electrical and Logical Interface for Airborne Fuzing Systems

2010-02-11
HISTORICAL
AS5716
This interface standard applies to fuzes/fuzing systems (referred to as fuzing system hereafter) in airborne weapons that use a MIL-STD-1760 interface. It defines the powers, the discrete signals and the serial data interface for the communications at the interface between the fuzing system and the remainder of the weapon, including the weapon control unit, for Class 1 interfaces. Future issues of the standard will provide for additional fuzing system related functionality defined as Class 2 and Class 3 interfaces. For future issues of this standard, the connector definition is contained in AS5680. This standard does not impose any safety requirements and does not supersede or replace any existing applicable safety standards.
Standard

Standard Electrical and Logical Interface for Airborne Fuzing Systems

2012-12-03
CURRENT
AS5716A
This interface standard applies to fuzes/fuzing systems (referred to as fuzing system hereafter) in airborne weapons that use a MIL-STD-1760 type interface. It defines the powers, the discrete signals and the serial data interface for the communications at the interface between the fuzing system and the remainder of the weapon, including the weapon control unit. The Class 1 interface is an electrical only interface that facilitates use of MIL-STD-1760 type platform store interfaces for the fuze to monitor intentional release and defines the fuze interface bus communications protocol to allow sending and receiving data from fuzing systems. Class 2 interfaces add a defined connector and additional interfaces to facilitate the exchange of compatible fuzing systems. Class 3 interfaces add further interface definitions to facilitate the exchange of AS5680A compatible fuzing systems components.
Standard

Considerations for Safe Store Operation on Manned and Unmanned Vehicles

2012-05-03
HISTORICAL
AIR6027
The information presented in this AIR is intended to provide designers of armed unmanned systems with guidelines that may be applied to ensure safe integration and operation of weapons on unmanned platforms. The guidelines have been developed from experiences gained in the design and operation of weapons on manned aircraft that have been accepted by relevant safety authorities in the USA and Europe and proven effective over many years. Whilst the guidelines have been developed from experience with aircraft operations, the concepts are considered equally applicable to non-aircraft systems, such as those used on the surface or undersea environments. This document does not attempt to define or describe a comprehensive safety program for unmanned systems. System Safety is a system characteristic and a non-functional requirement. It has to be addressed at each level of system design, system integration and during each phase of system operation.
X