Search NASA⌕ Search

SEARCH · Search NASA

Results for “hardware reliability”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS1977

Traveling-wave tube reliability estimates, life tests, and space flight experience

Infant mortality, useful life, and wearout phase of twt life are considered. The performance of existing developmental tubes, flight experience, and sequential hardware testing are evaluated. The reliability history of twt's in space applications is documented by considering: (1) the generic parts of the tube in light of the manner in which their design and operation affect the ultimate reliability of the device, (2) the flight experience of medium power tubes, and (3) the available life test data for existing space-qualified twt's in addition to those of high power devices.

Lalli, V. R.↗
NASA NTRS2011

Composite Overwrapped Pressure Vessels (COPV): Flight Rationale for the Space Shuttle Program

Each Orbiter Vehicle (Space Shuttle Program) contains up to 24 Kevlar49/Epoxy Composite Overwrapped Pressure Vessels (COPV) for storage of pressurized gases. In the wake of the Columbia accident and the ensuing Return To Flight (RTF) activities, Orbiter engineers reexamined COPV flight certification. The original COPV design calculations were updated to include recently declassified Kevlar COPV test data from Lawrence Livermore National Laboratory (LLNL) and to incorporate changes in how the Space Shuttle was operated as opposed to orinigially envisioned. 2005 estimates for the probability of a catastrophic failure over the life of the program (from STS-1 through STS-107) were one-in-five. To address this unacceptable risk, the Orbiter Project Office (OPO) initiated a comprehensive investigation to understand and mitigate this risk. First, the team considered and eventually deemed unfeasible procuring and replacing all existing flight COPVs. OPO replaced the two vessels with the highest risk with existing flight spare units. Second, OPO instituted operational improvements in ground procedures to signficiantly reduce risk, without adversely affecting Shuttle capability. Third, OPO developed a comprehensive model to quantify the likelihood of occurrance. A fully-instrumented burst test (recording a lower burst pressure than expected) on a flight-certified vessel provided critical understanding of the behavior of Orbiter COPVs. A more accurate model was based on a newly-compiled comprehensive database of Kevlar data from LLNL and elsewhere. Considering hardware changes, operational improvements and reliability model refinements, the mean reliability was determined to be 0.998 for the remainder of the Shuttle Program (from 2007, for STS- 118 thru STS-135). Since limited hardware resources precluded full model validation through multiple tests, additional model confidence was sought through the first-ever Accelerated Stress Rupture Test (ASRT) of a flown flight article. A Bayesian statistical approach was developed to interpret possible test results. Since the lifetime observed in the ASRT exceeded initial estimates by one to two orders of magnitude, the Space Shuttle Program deemed there was significant conservatism in the model and accepted continued operation with existing flight hardware. Given the variability in tank-to-tank original prooftest response, a non-destructive evaluation (NDE) technique utilizing Raman Spectroscopy was developed to directly measure COPV residual stress state. Preliminary results showed that patterns of low fiber elastic strains over the outside vessel surface, together with measured permanent volume growth during proof, could be directly correlated to increased fiber stress ratios on the inside fibers adjacent to the liner, and thus reduced reliability.

Kezirian, Michael T.↗
DOE OSTI2020

Reliability Analysis for Unreliable FSM Computations

Finite State Machines (FSMs) are fundamental in both hardware design and software development. However, the reliability of FSM computations remains poorly understood. This becomes increasingly critical as the technology scaling becomes more aggressive. Existing reliability analyses are mainly designed for generic computations and are unaware of the special error tolerance characteristics in FSM computations. In this work, we introduce RelyFSM – a state-level reliability analysis framework for FSM computations. By qualitatively reasoning about the transition structures in FSM computations, RelyFSM can precisely capture their inherent error tolerance. Basically, RelyFSM takes an FSM specification as input and analyzes its reliability for a specific execution. At the core of the analysis is a set of mathematical models that accurately define the behaviors of unreliable FSM executions. Our evaluation with a spectrum of FSM benchmarks confirms the accuracy and efficiency of RelyFSM in analyzing the reliability of real-world FSM computations.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS2021

JSC Avionics Ionizing Radiation Effects Standard (AIRES)

