Search Results

This document, the JAUS Compliance and Interoperability Policy (ARP6012), recommends an approach to documenting the complete interface of an unmanned system or component in regard to the application of the standard set. While non-SAE AS-4 JAUS documents are referenced in this ARP they are not within the scope of this document and should be viewed as examples only.

This document, the JAUS Compliance and Interoperability Policy (ARP6012), recommends an approach to documenting the complete interface of an unmanned system or component in regard to the application of the standard set. While non-SAE AS-4 JAUS documents are referenced in this ARP they are not within the scope of this document and should be viewed as examples only.

This document defines a set of standard application layer interfaces called JAUS Core Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Core Services represent the infrastructure commonly found across all domains and types of unmanned systems.

This document defines a set of standard application layer1 interfaces called JAUS Core Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Core Services represent the infrastructure commonly found across all domains and types of unmanned systems.

This document defines a set of standard application layer interfaces called JAUS Core Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Core Services represent the infrastructure commonly found across all domains and types of unmanned systems.

This document defines a set of standard application layer interfaces called JAUS HMI Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The HMI Services represent the platform-independent Human Machine Interface (HMI) capabilities commonly found across all domains and types of unmanned systems. Five services are defined in this document: Drawing Pointing Device Keyboard Digital Control Analog Control Each service is described by a JAUS Service Definition (JSD) which specifies the message set and protocol required for compliance. Each JSD is fully compliant with the JAUS Service Interface Definition Language (JSIDL) [AS5684].

The purpose of this SAE Aerospace Information Report (AIR) is two-fold: to inform the reader of the extent of effort that went into the development of the Joint Architecture for Unmanned Systems (JAUS); and to capture for posterity the domain analysis that provides the underpinnings for the work by the AS-4 Committee (Unmanned Systems).

The purpose of this SAE Aerospace Information Report (AIR) is two-fold: to inform the reader of the extent of effort that went into the development of the Joint Architecture for Unmanned Systems (JAUS); and to capture for posterity the domain analysis that provides the underpinnings for the work by the AS-4 Committee (Unmanned Systems).

This document defines a set of standard application layer interfaces called JAUS Mission Spooling Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Mission Spooling Services represent the platform-independent capabilities commonly found across all domains and types of unmanned systems. At present, 1 service is defined in this document (more services are planned for future versions of this document): Mission Spooler: Stores mission plans, coordinates mission plans, and parcels out elements of the mission plan for execution The Mission Spooler service is described by a JAUS Service Definition (JSD) which specifies the message set and protocol required for compliance. The JSD is fully compliant with the JAUS Service Interface Definition Language [JSIDL].

The SAE Aerospace Information Report AIR5315 – Generic Open Architecture (GOA) defines “a framework to identify interface classes for applying open systems to the design of a specific hardware/software system.” [sae] JAUS Service (Interface) Definition Language defines an XML schema for the interface definition of services at the Class 4L, or Application Layer, and Class 3L, or System Services Layer, of the Generic Open Architecture stack (see Figure 1). The specification of JAUS services shall be defined according to the JAUS Service (Interface) Definition Language document.

The SAE Aerospace Information Report AIR5315 – Generic Open Architecture (GOA) defines “a framework to identify interface classes for applying open systems to the design of a specific hardware/software system.” [sae] JAUS Service (Interface) Definition Language defines an XML schema for the interface definition of services at the Class 4L, or Application Layer, and Class 3L, or System Services Layer, of the Generic Open Architecture stack (See Figure 1 below). The specification of JAUS services shall be defined according to the JAUS Service (Interface) Definition Language document.

The SAE Aerospace Information Report AIR5315 – Generic Open Architecture (GOA) defines “a framework to identify interface classes for applying open systems to the design of a specific hardware/software system.” [sae]JAUS Service (Interface) Definition Language defines an XML schema for the interface definition of services at the Class 4L, or Application Layer, and Class 3L, or System Services Layer, of the Generic Open Architecture stack (See Figure 1 below). The specification of JAUS services shall be defined according to the JAUS Service (Interface) Definition Language document.