Search NASA⌕ Search

SEARCH · Search NASA

Results for “autonomy software”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10

An Overview of Distributed Spacecraft Autonomy at NASA Ames

Autonomous decision-making significantly increases mission effectiveness by mitigating the effects of communication constraints, like latency and bandwidth, and mission complexity on multi-spacecraft operations. To advance the state of the art in autonomous Distributed Space Systems (DSS), the Distributed Spacecraft Autonomy (DSA) team at NASA's Ames Research Center is developing within five relevant technical areas: distributed resource and task management, reactive operations, system modeling and simulation, human-swarm interaction, and ad hoc network communications. DSA is maturing these technologies - critical for future large autonomous DSS - from concept to launch via simulation studies and orbital deployments. A 100-node heterogenous Processor-in-the-Loop (PiL) testbed aids distributed autonomy capability development and verification of multi-spacecraft missions. The DSA software payload deployed to the D-Orbit SCV-004 spacecraft demonstrates multi-agent reconfigurability and reliability as part of an ESA-sponsored in-orbit technology demonstration. Finally, DSA's primary flight mission showcases collaborative resource allocation for multipoint science data collection with four small spacecraft as a payload on NASA's Starling 1.0 satellites.

Caleb Ashmore Adams↗

Virtual Satellite

Virtual Satellite (VirtualSat) is a computer program that creates an environment that facilitates the development, verification, and validation of flight software for a single spacecraft or for multiple spacecraft flying in formation. In this environment, enhanced functionality and autonomy of navigation, guidance, and control systems of a spacecraft are provided by a virtual satellite that is, a computational model that simulates the dynamic behavior of the spacecraft. Within this environment, it is possible to execute any associated software, the development of which could benefit from knowledge of, and possible interaction (typically, exchange of data) with, the virtual satellite. Examples of associated software include programs for simulating spacecraft power and thermal- management systems. This environment is independent of the flight hardware that will eventually host the flight software, making it possible to develop the software simultaneously with, or even before, the hardware is delivered. Optionally, by use of interfaces included in VirtualSat, hardware can be used instead of simulated. The flight software, coded in the C or C++ programming language, is compilable and loadable into VirtualSat without any special modifications. Thus, VirtualSat can serve as a relatively inexpensive software test-bed for development test, integration, and post-launch maintenance of spacecraft flight software.

Hammrs, Stephan R.↗

Avionics Architectures for Exploration: Ongoing Efforts in Human Spaceflight

