Search NASA⌕ Search

SEARCH · Search NASA

Results for “Space Flight Architecture”

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 145 records · Page 8

Crew Launch Vehicle (CLV) Avionics and Software Integration Overview

On January 14, 2004, the President of the United States announced a new plan to explore space and extend a human presence across our solar system. The National Aeronautics and Space Administration (NASA) established the Exploration Systems Mission Directorate (ESMD) to develop and field a Constellation Architecture that will bring the Space Exploration vision to fruition. The Constellation Architecture includes a human-rated Crew Launch Vehicle (CLV) segment, managed by the Marshall Space Flight Center (MSFC), comprised of the First Stage (FS), Upper Stage (US), and Upper Stage Engine (USE) elements. The CLV s purpose is to provide safe and reliable crew and cargo transportation into Low Earth Orbit (LEO), as well as insertion into trans-lunar trajectories. The architecture's Spacecraft segment includes, among other elements, the Crew Exploration Vehicle (CEV), managed by the Johnson Space Flight Center (JSC), which is launched atop the CLV. MSFC is also responsible for CLV and CEV stack integration. This paper provides an overview of the Avionics and Software integration approach (which includes the Integrated System Health Management (ISHM) functions), both within the CLV, and across the CEV interface; it addresses the requirements to be met, logistics of meeting those requirements, and the roles of the various groups. The Avionics Integration and Vehicle Systems Test (ANST) Office was established at the MSFC with system engineering responsibilities for defining and developing the integrated CLV Avionics and Software system. The AIVST Office has defined two Groups, the Avionics and Software Integration Group (AVSIG), and the Integrated System Simulation and Test Integration Group (ISSTIG), and four Panels which will direct trade studies and analyses to ensure the CLV avionics and software meet CLV system and CEV interface requirements. The four panels are: 1) Avionics Integration Panel (AIP), 2) Software Integration Panel, 3) EEE Panel, and 4) Systems Simulation and Test Panel. Membership on the groups and panels includes the MSFC representatives from the requisite engineering disciplines, the First Stage, the Upper Stage, the Upper Stage Engine projects, and key personnel from other NASA centers. The four panels will take the results of trade studies and analyses and develop documentation in support of Design Analysis Cycle Reviews and ultimately the System Requirements Review.

Monell, Donald W.↗

Stochastic Verification by Analysis for Autonomous Systems Management Architecture (ASMA)

The Gateway Vehicle Systems Manager (VSM) is the top-level of a distributed, hierarchical software control system. VSM is data-driven and will make decisions related to mission, fault, resource management and vehicle control. These attributes combined with a high degree of autonomy make it susceptible to emergent behavior. In order to achieve the high level of confidence needed in this critical system, the VSM team has developed a multifaceted verification strategy employing traditional verification techniques, simulation, model checking, and runtime verification. Individual algorithms are verified using conventional testing and model checking using assume-guarantee contracts. A discrete event-based simulation approach is being developed to verify timelines. This presentation describes an enhancement to the verification approach using analysis to enhance system robustness by detecting and resolving the potential for emergent behavior. The verification by analysis employs a Software in the Loop (SITL) environment with real flight software executing on emulated processors, simulations of vehicle subsystems, flight dynamics, and human inputs. Since the possible input space and configuration data set are too large for exhaustive testing, a Monte Carlo approach is used to cover feasible scenarios, augmented with corner cases and known higher-risk scenarios. A key problem in using Monte Carlo-based system verification is evaluating test results to ensure that system behavior is correct. The presentation describes the approach the VSM team uses to monitor behavior for compliance with predetermined boundaries and to identify anomalous behavior for further analysis. This presentation describes the multi-level systems approach to verification, and the simulation-based layer that covers the feasible state space: 1. Overview of the Gateway VSM 2. Special challenges due to heterogeneous, hierarchical architecture 3. Modeling and simulation environment using flight software and system simulations 4. Developing input sets to ensure state-space coverage 5. Developing model and data configuration sets to ensure model coverage 6. Interpreting results without predetermined outcomes 7. Lessons learned and future work

Verification and Validation↗

Energy Beam Highways Through the Skies

