Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 703 records · Page 39

The Langley Advanced Real-Time Simulation (ARTS) system

This paper is intended as a status report on the ARTS system. It briefly describes the architecture and principal subsystems including: the CAMAC network system (hardware and software), the clocking system, the signal converters, the control consoles, and the minicomputer and microcomputer interfaces. The performance and reliability of the system exceeds expectations and component failure data over an 11-month period are presented. Planned enhancements, including the replacement of the mainframe computers, are discussed.

Crawford, Daniel J.↗

Measurement and analysis of workload effects on fault latency in real-time systems

The authors demonstrate the need to address fault latency in highly reliable real-time control computer systems. It is noted that the effectiveness of all known recovery mechanisms is greatly reduced in the presence of multiple latent faults. The presence of multiple latent faults increases the possibility of multiple errors, which could result in coverage failure. The authors present experimental evidence indicating that the duration of fault latency is dependent on workload. A synthetic workload generator is used to vary the workload, and a hardware fault injector is applied to inject transient faults of varying durations. This method makes it possible to derive the distribution of fault latency duration. Experimental results obtained from the fault-tolerant multiprocessor at the NASA Airlab are presented and discussed.

Woodbury, Michael H.↗

Capabilities of the Materials Contamination Team at Marshall Space Flight Center

The Materials Contamination Team at the Marshall Space Flight Center (MSFC) has been recognized for its contributions supporting the National Aeronautics and Space Administration (NASA) spacecraft development programs. These programs include the Reusable Solid Rocket Motor (RSRM), Chandra X-Ray Observatory, and the International Space Station (ISS). The Environmental Effects Group, with the Materials Contamination Team and the Space Environmental Effects Team has been an integral part of NASA's success by the testing, evaluation, and qualification of materials, hardware, and processes. This paper focuses on the capabilities of the Materials Contamination Team. The Materials Contamination Team's realm of responsibility includes establishing contamination control during all phases of hardware development, including design, manufacturing, assembly, test, transportation, launch site processing, on-orbit exposure, return, and refurbishment. The team continues its mission of reducing the risk of equipment failure due to molecular or particulate contamination. Contamination is a concern in the Space Shuttle with sensitive bond-lines and reactive fluid (liquid oxygen) compatibility as well as for spacecraft with sensitive optics, such as Hubble Space Telescope and Chandra X-ray Observatory. The Materials Contamination Team has a variety of facilities and instrumentation capable of contaminant detection, identification, and monitoring. The team addresses material applications dealing with environments, including production facilities, clean rooms, and on-orbit exposure. The optically stimulated electron emission (OSEE) system, the Ultraviolet (UV) fluorescence (UVF) surface contamination detection, and the Surface Optics Corporation 400 (SOC 400) portable hand-held Fourier Transform Infrared (FTIR) spectrometer are state-of-the-art tools for in-process molecular contamination detection. The team of engineers and technicians also develop contamination calibration standards and evaluate new surface cleanliness inspection technologies. The team utilizes facilities for on-orbit simulation testing of materials for outgassing and molecular film deposition characteristics in the presence of space environmental effects, such as Atomic Oxygen (AO) and UV radiation exposure. The Materials Contamination Team maintains databases for process materials as well as outgassing and optical compatibility test results for specific environments.

Burns, Howard↗

Handheld White Light Interferometer for Measuring Defect Depth in Windows

Accurate quantification of defects (scratches and impacts) is vital to the certification of flight hardware and other critical components. The amount of damage to a particular component contributes to the performance, reliability, and safety of a system, which ultimately affects the success or failure of a mission or test. The launch-commit criteria on a Space Shuttle Orbiter window are governed by the depth of the defects that are identified by a visual inspection. This measurement of a defect is not easy to obtain given the environment, size of the defect, and location of the window(s). The determination of depth has typically been performed by taking a mold impression and measuring the impression with an optical profiling instrument. Another method of obtaining an estimate of the depth is by using a refocus microscope. To use a refocus microscope, the surface of the glass and bottom of the defect are, in turn, brought into focus by the operator. The amount of movement between the two points corresponds to the depth of the defect. The refocus microscope requires a skilled operator and has been proven to be unreliable when used on Orbiter windows. White light interferometry was chosen as a candidate to replace the refocus microscope. The White Light Interferometer (WLI) was developed to replace the refocus microscope as the instrument used for measuring the depth of defects in Orbiter windows. The WLI consists of a broadband illumination source, interferometer, detector, motion control, displacement sensor, mechanical housing, and support electronics. The illumination source for the WLI is typically a visible light emitting diode (LED) or a near-infrared superluminescent diode (SLD) with power levels of less than a milliwatt. The interferometer is a Michelson configuration consisting of a 1-in. (2.5-cm) cube beam splitter, a 0.5-in. (1.3-cm) optical window as a movable leg (used to closely match the return intensity of the fixed leg from the window), and a mirrored prism to fold the optics into the mechanical housing. The detector may be one of many C-mount CCD (charge-coupled device) cameras. Motion is provided by a commercial nanostepping motor with a serial interface. The displacement sensor is a custom device specifically designed for this application. The mechanical housing and support electronics were designed to integrate the various components into an instrument that could be physically handled by a technician and easily transported.

