Search NASA⌕ Search

SEARCH · Search NASA

Results for “hardware failure”

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 811 records · Page 45

Lessons Learned from Astrobee Operations on the International Space Station

Since its launch in 2019, NASA has been operating three Astrobee free-flying robots providing an autonomous and adaptable research platform aboard the International Space Station (ISS). These robots have not only facilitated a myriad of national and international research endeavors in microgravity but have also served as a STEM outreach platform for student competitions aboard the ISS. Amidst its extensive operational tenure, spanning over five years and exceeding 1200 hours of cumulative free-flyer operation as of April 2024, the Astrobee robots have encountered software and hardware anomalies. Despite its inherent design for on-orbit repair or replacement, certain anomalies have proven to be complex, necessitating remote resolution via software and firmware updates or, in extreme cases, hardware replacements or the return of faulty units to NASA's ground facilities for repair. Such challenges underscore the delicate balance between the autonomous functionality of Astrobee and the occasional need for human intervention to maintain optimal performance. One recurring point of failure identified during Astrobee's operational lifespan has been the SD card, a critical component utilized by the different Astrobee processors and the Dock Station. The occurrence of SD card anomalies, both on orbit and within ground units, has provided invaluable insights into the improvement of Astrobee's systems and mitigation to future faults. This presentation will focus on four key areas: 1. Overview of Faults and Anomalies: A comprehensive examination of the diverse array of faults and anomalies encountered by Astrobee and its associated systems both in orbit and on the ground. From software glitches to hardware malfunctions, this section provides insights into the challenges faced during Astrobee's operational tenure. 2. Resolution Processes and Procedures: An in-depth discussion of the methodologies and procedures implemented to resolve the encountered anomalies. This includes remote troubleshooting, software patches, firmware updates, and, when necessary, the logistics involved in hardware replacements or down-massing for repair. 3. Implementation of Software Updates and Hardware Upgrades: A detailed exploration of the strategies employed to mitigate the risk of recurring anomalies through the implementation of software updates and hardware upgrades. This section highlights the iterative nature of Astrobee's development, emphasizing the continuous pursuit of robustness and reliability. 4. Lessons Learned and Future Directions: Reflecting on the insights gained from addressing anomalies, this section examines the lessons learned and outlines future directions for enhancing Astrobee's robustness and resilience. It underscores the iterative nature of space exploration and the importance of adaptability and continuous improvement in the pursuit of scientific discovery. Through a nuanced examination of Astrobee's operational challenges and the strategies employed to overcome them, this presentation sheds light on the complexities of operating autonomous robotic systems in the ISS environment. It underscores NASA's commitment to pushing the boundaries of exploration and innovation while navigating the inherent challenges of space exploration.

Astrobee↗

Lessons Learned in Space Life Support System Testing

The earlier problems can be found and corrected, the easier and cheaper it is to fix them. Doing less testing saves cost and time but doing too little testing increases the risk of operational failures causing large costs and delays. Integrated test is necessary to determine if the subsystems work together and the overall architecture performs as intended. This report reviews the testing lessons learned from the NASA Systems Engineering Handbook, a National Research Council report, and five reviews of International Space Station (ISS) lessons learned. The five reviews all mention two important points. First, that testing should be performed on the final integrated system, one as close as possible to the intended flight system. Second, “test as you fly,” while operating as planned in an environment as close as possible to the expected flight environment. Other lessons are the need for extensive preflight ground testing, the need to establish and defend an adequate budget, the problems using protoflight hardware on ISS, and the benefit of having ISS as a zero gravity test bed. The major ISS life support systems, carbon dioxide, water recycling, and oxygen recovery, were protoflight systems with little testing before launch to ISS. The failure rates these systems have been much greater than predicted and this has caused dissatisfaction with the protoflight approach. The more costly traditional approach is building qualification and test units in addition to flight units. The test units are used to test, analyze, and fix failure modes. Other work shows that there is an optimum cost-effective intuitive appeal of a human ecosystem in space.

