SEARCH · Search NASA

Results for “flexible architectures”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

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

At least 415 records · Page 23

All sources NASA NTRS DOE OSTI

NASA NTRS2012

Space Suit Portable Life Support System Test Bed (PLSS 1.0) Development and Testing

A multi-year effort has been carried out at NASA-JSC to develop an advanced extra-vehicular activity Portable Life Support System (PLSS) design intended to further the current state of the art by increasing operational flexibility, reducing consumables, and increasing robustness. Previous efforts have focused on modeling and analyzing the advanced PLSS architecture, as well as developing key enabling technologies. Like the current International Space Station Extra-vehicular Mobility Unit PLSS, the advanced PLSS comprises three subsystems required to sustain the crew during extra-vehicular activity including the Thermal, Ventilation, and Oxygen Subsystems. This multi-year effort has culminated in the construction and operation of PLSS 1.0, a test bed that simulates full functionality of the advanced PLSS design. PLSS 1.0 integrates commercial off the shelf hardware with prototype technology development components, including the primary and secondary oxygen regulators, Ventilation Subsystem fan, Rapid Cycle Amine swingbed carbon dioxide and water vapor removal device, and Spacesuit Water Membrane Evaporator heat rejection device. The overall PLSS 1.0 test objective was to demonstrate the capability of the Advanced PLSS to provide key life support functions including suit pressure regulation, carbon dioxide and water vapor removal, thermal control and contingency purge operations. Supplying oxygen was not one of the specific life support functions because the PLSS 1.0 test was not oxygen rated. Nitrogen was used for the working gas. Additional test objectives were to confirm PLSS technology development components performance within an integrated test bed, identify unexpected system level interactions, and map the PLSS 1.0 performance with respect to key variables such as crewmember metabolic rate and suit pressure. Successful PLSS 1.0 testing completed 168 test points over 44 days of testing and produced a large database of test results that characterize system level and component performance. With the exception of several minor anomalies, the PLSS 1.0 test rig performed as expected; furthermore, many system responses trended in accordance with pre-test predictions.

Watts, Carly↗

NASA NTRS2013

An Efficient Model-based Diagnosis Engine for Hybrid Systems Using Structural Model Decomposition

Complex hybrid systems are present in a large range of engineering applications, like mechanical systems, electrical circuits, or embedded computation systems. The behavior of these systems is made up of continuous and discrete event dynamics that increase the difficulties for accurate and timely online fault diagnosis. The Hybrid Diagnosis Engine (HyDE) offers flexibility to the diagnosis application designer to choose the modeling paradigm and the reasoning algorithms. The HyDE architecture supports the use of multiple modeling paradigms at the component and system level. However, HyDE faces some problems regarding performance in terms of complexity and time. Our focus in this paper is on developing efficient model-based methodologies for online fault diagnosis in complex hybrid systems. To do this, we propose a diagnosis framework where structural model decomposition is integrated within the HyDE diagnosis framework to reduce the computational complexity associated with the fault diagnosis of hybrid systems. As a case study, we apply our approach to a diagnostic testbed, the Advanced Diagnostics and Prognostics Testbed (ADAPT), using real data.

Structural Decomposition↗

NASA NTRS2017

Aerogels: Overview and Outlook for Future Space and Terrestrial Applications at NASA

Aerogels are a class of porous solids which exhibit many extreme properties originating from a nanoporous skeletal architecture. One class of aerogel, polyimide-based, possesses low dielectric constants, low thermal conductivities, high porosity, flexibility and low densities with outstanding mechanical properties. Due to their wide array of interesting and useful material properties, they are being employed in many new applications as an enabling technology. In this presentation, I will be giving an overview into the history, properties, and synthesis of aerogels along with a few successful projects at NASA involving the synthesis of novel aerogel formulations.

Nanoporous↗

NASA NTRS1995

Architecture for Payload Planning System (PPS) Software Distribution

