SEARCH · Search NASA

Results for “execution control”

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.

SourceResearch connectionFrom yearThrough year

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

At least 649 records · Page 36

All sources NASA NTRS DOE OSTI

NASA NTRS1985

Ground test experiment for large space structures

In recent years a new body of control theory has been developed for the design of control systems for Large Space Structures (LSS). The problems of testing this theory on LSS hardware are aggravated by the expense and risk of actual in orbit tests. Ground tests on large space structures can provide a proving ground for candidate control systems, but such tests require a unique facility for their execution. The current development of such a facility at the NASA Marshall Space Flight Center (MSFC) is the subject of this report.

Tollison, D. K.↗

NASA NTRS1986

An evaluation of the documented requirements of the SSP UIL and a review of commercial software packages for the development and testing of UIL prototypes

A review was conducted of software packages currently on the market which might be integrated with the interface language and aid in reaching the objectives of customization, standardization, transparency, reliability, maintainability, language substitutions, expandability, portability, and flexibility. Recommendations are given for best choices in hardware and software acquisition for inhouse testing of these possible integrations. Software acquisition in the line of tools to aid expert-system development and/or novice program development, artificial intelligent voice technology and touch screen or joystick or mouse utilization as well as networking were recommended. Other recommendations concerned using the language Ada for the user interface language shell because of its high level of standardization, structure, and ability to accept and execute programs written in other programming languages, its DOD ownership and control, and keeping the user interface language simple so that multiples of users will find the commercialization of space within their realm of possibility which is, after all, the purpose of the Space Station.

Gill, Esther Naomi↗

NASA NTRS1991

Validating system-level error recovery for spacecraft

The system-level software onboard a spacecraft is responsible for recovery from communication, thermal, power, and computer-health anomalies that may occur. The recovery must occur without disrupting any critical scientific or engineering activity that is executing at the time of the error. Thus, the error-recovery software may have to execute concurrently with the ongoing acquisition of scientific data or with spacecraft maneuvers. This paper provides a technique by which the rules that constrain the concurrent execution of these processes can be modeled in a graph. An algorithm is described that uses this model to validate that the constraints hold for all concurrent executions of the error-recovery softwave with the softwave that controls the science and engineering events on the spacecraft.

Lutz, Robyn R.↗

NASA NTRS1992

Estimation and enhancement of real-time software reliability through mutation analysis

A simulation-based technique for obtaining numerical estimates of the reliability of N-version, real-time software is presented. An extended stochastic Petri net is employed to represent the synchronization structure of N versions of the software, where dependencies among versions are modeled through correlated sampling of module execution times. Test results utilizing specifications for NASA's planetary lander control software indicate that mutation-based testing could hold greater potential for enhancing reliability than the desirable but perhaps unachievable goal of independence among N versions.

Geist, Robert↗

NASA NTRS1993

Constraint checking during error recovery

The system-level software onboard a spacecraft is responsible for recovery from communication, power, thermal, and computer-health anomalies that may occur. The recovery must occur without disrupting any critical scientific or engineering activity that is executing at the time of the error. Thus, the error-recovery software may have to execute concurrently with the ongoing acquisition of scientific data or with spacecraft maneuvers. This work provides a technique by which the rules that constrain the concurrent execution of these processes can be modeled in a graph. An algorithm is described that uses this model to validate that the constraints hold for all concurrent executions of the error-recovery software with the software that controls the science and engineering activities of the spacecraft. The results are applicable to a variety of control systems with critical constraints on the timing and ordering of the events they control.

Lutz, Robyn R.↗

NASA NTRS1996

Sequence-of-events-driven automation of the deep space network

In February 1995, sequence-of-events (SOE)-driven automation technology was demonstrated for a Voyager telemetry downlink track at DSS 13. This demonstration entailed automated generation of an operations procedure (in the form of a temporal dependency network) from project SOE information using artificial intelligence planning technology and automated execution of the temporal dependency network using the link monitor and control operator assistant system. This article describes the overall approach to SOE-driven automation that was demonstrated, identifies gaps in SOE definitions and project profiles that hamper automation, and provides detailed measurements of the knowledge engineering effort required for automation.

Hill, R., Jr.↗

NASA NTRS1997

A Users Guide for the NASA ANOPP Propeller Analysis System

The purpose of this report is to document improvements to the Propeller Analysis System of the Aircraft Noise Prediction Program (PAS-ANOPP) and to serve as a users guide. An overview of the functional modules and modifications made to the Propeller ANOPP system are described. Propeller noise predictions are made by executing a sequence of functional modules through the use of ANOPP control statements. The most commonly used ANOPP control statements are discussed with detailed examples demonstrating the use of each control statement. Originally, the Propeller Analysis System included the angle-of-attack only in the performance module. Recently, modifications have been made to also include angle-of-attack in the noise prediction module. A brief description of PAS prediction capabilities is presented which illustrate the input requirements necessary to run the code by way of ten templates. The purpose of the templates are to provide PAS users with complete examples which can be modified to serve their particular purposes. The examples include the use of different approximations in the computation of the noise and the effects of synchrophasing. Since modifications have been made to the original PAS-ANOPP, comparisons of the modified ANOPP and wind tunnel data are also included. Two appendices are attached at the end of this report which provide useful reference material. One appendix summarizes the PAS functional modules while the second provides a detailed discussion of the TABLE control statement.

