Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission execution”

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 721 records · Page 40
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

Automatic Command Sequence Generation

Automatic Sequence Generator (Autogen) Version 3.0 software automatically generates command sequences for the Mars Reconnaissance Orbiter (MRO) and several other JPL spacecraft operated by the multi-mission support team. Autogen uses standard JPL sequencing tools like APGEN, ASP, SEQGEN, and the DOM database to automate the generation of uplink command products, Spacecraft Command Message Format (SCMF) files, and the corresponding ground command products, DSN Keywords Files (DKF). Autogen supports all the major multi-mission mission phases including the cruise, aerobraking, mapping/science, and relay mission phases. Autogen is a Perl script, which functions within the mission operations UNIX environment. It consists of two parts: a set of model files and the autogen Perl script. Autogen encodes the behaviors of the system into a model and encodes algorithms for context sensitive customizations of the modeled behaviors. The model includes knowledge of different mission phases and how the resultant command products must differ for these phases. The executable software portion of Autogen, automates the setup and use of APGEN for constructing a spacecraft activity sequence file (SASF). The setup includes file retrieval through the DOM (Distributed Object Manager), an object database used to store project files. This step retrieves all the needed input files for generating the command products. Depending on the mission phase, Autogen also uses the ASP (Automated Sequence Processor) and SEQGEN to generate the command product sent to the spacecraft. Autogen also provides the means for customizing sequences through the use of configuration files. By automating the majority of the sequencing generation process, Autogen eliminates many sequence generation errors commonly introduced by manually constructing spacecraft command sequences. Through the layering of commands into the sequence by a series of scheduling algorithms, users are able to rapidly and reliably construct the desired uplink command products. With the aid of Autogen, sequences may be produced in a matter of hours instead of weeks, with a significant reduction in the number of people on the sequence team. As a result, the uplink product generation process is significantly streamlined and mission risk is significantly reduced. Autogen is used for operations of MRO, Mars Global Surveyor (MGS), Mars Exploration Rover (MER), Mars Odyssey, and will be used for operations of Phoenix. Autogen Version 3.0 is the operational version of Autogen including the MRO adaptation for the cruise mission phase, and was also used for development of the aerobraking and mapping mission phases for MRO.

Fisher, Forest↗
NASA NTRS2006

Software Defined Radio Standard Architecture and its Application to NASA Space Missions

A software defined radio (SDR) architecture used in space-based platforms proposes to standardize certain aspects of radio development such as interface definitions, functional control and execution, and application software and firmware development. NASA has charted a team to develop an open software defined radio hardware and software architecture to support NASA missions and determine the viability of an Agency-wide Standard. A draft concept of the proposed standard has been released and discussed among organizations in the SDR community. Appropriate leveraging of the JTRS SCA, OMG's SWRadio Architecture and other aspects are considered. A standard radio architecture offers potential value by employing common waveform software instantiation, operation, testing and software maintenance. While software defined radios offer greater flexibility, they also poses challenges to the radio development for the space environment in terms of size, mass and power consumption and available technology. An SDR architecture for space must recognize and address the constraints of space flight hardware, and systems along with flight heritage and culture. NASA is actively participating in the development of technology and standards related to software defined radios. As NASA considers a standard radio architecture for space communications, input and coordination from government agencies, the industry, academia, and standards bodies is key to a successful architecture. The unique aspects of space require thorough investigation of relevant terrestrial technologies properly adapted to space. The talk will describe NASA's current effort to investigate SDR applications to space missions and a brief overview of a candidate architecture under consideration for space based platforms.

Andro, Monty↗
NASA NTRS1972

Definition of experiments and instruments for a communication/navigation research laboratory. Volume 1: Executive summary