The complex and diverse nature of the pay load operations to be performed on the Space Station requires a robust and flexible planning approach, and the proper software tools which tools to support that approach. To date, the planning software for most manned operations in space has been utilized in a centralized planning environment. Centralized planning is characterized by the following: performed by a small team of people, performed at a single location, and performed using single-user planning systems. This approach, while valid for short duration flights, is not conducive to the long duration and highly distributed payload operations environment of the Space Station. The Payload Planning System (PPS) is being designed specifically to support the planning needs of the large number of geographically distributed users of the Space Station. This paper problem provides a general description of the distributed planning architecture that PPS must support and describes the concepts proposed for making PPS available to the Space Station payload user community.

Howell, Eric↗

NASA NTRS2015

Advances in Orion's On-Orbit Guidance and Targeting System Architecture

NASA's manned spaceflight programs have a rich history of advancing onboard guidance and targeting technology. In order to support future missions, the guidance and targeting architecture for the Orion Multi-Purpose Crew Vehicle must be able to operate in complete autonomy, without any support from the ground. Orion's guidance and targeting system must be sufficiently flexible to easily adapt to a wide array of undecided future missions, yet also not cause an undue computational burden on the flight computer. This presents a unique design challenge from the perspective of both algorithm development and system architecture construction. The present work shows how Orion's guidance and targeting system addresses these challenges. On the algorithm side, the system advances the state-of-the-art by: (1) steering burns with a simple closed-loop guidance strategy based on Shuttle heritage, and (2) planning maneuvers with a cutting-edge two-level targeting routine. These algorithms are then placed into an architecture designed to leverage the advantages of each and ensure that they function in concert with one another. The resulting system is characterized by modularity and simplicity. As such, it is adaptable to the on-orbit phases of any future mission that Orion may attempt.

Scarritt, Sara K.↗

NASA NTRS2016

Advanced Sensor Platform to Evaluate Manloads For Exploration Suit Architectures

Space suit manloads are defined as the outer bounds of force that the human occupant of a suit is able to exert onto the suit during motion. They are defined on a suit-component basis as a unit of maximum force that the suit component in question must withstand without failure. Existing legacy manloads requirements are specific to the suit architecture of the EMU and were developed in an iterative fashion; however, future exploration needs dictate a new suit architecture with bearings, load paths, and entry capability not previously used in any flight suit. No capability currently exists to easily evaluate manloads imparted by a suited occupant, which would be required to develop requirements for a flight-rated design. However, sensor technology has now progressed to the point where an easily-deployable, repeatable and flexible manloads measuring technique could be developed leveraging recent advances in sensor technology. INNOVATION: This development positively impacts schedule, cost and safety risk associated with new suit exploration architectures. For a final flight design, a comprehensive and accurate man loads requirements set must be communicated to the contractor; failing that, a suit design which does not meet necessary manloads limits is prone to failure during testing or worse, during an EVA, which could cause catastrophic failure of the pressure garment posing risk to the crew. This work facilitates a viable means of developing manloads requirements using a range of human sizes & strengths. OUTCOME / RESULTS: Performed sensor market research. Highlighted three viable options (primary, secondary, and flexible packaging option). Designed/fabricated custom bracket to evaluate primary option on a single suit axial. Manned suited manload testing completed and general approach verified.

McFarland, Shane↗

NASA NTRS1997

Issues in Defining Software Architectures in a GIS Environment

The primary mission of the Pan-American Center for Earth and Environmental Studies (PACES) is to advance the research areas that are relevant to NASA's Mission to Planet Earth program. One of the activities at PACES is the establishment of a repository for geographical, geological and environmental information that covers various regions of Mexico and the southwest region of the U.S. and that is acquired from NASA and other sources through remote sensing, ground studies or paper-based maps. The center will be providing access of this information to other government entities in the U.S. and Mexico, and research groups from universities, national laboratories and industry. Geographical Information Systems(GIS) provide the means to manage, manipulate, analyze and display geographically referenced information that will be managed by PACES. Excellent off-the-shelf software exists for a complete GIS as well as software for storing and managing spatial databases, processing images, networking and viewing maps with layered information. This allows the user flexibility in combining systems to create a GIS or to mix these software packages with custom-built application programs. Software architectural languages provide the ability to specify the computational components and interactions among these components, an important topic in the domain of GIS because of the need to integrate numerous software packages. This paper discusses the characteristics that architectural languages address with respect to the issues relating to the data that must be communicated between software systems and components when systems interact. The paper presents a background on GIS in section 2. Section 3 gives an overview of software architecture and architectural languages. Section 4 suggests issues that may be of concern when defining the software architecture of a GIS. The last section discusses the future research effort and finishes with a summary.

