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 1,009 records · Page 56
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

NASA GRC Fatigue Crack Initiation Life Prediction Models

Metal fatigue has plagued structural components for centuries, and it remains a critical durability issue in today's aerospace hardware. This is true despite vastly improved and advanced materials, increased mechanistic understanding, and development of accurate structural analysis and advanced fatigue life prediction tools. Each advance is quickly taken advantage of to produce safer, more reliable, more cost effective, and better performing products. In other words, as the envelope is expanded, components are then designed to operate just as close to the newly expanded envelope as they were to the initial one. The problem is perennial. The economic importance of addressing structural durability issues early in the design process is emphasized. Tradeoffs with performance, cost, and legislated restrictions are pointed out. Several aspects of structural durability of advanced systems, advanced materials and advanced fatigue life prediction methods are presented. Specific items include the basic elements of durability analysis, conventional designs, barriers to be overcome for advanced systems, high-temperature life prediction for both creep-fatigue and thermomechanical fatigue, mean stress effects, multiaxial stress-strain states, and cumulative fatigue damage accumulation assessment.

Arya, Vinod K.↗
NASA NTRS2004

Contingency Power Study for Short Haul Civil Tiltrotor

NASA has concluded from previous studies that the twin engine tiltrotor is the most economical and technologically viable rotorcraft for near-term civil applications. Twin engine civil rotorcraft must be able to hover safely on one engine in an emergency. This emergency power requirement generally results in engines 20 to 50 percent larger than needed for normal engine operation, negatively impacting aircraft economics. This study identifies several contingency power enhancement concepts, and quantifies their potential to reduce aircraft operating costs. Many unique concepts were examined, and the selected concepts are simple, reliable, and have a high potential for near term realization. These engine concepts allow extremely high turbine temperatures during emergency operation by providing cooling to the power turbine and augmenting cooling of both turbines and structural hardware. Direct operating cost are reduced 3 to percent, which could yield a 30 to 80 percent increase in operating profits. The study consists of the definition of an aircraft economics model and a baseline engine, and an engine concept screening study, and a preliminary definition of the selected concepts. The selected concepts are evaluated against the baseline engine, and the critical technologies and development needs are identified, along with applications for this technology.

D'Angelo, Marin M.↗
NASA NTRS2007

J-2X: Progress on the Ares Upper Stage Engine

NASA's Vision for Exploration requires a safe, reliable, affordable upper stage engine to power the Ares I Crew Launch Vehicle (CLV) and the Ares V Cargo Launch Vehicle (CaLV). The J-2X engine epitomizes NASA's philosophy of employing legacy knowledge, heritage hardware, and commonality to carry the next generation of explorers into low-Earth orbit and out into the solar system. As envisioned by the Exploration Systems Architecture Study (ESAS), the reference lunar mission would begin by launching the Ares V into orbit with the Earth Departure Stage (EDS) transporting the Lunar Surface Access Module (LSAM), followed by the Ares I, carrying the Orion Crew Exploration Vehicle, which would rendezvous with the EDS/LSAM before beginning its journey to the Moon.

Byrd, Thomas D.↗
NASA NTRS2008

NASA's Ares I and Ares V Launch Vehicles--Effective Space Operations Through Efficient Ground Operations

The United States (U.S.) is charting a renewed course for lunar exploration, with the fielding of a new human-rated space transportation system to replace the venerable Space Shuttle, which will be retired after it completes its missions of building the International Space Station (ISS) and servicing the Hubble Space Telescope. Powering the future of space-based scientific exploration will be the Ares I Crew Launch Vehicle, which will transport the Orion Crew Exploration Vehicle to orbit where it will rendezvous with the Altair Lunar Lander, which will be delivered by the Ares V Cargo Launch Vehicle (fig. 1). This configuration will empower rekindled investigation of Earth's natural satellite in the not too distant future. This new exploration infrastructure, developed by the National Aeronautics and Space Administration (NASA), will allow astronauts to leave low-Earth orbit (LEO) for extended lunar missions and preparation for the first long-distance journeys to Mars. All space-based operations - to LEO and beyond - are controlled from Earth. NASA's philosophy is to deliver safe, reliable, and cost-effective architecture solutions to sustain this multi-billion-dollar program across several decades. Leveraging SO years of lessons learned, NASA is partnering with private industry and academia, while building on proven hardware experience. This paper outlines a few ways that the Engineering Directorate at NASA's Marshall Space Flight Center is working with the Constellation Program and its project offices to streamline ground operations concepts by designing for operability, which reduces lifecycle costs and promotes sustainable space exploration.

