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 109 records · Page 6

Moving Towards a Common Ground and Flight Data Systems Architecture for NASA's Exploration Missions

The National Aeronautics and Space Administration has embarked on an ambitious effort to return man to the moon and then on to Mars. The Exploration Vision requires development of major new space and ground assets and poses challenges well beyond those faced by many of NASA's recent programs. New crewed vehicles must be developed. Compatible supply vehicles, surface mobility modules and robotic exploration capabilities will supplement the manned exploration vehicle. New launch systems will be developed as well as a new ground communications and control infrastructure. The development must take place in a cost-constrained environment and must advance along an aggressive schedule. Common solutions and system interoperability and will be critical to the successful development of the Exploration data systems for this wide variety of flight and ground elements. To this end, NASA has assembled a team of engineers from across the agency to identify the key challenges for Exploration data systems and to establish the most beneficial strategic approach to be followed. Key challenges and the planned NASA approach for flight and ground systems will be discussed in the paper. The described approaches will capitalize on new technologies, and will result in cross-program interoperability between spacecraft and ground systems, from multiple suppliers and agencies.

Rader. Steve↗

Towards a Common Basis of Comparison Across a Broad Trade Space of Mars Architecture Options

Humanity’s fascination with Mars predates the advent of space access, but the coming-of-age of rocket propulsion in the mid-20th century provided the technological foundation for considering a human visit to the red planet. Werner von Braun’s “The Mars Project,” published in 1953, is acknowledged as the first integrated Mars mission architecture plan [1]; since then, the reformulation and refinement of Mars architectures and system concepts has been an ongoing activity, as continued study and planning for human Mars missions is necessary in order to incorporate evolving mission objectives, technology advancements, and the increasing body of knowledge regarding human factors and the various environments of space. Historical Mars architecture studies represent an enormous body of work, but apart from a couple of high-level reviews [2], tapping into the findings and philosophies of these varied works entails a tedious and time-consuming individual effort. The unfortunate result of the widely scattered corpus of Mars architectures is that knowledge and understanding acquired in previous studies is not consistently and effectively brought to bear in the studies of today. The primary vehicle for bringing forward past learning is human recall, which both is imperfect and experiences significant attrition. An effort is underway in the Advanced Concepts Office (ACO) at NASA’s Marshall Space Flight Center to recapture and re-baseline previous architecture studies in order to establish a broad basis of comparison for future Mars architecture studies. Recapturing involves gathering and organizing data and documentation from previous efforts; re-baselining entails developing models capable of reproducing the original results, and then utilizing these models to implement a common set of ground rules and assumptions across the resulting trade space of Mars architecture options. This paper will present the methodology ACO is employing in performing this architecture meta-study, including a discussion on the challenges involved in re-baselining without losing the intent behind previous concepts. As part of this discussion some initial results will be presented, along with a list of studies targeted for inclusion. It is expected that the completed basis of comparison results will be presented as a follow-on paper in the following year.

Stephen James Edwards↗

REACH: Real-Time Data Awareness in Multi-Spacecraft Missions

NASA's Advanced Architectures and Automation Branch at the Goddard Space Flight Center (Code 588) saw the potential to reduce the cost of constellation missions by creating new user interfaces to the ground system health-and-safety data. The goal is to enable a small Flight Operations Team (FOT) to remain aware and responsive to the increased amount of ground system information in a multi-spacecraft environment. Rather than abandon the tried and true, these interfaces were developed to run alongside existing ground system software to provide additional support to the FOT. These new user interfaces have been combined in a tool called REACH. REACH-the Real-time Evaluation and Analysis of Consolidated Health-is a software product that uses advanced visualization techniques to make spacecraft anomalies easy to spot, no matter how many spacecraft are in the constellation. REACH reads numerous real-time streams of data from the ground system(s) and displays synthesized information to the FOT such that anomalies are easy to pick out and investigate.

Maks, Lori↗

Using Existing NASA Satellites as Orbiting Testbeds to Accelerate Technology Infusion into Future Missions

