Search NASA⌕ Search

SEARCH · Search NASA

Results for “Constellations”

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 199 records · Page 11

Distributed Avionics and Software Verification for the Constellation Program

This viewgraph presentation reviews the planned verification of the avionics and software being developed for the Constellation program.The Constellation Distributed System Integration Laboratory (DSIL) will consist of multiple System Integration Labs (SILs), Simulators, Emulators, Testbeds, and Control Centers interacting with each other over a broadband network to provide virtual test systems for multiple test scenarios.

Hood, Laura E.↗

Summary of Liquid Propulsion System Needs in Support of the Constellation Program

In January 2004, the President of the United States established the Vision for Space Exploration (VSE) to complete the International Space Station, retire the Space Shuttle and develop its replacement, and expand the human presence on the Moon as a stepping stone to human exploration of Mars and worlds beyond. In response, NASA developed the Constellation Program, consisting of the components shown in Figure 1. This paper will summarize the manned spaceflight liquid propulsion system needs in support of the Constellation Program over the next 10 years. It will address all liquid engine needs to support human exploration from low Earth orbit (LEO) to the lunar surface, including an overview of engines currently under contract, those baselined but not yet under contract, and those propulsion needs that have yet to be initiated. There may be additional engine needs for early demonstrators, but those will not be addressed as part of this paper. Also, other portions of the VSE architecture, including the planned Orion abort test boosters and the Lunar Precursor Robotic Program, are not addressed here as they either use solid motors or are focused on unmanned elements of returning humans to the Moon.

Lorier, Terry↗

Summary of Propulsion System Needs in Support of Project Constellation

