Search NASA⌕ Search

SEARCH · Search NASA

Results for “Autonomous 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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2009

Autonomous Instrument Placement for Mars Exploration Rovers

Autonomous Instrument Placement (AutoPlace) is onboard software that enables a Mars Exploration Rover to act autonomously in using its manipulator to place scientific instruments on or near designated rock and soil targets. Prior to the development of AutoPlace, it was necessary for human operators on Earth to plan every motion of the manipulator arm in a time-consuming process that included downlinking of images from the rover, analysis of images and creation of commands, and uplinking of commands to the rover. AutoPlace incorporates image analysis and planning algorithms into the onboard rover software, eliminating the need for the downlink/uplink command cycle. Many of these algorithms are derived from the existing groundbased image analysis and planning algorithms, with modifications and augmentations for onboard use.

Leger, P. Chris↗
NASA NTRS2006

Coordinating an Autonomous Earth-Observing Sensorweb

A system of software has been developed to coordinate the operation of an autonomous Earth-observing sensorweb. Sensorwebs are collections of sensor units scattered over large regions to gather data on spatial and temporal patterns of physical, chemical, or biological phenomena in those regions. Each sensor unit is a node in a data-gathering/ data-communication network that spans a region of interest. In this case, the region is the entire Earth, and the sensorweb includes multiple terrestrial and spaceborne sensor units. In addition to acquiring data for scientific study, the sensorweb is required to give timely notice of volcanic eruptions, floods, and other hazardous natural events. In keeping with the inherently modular nature of the sensory, communication, and data-processing hardware, the software features a flexible, modular architecture that facilitates expansion of the network, customization of conditions that trigger alarms of hazardous natural events, and customization of responses to alarms. The soft8 NASA Tech Briefs, July 2006 ware facilitates access to multiple sources of data on an event of scientific interest, enables coordinated use of multiple sensors in rapid reaction to detection of an event, and facilitates the tracking of spacecraft operations, including tracking of the acquisition, processing, and downlinking of requested data.

Sherwood, Robert↗
NASA NTRS2012

Automated Operations Development for Advanced Exploration Systems

Automated space operations command and control software development and its implementation must be an integral part of the vehicle design effort. The software design must encompass autonomous fault detection, isolation, recovery capabilities and also provide "single button" intelligent functions for the crew. Development, operations and safety approval experience with the Timeliner system onboard the International Space Station (ISS), which provided autonomous monitoring with response and single command functionality of payload systems, can be built upon for future automated operations as the ISS Payload effort was the first and only autonomous command and control system to be in continuous execution (6 years), 24 hours a day, 7 days a week within a crewed spacecraft environment. Utilizing proven capabilities from the ISS Higher Active Logic (HAL) System, along with the execution component design from within the HAL 9000 Space Operating System, this design paper will detail the initial HAL System software architecture and interfaces as applied to NASA's Habitat Demonstration Unit (HDU) in support of the Advanced Exploration Systems, Autonomous Mission Operations project. The development and implementation of integrated simulators within this development effort will also be detailed and is the first step in verifying the HAL 9000 Integrated Test-Bed Component [2] designs effectiveness. This design paper will conclude with a summary of the current development status and future development goals as it pertains to automated command and control for the HDU.

Haddock, Angie T.↗
NASA NTRS2012

Automated Operations Development for Advanced Exploration Systems

Automated space operations command and control software development and its implementation must be an integral part of the vehicle design effort. The software design must encompass autonomous fault detection, isolation, recovery capabilities and also provide single button intelligent functions for the crew. Development, operations and safety approval experience with the Timeliner system on-board the International Space Station (ISS), which provided autonomous monitoring with response and single command functionality of payload systems, can be built upon for future automated operations as the ISS Payload effort was the first and only autonomous command and control system to be in continuous execution (6 years), 24 hours a day, 7 days a week within a crewed spacecraft environment. Utilizing proven capabilities from the ISS Higher Active Logic (HAL) System [1] , along with the execution component design from within the HAL 9000 Space Operating System [2] , this design paper will detail the initial HAL System software architecture and interfaces as applied to NASA s Habitat Demonstration Unit (HDU) in support of the Advanced Exploration Systems, Autonomous Mission Operations project. The development and implementation of integrated simulators within this development effort will also be detailed and is the first step in verifying the HAL 9000 Integrated Test-Bed Component [2] designs effectiveness. This design paper will conclude with a summary of the current development status and future development goals as it pertains to automated command and control for the HDU.

