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 217 records · Page 12

Space Station communications and tracking system

A comprehensive description of the existing Space Station communications and tracking system requirements, architecture, and design concepts is provided. Areas which will require innovative solutions to provide cost-effective flight systems are emphasized. Among these are the space-to-space links, the differential global positioning system for determining relative position with free-flying vehicles, multitarget radar, packet/isochronous signal processing, and laser docking systems. In addition, the importance of advanced development, tests, and analyses is summarized.

Dietz, Reinhold H.↗

Taking advantage of ground data systems attributes to achieve quality results in testing software

During the software development life cycle process, basic testing starts with the development team. At the end of the development process, an acceptance test is performed for the user to ensure that the deliverable is acceptable. Ideally, the delivery is an operational product with zero defects. However, the goal of zero defects is normally not achieved but is successful to various degrees. With the emphasis on building low cost ground support systems while maintaining a quality product, a key element in the test process is simulator capability. This paper reviews the Transportable Payload Operations Control Center (TPOCC) Advanced Spacecraft Simulator (TASS) test tool that is used in the acceptance test process for unmanned satellite operations control centers. The TASS is designed to support the development, test and operational environments of the Goddard Space Flight Center (GSFC) operations control centers. The TASS uses the same basic architecture as the operations control center. This architecture is characterized by its use of distributed processing, industry standards, commercial off-the-shelf (COTS) hardware and software components, and reusable software. The TASS uses much of the same TPOCC architecture and reusable software that the operations control center developer uses. The TASS also makes use of reusable simulator software in the mission specific versions of the TASS. Very little new software needs to be developed, mainly mission specific telemetry communication and command processing software. By taking advantage of the ground data system attributes, successful software reuse for operational systems provides the opportunity to extend the reuse concept into the test area. Consistency in test approach is a major step in achieving quality results.

Sigman, Clayton B.↗

Utilization fo the Satellite Test Assistant Robot (STAR) for Visual and Thermal Analysis for Articles in the Thermal Vacuum Test Environment

An innovative new telerobotic inspection system called STAR has been developed to asist engineers in the visual and thermal analysis fo flight hardware being tested in a simulated space environment. This paper describes the architecture of the STAR mechanical and control systems and discusses some uses of STAR to date.

STAR satellite test assistant robot space simulati↗

From Concept to Design: Progress on the J-2X Upper Stage Engine for the Ares Launch Vehicles

In accordance with national policy and NASA's Global Exploration Strategy, the Ares Projects Office is embarking on development of a new launch vehicle fleet to fulfill the national goals of replacing the space shuttle fleet, returning to the moon, and exploring farther destinations like Mars. These goals are shaped by the decision to retire the shuttle fleet by 2010, budgetary constraints, and the requirement to create a new fleet that is safer, more reliable, operationally more efficient than the shuttle fleet, and capable of supporting long-range exploration goals. The present architecture for the Constellation Program is the result of extensive trades during the Exploration Systems Architecture Study and subsequent refinement by the Ares Projects Office at Marshall Space Flight Center.

Byrd, Thomas↗

Millimeter- and Submillimeter-Wave Remote Sensing Using Small Satellites

Cloud ice properties and processes play fundamental roles in atmospheric radiation and precipitation. Limited knowledge and poor representation of clouds in global climate models have led to large uncertainties about cloud feedback processes under climate change. Ice clouds have been used as a tuning parameter in the models to force agreement with observations of the radiation budget at the top of the atmosphere, and precipitation at the bottom. The lack of ice cloud measurements has left the cloud processes at intermediate altitudes unconstrained. Millimeter (mm) and submillimeter (submm)-wave radiometry is widely recognized for its potential to fill the cloud measurement gap in the middle and upper troposphere. Analyses have shown that channels from 183900 GHz offer good sensitivity to ice cloud scattering and can provide ice water path (IWP) products to an accuracy of 25 by simultaneously retrieving ice particle size (Dme) and IWP. Therefore, it is highly desirable to develop a cost-effective, compact mm/submm-wave instrument for cloud observations that can be deployed on future small satellites.This paper presents a conceptual study for a mm/submm-wave instrument for multispectral measurements of ice clouds. It discusses previous work at these frequencies by NASA Goddard Space Flight Center (GSFC) and the current instrument study, as well as receiver architectures and their anticipated performance. And finally, it describes a microsatellite prototype intended for use with this mm/submm-wave instrument.

