Search NASA⌕ Search

SEARCH · Search NASA

Results for “Flight 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 1,549 records · Page 86

Lessons Learned in the Livingstone 2 on Earth Observing One Flight Experiment

The Livingstone 2 (L2) model-based diagnosis software is a reusable diagnostic tool for monitoring complex systems. In 2004, L2 was integrated with the JPL Autonomous Sciencecraft Experiment (ASE) and deployed on-board Goddard's Earth Observing One (EO-1) remote sensing satellite, to monitor and diagnose the EO-1 space science instruments and imaging sequence. This paper reports on lessons learned from this flight experiment. The goals for this experiment, including validation of minimum success criteria and of a series of diagnostic scenarios, have all been successfully net. Long-term operations in space are on-going, as a test of the maturity of the system, with L2 performance remaining flawless. L2 has demonstrated the ability to track the state of the system during nominal operations, detect simulated abnormalities in operations and isolate failures to their root cause fault. Specific advances demonstrated include diagnosis of ambiguity groups rather than a single fault candidate; hypothesis revision given new sensor evidence about the state of the system; and the capability to check for faults in a dynamic system without having to wait until the system is quiescent. The major benefits of this advanced health management technology are to increase mission duration and reliability through intelligent fault protection, and robust autonomous operations with reduced dependency on supervisory operations from Earth. The work-load for operators will be reduced by telemetry of processed state-of-health information rather than raw data. The long-term vision is that of making diagnosis available to the onboard planner or executive, allowing autonomy software to re-plan in order to work around known component failures. For a system that is expected to evolve substantially over its lifetime, as for the International Space Station, the model-based approach has definite advantages over rule-based expert systems and limit-checking fault protection systems, as these do not scale well. The model-based approach facilitates reuse of the L2 diagnostic software; only the model of the system to be diagnosed and telemetry monitoring software has to be rebuilt for a new system or expanded for a growing system. The hierarchical L2 model supports modularity and expendability, and as such is suitable solution for integrated system health management as envisioned for systems-of-systems.

Hayden, Sandra C.↗

The Spartan attitude control system - Ground support computer

The Spartan Attitude Control System (ACS) contains a command and control computer. This computer is optimized for the activities of the flight and contains very little human interface hardware and software. The computer system provides the technicians testing of Spartan ACS with a convenient command-oriented interface to the flight ACS computer. The system also decodes and time tags data automatically sent out by the flight computer as key events occur. The duration and magnitude of all system maneuvers is also derived and displayed by this system. The Ground Support Computer is also the primary Ground Support Equipment for the flight sequencer which controls all payload maneuvers, and long term program timing.

Schnurr, R. G., Jr.↗

Schedule Analysis Software Saves Time for Project Planners

Since the early 2000s, a resource management team at Marshall Space Flight Center has developed and improved the Schedule Test and Assessment Tool, a software add-on capable of analyzing, summarizing, and finding logic gaps in project schedules. Companies like Lanham, Maryland-based Vantage Systems Inc. use the tool to manage NASA projects, but it has also been released for free to more than 200 US companies, agencies, and other entities.

Source record↗

Mission Control Center operations for the Space Transportation System

Orbital flight tests of the Space Shuttle Program involved three types of activities, including classic flight testing of the vehicle hardware and software, operational procedures evaluation and development, and performance of payload mission operations. This combination of activities required a capability of the Mission Control Center (MCC) to provide thorough support to the Orbiter and its crew across a broad spectrum of activities. Attention is given to MCC organization, the general functions performed by the MCC teams, a flight support description, the motivation for a change in MCC operations, support elements, orbit phase functions, and dynamic flight phase functions. It is pointed out that the MCC facilities for the operational mode of support will not be fully implemented until 1984.

Frank, M. P.↗

Transportable Payload Operations Control Center reusable software: Building blocks for quality ground data systems

The Mission Operations Division (MOD) at Goddard Space Flight Center builds Mission Operations Centers which are used by Flight Operations Teams to monitor and control satellites. Reducing system life cycle costs through software reuse has always been a priority of the MOD. The MOD's Transportable Payload Operations Control Center development team established an extensive library of 14 subsystems with over 100,000 delivered source instructions of reusable, generic software components. Nine TPOCC-based control centers to date support 11 satellites and achieved an average software reuse level of more than 75 percent. This paper shares experiences of how the TPOCC building blocks were developed and how building block developer's, mission development teams, and users are all part of the process.

Mahmot, Ron↗

