Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “mission 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 991 records · Page 55
All sourcesNASA NTRSDOE OSTI
NASA NTRS1972

Space shuttle orbiter guidance, naviagation and control software functional requirements: Horizontal flight operations

The shuttle GN&C software functions for horizontal flight operations are defined. Software functional requirements are grouped into two categories: first horizontal flight requirements and full mission horizontal flight requirements. The document privides the intial step in the shuttle GN&C software design process. It also serves as a management tool to identify analyses which are required to define requirements.

Source record↗
NASA NTRS2002

Software Safety Assurance of Programmable Logic

Programmable Logic (PLC, FPGA, ASIC) devices are hybrids - hardware devices that are designed and programmed like software. As such, they fall in an assurance gray area. Programmable Logic is usually tested and verified as hardware, and the software aspects are ignored, potentially leading to safety or mission success concerns. The objective of this proposal is to first determine where and how Programmable Logic (PL) is used within NASA and document the current methods of assurance. Once that is known, raise awareness of the PL software aspects within the NASA engineering community and provide guidance for the use and assurance of PL form a software perspective.

Berens, Kalynnda↗
NASA NTRS2004

The impact of organizational structure on flight software cost risk

This paper summarizes the final results of the follow-up study updating the estimated software effort growth for those projects that were still under development and including an evaluation of the roles versus observed cost risk for the missions included in the original study which expands the data set to thirteen missions.

software cost↗
NASA NTRS1973

Maneuver analysis

The maneuver analysis for the Mariner 9 mission, both prelaunch and in-flight, was different from that of previous Mariners because of the requirement to insert the spacecraft into orbit about Mars and to trim the orbit to an unprecedented accuracy. The most apparent differences were in the spacecraft design, the software development, and the maneuver strategy required for each phase of the mission. The analysis that was performed and the software that was developed, with emphasis on the maneuver strategy and actual in-flight results are described.

Mitchell, R. T.↗
NASA NTRS2005

You Can't Get There From Here! Problems and Potential Solutions in Developing New Classes of Complex Systems

The explosion of capabilities and new products within the sphere of Information Technology (IT) has fostered widespread, overly optimistic opinions regarding the industry, based on common but unjustified assumptions of quality and correctness of software. These assumptions are encouraged by software producers and vendors, who at this late date have not succeeded in finding a way to overcome the lack of an automated, mathematically sound way to develop correct systems from requirements. NASA faces this dilemma as it envisages advanced mission concepts that involve large swarms of small spacecraft that will engage cooperatively to acheve science goals. Such missions entail levels of complexity that beg for new methods for system development far beyond today's methods, which are inadequate for ensuring correct behavior of large numbers of interacting intelligent mission elements. New system development techniques recently devised through NASA-led research will offer some innovative approaches to achieving correctness in complex system development, including autonomous swarm missions that exhibit emergent behavior, as well as general software products created by the computing industry.

Hinchey, Michael G.↗
NASA NTRS1986

MCC flight operations automation of STS orbiter systems monitoring

The integration of new capabilities into the Mission Control Center at the Johnson Space Center in Houston, Texas in order to improve the data monitoring and analysis of the STS is discussed. User interface application software and systems, such as the flight data file Shuttle mission simulator and failure analysis program, to be utilized for flight operations automation are examined. Consideration is given to task automation, the trend monitoring system, the data retrieval system, and the launch processing system. The development and functions of the Shuttle data analysis system, which is to operate in real time, are described.

Bates, William V., Jr.↗
NASA NTRS1996

The Impact of Information Technology on the Design, Development, and Implementation of a Lunar Exploration Mission

From the beginning to the present expeditions to the Moon have involved a large investment of human labor. This has been true for all aspects of the process, from the initial design of the mission, whether scientific or technological, through the development of the instruments and the spacecraft, to the flight and operational phases. In addition to the time constraints that this situation imposes, there is also a significant cost associated with the large labor costs. As a result lunar expeditions have been limited to a few robotic missions and the manned Apollo program missions of the 1970s. With the rapid rise of the new information technologies, new paradigms are emerging that promise to greatly reduce both the time and cost of such missions. With the rapidly increasing capabilities of computer hardware and software systems, as well as networks and communication systems, a new balance of work is being developed between the human and the machine system. This new balance holds the promise of greatly increased exploration capability, along with dramatically reduced design, development, and operating costs. These new information technologies, utilizing knowledge-based software and very highspeed computer systems, will provide new design and development tools, scheduling mechanisms, and vehicle and system health monitoring capabilities that have hitherto been unavailable to the mission and spacecraft designer and the system operator. This paper will utilize typical lunar missions, both robotic and crewed, as a basis to describe and illustrate how these new information system technologies could be applied to all aspects such missions. In particular, new system design tradeoff tools will be described along with technologies that will allow a very much greater degree of autonomy of exploration vehicles than has heretofore been possible. In addition, new information technologies that will significantly reduce the human operational requirements will be discussed.