Haddock, Angie↗
NASA NTRSDate not supplied

Celestial Navigation in Cislunar Space with autoNGC

Celestial navigation (CelNav) is a source of navigation observables where images of known solar system bodies are used to locate a spacecraft, beneficial within the solar system for both cislunar and deep space missions. CelNav provides a variety of design benefits to support and enable current and new autonomous space operations- using only a camera and a processor to produce in-situ measurements for navigation. This technology reduces subscription to ground-based tracking during all phases of a mission, freeing up resources for other operational needs. This also supports secure navigation since it eliminates the need for ground contact. CelNav enables missions where the light time delay between Earth and the spacecraft is too long (or the Earth to spacecraft line of sight is obscured) to support critical operations. It also enables smaller mission classes, where Deep Space Network (DSN)time is cost prohibitive, to reduce its cost by focusing primarily on data downlink. Finally, it enables the NASA Artemis program and other cislunar human space flight by providing redundant navigation to traditional radiometric tracking. In this presentation, we discuss the implementation of a CelNav app in autonomous Navigation, Guidance, and Control (autoNGC), a comprehensive flight software suite for onboard autonomy that is built on the core Flight System (cFS). The presentation also summarizes the results of flight software-in-the-loop (SIL) and processor-in-the-loop (PIL) demonstrations. Both are high-fidelity simulations with the use of a camera emulator hosted on a GPU server that simulates images that would be captured by the camera. The CelNav app leverages the use of cGIANT (cFS Goddard Image Analysis and Navigation Tool).Previously developed for the autoNGC software suite, cGIANT is an onboard autonomous image processing and optical navigation (OpNav) tool that performs limb-based OpNav and Terrain Relative Navigation. The added CelNav capability of cGIANT generates bearing measurements to multiple known celestial bodies (planets, moons, asteroids, comets, etc.) in monocular (2D) images. These observables are then fed to the Goddard Enhanced Onboard Navigation System (GEONS)navigation filter app, enabling us to navigate the spacecraft autonomously. In early 2025, the autoNGC CelNav capability is planned to be flight tested as part of the onboard autonomy experiment on the Cislunar Autonomous Positioning System Technology Operations and Navigation Experiment(CAPSTONE) spacecraft that is currently in a Lunar Near Rectilinear Halo Orbit(NRHO).

celestial navigation↗
NASA NTRS2010

Data Acquisition System for Multi-Frequency Radar Flight Operations Preparation

A three-channel data acquisition system was developed for the NASA Multi-Frequency Radar (MFR) system. The system is based on a commercial-off-the-shelf (COTS) industrial PC (personal computer) and two dual-channel 14-bit digital receiver cards. The decimated complex envelope representations of the three radar signals are passed to the host PC via the PCI bus, and then processed in parallel by multiple cores of the PC CPU (central processing unit). The innovation is this parallelization of the radar data processing using multiple cores of a standard COTS multi-core CPU. The data processing portion of the data acquisition software was built using autonomous program modules or threads, which can run simultaneously on different cores. A master program module calculates the optimal number of processing threads, launches them, and continually supplies each with data. The benefit of this new parallel software architecture is that COTS PCs can be used to implement increasingly complex processing algorithms on an increasing number of radar range gates and data rates. As new PCs become available with higher numbers of CPU cores, the software will automatically utilize the additional computational capacity.

Leachman, Jonathan↗
NASA NTRS1991

Simulation models for autonomous rendezvous and capture

Autonomous rendezvous and capture (AR&C) is a critical space technology with significant application to a variety of missions. Martin Marietta Astronautics Group (MMAG) has been developing AR&C technical capability in support of several recent NASA contracts. The use of AR&C for the Mars Rover/Sample Return (MRSR) mission was studied through a contract with JSC. Incorporation of AR&C in the Space Transportation Vehicle (STV) lunar mission was studied through a contract with MSFC. The MMAG has also been developing AR&C simulation capability under independent research and development studies. Simulation development was driven by two goals: comprehensive software simulation of the autonomous rendezvous and capture mission from launch to final capture; and integration of the overall software and hardware simulation to support an AR&C flight demonstration. This presentation will highlight the AR&C software simulation tools and analyze results from their application to the STV lunar mission. Plans for an integrated software and hardware simulation will also be summarized.