Nguygen, L. Cathy↗

NASA NTRS1996

Sequence-of-Events-Driven Automation of the Deep Space Network

Hill, R., Jr.↗

NASA NTRS2002

Ground and Flight Evaluation of a Small-Scale Inflatable-Winged Aircraft

A small-scale, instrumented research aircraft was flown to investigate the night characteristics of innersole wings. Ground tests measured the static structural characteristics of the wing at different inflation pressures, and these results compared favorably with analytical predictions. A research-quality instrumentation system was assembled, largely from commercial off-the-shelf components, and installed in the aircraft. Initial flight operations were conducted with a conventional rigid wing having the same dimensions as the inflatable wing. Subsequent flights were conducted with the inflatable wing. Research maneuvers were executed to identify the trim, aerodynamic performance, and longitudinal stability and control characteristics of the vehicle in its different wing configurations. For the angle-of-attack range spanned in this flight program, measured flight data demonstrated that the rigid wing was an effective simulator of the lift-generating capability of the inflatable wing. In-flight inflation of the wing was demonstrated in three flight operations, and measured flight data illustrated the dynamic characteristics during wing inflation and transition to controlled lifting flight. Wing inflation was rapid and the vehicle dynamics during inflation and transition were benign. The resulting angles of attack and of sideslip ere small, and the dynamic response was limited to roll and heave motions.

Murray, James E.↗

NASA NTRS2002

Advanced Computing Technologies for Rocket Engine Propulsion Systems: Object-Oriented Design with C++

This document explores the use of advanced computer technologies with an emphasis on object-oriented design to be applied in the development of software for a rocket engine to improve vehicle safety and reliability. The primary focus is on phase one of this project, the smart start sequence module. The objectives are: 1) To use current sound software engineering practices, object-orientation; 2) To improve on software development time, maintenance, execution and management; 3) To provide an alternate design choice for control, implementation, and performance.

Gete Bekele↗

NASA NTRS2001

Autonomy technology at JPL

This paper and exhibit describes the on-going research activities, plans and products of the Autonomy Technology program at NASA Jet Propulsion Laboratory. In this paper, we briefly describe the areas of Mission Planning and Execution, Distributed Autonomous Systems, Science Data Understanding, and Autonomous Guidance and Control.

autonomous rovers distributed systems planning con↗

NASA NTRS2005

Study on the Station Keeping Maintenance for the TPF Mission

The main goal of this paper is to extend the results of Gomez et al, 2001, related to the execution of the formation manoeuvres of the TPF constellation, including the controls for the station keeping and allowing a greater flexibility in the basic manoeuvres to be done by the formation.

terrestrial planet finder (TPF)↗

NASA NTRS2008

A Flexible Evolvable Architecture for Constellation Mission Systems User Applications

While simulating a complex set of repair tasks to be performed by EVA crewmembers on an upcoming mission, flight controllers and astronauts determine that the repair will take much longer than originally anticipated. All equipment in the vicinity of the worksite must be powered off to maintain a safe environment for the astronauts. Because heater power will be unavailable, several critical components will now be at risk of freezing and permanent damage. If an impending thermal violation is detected, Mission Control will have very limited time to react. Therefore, flight controllers must not only modify their procedures to account for these risks, they must also incorporate into their displays outputs from thermal models, alternate temperature measurements, new alarm limits, and emergency power-on commands to enable the detection and response to freezing conditions. Current software for mission control systems makes scenarios like this difficult to address. Given the time frame for modifying software, operations teams are left with labor-intensive operational workarounds as their only options. NASA Ames Research Center (ARC) and NASA Johnson Space Center (JSC) are collaborating on the development of a flexible software system for mission operations that will enable greater user flexibility than has been available to date. Using composable software, end users in the scenario described above could recompose procedures and command and control displays to allow flight controllers to monitor temperature measurements, identify time-critical conditions, and execute the procedures required to respond to these conditions before flight hardware is permanently damaged.

Trimble, Jay P.↗

NASA NTRS2010

AutoGNC Testbed

