Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “tolerance”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

Statistical Tolerance and Clearance Analysis for Assembly

Tolerance is inevitable because manufacturing exactly equal parts is known to be impossible. Furthermore, the specification of tolerances is an integral part of product design since tolerances directly affect the assemblability, functionality, manufacturability, and cost effectiveness of a product. In this paper, we present statistical tolerance and clearance analysis for the assembly. Our proposed work is expected to make the following contributions: (i) to help the designers to evaluate products for assemblability, (ii) to provide a new perspective to tolerance problems, and (iii) to provide a tolerance analysis tool which can be incorporated into a CAD or solid modeling system.

statistical tolerance clearance analysis Monte-Car↗
NASA NTRS1972

+Gz tolerance after 14 days bed rest and the effects of rehydration.

Measurement of the reduction in centrifugation tolerance after two weeks of bedrest with moderate daily exercise, with an attempt to determine if rehydration improves +Gz tolerance. There were significant reductions in +Gz tolerance during bedrest periods at three acceleration levels. Rehydration resulted in a significant increase in tolerance at 2.1G but it did not restore tolerance to control levels. Rehydration did not affect tolerance at 3.2G and 3.8G.

Greenleaf, J. E.↗
NASA NTRS1985

Systems approach to software fault tolerance

Computing systems are employed for aerospace applications with high reliability requirements. In order to provide the needed reliability, it was necessary to make use of computing systems with fault-tolerance characteristics. Traditionally, fault tolerance is achieved through the use of hardware redundance. However, fault-tolerant techniques based on suitable software design considerations have also been developed. The present paper is concerned with the major issues arising in the context of an application of fault-tolerant software techniques to dynamic systems. Attention is given to fault-tolerant flight software, software component stability, system stability with fault-tolerant software, the preservation of functional performance, N-version vs. recovery blocks in flight software, systems-based software, static and dynamic models, static and dynamic consistency tests, and recovery block initialization.

Caglayan, A. K.↗
NASA NTRS1991

Intelligent failure-tolerant control

An overview of failure-tolerant control is presented, beginning with robust control, progressing through parallel and analytical redundancy, and ending with rule-based systems and artificial neural networks. By design or implementation, failure-tolerant control systems are 'intelligent' systems. All failure-tolerant systems require some degrees of robustness to protect against catastrophic failure; failure tolerance often can be improved by adaptivity in decision-making and control, as well as by redundancy in measurement and actuation. Reliability, maintainability, and survivability can be enhanced by failure tolerance, although each objective poses different goals for control system design. Artificial intelligence concepts are helpful for integrating and codifying failure-tolerant control systems, not as alternatives but as adjuncts to conventional design methods.

Stengel, Robert F.↗
NASA NTRS1993

A fault-tolerant intelligent robotic control system

This paper describes the concept, design, and features of a fault-tolerant intelligent robotic control system being developed for space and commercial applications that require high dependability. The comprehensive strategy integrates system level hardware/software fault tolerance with task level handling of uncertainties and unexpected events for robotic control. The underlying architecture for system level fault tolerance is the distributed recovery block which protects against application software, system software, hardware, and network failures. Task level fault tolerance provisions are implemented in a knowledge-based system which utilizes advanced automation techniques such as rule-based and model-based reasoning to monitor, diagnose, and recover from unexpected events. The two level design provides tolerance of two or more faults occurring serially at any level of command, control, sensing, or actuation. The potential benefits of such a fault tolerant robotic control system include: (1) a minimized potential for damage to humans, the work site, and the robot itself; (2) continuous operation with a minimum of uncommanded motion in the presence of failures; and (3) more reliable autonomous operation providing increased efficiency in the execution of robotic tasks and decreased demand on human operators for controlling and monitoring the robotic servicing routines.

Marzwell, Neville I.↗
NASA NTRS1993

Avoiding and tolerating latency in large-scale next-generation shared-memory multiprocessors

A scalable solution to the memory-latency problem is necessary to prevent the large latencies of synchronization and memory operations inherent in large-scale shared-memory multiprocessors from reducing high performance. We distinguish latency avoidance and latency tolerance. Latency is avoided when data is brought to nearby locales for future reference. Latency is tolerated when references are overlapped with other computation. Latency-avoiding locales include: processor registers, data caches used temporally, and nearby memory modules. Tolerating communication latency requires parallelism, allowing the overlap of communication and computation. Latency-tolerating techniques include: vector pipelining, data caches used spatially, prefetching in various forms, and multithreading in various forms. Relaxing the consistency model permits increased use of avoidance and tolerance techniques. Each model is a mapping from the program text to sets of partial orders on program operations; it is a convention about which temporal precedences among program operations are necessary. Information about temporal locality and parallelism constrains the use of avoidance and tolerance techniques. Suitable architectural primitives and compiler technology are required to exploit the increased freedom to reorder and overlap operations in relaxed models.