Gross, Anthony R.↗
NASA NTRS2015

Generation of Simulated Tracking Data for LADEE Operational Readiness Testing

Operational Readiness Tests were an important part of the pre-launch preparation for the LADEE mission. The generation of simulated tracking data to stress the Flight Dynamics System and the Flight Dynamics Team was important for satisfying the testing goal of demonstrating that the software and the team were ready to fly the operational mission. The simulated tracking was generated in a manner to incorporate the effects of errors in the baseline dynamical model, errors in maneuver execution and phenomenology associated with various tracking system based components. The ability of the mission team to overcome these challenges in a realistic flight dynamics scenario indicated that the team and flight dynamics system were ready to fly the LADEE mission. Lunar Atmosphere and Dust Environment.

Tracking↗
NASA NTRS2010

Computer Software Configuration Item-Specific Flight Software Image Transfer Script Generator

A K-shell UNIX script enables the International Space Station (ISS) Flight Control Team (FCT) operators in NASA s Mission Control Center (MCC) in Houston to transfer an entire or partial computer software configuration item (CSCI) from a flight software compact disk (CD) to the onboard Portable Computer System (PCS). The tool is designed to read the content stored on a flight software CD and generate individual CSCI transfer scripts that are capable of transferring the flight software content in a given subdirectory on the CD to the scratch directory on the PCS. The flight control team can then transfer the flight software from the PCS scratch directory to the Electronically Erasable Programmable Read Only Memory (EEPROM) of an ISS Multiplexer/ Demultiplexer (MDM) via the Indirect File Transfer capability. The individual CSCI scripts and the CSCI Specific Flight Software Image Transfer Script Generator (CFITSG), when executed a second time, will remove all components from their original execution. The tool will identify errors in the transfer process and create logs of the transferred software for the purposes of configuration management.

Bolen, Kenny↗
NASA NTRS2002

The Personal Satellite Assistant: An Internal Spacecraft Autonomous Mobile Monitor

This paper presents an overview of the research and development effort at the NASA Ames Research Center to create an internal spacecraft autonomous mobile monitor capable of performing intra-vehicular sensing activities by autonomously navigating onboard the International Space Station. We describe the capabilities, mission roles, rationale, high-level functional requirements, and design challenges for an autonomous mobile monitor. The rapid prototyping design methodology used, in which five prototypes of increasing fidelity are designed, is described as well as the status of these prototypes, of which two are operational and being tested, and one is actively being designed. The physical test facilities used to perform ground testing are briefly described, including a micro-gravity test facility that permits a prototype to propel itself in 3 dimensions with 6 degrees-of-freedom as if it were in an micro-gravity environment. We also describe an overview of the autonomy framework and its components including the software simulators used in the development process. Sample mission test scenarios are also described. The paper concludes with a discussion of future and related work followed by the summary.

Dorais, Gregory A.↗
NASA NTRS1998

Onboard Science Data Analysis: Opportunities, Benefits, and Effects on Mission Design

Much of the initial focus for spacecraft autonomy has been on developing new software and systems concepts to automate engineering functions of the spacecraft: guidance, navigation and control, fault protection, and resources management. However, the ultimate objectives of NASA missions are science objectives, which implies that we need a new framework for perfoming science data evaluation and observation planning autonomously onboard spacecraft.

spacecraft autonomy observation planning science d↗
NASA NTRS2014

An Architecture to Enable Autonomous Control of Spacecraft

Autonomy is required for manned spacecraft missions distant enough that light-time communication delays make ground-based mission control infeasible. Presently, ground controllers develop a complete schedule of power modes for all spacecraft components based on a large number of factors. The proposed architecture is an early attempt to formalize and automate this process using on-vehicle computation resources. In order to demonstrate this architecture, an autonomous electrical power system controller and vehicle Mission Manager are constructed. These two components are designed to work together in order to plan upcoming load use as well as respond to unanticipated deviations from the plan. The communication protocol was developed using "paper" simulations prior to formally encoding the messages and developing software to implement the required functionality. These software routines exchange data via TCP/IP sockets with the Mission Manager operating at NASA Ames Research Center and the autonomous power controller running at NASA Glenn Research Center. The interconnected systems are tested and shown to be effective at planning the operation of a simulated quasi-steady state spacecraft power system and responding to unexpected disturbances.