One of the shared problems for new space mission developers is that it is extremely difficult to infuse new technology into new missions unless that technology has been flight validated. Therefore, the issue is that new technology is required to fly on a successful mission for flight validation. We have been experimenting with new technology on existing satellites by retrofitting primarily the flight software while the missions are on-orbit to experiment with new operations concepts. Experiments have been using Earth Observing 1 (EO-1), which is part of the New Millennium Program at NASA. EO-1 finished its prime mission one year after its launch on November 21,2000. From November 21,2001 until the present, EO-1 has been used in parallel with additional science data gathering to test out various sensor web concepts. Similarly, the Cosmic Hot Interstellar Plasma Spectrometer (CHIPS) satellite was also a one year mission flown by the University of Berkeley, sponsored by NASA and whose prime mission ended August 30,2005. Presently, CHIPS is being used to experiment with a seamless space to ground interface by installing Core Flight System (cFS), a "plug-and-play" architecture developed by the Flight Software Branch at NASA/GSFC on top of the existing space-to-ground Internet Protocol (IP) interface that CHIPS implemented. For example, one targeted experiment is to connect CHIPS to a rover via this interface and the Internet, and trigger autonomous actions on CHIPS, the rover or both. Thus far, having satellites to experiment with new concepts has turned out to be an inexpensive way to infuse new technology for future missions. Relevant experiences thus far and future plans will be discussed in this presentation.

Mandl, Daniel↗

A Core Plug and Play Architecture for Reusable Flight Software Systems

The Flight Software Branch, at Goddard Space Flight Center (GSFC), has been working on a run-time approach to facilitate a formal software reuse process. The reuse process is designed to enable rapid development and integration of high-quality software systems and to more accurately predict development costs and schedule. Previous reuse practices have been somewhat successful when the same teams are moved from project to project. But this typically requires taking the software system in an all-or-nothing approach where useful components cannot be easily extracted from the whole. As a result, the system is less flexible and scalable with limited applicability to new projects. This paper will focus on the rationale behind, and implementation of the run-time executive. This executive is the core for the component-based flight software commonality and reuse process adopted at Goddard.

Wilmot, Jonathan↗

Space Software Defined Radio Characterization to Enable Reuse

NASA's Space Communication and Navigation Testbed is beginning operations on the International Space Station this year. The objective is to promote new software defined radio technologies and associated software application reuse, enabled by this first flight of NASA's Space Telecommunications Radio System architecture standard. The Space Station payload has three software defined radios onboard that allow for a wide variety of communications applications; however, each radio was only launched with one waveform application. By design the testbed allows new waveform applications to be uploaded and tested by experimenters in and outside of NASA. During the system integration phase of the testbed special waveform test modes and stand-alone test waveforms were used to characterize the SDR platforms for the future experiments. Characterization of the Testbed's JPL SDR using test waveforms and specialized ground test modes is discussed in this paper. One of the test waveforms, a record and playback application, can be utilized in a variety of ways, including new satellite on-orbit checkout as well as independent on-board testbed experiments.

Mortensen, Dale J.↗

STRS Radio Service Software for NASA's SCaN Testbed

NASAs Space Communication and Navigation(SCaN) Testbed was launched to the International Space Station in 2012. The objective is to promote new software defined radio technologies and associated software application reuse, enabled by this first flight of NASAs Space Telecommunications Radio System(STRS) architecture standard. Pre-launch testing with the testbeds software defined radios was performed as part of system integration. Radio services for the JPL SDR were developed during system integration to allow the waveform application to operate properly in the space environment, especially considering thermal effects. These services include receiver gain control, frequency offset, IQ modulator balance, and transmit level control. Development, integration, and environmental testing of the radio services will be described. The added software allows the waveform application to operate properly in the space environment, and can be reused by future experimenters testing different waveform applications. Integrating such services with the platform provided STRS operating environment will attract more users, and these services are candidates for interface standardization via STRS.

Mortensen, Dale J.↗

L1 Adaptive Control Law for Flexible Space Launch Vehicle and Proposed Plan for Flight Test Validation