small satellites↗

Safety Characteristics in System Application of Software for Human Rated Exploration Missions for the 8th IAASS Conference

NASA and its industry and international partners are embarking on a bold and inspiring development effort to design and build an exploration class space system. The space system is made up of the Orion system, the Space Launch System (SLS) and the Ground Systems Development and Operations (GSDO) system. All are highly coupled together and dependent on each other for the combined safety of the space system. A key area of system safety focus needs to be in the ground and flight application software system (GFAS). In the development, certification and operations of GFAS, there are a series of safety characteristics that define the approach to ensure mission success. This paper will explore and examine the safety characteristics of the GFAS development. The GFAS system integrates the flight software packages of the Orion and SLS with the ground systems and launch countdown sequencers through the 'agile' software development process. A unique approach is needed to develop the GFAS project capabilities within this agile process. NASA has defined the software development process through a set of standards. The standards were written during the infancy of the so-called industry 'agile development' movement and must be tailored to adapt to the highly integrated environment of human exploration systems. Safety of the space systems and the eventual crew on board is paramount during the preparation of the exploration flight systems. A series of software safety characteristics have been incorporated into the development and certification efforts to ensure readiness for use and compatibility with the space systems. Three underlining factors in the exploration architecture require the GFAS system to be unique in its approach to ensure safety for the space systems, both the flight as well as the ground systems. The first are the missions themselves, which are exploration in nature, and go far beyond the comfort of low Earth orbit operations. The second is the current exploration system will launch only one mission per year even less during its developmental phases. Finally, the third is the partnered approach through the use of many different prime contractors, including commercial and international partners, to design and build the exploration systems. These three factors make the challenges to meet the mission preparations and the safety expectations extremely difficult to implement. As NASA leads a team of partners in the exploration beyond earth's influence, it is a safety imperative that the application software used to test, checkout, prepare and launch the exploration systems put safety of the hardware and mission first. Software safety characteristics are built into the design and development process to enable the human rated systems to begin their missions safely and successfully. Exploration missions beyond Earth are inherently risky, however, with solid safety approaches in both hardware and software, the boldness of these missions can be realized for all on the home planet.

capability↗

MONTE's Client-Based Trajectory Propagation Architecture

The Mission Analysis, Operations, and Navigation Toolkit Environment (MONTE) is JPL's (Jet Propulsion Laboratory's) signature astrodynamic computing platform. It supports all phases of space mission development, from early stage mission design and analysis through flight navigation services. MONTE employs a client-based trajectory propagation architecture where accelerations are calculated in the main MONTE library and the integrator exists on the periphery as a client. This paper outlines this approach to a trajectory propagation system and provides a concrete set of examples showing its utility.

Smith, Jonathan↗

Reconfigurable Very Long Instruction Word (VLIW) Processor

Future NASA missions will depend on radiation-hardened, power-efficient processing systems-on-a-chip (SOCs) that consist of a range of processor cores custom tailored for space applications. Aries Design Automation, LLC, has developed a processing SOC that is optimized for software-defined radio (SDR) uses. The innovation implements the Institute of Electrical and Electronics Engineers (IEEE) RazorII voltage management technique, a microarchitectural mechanism that allows processor cores to self-monitor, self-analyze, and selfheal after timing errors, regardless of their cause (e.g., radiation; chip aging; variations in the voltage, frequency, temperature, or manufacturing process). This highly automated SOC can also execute legacy PowerPC 750 binary code instruction set architecture (ISA), which is used in the flight-control computers of many previous NASA space missions. In developing this innovation, Aries Design Automation has made significant contributions to the fields of formal verification of complex pipelined microprocessors and Boolean satisfiability (SAT) and has developed highly efficient electronic design automation tools that hold promise for future developments.

Velev, Miroslav N.↗

Launch Vehicle Control Center Architectures