In January 2004, the President of the United States established the Vision for Space Exploration (VSE) to return man to the moon and ultimately to extend manned space travel to Mars. This paper will summarize the manned space flight liquid propulsion system needs in support of Project Constellation over the next 10 years. It will include all engine needs to return man to the moon. An overview of engines currently under contract, those baselined but not yet under contract, and those engine needs that hav.e yet to be initiated. Project Constellation includes the components as shown Figure 1. Liquid propulsion systems supporting the manned portion of these elements include the following: the Crew Exploration Vehicle named Orion (crew module reaction control system (CMRCS), service module Orion Main Engine (OME), service module auxiliary RCS, and service module reaction control system (SMRCS)), the Crew Launch Vehicle named Ares 1 (J2X upper stage, first stage roll control system, second stage reaction control system, and the Ares I-X roll control system), the Heavy Lift Launch Vehicle named Ares V (RS68B first stage booster, J-2X upper stage, roll control systems, and the Earth Departure Stage (EDS) (powered by the same Ares V Upper Stage J-2X), and the Lunar Lander named Altair with both descent and ascent stages (lunar orbit insertion and descent main engine, ascent main engine, and attitude control systems for both stages). In addition, there may be additional engine needs for early demonstrators, but those will not be speculated on as part of this paper. Also, other portions of the VSE architecture, including the planned Orion abort demonstrations and the Lunar Precursor Robotic Program, are not addressed here as they either use solid motors or are focused on unmanned precursor missions.

Sumrall, Phil↗

Mechanical and Thermal Analysis of the Spectroscopy X-ray Telescopes for the Constellation-X Mission

Area and mass requirements for the Constellation-X Spectroscopy X-Ray Telescopes restrict the thickness of the mirror segment to below a mm. Requirement of angular resolution of 15" over the soft x-ray band implies that allowable optic deformation is sub-micrometer for these thin segments. These requirements place stringent constraint on the mounting, alignment and affixing of these mirror segments in both the metrology and integration processes. We present analyses and optimization of the Constellation-X mirrors under relevant mechanical and thermal environments.

Chan, Kai-Wing↗

"Constellation-X and JWST: Concurrent X-ray and Infrared Great Observatories"

Great synergy has been enjoyed between NASA's current Great Observatories and we expect that this will continue in the next decade with the concurrent operation of both Constellation-X and JWST. The great increase in sensitivity offered by these two observatories, working in unison, will be required for a number of key science investigations, several of which we describe in this poster. For instance, although >SO% of the cosmic X-ray background is resolved at 2-8 keV in the deepest Chandra surveys, the peak of the cosmic X-ray background remains largely unexplained (at energies of 8-40 keV). There may be a significant population of obscured (perhaps Compton-thick) AGN that produce this part of the extragalactic background radiation, and Constellation-X's large collecting area and spectroscopic capabilities over the 1-40 keV bandpass will allow determination of the nature of the obscuring material. This obscured nuclear emission is expected to be re-emitted at longer wavelengths and hence mid-infrared (MIR) observations can be crucial to reveal obscured AGN emission. However, current photometric observations in the infrared are limited by contamination from star formation, and sensitive, moderate-to-high resolution IR spectroscopy (provided by JWST) will be required. In addition, the two observatories will make great advances in unraveling the nature of the highest redshift AGN (4 < z < 8; and possibly ~ 8dow)n to Seyfert luminosities and will probe the formation and evolution of galaxy groups and clusters (including important cosmological measurements). This poster describes these science areas and briefly touches upon the role of the various Con-X and JWST instruments in these science investigations.

Hornschemeier, Ann↗

Close Approach Prediction Analysis of the Earth Science Constellation with the Fengyun-1C Debris

Routine satellite operations for the Earth Science Constellation (ESC) include collision risk assessment between members of the constellation and other orbiting space objects. Each day, close approach predictions are generated by a U.S. Department of Defense Joint Space Operations Center Orbital Safety Analyst using the high accuracy Space Object Catalog maintained by the Air Force's 1" Space Control Squadron. Prediction results and other ancillary data such as state vector information are sent to NASAJGoddard Space Flight Center's (GSFC's) Collision Risk Assessment analysis team for review. Collision analysis is performed and the GSFC team works with the ESC member missions to develop risk reduction strategies as necessary. This paper presents various close approach statistics for the ESC. The ESC missions have been affected by debris from the recent anti-satellite test which destroyed the Chinese Fengyun- 1 C satellite. The paper also presents the percentage of close approach events induced by the Fengyun-1C debris, and presents analysis results which predict the future effects on the ESC caused by this event. Specifically, the Fengyun-1C debris is propagated for twenty years using high-performance computing technology and close approach predictions are generated for the ESC. The percent increase in the total number of conjunction events is considered to be an estimate of the collision risk due to the Fengyun-1C break- UP.

Duncan, Matthew↗

Defining Constellation Suit Helmet Field of View Requirements Employing a Mission Segment Based Reduction Process

Field of view has always been a design feature paramount to helmet design, and in particular space suit design, where the helmet must provide an adequate field of view for a large range of activities, environments, and body positions. For Project Constellation, a slightly different approach to helmet requirement maturation was utilized; one that was less a direct function of body position and suit pressure and more a function of the mission segment in which the field of view is required. Through taxonimization of various parameters that affect suited FOV, as well as consideration for possible nominal and contingency operations during that mission segment, a reduction process was able to condense the large number of possible outcomes to only six unique field of view angle requirements that still captured all necessary variables without sacrificing fidelity. The specific field of view angles were defined by considering mission segment activities, historical performance of other suits, comparison between similar requirements (pressure visor up versus down, etc.), estimated requirements from other teams for field of view (Orion, Altair, EVA), previous field of view tests, medical data for shirtsleeve field of view performance, and mapping of visual field data to generate 45degree off-axis field of view requirements. Full resolution of several specific field of view angle requirements warranted further work, which consisted of low and medium fidelity field of view testing in the rear entry ISuit and DO27 helmet prototype. This paper serves to document this reduction progress and followup testing employed to write the Constellation requirements for helmet field of view.

McFarland, Shane M.↗

CEOS Precipitation Constellation

This viewgraph presentation discusses the implementation of the Committee on Earth Observation Satellites (CEOS) precipitation constellation. The contents include: 1) Why a constellation; 2) Who is working on it; 3) Where are we; 4) Where are we going; and 5) What is the approach.

Stocker, Erich F.↗

Evaluation of Dowfrost(TM) HD as a Thermal Control Fluid for Constellation Vehicles

