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.

SourceResearch connectionFrom yearThrough year

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

At least 451 records · Page 25

All sources NASA NTRS DOE OSTI

NASA NTRS2000

Performance Evaluation of the NASA/KSC Transmission System

NASA-KSC currently uses three bridged 100-Mbps FDDI segments as its backbone for data traffic. The FDDI Transmission System (FTXS) connects the KSC industrial area, KSC launch complex 39 area, and the Cape Canaveral Air Force Station. The report presents a performance modeling study of the FTXS and the proposed ATM Transmission System (ATXS). The focus of the study is on performance of MPEG video transmission on these networks. Commercial modeling tools - the CACI Predictor and Comnet tools - were used. In addition, custom software tools were developed to characterize conversation pairs in Sniffer trace (capture) files to use as input to these tools. A baseline study of both non-launch and launch day data traffic on the FTXS is presented. MPEG-1 and MPEG-2 video traffic was characterized and the shaping of it evaluated. It is shown that the characteristics of a video stream has a direct effect on its performance in a network. It is also shown that shaping of video streams is necessary to prevent overflow losses and resulting poor video quality. The developed models can be used to predict when the existing FTXS will 'run out of room' and for optimizing the parameters of ATM links used for transmission of MPEG video. Future work with these models can provide useful input and validation to set-top box projects within the Advanced Networks Development group in NASA-KSC Development Engineering.

Christensen, Kenneth J.↗

NASA NTRS2010

FUN3D Grid Refinement and Adaptation Studies for the Ares Launch Vehicle

This paper presents grid refinement and adaptation studies performed in conjunction with computational aeroelastic analyses of the Ares crew launch vehicle (CLV). The unstructured grids used in this analysis were created with GridTool and VGRID while the adaptation was performed using the Computational Fluid Dynamic (CFD) code FUN3D with a feature based adaptation software tool. GridTool was developed by ViGYAN, Inc. while the last three software suites were developed by NASA Langley Research Center. The feature based adaptation software used here operates by aligning control volumes with shock and Mach line structures and by refining/de-refining where necessary. It does not redistribute node points on the surface. This paper assesses the sensitivity of the complex flow field about a launch vehicle to grid refinement. It also assesses the potential of feature based grid adaptation to improve the accuracy of CFD analysis for a complex launch vehicle configuration. The feature based adaptation shows the potential to improve the resolution of shocks and shear layers. Further development of the capability to adapt the boundary layer and surface grids of a tetrahedral grid is required for significant improvements in modeling the flow field.

Bartels, Robert E.↗

NASA NTRS2015

Big Software for SmallSats: Adapting cFS to CubeSat Missions

Expanding capabilities and mission objectives for SmallSats and CubeSats is driving the need for reliable, reusable, and robust flight software. While missions are becoming more complicated and the scientific goals more ambitious, the level of acceptable risk has decreased. Design challenges are further compounded by budget and schedule constraints that have not kept pace. NASA's Core Flight Software System (cFS) is an open source solution which enables teams to build flagship satellite level flight software within a CubeSat schedule and budget. NASA originally developed cFS to reduce mission and schedule risk for flagship satellite missions by increasing code reuse and reliability. The Lunar Reconnaissance Orbiter, which launched in 2009, was the first of a growing list of Class B rated missions to use cFS.

Flight Software↗

NASA NTRS2011

Space Shuttle Abort Evolution

This paper documents some of the evolutionary steps in developing a rigorous Space Shuttle launch abort capability. The paper addresses the abort strategy during the design and development and how it evolved during Shuttle flight operations. The Space Shuttle Program made numerous adjustments in both the flight hardware and software as the knowledge of the actual flight environment grew. When failures occurred, corrections and improvements were made to avoid a reoccurrence and to provide added capability for crew survival. Finally some lessons learned are summarized for future human launch vehicle designers to consider.

Henderson, Edward M.↗

NASA NTRS2022

The Psyche Planning Software Subsystem: Creating a Robust Toolset for a Discovery-class Mission

