Search NASA⌕ Search

SEARCH · Search NASA

Results for “Redundant Designs”

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 199 records · Page 11

Numerical model of solar dynamic radiator for parametric analysis

Growth power requirements for Space Station Freedom will be met through addition of 25 kW solar dynamic (SD) power modules. The SD module rejects waste heat from the power conversion cycle to space through a pumped-loop, multi-panel, deployable radiator. The baseline radiator configuration was defined during the Space Station conceptual design phase and is a function of the state point and heat rejection requirements of the power conversion unit. Requirements determined by the overall station design such as mass, system redundancy, micrometeoroid and space debris impact survivability, launch packaging, costs, and thermal and structural interaction with other station components have also been design drivers for the radiator configuration. Extensive thermal and power cycle modeling capabilities have been developed which are powerful tools in Station design and analysis, but which prove cumbersome and costly for simple component preliminary design studies. In order to aid in refining the SD radiator to the mature design stage, a simple and flexible numerical model was developed. The model simulates heat transfer and fluid flow performance of the radiator and calculates area mass and impact survivability for many combinations of flow tube and panel configurations, fluid and material properties, and environmental and cycle variations. A brief description and discussion of the numerical model, it's capabilities and limitations, and results of the parametric studies performed is presented.

Rhatigan, Jennifer L.↗

Magnetic Actuators and Suspension for Space Vibration Control

The research on microgravity vibration isolation performed at the University of Virginia is summarized. This research on microgravity vibration isolation was focused in three areas: (1) the development of new actuators for use in microgravity isolation; (2) the design of controllers for multiple-degree-of-freedom active isolation; and (3) the construction of a single-degree-of-freedom test rig with umbilicals. Described are the design and testing of a large stroke linear actuator; the conceptual design and analysis of a redundant coarse-fine six-degree-of-freedom actuator; an investigation of the control issues of active microgravity isolation; a methodology for the design of multiple-degree-of-freedom isolation control systems using modern control theory; and the design and testing of a single-degree-of-freedom test rig with umbilicals.

Knospe, Carl R.↗

Control of large flexible space structures

Progress in robust design of generalized parity relations, design of failure sensitive observers using the geometric system theory of Wonham, computational techniques for evaluation of the performance of control systems with fault tolerance and redundancy management features, and the design and evaluation od control systems for structures having nonlinear joints are described.

Vandervelde, W. E.↗

Risk Assessment and Control through Countermeasure System Iplementation for Long-term Crew Exposure to Microgravity

Experience with the International Space Station (ISS) program demonstrates the degree to which engineering design and operational solutions must protect crewmembers from health risks due to long-term exposure to the microgravity environment. Risks to safety and health due to degradation in the microgravity environment include crew inability to complete emergency or nominal activities, increased risk of injury, and inability to complete safe return to the ground due to reduced strength or embrittled bones. These risks without controls slowly increase in probability for the length of the mission and become more significant for increasing mission durations. Countermeasures to microgravity include hardware systems that place a crewmember s body under elevated stress to produce an effect similar to daily exposure to gravity. The ISS countermeasure system is predominately composed of customized exercise machines. Historical treatment of microgravity countermeasure systems as medical research experiments unintentionally reduced the foreseen importance and therefore the capability of the systems to function in a long-term operational role. Long-term hazardous effects and steadily increasing operational risks due to non-functional countermeasure equipment require a more rigorous design approach and incorporation of redundancy into seemingly non- mission-critical hardware systems. Variations in the rate of health degradation and responsiveness to countermeasures among the crew population drastically increase the challenge for design requirements development and verification of the appropriate risk control strategy. The long-term nature of the hazards and severe limits on logistical re-supply mass, volume and frequency complicates assessment of hardware availability and verification of an adequate maintenance and sparing plan. Design achievement of medically defined performance requirements by microgravity countermeasure systems and incorporation of adequate failure tolerance significantly reduces these risks. Future implementation of on-site monitoring hardware for critical health parameters such as bone mineral density would allow greater responsiveness, efficiency, and optimized design of the countermeasures system.

