Search NASA⌕ Search

SEARCH · Search NASA

Results for “launch 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 469 records · Page 26
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

Demonstration of Autonomous Rendezvous Technology (DART) Project Summary

Since the 1960's, NASA has performed numerous rendezvous and docking missions. The common element of all US rendezvous and docking is that the spacecraft has always been piloted by astronauts. Only the Russian Space Program has developed and demonstrated an autonomous capability. The Demonstration of Autonomous Rendezvous Technology (DART) project currently funded under NASA's Space Launch Initiative (SLI) Cycle I, provides a key step in establishing an autonomous rendezvous capability for the United States. DART's objective is to demonstrate, in space, the hardware and software necessary for autonomous rendezvous. Orbital Sciences Corporation intends to integrate an Advanced Video Guidance Sensor and Autonomous Rendezvous and Proximity Operations algorithms into a Pegasus upper stage in order to demonstrate the capability to autonomously rendezvous with a target currently in orbit. The DART mission will occur in April 2004. The launch site will be Vandenburg AFB and the launch vehicle will be a Pegasus XL equipped with a Hydrazine Auxiliary Propulsion System 4th stage. All mission objectives will be completed within a 24 hour period. The paper provides a summary of mission objectives, mission overview and a discussion on the design features of the chase and target vehicles.

TImothy E Rumford↗
NASA NTRS2011

Software Users Manual (SUM): Extended Testability Analysis (ETA) Tool

This software user manual describes the implementation and use the Extended Testability Analysis (ETA) Tool. The ETA Tool is a software program that augments the analysis and reporting capabilities of a commercial-off-the-shelf (COTS) testability analysis software package called the Testability Engineering And Maintenance System (TEAMS) Designer. An initial diagnostic assessment is performed by the TEAMS Designer software using a qualitative, directed-graph model of the system being analyzed. The ETA Tool utilizes system design information captured within the diagnostic model and testability analysis output from the TEAMS Designer software to create a series of six reports for various system engineering needs. The ETA Tool allows the user to perform additional studies on the testability analysis results by determining the detection sensitivity to the loss of certain sensors or tests. The ETA Tool was developed to support design and development of the NASA Ares I Crew Launch Vehicle. The diagnostic analysis provided by the ETA Tool was proven to be valuable system engineering output that provided consistency in the verification of system engineering requirements. This software user manual provides a description of each output report generated by the ETA Tool. The manual also describes the example diagnostic model and supporting documentation - also provided with the ETA Tool software release package - that were used to generate the reports presented in the manual

Maul, William A.↗
NASA NTRSDate not supplied

NASA Space Launch System Prepares for Key Hotfire Test Before Vehicle Integration

NASA this year is working toward the final major integrated hardware and avionics test for its Space Launch System (SLS), the agency’s new super heavy-lift vehicle to send large, strategic payloads to the Moon, Mars and beyond. As the backbone of the Artemis human lunar exploration program, Artemis I SLS operations will then shift to the launch site and integration for the inaugural mission. For this final major test of the first vehicle NASA has built exclusively for deep space exploration since the Saturn V, a NASA/Boeing/Aerojet Rocketdyne team will conduct the final core stage “green run” test at NASA's Stennis Space Center with a dramatic firing of all four core stage engines. This test will validate the operation of the stage structures, main propulsion system, engines, avionics, and software. Following data review, stage inspection, and refurbishment, the stage will be barged to NASA’s Kennedy Space Center to continue integration of the Artemis I launch vehicle. Already underway is assembly of the mission’s five-segment solid rocket boosters. The mission’s upper stage and spacecraft adapters also are staged at the launch site ready for integration. Even as the Artemis I SLS proceeds toward launch later this year, the Artemis II and Artemis III vehicles are coming together, with core stages, engines, boosters, upper stage, and payload accommodations in various stages of manufacturing and/or processing. Planning is also underway for additional core stages and a new, more powerful upper stage that will increase lunar payload mass. SLS is the anchor transportation leg of a plan for sustained human exploration of the Moon, including the first human landing later in the decade. This paper will discuss SLS progress to date and expected 2021 milestones.

