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 973 records · Page 54

Copilot 3

Ultra-critical systems require high-level assurance, which cannot always be guaranteed in compile time. The use of runtime verification (RV) enables monitoring these systems in runtime, to detect property violations early and limit their potential consequences. The introduction of monitors in ultra-critical systems poses a challenge, as failures and delays in the RV subsystem could affect other subsystems and threaten the mission as a whole. This paper presents Copilot 3, a runtime verification framework for real-time embedded systems. Copilot monitors are written in a compositional, stream-based language with support for a variety of Temporal Logics (TL), which results in robust, high-level specifications that are easier to understand than their traditional counterparts. The framework translates monitor specifications into C code with static memory requirements, which can be compiled to run on embedded hardware. This paper presents version 3 of the Copilot language, demonstrates its suitability with a number of examples, and discusses its use in larger applications. Additionally, it describes the framework?s architecture, its implementation as a Domain Specific Language (DSL) embedded in Haskell, and the progress of the project over the years.

Ivan Perez↗

Interpretation of Space Shuttle telemetry

This paper describes the Payload Deployment and Retrieval System (PDRS) Failure Analysis and Diagnosis problem, our planned use of an expert system employing the C Language Integrated Production System (CLIPS) language to solve it, and our progress to date. In addition, it will address the importance of the overall design within the context of automation in the RTDS architecture, the methodology used, and the validation approach taken. The Decision Support System will evolve as a modularized rule-based system programmed in the CLIPS expert system language. Each of five modules represents a subsystem of the RMS and includes the positioning and retention hardware (MPM/MRL), the Display & Control panel (D8C), the Arm Based Electronics (ABE), the End Effector (EE), and the Orbiter to RMS data interface unit (MCIU). The MPM/MRL subsystem was chosen as the target of a prototype development and its knowledge base is completed. Testing and validation of the software is conducted by experienced mission controllers. The initial design stages for the D&C panel module are beginning.

Culp, Donald R.↗

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy M. Mclaughlin↗

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy McLaughlin↗

Evaluation of Anomaly Detection Capability for Ground-Based Pre-Launch Shuttle Operations

This chapter will provide a thorough end-to-end description of the process for evaluation of three different data-driven algorithms for anomaly detection to select the best candidate for deployment as part of a suite of IVHM (Integrated Vehicle Health Management) technologies. These algorithms were deemed to be sufficiently mature enough to be considered viable candidates for deployment in support of the maiden launch of Ares I-X, the successor to the Space Shuttle for NASA's Constellation program. Data-driven algorithms are just one of three different types being deployed. The other two types of algorithms being deployed include a "nile-based" expert system, and a "model-based" system. Within these two categories, the deployable candidates have already been selected based upon qualitative factors such as flight heritage. For the rule-based system, SHINE (Spacecraft High-speed Inference Engine) has been selected for deployment, which is a component of BEAM (Beacon-based Exception Analysis for Multimissions), a patented technology developed at NASA's JPL (Jet Propulsion Laboratory) and serves to aid in the management and identification of operational modes. For the "model-based" system, a commercially available package developed by QSI (Qualtech Systems, Inc.), TEAMS (Testability Engineering and Maintenance System) has been selected for deployment to aid in diagnosis. In the context of this particular deployment, distinctions among the use of the terms "data-driven," "rule-based," and "model-based," can be found in. Although there are three different categories of algorithms that have been selected for deployment, our main focus in this chapter will be on the evaluation of three candidates for data-driven anomaly detection. These algorithms will be evaluated upon their capability for robustly detecting incipient faults or failures in the ground-based phase of pre-launch space shuttle operations, rather than based oil heritage as performed in previous studies. Robust detection will allow for the achievement of pre-specified minimum false alarm and/or missed detection rates in the selection of alert thresholds. All algorithms will also be optimized with respect to an aggregation of these same criteria. Our study relies upon the use of Shuttle data to act as was a proxy for and in preparation for application to Ares I-X data, which uses a very similar hardware platform for the subsystems that are being targeted (TVC - Thrust Vector Control subsystem for the SRB (Solid Rocket Booster)).

Martin, Rodney Alexander↗

A Relief Zone Architecture for Enhanced Durability of Ultrathin Membranes in Electrochemical Conversion Devices