A test was conducted from November 2008 to January 2009 to help determine the compatibility of an inhibited propylene glycol/water solution with planned Constellation vehicles. Dowfrost(TradeMark) HD was selected as the baseline for Orion, as well as other Constellation systems. Therefore, the same Dowfrost(TradeMark) HD/Water solution planned for Orion was chosen for this test. The fluid was subjected to a thermal fluid loop that had flightlike properties, as compared to Orion. The fluid loop had similar wetted materials, temperatures, flow rates, and aluminum wetted surface area to fluid volume ratio. The test was designed to last for 10 years, the life expectancy of the lunar habitat. However, the test lasted less than two months. System filters became clogged with precipitate, rendering the fluid system inoperable. Upon examination of the precipitate, it was determined that the precipitate composition contained aluminum, which could have only come from materials in the test stand, as aluminum is not part of the Dowfrost(TradeMark HD composition. Also, the fluid pH was determined to have increased from 10.1, at the first test sample, to 12.2, at the completion of the test. This high of a pH is corrosive to aluminum and was certainly a contributing factor to the development of precipitate. Chemical analyses and bench-top tests are currently ongoing to determine the underlying cause for this rapid degradation of the fluid. Hamilton Sundstrand, the contractor developing the Orion thermal fluid loop, is performing a parallel effort to not only understand the cause of fluid degradation in the test, but also to investigate solutions to avoid this problem in the Orion s thermal control system. JSC also consulted with the Hamilton Sundstrand team in the development of this test and the subsequent analysis.

Lee, Steve↗

Constellation Program DOLILU Operational Concepts

Day of launch I-load uplink (DOLILU) and a corresponding day of launch trajectory and loads evaluation are being considered for the Constellation Program. Abort effectiveness, controllability, and ascent structural loads all improve with some of the flight software I-loads designed using current measured atmospheric conditions. While a generalized DOLILU framework has been assumed, specific implementation details have not yet been discussed in depth nor documented. Operational improvements can be leveraged from Space Shuttle experience to create a more cost-effective and streamlined process while maintaining the integrity of the results. A preliminary discussion of DOLILU design methodology is presented followed by some suggestions and implementation details for Constellation Program DOLILU operations

Puperi, Daniel S.↗

Requirements and Sizing Investigation for Constellation Space Suit Portable Life Support System Trace Contaminant Control

The Trace Contaminant Control System (TCCS), located within the ventilation loop of the Constellation Space Suit Portable Life Support System (PLSS), is responsible for removing hazardous trace contaminants from the space suit ventilation flow. This paper summarizes the results of a trade study that evaluated if trace contaminant control could be accomplished without a TCCS, relying on suit leakage, ullage loss from the carbon dioxide and humidity control system, and other factors. Trace contaminant generation rates were revisited to verify that values reflect the latest designs for Constellation Space Suit System (CSSS) pressure garment materials and PLSS hardware. Additionally, TCCS sizing calculations were performed and a literature survey was conducted to review the latest developments in trace contaminant technologies.

Paul, Heather L.↗

Constellation's First Flight Test: Ares I-X

On October 28, 2009, NASA launched Ares I-X, the first flight test of the Constellation Program that will send human beings to the Moon and beyond. This successful test is the culmination of a three-and-a-half-year, multi-center effort to design, build, and fly the first demonstration vehicle of the Ares I crew launch vehicle, the successor vehicle to the Space Shuttle. The suborbital mission was designed to evaluate the atmospheric flight characteristics of a vehicle dynamically similar to Ares I; perform a first stage separation and evaluate its effects; characterize and control roll torque; stack, fly, and recover a solid-motor first stage testing the Ares I parachutes; characterize ground, flight, and reentry environments; and develop and execute new ground hardware and procedures. Built from existing flight and new simulator hardware, Ares I-X integrated a Shuttle-heritage four-segment solid rocket booster for first stage propulsion, a spacer segment to simulate a five-segment booster, Peacekeeper axial engines for roll control, and Atlas V avionics, as well as simulators for the upper stage, crew module, and launch abort system. The mission leveraged existing logistical and ground support equipment while also developing new ones to accommodate the first in-line rocket for flying astronauts since the Saturn IB last flew from Kennedy Space Center (KSC) in 1975. This paper will describe the development and integration of the various vehicle and ground elements, from conception to stacking in KSC s Vehicle Assembly Building; hardware performance prior to, during, and after the launch; and preliminary lessons and data gathered from the flight. While the Constellation Program is currently under review, Ares I-X has and will continue to provide vital lessons for NASA personnel in taking a vehicle concept from design to flight.

Davis, Stephan R.↗

The Role and Quality of Software Safety in the NASA Constellation Program

In this study, we examine software safety risk in the early design phase of the NASA Constellation spaceflight program. Obtaining an accurate, program-wide picture of software safety risk is difficult across multiple, independently-developing systems. We leverage one source of safety information, hazard analysis, to provide NASA quality assurance managers with information regarding the ongoing state of software safety across the program. The goal of this research is two-fold: 1) to quantify the relative importance of software with respect to system safety; and 2) to quantify the level of risk presented by software in the hazard analysis. We examined 154 hazard reports created during the preliminary design phase of three major flight hardware systems within the Constellation program. To quantify the importance of software, we collected metrics based on the number of software-related causes and controls of hazardous conditions. To quantify the level of risk presented by software, we created a metric scheme to measure the specificity of these software causes. We found that from 49-70% of hazardous conditions in the three systems could be caused by software or software was involved in the prevention of the hazardous condition. We also found that 12-17% of the 2013 hazard causes involved software, and that 23-29% of all causes had a software control. Furthermore, 10-12% of all controls were software-based. There is potential for inaccuracy in these counts, however, as software causes are not consistently scoped, and the presence of software in a cause or control is not always clear. The application of our software specificity metrics also identified risks in the hazard reporting process. In particular, we found a number of traceability risks in the hazard reports may impede verification of software and system safety.