This study was undertaken to develop conceptual designs for a manned, space shuttle sortie mission laboratory capable of supporting a wide variety of experiments in conjunction with communications and navigation research. This space/laboratory would be one in which man may effectively increase experiment efficiency by certain observations, modifications, setup, calibration, and limited maintenance steps. In addition, man may monitor experiment progress and perform preliminary data evaluation to verify proper equipment functioning and may terminate or redirect experiments to obtain the most desirable end results. The flexibility and unique capabilities of man as an experimenter in such a laboratory will add greatly to the simplification of space experiments and this provides the basis for commonality in many of the supportive subsystems, thus reaping the benefits of reusability and reduced experiment costs. For Vol. 4, see N73-19268.

Source record↗
NASA NTRS1990

Manned Mars System Study (MMSS): Mars transportation and facility study. Volume 1: Executive Summary

The purpose of the study was to design and analyze systems for conducting human missions to Mars and the moon, with special emphasis on the transportation and facility infrastructure. This study was conducted by Martin Marietta Astronautics Group, with an important teaming role by Science Applications International Corporation (SAIC). This work included the studies and separate reports of the FY-1988 and 1989 case studies as well as special analyses and parametric studies.

Source record↗
NASA NTRS2019

Supporting automation in spacecraft activity planning with simulation and visualization

Automation is gaining momentum in spacecraft operations, however, at a much slower pace than comparable application domains. The reasons behind slow adoption is (1) the need for high reliability and (2) the limited interaction between human operators and the automated systems. For automated systems to be adopted and trusted by humans, humans need to gain intuition about the decision making process of the automated system and trust in its execution [1]. In this paper, we present how simulation and visualization can enhance adoption of an automated on-board activity scheduling system, specifically in the context of Mars2020 rover mission[2]. The visualization aims to communicate to the users degree of variance and uncertainty in possible schedule execution. Our preliminary validation results suggest that the proposed visualization increases operators’ confidence in—and likelihood of adopting—the automated scheduling system.

Chien, Steve↗
NASA NTRSDate not supplied

What is the Role of Usability and Trust in Autonomy?

Usability encompasses learnability, efficiency, memorability, effectiveness, and satisfaction. NASA’s standards for usability acceptance criteria focus on interfaces that help operators achieve their tasks efficiently, effectively, and with satisfaction. However, discussions on usability, especially regarding future highly automated and autonomous systems, rarely include trust. As NASA plans for long-duration exploration missions, it envisions astronauts operating more independently from Mission Control on Earth. This independence will drive the development of these highly automated and autonomous systems that astronauts will use daily. To prepare for this future, our team has developed a scheduling and execution software tool that facilitates self-scheduling, allowing astronauts to independently manage their own schedule without Mission Control’s involvement. Over many years, we have developed, matured, and evaluated our software tool in extreme environments, prioritizing user-centered design and high usability. These evaluations have included multiple campaigns in NASA analogs, including NEEMO, BASALT, and HERA, as well as technology demonstrations onboard the International Space Station. Our recent research on software interfaces for future astronaut autonomy revealed a strong correlation between usability and trust measures. In a controlled lab experiment, we asked novice users to perform a complex scheduling task, during which the software immediately validated the schedule’s constraints and checked for violations. We collected usability (User Experience Questionnaire, UEQ) and trust (Trust in Automated Systems scale, TAS) measures; significant, strong, and moderate correlations emerged between several of the UEQ metrics and TAS. These results support the argument for investing in usability early to enable and sustain trust in highly automated and autonomous systems.

usability↗
NASA NTRS1985

Development of ADOCS controllers and control laws. Volume 1: Executive summary

The Advanced Cockpit Controls/Advanced Flight Control System (ACC/AFCS) study was conducted by the Boeing Vertol Company as part of the Army's Advanced Digital/Optical Control System (ADOCS) program. Specifically, the ACC/AFCS investigation was aimed at developing the flight control laws for the ADOCS demonstrator aircraft that will provide satisfactory handling qualities for an attack helicopter mission. The three major elements of design considered during the study are as follows: Pilot's integrated Side-Stick Controller (SSC) -- Number of axes controlled; force/displacement characteristics; ergonomic design. Stability and Control Augmentation System (SCAS)--Digital flight control laws for the various mission phases; SCAS mode switching logic. Pilot's Displays--For night/adverse weather conditions, the dynamics of the superimposed symbology presented to the pilot in a format similar to the Advanced Attack Helicopter (AAH) Pilot Night Vision System (PNVS) for each mission phase as a function of SCAS characteristics; display mode switching logic. Volume 1 is an Executive Summary of the study. Conclusions drawn from analysis of pilot rating data and commentary were used to formulate recommendations for the ADOCS demonstrator flight control system design. The ACC/AFCS simulation data also provide an extensive data base to aid the development of advanced flight control system design for future V/STOL aircraft.