Premature cell failures in electrochemical conversion systems often result when membrane electrode assemblies (MEAs) are prepared with ultra-thin (= 15 micrometer-thick) polymer electrolyte membranes (PEMs). These high-performance PEMs are susceptible to mechanical degradation from stress concentrations arising from component and device-level integration. Herein, a relief zone was developed to mitigate mechanical degradation by alleviating excess and non-uniform compression across the active area. Relief zones, created through the ablation of carbonaceous diffusion material achieves a seamless adaptation across a range of MEA dimensions and electrochemical applications without need for costly hardware modifications. This concept was demonstrated using fuel cells as a case study. Accelerated stress test (AST) validations yielded a 6-fold improvement for MEAs prepared with relief zones (i.e., lifetime approximately 1500 h) compared to those fabricated using conventional edge-protection techniques, showcasing the utility of this technique in decoupling integration and device-level engineering effects from intrinsic material limitations for durable electrochemical devices.

14 SOLAR ENERGY↗

Control algorithm implementation for a redundant degree of freedom manipulator

This project's purpose is to develop and implement control algorithms for a kinematically redundant robotic manipulator. The manipulator is being developed concurrently by Odetics Inc., under internal research and development funding. This SBIR contract supports algorithm conception, development, and simulation, as well as software implementation and integration with the manipulator hardware. The Odetics Dexterous Manipulator is a lightweight, high strength, modular manipulator being developed for space and commercial applications. It has seven fully active degrees of freedom, is electrically powered, and is fully operational in 1 G. The manipulator consists of five self-contained modules. These modules join via simple quick-disconnect couplings and self-mating connectors which allow rapid assembly/disassembly for reconfiguration, transport, or servicing. Each joint incorporates a unique drive train design which provides zero backlash operation, is insensitive to wear, and is single fault tolerant to motor or servo amplifier failure. The sensing system is also designed to be single fault tolerant. Although the initial prototype is not space qualified, the design is well-suited to meeting space qualification requirements. The control algorithm design approach is to develop a hierarchical system with well defined access and interfaces at each level. The high level endpoint/configuration control algorithm transforms manipulator endpoint position/orientation commands to joint angle commands, providing task space motion. At the same time, the kinematic redundancy is resolved by controlling the configuration (pose) of the manipulator, using several different optimizing criteria. The center level of the hierarchy servos the joints to their commanded trajectories using both linear feedback and model-based nonlinear control techniques. The lowest control level uses sensed joint torque to close torque servo loops, with the goal of improving the manipulator dynamic behavior. The control algorithms are subjected to a dynamic simulation before implementation.

Cohan, Steve↗

PhoneSat: Ground Testing of a Phone-Based Prototype Bus

Most of the key capabilities that are requisite of a satellite bus are housed in today's smart phones. PhoneSat refers to an initiative to build a ground-based prototype vehicle that could all the basic functionality of a satellite, including attitude control, using a smart Phone as its central hardware. All components used were also low cost Commercial off the Shelf (COTS). In summer 2009, an initial prototype was created using the LEGO Mindstorm toolkit demonstrating simple attitude control. Here we report on a follow up initiative to design, build and test a vehicle based on the Google s smart phone Nexus One. The report includes results from initial thermal-vacuum chamber tests and low altitude sub-orbital rocket flights which show that, at least for short durations, the Nexus One phone is able to withstand key aspects of the space environment without failure. We compare the sensor data from the Phone's accelerometers and magnetometers with that of an external microelectronic inertial measurement unit.

Felix, Carmen↗

Space Shuttle Upgrades Advanced Hydraulic Power System