This document, the JSC Engineering Directorate Avionics Ionizing Radiation Effects Standard (AIRES), provides design, test, and analysis requirements to ensure electronic hardware meets functional, performance and reliability requirements in the mission ionizing radiation environment. This suite of activities is referred to as Radiation Hardening Assurance (RHA) and is an integral part of the hardware design process.

Ionizing Radiation↗
NASA NTRS1990

An experimental evaluation of software redundancy as a strategy for improving reliability

The strategy of using multiple versions of independently developed software as a means to tolerate residual software design faults is suggested by the success of hardware redundancy for tolerating hardware failures. Although, as generally accepted, the independence of hardware failures resulting from physical wearout can lead to substantial increases in reliability for redundant hardware structures, a similar conclusion is not immediate for software. The degree to which design faults are manifested as independent failures determines the effectiveness of redundancy as a method for improving software reliability. Interest in multi-version software centers on whether it provides an adequate measure of increased reliability to warrant its use in critical applications. The effectiveness of multi-version software is studied by comparing estimates of the failure probabilities of these systems with the failure probabilities of single versions. The estimates are obtained under a model of dependent failures and compared with estimates obtained when failures are assumed to be independent. The experimental results are based on twenty versions of an aerospace application developed and certified by sixty programmers from four universities. Descriptions of the application, development and certification processes, and operational evaluation are given together with an analysis of the twenty versions.

Eckhardt, Dave E., Jr.↗
NASA NTRS1991

An experimental evaluation of software redundancy as a strategy for improving reliability

The strategy of using multiple versions of independently developed software as a means to tolerate residual software design faults is suggested by the success of hardware redundancy for tolerating hardware failires. Although, as generally accepted, the independence of hardware failures resulting from physical wearout can lead to substantial increases in reliability for redundant hardware structures, a similar conclusion is not immediate for software. The degree to which design faults are manifested as independent failures determines the effectiveness of redundancy as a method for improving software reliability. Interest in multi-version software centers on whether it provides an adequate measure of increased reliability to warrant its use in critical applications. The effectiveness of multi-version software is studied by comparing estimates of the failure probabilities of these systems with the failure probabilities of single versions. The estimates are obtained under a model of dependent failures and compared with the estimates obtained when failures are assumed to be independent. The experimental results are based on twenty versions of an aerospace application developed and certified by sixty programmers from four universities. Descriptions of the application, development and certifications processes, and operational evaluation are given together with an analysis of the twenty versions.

Eckhardt, Dave E.↗
NASA NTRS2013

RS-34 Phoenix (Peacekeeper Post Boost Propulsion System) Utilization Study

The Advanced Concepts Office (ACO) at the NASA Marshall Space Flight Center (MSFC) in conjunction with Pratt & Whitney Rocketdyne conducted a study to evaluate potential in-space applications for the Rocketdyne produced RS-34 propulsion system. The existing RS-34 propulsion system is a remaining asset from the de-commissioned United States Air Force Peacekeeper ICBM program, specifically the pressure-fed storable bipropellant Stage IV Post Boost Propulsion System, renamed Phoenix. MSFC gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in October 2009. RS-34 propulsion system components were harvested from stages supplied by the USAF and used on the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. MSFC is working closely with the USAF to obtain RS-34 stages for re-use opportunities. Prior to pursuit of securing the hardware, MSFC commissioned the Advanced Concepts Office to understand the capability and potential applications for the RS-34 Phoenix stage as it benefits NASA, DoD, and commercial industry. As originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy multiple payloads at various orbital locations. The RS-34 Phoenix Utilization Study sought to understand how the unique capabilities of the RS-34 Phoenix and its application to six candidate missions: 1) small satellite delivery (SSD), 2) orbital debris removal (ODR), 3) ISS re-supply, 4) SLS kick stage, 5) manned GEO servicing precursor mission, and an Earth-Moon L-2 Waypoint mission. The small satellite delivery and orbital debris removal missions were found to closely mimic the heritage RS-34 mission. It is believed that this technology will enable a small, low-cost multiple satellite delivery to multiple orbital locations with a single boost. For both the small satellite delivery and the orbital debris mission candidates, the RS-34 Phoenix requires the least amount of modification to the existing hardware. The results of the RS-34 Phoenix Utilization Study show that the system is technically sufficient to successfully support all of the missions analyzed.

