Search NASA⌕ Search

SEARCH · Search NASA

Results for “fault tolerant systems”

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 559 records · Page 31

Future NTP Development Synergy Leveraged from Current J-2X Engine Development

This paper is a discussion of how the many long-lead development elements required for the realization of a future nuclear thermal propulsion (NTP) system can be effectively leveraged from the ongoing work being conducted on the J-2X engine program for the Constellation Program. Development studies conducted to date for NTP forward planning have identified a number of technical areas that will require advancement to acceptable technology readiness levels (TRLs) before they can be utilized in NTP system development. These include high-temperature, high-area ratio nozzle extension; long-life, low-NPSP. turbomachinery; and low-boiloff propellant management; and a qualified nuclear fuel element. The current J-2X program is working many of these areas that can be leveraged to support NTP development in a highly compatible and synergistic fashion. In addition to supporting technical development, there are other programmatic issues being worked in the J-2X program that can be leveraged by a future NTP development program. These include compliance with recently-evolved space system requirements such as human-rating, fault tolerance and fracture control. These and other similar mandatory system requirements have been adopted by NASA and can result in a significant technical impact beyond elevation of the root technologies required by NTP. Finally, the exploitation of experience, methodologies, and procedures developed by the J-2X program in the areas of verification, qualification, certification, altitude simulation testing, and facility definition will be especially applicable to a future NTP system. The similarities in system mission (in-space propulsion) and operational environment (vacuum, zero-gee) between J-2X and NTP make this highly synergistic. Thus, it can be $hown that the collective benefit of leveraging experience and technologies developed during the J-2X program can result in significant savings in development cost and schedule for NTP.

Ballard, Richard O.↗

Space Shuttle critical function audit

A large fault-tolerance model of the main propulsion system of the US space shuttle has been developed. This model is being used to identify single components and pairs of components that will cause loss of shuttle critical functions. In addition, this model is the basis for risk quantification of the shuttle. The process used to develop and analyze the model is digraph matrix analysis (DMA). The DMA modeling and analysis process is accessed via a graphics-based computer user interface. This interface provides coupled display of the integrated system schematics, the digraph models, the component database, and the results of the fault tolerance and risk analyses.

Sacks, Ivan J.↗

Evolution of safety-critical requirements post-launch

This paper reports the results of a small study of requirements changes to the onboard software of three spacecraft subsequent to launch. Only those requirement changes that resulted from post-launch anoma-lies (i.e., during operations) were of interest here, since the goal was to better understand the relation-ship between critical anomalies during operations and how safety-critical requirements evolve. The results of the study were surprising in that anomaly-driven, post-launch requirements changes were rarely due to previous requirements having been incorrect. Instead, changes involved new requirements (1) for the software to handle rare events or (2) for the software to compensate for hardware failures or limitations. The prevalence of new requirements as a result of post-launch anomalies suggests a need for increased requirements-engineering support of maintenance activities in these systems. The results also confirm both the difficulty and the benefits of pursuing requirements completeness, especially in terms of fault tolerance, during development of critical systems.

Software requirements↗

Benchmarking Variables for Checkpointing in HPC Applications

Checkpoint/Restart (C/R) is a widely used fault tolerance mechanism in converged systems of cloud, edge, and HPC. However, users often rely on their experience to determine which variables to checkpoint, as there is currently no benchmark that can provide a reference. This can result in checkpointing redundant or even incorrect variables. To address this issue, we propose a benchmark suite that includes critical variables for checkpointing, which have been manually identified, and a method for identifying those critical variables, with 20 representative HPC applications. Our method involves analyzing data dependency between variables to identify critical variables analytically. We verify the identified variables' correctness with a widely used C/R library FTI by an ablation study. With our benchmark suite and data dependency analysis, HPC practitioners now have a reference for identifying checkpointing variables and better knowledge of what kind of variables to checkpoint.

Fu, Xiang↗