This paper explores application of the L1 adaptive control architecture to a generic flexible Crew Launch Vehicle (CLV). Adaptive control has the potential to improve performance and enhance safety of space vehicles that often operate in very unforgiving and occasionally highly uncertain environments. NASA s development of the next generation space launch vehicles presents an opportunity for adaptive control to contribute to improved performance of this statically unstable vehicle with low damping and low bending frequency flexible dynamics. In this paper, we consider the L1 adaptive output feedback controller to control the low frequency structural modes and propose steps to validate the adaptive controller performance utilizing one of the experimental test flights for the CLV Ares-I Program.

Kharisov, Evgeny↗

Design, Development and Pre-Flight Testing of the Communications, Navigation, and Networking Reconfigurable Testbed (Connect) to Investigate Software Defined Radio Architecture on the International Space Station

The Communication Navigation and Networking Reconfigurable Testbed (CoNNeCT) is a NASA-sponsored mission, which will investigate the usage of Software Defined Radios (SDRs) as a multi-function communication system for space missions. A softwaredefined radio system is a communication system in which typical components of the system (e.g., modulators) are incorporated into software. The software-defined capability allows flexibility and experimentation in different modulation, coding and other parameters to understand their effects on performance. This flexibility builds inherent redundancy and flexibility into the system for improved operational efficiency, real-time changes to space missions and enhanced reliability/redundancy. The CoNNeCT Project is a collaboration between industrial radio providers and NASA. The industrial radio providers are providing the SDRs and NASA is designing, building and testing the entire flight system. The flight system will be integrated on the Express Logistics Carrier (ELC) on the International Space Station (ISS) after launch on the H-IIB Transfer Vehicle in 2012. This paper provides an overview of the technology research objectives, payload description, design challenges and pre-flight testing results.

Over, Ann P.↗

Quality Attributes for Mission Flight Software: A Reference for Architects

In the international standards for architecture descriptions in systems and software engineering (ISO/IEC/IEEE 42010), "concern" is a primary concept that often manifests itself in relation to the quality attributes or "ilities" that a system is expected to exhibit - qualities such as reliability, security and modifiability. One of the main uses of an architecture description is to serve as a basis for analyzing how well the architecture achieves its quality attributes, and that requires architects to be as precise as possible about what they mean in claiming, for example, that an architecture supports "modifiability." This paper describes a table, generated by NASA's Software Architecture Review Board, which lists fourteen key quality attributes, identifies different important aspects of each quality attribute and considers each aspect in terms of requirements, rationale, evidence, and tactics to achieve the aspect. This quality attribute table is intended to serve as a guide to software architects, software developers, and software architecture reviewers in the domain of mission-critical real-time embedded systems, such as space mission flight software.

Software architecture↗

The Orion GN and C Data-Driven Flight Software Architecture for Automated Sequencing and Fault Recovery

The Orion Crew Exploration Vehicle (CET) is being designed to include significantly more automation capability than either the Space Shuttle or the International Space Station (ISS). In particular, the vehicle flight software has requirements to accommodate increasingly automated missions throughout all phases of flight. A data-driven flight software architecture will provide an evolvable automation capability to sequence through Guidance, Navigation & Control (GN&C) flight software modes and configurations while maintaining the required flexibility and human control over the automation. This flexibility is a key aspect needed to address the maturation of operational concepts, to permit ground and crew operators to gain trust in the system and mitigate unpredictability in human spaceflight. To allow for mission flexibility and reconfrgurability, a data driven approach is being taken to load the mission event plan as well cis the flight software artifacts associated with the GN&C subsystem. A database of GN&C level sequencing data is presented which manages and tracks the mission specific and algorithm parameters to provide a capability to schedule GN&C events within mission segments. The flight software data schema for performing automated mission sequencing is presented with a concept of operations for interactions with ground and onboard crew members. A prototype architecture for fault identification, isolation and recovery interactions with the automation software is presented and discussed as a forward work item.

King, Ellis↗

Candidate Mission from Planet Earth control and data delivery system architecture