The emergence of Energy Beam Flight Transportation Systems could dramatically change the way we travel in the 21st Century. A framework for formulating 'Highways of Light' and the top level architectures that invoke radically new Space Power Grid infrastructure, are introduced. Basically, such flight systems, hereafter called Lightcraft, would employ off-board energy beam sources (either laser or microwave) to energize on-board dependent 'motors' -- instead of the traditional autonomous 'engines' with their on-board energy sources (e.g., chemical fuels). Extreme reductions in vehicle dry mass appear feasible with the use of off-board power and a high degree of on-board artificial intelligence. Such vehicles may no longer need airports for refueling (since they require no propellant), and could possibly pick up travelers at their homes -- before motoring over to one of many local boost stations, for the flight out. With off-board power, hyper-energetic acceleration performance and boost-glide trajectories become feasible. Hypersonic MS airbreathing propulsion can enable boosts up to twice escape velocity, which will cut trip times to the moon down to 5.5 hours. The predominant technological, environmental and social factors that will result from such transportation systems will be stressed. This presentation first introduces the remote source siting options for the space power system infrastructure, and then provides three representative laser/microwave Lightcraft options (derived from historical Case Studies): i.e., 'Acorn', 'Toy Top', and 'Disc.' Next the gamut of combined-cycle engine options developed for these Lightcraft are examined -- to illuminate the 'emerging technologies' that must be harnessed to produce flight hardware. Needed proof-of concept experiments are identified, along with the Macro-Level Issues that can springboard these revolutionary concepts into hardware reality.

Myrabo, Leik N.↗

TPSAS-NF1676L-13680-DND

The International Space Station will require a continuous supply of replacement parts for ongoing maintenance and repair after the retirement of the Space Shuttle. These parts, existing line-replaceable items collectively called Orbital Replacement Units, include heavy and oversized items such as Control Moment Gyroscopes and stowed radiator arrays originally intended for delivery aboard the Space Shuttle. Current resupply spacecraft have limited to no capability to deliver these external logistics. In support of NASA?s Exploration Systems Architecture Study, a team at Langley Research Center designed an Unpressurized Cargo Delivery Vehicle to deliver bulk cargo to the Space Station. The Unpressurized Cargo Delivery Vehicle was required to deliver at least 13,200 lb of cargo mounted on at least 18 Flight Releasable Attachment Mechanisms. The baseline vehicle design developed here has a cargo capacity of 16,000 lbs mounted on up to 20 Flight Releasable Attachment Mechanisms. Major vehicle components are a 5.5m-diameter cargo module containing two detachable cargo pallets with the payload, a Service Module to provide propulsion and power, and an aerodynamic nose cone. To reduce cost and risk, the Service Module is identical to the one used for the Crew Exploration Vehicle design. The Crew Launch Vehicle design recommended in the Exploration Systems Architecture Study was used to launch one annual resupply flight to the International Space Station.

K Chauncey Wu↗

Injury Potential Testing of Suited Occupants During Dynamic Spacecraft Flight Phases

In support of the Constellation Program, a space-suit architecture was envisioned for support of Launch, Entry, Abort, Micro-g EVA, Post Landing crew operations, and under emergency conditions, survival. This space suit architecture is unique in comparison to previous launch, entry, and abort (LEA) suit architectures in that it utilized rigid mobility elements in the scye and the upper arm regions. The suit architecture also employed rigid thigh disconnect elements to allow for quick disconnect functionality above the knee which allowed for commonality of the lower portion of the suit across two suit configurations. This suit architecture was designed to interface with the Orion seat subsystem, which includes seat components, lateral supports, and restraints. Due to this unique configuration of spacesuit mobility elements, combined with the need to provide occupant protection during dynamic landing events, risks were identified with potential injury due to the suit characteristics described above. To address the risk concerns, a test series was developed to evaluate the likelihood and consequences of these potential issues. Testing included use of Anthropomorphic Test Devices (ATDs), Post Mortem Human Subjects (PMHS), and representative seat/suit hardware in combination with high linear acceleration events. The ensuing treatment focuses o detailed results of the testing that has ben conducted under this test series thus far.

McFarland, Shane M.↗

Space ROS: Architecture Roadmap

Space ROS is a matured version of ROS 2 using flight software engineering practices to facilitate mission- and safety-critical applications. This roadmap was developed by the team to communicate the planned future evolution of Space ROS

Austin Probe↗

The ASC Data Archive for the AXAF Ground Calibration