A maintenance model for k-out-of-n subsystems aboard a fleet of advanced commercial aircraft

Proposed highly reliable fault-tolerant reconfigurable digital control systems for a future generation of commercial aircraft consist of several k-out-of-n subsystems. Each of these flight-critical subsystems will consist of n identical components, k of which must be functioning properly in order for the aircraft to be dispatched. Failed components are recoverable; they are repaired in a shop. Spares are inventoried at a main base where they may be substituted for failed components on planes during layovers. Penalties are assessed when failure of a k-out-of-n subsystem causes a dispatch cancellation or delay. A maintenance model for a fleet of aircraft with such control systems is presented. The goals are to demonstrate economic feasibility and to optimize.

Miller, D. R.↗

Formal methods for achieving reliable software

Requirements for reliable avionic systems are discussed in terms of the effectiveness of programming methodology. The need for methods to cope with the complexity of critical real-time systems is emphasized. Some general concepts about formal methods are presented and an example is given of the SRI hierarchical development methodology taken from the executive system of the SIFT fault tolerant computer. Formal methods with alternatives are compared and the prospects for introducing formal methods into practice are considered.

Goldberg, J.↗

Control - Demands mushroom as station grows

The NASA space station, which is presently in the planning stage, is to be composed of both rigid and nonrigid modules, rotating elements, and flexible appendages subjected to environmental disturbances from the earth's atmospheric gravity gradient, and magnetic field, as well as solar radiation and self-generated disturbances. Control functions, which will originally include attitude control, docking and berthing control, and system monitoring and management, will with evolving mission objectives come to encompass such control functions as articulation control, autonomous navigation, space traffic control, and large space structure control. Attention is given to the advancements in modular, distributed, and adaptive control methods, as well as system identification and hardware fault tolerance techniques, which will be required.

Szirmay, S. Z.↗

Electronic Power Switch for Fault-Tolerant Networks

Power field-effect transistors reduce energy waste and simplify interconnections. Current switch containing power field-effect transistor (PFET) placed in series with each load in fault-tolerant power-distribution system. If system includes several loads and supplies, switches placed in series with adjacent loads and supplies. System of switches protects against overloads and losses of individual power sources.

Volp, J.↗

Computer Sciences and Data Systems, volume 1

Topics addressed include: software engineering; university grants; institutes; concurrent processing; sparse distributed memory; distributed operating systems; intelligent data management processes; expert system for image analysis; fault tolerant software; and architecture research.

Source record↗

Near-term, 100-kW class ion engines

A design approach for large area, high power ion engines is presented. This approach conceptually divides a single engine into a combination of smaller discharge chambers (or segments) configured to operate as a single large area engine. This segmented ion thruster (SIT) approach is shown to enable the immediate development of 100-kW class argon ion engines for operation at a specific impulse of 10,000 s. A combination of six 30-cm diameter ion chambers operating as a single engine can process over 100 kW. Such a segmented ion engine could be built today and would operate from a single power processor unit. The segmented engine design approach may also enable the development of megawatt class ion engines. Potential benefits of the segmented ion thruster design include: mitigation of the span-to-gap problem central to the development of large area, high power ion engines; reduction in hollow cathode emission current requirements; improved fault tolerance; and reduced vacuum system pumping speed requirements for engine development testing.

Brophy, John R.↗

Mark 4A antenna control system data handling architecture study