Esther, Elizabeth A.↗
NASA NTRS2009

Test Rack Development for Extended Operation of Advanced Stirling Convertors at NASA Glenn Research Center

The U.S. Department of Energy (DOE), Lockheed Martin Space Company (LMSC), Sun power Inc., and NASA Glenn Research Center (GRC) have been developing an Advanced Stirling Radioisotope Generator (ASRG) for use as a power system on space science missions. This generator will make use of free-piston Stirling convertors to achieve higher conversion efficiency than currently available alternatives. NASA GRC's support of ASRG development includes extended operation testing of Advanced Stirling Convertors (ASCs) developed by Sunpower Inc. In the past year, NASA GRC has been building a test facility to support extended operation of a pair of engineering level ASCs. Operation of the convertors in the test facility provides convertor performance data over an extended period of time. Mechanical support hardware, data acquisition software, and an instrumentation rack were developed to prepare the pair of convertors for continuous extended operation. Short-term tests were performed to gather baseline performance data before extended operation was initiated. These tests included workmanship vibration, insulation thermal loss characterization, low-temperature checkout, and fUll-power operation. Hardware and software features are implemented to ensure reliability of support systems. This paper discusses the mechanical support hardware, instrumentation rack, data acquisition software, short-term tests, and safety features designed to support continuous unattended operation of a pair of ASCs.

Dugala, Gina M.↗
NASA NTRS2012

RS-34 Phoenix (Peacekeeper Post Boost Propulsion System) Utilization Study

The Advanced Concepts Office (ACO) at the NASA Marshall Space Flight Center (MSFC) in conjunction with Pratt & Whitney Rocketdyne conducted a study to evaluate potential in-space applications for the Rocketdyne produced RS-34 propulsion system. The existing RS-34 propulsion system is a remaining asset from the decommissioned United States Air Force Peacekeeper ICBM program; specifically the pressure-fed storable bipropellant Stage IV Post Boost Propulsion System, renamed Phoenix. MSFC gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in October 2009. RS-34 propulsion system components were harvested from stages supplied by the USAF and used on the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. Subsequently, MSFC is working closely with the USAF to obtain all the remaining RS-34 stages for re-use opportunities. Prior to pursuit of securing the hardware, MSFC commissioned the Advanced Concepts Office to understand the capability and potential applications for the RS-34 Phoenix stage as it benefits NASA, DoD, and commercial industry. Originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy multiple payloads at various orbital locations. The RS-34 Phoenix Utilization Study sought to understand how the unique capabilities of the RS-34 Phoenix and its application to six candidate missions: 1) small satellite delivery (SSD), 2) orbital debris removal (ODR), 3) ISS re-supply, 4) SLS kick stage, 5) manned GEO servicing precursor mission, and an Earth-Moon L-2 Waypoint mission. The small satellite delivery and orbital debris removal missions were found to closely mimic the heritage RS-34 mission. It is believed that this technology will enable a small, low-cost multiple satellite delivery to multiple orbital locations with a single boost. For both the small satellite delivery and the orbital debris mission candidates, the RS-34 Phoenix requires the least amount of modification to the existing hardware. The results of the RS-34 Phoenix Utilization Study show that the system is technically sufficient to successfully support all of the missions analyzed

Esther, Elizabeth A.↗
NASA NTRS2013

RS-34 (Peacekeeper Post Boost Propulsion System) Orbital Debris Application Concept Study