A data archive is near completion at the AXAF Science Center (ASC) to store and provide access to AXAF data. The archive is a distributed client/server system. It consists of a number of different servers which handle flat data files, relational data, replication across multiple sites, and the interface to the WWW. There is a 4GL client interface for each type of data server, C++ and Java APIs, and a number of standard clients to archive and retrieve data. The architecture is scalable and configurable in order to accommodate future data types and increasing data volumes. The first release of the system became available in August 1996 and has been successfully operated since then in support of the AXAF calibration at the George C. Marshall Space Flight Center, Huntsville, AL. This paper will present the overall archive architecture and the design of client and server components. It will also review the ground calibration data contents, the plan for flight data, and the access to the data by ASC internal users and processing pipelines.

Zografou, Panagoula↗

Evaluation of Dual-Launch Lunar Architectures Using the Mission Assessment Post Processor

The National Aeronautics and Space Administrations (NASA) Constellation Program is currently designing a new transportation system to replace the Space Shuttle, support human missions to both the International Space Station (ISS) and the Moon, and enable the eventual establishment of an outpost on the lunar surface. The present Constellation architecture is designed to meet nominal capability requirements and provide flexibility sufficient for handling a host of contingency scenarios including (but not limited to) launch delays at the Earth. This report summarizes a body of work performed in support of the Review of U.S. Human Space Flight Committee. It analyzes three lunar orbit rendezvous dual-launch architecture options which incorporate differing methodologies for mitigating the effects of launch delays at the Earth. NASA employed the recently-developed Mission Assessment Post Processor (MAPP) tool to quickly evaluate vehicle performance requirements for several candidate approaches for conducting human missions to the Moon. The MAPP tool enabled analysis of Earth perturbation effects and Earth-Moon geometry effects on the integrated vehicle performance as it varies over the 18.6-year lunar nodal cycle. Results are provided summarizing best-case and worst-case vehicle propellant requirements for each architecture option. Additionally, the associated vehicle payload mass requirements at launch are compared between each architecture and against those of the Constellation Program. The current Constellation Program architecture assumes that the Altair lunar lander and Earth Departure Stage (EDS) vehicles are launched on a heavy lift launch vehicle. The Orion Crew Exploration Vehicle (CEV) is separately launched on a smaller man-rated vehicle. This strategy relaxes man-rating requirements for the heavy lift launch vehicle and has the potential to significantly reduce the cost of the overall architecture over the operational lifetime of the program. The crew launch occurs first, four days prior to the optimal trans-lunar injection (TLI) departure window. This is done to allow for launch delays in the Altair/EDS launch. During this time, the Orion vehicle is required to conduct orbit maintenance while loitering in low Earth orbit (LEO). The alternative architectures presented aim to eliminate the need for costly orbit maintenance maneuvers while loitering in LEO. In all of the alternative architectures considered, it is assumed that the Altair and Orion vehicles are nominally launched 90 minutes apart, depart the Earth separately, and complete the rendezvous and docking sequence at the Moon. In this lunar orbit rendezvous (LOR) strategy, both the Altair and Orion vehicles will require separate EDS stages, and each will be required to perform lunar orbit insertion (LOI). This has the effect of balancing payload requirements between the two launch vehicles at the Earth. In this case, the overall payload mass is increased slightly, but the increased mission costs could potentially be offset by requiring the construction of two rockets similar in size and nature, unlike the current Constellation architecture. Three dual-launch architecture options with LOR were evaluated, which incorporate differing methodologies for mitigating the effects of launch delays at the Earth. Benefits and drawbacks of each of the dual-launch architecture options with LOR are discussed and the overall mission performance is compared with that of the existing Constellation Program lunar architecture.

Stewart, Shaun M.↗

Mated Flight Control Issues for Space Exploration Systems

Several unique issues related to mated flight control have been broadly identified. These issues include redundancies in subsystems, controllability, command and control authority distribution, information flow across elements, and changes and variability in system characteristics due to variable mated configurations during operations. Architectural options for mated flight control are discussed in the context of evolving space systems.

Lim, Kyong B.↗

Software technology testbed softpanel prototype

The following subject areas are covered: analysis of using Ada for the development of real-time control systems for the Space Station; analysis of the functionality of the Application Generator; analysis of the User Support Environment criteria; analysis of the SSE tools and procedures which are to be used for the development of ground/flight software for the Space Station; analysis if the CBATS tutorial (an Ada tutorial package); analysis of Interleaf; analysis of the Integration, Test and Verification process of the Space Station; analysis of the DMS on-orbit flight architecture; analysis of the simulation architecture.