Landis, Kenneth H.↗
NASA NTRS2017

Increasing Small Satellite Reliability- A Public-Private Initiative

At present, CubeSat components and buses are generally not appropriate for missions where significant risk of failure, or the inability to quantify risk or confidence, is acceptable. However, in the future we anticipate that CubeSats will be used for missions requiring reliability of 1-3 years for Earth-observing missions and even longer for Planetary, Heliophysics, and Astrophysics missions. Their growing potential utility is driving an interagency effort to improve and quantify CubeSat reliability, and more generally, small satellite mission risk. The Small Satellite Reliability Initiative (SSRI)—an ongoing activity with broad collaborative participation from civil, DoD, and commercial space systems providers and stakeholders—targets this challenge. The Initiative seeks to define implementable and broadly-accepted approaches to achieve reliability and acceptable risk postures associated with several SmallSat mission risk classes—from “do no harm” missions, to those associated with missions whose failure would result in loss or delay of key national objectives. These approaches will maintain, to the extent practical, cost efficiencies associated with small satellite missions and consider constraints associated with supply chain elements, as appropriate. The SSRI addresses this challenge from two architectural levels—the mission- or system-level, and the component- or subsystem-level. The mission- or system-level scope targets assessment approaches that are efficient and effective, with mitigation strategies that facilitate resiliency to mission or system anomalies while the component- or subsystem-level scope addresses the challenge at lower architectural levels. The initiative does not limit strategies and approaches to proven and traditional methodologies, but is focused on fomenting thought on novel and innovative solutions. This paper discusses the genesis of and drivers for this initiative, how the public-private collaboration is being executed, findings and recommendations derived to date, and next steps towards broadening small satellite mission potential.

SmallSat↗
NASA NTRS2019

Maturation of Dynamic Power Convertors for Radioisotope Power Systems

Dynamic Radioisotope Power Systems (DRPS) are being developed by NASA's RPS Program in collaboration with the U.S. Department of Energy (DOE) for space science and exploration missions. A development effort is currently underway to mature dynamic power convertors for infusion into a potential future flight generator. This convertor maturation effort was formulated by the RPS Program at NASA Headquarters based on successful maturation models and utilizes expertise from agency technology and mission centers to support requirements development and technology assessments. The effort is being executed by Glenn Research Center's Dynamic Radioisotope Power Systems (DRPS) project and the Thermal Energy Conversion Branch. The Dynamic Power Convertor (DPC) contracts consist of three phases to enable design, fabrication, and independent assessment after delivery to the government. The contracts are intended to gather data on candidate dynamic conversion technologies to fill knowledge gaps, support assessments of dynamic conversion technologies, and elicit generator requirements. The SRG-110 (Stirling Radioisotope Generator) and ASRG (Advanced Stirling Radioisotope Generator) flight development projects provided Stirling convertor demonstration units and engineering models to verify and validate convertors against performance specifications and mission requirements. These units utilize temperature resistance materials and non-contacting bearings to demonstrate wear-free, long-life operation. This maturation effort builds on past lessons learned and new requirements focused on demonstrating convertor robustness to critical environments meant to stress key aspects of each convertor within the margins of the design. This effort seeks to realize the full potential of dynamic power conversion technologies for NASA's space science and exploration missions.

Wilson, Scott↗
NASA NTRS2019

Maturation of Dynamic Power Convertors for Radioisotope Power Systems