Gernand, Jeremy M.↗

Prevention of design flaws in multicomputer systems

Multicomputer configurations and redundancy management techniques used in various airborne systems were investigated to determine methods to prevent and/or treat generic design flaws. The findings are intended for use in the design of a computer system for use in the space shuttle orbiter.

Source record↗

Common Cause Failures Dominate and Defeat Redundancy

Common cause failures occur when several malfunctions are produced by a single event or process. They are especially damaging when they eliminate an entire set of redundant systems and disable their intended function. Redundancy is used when the individual system failure probability is unacceptably high. Redundancy can improve the overall system failure probability if the failures are independent, but the reliability gain is limited if there are dependent failures having a common cause. No amount of redundancy can reduce the total failure probability below the common cause failure probability. Common cause failures defeat redundancy. Systems with high reliability requirements often use extensive redundancy. These highly redundant systems rarely fail unless all the redundant components providing a particular function fail. Complete failures of such highly redundant systems are then usually common cause failures. Common cause failures are prevalent in highly redundant, high reliability systems. Common cause failures dominate redundancy. Redundant systems may fail due to specification, design, manufacturing, operations, or maintenance problems that disable all the identical redundant systems. Common cause failures typically account for one tenth of all failures. If the failure probability is relatively low and common cause failures are significant, adding more than two or three redundant identical units usually gives little added reliability improvement. Common cause failures can be reduced by using diverse components with different technologies and manufacturers, by separating and shielding subsystems, and by avoiding shared control, power, or location. External events and shared vulnerabilities may still cause common cause failures.

common cause failures↗

Common Cause Failures Dominate and Defeat Redundancy

Common cause failures occur when several malfunctions are produced by a single event or process. They are especially damaging when they eliminate an entire set of redundant systems and disable their intended function. Redundancy is used when the individual system failure probability is unacceptably high. Redundancy can improve the overall system failure probability if the failures are independent, but the reliability gain is limited if there are dependent failures having a common cause. No amount of redundancy can reduce the total failure probability below the common cause failure probability. Common cause failures defeat redundancy. Systems with high reliability requirements often use extensive redundancy. These highly redundant systems rarely fail unless all the redundant components providing a particular function fail. Complete failures of such highly redundant systems are then usually common cause failures. Common cause failures are prevalent in highly redundant, high reliability systems. Common cause failures dominate redundancy. Redundant systems may fail due to specification, design, manufacturing, operations, or maintenance problems that disable all the identical redundant systems. Common cause failures typically account for one tenth of all failures. If the failure probability is relatively low and common cause failures are significant, adding more than two or three redundant identical units usually gives little added reliability improvement. Common cause failures can be reduced by using diverse components with different technologies and manufacturers, by separating and shielding subsystems, and by avoiding shared control, power, or location. External events and shared vulnerabilities may still cause common cause failures.

common cause failures↗

Making Human Spaceflight Practical and Affordable: Spacecraft Designs and their Degree of Operability

As we push toward new and diverse space transportation capabilities, reduction in operations cost becomes increasingly important. Achieving affordable and safe human spaceflight capabilities will be the mark of success for new programs and new providers. The ability to perceive the operational implications of design decisions is crucial in developing safe yet cost competitive space transportation systems. Any human spaceflight program - government or commercial - must make countless decisions either to implement spacecraft system capabilities or adopt operational constraints or workarounds to account for the lack of such spacecraft capabilities. These decisions can benefit from the collective experience that NASA has accumulated in building and operating crewed spacecraft over the last five decades. This paper reviews NASA s history in developing and operating human rated spacecraft, reviewing the key aspects of spacecraft design and their resultant impacts on operations phase complexity and cost. Specific examples from current and past programs - including the Space Shuttle and International Space Station - are provided to illustrate design traits that either increase or increase cost and complexity associated with spacecraft operations. These examples address factors such as overall design performance margins, levels of redundancy, degree of automated failure response, type and quantity of command and telemetry interfaces, and the definition of reference scenarios for analysis and test. Each example - from early program requirements, design implementation and resulting real-time operations experience - to tell the end-to-end "story" Based on these experiences, specific techniques are recommended to enable earlier and more effective assessment of operations concerns during the design process. A formal method for the assessment of spacecraft operability is defined and results of such operability assessments for recent spacecraft designs are provided. Recent experience in applying these techniques to Orion spacecraft development is reviewed to highlight the direct benefits of early operational assessment and collaborative development efforts.