The Advanced Concepts Office (ACO) at the NASA Marshall Space Flight Center (MSFC) lead a study to evaluate the Rocketdyne produced RS-34 propulsion system as it applies to an orbital debris removal design reference mission. The existing RS-34 propulsion system is a remaining asset from the de-commissioned United States Air Force Peacekeeper ICBM program; specifically the pressure-fed storable bi-propellant Stage IV Post Boost Propulsion System. MSFC gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. Subsequently, MSFC is working closely with the USAF to obtain all the remaining RS-34 stages for re-use opportunities. Prior to pursuit of securing the hardware, MSFC commissioned the Advanced Concepts Office to understand the capability and potential applications for the RS-34 Phoenix stage as it benefits NASA, DoD, and commercial industry. Originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy multiple payloads at various orbital locations. The RS-34 Concept Study, preceded by a utilization study to understand how the unique capabilities of the RS-34 Phoenix and its application to six candidate missions, sought to further understand application for an orbital debris design reference mission as the orbital debris removal mission was found to closely mimic the heritage RS-34 mission. The RS-34 Orbital Debris Application Concept Study sought to identify multiple configurations varying the degree of modification to trade for dry mass optimization and propellant load for overall capability and evaluation of several candidate missions. The results of the RS-34 Phoenix Utilization Study show that the system is technically sufficient to successfully support all of the missions analyzed. The results and benefits of the RS-34 Orbital Debris Application Concept Study are presented in this paper.

Esther, Elizabeth A.↗
NASA NTRS2005

Highly Reliable, High-Speed, Unidirectional Serial Data Links

Highly reliable, high-speed, unidirectional serial data-communication subsystems have been proposed to be installed in an upgrade of the computing systems aboard the space shuttles. The basic design concept of these serial data links is also adaptable to terrestrial use in applications in which there are requirements for highly reliable serial data communications. The hardware and software aspects of the architecture of the data links are dictated largely by a requirement, in the original space-shuttle application, for one computer to monitor the memory transactions and memory contents of other computers in real time with high reliability and without reliance on requests for retransmission. To minimize weight while affording a capability to transfer data at a required rate of 2.56 x 10(exp 8) bits per second, it was decided that the links would be serial ones of the fiber-channel type. [Fiber channel denotes a type of serial computer bus that is used to connect a computer (usually a supercomputer) with a high-speed data storage device. Depending on the specific application, the physical connection between the transmitter and receiver could be made via an optical fiber or a twisted pair of wires.] Heretofore, fiber-channel links have ordinarily been bidirectional and have operated under protocols that provide for receiving stations to detect errors and request retransmission when necessary. In the present case, the time taken by processing to request retransmission would conflict with the requirement for real-time transfer of data. To ensure reliability without retransmission, a link according to the proposal would utilize a modified version of the normal fiberchannel character set in conjunction with forward error correction by means of a Reed-Solomon code (see figure). The Reed-Solomon encoding and decoding and the translations between the normal and modified character sets would be effected by logic circuitry external to the fiber-channel transmitter and receiver, which would be commercial off-the-shelf units. The receiving end of the link could detect and correct errors at a rate as high as 4 million times per second, if necessary. The receiver detects uncorrectable double-byte errors. It has been estimated that uncorrectable-error rate would amount to one failure in about 10(exp 19) characters.

Cole, Robert M.↗
NASA NTRS1989

On the feasibility of a spaceborne fault-tolerant hypercube

The feasibility of implementing a fault-tolerant hypercube architecture for space applications is discussed. Node-level architectures and designs are considered and a first-order reliability model is presented. It is shown how error recovery can be implemented using program rollback or roll-forward techniques. Shared memory augmentations to the message-passing structure can be used to get around the inefficiencies of multicomputers to provide efficient use of hardware to achieve the needed reliabilities while maintaining performance.

Rennels, David A.↗
NASA NTRS2015

Reliability and Probabilistic Risk Assessment - How They Play Together