Launch vehicles within the international community vary greatly in their configuration and processing. Each launch site has a unique processing flow based on the specific launch vehicle configuration. Launch and flight operations are managed through a set of control centers associated with each launch site. Each launch site has a control center for launch operations; however flight operations support varies from being co-located with the launch site to being shared with the space vehicle control center. There is also a nuance of some having an engineering support center which may be co-located with either the launch or flight control center, or in a separate geographical location altogether. A survey of control center architectures is presented for various launch vehicles including the NASA Space Launch System (SLS), United Launch Alliance (ULA) Atlas V and Delta IV, and the European Space Agency (ESA) Ariane 5. Each of these control center architectures shares some similarities in basic structure while differences in functional distribution also exist. The driving functions which lead to these factors are considered and a model of control center architectures is proposed which supports these commonalities and variations.

Watson, Michael D.↗

Ares I Crew Launch Vehicle Project: Forward Plan to Preliminary Design Review

The Exploration Launch Projects Office, located at NASA's Marshall Space Flight Center, conducted the Ares I Crew Launch Vehicle System Requirements Review (SRR) at the end of 2006, a mere year after the project team was assembled. In Ares' first year, extensive trade studies and evaluations were conducted to refine the design initially recommended by the Exploration Systems Architecture Study, conceptual designs were analyzed for fitness, and the contractual framework was assembled to enable a development effort unparalleled in American space flight since the Space Shuttle. Now, the project turns its focus to the Preliminary Design Review (PDR), scheduled for 2008. Taking into consideration the findings of the SRR, the design of the Ares I is being tightened and refined to meet the operability, reliability, and affordability goals outlined by the Constellation Program. As directed in NASA Procedure and Regulation (NPR) 7123, NASA Systems Engineering Procedural Requirements, the Ares I SRR examined "the functional and performance requirements defined for the system and the preliminary program or project plan and ensures that the requirements and the selected concept will satisfy the mission." The SRR was conducted to ensure the system- and element-level design and interface requirements are defined prior to proceeding into the project's design phase. The Exploration Launch Projects Control Board convened on December 19,2006, and accepted the findings of the SRR and the go-forward plan proceeding to PDR. Based upon these findings, the Ares project believes that operability must drive the vehicle's design, and that a number of design challenges, including system mass and reliability, must be addressed as part of the progress to PDR.

Dumbacher, Daniel L.↗

A Closed-Loop Hardware Simulation of Decentralized Satellite Formation Control

In recent years, there has been significant interest in the use of formation flying spacecraft for a variety of earth and space science missions. Formation flying may provide smaller and cheaper satellites that, working together, have more capability than larger and more expensive satellites. Several decentralized architectures have been proposed for autonomous establishment and maintenance of satellite formations. In such architectures, each satellite cooperatively maintains the shape of the formation without a central supervisor, and processing only local measurement information. The Global Positioning System (GPS) sensors are ideally suited to provide such local position and velocity measurements to the individual satellites. An investigation of the feasibility of a decentralized approach to satellite formation flying was originally presented by Carpenter. He extended a decentralized linear-quadratic-Gaussian (LQG) framework proposed by Speyer in a fashion similar to an extended Kalman filter (EKE) which processed GPS position fix solutions. The new decentralized LQG architecture was demonstrated in a numerical simulation for a realistic scenario that is similar to missions that have been proposed by NASA and the U.S. Air Force. Another decentralized architecture was proposed by Park et al. using carrier differential-phase GPS (CDGPS). Recently, Busse et al demonstrated the decentralized CDGPS architecture in a hardware-in-the-loop simulation on the Formation Flying TestBed (FFTB) at Goddard Space Flight Center (GSFC), which features two Spirent Cox 16 channel GPS signal generator. Although representing a step forward by utilizing GPS signal simulators for a spacecraft formation flying simulation, only an open-loop performance, in which no maneuvers were executed based on the real-time state estimates, was considered. In this research, hardware experimentation has been extended to include closed-loop integrated guidance and navigation of multiple spacecraft formations using GPS receivers and real-time vehicle telemetry. A hardware closed-loop simulation has been performed using the decentralized LQG architecture proposed by Carpenter in the GPS test facility at the Center for Space Research (CSR). This is the first presentation using this type of hardware for demonstration of closed-loop spacecraft formation flying.

Ebimuma, Takuji↗