A high-level review was conducted to provide an analysis of the existing architecture used to handle data and implement control algorithms for NASA's Deep Space Network (DSN) antennas and to make system-level recommendations for improving this architecture so that the DSN antennas can support the ever-tightening requirements of the next decade and beyond. It was found that the existing system is seriously overloaded, with processor utilization approaching 100 percent. A number of factors contribute to this overloading, including dated hardware, inefficient software, and a message-passing strategy that depends on serial connections between machines. At the same time, the system has shortcomings and idiosyncrasies that require extensive human intervention. A custom operating system kernel and an obscure programming language exacerbate the problems and should be modernized. A new architecture is presented that addresses these and other issues. Key features of the new architecture include a simplified message passing hierarchy that utilizes a high-speed local area network, redesign of particular processing function algorithms, consolidation of functions, and implementation of the architecture in modern hardware and software using mainstream computer languages and operating systems. The system would also allow incremental hardware improvements as better and faster hardware for such systems becomes available, and costs could potentially be low enough that redundancy would be provided economically. Such a system could support DSN requirements for the foreseeable future, though thorough consideration must be given to hard computational requirements, porting existing software functionality to the new system, and issues of fault tolerance and recovery.

Briggs, H. C.↗

Preliminary design features of the RASCAL - A NASA/Army rotorcraft in-flight simulator

Salient design features of a new NASA/Army research rotorcraft - the Rotorcraft Aircrew Systems Concepts Airborne Laboratory (RASCAL) - are described. Using a UH-60A Black Hawk helicopter as a baseline vehicle, the RASCAL will be a flying laboratory capable of supporting the research requirements of major NASA and Army guidance, control, and display research programs. The paper describes the research facility requirements of these programs together with other critical constraints on the design of the research system, including safety-of-flight. Research program schedules demand a phased development approach, wherein specific research capability milestones are met and flight research projects are flown throughout the complete development cycle of the RASCAL. This development approach is summarized, and selected features of the research system are described. The research system includes a full-authority, programmable, fault-tolerant/fail-safe, fly-by-wire flight control system and a real-time obstacle detection and avoidance system which will generate low-latitude guidance commands to the pilot on a wide field-of-view, color helmet-mounted display.

Aiken, Edwin W.↗

Preliminary design features of the RASCAL: A NASA /Army rotorcraft in-flight simulator

Salient design features of a new NASA/Army research rotorcraft - the Rotorcraft-Aircrew Systems Concepts Airborne Laboratory (RASCAL) - are described. Using a UH-60A Black Hawk helicopter as a baseline vehicle, the RASCAL will be a flying laboratory capable of supporting the research requirements of major NASA and Army guidance, control, and display research programs. The paper describes the research facility requirements of these programs together with other critical constraints on the design of the research system, including safety-of-flight. Research program schedules demand a phased development approach, wherein specific research capability milestones are met and flight research projects are flown throughout the complete development cycle of the RASCAL. This development approach is summarized, and selected features of the research system are described. The research system includes a full-authority, programmable, fault-tolerant/fail-safe, fly-by-wire flight control system and a real-time obstacle detection and avoidance system which will generate low-altitude guidance commands to the pilot on a wide field-of-view, color helmet-mounted display.

Aiken, Edwin W.↗

Fault handling schemes in electronic systems with specific application to radiation tolerance and VLSI design

Naturally occurring space radiation particles can produce transient and permanent changes in the electrical properties of electronic devices and systems. In this work, the transient radiation effects on DRAM and CMOS SRAM were considered. In addition, the effect of total ionizing dose radiation of the switching times of CMOS logic gates were investigated. Effects of transient radiation on the column and cell of MOS dynamic memory cell was simulated using SPICE. It was found that the critical charge of the bitline was higher than that of the cell. In addition, the critical charge of the combined cell-bitline was found to be dependent on the gate voltage of the access transistor. In addition, the effect of total ionizing dose radiation on the switching times of CMOS logic gate was obtained. The results of this work indicate that, the rise time of CMOS logic gates increases, while the fall time decreases with an increase in total ionizing dose radiation. Also, by increasing the size of the P-channel transistor with respect to that of the N-channel transistor, the propagation delay of CMOS logic gate can be made to decrease with, or be independent of an increase in total ionizing dose radiation. Furthermore, a method was developed for replacing polysilicon feedback resistance of SRAMs with a switched capacitor network. A switched capacitor SRAM was implemented using MOS Technology. The critical change of the switched capacitor SRAM has a very large critical charge. The results of this work indicate that switched capacitor SRAM is a viable alternative to SRAM with polysilicon feedback resistance.