The field of Avionics is advancing far more rapidly in terrestrial applications than in spaceflight applications. Spaceflight Avionics are not keeping pace with expectations set by terrestrial experience, nor are they keeping pace with the need for increasingly complex automation and crew interfaces as we move beyond Low Earth Orbit. NASA must take advantage of the strides being made by both space-related and terrestrial industries to drive our development and sustaining costs down. This paper describes ongoing efforts by the Avionics Architectures for Exploration (AAE) project chartered by NASA's Advanced Exploration Systems (AES) Program to evaluate new avionic architectures and technologies, provide objective comparisons of them, and mature selected technologies for flight and for use by other AES projects. The AAE project team includes members from most NASA centers, and from industry. It is our intent to develop a common core avionic system that has standard capabilities and interfaces, and contains the basic elements and functionality needed for any spacecraft. This common core will be scalable and tailored to specific missions. It will incorporate hardware and software from multiple vendors, and be upgradeable in order to infuse incremental capabilities and new technologies. It will maximize the use of reconfigurable open source software (e.g., Goddard Space Flight Center's (GSFC's) Core Flight Software (CFS)). Our long-term focus is on improving functionality, reliability, and autonomy, while reducing size, weight, and power. Where possible, we will leverage terrestrial commercial capabilities to drive down development and sustaining costs. We will select promising technologies for evaluation, compare them in an objective manner, and mature them to be available for future programs. The remainder of this paper describes our approach, technical areas of emphasis, integrated test experience and results as of mid-2014, and future plans. As a part of the AES Program, we are encouraged to set aggressive goals and fall short if necessary, rather than to set our sights too low. We are also asked to emphasize providing our personnel with hands-on experience in development, integration, and testing. That we have embraced both of these philosophies will be evident in the descriptions below.

Goforth, Montgomery B.↗

System Autonomy for Space Traffic Management

This paper proposes an initial architecture for a Space Traffic Management (STM) system, based on openApplication Programming Interfaces (APIs) and drawing on previous work by the NASA Ames Research Center (ARC) to develop an architecture for low-altitude Unmanned Aerial System Traffic Management (UTM). The authors explore how autonomy could be used to enhance an STM system, and how constraints inherent in STM complicate and challenge certain applications of autonomy. We conceptually explore how autonomy could be used within an STM architecture, with multiple non-authoritative catalogs of resident space objects, and to determine which oftwo conjuncting spacecraft moves. NASA ARC is developing a software research environment for STM, along with a physical laboratory and visualization space. We invite STM stakeholders to collaborate in our infrastructure, to help inform the design of the proposed STM architecture, and to participate in the refinement and validation of its concept of operations using the software research platform.

space situational awareness↗

Implementing Artificial Thinking Autonomy with Model-Based System Engineering

Complex autonomous systems capable of successfully operating independently under ‘known unknowns’ and harsh conditions require paradigm innovation in modern development strategies. In the field of autonomy, developing a system-of-systems which can ostensibly think for itself in the face of ‘unknown unknowns’ is still a field of ongoing research. Maturing the systems architecting and modeling methodologies for developing henceforth named Thinking Autonomous Systems, which are verified with digital mission simulation, can potentially usher in the next generation of artificial intelligence for space exploration. The concept presented in this paper incorporates multiple Model-Based Systems Engineering and simulation methodologies combined as a new paradigm to design a novel, biomimetic thinking autonomy strategy. Anachronistic concepts from classical Kantian philosophy will be leveraged to inspire architectural designs that could be used for complex distributed systems in deep space. To accomplish this, digital transformation of a document-based implementation plan for Thinking Autonomous Systems, generated by experienced NASA software engineers, is implemented for NASA’s Platform for Autonomous Systems by creating descriptive and executable software models in SysML to prototype real-time operating capabilities. This conceptual implementation has been developed by incorporating model-based digital simulations to theorize how a cyberphysical thinking system would achieve specific strategies without crew reliance, while simultaneously being resilient to all operating conditions and remaining functional when devoid of ground communication. Additionally, ensuring that an autonomous system framework is an ethical Artificial Intelligence requires careful consideration of system behavior and accountability, human factors for teaming with a thinking autonomous system, and comparison to other modern approaches used for implementing true autonomy. This paper presents the first steps in formalizing the metacognition required for instantiating a truly Thinking Autonomous System; the approach described symphonizes autonomy characteristics from classical philosophical into a unified software architecture describing human thought. In the future, the foundational models described in this paper can be further leveraged to help advance research into thinking autonomy requirements for future deep space missions as well as for current near-term applications, i.e., living aboard crewed spacecraft like a NASA Gateway cislunar habitat.

Artificial Thought↗

User Needs and Advances in Space Wireless Sensing and Communications

Decades of space exploration and technology trends for future missions show the need for new approaches in space/planetary sensor networks, observatories, internetworking, and communications/data delivery to Earth. The User Needs to be discussed in this talk includes interviews with several scientists and reviews of mission concepts for the next generation of sensors, observatories, and planetary surface missions. These observatories, sensors are envisioned to operate in extreme environments, with advanced autonomy, whereby sometimes communication to Earth is intermittent and delayed. These sensor nodes require software defined networking capabilities in order to learn and adapt to the environment, collect science data, internetwork, and communicate. Also, some user cases require the level of intelligence to manage network functions (either as a host), mobility, security, and interface data to the physical radio/optical layer. For instance, on a planetary surface, autonomous sensor nodes would create their own ad-hoc network, with some nodes handling communication capabilities between the wireless sensor networks and orbiting relay satellites. A section of this talk will cover the advances in space communication and internetworking to support future space missions. NASA's Space Communications and Navigation (SCaN) program continues to evolve with the development of optical communication, a new vision of the integrated network architecture with more capabilities, and the adoption of CCSDS space internetworking protocols. Advances in wireless communications hardware and electronics have enabled software defined networking (DVB-S2, VCM, ACM, DTN, Ad hoc, etc.) protocols for improved wireless communication and network management. Developing technologies to fulfil these user needs for wireless communications and adoption of standardized communication/internetworking protocols will be a huge benefit to future planetary missions, space observatories, and manned missions to other planets.

Kegege, Obadiah↗

The TSTAR Autonomy Test Tool

The new breed of autonomous goal-driven spacecraft contain much more onboard capability than their syquence-driven predecessors, demanding corresponding advances in software verification techniques. Although autonomous systems are deterministic, they are hightly sensitive to the environment, such that the response of a system in certain contexts must be explored in detail in order to prove confidence in both the design and implementaiton.

Autonomy↗

Apex Reference Manual 3.0 Beta

Apex is a toolkit for constructing software that behaves intelligently and responsively in demanding task environments. Reflecting its origin at NASA where Apex continues to be developed, current applications include: a) Providing autonomous mission management and tactical control capabilities for unmanned aerial vehicles including an autonomous surveillance helicopter and a simulation prototype of an unmanned fixed-wing aircraft to be used for wildfire mapping; b) Simulating human air traffic controllers, pilots and astronauts to help predict how people might respond to changes in equipment or procedures; and c) Predicting the precise duration and sequence of routine human behaviors based on a human-computer interaction engineering technique called CPM-GOMS. Among Apex s components are a set of implemented reasoning services, such as those for reactive planning and temporal pattern recognition; a software architecture that embeds and integrates these services and allows additional reasoning elements to be added as extensions; a formal language for specifying agent knowledge; a simulation environment to facilitate prototyping and analysis; and Sherpa, a set of tools for visualizing autonomy logic and runtime behavior. In combination, these are meant to provide a flexible and usable framework for creating, testing, and deploying intelligent agent software. Overall, our goal in developing Apex is to lower economic barriers to developing intelligent software agents. New ideas about how to extend or modify the system are evaluated in terms of their impact in reducing the time, expertise, and inventiveness required to build and maintain applications. For example, potential enhancements to the AI reasoning capabilities in the system are reviewed not only for usefulness and distinctiveness, but also for their impact on the readability and general usability of Apex s behavior representation language (PDL) and on the transparency of resulting behavior. A second central part of our approach is to iteratively refine Apex based on lessons learned from as diverse a set of applications as possible. Many applications have been developed by users outside the core development team including engineers, researchers, and students. Usability is thus a central concern for every aspect of Apex visible to a user, including PDL, Sherpa, the Apex installation process, APIs, and user documentation. Apex users vary in their areas of expertise and in their familiarity with autonomy technology. Focusing on usability, a development philosophy summarized by the project motto "Usable Autonomy," has been important part of enabling diverse users to employ Apex successfully and to provide feedback needed to guide iterative, user-centered refinement.