Life support↗

Pattern-based Modeling of High-Performance Computing Resilience

With the growing scale and complexity of high-performance computing (HPC) systems, resilience solutions that ensure continuity of service despite frequent errors and component failures must be methodically designed to balance the reliability requirements with the overheads to performance and power. Design patterns enable a structured approach to the development of resilience solutions, providing hardware and software designers with the building block elements for the rapid development of novel solutions and for adapting existing technologies for emerging, extreme-scale HPC environments. In this paper, we develop analytical models that enable designers to evaluate the reliability and performance characteristics of the design patterns. These models are particularly useful in building a unified framework that analyzes and compares various resilience solutions built using a combination of patterns.

Hukerikar, Saurabh↗

Development, Demonstration, and Control of a Testbed for Multiterminal HVDC System

This paper presents the development of a scaled four-terminal high-voltage direct current (HVDC) testbed, including hardware structure, communication architecture, and different control schemes. The developed testbed is capable of emulating typical operation scenarios including system start-up, power variation, line contingency, and converter station failure. Some unique scenarios are also developed and demonstrated, such as online control mode transition and station re-commission. In particular, a dc line current control is proposed, through the regulation of a converter station at one terminal. By controlling a dc line current to zero, the transmission line can be opened by using relatively low-cost HVDC disconnects with low current interrupting capability, instead of the more expensive dc circuit breaker. Utilizing the dc line current control, an automatic line current limiting scheme is developed. As a result, when a dc line is overloaded, the line current control will be automatically activated to regulate current within the allowable maximum value.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Mariner 10 Venus encounter

Review of the scientific objectives of the Mariner 10 mission with regard to observations of Venus during a flyby, and description of the equipment installed on the spacecraft to fulfill these objectives. A detailed description is given of the hardware modifications made to the payload specifically for the Venus sequence. In discussing the encounter operations, two spacecraft problems which significantly affected the Venus encounter sequence are cited - namely, a failure of the television optic heaters to come on shortly after launch, and the occurrence of a roll gyro oscillation.

Dunne, J. A.↗

Operational perspectives for performing microgravity science in orbit

The combination of automation and operator-based technologies is discussed with respect to orbital microgravity experiments in order to optimize the performance and results. A list of five design objectives is presented, and each item is examined in terms of on-orbit flight history to identify relevant examples. It is suggested that human factors be considered in hardware design and that in-flight maintenance operations be considered an integral part of a program. The operational design can produce more effective results when it is established for 'failures' and mission success operations. The design must also be approached in terms of both the limitations and advantages of microgravity. The overarching theme of the investigation is that the mix of automation and operator interaction should be optimized by automating routine tasks and using the operator for critical assessments.

Dunbar, Bonnie J.↗

The application of automated operations at the Institutional Processing Center

The JPL Institutional and Mission Computing Division, Communications, Computing and Network Services Section, with its mission contractor, OAO Corporation, have for some time been applying automation to the operation of JPL's Information Processing Center (IPC). Automation does not come in one easy to use package. Automation for a data processing center is made up of many different software and hardware products supported by trained personnel. The IPC automation effort formally began with console automation, and has since spiraled out to include production scheduling, data entry, report distribution, online reporting, failure reporting and resolution, documentation, library storage, and operator and user education, while requiring the interaction of multi-vendor and locally developed software. To begin the process, automation goals are determined. Then a team including operations personnel is formed to research and evaluate available options. By acquiring knowledge of current products and those in development, taking an active role in industry organizations, and learning of other data center's experiences, a forecast can be developed as to what direction technology is moving. With IPC management's approval, an implementation plan is developed and resources identified to test or implement new systems. As an example, IPC's new automated data entry system was researched by Data Entry, Production Control, and Advance Planning personnel. A proposal was then submitted to management for review. A determination to implement the new system was made and elements/personnel involved with the initial planning performed the implementation. The final steps of the implementation were educating data entry personnel in the areas effected and procedural changes necessary to the successful operation of the new system.