Crocker, Alan R.↗

Essential SpaceWire Hardware Capabilities for a Robust Network

The Geostationary Operational Environmental Satellite R-Series Program (GOES-R) mission is a joint program between National Oceanic & Atmospheric Administration (NOAA) and National Aeronautics & Space Administration (NASA) Goddard Space Flight Center (GSFC). GOES-R project selected SpaceWire as the best solution to satisfy the desire for simple and flexible instrument to spacecraft command and telemetry communications. GOES-R development and integration is complete and the observatory is scheduled for launch October 2016. The spacecraft design was required to support redundant SpaceWire links for each instrument side, as well as to route the fewest number of connections through a Slip Ring Assembly necessary to support Solar pointing instruments. The final design utilized two different router designs. The SpaceWire standard alone does not ensure the most practical or reliable network. On GOES-R a few key hardware capabilities were identified that merit serious consideration for future designs. Primarily these capabilities address persistent port stalls and the prevention of receive buffer overflows. Workarounds were necessary to overcome shortcomings that could be avoided in future designs if they utilize the capabilities, discussed in this paper, above and beyond the requirements of the SpaceWire standard.

SpaceWire↗

Summary report: A preliminary investigation into the use of fuzzy logic for the control of redundant manipulators

The Rice University Department of Mechanical Engineering and Materials Sciences' Robotics Group designed and built an eight degree of freedom redundant manipulator. Fuzzy logic was proposed as a control scheme for tasks not directly controlled by a human operator. In preliminary work, fuzzy logic control was implemented for a camera tracking system and a six degree of freedom manipulator. Both preliminary systems use real time vision data as input to fuzzy controllers. Related projects include integration of tactile sensing and fuzzy control of a redundant snake-like arm that is under construction.

Cheatham, John B., Jr.↗

Joint-space Lyapunov-based direct adaptive control of a kinematically redundant telerobot manipulator

This paper presents the design of a joint-space adaptive control scheme for controlling the slave arm motion of a dual-arm telerobot system developed at Goddard Space Flight Center (GSFC) to study telerobotic operations in space. Each slave arm of the dual-arm system is a kinematically redundant manipulator with seven degrees of freedom (DOF). Using the concept of model reference adaptive control (MRAC) and Liupunov direct method, we derive an adaptation algorithm that adjusts the PD controller gains of the control scheme. The development of the adaptive control scheme assumes that the slave arm motion is non-compliant and slowly varying. The implementation of the derived control scheme does not require the computation of manipulator dynamics which makes the control scheme sufficiently fast for real-time applications. Computer simulation study performed for the 7-DOF slave arm shows that the developed control scheme can efficiently adapt to sudden change in payload while tracking various test trajectories such as ramp or sinusoids with negligible position errors.

Nguyen, Charles C.↗

Robustness

The concept of rubustness includes design simplicity, component and path redundancy, desensitization to the parameter and environment variations, control of parameter variations, and punctual operations. These characteristics must be traded with functional concepts, materials, and fabrication approach against the criteria of performance, cost, and reliability. The paper describes the robustness design process, which includes the following seven major coherent steps: translation of vision into requirements, definition of the robustness characteristics desired, criteria formulation of required robustness, concept selection, detail design, manufacturing and verification, operations.

Ryan, Robert↗

Program Helps In Analysis Of Failures