Psyche is a Discovery-class mission to the small metal-rich asteroid (16) Psyche, and is slated to launch in 2022. Psyche, like many missions, requires low-cost activity planning and sequence generation that serves as the backbone to overall uplink design. Such tools must be maintainable over long periods of operations, and powerful enough to solve complex issues that deep-space one-off missions encounter. In this paper we introduce cost-effective solutions that leverage inner- and open-source principles to meet a variety of common and novel use cases.The uplink process that was designed to meet these challenges is presented, as well as the data-flow through the high-level architecture of the planning software subsystem. The user-facing planning tools are described, particularly the Science Opportunity Analyzer, the Plan Editor, Psyche’s planning automation in the Blackbird framework, and Psyche Simulation Reports. All these applications are either new or have been substantially revamped to meet Psyche’s concept of operations. In particular, ensuring the entire toolchain can correctly process epoch-relative activities is discussed. Underlying the main applications are a common set of dependencies developed and maintained by a new cross-mission association of planning developers. In this way, Psyche can inherit well-tested functionality which saves effort and ensures its developers can focus on solving domain challenges. Quality control of the applications and libraries is ensured with a code-review and unit-test based novel ‘CM lite’ process. Collaboration with international industry and academia using the open-source modules is already occurring.The planning and scheduling software is designed to maximize operator awareness of the integrated plan at every step of the process and use common interfaces and file formats to easily transfer information. Design choices plus the team’s test-driven development process enables more expansive capabilities compared to the decentralized planning and sequence generation functions typical of Discovery-class orbiters without significant development cost increases. Benefits and drawbacks of Psyche’s approach are discussed, including comparison to other missions and tools where appropriate.

Ramanathan, Keshav↗

NASA NTRS2014

Launch Control System Message Reduction

System Monitoring and Control (SMC) message browsers receive many messages daily that operators do not need to see. My job is to reduce the number of messages so that warning and emergency messages can be seen easily and therefore, responded to promptly. There are two methods to reduce messages: duplicate and state-based message correlations. With duplicate message correlation, SMC display the message the first time it shows up. The next times it occurs, a duplicate number will count the number of times the message appears. State-based message correlation is a process in which more informative messages acknowledge less useful ones and send them to history. I also work on correcting the severity level and text formats of messages. I follow two SMC message filtering tenets as I'm working on this project. Firstly, before filtering an offending message, a non-conformance (NC) must be created in order to attempt fixing that message through hardware or software. Only after the NC assessment states that it cannot fix an offending message, it can be filtered by SMC. Secondly, per Launch Control System (LCS) Coding Standards, SMC does not send information messages to the active message browser unless it's a response to an operator action.

correlation↗

NASA NTRS2010

Tight Fits for Americas Next Moon Rocket, Ares V

America has begun the development of a new heavy lift rocket which will enable humans to return to the moon and reach even farther destinations. Five decades ago, the National Aeronautics and Space Administration designed a system (called Saturn/Apollo) to carry men to the moon and back; the rocket which boosted them to the moon was the Saturn V. Saturn V was huge relative to contemporary rockets and is still the largest rocket ever launched. The new moon rocket is called Ares V. It will insert 40% more payload into low earth orbit than Saturn V; and after docking with the crew spacecraft, it will insert 50% more payload onto the translunar trajectory than Saturn V. The current design of Ares V calls for two liquid-fueled stages and 2 "strap-on" solid rockets. The solid rockets are extended-length versions of the solid rockets used on the Shuttle. The diameter of the liquid stages is at least as large as the first stage of the Saturn V; the height of the lower liquid stage (called the core stage) is longer than the external tank of the Shuttle. Huge rockets require huge infrastructure and, during the Saturn/Apollo era, America invested significantly in manufacturing, assembly and launch facilities which are still in use today. Since the Saturn/Apollo era, America has invested in additional infrastructure for the Shuttle program. Ares V must utilize this existing infrastructure, with reasonable modifications. Building a rocket with 50% more capability in the same buildings, testing it in the same test stands, shipping on the same canals under the same bridges, assembling it in the same building, rolling it to the pad on the same crawler, and launching it from the same launch pad is an engineering and logistics challenge which goes hand-in-hand with designing the structure, tanks, turbines, engines, software, etc. necessary to carry such a large payload to earth orbit and to the moon. This paper quantitatively discusses the significant "tight fits" that are constraining Ares V. The engineers designing and building the infrastructure for the Saturn/Apollo program usually added margins and growth capability; sometimes the size of existing facilities (such as the width of a draw bridge) was not a constraint. Ares V may utilize the "extra" space in the existing facilities and expand other tight fits. Some of the tight fits cannot be overcome without great expense; raising the roof on the Vertical Assembly Building for example. Other tight fits are easily overcome; the transporter at the manufacturing facility for the core stage can pass under low ceilings and later over a dike (without dragging the middle) by retracting or extending the struts which support the stage. Tight fits discussed in this paper include manufacturing (jigs, widths, heights, and local transportation), testing (test stand sizes and crane capability), transportation to the test stands and the launch site (barge, waterway, and rail), assembly (VAB internal dimensions and door size), roll-out limits, and launch pad size.