Dynamic Radioisotope Power Systems (DRPS) are being developed by NASA’s Radioisotope Power Systems (RPS) Program in collaboration with the U.S. Department of Energy (DOE) for space science and exploration missions. A development effort is currently underway to mature dynamic power convertors for infusion into a potential future flight generator. This convertor maturation effort was formulated by the RPS Program at NASA Headquarters based on successful maturation models and utilizes expertise from agency’s technology and mission centers to support requirements development and technology assessments. The effort is being executed by Glenn Research Center’s (GRC) DRPS Project and the Thermal Energy Conversion Branch. The Dynamic Power Convertor (DPC) contracts consist of three phases to enable design, fabrication, and independent assessment of prototypes after delivery to the government. The contracts are intended to gather data on candidate dynamic conversion technologies to fill knowledge gaps, support assessments of dynamic conversion technologies, and elicit generator requirements. The 110-watt Stirling Radioisotope Generator (SRG-110) and Advanced Stirling Radioisotope Generator (ASRG) flight development projects provided Stirling convertor demonstration units and engineering models to verify and validate convertors against performance specifications and mission requirements. These units utilize temperature resistant materials and non-contacting bearings to demonstrate wear-free, long-life operation. This maturation effort builds on past lessons-learned and new requirements focused on demonstrating convertor robustness to critical environments meant to stress key aspects of each convertor within the margins of the design. This effort seeks to realize the full potential of dynamic power conversion technologies for NASA’s space science and exploration missions.

Wilson, Scott↗
NASA NTRS2002

Systems Architecture for Fully Autonomous Space Missions

The NASA Goddard Space Flight Center is working to develop a revolutionary new system architecture concept in support of fully autonomous missions. As part of GSFC's contribution to the New Millenium Program (NMP) Space Technology 7 Autonomy and on-Board Processing (ST7-A) Concept Definition Study, the system incorporates the latest commercial Internet and software development ideas and extends them into NASA ground and space segment architectures. The unique challenges facing the exploration of remote and inaccessible locales and the need to incorporate corresponding autonomy technologies within reasonable cost necessitate the re-thinking of traditional mission architectures. A measure of the resiliency of this architecture in its application to a broad range of future autonomy missions will depend on its effectiveness in leveraging from commercial tools developed for the personal computer and Internet markets. Specialized test stations and supporting software come to past as spacecraft take advantage of the extensive tools and research investments of billion-dollar commercial ventures. The projected improvements of the Internet and supporting infrastructure go hand-in-hand with market pressures that provide continuity in research. By taking advantage of consumer-oriented methods and processes, space-flight missions will continue to leverage on investments tailored to provide better services at reduced cost. The application of ground and space segment architectures each based on Local Area Networks (LAN), the use of personal computer-based operating systems, and the execution of activities and operations through a Wide Area Network (Internet) enable a revolution in spacecraft mission formulation, implementation, and flight operations. Hardware and software design, development, integration, test, and flight operations are all tied-in closely to a common thread that enables the smooth transitioning between program phases. The application of commercial software development techniques lays the foundation for delivery of product-oriented flight software modules and models. Software can then be readily applied to support the on-board autonomy required for mission self-management. An on-board intelligent system, based on advanced scripting languages, facilitates the mission autonomy required to offload ground system resources, and enables the spacecraft to manage itself safely through an efficient and effective process of reactive planning, science data acquisition, synthesis, and transmission to the ground. Autonomous ground systems in turn coordinate and support schedule contact times with the spacecraft. Specific autonomy software modules on-board include mission and science planners, instrument and subsystem control, and fault tolerance response software, all residing within a distributed computing environment supported through the flight LAN. Autonomy also requires the minimization of human intervention between users on the ground and the spacecraft, and hence calls for the elimination of the traditional operations control center as a funnel for data manipulation. Basic goal-oriented commands are sent directly from the user to the spacecraft through a distributed internet-based payload operations "center". The ensuing architecture calls for the use of spacecraft as point extensions on the Internet. This paper will detail the system architecture implementation chosen to enable cost-effective autonomous missions with applicability to a broad range of conditions. It will define the structure needed for implementation of such missions, including software and hardware infrastructures. The overall architecture is then laid out as a common thread in the mission life cycle from formulation through implementation and flight operations.