Singer, Christopher E.↗
NASA NTRS2009

Biomorphic Multi-Agent Architecture for Persistent Computing

A multi-agent software/hardware architecture, inspired by the multicellular nature of living organisms, has been proposed as the basis of design of a robust, reliable, persistent computing system. Just as a multicellular organism can adapt to changing environmental conditions and can survive despite the failure of individual cells, a multi-agent computing system, as envisioned, could adapt to changing hardware, software, and environmental conditions. In particular, the computing system could continue to function (perhaps at a reduced but still reasonable level of performance) if one or more component( s) of the system were to fail. One of the defining characteristics of a multicellular organism is unity of purpose. In biology, the purpose is survival of the organism. The purpose of the proposed multi-agent architecture is to provide a persistent computing environment in harsh conditions in which repair is difficult or impossible. A multi-agent, organism-like computing system would be a single entity built from agents or cells. Each agent or cell would be a discrete hardware processing unit that would include a data processor with local memory, an internal clock, and a suite of communication equipment capable of both local line-of-sight communications and global broadcast communications. Some cells, denoted specialist cells, could contain such additional hardware as sensors and emitters. Each cell would be independent in the sense that there would be no global clock, no global (shared) memory, no pre-assigned cell identifiers, no pre-defined network topology, and no centralized brain or control structure. Like each cell in a living organism, each agent or cell of the computing system would contain a full description of the system encoded as genes, but in this case, the genes would be components of a software genome.

Lodding, Kenneth N.↗
NASA NTRS2008

On-Site Fabrication Infrastructure to Enable Efficient Exploration and Utilization of Space

Unlike past one-at-a-time mission approaches, system-of-systems infrastructures will be needed to enable ambitious scenarios for sustainable future space exploration and utilization. So what do we do when we get to the moon for sustainable exploration. On-site fabrication infrastructure will be needed to support habitat structure development, tools and mechanical part fabrication, as well as repair and replacement of ground support and space mission hardware such as life support items, vehicle components and crew systems. The on-site fabrication infrastructure will need the In Situ Fabrication and Repair (ISFR) element, which is working in conjunction with the In Situ Resources Utilization (ISRU) element, to live off the land. The ISFR element has worked closely with the ISRU element in the past year to assess the ability of using lunar regolith as a viable feedstock for fabrication material. Preliminary work has shown promise and the ISFR Element will continue to concentrate on this activity. Fabrication capabilities have been furthered with the process certification effort that, when completed, will allow for space-qualified hardware to be manufactured. Materials being investigated include titanium and aluminum alloys as well as lunar regolith simulants with binders. This paper addresses the latest advancements made in the fabrication of infrastructures that support efficient, affordable, reliable infrastructures for both space exploration systems and logistics; infrastructures that allow sustained, affordable and highly effective operations on the Moon and beyond.

Howell, Joe T.↗
NASA NTRS2012

Rocket engine injectorhead with flashback barrier

Propellants flow through specialized mechanical hardware that is designed for effective and safe ignition and sustained combustion of the propellants. By integrating a micro-fluidic porous media element between a propellant feed source and the combustion chamber, an effective and reliable propellant injector head may be implemented that is capable of withstanding transient combustion and detonation waves that commonly occur during an ignition event. The micro-fluidic porous media element is of specified porosity or porosity gradient selected to be appropriate for a given propellant. Additionally the propellant injector head design integrates a spark ignition mechanism that withstands extremely hot running conditions without noticeable spark mechanism degradation.

Mungas, Gregory S.↗
NASA NTRS2014

UAS-Systems Integration, Validation, and Diagnostics Simulation Capability