Probst, David K.↗
NASA NTRS1993

A minimum cost tolerance allocation method for rocket engines and robust rocket engine design

Rocket engine design follows three phases: systems design, parameter design, and tolerance design. Systems design and parameter design are most effectively conducted in a concurrent engineering (CE) environment that utilize methods such as Quality Function Deployment and Taguchi methods. However, tolerance allocation remains an art driven by experience, handbooks, and rules of thumb. It was desirable to develop and optimization approach to tolerancing. The case study engine was the STME gas generator cycle. The design of the major components had been completed and the functional relationship between the component tolerances and system performance had been computed using the Generic Power Balance model. The system performance nominals (thrust, MR, and Isp) and tolerances were already specified, as were an initial set of component tolerances. However, the question was whether there existed an optimal combination of tolerances that would result in the minimum cost without any degradation in system performance.

Gerth, Richard J.↗
NASA NTRS1994

Dynamic Leg Exercise Improves Tolerance to Lower Body Negative Pressure

These results clearly demonstrate that dynamic leg exercise against the footward force produced by LBNP substantially improves tolerance to LBNP, and that even cyclic ankle flexion without load bearing also increases tolerance. This exercise-induced increase of tolerance was actually an underestimate, because subjects who completed the tolerance test while exercising could have continued for longer periods. Exercise probably increases LBNP tolerance by multiple mechanisms. Tolerance was increased in part by skeletal muscle pumping venous blood from the legs. Rosenhamer and Linnarsson and Rosenhamer also deduced this for subjects cycling during centrifugation, although no measurements of leg volume were made in those studies: they found that male subjects cycling at 98 W could endure 3 Gz centrifugation longer than when they remained relaxed during centrifugation. Skeletal muscle pumping helps maintain cardiac filling pressure by opposing gravity-, centrifugation-, or LBNP-induced accumulation of blood and extravascular fluid in the legs.

Watenpaugh, D. E.↗
NASA NTRS1999

The Design of a Fault-Tolerant COTS-Based Bus Architecture

In this paper, we report our experiences and findings on the design of a fault-tolerant bus architecture comprised of two COTS buses, the IEEE 1394 and the 12C. This fault-tolerant bus is the backbone system bus for the avionics architecture of the X2000 program at the Jet Propulsion Laboratory. COTS buses are attractive because of the availability of low cost commercial products. However, they are not specifically designed for highly reliable applications such as long-life deep-space missions. The X2000 design team has devised a multi-level fault tolerance approach to compensate for this shortcoming of COTS buses. First, the approach enhances the fault tolerance capabilities of the IEEE 1394 and 12 C buses by adding a layer of fault handling hardware and software. Second, algorithms are developed to enable the IEEE 1394 and the 12 C buses assist each other to isolate and recovery from faults. Third, the set of IEEE 1394 and 12 C buses is duplicated to further enhance system reliability. The X2000 design team has paid special attention to guarantee that all fault tolerance provisions will not cause the bus design to deviate from the commercial standard specifications. Otherwise, the economic attractiveness of using COTS will be diminished. The hardware and software design of the X2000 fault-tolerant bus are being implemented and flight hardware will be delivered to the ST4 and Europa Orbiter missions.

Chau, Savio N.↗
NASA NTRS2005

Fault-Tolerant Heat Exchanger

A compact, lightweight heat exchanger has been designed to be fault-tolerant in the sense that a single-point leak would not cause mixing of heat-transfer fluids. This particular heat exchanger is intended to be part of the temperature-regulation system for habitable modules of the International Space Station and to function with water and ammonia as the heat-transfer fluids. The basic fault-tolerant design is adaptable to other heat-transfer fluids and heat exchangers for applications in which mixing of heat-transfer fluids would pose toxic, explosive, or other hazards: Examples could include fuel/air heat exchangers for thermal management on aircraft, process heat exchangers in the cryogenic industry, and heat exchangers used in chemical processing. The reason this heat exchanger can tolerate a single-point leak is that the heat-transfer fluids are everywhere separated by a vented volume and at least two seals. The combination of fault tolerance, compactness, and light weight is implemented in a unique heat-exchanger core configuration: Each fluid passage is entirely surrounded by a vented region bridged by solid structures through which heat is conducted between the fluids. Precise, proprietary fabrication techniques make it possible to manufacture the vented regions and heat-conducting structures with very small dimensions to obtain a very large coefficient of heat transfer between the two fluids. A large heat-transfer coefficient favors compact design by making it possible to use a relatively small core for a given heat-transfer rate. Calculations and experiments have shown that in most respects, the fault-tolerant heat exchanger can be expected to equal or exceed the performance of the non-fault-tolerant heat exchanger that it is intended to supplant (see table). The only significant disadvantages are a slight weight penalty and a small decrease in the mass-specific heat transfer.