Bruce R. Askins↗
NASA NTRS2001

The Standard Autonomous File Server, a Customized, Off-the-Shelf Success Story

The Standard Autonomous File Server (SAFS), which includes both off-the-shelf hardware and software, uses an improved automated file transfer process to provide a quicker, more reliable, prioritized file distribution for customers of near real-time data without interfering with the assets involved in the acquisition and processing of the data. It operates as a stand-alone solution, monitoring itself, and providing an automated fail-over process to enhance reliability. This paper will describe the unique problems and lessons learned both during the COTS selection and integration into SAFS, and the system's first year of operation in support of NASA's satellite ground network. COTS was the key factor in allowing the two-person development team to deploy systems in less than a year, meeting the required launch schedule. The SAFS system his been so successful, it is becoming a NASA standard resource, leading to its nomination for NASA's Software or the Year Award in 1999.

Semancik, Susan K.↗
NASA NTRS2002

Managing MDO Software Development Projects

Over the past decade, the NASA Langley Research Center developed a series of 'grand challenge' applications demonstrating the use of parallel and distributed computation and multidisciplinary design optimization. All but the last of these applications were focused on the high-speed civil transport vehicle; the final application focused on reusable launch vehicles. Teams of discipline experts developed these multidisciplinary applications by integrating legacy engineering analysis codes. As teams became larger and the application development became more complex with increasing levels of fidelity and numbers of disciplines, the need for applying software engineering practices became evident. This paper briefly introduces the application projects and then describes the approaches taken in project management and software engineering for each project; lessons learned are highlighted.

Townsend, J. C.↗
NASA NTRS1995

Advanced systems for shuttle launch processing

Four advanced technologies that could be used in a new shuttle launch processing center are described. The latest methods for high capacity data storage technology, disk arrays and magneto optical disks, are described and their advantages and disadvantages compared. A 3-D protein based optical memory, now being researched, is also described as a possible future technology for data storage. An overview of neural network technology is presented together with several commercial software development options now available for neural network applications. The feasibility of Asynchronous Data Transfer technology as the networking technology to integrate video, voice, and data in a new launch processing center is also considered. Different applications of expert system technology at KSC are enumerated together with a number of commercial expert systems development packages presently available.

Perez, Rafael A.↗
NASA NTRS2006

Crew Launch Vehicle (CLV) Upper Stage Configuration Selection Process

The Crew Launch Vehicle (CLV), a key component of NASA's blueprint for the next generation of spacecraft to take humans back to the moon, is being designed and built by engineers at NASA s Marshall Space Flight Center (MSFC). The vehicle s design is based on the results of NASA's 2005 Exploration Systems Architecture Study (ESAS), which called for development of a crew-launch system to reduce the gap between Shuttle retirement and Crew Exploration Vehicle (CEV) Initial Operating Capability, identification of key technologies required to enable and significantly enhance these reference exploration systems, and a reprioritization of near- and far-term technology investments. The Upper Stage Element (USE) of the CLV is a clean-sheet approach that is being designed and developed in-house, with element management at MSFC. The USE concept is a self-supporting cylindrical structure, approximately 115' long and 216" in diameter, consisting of the following subsystems: Primary Structures (LOX Tank, LH2 Tank, Intertank, Thrust Structure, Spacecraft Payload Adaptor, Interstage, Forward and Aft Skirts), Secondary Structures (Systems Tunnel), Avionics and Software, Main Propulsion System, Reaction Control System, Thrust Vector Control, Auxiliary Power Unit, and Hydraulic Systems. The ESAS originally recommended a CEV to be launched atop a four-segment Space Shuttle Main Engine (SSME) CLV, utilizing an RS-25 engine-powered upper stage. However, Agency decisions to utilize fewer CLV development steps to lunar missions, reduce the overall risk for the lunar program, and provide a more balanced engine production rate requirement prompted engineers to switch to a five-segment design with a single Saturn-derived J-2X engine. This approach provides for single upper stage engine development for the CLV and an Earth Departure Stage, single Reusable Solid Rocket Booster (RSRB) development for the CLV and a Cargo Launch Vehicle, and single core SSME development. While the RSRB design has changed since the CLV Project's inception, the USE design has remained essentially a clean-sheet approach. Although a clean-sheet upper stage design inherently carries more risk than a modified design, it does offer many advantages: a design for increased reliability; built-in extensibility to allow for commonality/growth without major redesign; and incorporation of state-of-the-art materials, hardware, and design, fabrication, and test techniques and processes to facilitate a potentially better, more reliable system. Because consideration was given in the ESAS to both clean-sheet and modified USE designs, this paper will highlight the advantages and disadvantages of both approaches and provide a detailed discussion of trades/selections made that led to the final upper stage configuration.