Youngquist, Robert↗

Resilient Space Habitat Design Using Safety Controls

Space habitats will involve a complex and tightly coupled combination of hardware, software, and humans, while operating in challenging environments that pose many risks, both known and unknown. It will not be possible to design habitats that are immune to failure, nor will it be possible to foresee all possible failures. Rather than aiming for designs where ―failure is not an option,‖ habitats must be resilient to disruptions. We propose an approach to resilient design for space habitats based on the concept of safety controls from system safety engineering. We model disruptions using a state-and-trigger approach, where the space habitat is in one of three distinct states at each time instance: nominal, hazardous, or accident. We use safety controls as ways of preventing a system from entering or remaining in a hazardous or accident state. We develop a safety control option space for the habitat, from which designers can select the set of safety controls that best meet resilience, performance, and other system goals. The safety control option space is likely to be large, accordingly, we design a database that links safety controls to the applicable states and triggers. We demonstrate our approach on the early design stage of a Martian space habitat.

Safety↗

Initial Criticality Assessments to Guide FMEAs on Rocket Engine Hot Fire Testing

Presented is an explanation of the use of the Initial Criticality Assessment (ICA) technique, a triage process for prioritizing required Failure Modes and Effects Analysis (FMEAs), for the European Service Module's main propulsion system's hot-fire test bed at White Sands New Mexico. Rather than instinctively performing many FMEAs of subsystems, or one large system level FMEA where every subcomponent is analyzed, the ICA guided an informed analysis of only the hardware that had a large impact to hazards. The low criticality hardware was documented via the ICA and no FMEA was performed; the work could then focus on the high criticality hardware. Thus a savings of Program resources was achieved. The experiences gained in creating these ICAs for this international collaborative project confirmed that the need for continuous communication across the technical teams is one of the greatest areas of emphasis. The European Space Agency (ESA) is developing the European Service Module (ESM), with its primary contractor, Airbus Defence and Space in Germany, for delivery to the National Aeronautics and Space Administration (NASA). The module will be equipped with a total of 21 engines to support NASA’s Orion spacecraft: one U.S. Space Shuttle Orbital Maneuvering System-Engine (OMS-E), eight auxiliary thrusters and 12 smaller RCS (Reaction Control System) thrusters. The main ESM propulsion system, used for large translational maneuvers, consists of one OMS-E... To qualify the design of the ESM propulsion subsystem (PSS) an all-steel Propulsion Qualification Module (PQM) structure is used to test the propulsion systems on Orion, including “hot firing” of the OMS engine, thrusters, and RCS. The PQM has been developed as a hot-fire test bed to be tested at the NASA White Sands Test Facility (WSTF). One of the objectives of the testing is to assure that the OMS-E can be safely operated with the PQM. Testing will also demonstrate that the PQM can set the proper upstream pressures and temperatures for the OMS-E to operate nominally given the PQM has never been tested in hot-fire operation with OMS-E before. In order to safely conduct the test campaign, hardware such as the engine subassembly, fluid feed lines, valves, electrical power lines, instrumentation, stiff links, installation Ground Support Equipment (GSE), and diffuser [whose objectives are to collect the exhaust of the OMS-E to actively cool down the exhaust gases, reduce thermal exchanges, and create a vacuum at OMS-E level before igniting], had to be analyzed for any hazards and failure modes.

Fault Tolerance↗

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 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↗

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.↗