A High Power Density Power System Electronics for NASA's Lunar Reconnaissance Orbiter

A high power density, modular and state-of-the-art Power System Electronics (PSE) has been developed for the Lunar Reconnaissance Orbiter (LRO) mission. This paper addresses the hardware architecture and performance, the power handling capabilities, and the fabrication technology. The PSE was developed by NASA s Goddard Space Flight Center (GSFC) and is the central location for power handling and distribution of the LRO spacecraft. The PSE packaging design manages and distributes 2200W of solar array input power in a volume less than a cubic foot. The PSE architecture incorporates reliable standard internal and external communication buses, solid state circuit breakers and LiIon battery charge management. Although a single string design, the PSE achieves high reliability by elegantly implementing functional redundancy and internal fault detection and correction. The PSE has been environmentally tested and delivered to the LRO spacecraft for the flight Integration and Test. This modular design is scheduled to flight in early 2009 on board the LRO and Lunar Crater Observation and Sensing Satellite (LCROSS) spacecrafts and is the baseline architecture for future NASA missions such as Global Precipitation Measurement (GPM) and Magnetospheric MultiScale (MMS).

Hernandez-Pellerano, A.↗

The Space Mobile Network

The definition and development of the next generation space communications and navigation architecture is underway. The primary goals are to remove communications and navigations constraints from missions and to enable increased autonomy. The Space Mobile Network (SMN) is an architectural concept that includes new technology and operations that will provide flight systems with an similar user experience to terrestrial wireless mobile networks. This talk will describe the SMN and its proposed new features, such as Disruption Tolerant Networking (DTN), optical communications, and User Initiated Services (UIS).

Spacecraft Communications↗

Ares Launch Vehicles Overview: Space Access Society

America is returning to the Moon in preparation for the first human footprint on Mars, guided by the U.S. Vision for Space Exploration. This presentation will discuss NASA's mission, the reasons for returning to the Moon and going to Mars, and how NASA will accomplish that mission in ways that promote leadership in space and economic expansion on the new frontier. The primary goals of the Vision for Space Exploration are to finish the International Space Station, retire the Space Shuttle, and build the new spacecraft needed to return people to the Moon and go to Mars. The Vision commits NASA and the nation to an agenda of exploration that also includes robotic exploration and technology development, while building on lessons learned over 50 years of hard-won experience. NASA is building on common hardware, shared knowledge, and unique experience derived from the Apollo Saturn, Space Shuttle, and contemporary commercial launch vehicle programs. The journeys to the Moon and Mars will require a variety of vehicles, including the Ares I Crew Launch Vehicle, which transports the Orion Crew Exploration Vehicle, and the Ares V Cargo Launch Vehicle, which transports the Lunar Surface Access Module. The architecture for the lunar missions will use one launch to ferry the crew into orbit, where it will rendezvous with the Lunar Module in the Earth Departure Stage, which will then propel the combination into lunar orbit. The imperative to explore space with the combination of astronauts and robots will be the impetus for inventions such as solar power and water and waste recycling. This next chapter in NASA's history promises to write the next chapter in American history, as well. It will require this nation to provide the talent to develop tools, machines, materials, processes, technologies, and capabilities that can benefit nearly all aspects of life on Earth. Roles and responsibilities are shared between a nationwide Government and industry team. The Exploration Launch Projects Office at the Marshall Space Flight Center manages the design, development, testing, and evaluation of both vehicles and serves as lead systems integrator. A little over a year after it was chartered, the Exploration Launch Projects team is testing engine components, refining vehicle designs, performing wind tunnel tests, and building hardware for the first flight test of Ares I-X, scheduled for spring 2009. The Exploration Launch Projects team conducted the Ares I System Requirements Review (SRR) at the end of 2006. In Ares' first year, extensive trade studies and evaluations were conducted to refine the design initially recommended by the Exploration Systems Architecture Study, conceptual designs were analyzed for fitness, and the contractual framework was assembled to enable a development effort unparalleled in American space flight since the Space Shuttle. Now, the project turns its focus to the Preliminary Design Review (PDR), scheduled for 2008. Taking into consideration the findings of the SRR, the design of the Ares I is being tightened and refined to meet the safety, operability, reliability, and affordability goals outlined by the Constellation Program. The Ares V is in the early design stage, focusing its activities on requirements validation and ways to develop this heavy-lift system so that synergistic hardware commonality between it and the Ares I can reduce the operational footprint and foster sustained exploration across the decades ahead.

