Results for “autonomous execution” — Page 12

NASA NTRS2021

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↗

NASA NTRSDate not supplied

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

NASA NTRSDate not supplied

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

NASA NTRS2019

NASA Platform for Autonomous Systems (NPAS)

NASA Platform for Autonomous Systems (NPAS) is a disruptive software platform and processes being developed by the NASA Stennis Space Center (SSC) Autonomous Systems Laboratory (ASL). Autonomous operations are critical for the success, safety and crew survival of NASA deep space missions beyond low Earth orbit, including the Gateway, and for the future of cost-effective ground mission operations. NPAS represents the embodiment of an innovative paradigm for “thinking” autonomy in contrast to brute-force autonomy. NPAS uniquely addresses the requirements and integrates the primary functionalities for autonomous operations, in one platform that includes: (1) Integrated System Health Management (ISHM); (2) autonomy strategies, guided by system health and concepts of operations; (3) domain objects (system elements) and infrastructure to create complete application domain knowledge models (4) infrastructure to create, schedule, and execute mission plans; (5) infrastructure to develop user interfaces for comprehensive awareness; and (6) infrastructure to integrate distributed autonomous applications across networks. NPAS is a single platform that can be used to make any system operate with any desirable degree of autonomy, as well as provide comprehensive system awareness to operators and users.

Figueroa, Fernando↗

NASA NTRS2003

Cooperative Exploration of Rough Martian Terrains with the "Scorpion" Legged Robot as an Adjunct to a Rover.

NASA needs autonomous robotic exploration of difficult (rough and/or steep) scientifically interesting Martian terrains. Concepts involving distributed autonomy for cooperative robotic exploration are key to enabling new scientific objectives in robotic missions. We propose to utilize a legged robot as an adjunct scout to a rover for access to difficult - scientifically interesting - terrains (rocky areas, slopes, cliffs). Our final mission scenario involves the Ames rover platform "K9" and Scorpion acting together to explore a steep cliff, with the Scorpion robot rappelling down using the K9 as an anchor as well as mission planner and executive. Cooperation concepts, including wheeled rappelling robots have been proposed before. Now we propose to test the combined advantages of a wheeled vehicle with a legged scout as well as the advantages of merging of high level planning and execution with biologically inspired, behavior based robotics. We propose to use the 8-legged, multifunctional autonomous robot platform Scorpion that is currently capable of: Walking on different terrains (rocks, sand, grass, ...). Perceiving its environment and modifying its behavioral pattern accordingly. These capabilities would be extended to enable the Scorpion to: communicate and cooperate with a partner robot; climb over rocks, rubble piles, and objects with structural features. This will be done in the context of exploration of rough terrains in the neighborhood of the rover, but inaccessible to it, culminating in the added capability of rappelling down a steep cliff for both vertical and horizontal terrain observation.

Colombano, Silvano P.↗

NASA NTRS1973

A programmable computer interface for CAMAC

An interface has been developed for CAMAC instrumentation systems that implements data transfers controlled either by the computer CPU or by an autonomous (data-channel) processor in the interface unit. The data channel processor executes programs stored in the computer memory. These programs consist of standard CAMAC module commands plus special control characters and commands for the processor itself. The interface was built for the PDP-15 computer, which has an 18-bit word structure, but both 18- and 24-bit data transfers can be made. A software system has been written that exploits the many features of the processor.

Bercaw, R. W.↗

NASA NTRS1990

Autonomous navigation and control of a Mars rover

A Mars rover will need to be able to navigate autonomously kilometers at a time. This paper outlines the sensing, perception, planning, and execution monitoring systems that are currently being designed for the rover. The sensing is based around stereo vision. The interpretation of the images use a registration of the depth map with a global height map provided by an orbiting spacecraft. Safe, low energy paths are then planned through the map, and expectations of what the rover's articulation sensors should sense are generated. These expectations are then used to ensure that the planned path is correctly being executed.

Miller, D. P.↗

NASA NTRS1992

Performance of a six-legged planetary rover - Power, positioning, and autonomous walking

The authors quantify several performance metrics for the Ambler, a six-legged robot configured for autonomous traversal of Mars-like terrain. They present power consumption measures for walking on sandy terrain and for vertical lifts at different velocities. They document the accuracy of a novel dead reckoning approach, and analyze the accuracy. They describe the results of autonomous walking experiments in terms of terrain traversed, walking speed, number of instructions executed and endurance.

Krotkov, Eric↗

NASA NTRS1992

Ground-remote control for space station telerobotics with time delay