Jaap, John↗

NASA NTRS2011

Time-Accurate Computational Fluid Dynamics Simulation of a Pair of Moving Solid Rocket Boosters

Since the Columbia accident, the threat to the Shuttle launch vehicle from debris during the liftoff timeframe has been assessed by the Liftoff Debris Team at NASA/MSFC. In addition to engineering methods of analysis, CFD-generated flow fields during the liftoff timeframe have been used in conjunction with 3-DOF debris transport methods to predict the motion of liftoff debris. Early models made use of a quasi-steady flow field approximation with the vehicle positioned at a fixed location relative to the ground; however, a moving overset mesh capability has recently been developed for the Loci/CHEM CFD software which enables higher-fidelity simulation of the Shuttle transient plume startup and liftoff environment. The present work details the simulation of the launch pad and mobile launch platform (MLP) with truncated solid rocket boosters (SRBs) moving in a prescribed liftoff trajectory derived from Shuttle flight measurements. Using Loci/CHEM, time-accurate RANS and hybrid RANS/LES simulations were performed for the timeframe T0+0 to T0+3.5 seconds, which consists of SRB startup to a vehicle altitude of approximately 90 feet above the MLP. Analysis of the transient flowfield focuses on the evolution of the SRB plumes in the MLP plume holes and the flame trench, impingement on the flame deflector, and especially impingment on the MLP deck resulting in upward flow which is a transport mechanism for debris. The results show excellent qualitative agreement with the visual record from past Shuttle flights, and comparisons to pressure measurements in the flame trench and on the MLP provide confidence in these simulation capabilities.

Strutzenberg, Louise L.↗

DOE OSTI2025

LLGoMAX : Enhancing Industry-Standard Tools for AC Optimal Unit Commitment

In 2018, the Advanced Research Project Agency – Energy (ARPA-E) launched the Grid Optimization Competition (GOC) [1], a series of competitive challenges intended to accelerate innovation in decision support software used to schedule power grid operations, making them as efficient as possible, while respecting operational constraints of power equipment and operational security. This report covers the participation of the LLGoMAX team—a collaboration of the Lawrence Livermore National Laboratory (LLNL) and ECCO International, Inc.—in Challenge 3 of the competition.

97 MATHEMATICS AND COMPUTING↗

NASA NTRS1980

Telemetry Computer System at Wallops Flight Center

This paper describes the Telemetry Computer System in operation at NASA's Wallops Flight Center for real-time or off-line processing, storage, and display of telemetry data from rockets and aircraft. The system accepts one or two PCM data streams and one FM multiplex, converting each type of data into computer format and merging time-of-day information. A data compressor merges the active streams, and removes redundant data if desired. Dual minicomputers process data for display, while storing information on computer tape for further processing. Real-time displays are located at the station, at the rocket launch control center, and in the aircraft control tower. The system is set up and run by standard telemetry software under control of engineers and technicians. Expansion capability is built into the system to take care of possible future requirements.

Bell, H.↗

NASA NTRS1995

Helpful hints to painless payload processing

The helpful hints herein describe, from a system perspective, the functional flow of hardware and software. The flow will begin at the experiment development stage and continue through build-up, test, verification, delivery, launch and deintegration of the experiment. An effort will be made to identify those interfaces and transfer functions of processing that can be improved upon in the new world of 'Faster, Better, and Cheaper.' The documentation necessary to ensure configuration and processing requirements satisfaction will also be discussed. Hints and suggestions for improvements to enhance each phase of the flow will be derived from extensive experience and documented lessons learned. Charts will be utilized to define the functional flow and a list of 'lessons learned' will be addressed to show applicability. In conclusion, specific improvements for several areas of hardware processing, procedure development and quality assurance, that are generic to all Small Payloads, will be identified.

Terhune, Terry↗

NASA NTRS2001

Collaboration Between NASA Centers of Excellence on Autonomous System Software Development