Source record↗

Systems engineering and integration and management for manned space flight programs

This paper discusses the history of SE&I management of the overall program architecture, organizational structure and the relationship of SE&I to other program organizational elements. A brief discussion of the method of executing the SE&I process, a summary of some of the major lessons learned, and identification of things that have proven successful are included.

Morris, Owen↗

Optimization of Supercomputer Use on EADS II System

The main objective of this research was to optimize supercomputer use to achieve better throughput and utilization of supercomputers and to help facilitate the movement of non-supercomputing (inappropriate for supercomputer) codes to mid-range systems for better use of Government resources at Marshall Space Flight Center (MSFC). This work involved the survey of architectures available on EADS II and monitoring customer (user) applications running on a CRAY T90 system.

Ahmed, Ardsher↗

Energy Storage Flywheels on Spacecraft

With advances in carbon composite material, magnetic bearings, microprocessors, and high-speed power switching devices, work has begun on a space qualifiable Energy Momentum Wheel (EMW). An EMW is a device that can be used on a satellite to store energy, like a chemical battery, and manage angular momentum, like a reaction wheel. These combined functions are achieved by the simultaneous and balanced operation of two or more energy storage flywheels. An energy storage flywheel typically consists of a carbon composite rotor driven by a brushless DC motor/generator. Each rotor has a relatively large angular moment of inertia and is suspended on magnetic bearings to minimize energy loss. The use of flywheel batteries on spacecraft will increase system efficiencies (mass and power), while reducing design-production time and life-cycle cost. This paper will present a discussion of flywheel battery design considerations and a simulation of spacecraft system performance utilizing four flywheel batteries to combine energy storage and momentum management for a typical LEO satellite. A proposed set of control laws and an engineering animation will also be presented. Once flight qualified and demonstrated, space flywheel batteries may alter the architecture of most medium and high-powered spacecraft.

Bartlett, Robert O.↗

Lunar Lander Structural Design Studies at NASA Langley

The National Aeronautics and Space Administration is currently developing mission architectures, vehicle concepts and flight hardware to support the planned human return to the Moon. During Phase II of the 2006 Lunar Lander Preparatory Study, a team from the Langley Research Center was tasked with developing and refining two proposed Lander concepts. The Descent-Assisted, Split Habitat Lander concept uses a disposable braking stage to perform the lunar orbit insertion maneuver and most of the descent from lunar orbit to the surface. The second concept, the Cargo Star Horizontal Lander, carries ascent loads along its longitudinal axis, and is then rotated in flight so that its main engines (mounted perpendicular to the vehicle longitudinal axis) are correctly oriented for lunar orbit insertion and a horizontal landing. Both Landers have separate crew transport volumes and habitats for surface operations, and allow placement of large cargo elements very close to the lunar surface. As part of this study, lightweight, efficient structural configurations for these spacecraft were proposed and evaluated. Vehicle structural configurations were first developed, and preliminary structural sizing was then performed using finite element-based methods. Results of selected structural design and trade studies performed during this activity are presented and discussed.

Wu, K. Chauncey↗

Human Exploration Framework Team: Strategy and Status

Human Exploration Framework Team (HEFT) was formulated to create a decision framework for human space exploration that drives out the knowledge, capabilities and infrastructure NASA needs to send people to explore multiple destinations in the Solar System in an efficient, sustainable way. The specific goal is to generate an initial architecture that can evolve into a long term, enterprise-wide architecture that is the basis for a robust human space flight enterprise. This paper will discuss the initial HEFT activity which focused on starting up the cross-agency team, getting it functioning, developing a comprehensive development and analysis process and conducting multiple iterations of the process. The outcome of this process will be discussed including initial analysis of capabilities and missions for at least two decades, keeping Mars as the ultimate destination. Details are provided on strategies that span a broad technical and programmatic trade space, are analyzed against design reference missions and evaluated against a broad set of figures of merit including affordability, operational complexity, and technical and programmatic risk.

High Earth Orbit (HEO),↗

Development of NASA's Next Generation L-Band Digital Beamforming Synthetic Aperture Radar (DBSAR-2)