Freed, Michael A.↗

Future Vision for Autonomous Ocean Observations

Autonomous platforms already make observations over a wide range of temporal and spatial scales, measuring salinity, temperature, nitrate, pressure, oxygen, biomass; and many other parameters. However, the observations are not comprehensive. Future autonomous systems need to be more affordable, more modular, more capable and easier to operate. Creative new types of platforms and new compact, low power, calibrated and stable sensors are under development to expand autonomous observations. Communications and recharging need bandwidth and power which can be supplied by standardized docking stations. In situ power generation will also extend endurance for many types of autonomous platforms, particularly autonomous surface vehicles. Standardized communications will improve ease of use, interoperability, and enable coordinated behaviors. Improved autonomy and communications will enable adaptive networks of autonomous platforms. Improvements in autonomy will have three aspects: hardware, control, and operations. As sensors and platforms have more onboard processing capability and energy capacity, more measurements become possible. Control systems and software will have the capability to address more complex states and sophisticated reactions to sensor inputs, which allows the platform to handle a wider variety of circumstances without direct operator control. Operational autonomy is increased by reducing operating costs. To maximize the potential of autonomous observations new standards and best practices are needed. In some applications, focus on common platforms and volume purchases could lead to significant cost reductions. Cost reductions could enable order-of-magnitude increases in platform operations and increase sampling resolution for a given level of investment. Energy harvesting technologies should be integral to the system design, for sensors, platforms, vehicles, and docking stations. Connections are needed between the marine energy and ocean observing communities to coordinate among funding sources, researchers, and end users. Regional teams should work with global organizations such as IOC/GOOS in governance development. International networks such as EGO for the emerging glider operations should also provide a forum for addressing governance. Networks of multiple vehicles can improve operational efficiencies and transform operational patterns. There is a need to develop operational architectures at regional and global scales to provide a backbone for active networking of autonomous platforms.