A simulation testbed architecture was developed and implemented for the integration, test, and development of a TRL-6 flight software set called Auto- GNC. The AutoGNC software will combine the TRL-9 Deep Impact AutoNAV flight software suite, the TRL-9 Virtual Machine Language (VML) executive, and the TRL-3 G-REX guidance, estimation, and control algorithms. The Auto- GNC testbed was architected to provide software interface connections among the AutoNAV and VML flight code written in C, the G-REX algorithms in MATLAB and C, stand-alone image rendering algorithms in C, and other Fortran algorithms, such as the OBIRON landmark tracking suite. The testbed architecture incorporates software components for propagating a high-fidelity truth model of the environment and the spacecraft dynamics, along with the flight software components for onboard guidance, navigation, and control (GN&C). The interface allows for the rapid integration and testing of new algorithms prior to development of the C code for implementation in flight software. This testbed is designed to test autonomous spacecraft proximity operations around small celestial bodies, moons, or other spacecraft. The software is baselined for upcoming comet and asteroid sample return missions. This architecture and testbed will provide a direct improvement upon the onboard flight software utilized for missions such as Deep Impact, Stardust, and Deep Space 1.

Carson, John M., III↗

NASA NTRS2011

Space Vehicle Powerdown Philosophies Derived from the Space Shuttle Program

In spaceflight, electrical power is a vital but limited resource. Almost every spacecraft system, from avionics to life support systems, relies on electrical power. Since power can be limited by the generation system s performance, available consumables, solar array shading, or heat rejection capability, vehicle power management is a critical consideration in spacecraft design, mission planning, and real-time operations. The purpose of this paper is to capture the powerdown philosophies used during the Space Shuttle Program. This paper will discuss how electrical equipment is managed real-time to adjust the overall vehicle power level to ensure that systems and consumables will support changing mission objectives, as well as how electrical equipment is managed following system anomalies. We will focus on the power related impacts of anomalies in the generation systems, air and liquid cooling systems, and significant environmental events such as a fire, decrease in cabin pressure, or micrometeoroid debris strike. Additionally, considerations for executing powerdowns by crew action or by ground commands from Mission Control will be presented. General lessons learned from nearly 30 years of Space Shuttle powerdowns will be discussed, including an in depth case-study of STS-117. During this International Space Station (ISS) assembly mission, a failure of computers controlling the ISS guidance, navigation, and control system required that the Space Shuttle s maneuvering system be used to maintain attitude control. A powerdown was performed to save power generation consumables, thus extending the docked mission duration and allowing more time to resolve the issue.

Willsey, Mark↗

NASA NTRS2011

Remote Infrared Imaging of the Space Shuttle During Hypersonic Flight: HYTHIRM Mission Operations and Coordination

The Hypersonic Thermodynamic Infrared Measurements (HYTHIRM) project has been responsible for obtaining spatially resolved, scientifically calibrated in-flight thermal imagery of the Space Shuttle Orbiter during reentry. Starting with STS-119 in March of 2009 and continuing through to the majority of final flights of the Space Shuttle, the HYTHIRM team has to date deployed during seven Shuttle missions with a mix of airborne and ground based imaging platforms. Each deployment of the HYTHIRM team has resulted in obtaining imagery suitable for processing and comparison with computational models and wind tunnel data at Mach numbers ranging from over 18 to under Mach 5. This paper will discuss the detailed mission planning and coordination with the NASA Johnson Space Center Mission Control Center that the HYTHIRM team undergoes to prepare for and execute each mission.

Schwartz, Richard J.↗

NASA NTRS2011

ISS Operations Cost Reductions Through Automation of Real-Time Planning Tasks

In 2007 the Johnson Space Center s Mission Operations Directorate (MOD) management team challenged their organizations to find ways to reduce the cost of operations for supporting the International Space Station (ISS) in the Mission Control Center (MCC). Each MOD organization was asked to define and execute projects that would help them attain cost reductions by 2012. The MOD Operations Division Flight Planning Branch responded to this challenge by launching several software automation projects that would allow them to greatly improve console operations and reduce ISS console staffing and intern reduce operating costs. These tasks ranged from improving the management and integration mission plan changes, to automating the uploading and downloading of information to and from the ISS and the associated ground complex tasks that required multiple decision points. The software solutions leveraged several different technologies including customized web applications and implementation of industry standard web services architecture; as well as engaging a previously TRL 4-5 technology developed by Ames Research Center (ARC) that utilized an intelligent agent-based system to manage and automate file traffic flow, archive data, and generate console logs. These projects to date have allowed the MOD Operations organization to remove one full time (7 x 24 x 365) ISS console position in 2010; with the goal of eliminating a second full time ISS console support position by 2012. The team will also reduce one long range planning console position by 2014. When complete, these Flight Planning Branch projects will account for the elimination of 3 console positions and a reduction in staffing of 11 engineering personnel (EP) for ISS.

Hall, Timothy A.↗

NASA NTRS2019

Autonomous Operating System (AOS)

The Autonomy Operating System (AOS) is a software system that enables core capabilities for the autonomous operations for an unmanned aircraft. It is based on the NASA cFS system and provides a higher-level layer of infrastructure and applications for the execution of flight plans, natural-language communication with Air Traffic Control, Diagnostics, Prognostics, and contingency planning.

Lowry, Michael R.↗