Three Auxiliary Power Units (APU) on the Space Shuttle Orbiter each provide 145 hp shaft power to a hydraulic pump which outputs 3000 psi hydraulic fluid to 41 hydraulic actuators. A hydrazine fuel powered APU utilized throughout the Shuttle program has undergone many improvements, but concerns remain with flight safety, operational cost, critical failure modes, and hydrazine related hazards. The advanced hydraulic power system (AHPS), also known as the electric APU, is being evaluated as an upgrade to replace the hydrazine APU. The AHPS replaces the high-speed turbine and hydrazine fuel supply system with a battery power supply and electric motor/pump that converts 300 volt electrical power to 3000 psi hydraulic power. AHPS upgrade benefits include elimination of toxic hydrazine propellant to improve flight safety, reduction in hazardous ground processing operations, and improved reliability. Development of this upgrade provides many interesting challenges and includes development of four hardware elements that comprise the AHPS system: Battery - The battery provides a high voltage supply of power using lithium ion cells. This is a large battery that must provide 28 kilowatt hours of energy over 99 minutes of operation at 300 volts with a peak power of 130 kilowatts for three seconds. High Voltage Power Distribution and Control (PD&C) - The PD&C distributes electric power from the battery to the EHDU. This 300 volt system includes wiring and components necessary to distribute power and provide fault current protection. Electro-Hydraulic Drive Unit (EHDU) - The EHDU converts electric input power to hydraulic output power. The EHDU must provide over 90 kilowatts of stable, output hydraulic power at 3000 psi with high efficiency and rapid response time. Cooling System - The cooling system provides thermal control of the Orbiter hydraulic fluid and EHDU electronic components. Symposium presentation will provide an overview of the AHPS upgrade, descriptions of the four hardware elements, and a summary of development results to date.

Source record↗

Hazard Analysis for Building 34 Vacuum Glove Box Assembly

One of the characteristics of an effective safety program is the recognition and control of hazards before mishaps or failures occur. Conducting potentially hazardous tests necessitates a thorough hazard analysis in order to prevent injury to personnel, and to prevent damage to facilities and equipment. The primary purpose of this hazard analysis is to define and address the potential hazards and controls associated with the Building 34 Vacuum Glove Box Assembly, and to provide the applicable team of personnel with the documented results. It is imperative that each member of the team be familiar with the hazards and controls associated with his/her particular tasks, assignments and activities while interfacing with facility test systems, equipment and hardware. In fulfillment of the stated purposes, the goal of this hazard analysis is to identify all hazards that have the potential to harm personnel, damage the facility or its test systems or equipment, test articles, Government or personal property, or the environment. This analysis may also assess the significance and risk, when applicable, of lost test objectives when substantial monetary value is involved. The hazards, causes, controls, verifications, and risk assessment codes have been documented on the hazard analysis work sheets in Appendix A of this document. The preparation and development of this report is in accordance with JPR 1700.1, "JSC Safety and Health Handbook" and JSC 17773 Rev D "Instructions for Preparation of Hazard Analysis for JSC Ground Operations".

Meginnis, Ian↗

Theoretical Analysis and Experimental Validation of Flying-Capacitor Multilevel Converters Under Short-Circuit Fault Conditions

Addressing the increasing demand for high- efficiency and high-power-density converters, the flying-capacitor multilevel converter has shown itself as a promising topology. A key advantage of this topology is the reduced voltage rating of the switches, though also makes it vulnerable to device failure during short-circuit conditions. Despite large interest in fault-tolerant operation of these converters, alongside detailed descriptions of flying capacitor balancing, little research has focused on the converter short-circuit fault analysis, which may cause a switch failure if not properly designed for. Therefore, this work presents a comprehensive model describing the large- signal short-circuit switching behavior of a general N -level flying- capacitor multilevel converter. Highly simplified models used to predict the evolution of the switch current and voltage stress during the fault are proposed, targeted at practicing engineers for conservative design guidelines. These models are used to determine the critical time for remedial action of the converter before reaching some predefined maximum conditions. A 2-to-10- level fully-configurable flying-capacitor multilevel converter and a fault circuit hardware prototype are used to experimentally perform different short-circuit tests that show a good match to the measured behavior.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Demonstrating the Effect of Particle Impact Dampers on the Random Vibration Response and Fatigue Life of Printed Wiring Assemblies