Barr, Thomas H.↗

Free-Swinging Failure Tolerance for Robotic Manipulators

Under this GSRP fellowship, software-based failure-tolerance techniques were developed for robotic manipulators. The focus was on failures characterized by the loss of actuator torque at a joint, called free-swinging failures. The research results spanned many aspects of the free-swinging failure-tolerance problem, from preparing for an expected failure to discovery of postfailure capabilities to establishing efficient methods to realize those capabilities. Developed algorithms were verified using computer-based dynamic simulations, and these were further verified using hardware experiments at Johnson Space Center.

English, James↗

Free-Swinging Failure Tolerance for Robotic Manipulators

Under this GSRP fellowship, software-based failure-tolerance techniques were developed for robotic manipulators. The focus was on failures characterized by the loss of actuator torque at a joint, called free-swinging failures. The research results spanned many aspects of the free-swinging failure-tolerance problem, from preparing for an expected failure to discovery of postfailure capabilities to establishing efficient methods to realize those capabilities. Developed algorithms were verified using computer-based dynamic simulations, and these were further verified using hardware experiments at Johnson Space Center.

English, James↗

Rotorcraft Diagnostics

Health management (HM) in any engineering systems requires adequate understanding about the system s functioning; a sufficient amount of monitored data; the capability to extract, analyze, and collate information; and the capability to combine understanding and information for HM-related estimation and decision-making. Rotorcraft systems are, in general, highly complex. Obtaining adequate understanding about functioning of such systems is quite difficult, because of the proprietary (restricted access) nature of their designs and dynamic models. Development of an EIM (exact inverse map) solution for rotorcraft requires a process that can overcome the abovementioned difficulties and maximally utilize monitored information for HM facilitation via employing advanced analytic techniques. The goal was to develop a versatile HM solution for rotorcraft for facilitation of the Condition Based Maintenance Plus (CBM+) capabilities. The effort was geared towards developing analytic and reasoning techniques, and proving the ability to embed the required capabilities on a rotorcraft platform, paving the way for implementing the solution on an aircraft-level system for consolidation and reporting. The solution for rotorcraft can he used offboard or embedded directly onto a rotorcraft system. The envisioned solution utilizes available monitored and archived data for real-time fault detection and identification, failure precursor identification, and offline fault detection and diagnostics, health condition forecasting, optimal guided troubleshooting, and maintenance decision support. A variant of the onboard version is a self-contained hardware and software (HW+SW) package that can be embedded on rotorcraft systems. The HM solution comprises components that gather/ingest data and information, perform information/feature extraction, analyze information in conjunction with the dependency/diagnostic model of the target system, facilitate optimal guided troubleshooting, and offer decision support for optimal maintenance.

Haste, Deepak↗

Potential Lunar In-Situ Resource Utilization Experiments and Mission Scenarios