Robustness Analysis and Reliable Flight Regime Estimation of an Integrated Resilent Control System for a Transport Aircraft

Formal robustness analysis of aircraft control upset prevention and recovery systems could play an important role in their validation and ultimate certification. As a part of the validation process, this paper describes an analysis method for determining a reliable flight regime in the flight envelope within which an integrated resilent control system can achieve the desired performance of tracking command signals and detecting additive faults in the presence of parameter uncertainty and unmodeled dynamics. To calculate a reliable flight regime, a structured singular value analysis method is applied to analyze the closed-loop system over the entire flight envelope. To use the structured singular value analysis method, a linear fractional transform (LFT) model of a transport aircraft longitudinal dynamics is developed over the flight envelope by using a preliminary LFT modeling software tool developed at the NASA Langley Research Center, which utilizes a matrix-based computational approach. The developed LFT model can capture original nonlinear dynamics over the flight envelope with the ! block which contains key varying parameters: angle of attack and velocity, and real parameter uncertainty: aerodynamic coefficient uncertainty and moment of inertia uncertainty. Using the developed LFT model and a formal robustness analysis method, a reliable flight regime is calculated for a transport aircraft closed-loop system.

Shin, Jong-Yeob↗

The Spacelab Experiment Interface Device (SEID)

The Spacelab experiment interface device (SEID) is described which simulates the electrical, and logical connections of the Spacelab remote acquisition unit (RAU), the interface functions of the Spacelab experiment computer software, and the electrical aspects of the high rate multiplexer. Simulated RAU interfaces include PCM serial channels (up to four), user time clock (UTC), flexible inputs (up to 128) and discrete outputs (up to 64). Connectors are logically compatible with the rau. be instructed to execute sequences of input/output commands to the RAU, similar to those performed during flight. This approximation of the experiment computer software is adequate to detect interface problems and prevent these from occurring during Spacelab payload integration. The SEID hardware is a microprocessor based system, utilizing an 8085 microprocessor with 6K of PROM and 4K of static RAM. The basic unit is augmented with an LSI-11 microcomputer to provide disk storage and a more dynamic environment for generation of control data. A simulation of the general monitoring loop is provided to emulate Spacelab system timing.

Kallus, R.↗

Software Process Assessment (SPA)

NASA's environment mirrors the changes taking place in the nation at large, i.e. workers are being asked to do more work with fewer resources. For software developers at NASA's Goddard Space Flight Center (GSFC), the effects of this change are that we must continue to produce quality code that is maintainable and reusable, but we must learn to produce it more efficiently and less expensively. To accomplish this goal, the Data Systems Technology Division (DSTD) at GSFC is trying a variety of both proven and state-of-the-art techniques for software development (e.g., object-oriented design, prototyping, designing for reuse, etc.). In order to evaluate the effectiveness of these techniques, the Software Process Assessment (SPA) program was initiated. SPA was begun under the assumption that the effects of different software development processes, techniques, and tools, on the resulting product must be evaluated in an objective manner in order to assess any benefits that may have accrued. SPA involves the collection and analysis of software product and process data. These data include metrics such as effort, code changes, size, complexity, and code readability. This paper describes the SPA data collection and analysis methodology and presents examples of benefits realized thus far by DSTD's software developers and managers.

Rosenberg, Linda H.↗

Crew Health and Performance Integrated Data Architecture (CHP-IDA) Project

BACKGROUND: Future Human Exploration missions introduce a new paradigm as crews move further from the resupply and near real-time ground support typical of Low Earth Orbit missions today. Without immediate support from ground-based personnel, exploration crews will be more reliant on inflight data and technology to respond to emergencies and anomalies. A data architecture to support a new generation of technologies, employing advanced analytical and predictive modeling techniques, is needed to enable crew autonomy. OVERVIEW: The Crew Health and Performance Integrated Data Architecture (CHP-IDA) project funded by NASA’s Exploration Medical Integrated Product Team (XMIPT) is laying a foundation for future in-flight informatics by providing a back-end architecture for collecting, storing, and integrating multiple sources of data generated by and around the crew. CHP-IDA provides a platform for common data models and Application Programming Interfaces to access, integrate, process, and display CHP data (e.g., environmental, exercise, medical, sleep, performance, etc.). This will facilitate the increased situation awareness and decision support required by the crew and remote support of exploration missions. This presentation will describe the currently ongoing effort to develop and evaluate a path-to-flight concept of the CHP-IDA software and its core capabilities. Current integrations will be discussed, including analytics for Extravehicular Activity metabolic rate and data ingestion from a multi-functional integrated medical device. The presentation will also provide examples of scenarios used to demonstrate the CHP-IDA through human-in-the-loop test bed activities as well as examples of appropriate system performance metrics. DISCUSSION: Today, in-flight data is often siloed, unsynchronized, and largely inaccessible in real time. Many data sets require manual entry and/or data transfer between vehicles and the ground. These issues contribute to risks in supporting exploration medical capabilities. The CHP-IDA is a back-end data system providing core capabilities needed for timely and meaningful data insights across CHP domains to crew and remote personnel to enable increased crew autonomy. Future work includes collaboration with additional CHP domains, new technology integrations, and further demonstrations of the IDA within different vehicle and communication latency contexts. LEARNING OBJECTIVES 1. The audience will understand that the CHP-IDA is a back-end system, providing a platform to facilitate access, promote decision tools, and provide meaningful insights to crew and to remote stakeholders during exploration missions. 2. The audience will gain insight into human-centered research and activities used to discover CHP domain data needs and pain points and how this information is used to guide development of the IDA.