Davis, Daniel J.↗
NASA NTRS2009

Modeling and Simulation of Variable Mass, Flexible Structures

The advent of the new Ares I launch vehicle has highlighted the need for advanced dynamic analysis tools for variable mass, flexible structures. This system is composed of interconnected flexible stages or components undergoing rapid mass depletion through the consumption of solid or liquid propellant. In addition to large rigid body configuration changes, the system simultaneously experiences elastic deformations. In most applications, the elastic deformations are compatible with linear strain-displacement relationships and are typically modeled using the assumed modes technique. The deformation of the system is approximated through the linear combination of the products of spatial shape functions and generalized time coordinates. Spatial shape functions are traditionally composed of normal mode shapes of the system or even constraint modes and static deformations derived from finite element models of the system. Equations of motion for systems undergoing coupled large rigid body motion and elastic deformation have previously been derived through a number of techniques [1]. However, in these derivations, the mode shapes or spatial shape functions of the system components were considered constant. But with the Ares I vehicle, the structural characteristics of the system are changing with the mass of the system. Previous approaches to solving this problem involve periodic updates to the spatial shape functions or interpolation between shape functions based on system mass or elapsed mission time. These solutions often introduce misleading or even unstable numerical transients into the system. Plus, interpolation on a shape function is not intuitive. This paper presents an approach in which the shape functions are held constant and operate on the changing mass and stiffness matrices of the vehicle components. Each vehicle stage or component finite element model is broken into dry structure and propellant models. A library of propellant models is used to describe the distribution of mass in the fuel tank or Solid Rocket Booster (SRB) case for various propellant levels. Based on the mass consumed by the liquid engine or SRB, the appropriate propellant model is coupled with the dry structure model for the stage. Then using vehicle configuration data, the integrated vehicle model is assembled and operated on by the constant system shape functions. The system mode shapes and frequencies can then be computed from the resulting generalized mass and stiffness matrices for that mass configuration. The rigid body mass properties of the vehicle are derived from the integrated vehicle model. The coupling terms between the vehicle rigid body motion and elastic deformation are also updated from the constant system shape functions and the integrated vehicle model. This approach was first used to analyze variable mass spinning beams and then prototyped into a generic dynamics simulation engine. The resulting code was tested against Crew Launch Vehicle (CLV-)class problems worked in the TREETOPS simulation package and by Wilson [2]. The Ares I System Integration Laboratory (SIL) is currently being developed at the Marshall Space Flight Center (MSFC) to test vehicle avionics hardware and software in a hardware-in-the-loop (HWIL) environment and certify that the integrated system is prepared for flight. The Ares I SIL utilizes the Ares Real-Time Environment for Modeling, Integration, and Simulation (ARTEMIS) tool to simulate the launch vehicle and stimulate avionics hardware. Due to the presence of vehicle control system filters and the thrust oscillation suppression system, which are tuned to the structural characteristics of the vehicle, ARTEMIS must incorporate accurate structural models of the Ares I launch vehicle. The ARTEMIS core dynamics simulation models the highly coupled nature of the vehicle flexible body dynamics, propellant slosh, and vehicle nozzle inertia effects combined with mass and flexible body properties that vary significant with time during the flight. All forces that act on the vehicle during flight must be simulated, including deflected engine thrust force, spatially distributed aerodynamic forces, gravity, and reaction control jet thrust forces. These forces are used to excite an integrated flexible vehicle, slosh, and nozzle dynamics model for the vehicle stack that simulates large rigid body translations and rotations along with small elastic deformations. Highly effective matrix math operations on a distributed, threaded high-performance simulation node allow ARTEMIS to retain up to 30 modes of flex for real-time simulation. Stage elements that separate from the stack during flight are propagated as independent rigid six degrees of freedom (6DOF) bodies. This paper will present the formulation of the resulting equations of motion, solutions to example problems, and describe the resulting dynamics simulation engine within ARTEMIS.

