Search Results

This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760 Revision E.

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.

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.

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.

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.

This document establishes techniques for validating that an aircraft station complies with the interface requirements delineated in MIL-STD-1760.

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.

This document was prepared by the SAE AS-1B1 IMM Task Group to explain and document background information and design decisions made during the development of AS5726. This handbook is published separately to preserve information that is not required or provided in the AS5726 but may be important to system designers to ensure interoperability between the Micro Munition Host and Micro Munition. As a handbook, it cannot be invoked as a requirement in a contract. The structure and numbering of this document mirrors that of AS5726 for the convenience of readers. Headings such as “Requirements” in this handbook should not be interpreted as invoking requirements.

This standard only defines interconnect, electrical and logical (functional) requirements for the interface between a Micro Munition and the Host. The physical and mechanical interface between the Micro Munition and Host is undefined. Individual programs will define the relevant requirements for physical and mechanical interfaces in the Interface Control Document (ICD) or system specifications. It is acknowledged that this does not guarantee full interoperability of Interface for Micro Munitions (IMM) interfaces until further standardization is achieved.

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.

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.

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.

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.

CLARA identifies four functions: Data Space Generator, Truth Data Generator, Coefficient Generator, and Reconstructor. Together these four functions standardize the solution to the LAR problem.

CLARA identifies four functions: Data Space Generator, Truth Data Generator, Coefficient Generator, and Reconstructor. Together these four functions standardize the solution to the LAR problem. This ICD defines the logical interfaces of the four functions.

CLARA identifies four functions: Data Space Generator, Truth Data Generator, Coefficient Generator, and Reconstructor. Together these four functions standardize the solution to the LAR problem. This ICD defines the logical interfaces of the four functions.

This document was developed by the SAE AS-1B5 CLARA Task Group to explain and document background information and decisions with associated rationale made in development of the CLARA Interface Control Document (ICD), AIR5682. This rationale document is published separately to preserve information that is not required or provided in the ICD but may be important to users.

This document was developed by the SAE AS-1B5 CLARA Task Group to explain and document background information and decisions with associated rationale made in development of the CLARA Interface Control Document (ICD), AIR5682. This rationale document is published separately to preserve information that is not required or provided in the ICD but may be important to users.

This document specifies the CLARA interfaces of the CLAR Truth Data Generator as shown in Figure 1. The solid bold arrows are defined in Table 1 and Table 2. The dashed arrows from the CLAR Coefficient Generator and Truth Database to the CLAR Data Space Generator indicate a feedback loop and are defined in the CLAR Data Space Generator ICD (Reference 1). The dashed arrow from the Truth Database to the CLAR Coefficient Generator is defined in the CLAR Coefficient Generator ICD (Reference 2). The objective for the CLAR Truth Data Generator is to produce impact data sets to be used in the CLAR Coefficient Generator first to score and form LAR boundaries, and then to generate coefficients. A model of the weapon system that predicts weapon delivery performance to a predefined accuracy is to be used for this purpose. The model can be the Six-Degree-Of-Freedom (6DOF) equations of motion or another mathematical representation that meets the objective for the weapon system LAR.

This document specifies the CLARA interfaces of the CLAR Truth Data Generator as shown in Figure 1. The solid bold arrows are defined in Table 1 and Table 2. The dashed arrows from the CLAR Coefficient Generator and Truth Database to the CLAR Data Space Generator indicate a feedback loop and are defined in the CLAR Data Space Generator ICD (Reference 1). The dashed arrow from the Truth Database to the CLAR Coefficient Generator is defined in the CLAR Coefficient Generator ICD (Reference 2). The objective for the CLAR Truth Data Generator is to produce impact data sets to be used in the CLAR Coefficient Generator first to score and form LAR boundaries, and then to generate coefficients. A model of the weapon system that predicts weapon delivery performance to a predefined accuracy is to be used for this purpose. The model can be the Six-Degree-Of-Freedom (6DOF) equations of motion or another mathematical representation that meets the objective for the weapon system LAR.