As part of the Phase 1 efforts of NASA's UAS-in-the-NAS Project a task was initiated to explore the merits of developing a system simulation capability for UAS to address airworthiness certification requirements. The core of the capability would be a software representation of an unmanned vehicle, including all of the relevant avionics and flight control system components. The specific system elements could be replaced with hardware representations to provide Hardware-in-the-Loop (HWITL) test and evaluation capability. The UAS Systems Integration and Validation Laboratory (UAS-SIVL) was created to provide a UAS-systems integration, validation, and diagnostics hardware-in-the-loop simulation capability. This paper discusses how SIVL provides a robust and flexible simulation framework that permits the study of failure modes, effects, propagation paths, criticality, and mitigation strategies to help develop safety, reliability, and design data that can assist with the development of certification standards, means of compliance, and design best practices for civil UAS.

Buttrill, Catherine W.↗
NASA NTRS2013

Microfluidic Flame Barrier

Propellants flow through specialized mechanical hardware that is designed for effective and safe ignition and sustained combustion of the propellants. By integrating a micro-fluidic porous media element between a propellant feed source and the combustion chamber, an effective and reliable propellant injector head may be implemented that is capable of withstanding transient combustion and detonation waves that commonly occur during an ignition event. The micro-fluidic porous media element is of specified porosity or porosity gradient selected to be appropriate for a given propellant. Additionally the propellant injector head design integrates a spark ignition mechanism that withstands extremely hot running conditions without noticeable spark mechanism degradation.

Mungas, Gregory S.↗
NASA NTRS2019

Adaptations of Guidance, Navigation and Control Verification and Validation Philosophies for Small Spacecraft

Decades of experience developing increasingly capable and more complex space-craft have resulted in a set of accepted practices and philosophies to verify and validate (V&V) guidance, navigation, and control (GN&C) subsystems. Until recently, small, low-cost spacecraft have had very simple or non-existent GN&C subsystems requiring minimal or no subsystem testing. As the next generation of small spacecraft take on more challenging GN&C requirements, the GN&C community is struggling with how to scale the subsystem V&V effort to produce spacecraft approaching the reliability of flagship-class missions while staying within the reduced resources of a small satellite project. For this paper, we will examine five aspects of GN&C V&V (requirements definition, software testing and analysis, hardware component testing, integrated vehicle testing, and in-flight V&V) and compare the V&V campaign of a flagship-class mission (Mars 2020) to that of two recent, successful CubeSat missions: ASTERIA and MarCO. Experiences from the development of these CubeSats yield valuable lessons learned and guidelines for future small spacecraft designers.

Pong, Christopher M.↗
NASA NTRS2016

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗
DOE OSTI2019

Photovoltaic Inverter Reliability Assessment

As the price of PV modules drops, the price of power electronics become more important. Power electronics now constitute 8%-12% of the total lifetime PV cost. As of 2010, the inverter and associated power conditioning components accounted for $\$0.25$/W, well above the DOE benchmark of $\$0.12$/W by 2020. As efforts to reduce PV module costs yield diminishing returns, the importance of understanding and reducing inverter costs becomes an increasingly critical and cost-effective investment toward achieving the DOE SunShot goals. With this in view, this report showcases and describes an approach to help assess and predict the reliability of photovoltaic (PV) inverters. To predict the reliability, thermal cycling is considered as a prominent stressor in the inverter system. To evaluate the impacts of thermal cycling, a detailed linearized model of the PV inverter is developed along with controllers. This research also develops models and methods to compute the losses of the power electronics switches and other components in a PV inverter. The losses are then used to estimate the junction and heat sink temperature. The model is verified by developing an in-house inverter. Additionally, to assess the scalability of the research, the hardware inverter is placed inside a thermal chamber to verify the losses for different ambient temperatures. After the verification of the model, a reduced-order model of the inverter is implemented to translate the profile of ambient temperature and solar irradiance into the profile of junction temperatures of the switches. The estimated junction temperature data are used to identify inverter reliability indices and predict the useful lifetime of the inverter system. After developing the models to predict the useful lifetime of the system, the impact of reactive power on the overall reliability of the system will be studied. The first chapter involves the motivation behind the research on assessing the reliability of PV inverters. The inverter power stage and controller design of the power converter used in this research is also explained in detail in this chapter. The second chapter presents the various losses of the power converter system and the translation of power loss into temperature increase with thermal modeling. The results of the loss modeling and the thermal modeling are also explained in detail in this chapter. The third chapter involves implementing the reduced-order model to translate the mission profile of ambient temperature and solar irradiance into profile of the junction temperatures of the switches. The final chapter involves identifying reliability indices, which are of interest for this system to predict the remaining useful life of the system, and concludes with the impact of reactive power on the overall reliability of the inverter system.