Izenson, Michael G.↗
NASA NTRS2012

Fault Tolerance Middleware for a Multi-Core System

Fault Tolerance Middleware (FTM) provides a framework to run on a dedicated core of a multi-core system and handles detection of single-event upsets (SEUs), and the responses to those SEUs, occurring in an application running on multiple cores of the processor. This software was written expressly for a multi-core system and can support different kinds of fault strategies, such as introspection, algorithm-based fault tolerance (ABFT), and triple modular redundancy (TMR). It focuses on providing fault tolerance for the application code, and represents the first step in a plan to eventually include fault tolerance in message passing and the FTM itself. In the multi-core system, the FTM resides on a single, dedicated core, separate from the cores used by the application. This is done in order to isolate the FTM from application faults and to allow it to swap out any application core for a substitute. The structure of the FTM consists of an interface to a fault tolerant strategy module, a responder module, a fault manager module, an error factory, and an error mapper that determines the severity of the error. In the present reference implementation, the only fault tolerant strategy implemented is introspection. The introspection code waits for an application node to send an error notification to it. It then uses the error factory to create an error object, and at this time, a severity level is assigned to the error. The introspection code uses its built-in knowledge base to generate a recommended response to the error. Responses might include ignoring the error, logging it, rolling back the application to a previously saved checkpoint, swapping in a new node to replace a bad one, or restarting the application. The original error and recommended response are passed to the top-level fault manager module, which invokes the response. The responder module also notifies the introspection module of the generated response. This provides additional information to the introspection module that it can use in generating its next response. For example, if the responder triggers an application rollback and errors are still occurring, the introspection module may decide to recommend an application restart.

Some, Raphael R.↗
NASA NTRS2014

Mechanisms of Orthostatic Tolerance Improvement Following Artificial Gravity Exposure Differ Between Men and Women

We recently determined that a short exposure to artificial gravity (AG) improved the orthostatic tolerance limit (OTL) of cardiovascularly deconditioned subjects. We now seek to determine the mechanisms of that improvement in these hypovolemic men and women. Methods. We determined the orthostatic tolerance limit (OTL) of 9 men and 8 women following a 90 min exposure to AG compared to 90 min of head down bed rest (HDBR). In both cases (21 days apart), subjects were made hypovolemic (low salt diet plus 20 mg intravenous furosemide). Orthostatic tolerance was determined from a combination of head up tilt and increasing lower body negative pressure until presyncope. Mean values and correlations with OTL were determined for heart rate, blood pressure, stroke volume, cardiac output and peripheral resistance (Finometer), cerebral artery blood velocity (DWL), partial pressure of carbon dioxide (Novametrics) and body segmental impedance (UFI THRIM) were measured during supine baseline, during OTL to presyncope and during supine recovery Results. Orthostatic tolerance of these hypovolemic subjects was significantly greater on the day of AG exposure than on the HDBR day. Regression of OTL on these variables identified significant relationships on the HDBR day that were not evident on the AG day: resting TPR correlated positively while resting cerebral flow correlated negatively with OTL. On both days, women's resting stroke volume correlated positively with orthostatic tolerance. Higher group mean values of stroke volume and cerebral artery flow and lower values of blood pressure, peripheral vascular and cerebrovascular resistance both at control and during OTL testing were observed on the AG day. Even though regression of OTL on resting stroke volume was significant only in women, presyncopal stroke volume reached the same level on each day of study for both men and women while the OTL test lasted 30% longer in men and 22% longer in women. Cerebral artery flow appeared to follow stroke volume and absolute values of cerebral flow did not correlate with the development of presyncope. Women responded to AG exposure with elevated cerebral flow at resting control and throughout the OTL test, implying a loss of autoregulation in deconditioned (hypovolemic) women following AG exposure. Conclusions. Before countermeasures to space flight cardiovascular deconditioning are established, gender differences in cardiovascular responses to orthostatic stress, in general, and to orthostatic stress following exposure to artificial gravity, in particular, need to be determined. Since, in both men and women, a single, acute bout of AG exposure improved orthostatic tolerance, the feasibility of short exposures to AG during longer spaceflights or prior to entry into a gravity (Earth or Mars) environment, should be explored. Given the known beneficial effects of AG on other organ systems, the present study indicates that the positive effects of AG on cardiac stroke volume make AG a likely candidate for maintaining cardiovascular conditioning.