Tobbe, Patrick A.↗
NASA NTRS1974

Operational concepts for selected Sortie missions: Executive summary

An executive summary is presented of a Spacelab concept study conducted from August 1973 to June 1974. Background information and a summary of study conclusions are given. Specific data are reported for the quick-reaction carrier concept, software and mission integration, configuration management, documentation, equipment pool, and integration alternatives. A forecast of the impact of a second launch site, mission feasibility, and space availability for the Spacelab are also discussed.

Dulock, V. A., Jr.↗
NASA NTRS1993

Optimizing interplanetary trajectories with deep space maneuvers

Analysis of interplanetary trajectories is a crucial area for both manned and unmanned missions of the Space Exploration Initiative. A deep space maneuver (DSM) can improve a trajectory in much the same way as a planetary swingby. However, instead of using a gravitational field to alter the trajectory, the on-board propulsion system of the spacecraft is used when the vehicle is not near a planet. The purpose is to develop an algorithm to determine where and when to use deep space maneuvers to reduce the cost of a trajectory. The approach taken to solve this problem uses primer vector theory in combination with a non-linear optimizing program to minimize Delta(V). A set of necessary conditions on the primer vector is shown to indicate whether a deep space maneuver will be beneficial. Deep space maneuvers are applied to a round trip mission to Mars to determine their effect on the launch opportunities. Other studies which were performed include cycler trajectories and Mars mission abort scenarios. It was found that the software developed was able to locate quickly DSM's which lower the total Delta(V) on these trajectories.

Navagh, John↗
NASA NTRS1993

Expanding the KATE toolbox

KATE (Knowledge-based Autonomous Test Engineer) is a model-based software system developed in the Artificial Intelligence Laboratory at the Kennedy Space Center for monitoring, fault detection, and control of launch vehicles and ground support systems. In order to bring KATE to the level of performance, functionality, and integratability needed for firing room applications, efforts are underway to implement KATE in the C++ programming language using an X-windows interface. Two programs which were designed and added to the collection of tools which comprise the KATE toolbox are described. The first tool, called the schematic viewer, gives the KATE user the capability to view digitized schematic drawings in the KATE environment. The second tool, called the model editor, gives the KATE model builder a tool for creating and editing knowledge base files. Design and implementation issues having to do with these two tools are discussed. It will be useful to anyone maintaining or extending either the schematic viewer or the model editor.

Thomas, Stan J.↗
NASA NTRS2001

Experience and Challenges in Implementing Stratospheric Aerosol Gas Experiment on Meteor-3M Platform

Implementation of Stratospheric Aerosol Gas Experiment (SAGE) is a joint science mission between the Rosavioskosmos, also called Russian Aviation and Space Agency (RASA) and the National Aeronautics and Space Administration (NASA). Under the global collaboration agreement established by President Clinton and Yeltsin in 1995 between the United States and Russia, space was one of the major areas identified for joint scientific collaboration. There were several collaborative projects identified under space, earth, human exploration of space and aeronautics. SAGE was one of the key Earth Science instruments selected common to both countries' interests in ozone research. SAGE has a long space heritage, and four earlier versions of this instrument have flown in space for the last 15-year period. It has provided a vital ozone and aerosol data in the mid latitudes and has contributed in the overall ozone depletion research. SAGE II, the fourth instrument has been flying in space on NASA's Earth Radiation Budget Satellite (ERBS) for the last 14 years. Ball Aerospace built the instrument under Langley Research Center's (LaRC) management. SAGE III for Russian Meteor-3M mission is a third generation design with more spectral bands, elaborate data gathering and storage and intelligent terrestrial software. The Russian collaboration required a complete integration of SAGE III on the Russian Meteor-3M satellite and a launch on a Zenit-2 launch vehicle manufactured in Ukraine. The whole complex is scheduled to be launched from Baikonur cosmodrome in early 2001. This cooperative mission has presented a number of management, technical and logistical challenges on both sides. This paper makes an attempt to review and document such experiences.