14 SOLAR ENERGY↗
DOE OSTI2012

Cooperation Reliability Testing of the Clipper Windpower Liberty 2.5 MW Turbine: Cooperative Research and Development Final Report

Clipper Windpower (CWP) has developed the Liberty 2.5 MW wind turbine. The development, manufacturing, and certification process depends heavily on being able to validate the full-scale system design and performance under load in both an accredited structural test facility and through accredited field testing. CWP requested that DOE/ NREL upgrade blade test capabilities to perform a scope of workincluding structural testing of the C-96 blade used on the CWP Liberty turbine. This funds-in CRADA was developed to upgrade NREL blade test capability, while enabling certification testing of the C-96 blade through the facility and equipment upgrades. NREL shared resource funds were used to develop hardware necessary to structurally attach a large wind turbine to the test stand at the NWTC.Participant funds-in monies were used for developing the test program.

17 WIND ENERGY↗
DOE OSTI2011

OPSAID improvements and capabilities report.

Process Control System (PCS) and Industrial Control System (ICS) security is critical to our national security. But there are a number of technological, economic, and educational impediments to PCS owners implementing effective security on their systems. Sandia National Laboratories has performed the research and development of the OPSAID (Open PCS Security Architecture for Interoperable Design), a project sponsored by the US Department of Energy Office of Electricity Delivery and Energy Reliability (DOE/OE), to address this issue. OPSAID is an open-source architecture for PCS/ICS security that provides a design basis for vendors to build add-on security devices for legacy systems, while providing a path forward for the development of inherently-secure PCS elements in the future. Using standardized hardware, a proof-of-concept prototype system was also developed. This report describes the improvements and capabilities that have been added to OPSAID since an initial report was released. Testing and validation of this architecture has been conducted in another project, Lemnos Interoperable Security Project, sponsored by DOE/OE and managed by the National Energy Technology Laboratory (NETL).

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗
NASA NTRS2007

Quiet Spike Build-Up Ground Vibration Testing Approach

NASA's Dryden Flight Research Center uses a modified F-15B (836) aircraft as a testbed for a variety of flight research:experiments mounted underneath the aircraft fuselage. The F-15B was selected to fly Gulfstream Aerospace Corporation's (GAC)QuietSpike(TM)(QS) project; however, this experiment is very unique and unlike any of the previous testbed experiments flown on the F-15B. It involves the addition of a relatively long quiet spike boom attached to the radar bulkhead of the aircraft. This QS experiment is a stepping stone to airframe structural morphing technologies designed to mitigate sonic born strength of business jets over land. The QS boom is a concept in Which an aircraft's front-end would be extended prior to supersonic acceleration. This morphing would effectively lengthen the aircraft, reducing peak sonic boom amplitude, but is also expected to partition the otherwise strong bow shock into a series of reduced-strength, non-coalescing shocklets. Prior to flying the Quietspike(TM) experiment on the F-15B aircraft several ground vibration tests (GVT) were required in order to understand the QS modal characteristics and coupling effects with the F-15B. However, due to the project's late hardware delivery of the QS and the intense schedule, a "traditional" GVT of the mated F-1513 Quietspike(tm) ready-for-flight configuration would not have left sufficient time available for the finite element model update and flutter analyses before flight testing. Therefore, a "nontraditional" ground vibration testing approach was taken. The objective of the QuietSpike (TM) build-up ground testing approach was to ultimately obtain confidence in the F-15B Quietspike(TM) finite element model (FEM) to be used for the flutter analysis. In order to obtain the F15B QS FEM with reliable foundation stiffness between the QS and the F-15B radar bulkhead as well as QS modal characteristics, several different GVT configurations were performed. EAch of the four GVT's performed had a specific objective. The overall intent was to provide adequate data which would replicate a "traditional" F-15B QS GVT with actual ready-for-flight hardware. NASA Dryden was tasked with the conduct of the 1st, 2nd and 4th GVT and the 3rd GVT was GAC's responsibility. In order for this build-up GVT approach to be feasible, it was absolutely critical that each GVT configuration matched as closely as possible the connection interface configuration between the and aircraft bulkhead.