47 OTHER INSTRUMENTATION↗

Autonomous dexterous end-effectors for space robotics

The development of a knowledge-based controller is summarized for the Belgrade/USC robot hand, a five-fingered end effector, designed for maximum autonomy. The biological principles of the hand and its architecture are presented. The conceptual and software aspects of the grasp selection system are discussed, including both the effects of the geometry of the target object and the task to be performed. Some current research issues are presented.

Bekey, George A.↗

SHINE Virtual Machine Model for In-flight Updates of Critical Mission Software

This software is a new target for the Spacecraft Health Inference Engine (SHINE) knowledge base that compiles a knowledge base to a language called Tiny C - an interpreted version of C that can be embedded on flight processors. This new target allows portions of a running SHINE knowledge base to be updated on a "live" system without needing to halt and restart the containing SHINE application. This enhancement will directly provide this capability without the risk of software validation problems and can also enable complete integration of BEAM and SHINE into a single application. This innovation enables SHINE deployment in domains where autonomy is used during flight-critical applications that require updates. This capability eliminates the need for halting the application and performing potentially serious total system uploads before resuming the application with the loss of system integrity. This software enables additional applications at JPL (microsensors, embedded mission hardware) and increases the marketability of these applications outside of JPL.

Plesea, Lucian↗

A Simulation Architecture for Air Traffic Over Urban Environments Supporting Autonomy Research in Advanced Air Mobility

NASA is conducting investigations into Advanced Air Mobility (AAM) concepts, aircraft, and operations. One of the most challenging scenarios for AAM will be enabling safe routine access into densely populated urban centers. To address challenges in the urban environment, a moderately high-fidelity simulation capability is needed to investigate AAM flight operations over a regional area for the development and evaluation of autonomy technologies. This paper describes a system to simulate flight operations around regions such as the San Francisco-Oakland Bay area at a moderately-high scale (10's-100's of flights) that incorporates detailed vehicle models and control necessary to support research in airborne autonomy. The flight vehicle utilizes NASA AAM concept vehicle dynamics integrated with a custom flight management system and flight control system to accurately simulate all phases of flight. Glass cockpit displays have been developed for monitoring aircraft operation over a detailed simulated urban environment. Simulation models have been integrated to simulate air and ground-based sensors, such as radar and LIDAR. The commercial X-Plane software package is used as a rendering engine to mimic vision-based sensors (such as onboard and ground-based cameras) at various times of day and in various weather conditions over a relatively detailed graphical model of the city. The paper presents a detailed illustration of the simulation and software architecture used for traffic over this urban region. This system is enabling the evaluation of NASA research concepts in autonomy for urban AAM operations on the path toward aircraft flight test evaluation.

Keerthana Kannan↗

Realtime Decision Making on EO-1 Using Onboard Science Analysis

Recent autonomy experiments conducted on Earth Observing 1 (EO-1) using the Autonomous Sciencecraft Experiment (ASE) flight software has been used to classify key features in hyperspectral images captured by EO-1. Furthermore, analysis is performed by this software onboard EO-1 and then used to modify the operational plan without interaction from the ground. This paper will outline the overall operations concept and provide some details and examples of the onboard science processing, science analysis, and replanning.

Sherwood, Robert↗

Mission data system and the future of autonomy at Jet Propulsion Laboratory

Planetary missions require significant levels of autonomy, due to the critical, one-time-only, nature of many mission objectives, and to the long delay times for human intervention. These missions also operate in highly uncertain environments, such as planetary atmospheres or surfaces. Mission Data Systems (MDS) is a project to construct a reusable software architecture for planetary missions, based on identifying the states of the mission.

MDS autonomy↗

Principles for Architecting Autonomous Systems