Exploration↗

Orbit Software Suite

Orbit Software Suite is used to support a variety of NASA/DM (Dependable Multiprocessor) mission planning and analysis activities on the IPS (Intrusion Prevention System) platform. The suite of Orbit software tools (Orbit Design and Orbit Dynamics) resides on IPS/Linux workstations, and is used to perform mission design and analysis tasks corresponding to trajectory/ launch window, rendezvous, and proximity operations flight segments. A list of tools in Orbit Software Suite represents tool versions established during/after the Equipment Rehost-3 Project.

Osgood, Cathy↗

Balloon Ascent: 3-D Simulation Tool for the Ascent and Float of High-Altitude Balloons

The BalloonAscent balloon flight simulation code represents a from-scratch development using Visual Basic 5 as the software platform. The simulation code is a transient analysis of balloon flight, predicting the skin and gas temperatures along with the 3-D position and velocity in a time and spatially varying environment. There are manual and automated controls for gas valving and the dropping of ballast. Also, there are many handy calculators, such as appropriate free lift, and steady-state thermal solutions with temperature gradients. The strength of this simulation model over others in the past is that the infrared environment is deterministic rather than guessed at. The ground temperature is specified along with the emissivity, which creates a ground level IR environment that is then partially absorbed as it travels upward through the atmosphere to the altitude of the balloon.

Farley, Rodger E.↗

Agile Development Methods for Space Operations

Main stream industry software development practice has gone from a traditional waterfall process to agile iterative development that allows for fast response to customer inputs and produces higher quality software at lower cost. How can we, the space ops community, adopt state of the art software development practice, achieve greater productivity at lower cost, and maintain safe and effective space flight operations? At NASA Ames, we are developing Mission Control Technologies Software, in collaboration with Johnson Space Center (JSC) and, more recently, the Jet Propulsion Laboratory (JPL).

Trimble, Jay↗

Ares I-X: On the Threshold of Exploration

Ares I-X, the first flight of the Ares I crew launch vehicle, is less than a year from launch. Ares I-X will test the flight characteristics of Ares I from liftoff to first stage separation and recovery. The flight also will demonstrate the computer hardware and software (avionics) needed to control the vehicle; deploy the parachutes that allow the first stage booster to land in the ocean safely; measure and control how much the rocket rolls during flight; test and measure the effects of first stage separation; and develop and try out new ground handling and rocket stacking procedures in the Vehicle Assembly Building (VAB) and first stage recovery procedures at Kennedy Space Center (KSC) in Florida. All Ares I-X major elements have completed their critical design reviews, and are nearing final fabrication. The first stage--four-segment solid rocket booster from the Space Shuttle inventory--incorporates new simulated forward structures to match the Ares I five-segment booster. The upper stage, Orion crew module, and launch abort system will comprise simulator hardware that incorporates developmental flight instrumentation for essential data collection during the mission. The upper stage simulator consists of smaller cylindrical segments, which were transported to KSC in fall 2008. The crew module and launch abort system simulator were shipped in December 2008. The first stage hardware, active roll control system (RoCS), and avionics components will be delivered to KSC in 2009. This paper will provide detailed statuses of the Ares I-X hardware elements as NASA's Constellation Program prepares for this first flight of a new exploration era in the summer of 2009.

Davis, Stephan R.↗

Parameter identification and modeling of longitudinal aerodynamics