Layman, Lucas↗

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, within a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability, and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation, testing results, and other information. Where appropriate, actual performance history was used to calculate failure rates for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to assess compliance with requirements and to highlight design or performance shortcomings for further decision making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability, and maintainability analysis, and present findings and observation based on analysis leading to the Ground Operations Project Preliminary Design Review milestone.

Gernand, Jeffrey L.↗

A Case Study: Using Delmia at Kennedy Space Center to Support NASA's Constellation Program

The presentation examines the use of Delmia (Digital Enterprise Lean Manufacturing Interactive Application) for digital simulation in NASA's Constellation Program. Topics include an overview of the Kennedy Space Center (KSC) Design Visualization Group tasks, NASA's Constellation Program, Ares 1 ground processing preliminary design review, and challenges and how Delmia is used at KSC, Challenges include dealing with large data sets, creating and maintaining KSC's infrastructure, gathering customer requirements and meeting objectives, creating life-like simulations, and providing quick turn-around on varied products,

Kickbusch, Tracey↗

Enhancements to TetrUSS for NASA Constellation Program

The NASA Constellation program is utilizing Computational Fluid Dynamics (CFD) predictions for generating aerodynamic databases and design loads for the Ares I, Ares I-X, and Ares V launch vehicles and for aerodynamic databases for the Orion crew exploration vehicle and its launch abort system configuration. This effort presents several challenges to applied aerodynamicists due to complex geometries and flow physics, as well as from the juxtaposition of short schedule program requirements with high fidelity CFD simulations. NASA TetrUSS codes (GridTool/VGRID/USM3D) have been making extensive contributions in this effort. This paper will provide an overview of several enhancements made to the various elements of TetrUSS suite of codes. Representative TetrUSS solutions for selected Constellation program elements will be shown. Best practices guidelines and scripting developed for generating TetrUSS solutions in a production environment will also be described.

Pandya, Mohagna J.↗

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, in a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation; testing results, and other information. Where appropriate, actual performance history was used for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to verify compliance with requirements and to highlight design or performance shortcomings for further decision-making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability and maintainability analysis, and present findings and observation based on analysis leading to the Ground Systems Preliminary Design Review milestone.

Gernand, Jeffrey L.↗

First Crewed Flight: Rationale, Considerations and Challenges from the Constellation Experience

NASA's Constellation Program has made the most progress in a generation towards building an integrated human-rated spacecraft and launch vehicle. During that development, it became clear that NASA's human-rating requirements lacked the specificity necessary to defend a program plan, particularly human-rating test flight plans, from severe budget challenges. This paper addresses the progress Constellation achieved, problems encountered in clarifying and defending a human-rating certification plan, and discusses key considerations for those who find themselves in similar straits with future human-rated spacecraft and vehicles. We assert, and support with space flight data, that NASA's current human-rating requirements do not adequately address "unknown-unknowns", or the unexpected things the hardware can reveal to the designer during test.

Noriega, Carlos↗