Smith, Nick G.↗
NASA NTRS2022

Mars 2020 Entry, Descent, and Landing System Software Implementation

On February 18th, 2021, the Mars 2020 project's Perseverance Rover successfully touched down on the Martian surface after nearly eight years of development. The Mars 2020 Entry, Descent, and Landing (EDL) System largely leveraged heritage from the Mars Science Laboratory (MSL) EDL System while employing targeted technological advancements. The landing process is autonomously directed by a software behavior implemented in the rover's primary flight computer called the EDL Timeline that assumes control of the vehicle six days before atmospheric entry. This paper first walks through the basics of the EDL Timeline mechanics and how the behavior is designed to account for internal system variations and environmental unknowns. It then summarizes the interactions between the EDL timeline and other high-level system behaviors like spacecraft mode transitions and system fault protection, focusing on the complications that arise when passing spacecraft control between executive functions. Although the MSL-inherited EDL System is reliable and capable, targeted updates and a thorough verification and validation program were required for Mars 2020. This paper discusses changes made to close vulnerabilities discovered during both MSL and Mars 2020 development cycles, landing system capability enhancements that were enabling for Mars 2020's mission, and how these updates were integrated with the heritage system. It then describes how both analysis and testing campaigns were utilized to verify and validate all aspects of EDL and system behaviors that run during the six days before landing, as well as the operational workarounds that were needed to address problems found during the development and commissioning process. Finally, this paper imparts lessons learned from Mars 2020 EDL development, implementation, and operations, emphasizing how systems designed to conduct time-critical mission events with low margin of error can be improved in the future.

Stehura, Aaron↗
NASA NTRS2022

Mars 2020 Entry, Descent, and Landing Software Implementation

On February 18th, 2021, the Mars 2020 project's Perseverance Rover successfully touched down on the Martian surface after nearly eight years of development. The Mars 2020 Entry, Descent, and Landing (EDL) System largely leveraged heritage from the Mars Science Laboratory (MSL) EDL System while employing targeted technological advancements. The landing process is autonomously directed by a software behavior implemented in the rover's primary flight computer called the EDL Timeline that assumes control of the vehicle six days before atmospheric entry. In addition to performing the critical function of landing the rover on the Martian surface, the EDL timeline behavior must co-exist in a non-partitioned software and system environment with other high-level functions that accomplish the goals for the rest of the mission. Due to the criticality of EDL, the potential for loss of mission, and a need for complete system autonomy, the standard for how the EDL Timeline interacts with other functions in the system is highly constrained. This paper first walks through the basics of the EDL Timeline mechanics and how the behavior is designed to account for internal system variations and environmental unknowns. It then summarizes the interactions between the EDL timeline and other high-level system behaviors like spacecraft mode transitions and system fault protection, focusing on the complications that arise when passing spacecraft control between executive functions. Although the MSL-inherited EDL System is reliable and capable, targeted updates and a thorough verification and validation program were required for Mars 2020. This paper discusses changes made to close vulnerabilities discovered during both MSL and Mars 2020 development cycles, landing system capability enhancements that were enabling for Mars 2020's mission, and how these updates were integrated with the heritage system. It then describes how both analysis and testing campaigns were utilized to verify and validate all aspects of EDL and system behaviors that run during the six days before landing, as well as the operational workarounds that were needed to address problems found during the development and commissioning process. Finally, this paper imparts lessons learned from Mars 2020 EDL development, implementation, and operations, emphasizing how systems designed to conduct time-critical mission events with low margin of error can be improved in the future.

Stehura, Aaron↗
NASA NTRS2005

An Expert System for Autonomous Spacecraft Control

The Autonomous Sciencecraft Experiment (ASE), part of the New Millennium Space Technology 6 Project, is flying onboard the Earth Orbiter 1 (EO-1) mission. The ASE software enables EO-1 to autonomously detect and respond to science events such as: volcanic activity, flooding, and water freeze/thaw. ASE uses classification algorithms to analyze imagery onboard to detect chang-e and science events. Detection of these events is then used to trigger follow-up imagery. Onboard mission planning software then develops a response plan that accounts for target visibility and operations constraints. This plan is then executed using a task execution system that can deal with run-time anomalies. In this paper we describe the autonomy flight software and how it enables a new paradigm of autonomous science and mission operations. We will also describe the current experiment status and future plans.