Using a comprehensive flight test database and a parameter identification software program produced at NASA Ames Research Center, a math model of the longitudinal aerodynamics of the Harrier aircraft was formulated. The identification program employed the equation error method using multiple linear regression to estimate the nonlinear parameters. The formulated math model structure adhered closely to aerodynamic and stability/control theory, particularly with regard to compressibility and dynamic manoeuvring. Validation was accomplished by using a three degree-of-freedom nonlinear flight simulator with pilot inputs from flight test data. The simulation models agreed quite well with the measured states. It is important to note that the flight test data used for the validation of the model was not used in the model identification.

Aksteter, J. W.↗

Collaborative research on V/STOL control system/cockpit display tradeoffs under the NASA/MOD joint aeronautical program

Summarized here are activities that have taken place from 1979 to the present in a collaborative program between NASA Ames Research Center and the Royal Aerospace Establishment (now Defence Research Agency), Bedford on flight control system and cockpit display tradeoffs for low-speed and hover operations of future V/STOL aircraft. This program was created as Task 8A of the Joint Aeronautical Program between NASA in the United States and the Ministry of Defence (Procurement Executive) in the United Kingdom. The program was initiated based on a recognition by both parties of the strengths of the efforts of their counterparts and a desire to participate jointly in future simulation and flight experiments. In the ensuing years, teams of NASA and RAE engineers and pilots have participated in each other's simulation experiments to evaluate control and display concepts and define design requirements for research aircraft. Both organizations possess Harrier airframes that have undergone extensive modification to provide in-flight research capabilities in the subject areas. Both NASA and RAE have profited by exchanges of control/display concepts, design criteria, fabrication techniques, software development and validation, installation details, and ground and flight clearance techniques for their respective aircraft. This collaboration has permitted the two organizations to achieve jointly substantially more during the period than if they had worked independently. The two organizations are now entering the phase of flight research for the collaborative program as currently defined.

Franklin, J. A.↗

Role of simulation and emulation in the development of Shuttle-Centaur (STS-Centaur)

To support the task of integrating the Centaur liquid-fueled upper-stage space vehicle into the space shuttle program. A system to simulate and emulate the STS-Centaur avionic flight system and its supporting ground control and checkout equipment was selected and designated the systems integration facility (SIF). Located in San Diego, California, the SIF is composed of integrated simulators that form a composite control system complement to the STS-Centaur airborne and avionic support equipment. An off-line capability to verify the system design of the Centaur airborne support equipment (CASE) and the Centaur avionic flight system is provided as well as a realistic medium for the development and integration of ground checkout and airborne control software programs. Each simulator is composed of prototype hardware, where feasible, to maximize configuration likeness. Where emulated flight or ground hardware is used, it provides physical characteristics (loads, signals, etc.) equivalent to those of the flight hardware. The hardware and software implementation of the SIF are described.

Gordan, A. L.↗

Detailed design of a Ride Quality Augmentation System for commuter aircraft

The design of a Ride Quality Augmentation System (RQAS) for commuter aircraft is documented. The RQAS is designed for a Cessna 402B, an 8 passenger prop twin representative to this class of aircraft. The purpose of the RQAS is the reduction of vertical and lateral accelerations of the aircraft due to atmospheric turbulence by the application of active control. The detailed design of the hardware (the aircraft modifications, the Ride Quality Instrumentation System (RQIS), and the required computer software) is examined. The aircraft modifications, consisting of the dedicated control surfaces and the hydraulic actuation system, were designed at Cessna Aircraft by Kansas University-Flight Research Laboratory. The instrumentation system, which consist of the sensor package, the flight computer, a Data Acquisition System, and the pilot and test engineer control panels, was designed by NASA-Langley. The overall system design and the design of the software, both for flight control algorithms and ground system checkout are detailed. The system performance is predicted from linear simulation results and from power spectral densities of the aircraft response to a Dryden gust. The results indicate that both accelerations are possible.

Suikat, Reiner↗

Software Design Methodology Migration for a Distributed Ground System

The Marshall Space Flight Center's (MSFC) Payload Operations Center (POC) ground system has been developed and has evolved over a period of about 10 years. During this time the software processes have migrated from more traditional to more contemporary development processes. The new Software processes still emphasize requirements capture, software configuration management, design documenting, and making sure the products that have been developed are accountable to initial requirements. This paper will give an overview of how the Software Process have evolved highlighting the positives as well as the negatives. In addition, we will mention the COTS tools that have been integrated into the processes and how the COTS have provided value to the project .

Ritter, George↗