The study proposes a ground-remote telerobot control architecture which could be used for control of Space Station Freedom manipulators. The architecture provides two local-site operator control stations representing potential earth-based and remote Space Station-based operator control stations. A unified control system at the remote site provides autonomous, shared, and teleoperation control for single-and dual-arm task execution. An operational laboratory system which demonstrates the feasibility of various technologies in the proposed architecture, including teleoperation, shared control, and supervised autonomy, is described. Enhancements to the system currently under development, including remote site implementation in Ada, integration and control of a redundant 7-DOF manipulator, and local site advanced operator aids, are also described.

Backes, Paul G.↗

NASA NTRS1994

The ground vehicle manager's associate

An overview of MAX, a software framework for manager's associate systems, is presented. MAX is used to develop and execute a problem-solving strategy for the task planning of semi-autonomous agents with the assistance of human performance. This paper describes the use of MAX in the supervisory management of robotic vehicles as they explore a planetary surface.

Edwards, Gary R.↗

NASA NTRS2008

Terrain-Adaptive Navigation Architecture

A navigation system designed for a Mars rover has been designed to deal with rough terrain and/or potential slip when evaluating and executing paths. The system also can be used for any off-road, autonomous vehicles. The system enables vehicles to autonomously navigate different terrain challenges including dry river channel systems, putative shorelines, and gullies emanating from canyon walls. Several of the technologies within this innovation increase the navigation system s capabilities compared to earlier rover navigation algorithms.

Helmick, Daniel M.↗

NASA NTRS2010

The Evolution of Extravehicular Activity Operations to Lunar Exploration Based on Operational Lessons Learned During 2009 NASA Desert RATS Field Testing

This paper will present options to evolutionary changes in several philosophical areas of extravehicular activity (EVA) operations. These areas will include single person verses team EVAs; various loss of communications scenarios (with Mission Control, between suited crew, suited crew to rover crew, and rover crew A to rover crew B); EVA termination and abort time requirements; incapacitated crew ingress time requirements; autonomous crew operations during loss of signal periods including crew decisions on EVA execution (including decision for single verses team EVA). Additionally, suggestions as to the evolution of the make-up of the EVA flight control team from the current standard will be presented. With respect to the flight control team, the major areas of EVA flight control, EVA Systems and EVA Tasks, will be reviewed, and suggested evolutions of each will be presented. Currently both areas receive real-time information, and provide immediate feedback during EVAs as well as spacesuit (extravehicular mobility unit - EMU) maintenance and servicing periods. With respect to the tasks being performed, either EMU servicing and maintenance, or the specific EVA tasks, daily revising of plans will need to be able to be smoothly implemented to account for unforeseen situations and findings. Many of the presented ideas are a result of lessons learned by the NASA Johnson Space Center Mission Operations Directorate operations team support during the 2009 NASA Desert Research and Technology Studies (Desert RATS). It is important that the philosophy of both EVA crew operations and flight control be examined now, so that, where required, adjustments can be made to a next generation EMU and EVA equipment that will complement the anticipated needs of both the EVA flight control team and the crews.

Bell, Ernest R., Jr.↗

NASA NTRS2014

Autonomous Spacecraft Communication Interface for Load Planning

Ground-based controllers can remain in continuous communication with spacecraft in low Earth orbit (LEO) with near-instantaneous communication speeds. This permits near real-time control of all of the core spacecraft systems by ground personnel. However, as NASA missions move beyond LEO, light-time communication delay issues, such as time lag and low bandwidth, will prohibit this type of operation. As missions become more distant, autonomous control of manned spacecraft will be required. The focus of this paper is the power subsystem. For present missions, controllers on the ground develop a complete schedule of power usage for all spacecraft components. This paper presents work currently underway at NASA to develop an architecture for an autonomous spacecraft, and focuses on the development of communication between the Mission Manager and the Autonomous Power Controller. These two systems must work together in order to plan future load use and respond to unanticipated plan deviations. Using a nominal spacecraft architecture and prototype versions of these two key components, a number of simulations are run under a variety of operational conditions, enabling development of content and format of the messages necessary to achieve the desired goals. The goals include negotiation of a load schedule that meets the global requirements (contained in the Mission Manager) and local power system requirements (contained in the Autonomous Power Controller), and communication of off-plan disturbances that arise while executing a negotiated plan. The message content is developed in two steps: first, a set of rapid-prototyping "paper" simulations are preformed; then the resultant optimized messages are codified for computer communication for use in automated testing.

Controls↗

NASA NTRS2017

Progress of Crew Autonomous Scheduling Test (CAST) On the ISS