Spivey, Natalie D.↗
DOE OSTI2017

How reliable are efficiency measurements of perovskite solar cells? The first inter-comparison, between two accredited and eight non-accredited laboratories

Perovskite materials have generated significant interest from academia and industry as a potential component in next-generation, high-efficiency, low-cost, photovoltaic (PV) devices. The record efficiency reported for perovskite solar cells has risen rapidly, and is now more than 22%. However, due to their complex dynamic behaviour, the process of measuring the efficiency of perovskite solar cells appears to be much more complicated than for other technologies. It has long been acknowledged that this is likely to greatly reduce the reliability of reported efficiency measurements, but the quantitative extent to which this occurs has not been determined. To investigate this, we conduct the first major inter-comparison of this PV technology. The participants included two labs accredited for PV performance measurement (CSIRO and NREL) and eight PV research laboratories. We find that the inter-laboratory measurement variability can be almost ten times larger for a slowly responding perovskite cell than for a control silicon cell. We show that for such a cell, the choice of measurement method, far more so than measurement hardware, is the single-greatest cause for this undesirably large variability. We provide recommendations for identifying the most appropriate method for a given cell, depending on its stabilization and degradation behaviour. Moreover, the results of this study suggest that identifying a consensus technique for accurate and meaningful efficiency measurements of perovskite solar cells will lead to an immediate improvement in reliability. This, in turn, should assist device researchers to correctly evaluate promising new materials and fabrication methods, and further boost the development of this technology.

14 SOLAR ENERGY↗
DOE OSTI2017

MACORD: Online Adaptive Machine Learning Framework for Silent Error Detection

Future HPC systems with ever-increasing resource capacity (such as compute cores, memory and storage) may significantly increase the risks on reliability. Silent data corruptions (SDCs) or silent errors are one of the major sources that corrupt HPC execution results. Unlike fail-stop errors, SDCs are rather harmful and dangerous in that they cannot be detected by hardware. We propose an online machine-learning based silent data corruption detection framework (abbreviated as MACORD) for detecting SDCs in HPC applications. In particular, we comprehensively investigate the prediction ability of a multitude of machine-learning algorithms in our study, and enable the detector to automatically select the best-fit algorithms at runtime to adapt to the data dynamics. Our learning framework exhibits low memory overhead (less than 1%), since it takes only spatial features (i.e., neighboring data values for each data point in the current time step) into the training data. Experiments based on real-world scientific applications/benchmarks show that our framework can get the detection sensitivity (i.e., recall) up to 99% while the false positive rate is limited to 0.1% in most cases, which is one order of magnitude improvement compared with the latest state-of-art spatial technique.

Subasi, Omer↗
NASA NTRS1999

Assurance of COTS Boards for Space Flight

Space Flight hardware and software designers are increasingly turning to Commercial-Off-the-Shelf (COTS) products in hopes of meeting the demands imposed on them by projects with short development cycle times. The Technology Validation Assurance (TVA) team at NASA GSFC has embarked on applying a method for inserting COTS hardware into the Spartan 251 spacecraft. This method includes Procurement, Characterization, Ruggedization/Remediation and Verification Testing process steps which are intended to increase the user's confidence in the hardware's ability to function in the intended application for the required duration. As this method is refined with use, it has the potential for becoming a benchmark for industry-wide use of COTS in high reliability systems.

Plante Jeannette↗