Habib, Shahid↗
NASA NTRS2003

Rocket Engine Health Management: Early Definition of Critical Flight Measurements

The NASA led Space Launch Initiative (SLI) program has established key requirements related to safety, reliability, launch availability and operations cost to be met by the next generation of reusable launch vehicles. Key to meeting these requirements will be an integrated vehicle health management ( M) system that includes sensors, harnesses, software, memory, and processors. Such a system must be integrated across all the vehicle subsystems and meet component, subsystem, and system requirements relative to fault detection, fault isolation, and false alarm rate. The purpose of this activity is to evolve techniques for defining critical flight engine system measurements-early within the definition of an engine health management system (EHMS). Two approaches, performance-based and failure mode-based, are integrated to provide a proposed set of measurements to be collected. This integrated approach is applied to MSFC s MC-1 engine. Early identification of measurements supports early identification of candidate sensor systems whose design and impacts to the engine components must be considered in engine design.

Christenson, Rick L.↗
NASA NTRS2016

Spaceport Command and Control System Support Software Development

The Spaceport Command and Control System (SCCS) is a project developed and used by NASA at Kennedy Space Center in order to control and monitor the Space Launch System (SLS) at the time of its launch. One integral subteam under SCCS is the one assigned to the development of a data set building application to be used both on the launch pad and in the Launch Control Center (LCC) at the time of launch. This web application was developed in Ruby on Rails, a web framework using the Ruby object-oriented programming language, by a 15 - employee team (approx.). Because this application is such a huge undertaking with many facets and iterations, there were a few areas in which work could be more easily organized and expedited. As an intern working with this team, I was charged with the task of writing web applications that fulfilled this need, creating a virtual and highly customizable whiteboard in order to allow engineers to keep track of build iterations and their status. Additionally, I developed a knowledge capture web application wherein any engineer or contractor within SCCS could ask a question, answer an existing question, or leave a comment on any question or answer, similar to Stack Overflow.

Knowledge Transfer↗
NASA NTRS2002

Using Pilots to Assess the Value and Approach of CMMI Implementation

At Goddard Space Flight Center (GSFC), we have chosen to use Capability Maturity Model Integrated (CMMI) to guide our process improvement program. Projects at GSFC consist of complex systems of software and hardware that control satellites, operate ground systems, run instruments, manage databases and data and support scientific research. It is a challenge to launch a process improvement program that encompasses our diverse systems, yet is manageable in terms of cost effectiveness. In order to establish the best approach for improvement, our process improvement effort was divided into three phases: 1) Pilot projects; 2) Staged implementation; and 3) Sustainment and continual improvement. During Phase 1 the focus of the activities was on a baselining process, using pre-appraisals in order to get a baseline for making a better cost and effort estimate for the improvement effort. Pilot pre-appraisals were conducted from different perspectives so different approaches for process implementation could be evaluated. Phase 1 also concentrated on establishing an improvement infrastructure and training of the improvement teams. At the time of this paper, three pilot appraisals have been completed. Our initial appraisal was performed in a flight software area, considering the flight software organization as the organization. The second appraisal was done from a project perspective, focusing on systems engineering and acquisition, and using the organization as GSFC. The final appraisal was in a ground support software area, again using GSFC as the organization. This paper will present our initial approach, lessons learned from all three pilots and the changes in our approach based on the lessons learned.