The extraction and use of resources on the Moon, known as In-Situ Resource Utilization (ISRU), can potentially reduce the cost and risk of human lunar exploration while also increasing science achieved. By not having to bring all of the shielding and mission consumables from Earth and being able to make products on the Moon, missions may require less mass to accomplish the same objectives, carry more science equipment, go to more sites of exploration, and/or provide options to recover from failures not possible with delivery of spares and consumables from Earth alone. The concept of lunar ISRU has been considered and studied for decades, and scientists and engineers were theorizing and even testing concepts for how to extract oxygen from lunar soil even before the Apollo 11 mission to the Moon. There are four main areas where ISRU can significantly impact how human missions to the Moon will be performed: mission consumable production, civil engineering and construction, energy production, storage, and transfer, and manufacturing and repair. The area that has the greatest impact on mission mass, hardware design and selection, and mission architecture is mission consumable production, in particular, the ability to make propellants, life support consumables, and fuel cell reagents. Mission consumable production allows for refueling and reuse of spacecraft, increasing power production and storage, and increased capabilities and failure tolerance for crew life support. The other three areas allow for decreased mission risk due to radiation and plume damage, alternative power systems, and failure recover capabilities while also enabling infrastructure growth over Earth delivered assets. However, while lunar ISRU has significant potential for mass, cost, and risk reduction for human lunar missions, it has never been demonstrated before in space. To demonstrate that ISRU can meet mission needs and to increase confidence in incorporating ISRU capabilities into mission architectures, terrestrial laboratory and analog field testing along with robotic precursor missions are required. A stepwise approach with international collaboration is recommended. The first step is to understand the resources available through orbital and surface exploration missions. Resources of particular interest are hydrogen, hydroxyl, water, and other polar volatile resources recently measured by Chandrayaan, Lunar Reconnaissance Orbiter (LRO), and the Lunar Crater Observation and Sensing Satellite (LCROSS). The second step is to demonstrate critical aspects of ISRU systems to prove ISRU is feasible under lunar environmental and resource conditions (ex. subscale oxygen extraction from regolith). The third step is to perform integrated missions with ISRU and other connected systems, such as power, consumable storage, surface mobility, and life support at a relevant mission scale to demonstrate ISRU capabilities as well as the critical interfaces with other exploration systems. If possible, the mission should demonstrate the use of ISRU products (ex. in a rocket engine or fuel cell). This dress rehearsal mission would be the final step before full implementation of ISRU into human missions, and may be performed during human lunar exploration activities. This stepwise approach is the most conservative approach, and may only be possible with international cooperation due to the limited number of robotic missions each nation/space agency can perform within their budget.

Sanders, Gerald B.↗

Lessons Learned in Space Life Support System Testing

The earlier problems can be found and corrected, the easier and cheaper it is to fix them. Doing less testing saves cost and time but doing too little testing increases the risk of operational failures causing large costs and delays. Integrated test is necessary to determine if the subsystems work together and the overall architecture performs as intended. This report reviews the testing lessons learned from the NASA Systems Engineering Handbook, a National Research Council report, and five reviews of International Space Station (ISS) lessons learned. The five reviews all mention two important points. First, that testing should be performed on the final integrated system, one as close as possible to the intended flight system. Second, “test as you fly,” while operating as planned in an environment as close as possible to the expected flight environment. Other lessons are the need for extensive preflight ground testing, the need to establish and defend an adequate budget, the problems using protoflight hardware on ISS, and the benefit of having ISS as a zero gravity test bed. The major ISS life support systems, carbon dioxide removal, water recycling, and oxygen recovery, were protoflight systems with little testing before launch to ISS. The failure rates of these systems have been much greater than predicted and this has caused dissatisfaction with the protoflight approach. The more costly traditional approach builds qualification and test units in addition to flight units. The test units are used to find, analyze, and fix failure modes. Other work shows that there is an optimum cost-effective amount of testing when redundant systems must have a specified reliability and confidence.

Harry W. Jones↗

EPA requirements and programs

The proposed ERTS-DCS system is designed to allow EPA the capability to evaluate, through demonstrable hardware, the effectiveness of automated data collection techniques. The total effectiveness of any system is dependent upon many factors which include equipment cost, installation, maintainability, logistic support, growth potential, flexibility and failure rate. This can best be accomplished by installing the system at an operational environmental control agency (CAMP station) to insure that valid data is being obtained and processed. Consequently, it is imperative that the equipment interface must not compromise the validity of the sensor data nor should the experimental system effect the present operations of the CAMP station. Since both the system which is presently in use and the automatic system would be in operation in parallel, conformation and comparison are readily obtained.

Koutsandreas, J. D.↗

Spacecraft automated operations