Using a structured, experienced-based approach, Goddard Space Flight Center (GSFC) has assessed the generic functional requirements for a lunar mission control and data delivery (CDD) system. This analysis was based on lunar mission requirements outlined in GSFC-developed user traffic models. The CDD system will facilitate data transportation among user elements, element operations, and user teams by providing functions such as data management, fault isolation, fault correction, and link acquisition. The CDD system for the lunar missions must not only satisfy lunar requirements but also facilitate and provide early development of data system technologies for Mars. Reuse and evolution of existing data systems can help to maximize system reliability and minimize cost. This paper presents a set of existing and currently planned NASA data systems that provide the basic functionality. Reuse of such systems can have an impact on mission design and significantly reduce CDD and other system development costs.

Shapiro, Phillip↗

An avionics scenario and command model description for Space Generic Open Avionics Architecture (SGOAA)

This paper presents a description of a model for a space vehicle operational scenario and the commands for avionics. This model will be used in developing a dynamic architecture simulation model using the Statemate CASE tool for validation of the Space Generic Open Avionics Architecture (SGOAA). The SGOAA has been proposed as an avionics architecture standard to NASA through its Strategic Avionics Technology Working Group (SATWG) and has been accepted by the Society of Automotive Engineers (SAE) for conversion into an SAE Avionics Standard. This architecture was developed for the Flight Data Systems Division (FDSD) of the NASA Johnson Space Center (JSC) by the Lockheed Engineering and Sciences Company (LESC), Houston, Texas. This SGOAA includes a generic system architecture for the entities in spacecraft avionics, a generic processing external and internal hardware architecture, and a nine class model of interfaces. The SGOAA is both scalable and recursive and can be applied to any hierarchical level of hardware/software processing systems.

Stovall, John R.↗

Defining a Space Mission Architectural Framework: Guiding Robotic Space Mission Design and Development at NASA Goddard Spaceflight Center

Modern Systems Engineering activities for robotic science missions face increased complexity due to evolving measurement requirements, increased collaboration amongst stakeholders and increased collaboration between human and robotic systems. While NASA has employed standard process frameworks for project management and systems engineering for years, it has not yet established an architecture framework (AF) by which its mission systems are described. While an architecture framework is not a necessary component of an organization's operations, the value of a specified AF greatly enhances an organization's ability to define systems consistently and aid in communication across project and organizational boundaries. The current effort identifies an approach to establishing a Space Mission Architecture Framework (SMAF), an AF with roots in ISO 42010 (Systems and Software Engineering-Architecture Description), NASA Procedural Requirements (NPR) 7120.5 (NASA Space Flight Program and Project Management Requirements) and 7123.1B (NASA Systems Engineering Processes and Requirements). The heart of the AF lies in its viewpoints and work products, artifacts that represent a set of information from the viewpoint of a particular stakeholder. This effort articulates the needs, goals and objectives that the SMAF addresses, as well as the approach to creating the framework and establishing the various work products. A full set of work products, sufficient to satisfy the Mission System reporting requirements of NPR 7120/7123 at Key Decision Point (KDP) A is identified in this paper.

Architecture↗

Hydra Rendezvous and Docking Sensor

The U.S. technology to support a CEV AR&D activity is mature and was developed by NASA and supporting industry during an extensive research and development program conducted during the 1990's and early 2000 time frame at the Marshall Space Flight Center. Development and demonstration of a rendezvous/docking sensor was identified early in the AR&D Program as the critical enabling technology that allows automated proxin~ity operations and docking. A first generation rendezvous/docking sensor, the Video Guidance Sensor (VGS) was developed and successfully flown on STS 87 and again on STS 95, proving the concept of a video-based sensor. Advances in both video and signal processing technologies and the lessons learned from the two successful flight experiments provided a baseline for the development of a new generation of video based rendezvous/docking sensor. The Advanced Video Guidance Sensor (AVGS) has greatly increased performance and additional capability for longer-range operation. A Demonstration Automatic Rendezvous Technology (DART) flight experiment was flown in April 2005 using AVGS as the primary proximity operations sensor. Because of the absence of a docking mechanism on the target satellite, this mission did not demonstrate the ability of the sensor to co~ltrold ocking. Mission results indicate that the rendezvous sensor operated successfully in "spot mode" (2 km acquisition of the target, bearing data only) but was never commanded to "acquire and track" the docking target. Parts obsolescence issues prevent the construction of current design AVGS units to support the NASA Exploration initiative. This flight proven AR&D technology is being modularized and upgraded with additional capabilities through the Hydra project at the Marshall Space Flight Center. Hydra brings a unique engineering approach and sensor architecture to the table, to solve the continuing issues of parts obsolescence and multiple sensor integration. This paper presents an approach to sensor hardware trades, to address the needs of future vehicles that may rendezvous and dock with the International Space Station (ISS). It will also discuss approaches for upgrading AVGS to address parts obsolescence, and concepts for modularizing the sensor to provide configuration flexibility for multiple vehicle applications. Options for complementary sensors to be integrated into the multi-head Hydra system will also be presented. Complementary sensor options include ULTOR, a digital image correlator system that could provide relative six-degree-of-freedom information independently from AVGS, and time-of-flight sensors, which determine the range between vehicles by timing pulses that travel from the sensor to the target and back. Common targets and integrated targets, suitable for use with the multi-sensor options in Hydra, will also be addressed.