Attia, John Okyere↗

Catastrophic Fault Recovery with Self-Reconfigurable Chips

Mission critical systems typically employ multi-string redundancy to cope with possible hardware failure. Such systems are only as fault tolerant as there are many redundant strings. Once a particular critical component exhausts its redundant spares, the multi-string architecture cannot tolerate any further hardware failure. This paper aims at addressing such catastrophic faults through the use of 'Self-Reconfigurable Chips' as a last resort effort to 'repair' a faulty critical component.

fault tolerance↗

Method and apparatus for fault tolerance

A method and apparatus for achieving fault tolerance in a computer system having at least a first central processing unit and a second central processing unit. The method comprises the steps of first executing a first algorithm in the first central processing unit on input which produces a first output as well as a certification trail. Next, executing a second algorithm in the second central processing unit on the input and on at least a portion of the certification trail which produces a second output. The second algorithm has a faster execution time than the first algorithm for a given input. Then, comparing the first and second outputs such that an error result is produced if the first and second outputs are not the same. The step of executing a first algorithm and the step of executing a second algorithm preferably takes place over essentially the same time period.

Masson, Gerald M.↗

Relaxing USOS Solar Array Constraints for Russian Vehicle Undocking

With the retirement of Space Shuttle cargo delivery capability and the ten year life extension of the International Space Station (ISS) more emphasis is being put on preservation of the service life of ISS critical components. Current restrictions on the United States Orbital Segment (USOS) Solar Array (SA) positioning during Russian Vehicle (RV) departure from ISS nadir and zenith ports cause SA to be positioned in the plume field of Service Module thrusters and lead to degradation of SAs as well as potential damage to Sun tracking Beta Gimbal Assemblies (BGA). These restrictions are imposed because of the single fault tolerant RV Motion Control System (MCS), which does not meet ISS Safety requirements for catastrophic hazards and dictates 16 degree Solar Array Rotary Joint position, which ensures that ISS and RV relative motion post separation, does lead to collision. The purpose of this paper is to describe a methodology and the analysis that was performed to determine relative motion trajectories of the ISS and separating RV for nominal and contingency cases. Analysis was performed in three phases that included ISS free drift prior to Visiting Vehicle separation, ISS and Visiting Vehicle relative motion analysis and clearance analysis. First, the ISS free drift analysis determined the worst case attitude and attitude rate excursions prior to RV separation based on a series of different configurations and mass properties. Next, the relative motion analysis calculated the separation trajectories while varying the initial conditions, such as docking mechanism performance, Visiting Vehicle MCS failure, departure port location, ISS attitude and attitude rates at the time of separation, etc. The analysis employed both orbital mechanics and rigid body rotation calculations while accounting for various atmospheric conditions and gravity gradient effects. The resulting relative motion trajectories were then used to determine the worst case separation envelopes during the clearance analysis. Analytical models were developed individually for each stage and the results were used to build initial conditions for the following stages. In addition to the analysis approach, this paper also discusses the analysis results, showing worst case relative motion envelopes, the recommendations for ISS appendage positioning and the suggested approach for future analyses.

Menkin, Evgeny↗

Autonomous Dynamically Self-Organizing and Self-Healing Distributed Hardware Architecture - the eDNA Concept

This paper presents the current state of the autonomous dynamically self-organizing and self-healing electronic DNA (eDNA) hardware architecture (patent pending). In its current prototype state, the eDNA architecture is capable of responding to multiple injected faults by autonomously reconfiguring itself to accommodate the fault and keep the application running. This paper will also disclose advanced features currently available in the simulation model only. These features are future work and will soon be implemented in hardware. Finally we will describe step-by-step how an application is implemented on the eDNA architecture.

self-healing hardware↗