Godfrey, Sara↗
NASA NTRS1986

GRO attitude control and determination

Design features of the attitude control and determination (ACAD) system for the Gamma Ray Observatory (GRO) that will eventually be launched on the Shuttle are described. A tabulation of the ACAD system components is provided and the various standby and normal pointing operational modes of the system are summarized. The system software and sensors will maintain a quaternion model of the GRO attitude on the bases of kinematic equations and inertial data. The software is standardized and has previously been used on the Solar Maximum Mission and Landsat-D. Details of the processing components, redundant electronics for sensor processing, data handling and actuator control are outlined and illustrated with block diagrams. Tests applied to validate the ACAD design are outlined, as are ground support which will be implemented once the GRO is launched.

Jerkovsky, W.↗
NASA NTRS2012

Recovering Swift-XRT Energy Resolution through CCD Charge Trap Mapping

The X-ray telescope on board the Swift satellite for gamma-ray burst astronomy has been exposed to the radiation of the space environment since launch in November 2004. Radiation causes damage to the detector, with the generation of dark current and charge trapping sites that result in the degradation of the spectral resolution and an increase of the instrumental background. The Swift team has a dedicated calibration program with the goal of recovering a significant proportion of the lost spectroscopic performance. Calibration observations of supernova remnants with strong emission lines are analysed to map the detector charge traps and to derive position-dependent corrections to the measured photon energies. We have achieved a substantial recovery in the XRT resolution by implementing these corrections in an updated version of the Swift XRT gain file and in corresponding improvements to the Swift XRT HEAsoft software. We provide illustrations of the impact of the enhanced energy resolution, and show that we have recovered most of the spectral resolution lost since launch

Pagani, C.↗
NASA NTRS1998

An Adaptable Power System with Software Control Algorithm

A low cost, flexible and modular spacecraft power system design was developed in response to a call for an architecture that could accommodate multiple missions in the small to medium load range. Three upcoming satellites will use this design, with one launch date in 1999 and two in the year 2000. The design consists of modular hardware that can be scaled up or down, without additional cost, to suit missions in the 200 to 600 Watt orbital average load range. The design will be applied to satellite orbits that are circular, polar elliptical and a libration point orbit. Mission unique adaptations are accomplished in software and firmware. In designing this advanced, adaptable power system, the major goals were reduction in weight volume and cost. This power system design represents reductions in weight of 78 percent, volume of 86 percent and cost of 65 percent from previous comparable systems. The efforts to miniaturize the electronics without sacrificing performance has created streamlined power electronics with control functions residing in the system microprocessor. The power system design can handle any battery size up to 50 Amp-hour and any battery technology. The three current implementations will use both nickel cadmium and nickel hydrogen batteries ranging in size from 21 to 50 Amp-hours. Multiple batteries can be used by adding another battery module. Any solar cell technology can be used and various array layouts can be incorporated with no change in Power System Electronics (PSE) hardware. Other features of the design are the standardized interfaces between cards and subsystems and immunity to radiation effects up to 30 krad Total Ionizing Dose (TID) and 35 Mev/cm(exp 2)-kg for Single Event Effects (SEE). The control algorithm for the power system resides in a radiation-hardened microprocessor. A table driven software design allows for flexibility in mission specific requirements. By storing critical power system constants in memory, modifying the system code for other programs is simple. These constants can be altered also by ground command, or in response to an anomolous event. All critical power system functions have backup hardware functions to prevent a software or computer glitch from propagating. A number of battery charge control schemes can be implemented by selecting the proper control terms in the code. The architecture allows the design engineer to tune the system response to various system components and anticipated load profiles without costly alterations. A design trade was made with the size, weight and power dissipation of the electronics versus the performance of the power bus to load variations. Linear, fine control is maintained with a streamlined electronics design. This paper describes the hardware design as well as the software control algorithm. The challenges of closing the system control loop digitally is discussed. Control loop margin and power system performance is presented. Lab measurements are shown and compared to the system response of a hardware model running actual flight software.

Castell, Karen↗