The United States space policy is evolving toward missions beyond low Earth orbit. In an effort to meet that policy, NASA has recognized Autonomous Mission Operations (AMO) as a valuable capability. Identified within AMO capabilities is the potential for autonomous planning and replanning during human spaceflight operations. That is allowing crew members to collectively or individually participate in the development of their own schedules. Currently, dedicated mission operations planners collaborate with international partners to create daily plans for astronauts aboard the International Space Station (ISS), taking into account mission requirements, ground rules, and various vehicle and payload constraints. In future deep space operations the crew will require more independence from ground support due to communication transmission delays. Furthermore, crew members who are provided with the capability to schedule their own activities are able to leverage direct experience operating in the space environment, and possibly maximize their efficiency. CAST (Crew Autonomous Scheduling Test) is an ISS investigation designed to analyze three important hypotheses about crew autonomous scheduling. First, given appropriate inputs, the crew is able to create and execute a plan in a reasonable period of time without impacts to mission success. Second, the proximity of the planner, in this case the crew, to the planned operations increases their operational efficiency. Third, crew members are more satisfied when given a role in plan development. This presentation shows the progress done in this study with a single astronaut test subject participating in five CAST sessions. CAST is a technology demonstration payload sponsored by the ISS Research Science and Technology Office, and performed by experts in Mission Operations Planning from the Flight Operations Directorate at NASA Johnson Space Center, and researchers across multiple NASA centers.

Healy, Matthew↗

NASA NTRS2018

Evolving Relationship between Humans and Machines

Traditional design typically consists of a master-servant relationship between humans and machines where the human directly controls what the machine will do and when it will do it through an interface. The current archetypical path encompasses moving from informational displays, where the human directly controls the machine based on information displayed, to automation where the human still directs the machine that then caries out the request using predefined set of instructions. Rapid pace of technological advancement makes it possible now, or in a near future, for machines to reach a level of intelligence that enables for systems to execute tasks/missions without predefined specific instructions; thus attaining a status of non- human autonomous agents. Now the course of human-machine interface technology changes from an information system to automation to an autonomous agent—essentially moving from a master-servant relationship to teammates. This paper discusses these changing relationships and challenges associated with progressing from a master-servant relationship with technology to more of an equal teammate. Examples of this progression includes current work encompassing rotorcraft noise minimization for urban air mobility.

Trujillo, Anna C.↗

NASA NTRS2002

Autonomous sciencecraft experiment : NASA New Millennium Program

In 2006, the Air Force TechSat 21 mission will fly the Autonomous Sciencecraft Experiment (ASE). ASE will perform onboard: science analysis, mission re-planning, and robust execution. These technologies will enable TechSat 21 to respond onboard to sciene opportunities by retargeting future science observations and returning only the most important science data. This capability can dramatically increase science return and is central to future mission concepts to monitor dynamic phenomena such as lo volcanoes, the Europa ice crust, and Martian sandstorms.

Autonomous sciencecraft experiment↗

NASA NTRS2017

PHM Enabled Autonomous Propellant Loading Operations

The utility of Prognostics and Health Management (PHM) software capability applied to Autonomous Operations (AO) remains an active research area within aerospace applications. The ability to gain insight into which assets and subsystems are functioning properly, along with the derivation of confident predictions concerning future ability, reliability, and availability, are important enablers for making sound mission planning decisions. When coupled with software that fully supports mission planning and execution, an integrated solution can be developed that leverages state assessment and estimation for the purposes of delivering autonomous operations. The authors have been applying this integrated, model-based approach to the autonomous loading of cryogenic spacecraft propellants at Kennedy Space Center.

Walker, Mark↗

NASA NTRS2018

Safe2Ditch Autonomous Crash Management System for Small Unmanned Aerial Systems: Concept Definition and Flight Test Results

Small unmanned aerial systems (sUAS) have the potential for a large array of highly-beneficial applications. These applications are too numerous to comprehensively list, but include search and rescue, fire spotting, precision agriculture, etc. to name a few. Typically sUAS vehicles weigh less than 55 lbs and will be performing flight operations in the National Air Space (NAS). Certain sUAS applications, such as package delivery, will include operations in the close proximity of the general public. The full benefit from sUAS is contingent upon the resolution of several technological areas in order to provide an acceptable level of risk for widespread sUAS operations. Operations of sUAS vehicles pose risks to people and property on the ground as well as manned aviation. Several of the more significant sUAS technological areas include, but are not limited to: autonomous sense and avoid and deconfliction of sUAS from other sUAS and manned aircraft, communications and interfaces between the vehicle and human operators, and the overall reliability of the sUAS and constituent subsystems. While all of the technological areas listed contribute significantly to the safe execution of the sUAS flight operations, contingency or emergency systems can greatly contribute to sUAS risk mitigations to manage situations where the vehicle is in distress. The Safe2Ditch (S2D) system is an autonomous crash management system for sUAS. Its function is to enable sUAS to execute emergency landings and avoid injuring people on the ground, damaging property, and lastly preserving the sUAS and payload. A sUAS flight test effort was performed to test the integration of sub-elements of the S2D system with a representative sUAS multi-rotor.

Glaab, Louis J.↗