This paper distills principles for developing autonomous systems based on experience and lessons learned from past efforts. The purpose of these principles is to establish a common understanding and knowledge of architectural elements to guide the development of next-generation multi-mission autonomous systems and ensure the safe and productive operation of space assets. An attempt has been made to ground these principles in fundamentals that should withstand the test of time while allowing for and enabling the advancement of technologies. They are not intended to prescribe a design nor a software representation. There may be multiple designs that can honor these principles. These principles are focused on autonomy for robotic assets. As such, they do not address autonomy for crewed assets nor autonomy that can collectively generate intelligent behavior without top-level system cognizance (e.g., intelligent swarm behavior). These areas would be a subject of future efforts.

Day, John↗

A Thinking System and Thinking Autonomy

There are many definitions of what a “Thinking System” (TS) is. The literature primarily addresses what is called “Systems Thinking.” Dr. Marie Morganelli from Southern New Hampshire University states that “Systems thinking is a holistic way to investigate factors and interactions that could contribute to a possible outcome. A mindset more than a prescribed practice, systems thinking provides an understanding of how individuals can work together in different types of teams and through that understanding, create the best possible processes to accomplish just about anything.” So, a TS is a system that is capable of “systems thinking,” as it should be able to “ … create [utilize] the best possible processes [and intelligence] to accomplish just about anything.” To achieve this capability, human-like thinking is required. A truly autonomous system must be one that is capable of human-like thinking. This paper will address “Thinking Autonomy” (TA) enabled by a “Thinking System.” It will describe an architecture with the elements required to achieve the “thinking” behavior: understanding, intellect, reason, decision, will. The paper will further describe the contents and functionality of these elements and how to implement them, including software capabilities needed. Finally, the paper will provide details of a software platform that enables TA, the NASA Platform for Autonomous Systems (NPAS), and describe implementations of thinking systems. Thinking systems will enable a fundamental change how AI and autonomy are implemented. It will change from a “brute force” approach that results in one-time implementations that are minimally intelligent or autonomous to a “thinking” approach where implementations evolve continuously and enable powerful intelligence and autonomy on systems of high complexity as well as on systems-of-systems.

Thinking systems↗

FRESCO: A Framework for Spacecraft Systems Autonomy

Achieving the science exploration and defense goals of the following decades will require flight systems capable of operations with limited operator contact, system mode changes and retasking based on sensor data, and complex robotic operations. To support these capabilities, increasingly autonomous flight systems are required that can perform dedicated mission functions, e.g. payload targeting and communications, and system-level functions, e.g. planning and goal monitoring. Architecting an autonomous system requires a well-reasoned, self-consistent framework to avoid \textit{ad hoc} design choices that will introduce complexity and risk. The Framework for Robust Execution and Scheduling of Commands On-Board, FRESCO, is the result of lessons learned in developing a software architecture to enable autonomous solar system exploration. FRESCO generalizes this work to offer a modular, software-agnostic approach to developing verifiable architecture for autonomous space systems. FRESCO specifies guiding principles, functions, interfaces, and interactions from which mission-specific autonomous control architectures can be derived. FRESCO is a principled framework relying on explicit, state-based goal definitions, centralized management of state knowledge, clearly separated control boundaries, and hierarchical reasoning. Using components from FRESCO reference architecture, an autonomous decision-making architecture can be designed for spacecraft which can then be mapped to flight software architecture. FRESCO is flexibly defined to enable autonomous control of flight systems built using extensive software and hardware heritage. Finally, FRESCO-derived architectures support a spectrum of operator/spacecraft interactions, ranging from traditional commanding to goal-driven commanding with the ability to change mission goals autonomously. FRESCO has been used in defining the autonomy architectures for the ASTERIA mission and have been demonstrated in laboratory and software simulation for small body rendezvous and in-space servicing missions.

Kolcio, Ksenia↗

Integrated Systems and Operational Autonomy for Gateway

The Lunar Gateway space station will be operated with less human oversight and control than any human spacecraft thus far. An autonomous software control architecture has been developed to allow the spacecraft to maintain safe operations of the vehicle during times of no human involvement. The development of these autonomous control functionalities has been both technical and process driven. Given that the Gateway will be built modularly with contributions from all over the world, the systems engineering processes had to be shaped to fit with the contractual and political realities of the construction of the international lunar habitat. This paper will describe these challenges and contributions to the development of human spacecraft for sustainable deep space missions.

J M Badger↗