Trends in automation of planetary spacecraft are examined using data from missions as far back as Mariner '67 and up to the highly sophisticated Galileo. Nine design considerations which influence the degree of automation such as protection against catastrophic failures, highly repetitive functions, loss of spacecraft communications, and the need for near-real-time adaptivity are discussed. Rapid growth of automation is shown in terms of on-board hardware by plots of number of processors on board, the average speed of processors, and total core memory. The number of commands transmitted from the ground has grown to 5 million bits in Voyager, so that increases in mission complexity have increased both in spacecraft automation and ground operations. Achieving greater automation by transferring ground operations to the spacecraft with the current means of controlling missions, are considered noting proposed changes. For the future, improved computer technology, more microprocessors and increased core storage will be used, and the number of automated functions and their complexity will grow. It is concluded that using the growing computational capability of spacecraft will achieve more autonomy thus reversing the trend of increased mission complexity and cost.

Bird, T. H.↗

Effects of AEA Cell-Bypass-Switch Closure on Charged EOS-Aqua NiH2 Cell

The nominal performance of AEA CBPD under simulated EOS-Aqua/Aura flight hardware configuration has been demonstrated. There is no evidence of cell rupture or excessive heat production during or after CBPD switch activation under simulated high cell impedance (open-circuit cell failure mode). Inadvertent CBPD switch activation with a charged cell (low impedance path) intermittently closes and opens up the switch, therefore the device may or may not provide protection against future open-circuit cell failure. Further testing with switches F01 and F02 may provide clarification. The formation of a continuous low impedance path (a homogeneous low melting point alloy), has been confirmed - which is the expected mode of operation.

Keys, Denney↗

Transient Region Coverage in the Propulsion IVHM Technology Experiment

Over the last several years researchers at NASA Glenn and Ames Research Centers have developed a real-time fault detection and isolation system for propulsion subsystems of future space vehicles. The Propulsion IVHM Technology Experiment (PITEX), as it is called follows the model-based diagnostic methodology and employs Livingstone, developed at NASA Ames, as its reasoning engine. The system has been tested on,flight-like hardware through a series of nominal and fault scenarios. These scenarios have been developed using a highly detailed simulation of the X-34 flight demonstrator main propulsion system and include realistic failures involving valves, regulators, microswitches, and sensors. This paper focuses on one of the recent research and development efforts under PITEX - to provide more complete transient region coverage. It describes the development of the transient monitors, the corresponding modeling methodology, and the interface software responsible for coordinating the flow of information between the quantitative monitors and the qualitative, discrete representation Livingstone.

Balaban, Edward↗

Design, Fabrication, and Test of a LOX/LCH4 RCS Igniter at NASA

A workhorse liquid oxygen-liquid methane (LOX/LCH4) rocket igniter was recently tested at NASA Glenn Research Center s (GRC) Research Combustion Laboratory (RCL). These tests were conducted in support of the Reaction Control Engine (RCE) development task of the Propulsion and Cryogenics Advanced Development (PCAD) project. The igniter was a GRC in-house design used to evaluate the ignition processes for LOX/LCH4. The test matrix was developed to examine the flammability of LOX/LCH4 over a range of oxidizer-to-fuel mixture ratios, both in the core fuel flow and total flow. In addition, testing also examined the durability of the hardware by accumulating ignition pulses. Over the course of testing, a total of 1402 individual ignition pulses were successfully demonstrated over the range of mixture ratios. Testing was halted after the failure of the ceramic in the igniter spark plug.

Schneider, Steven J.↗

Power Goals for NASA's Exploration Program

Exciting Future Programs ahead for NASA. Power is needed for all Exploration vehicles and for the missions. For long term missions as in Lunar and Mars programs, safe, high energy/ultra high energy batteries are required. Safety is top priority for human-rated missions. Two-fault tolerance to catastrophic failures is required for human-rated safety To meet power safety goals -inherent cell safety may be required; it can lessen complexity of external protective electronics and prevents dependency on hardware that may also have limitations. Inherent cell safety will eliminate the need to carry out screening of all cells (X-rays, vibration, etc.)

Jeevarajan, Judith A.↗