In a recent experimental study, small Particle Impact Dampers (PID) were bonded directly to the surface of printed circuit board (PCB) or printed wiring assemblies (PWA), reducing the random vibration response and increasing the fatigue life. This study provides data verifying practicality of this approach. The measured peak strain and acceleration response of the fundamental out of plane bending mode was significantly attenuated by adding a PID device. Attenuation of this mode is most relevant to the fatigue life of a PWA because the local relative displacements between the board and the supported components, which ultimately cause fatigue failures of the electrical leads of the board-mounted components are dominated by this mode. Applying PID damping at the board-level of assembly provides mitigation with a very small mass impact, especially as compared to isolation at an avionics box or shelf level of assembly. When compared with other mitigation techniques at the PWA level (board thickness, stiffeners, constrained layer damping), a compact PID device has the additional advantage of not needing to be an integral part of the design. A PID can simply be bonded to heritage or commercial off the shelf (COTS) hardware to facilitate its use in environments beyond which it was originally qualified. Finite element analysis and test results show that the beneficial effect is not localized and that the attenuation is not due to the simple addition of mass. No significant, detrimental reduction in frequency was observed. Side-by-side life testing of damped and un-damped boards at two different thicknesses (0.070" and 0.090") has shown that the addition of a PID was much more significant to the fatigue life than increasing the thickness. High speed video, accelerometer, and strain measurements have been collected to correlate with analytical results.

Knight, Brent↗

Development of Composite Sandwich Bonded Longitudinal Joints for Space Launch Vehicle Structures

The NASA Composite Technology for Exploration (CTE) Project is developing and demonstrating critical composite technologies with a focus on composite bonded joints; incorporating materials, design/analysis, manufacturing, and tests that utilize NASA’s expertise and capabilities. The project has goals of advancing composite technologies and providing lightweight structures to support future NASA exploration missions. In particular, the CTE project will demonstrate weight-saving, performance-enhancing composite bonded joint technology for Space Launch System (SLS)-scale composite hardware. Advancements from the CTE project may be incorporated as future block upgrades for SLS structural components. This paper discusses the details of the development of a composite sandwich bonded longitudinal joint for a generic space launch vehicle structure called the CTE Point Design. The paper includes details of the design, analysis, materials, manufacturing, and testing of sub-element joint test articles to test the capability of the joint design. The test results show that the composite longitudinal bonded joint design significantly exceeds the design loads with a 2.0 factor of safety. Analysis pre-test failure predictions for all sub-element bonded joint test coupons were all within 10% of the average test coupon failure load. This testing and analysis provides confidence in the potential use of composite bonded joints for future launch vehicle structures.

Segal, Kenneth N.↗

NASA Kennedy Space Center Swamp Works: Innovation Methods for Advanced Research & Technology Development

Kennedy Space Center’s (KSC) Swamp Works, provides government and commercial space ventures with the technologies required for working and living on the surfaces of the Moon or other planets and bodies in our solar system. The Swamp Works team establishes agile, innovative and cost effective exploration mission solutions through leveraging of partnerships across NASA, industry and academia. Concepts start small and build up efficiently, with lean development processes and a hands on approach. Testing is performed in early stages to drive design improvements and progressively increase Technology Readiness Levels (TRL). Swamp Works provides concepts, architecture studies and trades, designs, data, technology development, technology demonstration hardware, flight hardware, testing, flight support and knowledge in support of the development of surface systems. This paper will summarize the state of the art in innovation methods, and it will compare the various other methods to how innovation is accomplished at the NASA KSC Swamp Works. Since 2013, Swamp Works has developed a wide variety of technologies, and has demonstrated viable methods for innovation while also collaborating with other government agencies, industry and academia to support space exploration. These methods focus on agile design, test, build iterations where each cycle of prototyping results in improved knowledge and designs. Failures are tole rated in the early stages of these iterations, since the overall development cycle is shorter more efficient and cost effective by retiring risk early in the cycle. Momentum is maintained and the development teams remain highly motivated by the high level of team work, technical excellence, engagement and creative freedom.

Robotic Mining↗

An integrated approach to system design, reliability, and diagnosis

The requirement for ultradependability of computer systems in future avionics and space applications necessitates a top-down, integrated systems engineering approach for design, implementation, testing, and operation. The functional analyses of hardware and software systems must be combined by models that are flexible enough to represent their interactions and behavior. The information contained in these models must be accessible throughout all phases of the system life cycle in order to maintain consistency and accuracy in design and operational decisions. One approach being taken by researchers at Ames Research Center is the creation of an object-oriented environment that integrates information about system components required in the reliability evaluation with behavioral information useful for diagnostic algorithms. Procedures have been developed at Ames that perform reliability evaluations during design and failure diagnoses during system operation. These procedures utilize information from a central source, structured as object-oriented fault trees. Fault trees were selected because they are a flexible model widely used in aerospace applications and because they give a concise, structured representation of system behavior. The utility of this integrated environment for aerospace applications in light of our experiences during its development and use is described. The techniques for reliability evaluation and failure diagnosis are discussed, and current extensions of the environment and areas requiring further development are summarized.