utonomy flight software↗
NASA NTRS2005

Safe Agents in Space: Preventing and Responding to Anomalies in the Autonomous Sciencecraft Experiment

This paper describes the design of the Autonomous Sciencecraft Experiment, a software agent that has been running on-board the EO-I spacecraft since 2003. The agent recognizes science events, retargets the spacecraft to respond to the science events, and reduces data downlink to only the highest value science data. The autonomous science agent was designed using a layered architectural approach with specific redundant safeguards to reduce the risk of an agent malfUnction to the EO-I spacecraft. The agent was designed to be "safe" by first preventing anomalies, then by automatically detecting and responding to them when possible. This paper describes elements of the design that increase the safety of the agent, the anomalies that occurred during the experiment, and how the agent responded to these anomalies.

autonomous science agent↗
NASA NTRSDate not supplied

Space Transformation -- Localizing the Remote and Connecting the Isolated

In motivating the Space Transformation theme for this year’s 4S symposium, the organizers provided the following context, “Transformation of economies are driven by a change in values and accelerated by new technologies.” These words rang particularly true when I read them at the beginning of the holiday season. Like so many others, I was in the early phases of my Christmas shopping procrastination campaign, and I’d just been reflecting on how Amazon Prime was the transformational tool I’d been waiting for. Basic limiting principles of time and space, supply and demand, were all but erased by the Amazon Prime phenomenon. Coupled with emerging 3D printing and other adaptive manufacturing technologies, a transformation from deliberate planning to “think it … have it” had occurred, empowering me to procrastinate longer than I’d ever dreamed possible. The organizers went on to ponder, “Will space transformation also affect society?”, just as our team at the Air Force Research Lab’s (AFRL) Center for Rapid Innovation (CRI) were working alongside partners within our larger Integrated Capabilities Directorate, NASA’s Flight Opportunities and Small Spacecraft Technology programs, and DARPA’s Luna-10 program to develop technologies and execute demonstration missions that leverage the space domain to genuinely connect even the most remote and austere domains on the timeline of need. Picking apart the miracle that is Amazon prime, where does the model fail, and why? More relevantly to the theme of this year’s symposium, how can the space domain be used to overcome its limitations and minimize its weaknesses? Perhaps it is best assessed in the context of Use Cases. What are the Amazon delivery cost, schedule, and cargo limiters to the Amundsen-Scott South Pole Research Station, or the Lunar South Pole Research Station? This paper will explore enabling infrastructure that allows Amazon prime to thrive and assess the transformational enabling technologies that would be necessary to extend that miracle to the truly remote or the truly austere. Localizing the Remote • First, it will evaluate the ability of the on-going AFRL Rocket Cargo and Space Initiatives Ringside Seats systems, coupled with Astrobotic’s Xodiak and Xogdor capabilities, developed to support the NASA Flight Opportunities Program (FOP), to supply orbital/suborbital delivery to both improved and austere sites on the Earth and Moon. • Then, it will add the surface terminal distribution leg, with an examination of Lunar Outpost’s Mobile Autonomous Prospecting Platform (MAPP), equipped with Mobile Autonomous Robotic Swarm (MARS) software, and Intuitive Machine’s Hopper, developed with support of AFRL and NASA’s Commercial Lunar Payload Services (CLPS) program. Connecting the Isolated From there, it will focus on the destination, asking what implied destination services are required to support highly assured autonomous delivery. • Specifically, it will highlight Astrobotic’s Skymage mesh-networked publish and subscribe communication and navigation service, as well as AFRL’s on-going developments of radioisotope and reactor nuclear-sourced thermoelectric power generation and distribution systems under development under the Joint Emergent Technology Supplying On-orbit Nuclear Power (JETSON) program by Lockheed Martin, Westinghouse, Intuitive Machines, and Zeno Power, to provide the power service to locations well off the grid. • Finally, the paper will connect to the “human machine”. What connects the remote or in-situ human consumer to the remote domain? What connects the diverse international government and commercial services to each other? The former will focus on AFRL’s OraCloud feeding their Space Defense Control and Characterization System (SDCCS) and Lunar Station’s MoonHacker systems, while the latter will focus on the BlueHalo/Tensor LunX Technology Platform for the Cislunar Commodity Marketplace. In 1984, Krafft Ehricke famously remarked that, “If God wanted man to become a spacefaring species, He would have given man a Moon.” This paper is not about the Moon, but is about humans as a spacefaring species, shedding the pesky land/air limitations of the Amazon Prime model … so that we can all live a procrastinator’s “think it … have it” existence.