NASA's Next generation Digital Beamforming SAR (DBSAR-2) is a state-of-the-art airborne L-band radar developed at the NASA Goddard Space Flight Center (GSFC). The instrument builds upon the advanced architectures in NASA's DBSAR-1 and EcoSAR instruments. The new instrument employs a 16-channel radar architecture characterized by multi-mode operation, software defined waveform generation, digital beamforming, and configurable radar parameters. The instrument has been design to support several disciplines in Earth and Planetary sciences. The instrument was recently completed, and tested and calibrated in a anechoic chamber.

SAR↗

Performance of a Regenerative Fuel Cell System for the Lunar Surface

Regenerative fuel cells (RFCs) are an attractive energy storage solution for lunar missions as a technology capable of providing a higher specific energy (i.e., W∙h/kg) than state-of-the-art packaged Li-ion battery systems. An RFC consists of the (1 & 2) electrochemical stacks (chemical to electrical energy conversion to supply electricity to an external load, i.e. the fuel cell reaction, and electrical to chemical energy conversion of supplied electrical power to dissociate water into hydrogen and oxygen gases, i.e. water electrolysis), (3) fluidic conditioning, (4) reactant storage, (5) avionics, (6) power management and distribution (PMAD), and (7) thermal management. NASA’s Glenn Research Center has designed, assembled, and tested a breadboard RFC sys-tem capable of operating autonomously for multiple simulated lunar day/night cycles in a laboratory environment. The system is comprised of a non-flow through proton exchange membrane (PEM) fuel cell stack and a liquid-anode feed PEM electrolyzer (EZ) stack designed to electrochemically compress the reactants at balanced pressures up to 12.4 MPa (1800 psia). The fluidic conditioning, avionics, PMAD, and thermal management sub-systems are largely comprised of commercial-off-the-shelf components for this system-level development effort. The hardware is controlled by a CubeSat space processor running an operational program based on core flight architecture that can control the RFC hardware autonomously through a state machine with fault monitoring. The testing results highlighted here were completed with the system in an open-loop configuration such that reactants generated through water electrolysis were vented while gas cylinders supplied fuel cell operation. The breadboard operated autonomously, but there were five unplanned transitions to a safe state that required a manual restart after reviewing the data, determining a root cause, and implementing a solution. Four of the transitions were caused by the thermal management subsystem and the fifth was caused by a water management control issue in the EZ sub-system. The RFC system operated for over 550 hours with the final cycle being slightly abbreviated due to reasons unrelated to system performance.

Kerrigan Cain↗

Performance of a Regenerative Fuel Cell System for the Lunar Surface

Regenerative fuel cells (RFCs) are an attractive energy storage solution for lunar missions as a technology capable of providing a higher specific energy (i.e., W∙h/kg) than state-of-the-art packaged Li-ion battery systems. An RFC consists of the (1 & 2) electrochemical stacks (chemical to electrical energy conversion to supply electricity to an external load, i.e. the fuel cell reaction, and electrical to chemical energy conversion of supplied electrical power to dissociate water into hydrogen and oxygen gases, i.e. water electrolysis), (3) fluidic conditioning, (4) reactant storage, (5) avionics, (6) power management and distribution (PMAD), and (7) thermal management. NASA’s Glenn Research Center has designed, assembled, and tested a breadboard RFC sys-tem capable of operating autonomously for multiple simulated lunar day/night cycles in a laboratory environment. The system is comprised of a non-flow through proton exchange membrane (PEM) fuel cell stack and a liquid-anode feed PEM electrolyzer (EZ) stack designed to electrochemically compress the reactants at balanced pressures up to 12.4 MPa (1800 psia). The fluidic conditioning, avionics, PMAD, and thermal management sub-systems are largely comprised of commercial-off-the-shelf components for this system-level development effort. The hardware is controlled by a CubeSat space processor running an operational program based on core flight architecture that can control the RFC hardware autonomously through a state machine with fault monitoring. The testing results highlighted here were completed with the system in an open-loop configuration such that reactants generated through water electrolysis were vented while gas cylinders supplied fuel cell operation. The breadboard operated autonomously, but there were five unplanned transitions to a safe state that required a manual restart after reviewing the data, determining a root cause, and implementing a solution. Four of the transitions were caused by the thermal management subsystem and the fifth was caused by a water management control issue in the EZ sub-system. The RFC system operated for over 550 hours with the final cycle being slightly abbreviated due to reasons unrelated to system performance.

Kerrigan Cain↗