Software for space systems flight operations has its roots in the early days of the space program when computer systems were incapable of supporting highly complex and flexible control logic. Control systems relied on fast data acquisition and supervisory control from a roomful of systems engineers on the ground. Even though computer hardware and software has become many orders of magnitude more capable, space systems have largely adhered to this original paradigm In an effort to break this mold, Kennedy Space Center (KSC) has invested in the development of model-based diagnosis and control applications for ten years having broad experience in both ground and spacecraft systems and software. KSC has now partnered with Ames Research Center (ARC), NASA's Center of Excellence in Information Technology, to create a new paradigm for the control of dynamic space systems. ARC has developed model-based diagnosis and intelligent planning software that enables spacecraft to handle most routine problems automatically and allocate resources in a flexible way to realize mission objectives. ARC demonstrated the utility of onboard diagnosis and planning with an experiment aboard Deep Space I in 1999. This paper highlights the software control system collaboration between KSC and ARC. KSC has developed a Mars In-situ Resource Utilization testbed based on the Reverse Water Gas Shift (RWGS) reaction. This plant, built in KSC's Applied Chemistry Laboratory, is capable of producing the large amount of Oxygen that would be needed to support a Human Mars Mission. KSC and ARC are cooperating to develop an autonomous, fault-tolerant control system for RWGS to meet the need for autonomy on deep space missions. The paper will also describe how the new system software paradigm will be applied to Vehicle Health Monitoring, tested on the new X vehicles and integrated into future launch processing systems.

Goodrich, Charles H.↗

NASA NTRS2005

Integration of Launch Vehicle Simulation/Analysis Tools and Lunar Cargo Lander Design

Simulation and analysis of vehicle performance is essential for design of a new launch vehicle system. It is more and more demand to have an integrated, highly efficient, robust simulation tool with graphical user interface (GUI) for vehicle performance and simulations. The objectives of this project are to integrate and develop launch vehicle simulation and analysis tools in MATLAB/Simulink under PC Platform, to develop a vehicle capable of being launched on a Delta-IV Heavy Launch Vehicle which can land on the moon with the goal of pre-implanting cargo for a new lunar mission, also with the capability of selecting other launch vehicles that are capable of inserting a payload into Trans-Lunar Injection (TLI). The vehicle flight simulation software, MAVERIC-II (Marshall Aerospace VEhicle Representation In 'C'), developed by Marshall Space Flight Center was selected as a starting point for integration of simulation/analysis tools. The goals are to convert MAVERIC-II from UNIX to PC platform and build input/output GUI s in the MATLAB environment, and then integrate them under MATLAB/Simulink with other modules. Currently, MAVERIC-II has been successfully converted from UNIX to PC using Microsoft Services for UNIX subsystem on PC. Input/Output GUI's have been done for some key input/output files. Calling MAVERIC-II from Simulink has been tested. Details regarding Lunar Cargo Lander Design are described in Part 2/2 of the paper on page X-1.

Shiue, Yeu-Sheng Paul↗

NASA NTRS2010

Streamlining Payload Integration

Payload integration onto space transport vehicles and the International Space Station (ISS) is a complex process. Yet, cargo transport is the sole reason for any space mission, be it for ferrying humans, science, or hardware. As the largest such effort in history, the ISS offers a wide variety of payload experience. However, for any payload to reach the Space Station under the current process, Payload Developers face a list of daunting tasks that go well beyond just designing the payload to the constraints of the transport vehicle and its stowage topology. Payload customers are required to prove their payload s functionality, structural integrity, and safe integration - including under less than nominal situations. They must also plan for or provide training, procedures, hardware labeling, ground support, and communications. In addition, they must deal with negotiating shared consumables, integrating software, obtaining video, and coordinating the return of data and hardware. All the while, they must meet export laws, launch schedules, budget limits, and the consensus of more than 12 panel and board reviews. Despite the cost and infrastructure overhead, payload proposals have increased. Just in the span from FY08 to FY09, the NASA Payload Space Station Support Office budget rose from $78M to $96M in attempt to manage the growing manifest, but the potential number of payloads still exceeds available Payload Integration Management manpower. The growth has also increased management difficulties due to the fact that payloads are more frequently added to a flight schedule late in the flow. The current standard ISS template for payload integration from concept to payload turn-over is 36 months, or 18 months if the payload already has a preliminary design. Customers are increasingly requiring a turn-around of 3 to 6-months to meet market needs. The following paper suggests options for streamlining the current payload integration process in order to meet customer schedule needs and reduce costs for both the integration support teams and the developers, without reducing quality or compromising safety. Issues for the key integration areas of planning, training, verification, and safety are presented in a Root-Cause Analysis study, with plausible solutions provided that involve technology and tools already available to the ISS community. Although based upon the ISS process, the payload integration techniques outlined herein also offer an integration template for any space transport endeavor.

Lufkin, Susan N.↗

NASA NTRS2015

Programmable Ultra-Lightweight System Adaptable Radio