Failure Environment Analysis Tool (FEAT) computer program developed to enable people to see and better understand effects of failures in system. User selects failures from either engineering schematic diagrams or digraph-model graphics, and effects or potential causes of failures highlighted in color on same schematic-diagram or digraph representation. Uses digraph models to answer two questions: What will happen to system if set of failure events occurs? and What are possible causes of set of selected failures? Helps design reviewers understand exactly what redundancies built into system and where there is need to protect weak parts of system or remove them by redesign. Program also useful in operations, where it helps identify causes of failure after they occur. FEAT reduces costs of evaluation of designs, training, and learning how failures propagate through system. Written using Macintosh Programmers Workshop C v3.1. Can be linked with CLIPS 5.0 (MSC-21927, available from COSMIC).

Stevenson, R. W.↗

Operations analysis (study 2.1). Payload designs for space servicing, addendum

Space replaceable units and payload configurations are revised to reflect increased levels of redundancy to be more consistent with current design practices. A reassessment of expendable payload design reliabilities was performed to provide a common basis for comparison with space serviceable configurations.

Wolfe, R. R.↗

Shooting the Moon

This story is about an unlikely NASA mission to the Moon. It was unlikely because it was started with far too little time and too-little money to complete. It was unlikely because it was able to take chances to accept risk of failure. It was unlikely because it was searching for the unthinkable: water-ice on the moon... Figure 1-1: LCROSS Mission. The mission of the Lunar CRater Observation and Sensing Satellite (LCROSS) was to investigate the possibility of water ice in craters on the Moon s poles. This is certainly an interesting scientific topic in itself, but I intend to focus on the compelling experience of managing the LCROSS Project in the context of this storied Agency. Perhaps most interesting are the implications this story has for managing any development effort, lunar or not, and working a balance to achieve success. NASA is by design a risk-taking agency within the US Government. It could be argued that NASA s purpose in the aerospace community is to take on the really big challenges that either the corporate world can t afford, are not yet profitable endeavors, or are just too risky for private corporations to entertain. However, expectations of the Agency have evolved. A combination of grim human tragedies and some very public cost and schedule overruns have challenged the public s and Congress s tolerance for risk-taking within the Agency. NASA, which is supposed to be in the business of taking risks to do bold, difficult things, has become less and less able to do so within its cost framework. Yet effectively replacing prudent risk management with attempts to "risk-eliminate" is completely unaffordable. So where does risk-taking fit within the Agency, or within private/corporate organizations for that matter? Where astronauts play there is clearly concern about risk. When an organization puts humans in harm s way, it is understandably going to take extra effort to assure nobody gets hurt. Doing so, of course, costs money - a lot of money to pay for labor and hardware which is attempting to assure nothing will go wrong. Sophisticated designs, with doubly- or triply-redundant systems, extensive testing to verify those systems, and numerous engineering test units built to learn and evolve a hardware design, all drive the cost and time required to implement. Human spaceflight is an expensive business because of the exceptional system complexity and levels of assurance required for human space travel. What about missions that do not involve human spaceflight? What about missions whose potential failure will not take a human life, whose costs are small and whose urgency and importance are limited by design? A portfolio consisting of this type of mission can be designed to be risk tolerant, not requiring large expenditures to guarantee against failure. With the money saved, the number of missions that can be executed within the portfolio grows, or the total cost of the portfolio can be reduced. The NASA LCROSS mission is a pathfinder example of a low-cost, quick turn-around mission which struck a balance on mission risk, while accomplishing big objectives, like defining how we understand the Moon.

Andrews, Daniel R.↗

Refined Gearbox Design for the Chariot Lunar Rover

In planning for NASA's return to the moon by the year 2020, the NASA Johnson Space Center (JSC) designed and built a lunar concept vehicle called Chariot. Slightly larger than a pickup truck, it was designed to demonstrate similar utilitarian functions, but with twelve wheels for redundancy, reliability, and reduced surface contact pressure. JSC designed a motor gearbox to drive each of Chariot s six wheel pods. The pods can be independently steered over 360 for maneuverability. This paper describes the design of a second generation, drop-in replacement gearbox. The new design has a lower parts count, and is lighter than the original, which represents a step toward flight hardware.

Bauman, Steve↗