space power systems↗
NASA NTRS2016

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IVV) Program, with Software Assurance Research Program support, extracted FM architectures across the IVV portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IVV projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management.

Fitz, Rhonda↗
NASA NTRS2009

DSN Simulator

The DSN Simulator (wherein DSN signifies NASA's Deep Space Network) is an updated version of the software described in DSN Array Simulator (NPO-44506), Software Tech Briefs (Special supplement to NASA Tech Briefs), Vol. 32, No. 9 (September 2008), page 26. To recapitulate: This software is used for computational modeling of proposed DSN facilities comprising arrays of antennas and transmitting and receiving equipment for microwave communication with spacecraft on interplanetary missions. Such modeling is performed to estimate facility performance, evaluate requirements that govern facility design, and evaluate proposed improvements in hardware and/or software. The software includes a Monte Carlo simulation component that enables rapid generation of key mission-set metrics (e.g., numbers of links, data rates, and data volumes), and statistical distributions thereof as functions of time. The prior version of the software could model only one DSN facility at a time and included hard-coded, unconfigurable metrics. The present updated version is capable of modeling the entire DSN and provides for configurable metrics, making it possible to perform loading analyses for alternative future DSN architectures and mission-set scenarios. The present version also features an improved user interface and interfaces for exchange of data with other DSN software and with a DSN mission model database.

Fijany, Amir↗
NASA NTRS2002

Development of a Two-Wheel Contingency Mode for the MAP Spacecraft

The Microwave Anisotropy Probe (MAP) is a follow-on mission to the Cosmic Background Explorer (COBE), and is currently collecting data from its orbit near the second Sun-Earth libration point. Due to limited mass, power, and financial resources, a traditional reliability concept including fully redundant components was not feasible for MAP. Instead, the MAP design employs selective hardware redundancy in tandem with contingency software modes and algorithms to improve the odds of mission success. One direction for such improvement has been the development of a two-wheel backup control strategy. This strategy would allow MAP to position itself for maneuvers and collect science data should one of its three reaction wheels fail. Along with operational considerations, the strategy includes three new control algorithms. These algorithms would use the remaining attitude control actuators-thrusters and two reaction wheels-in ways that achieve control goals while minimizing adverse impacts on the functionality of other subsystems and software.

Starin, Scott R.↗
NASA NTRS1996

Space Telescope Fine Guidance Sensor Bearing Anomaly

Early in 1993, a servo motor within one of three Fine Guidance Sensors (FGS) aboard the Hubble Space Telescope (HST) reached stall torque levels on several occasions. Little time was left to plan replacement during the first servicing mission, scheduled at the end of '93. Accelerated bearing life tests confirmed that a small angle rocking motion, known as Coarse Track (CT), accelerated bearing degradation. Saturation torque levels were reached after approximately 20 million test cycles, similar to the flight bearings. Reduction in CT operation, implemented in flight software, extended FGS life well beyond the first servicing mission. However in recent years, bearing torques have resumed upward trends and together with a second, recent bearing torque anomaly has necessitated a scheduled FGS replacement during the upcoming second servicing mission in '97. The results from two series of life tests to quantify FGS bearing remaining life, discussion of bearing on-orbit performance, and future plans to service the FGS servos are presented in this paper.

Loewenthal, S.↗
NASA NTRS2002

A Facility and Architecture for Autonomy Research

Autonomy is a key enabling factor in the advancement of the remote robotic exploration. There is currently a large gap between autonomy software at the research level and software that is ready for insertion into near-term space missions. The Mission Simulation Facility (MST) will bridge this gap by providing a simulation framework and suite of simulation tools to support research in autonomy for remote exploration. This system will allow developers of autonomy software to test their models in a high-fidelity simulation and evaluate their system's performance against a set of integrated, standardized simulations. The Mission Simulation ToolKit (MST) uses a distributed architecture with a communication layer that is built on top of the standardized High Level Architecture (HLA). This architecture enables the use of existing high fidelity models, allows mixing simulation components from various computing platforms and enforces the use of a standardized high-level interface among components. The components needed to achieve a realistic simulation can be grouped into four categories: environment generation (terrain, environmental features), robotic platform behavior (robot dynamics), instrument models (camera/spectrometer/etc.), and data analysis. The MST will provide basic components in these areas but allows users to plug-in easily any refined model by means of a communication protocol. Finally, a description file defines the robot and environment parameters for easy configuration and ensures that all the simulation models share the same information.

Pisanich, Greg↗