The programmable ultra-lightweight system adaptable radio (PULSAR) is a NASA Marshall Space Flight Center transceiver designed for the CubeSat market, but has the potential for other markets. The PULSAR project aims to reduce size, weight, and power while increasing telemetry data rate. The current version of the PULSAR has a mass of 2.2 kg and a footprint of 10.8 cm2. The height depends on the specific configuration. The PULSAR S-Band Communications Subsystem is an S- and X-band transponder system comprised of a receiver/detector (receiver) element, a transmitter element(s), and related power distribution, command, control, and telemetry element for operation and information interfaces. It is capable of receiving commands, encoding and transmitting telemetry, as well as providing tracking data in a manner compatible with Earthbased ground stations, near Earth network, and deep space network station resources. The software-defined radio's (SDR's) data format characteristics can be defined and reconfigured during spaceflight or prior to launch. The PULSAR team continues to evolve the SDR to improve the performance and form factor to meet the requirements that the CubeSat market space requires. One of the unique features is that the actual radio design can change (somewhat), but not require any hardware modifications due to the use of field programmable gate arrays.

Werkheiser, Arthur↗

NASA NTRS2018

ST7 Disturbance Reduction System (DRS) Colloid Micronewton Thruster Performance and Control Algorithm Model Simulation Validation in Flight

Colloid Micronewton Thrusters (CMNT) were flight demonstrated for the first time on the ST7Disturbance Reduction System (DRS) payload on the European Space Agency (ESA) Laser Interferometer Space Antenna (LISA) Pathfinder spacecraft for attitude and drag-free spacecraft control. LISA Pathfinder was a technology demonstration mission for ESA’s LISA gravitational wave observatory, currently in Phase A with a launch date of 2034. The DRS included the Integrated Avionics Unit (IAU), eight Colloid Micronewton Thrusters (CMNT), Dynamic Control Software (DCS) and Flight Software (FSW). The CMNT technology met performance requirements operating at 5-30 µN of thrust with ≤0.1 µN resolution and ≤0.1 µN/Hz thrust noise to deliver the required nanometer-level precision spacecraft control measured by the gravitational reference sensor (GRS) in the ESA LISA Technology Package (LTP). The performance of seven of the CMNT in flight was consistent with ground test results. The colloid thruster performance model of thrust and thrust noise as a function of operational parameters (i.e. beam current, voltage, temperature, etc.) was validated in flight over a wide range of conditions. A model and simulation of the thruster control algorithm was developed and validated with flight data to predict thrust noise. This capability is important because it is considered to be a significant source of position noise on the spacecraft and, therefore, the acceleration noise on the test masses, which provide the gravity wave measurements. The CMNT thruster model data and validation with LISA Pathfinder/ST7-DRS flight experiments are discussed in this paper.

Hruby, Vlad↗

NASA NTRSDate not supplied

Phase-Free Orbital Element Model Designed to Enable Rapid Assessment of Eclipse and Radiation Profiles for Low-Thrust Spiral Transfers Around the Earth

The Gateway Power and Propulsion Element (PPE) will be the first low-thrust solar electric ion propulsion mission to transfer from a highly elliptical Earth-bound orbit to a southern near-rectilinear halo orbit (NRHO) at the Earth-Moon L2 point. Due to the low thrust nature of the transfer orbit, it is desirable to locate viable trajectories that minimize the time spent in the Van Allen radiation belts to reduce solar array degradation and keep radiation dosages below design limits. In addition to radiation, low thrust trajectories which spiral around the Earth will pass through at least one or more seasons of Earth eclipses. The solar electric propulsion system relies on sunlight to generate the power necessary to operate the ion thrusters. Therefore, it is advantageous to find trajectories which also minimize the amount of time spent in eclipse and avoid excessive battery draw-down periods. We present an analytical method which rapidly approximates low-thrust spiral trajectories, fit to high-fidelity simulated data and parameterized to allow for changes in vehicle thrust characteristics, that is post-processed to determine eclipse profiles and time spent in the belts using a novel approach that estimates the geometry of the belts using a first-order dipole approximation of the Earth’s magnetic field. This method can be used to find satisfactory launch dates and orbit orientations that can serve as initial guesses when optimizing such missions in high-fidelity software.

low thrust trajectory design↗

NASA NTRSDate not supplied

Phase-Free Orbital Element Model Designed to Enable Rapid Assessment of Eclipse and Radiation Profiles for Low-Thrust Spiral Transfers Around the Earth

low thrust trajectory design↗