Esper, Jamie↗
NASA NTRS2018

Plan Execution Interchange Language (PLEXIL) Software User's Manual

Plan Execution Interchange Language (PLEXIL) is a Core Flight System (or Core Flight Software) (cFS) based application, developed by the Autonomy Operating System project at NASA. cFS is open-source, reusable flight software, also developed by NASA and targeted to space missions. PLEXIL runs within the cFS framework, and is a wrapper integrating the open source PLEXIL Executive into the cFE (core Flight Executive) infrastructure. Software features include: Executes PLEXIL plans stored on local file system; Can be event-driven or clock-driven; and, Intended for "soft real time" discrete control.

Fry, Charles R.↗
NASA NTRS2008

Automated and Adaptive Mission Planning for Orbital Express

The Orbital Express space mission was a Defense Advanced Research Projects Agency (DARPA) lead demonstration of on-orbit satellite servicing scenarios, autonomous rendezvous, fluid transfers of hydrazine propellant, and robotic arm transfers of Orbital Replacement Unit (ORU) components. Boeing's Autonomous Space Transport Robotic Operations (ASTRO) vehicle provided the servicing to the Ball Aerospace's Next Generation Serviceable Satellite (NextSat) client. For communication opportunities, operations used the high-bandwidth ground-based Air Force Satellite Control Network (AFSCN) along with the relatively low-bandwidth GEO-Synchronous space-borne Tracking and Data Relay Satellite System (TDRSS) network. Mission operations were conducted out of the RDT&E Support Complex (RSC) at the Kirtland Air Force Base in New Mexico. All mission objectives were met successfully: The first of several autonomous rendezvous was demonstrated on May 5, 2007; autonomous free-flyer capture was demonstrated on June 22, 2007; the fluid and ORU transfers throughout the mission were successful. Planning operations for the mission were conducted by a team of personnel including Flight Directors, who were responsible for verifying the steps and contacts within the procedures, the Rendezvous Planners who would compute the locations and visibilities of the spacecraft, the Scenario Resource Planners (SRPs), who were concerned with assignment of communications windows, monitoring of resources, and sending commands to the ASTRO spacecraft, and the Mission planners who would interface with the real-time operations environment, process planning products and coordinate activities with the SRP. The SRP position was staffed by JPL personnel who used the Automated Scheduling and Planning ENvironment (ASPEN) to model and enforce mission and satellite constraints. The lifecycle of a plan began three weeks outside its execution on-board. During the planning timeframe, many aspects could change the plan, causing the need for re-planning. These variable factors, ranging from shifting contact times to ground-station closures and required maintenance times, are discussed along with the flexibility of the ASPEN tool to accommodate changes to procedures and the daily or long-range plan, which contributed to the success of the mission. This paper will present an introduction to ASPEN, a more in-depth discussion on its use on the Orbital Express mission, and other relative work. A description of ground operations after the SRP deliveries were made is included, and we briefly discuss lessons learned from the planning perspective and future work.

scheduling↗
NASA NTRS1994

Integrating O/S models during conceptual design, part 3

Space vehicles, such as the Space Shuttle, require intensive ground support prior to, during, and after each mission. Maintenance is a significant part of that ground support. All space vehicles require scheduled maintenance to ensure operability and performance. In addition, components of any vehicle are not one-hundred percent reliable so they exhibit random failures. Once detected, a failure initiates unscheduled maintenance on the vehicle. Maintenance decreases the number of missions which can be completed by keeping vehicles out of service so that the time between the completion of one mission and the start of the next is increased. Maintenance also requires resources such as people, facilities, tooling, and spare parts. Assessing the mission capability and resource requirements of any new space vehicle, in addition to performance specification, is necessary to predict the life cycle cost and success of the vehicle. Maintenance and logistics support has been modeled by computer simulation to estimate mission capability and resource requirements for evaluation of proposed space vehicles. The simulation was written with Simulation Language for Alternative Modeling II (SLAM II) for execution on a personal computer. For either one or a fleet of space vehicles, the model simulates the preflight maintenance checks, the mission and return to earth, and the post flight maintenance in preparation to be sent back into space. THe model enables prediction of the number of missions possible and vehicle turn-time (the time between completion of one mission and the start of the next) given estimated values for component reliability and maintainability. The model also facilitates study of the manpower and vehicle requirements for the proposed vehicle to meet its desired mission rate. This is the 3rd part of a 3 part technical report.