Roe, Fred↗

Systems Analysis and Structural Design of an Unpressurized Cargo Delivery Vehicle

The International Space Station will require a continuous supply of replacement parts for ongoing maintenance and repair after the planned retirement of the Space Shuttle in 2010. These parts are existing line-replaceable items collectively called Orbital Replacement Units, and 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 lbs of cargo mounted on at least 18 Flight Releasable Attachment Mechanisms. The Crew Launch Vehicle design recommended in the Exploration Systems Architecture Study would be used to launch one annual resupply flight to the International Space Station. 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.

Wu, K. Chauncey↗

Status, Plans, and Initial Results for ARES 1 Crew Launch Vehicle Aerodynamics

Following the completion of NASA's Exploration Systems Architecture Study in August 2004 for the NASA Exploration Systems Mission Directorate (ESMD), the Exploration Launch Office at the NASA Marshall Space Flight Center was assigned project management responsibilities for the design and development of the first vehicle in the architecture, the Ares I Crew Launch Vehicle (CLV), which will be used to launch astronauts to low earth orbit and rendezvous with either the International Space Station or the ESMD s earth departure stage for lunar or other future missions beyond low Earth orbit. The primary elements of the Ares I CLV project are the first stage, the upper stage, the upper stage engine, and vehicle integration. Within vehicle integration is an effort in integrated design and analysis which is comprised of a number of technical disciplines needed to support vehicle design and development. One of the important disciplines throughout the life of the project is aerodynamics. This paper will present the status, plans, and initial results of Ares I CLV aerodynamics as the project was preparing for the Ares I CLV Systems Requirements Review. Following a discussion of the specific interactions with other technical panels and a status of the current activities, the plans for aerodynamic support of the Ares I CLV until the initial crewed flights will be presented.

Huebner, Lawrence D.↗

Status, Plans and Initial Results for Ares I Crew Launch Vehicle Aerodynamics

Following the completion of NASA s Exploration Systems Architecture Study in August 2004 for the NASA Exploration Systems Mission Directorate (ESMD), the Ares Projects Office at the NASA Marshall Space Flight Center was assigned project management responsibilities for the design and development of the first vehicle in the architecture, the Ares I Crew Launch Vehicle (CLV), which will be used to launch astronauts to low earth orbit and rendezvous with either the International Space Station or the ESMD s earth departure stage for lunar or other future missions beyond low Earth orbit. The primary elements of the Ares I CLV project are the first stage, the upper stage, the upper stage engine, and vehicle integration. Within vehicle integration is an effort in integrated design and analysis which is comprised of a number of technical disciplines needed to support vehicle design and development. One of the important disciplines throughout the life of the project is aerodynamics. This paper will present the status, plans, and initial results of Ares I CLV aerodynamics as the project was preparing for the Ares I CLV Systems Requirements Review. Following a discussion of the specific interactions with other technical panels and a status of the current activities, the plans for aerodynamic support of the Ares I CLV until the initial crewed flights will be presented. Keywords: Ares I Crew Launch Vehicle, aerodynamics, wind tunnel testing, computational fluid dynamics

Huebner, Lawrence D.↗