Acosta, Jesus↗

NASA NTRS1991

NASA Laboratory telerobotic manipulator control system architecture

In support of the National Aeronautics and Space Administration (NASA) goals to increase the utilization of dexterous robotic systems in space, the Oak Ridge National Laboratory (ORNL) has developed the Laboratory Telerobotic Manipulator (LTM) system. It is a dexterous, dual-arm, force reflecting teleoperator system with robotic features for NASA ground-based research. This paper describes the overall control system architecture, including both the hardware and software. The control system is a distributed, modular, and hierarchical design with flexible expansion capabilities for future enhancements of both the hardware and software.

Rowe, J. C.↗

NASA NTRS1992

NASA Laboratory Telerobotic Manipulator control system architecture

Rowe, J. C.↗

NASA NTRS2006

Spitzer Space Telescope Sequencing Operations Software, Strategies, and Lessons Learned

The Space Infrared Telescope Facility (SIRTF) was launched in August, 2003, and renamed to the Spitzer Space Telescope in 2004. Two years of observing the universe in the wavelength range from 3 to 180 microns has yielded enormous scientific discoveries. Since this magnificent observatory has a limited lifetime, maximizing science viewing efficiency (ie, maximizing time spent executing activities directly related to science observations) was the key operational objective. The strategy employed for maximizing science viewing efficiency was to optimize spacecraft flexibility, adaptability, and use of observation time. The selected approach involved implementation of a multi-engine sequencing architecture coupled with nondeterministic spacecraft and science execution times. This approach, though effective, added much complexity to uplink operations and sequence development. The Jet Propulsion Laboratory (JPL) manages Spitzer s operations. As part of the uplink process, Spitzer s Mission Sequence Team (MST) was tasked with processing observatory inputs from the Spitzer Science Center (SSC) into efficiently integrated, constraint-checked, and modeled review and command products which accommodated the complexity of non-deterministic spacecraft and science event executions without increasing operations costs. The MST developed processes, scripts, and participated in the adaptation of multi-mission core software to enable rapid processing of complex sequences. The MST was also tasked with developing a Downlink Keyword File (DKF) which could instruct Deep Space Network (DSN) stations on how and when to configure themselves to receive Spitzer science data. As MST and uplink operations developed, important lessons were learned that should be applied to future missions, especially those missions which employ command-intensive operations via a multi-engine sequence architecture.

missions operations↗

NASA NTRS2009

Low Impact Docking System (LIDS)

Since 1996, NASA has been developing a docking system that will simplify operations and reduce risks associated with mating spacecraft. This effort has focused on developing and testing an original, reconfigurable, active, closed-loop, force-feedback controlled docking system using modern technologies. The primary objective of this effort has been to design a docking interface that is tunable to the unique performance requirements for all types of mating operations (i.e. docking and berthing, autonomous and piloted rendezvous, and in-space assembly of vehicles, modules and structures). The docking system must also support the transfer of crew, cargo, power, fluid, and data. As a result of the past 10 years of docking system advancement, the Low Impact Docking System or LIDS was developed. The current LIDS design incorporates the lessons learned and development experiences from both previous and existing docking systems. LIDS feasibility was established through multiple iterations of prototype hardware development and testing. Benefits of LIDS include safe, low impact mating operations, more effective and flexible mission implementation with an anytime/anywhere mating capability, system level redundancy, and a more affordable and sustainable mission architecture with reduced mission and life cycle costs. In 1996 the LIDS project, then known as the Advanced Docking Berthing System (ADBS) project, launched a four year developmental period. At the end of the four years, the team had built a prototype of the soft-capture hardware and verified the control system that will be used to control the soft-capture system. In 2001, the LIDS team was tasked to work with the X- 38 Crew Return Vehicle (CRV) project and build its first Engineering Development Unit (EDU).

LaBauve, Tobie E.↗