Evans, J. M.↗
NASA NTRSDate not supplied

Best Practices, Lessons Learned, and Examples on the Application of Damage Tolerance in Space Structures

Damage tolerance is an important consideration in space structures applications. The intent of damage tolerance is to demonstrate that the structure is robust to the presence of flaws over the service life of the space vehicle. Damage tolerance requirements in documents such as those in NASA, AIAA, and ISO can be challenging to implement. The intent of this paper is three-fold: (1) Provide best practices in the application of damage tolerance requirements for space applications, (2) Provide lessons learned for each of class of hardware, (3) Provide examples of challenging situations encountered in the application of damage tolerance. Examples cover additive manufacturing, composite overwrapped pressure vessels, pressurized structures, liquid rocket engines, thermal protection systems, and other classes of hardware. The philosophy and limitations of leak before burst and proof test logic are also discussed. Finally, a discussion on elastic-plastic fracture mechanics with comparisons to test data will be presented.

Best Practices↗
NASA NTRS1972

Sequential behavior and its inherent tolerance to memory faults.

Representation of a memory fault of a sequential machine M by a function mu on the states of M and the result of the fault by an appropriately determined machine M(mu). Given some sequential behavior B, its inherent tolerance to memory faults can then be measured in terms of the minimum memory redundancy required to realize B with a state-assigned machine having fault tolerance type tau and fault tolerance level t. A behavior having maximum inherent tolerance is exhibited, and it is shown that behaviors of the same size can have different inherent tolerance.

Meyer, J. F.↗
NASA NTRS1975

+Gz tolerance in man after 14-day bedrest periods with isometric and isotonic exercise conditioning

The effects of isometric and isotonic exercise training on post-bedrest +Gz tolerance were determined. In general, 14-day bedrest resulted in a significant loss of Gz tolerance, as previously discovered. At 2.1 Gz, neither the isometric nor the isotonic exercises regimens resulted in a significant increase in post-bedrest Gz tolerance. However, following isometric exercise, restoration of about half the tolerance decrement occurred at 3.2 Gz and 3.8 Gz. Possible reasons for this partial restoration of tolerance are put forward.

Greenleaf, J. E.↗
NASA NTRS1975

System applications of the fault tolerant memory

Conventional memory technologies currently employed in aerospace applications contribute at least fifty percent to system unreliability (where the system includes CPU, I/O and memory). A fault tolerant memory performs both error correction and memory replacement at the bit plane level. To determine the effects of system design of using a fault tolerant memory in space applications, analysis was performed to determine tradeable hardware configurations that meet the reliability goals of each program. The candidate configurations, which included redundant elements of the computer system with both conventional and fault tolerant memories, were then traded in terms of selection criteria of cost, weight, volume, and power. These trade studies demonstrated that a fault tolerant memory provided significant advantages in terms of cost, weight, and volume. The memory selected for this analysis was a recently developed five fault tolerant memory.

Murphy, L. J.↗
NASA NTRS1978

Fault-tolerance - The survival attribute of digital systems

Fault-tolerance is the architectural attribute of a digital system that keeps the logic machine doing its specified tasks when its host, the physical system, suffers various kinds of failures of its components. A more general concept of fault-tolerance also includes human mistakes committed during software and hardware implementation and during man/machine interaction among the causes of faults that are to be tolerated by the logic machine. This paper discusses the concept of fault-tolerance, the reasons for its inclusion in digital system architecture, and the methods of its implementation. A chronological view of the evolution of fault-tolerant systems and an outline of some goals for its further development conclude the presentation.

Avizienis, A.↗
NASA NTRS1978

SIFT - Design and analysis of a fault-tolerant computer for aircraft control

SIFT (Software Implemented Fault Tolerance) is an ultrareliable computer for critical aircraft control applications that achieves fault tolerance by the replication of tasks among processing units. The main processing units are off-the-shelf minicomputers, with standard microcomputers serving as the interface to the I/O system. Fault isolation is achieved by using a specially designed redundant bus system to interconnect the processing units. Error detection and analysis and system reconfiguration are performed by software. Iterative tasks are redundantly executed, and the results of each iteration are voted upon before being used. Thus, any single failure in a processing unit or bus can be tolerated with triplication of tasks, and subsequent failures can be tolerated after reconfiguration. Independent execution by separate processors means that the processors need only be loosely synchronized, and a novel fault-tolerant synchronization method is described.

Wensley, J. H.↗