Patterson-Hine, F. A.↗

Advanced Information Processing System (AIPS)-based fault tolerant avionics architecture for launch vehicles

An avionics architecture for the advanced launch system (ALS) that uses validated hardware and software building blocks developed under the advanced information processing system program is presented. The AIPS for ALS architecture defined is preliminary, and reliability requirements can be met by the AIPS hardware and software building blocks that are built using the state-of-the-art technology available in the 1992-93 time frame. The level of detail in the architecture definition reflects the level of detail available in the ALS requirements. As the avionics requirements are refined, the architecture can also be refined and defined in greater detail with the help of analysis and simulation tools. A useful methodology is demonstrated for investigating the impact of the avionics suite to the recurring cost of the ALS. It is shown that allowing the vehicle to launch with selected detected failures can potentially reduce the recurring launch costs. A comparative analysis shows that validated fault-tolerant avionics built out of Class B parts can result in lower life-cycle-cost in comparison to simplex avionics built out of Class S parts or other redundant architectures.

Lala, Jaynarayan H.↗

Identification and interpretation of patterns in rocket engine data: Artificial intelligence and neural network approaches

This paper describes an expert system which is designed to perform automatic data analysis, identify anomalous events, and determine the characteristic features of these events. We have employed both artificial intelligence and neural net approaches in the design of this expert system. The artificial intelligence approach is useful because it provides (1) the use of human experts' knowledge of sensor behavior and faulty engine conditions in interpreting data; (2) the use of engine design knowledge and physical sensor locations in establishing relationships among the events of multiple sensors; (3) the use of stored analysis of past data of faulty engine conditions; and (4) the use of knowledge-based reasoning in distinguishing sensor failure from actual faults. The neural network approach appears promising because neural nets (1) can be trained on extremely noisy data and produce classifications which are more robust under noisy conditions than other classification techniques; (2) avoid the necessity of noise removal by digital filtering and therefore avoid the need to make assumptions about frequency bands or other signal characteristics of anomalous behavior; (3) can, in effect, generate their own feature detectors based on the characteristics of the sensor data used in training; and (4) are inherently parallel and therefore are potentially implementable in special-purpose parallel hardware.

Ali, Moonis↗

EMU Lessons Learned Database

As manned space exploration takes on the task of traveling beyond low Earth orbit, many problems arise that must be solved in order to make the journey possible. One major task is protecting humans from the harsh space environment. The current method of protecting astronauts during Extravehicular Activity (EVA) is through use of the specially designed Extravehicular Mobility Unit (EMU). As more rigorous EVA conditions need to be endured at new destinations, the suit will need to be tailored and improved in order to accommodate the astronaut. The Objective behind the EMU Lessons Learned Database(LLD) is to be able to create a tool which will assist in the development of next-generation EMUs, along with maintenance and improvement of the current EMU, by compiling data from Failure Investigation and Analysis Reports (FIARs) which have information on past suit failures. FIARs use a system of codes that give more information on the aspects of the failure, but if one is unfamiliar with the EMU they will be unable to decipher the information. A goal of the EMU LLD is to not only compile the information, but to present it in a user-friendly, organized, searchable database accessible to all familiarity levels with the EMU; both newcomers and veterans alike. The EMU LLD originally started as an Excel database, which allowed easy navigation and analysis of the data through pivot charts. Creating an entry requires access to the Problem Reporting And Corrective Action database (PRACA), which contains the original FIAR data for all hardware. FIAR data are then transferred to, defined, and formatted in the LLD. Work is being done to create a web-based version of the LLD in order to increase accessibility to all of Johnson Space Center (JSC), which includes converting entries from Excel to the HTML format. FIARs related to the EMU have been completed in the Excel version, and now focus has shifted to expanding FIAR data in the LLD to include EVA tools and support hardware such as the Pistol Grip Tool (PGT) and the Battery Charger Module (BCM), while adding any recently closed EMU-related FIARs.

Matthews, Kevin M., Jr.↗