NASA NTRS2001

Adjustable Autonomy Testbed

The Adjustable Autonomy Testbed (AAT) is a simulation-based testbed located in the Intelligent Systems Laboratory in the Automation, Robotics and Simulation Division at NASA Johnson Space Center. The purpose of the testbed is to support evaluation and validation of prototypes of adjustable autonomous agent software for control and fault management for complex systems. The AA T project has developed prototype adjustable autonomous agent software and human interfaces for cooperative fault management. This software builds on current autonomous agent technology by altering the architecture, components and interfaces for effective teamwork between autonomous systems and human experts. Autonomous agents include a planner, flexible executive, low level control and deductive model-based fault isolation. Adjustable autonomy is intended to increase the flexibility and effectiveness of fault management with an autonomous system. The test domain for this work is control of advanced life support systems for habitats for planetary exploration. The CONFIG hybrid discrete event simulation environment provides flexible and dynamically reconfigurable models of the behavior of components and fluids in the life support systems. Both discrete event and continuous (discrete time) simulation are supported, and flows and pressures are computed globally. This provides fast dynamic simulations of interacting hardware systems in closed loops that can be reconfigured during operations scenarios, producing complex cascading effects of operations and failures. Current object-oriented model libraries support modeling of fluid systems, and models have been developed of physico-chemical and biological subsystems for processing advanced life support gases. In FY01, water recovery system models will be developed.

Malin, Jane T.↗

NASA NTRSDate not supplied

Metallic Vs Inflatable Primary Structure: A Comprehensive Trade for a Mars Transit Habitat

Large diameter inflatable habitat solutions are hypothesized to have an advantage over traditional metallic habitats of equal volume and functional requirements in terms of minimizing mass. A fair and comprehensive trade of metallic primary structure versus inflatable softgoods primary structure for a Mars Transit Habitat was conducted by The Boeing Company under the NASA Next Space Technologies for Exploration Partnerships-2 (NextSTEP-2)Appendix A contract in order to determine the minimum mass option from a system level. A Mars Transit Habitat is a major system mass driver because small increases in the mass can create large mass changes in the propulsive stage, adding complexity and cost to the mission. Three different vehicle configurations were traded using a fixed volume constraint and the same Ground Rules and Assumptions(GR&A)provided by NASA. The configurations were 1) 5.5 m diameter metallic habitat, 2) 7.0 m diameter metallic habitat, and 3) 7.63 m diameter inflatable habitat. In order to complete the trade, each configuration was analyzed and sized, but a system level approach had to be taken to ensure other aspects and subsystems besides the structure were captured. The primary functions (i.e. restraint layer, bladder, multilayer insulation [MLI], micro-meteoroid orbital debris [MMOD]) and strength advantages of softgoods are well understood, but there were other system level impacts that were discovered or addressed that are unique to softgoods. For the metallic structure, a modern and mass optimal material and manufacturing process was adopted to ensure the lightest weight options were evaluated. Two different aluminium lithium structures were evaluated, a longer length 5.5 m diameter and a shorter length 7 m diameter structure. The trade demonstrates that each configuration is feasible and close to the target dry mass for the Mars Transit Habitat Trans-Martian Injection burn. System level mass was the primary consideration, but since the three concepts were close in total mass, a clear winner did not arise. Secondary factors were evaluated such as architecture habitability (human factors), development considerations, on-orbit activation and outfitting, extensibility to other applications, and configuration flexibility. The aggregation of the lowest mass, most benefits, and fewest challenges resulted in the 5.5m diameter metallic configuration being the most favorable.

Matthew Ziglar↗

NASA NTRS1994

Renaissance architecture for Ground Data Systems