Ebeling, Charles E.↗
NASA NTRSDate not supplied

Integrating Planning, Diagnosis and Execution for Vehicle Systems Management

We describe a prototype Vehicle System Manager (VSM) for NASA’s Gateway, a human-capable spacecraft that will also be capable of autonomous operations. The VSM consists of an execution system, planner, and fault management system, integrated via an over-arching mission management compo- nent. We describe the VSM architecture and each of its com- ponents. We describe a series of use cases, centered on a spacecraft propulsive operation that can fail at different times, for different reasons, and how the VSM detects and responds to these failures. We show the VSM is capable of detecting faults and loss of capability, and subsequently replanning, in the presence of each failure scenario.

Planning↗
NASA NTRS2014

Maneuver Design for the Juno Mission: Inner Cruise

The Juno spacecraft launched in August 2011 and, following a successful Earth flyby in October 2013, is on course for a nominal orbit insertion at Jupiter in July 2016. This paper examines the design and execution of deterministic and statistical trajectory correction maneuvers during the first approximately 27 months of post-launch operations that defined the "Inner Cruise" phase of the Juno mission. Topics of emphasis include the two deep space maneuvers, Earth flyby altitude biasing strategy, and the sequence of trajectory correction maneuvers executed in the weeks prior to the successful Earth gravity assist.

Pavlak, Thomas A.↗
NASA NTRSDate not supplied

Navigation Doppler Lidar

A Doppler lidar has been developed by NASA as an alternative to radars for providing velocity and altitude data to landing vehicles. Future robotic and manned missions to planetary bodies demand precise ground-relative velocity vector and altitude data to execute complex descent maneuvers for safe, soft and pinpoint landing at a pre-designated site. This lidar sensor, referred to as Navigation Doppler Lidar (NDL), provides velocity and altitude data from over five kilometers altitude to within a few cm/sec and tens of centimeters precision, respectively. NDL technology will be demonstrated on two lunar landing missions this year that will serve as precursors for large robotic and manned landing missions to the Moon, Mars, and other solar system destinations. NDL can also benefit terrestrial aerial vehicles that cannot rely on the GPS for position and velocity data or require precision data relative to local ground.

Doppler Lidar↗
NASA NTRS2006

Pilot Navigation Errors on the Airport Surface: Identifying Contributing Factors and Mitigating Solutions

A taxonomy of navigation errors (pilot deviations) during taxi operations was developed that defines 3 classes of errors: planning, decision, and execution errors. This taxonomy was applied to error data from 2 full-mission simulation studies that included trials that replicated current-day operations and trials with advanced cockpit technologies including datalink, electronic moving maps (EMM), and head-up displays (HUDs). Pilots committed navigation errors on 17% of current-day operations trials (in low-visibility and night), distributed roughly equally across the 3 error classes. Each error class was associated with a unique set of contributing factor s and mitigating solutions. Planning errors were mitigated by technologies that provided an unambiguous record of the clearance (datalink and the EMM, which possessed a text-based clearance). Decision errors were mitigated by technologies that provided both local and global awareness including information about the distance to and direction of the next turn, current township location, and a graphical depiction of the route (as provided by the EMM and HUD together). Execution errors were best mitigated by the HUD, which disambiguated the environment and depicted the clear ed taxi route. Implications for technology design and integration are provided.

Hooey, Becky L.↗