PRA methodology is one of the probabilistic analysis methods that NASA brought from the nuclear industry to assess the risk of LOM, LOV and LOC for launch vehicles. PRA is a system scenario based risk assessment that uses a combination of fault trees, event trees, event sequence diagrams, and probability and statistical data to analyze the risk of a system, a process, or an activity. It is a process designed to answer three basic questions: What can go wrong? How likely is it? What is the severity of the degradation? Since 1986, NASA, along with industry partners, has conducted a number of PRA studies to predict the overall launch vehicles risks. Planning Research Corporation conducted the first of these studies in 1988. In 1995, Science Applications International Corporation (SAIC) conducted a comprehensive PRA study. In July 1996, NASA conducted a two-year study (October 1996 - September 1998) to develop a model that provided the overall Space Shuttle risk and estimates of risk changes due to proposed Space Shuttle upgrades. After the Columbia accident, NASA conducted a PRA on the Shuttle External Tank (ET) foam. This study was the most focused and extensive risk assessment that NASA has conducted in recent years. It used a dynamic, physics-based, integrated system analysis approach to understand the integrated system risk due to ET foam loss in flight. Most recently, a PRA for Ares I launch vehicle has been performed in support of the Constellation program. Reliability, on the other hand, addresses the loss of functions. In a broader sense, reliability engineering is a discipline that involves the application of engineering principles to the design and processing of products, both hardware and software, for meeting product reliability requirements or goals. It is a very broad design-support discipline. It has important interfaces with many other engineering disciplines. Reliability as a figure of merit (i.e. the metric) is the probability that an item will perform its intended function(s) for a specified mission profile. In general, the reliability metric can be calculated through the analyses using reliability demonstration and reliability prediction methodologies. Reliability analysis is very critical for understanding component failure mechanisms and in identifying reliability critical design and process drivers. The following sections discuss the PRA process and reliability engineering in detail and provide an application where reliability analysis and PRA were jointly used in a complementary manner to support a Space Shuttle flight risk assessment.

Safie, Fayssal M.↗
DOE OSTI2013

Architecture, implementation, and testing of a multiple-shell gas injection system for high current implosions on the Z accelerator

Tests are ongoing to conduct {approx}20 MA z-pinch implosions on the Z accelerator at Sandia National Laboratory using Ar, Kr, and D{sub 2} gas puffs as the imploding loads. The relatively high cost of operations on a machine of this scale imposes stringent requirements on the functionality, reliability, and safety of gas puff hardware. Here we describe the development of a prototype gas puff system including the multiple-shell nozzles, electromagnetic drivers for each nozzle's valve, a UV pre-ionizer, and an inductive isolator to isolate the {approx}2.4 MV machine voltage pulse present at the gas load from the necessary electrical and fluid connections made to the puff system from outside the Z vacuum chamber. This paper shows how the assembly couples to the overall Z system and presents data taken to validate the functionality of the overall system.

42 ENGINEERING↗
NASA NTRS1972

Failure modes, effects and criticality analyses.

Failure mode, effects and criticality analyses were developed by NASA as a means of assuring that hardware built for space applications has the desired reliability characteristics. The failure mode and effects analysis is a qualitative reliability technique for systematically analyzing each possible failure mode within a hardware system, and identifying the resulting effect on that system, the mission and personnel. The criticality analysis is a quantitative procedure which ranks the critical failure modes according to their probability of occurrence. This paper describes the failure modes, effects analysis and the criticality analysis. It employs a simple hardware system, not related to the aerospace field, to illustrate the method. It encourages application of this type of analysis to industrial development programs outside the aerospace and defense complex.

Jordan, W. E.↗
NASA NTRS1975

Space vehicle onboard command encoder

A flexible onboard encoder system was designed for the space shuttle. The following areas were covered: (1) implementation of the encoder design into hardware to demonstrate the various encoding algorithms/code formats, (2) modulation techniques in a single hardware package to maintain comparable reliability and link integrity of the existing link systems and to integrate the various techniques into a single design using current technology. The primary function of the command encoder is to accept input commands, generated either locally onboard the space shuttle or remotely from the ground, format and encode the commands in accordance with the payload input requirements and appropriately modulate a subcarrier for transmission by the baseband RF modulator. The following information was provided: command encoder system design, brassboard hardware design, test set hardware and system packaging, and software.

Source record↗
NASA NTRS1990

Issues in designing transport layer multicast facilities

Multicasting denotes a facility in a communications system for providing efficient delivery from a message's source to some well-defined set of locations using a single logical address. While modem network hardware supports multidestination delivery, first generation Transport Layer protocols (e.g., the DoD Transmission Control Protocol (TCP) (15) and ISO TP-4 (41)) did not anticipate the changes over the past decade in underlying network hardware, transmission speeds, and communication patterns that have enabled and driven the interest in reliable multicast. Much recent research has focused on integrating the underlying hardware multicast capability with the reliable services of Transport Layer protocols. Here, we explore the communication issues surrounding the design of such a reliable multicast mechanism. Approaches and solutions from the literature are discussed, and four experimental Transport Layer protocols that incorporate reliable multicast are examined.

Dempsey, Bert J.↗