The Mission Operations and Data Systems Directorate (MO&DSD) has embarked on a new approach for developing and operating Ground Data Systems (GDS) for flight mission support. This approach is driven by the goals of minimizing cost and maximizing customer satisfaction. Achievement of these goals is realized through the use of a standard set of capabilities which can be modified to meet specific user needs. This approach, which is called the Renaissance architecture, stresses the engineering of integrated systems, based upon workstation/local area network (LAN)/fileserver technology and reusable hardware and software components called 'building blocks.' These building blocks are integrated with mission specific capabilities to build the GDS for each individual mission. The building block approach is key to the reduction of development costs and schedules. Also, the Renaissance approach allows the integration of GDS functions that were previously provided via separate multi-mission facilities. With the Renaissance architecture, the GDS can be developed by the MO&DSD or all, or part, of the GDS can be operated by the user at their facility. Flexibility in operation configuration allows both selection of a cost-effective operations approach and the capability for customizing operations to user needs. Thus the focus of the MO&DSD is shifted from operating systems that we have built to building systems and, optionally, operations as separate services. Renaissance is actually a continuous process. Both the building blocks and the system architecture will evolve as user needs and technology change. Providing GDS on a per user basis enables this continuous refinement of the development process and product and allows the MO&DSD to remain a customer-focused organization. This paper will present the activities and results of the MO&DSD initial efforts toward the establishment of the Renaissance approach for the development of GDS, with a particular focus on both the technical and process implications posed by Renaissance to the MO&DSD.

Perkins, Dorothy C.↗

NASA NTRS2015

Ethernet for Aerospace Applications - Ethernet Heads for the Skies

One of the goals of aerospace applications is to reduce the cost and complexity of avionic systems. Ethernet is a highly scalable, flexible, and popular protocol. The aerospace market is large, with a forecasted production of over 50,000 turbine-powered aircraft valued at $1.7 trillion between 2012 and 2022. Boeing estimates demand for commercial aircraft by 2033 to total over 36,000 with a value of over $5 trillion. In 2014 US airlines served over 750 million passengers and this is growing over 2% yearly. Electronic fly-by-wire is now used for all airliners and high performance aircraft. Although Ethernet has been widely used for four decades, its use in aerospace applications is just beginning to become common. Ethernet is the universal solution in commercial networks because of its high bandwidths, lower cost, openness, reliability, maintainability, flexibility, and interoperability. However, when Ethernet was designed applications with time-critical, safety relevant and deterministic requirements were not given much consideration. Many aerospace applications use a variety of communication architectures that add cost and complexity. Some of them are SpaceWire, MIL-STD-1553, Avionics Full Duplex Switched Ethernet (AFDX), and Time-Triggered Ethernet (TTE). Aerospace network designers desire to decrease the number of networks to reduce cost and effort while improving scalability, flexibility, openness, maintainability, and reliability. AFDX and TTE are being considered more for critical aerospace systems because they provide redundancy, failover protection, guaranteed timing, and frame priority and are based on Ethernet IEEE 802.3. This paper explores the use of AFDX and TTE for aerospace applications.

Ethernet↗

NASA NTRS2010

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↗

NASA NTRSDate not supplied

Component Level Regression Testing in a Hierarchical Architecture

The Goddard Earth Observing System (GEOS) is an Earth system model consisting of a large suite of individual model components that can be coupled in a flexible manner to investigate a variety of Earth science issues. Specific GEOS model configurations are composed as a hierarchical collection of components based on the Earth System Modeling Framework (ESMF). Regression testing of GEOS is currently limited to (1) full system tests that are poor at isolating specific defects and (2) a suite of unit tests which have very limited coverage. As part of our approach to improve upon the current testing situation, we have prototyped the capability to perform regression tests on individual GEOS components by leveraging and extending existing checkpoint/restart capabilities. In our implementation, each ESMF component has 3 states: Import (what it needs to run), Export (which it needs to provide to other components), and Internal (the component state proper). By capturing, Import, Export and Internal states for a given component during a ull run of GEOS, a generic driver can then rerun the component offline and compare expected exports with those that have been saved. The hierarchical structure of GEOS introduces an interesting wrinkle when trying to test components that in turn drive interacting child components. To fully isolate a parent component, we use the approach of software mocks, in which the exports of children are also saved during the initial capture run of GEOS. Then when testing the parent component, the children components are replaced by a generic mock component that produces exports from the previously saved data and ensures that that all interdependencies among children components are satisfied.

Thomas Clune↗

NASA NTRSDate not supplied

Component Level Testing in a Hierarchical Architecture

Tom Clune↗