Charles Finley↗
NASA NTRS2003

Autonomous Science on the EO-1 Mission

In mid-2003, we will fly software to detect science events that will drive autonomous scene selectionon board the New Millennium Earth Observing 1 (EO-1) spacecraft. This software will demonstrate the potential for future space missions to use onboard decision-making to detect science events and respond autonomously to capture short-lived science events and to downlink only the highest value science data.

autonomous systems robust execution↗
NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George↗
NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto-Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner- TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders

Plattsmier, George I.↗
NASA NTRS1994

Advanced Automation for Ion Trap Mass Spectrometry-New Opportunities for Real-Time Autonomous Analysis

The utility of MS/MS for both target compound analysis and the structure elucidation of unknowns has been described in a number of references. A broader acceptance of this technique has not yet been realized as it requires large, complex, and costly instrumentation which has not been competitive with more conventional techniques. Recent advancements in ion trap mass spectrometry promise to change this situation. Although the ion trap's small size, sensitivity, and ability to perform multiple stages of mass spectrometry have made it eminently suitable for on-line, real-time monitoring applications, advance automation techniques are required to make these capabilities more accessible to non-experts. Towards this end we have developed custom software for the design and implementation of MS/MS experiments. This software allows the user to take full advantage of the ion trap's versatility with respect to ionization techniques, scan proxies, and ion accumulation/ejection methods. Additionally, expert system software has been developed for autonomous target compound analysis. This software has been linked to ion trap control software and a commercial data system to bring all of the steps in the analysis cycle under control of the expert system. These software development efforts and their utilization for a number of trace analysis applications will be described.

Palmer, Peter T.↗
NASA NTRS2004

An Introduction to Flight Software Development: FSW Today, FSW 2010

Experience and knowledge gained from ongoing maintenance of Space Shuttle Flight Software and new development projects including Cockpit Avionics Upgrade are applied to projected needs of the National Space Exploration Vision through Spiral 2. Lessons learned from these current activities are applied to create a sustainable, reliable model for development of critical software to support Project Constellation. This presentation introduces the technologies, methodologies, and infrastructure needed to produce and sustain high quality software. It will propose what is needed to support a Vision for Space Exploration that places demands on the innovation and productivity needed to support future space exploration. The technologies in use today within FSW development include tools that provide requirements tracking, integrated change management, modeling and simulation software. Specific challenges that have been met include the introduction and integration of Commercial Off the Shelf (COTS) Real Time Operating System for critical functions. Though technology prediction has proved to be imprecise, Project Constellation requirements will need continued integration of new technology with evolving methodologies and changing project infrastructure. Targets for continued technology investment are integrated health monitoring and management, self healing software, standard payload interfaces, autonomous operation, and improvements in training. Emulation of the target hardware will also allow significant streamlining of development and testing. The methodologies in use today for FSW development are object oriented UML design, iterative development using independent components, as well as rapid prototyping . In addition, Lean Six Sigma and CMMI play a critical role in the quality and efficiency of the workforce processes. Over the next six years, we expect these methodologies to merge with other improvements into a consolidated office culture with all processes being guided by automated office assistants. The infrastructure in use today includes strict software development and configuration management procedures, including strong control of resource management and critical skills coverage. This will evolve to a fully integrated staff organization with efficient and effective communication throughout all levels guided by a Mission-Systems Architecture framework with focus on risk management and attention toward inevitable product obsolescence. This infrastructure of computing equipment, software and processes will itself be subject to technological change and need for management of change and improvement,

Gouvela, John↗
NASA NTRS2010

Range Safety for an Autonomous Flight Safety System

The Range Safety Algorithm software encapsulates the various constructs and algorithms required to accomplish Time Space Position Information (TSPI) data management from multiple tracking sources, autonomous mission mode detection and management, and flight-termination mission rule evaluation. The software evaluates various user-configurable rule sets that govern the qualification of TSPI data sources, provides a prelaunch autonomous hold-launch function, performs the flight-monitoring-and-termination functions, and performs end-of-mission safing

Lanzi, Raymond J.↗