Cook, Steve↗

Orion Launch Abort System Performance During Exploration Flight Test 1

The Orion Launch Abort System Office is taking part in flight testing to enable certification that the system is capable of delivering the astronauts aboard the Orion Crew Module to a safe environment during both nominal and abort conditions. Orion is a NASA program, Exploration Flight Test 1 is managed and led by the Orion prime contractor, Lockheed Martin, and launched on a United Launch Alliance Delta IV Heavy rocket. Although the Launch Abort System Office has tested the critical systems to the Launch Abort System jettison event on the ground, the launch environment cannot be replicated completely on Earth. During Exploration Flight Test 1, the Launch Abort System was to verify the function of the jettison motor to separate the Launch Abort System from the crew module so it can continue on with the mission. Exploration Flight Test 1 was successfully flown on December 5, 2014 from Cape Canaveral Air Force Station's Space Launch Complex 37. This was the first flight test of the Launch Abort System preforming Orion nominal flight mission critical objectives. The abort motor and attitude control motors were inert for Exploration Flight Test 1, since the mission did not require abort capabilities. Exploration Flight Test 1 provides critical data that enable engineering to improve Orion's design and reduce risk for the astronauts it will protect as NASA continues to move forward on its human journey to Mars. The Exploration Flight Test 1 separation event occurred at six minutes and twenty seconds after liftoff. The separation of the Launch Abort System jettison occurs once Orion is safely through the most dynamic portion of the launch. This paper will present a brief overview of the objectives of the Launch Abort System during a nominal Orion flight. Secondly, the paper will present the performance of the Launch Abort System at it fulfilled those objectives. The lessons learned from Exploration Flight Test 1 and the other Flight Test Vehicles will certainly contribute to the vehicle architecture of a human-rated space launch vehicle.

McCauley, Rachel↗

Revisiting Nuclear Thermal Propulsion for Human Mars Exploration

Nuclear Thermal Propulsion (NTP) has long been considered as a viable in-space transportation alternative for delivering crew and cargo to the Martian system. While technology development work in nuclear propulsion has continued over the year, general interest in NTP propulsion applications has historically been tied directly to the ebb and flow of interest in sending humans to explore Mars. As far back as the 1960’s, plans for NTP-based human Mars exploration have been proposed and periodically revisited having most recently been considered as part of NASA Design Reference Architecture (DRA) 5.0. NASA has been investigating human Mars exploration strategies tied to its current Journey to Mars for the past few years however, NTP has only recently been added into the set of alternatives under consideration for in-space propulsion under the Mars Study Capability (MSC) team, formerly the Evolvable Mars Campaign (EMC) team. The original charter of the EMC was to find viable human Mars exploration approaches that relied heavily on technology investment work already underway, specifically related to the development of large Solar Electric Propulsion (SEP) systems. The EMC team baselined several departures from traditional Mars exploration ground rules to enable these types of architectures. These ground rule changes included lower energy conjunction class trajectories with corresponding longer flight times, aggregation of mission elements in cis-Lunar space rather than Low Earth Orbit (LEO) and, in some cases, the pre-deployment of Earth return propulsion systems to Mars. As the MSC team continues to refine the in-space transportation trades, an NTP-based architecture that takes advantage of some of these ground rule departures is being introduced.

Percy, Thomas K.↗

Launch site integration for mixed fleet operations

Launch site impacts and integration planning issues are presented to support launch operations for a mixed vehicle fleet (manned and cargo). Proposed ground systems and launch site configurations are described. Prelaunch processing scenarios and schedules are developed for candidate launch vehicles. Earth-to-orbit (ETO) vehicle architectures are presented to meet future launch requirements, including the Space Exploration Initiative (SEI). Flight vehicle design recommendations to enhance launch processing are discussed. The significance of operational designs for future launch vehicles is shown to be a critical factor in planning for mixed fleet launch site operations.

Scott, L. P.↗