Results for “power system events” — Page 13

NASA NTRS1977

Preliminary design of a flight control system for a V/STOL airplane with geared variable pitch fans

A flight control system designed for an aircraft powered by three variable pitch fans, interconnected by shafts to provide lifting system redundancy is considered for application to a Navy Type A V/STOL aircraft with similar configurational features. The differences and similarities in the applications are discussed with emphasis on a design approach for safety in the event of failures in the propulsion and flight control systems. Differences in flying qualities and system design criteria are considered.

Gotleib, P.↗

NASA NTRSDate not supplied

Should Astronauts throw out their Trash? And if so, How?

We don’t think much about taking out the trash on Earth, but in space, it requires some thought. Should it even be thrown overboard? Besides the implications of littering in space, there are also practical considerations of whether waste materials can be reused for other purposes onboard or do they reduce mission efficiency. In a previous study, gasifying and venting trash along the way to Mars was found to noticeably reduce propellant needs and launch mass of the spacecraft, whereas keeping processed trash on board in the form of radiation shielding tiles would significantly lower the crew’s radiation dose during a solar particle event. The latest human exploration mission proposals will be considered with an eye toward answering the questions, “Should Astronauts throw out their Trash?” and “If so, what is the best way?” Besides reviewing the propulsion and radiation shielding aspects of the question, equivalent system mass factors of mass, power, volume, and crew time, as well as human factors, like smell, will be studied. Disposal options include jettison of an entire module containing waste, regular disposal of trash via an airlock, or gasifying waste products for easier disposal or reuse. Jettison via an airlock could take many forms, from “taking out the trash” on a spacewalk to launching trash tiles or pods with different mechanisms. Likewise, the “trash-to-gas” concept, which would allow for overboard venting via a pipe, has many thermochemical processes to choose from, each with their own pros and cons. Unraveling these various tradeoff studies is the goal of this paper.

trash↗

NASA NTRS1991

Consort 3 flight experiments

The third sounding rocket payload in the Consort program was launched from the White Sands Missile Range on May 16, 1990. It carried 12 experiments designed to investigate materials processes in low gravity. All of the experiments were reflights from the Consort 2 payload that was launched on November 1989 but failed to achieve microgravity because of a malfunction in the launch vehicle. Four national Centers for the Commercial Development of Space participated in the mission. The payload included five experiments and two accelerometer systems that flew on Consort 1 and seven new experiments, designed and developed since Consort 1. Experiments from Consort 1 incorporated hardware modifications and changes in experimental parameters based on mission results. The new experiments covered a variety of polymeric and biological investigations. A new power distribution and control system designed to provide discrete, computer-supervised, experiment power monitoring and control was flight qualified on Consort 3. Consort 3 featured very late access (3-5 h before launch vs 27-30 h for Consort 1) for installation of sensitive biological specimens. The integrated payload and mission sequence of events are described. Changes in the Consort 1 experiments are defined and the objectives, methods, and expectations for new experiments are discussed.

Wessling, Francis C.↗

NASA NTRS2004

Experience and Grouping Effects when Handling Non-Normal Situations

Currently, most of the displays in control rooms can be categorized as status, alerts/procedures, or control screens. With the advent and use of CRTs and the associated computing power available to compute and display information, it is now possible to combine these different elements of information and control onto a single display. An experiment was conducted to determine which, if any, of these functions should be collocated in order to better handle simple anticipated non-normal system events. The results indicated that there are performance benefits and subject preferences to combining all the information onto one screen or combining the status and alert/procedure information onto one screen and placing the controls in another area. The results indicated that operators quickly modify their display preferences to the display configuration most recently used.

Trujillo, Anna C.↗

NASA NTRSDate not supplied

M2-SCREAM: A Stratospheric Composition Reanalysis of Aura MLS

Stratospheric composition and transport patterns are changing because of increasing greenhouse gas concentrations and declining levels of ozone depleting substances. Superimposed on forced trends are: dynamical variability at a range of time scales and unforeseen perturbations such as those resulting from injections of volcanic material and smoke from PyroCb events. Chemical reanalyses can be powerful tools for studying the composition of the stratosphere and disentangling forced responses from internal variability. This presentation introduces a new chemical reanalysis of stratospheric constituents developed and produced at NASA’s Global Modeling and Assimilation Office (GMAO) using the recently developed GMAO Constituent Data Assimilation System. Called the MERRA-2 Stratospheric Composition Reanalysis with Aura MLS (M2-SCREAM), this reanalysis consists of assimilated global three-dimensional fields of stratospheric ozone, water vapor, hydrogen chloride (HCl), nitric acid (HNO3) and nitrous oxide (N2O) mixing ratios and covers the period since the beginning of MLS observations in September 2004 to the present. M2-SCREAM assimilates version 4.2 MLS profiles of the five constituents alongside total ozone column from the Ozone Monitoring Instrument. The dynamics and tropospheric water vapor are constrained by assimilated meteorological fields from MERRA-2. The assimilated constituent fields and meteorology are provided to users at a 50-km horizontal resolution and a three-hourly frequency. Monthly analysis uncertainties and flags are also provided to the users. M2-SCREAM is an accurate and dynamically consistent high-resolution data record of the five constituents, all of which are of primary importance to stratospheric chemistry and transport studies. We will present a description of M2-SCREAM and selected results of a process-based evaluation of this product using independent data. As an illustration, we will discuss the perturbation to stratospheric composition from the eruption of Hunga Tonga–Hunga Ha'apai in January 2022 as seen in the reanalysis. We will also propose potential scientific applications of M2-SCREAM and outline plans for an upcoming comprehensive composition reanalysis that is being developed at NASA GMAO.

MERRA-2↗

NASA NTRS2023

Transient Optimization for the Betterment of Turbine Electrified Energy Management

Gas turbine engine transients are associated with degraded compressor operability, which must be addressed by the engine control system and accounted for in the engine design. Failure to do so may result in events such as compressor stall/surge and combustor blow out. Transient operability concerns constrain the engine design and can result in sacrifices of efficiency and/or thrust responsiveness. The traditional approach to transient operability management is control logic that limits the fuel flow command. A companion paper presents a strategy for optimizing the transient fuel flow control logic taking into consideration transient operability and thrust responsiveness. The study covered here extends this idea to an electrified gas turbine engine that employs a power/energy management concept known as Turbine Electrified Energy Management (TEEM). TEEM uses an electric power system interfaced with the engine (hence the term ‘electrified gas turbine engine’) to further improve transient operability and alleviate associated design constraints. There can be costs associated with implementing TEEM in terms of power and energy requirements that impact the size of the electrical power system. However, the results of this study show that through optimization of the transient limit logic, power and energy requirements needed to implement TEEM can be significantly reduced. Among the conclusions that can be drawn from the results of the illustrative application covered herein are: (1) there is a reduction in the electric machine power requirement to manage operability during accelerations by 200 to 400 hp, and (2) power transfer from the low pressure spool (LPS) to the high pressure spool (HPS) is the most effective option for improving operability during decelerations, followed by the options of only injecting power on the HPS or only extracting power from the LPS.

Turbine Electrified Energy Management↗

NASA NTRSDate not supplied

Transient Optimization for the Betterment of Turbine Electrified Energy Management

Gas turbine engine transients are associated with degraded compressor operability, which must be addressed by the engine control system and accounted for in the engine design. Failure to do so may result in events such as compressor stall/surge and combustor blow out. Transient operability concerns constrain the engine design and can result in sacrifices of efficiency and/or thrust responsiveness. The traditional approach to transient operability management is control logic that limits the fuel flow command. A companion paper presents a strategy for optimizing the transient fuel flow control logic taking into consideration transient operability and thrust responsiveness. The study covered here extends this idea to an electrified gas turbine engine that employs a power/energy management concept known as Turbine Electrified Energy Management (TEEM). TEEM uses an electric power system interfaced with the engine (hence the term ‘electrified gas turbine engine’) to further improve transient operability and alleviate associated design constraints. There can be costs associated with implementing TEEM in terms of power and energy requirements that impact the size of the electrical power system. However, the results of this study show that through optimization of the transient limit logic, power and energy requirements needed to implement TEEM can be significantly reduced. Among the conclusions that can be drawn from the results of the illustrative application covered herein are: (1) there is a reduction in the electric machine power requirement to manage operability during accelerations by 200 to 400 hp, and (2) power transfer from the low pressure spool (LPS) to the high pressure spool (HPS) is the most effective option for improving operability during decelerations, followed by the options of only injecting power on the HPS or only extracting power from the LPS.

transient↗

NASA NTRSDate not supplied

Transient Optimization for the Betterment of Turbine Electrified Energy Management

Gas turbine engine transients are associated with degraded compressor operability, which must be addressed by the engine control system and accounted for in the engine design. Failure to do so may result in events such as compressor stall/surge and combustor blow out. Transient operability concerns constrain the engine design and can result in sacrifices of efficiency and/or thrust responsiveness. The traditional approach to transient operability management is control logic that limits the fuel flow command. A companion paper presents a strategy for optimizing the transient fuel flow control logic taking into consideration transient operability and thrust responsiveness. The study covered here extends this idea to an electrified gas turbine engine that employs a power/energy management concept known as Turbine Electrified Energy Management (TEEM). TEEM uses an electric power system interfaced with the engine (hence the term ‘electrified gas turbine engine’) to further improve transient operability and alleviate associated design constraints. There can be costs associated with implementing TEEM in terms of power and energy requirements that impact the size of the electrical power system. However, the results of this study show that through optimization of the transient limit logic, power and energy requirements needed to implement TEEM can be significantly reduced. Among the conclusions that can be drawn from the results of the illustrative application covered herein are: (1) there is a reduction in the electric machine power requirement to manage operability during accelerations by 200 to 400 hp, and (2) power transfer from the low pressure spool (LPS) to the high pressure spool (HPS) is the most effective option for improving operability during decelerations, followed by the options of only injecting power on the HPS or only extracting power from the LPS.

transient↗

NASA NTRS2007

Systems Modeling to Implement Integrated System Health Management Capability

ISHM capability includes: detection of anomalies, diagnosis of causes of anomalies, prediction of future anomalies, and user interfaces that enable integrated awareness (past, present, and future) by users. This is achieved by focused management of data, information and knowledge (DIaK) that will likely be distributed across networks. Management of DIaK implies storage, sharing (timely availability), maintaining, evolving, and processing. Processing of DIaK encapsulates strategies, methodologies, algorithms, etc. focused on achieving high ISHM Functional Capability Level (FCL). High FCL means a high degree of success in detecting anomalies, diagnosing causes, predicting future anomalies, and enabling health integrated awareness by the user. A model that enables ISHM capability, and hence, DIaK management, is denominated the ISHM Model of the System (IMS). We describe aspects of the IMS that focus on processing of DIaK. Strategies, methodologies, and algorithms require proper context. We describe an approach to define and use contexts, implementation in an object-oriented software environment (G2), and validation using actual test data from a methane thruster test program at NASA SSC. Context is linked to existence of relationships among elements of a system. For example, the context to use a strategy to detect leak is to identify closed subsystems (e.g. bounded by closed valves and by tanks) that include pressure sensors, and check if the pressure is changing. We call these subsystems Pressurizable Subsystems. If pressure changes are detected, then all members of the closed subsystem become suspect of leakage. In this case, the context is defined by identifying a subsystem that is suitable for applying a strategy. Contexts are defined in many ways. Often, a context is defined by relationships of function (e.g. liquid flow, maintaining pressure, etc.), form (e.g. part of the same component, connected to other components, etc.), or space (e.g. physically close, touching the same common element, etc.). The context might be defined dynamically (if conditions for the context appear and disappear dynamically) or statically. Although this approach is akin to case-based reasoning, we are implementing it using a software environment that embodies tools to define and manage relationships (of any nature) among objects in a very intuitive manner. Context for higher level inferences (that use detected anomalies or events), primarily for diagnosis and prognosis, are related to causal relationships. This is useful to develop root-cause analysis trees showing an event linked to its possible causes and effects. The innovation pertaining to RCA trees encompasses use of previously defined subsystems as well as individual elements in the tree. This approach allows more powerful implementations of RCA capability in object-oriented environments. For example, if a pressurizable subsystem is leaking, its root-cause representation within an RCA tree will show that the cause is that all elements of that subsystem are suspect of leak. Such a tree would apply to all instances of leak-events detected and all elements in all pressurizable subsystems in the system. Example subsystems in our environment to build IMS include: Pressurizable Subsystem, Fluid-Fill Subsystem, Flow-Thru-Valve Subsystem, and Fluid Supply Subsystem. The software environment for IMS is designed to potentially allow definition of any relationship suitable to create a context to achieve ISHM capability.

Figueroa, Jorge F.↗

NASA NTRS1972

Manned space flight nuclear system safety. Volume 3: Reactor system preliminary nuclear safety analysis. Part 2: Accident Model Document (AMD)

The Accident Model Document is one of three documents of the Preliminary Safety Analysis Report (PSAR) - Reactor System as applied to a Space Base Program. Potential terrestrial nuclear hazards involving the zirconium hydride reactor-Brayton power module are identified for all phases of the Space Base program. The accidents/events that give rise to the hazards are defined and abort sequence trees are developed to determine the sequence of events leading to the hazard and the associated probabilities of occurence. Source terms are calculated to determine the magnitude of the hazards. The above data is used in the mission accident analysis to determine the most probable and significant accidents/events in each mission phase. The only significant hazards during the prelaunch and launch ascent phases of the mission are those which arise form criticality accidents. Fission product inventories during this time period were found to be very low due to very limited low power acceptance testing.

Source record↗

NASA NTRS1984

Millstone Hill radar: Capabilities for S/T observations

During the past several years, the 440-MHz radar at Millstone Hill has been modified to detect coherent echoes from clear-air turbulence in the stratosphere/troposphere (S/T) over the altitude range 4-25 km. Two distinct modes of data acquisition have been developed, and data reduction programs have been completed for one of these modes. This mode (I-mode) transmits a 10 microsec (1.5 km) pulse on the fully steerable antenna. Typically, the antenna is set at a low elevation angle (e.g., 15 deg.) to reduce the altitude resolution to approximately 1 km., and power spectra are collected at some 40 range gates. The antenna may be scanned in azimuth to obtain the total wind vector, held fixed to monitor wave motion, or scanned in elevation to monitor the horizontal extent of the turbulent activity. This steerability gives Millstone a flexible system to focus on localized events, such as lee waves or convective storms. An additional advantage at low elevations is the relatively large Doppler shift of the signal, since the LOS velocity contains a large component of the horizontal velocity. This shift separates the turbulence signal sufficiently far from the ground clutter to allow the spectral moments to be readily inferred. Some 500 hours of S/T I-mode data have been reduced to geophysical parameters, and reside on a data base at Millstone Hill.

Loriot, G. B.↗

NASA NTRS2013

Development of the Orion Crew-Service Module Umbilical Retention and Release Mechanism

The Orion CSM umbilical retention and release mechanism supports and protects all of the cross-module commodities between the spacecrafts crew and service modules. These commodities include explosive transfer lines, wiring for power and data, and flexible hoses for ground purge and life support systems. The mechanism employs a single separation interface which is retained with pyrotechnically actuated separation bolts and supports roughly two dozen electrical and fluid connectors. When module separation is commanded, either for nominal on-orbit CONOPS or in the event of an abort, the mechanism must release the separation interface and sever all commodity connections within milliseconds of command receipt. There are a number of unique and novel aspects of the design solution developed by the Orion mechanisms team. The design is highly modular and can easily be adapted to other vehiclesmodules and alternate commodity sets. It will be flight tested during Orions Exploration Flight Test 1 (EFT-1) in 2014, and the Orion team anticipates reuse of the design for all future missions. The design packages fluid, electrical, and ordnance disconnects in a single separation interface. It supports abort separations even in cases where aerodynamic loading prevents the deployment of the umbilical arm. Unlike the Apollo CSM umbilical which was a destructive separation device, the Orion design is resettable and flight units can be tested for separation performance prior to flight.Initial development testing of the mechanisms separation interface resulted in binding failures due to connector misalignments. The separation interface was redesigned with a robust linear guide system, and the connector separation and boom deployment were separated into two discretely sequenced events. These changes addressed the root cause of the binding failure by providing better control of connector alignment. The new design was tuned and validated analytically via Monte Carlo simulation. The analytical validation was followed by a repeat of the initial test suite plus test cases at thermal extremes and test cases with imposed mechanical failures demonstrating fault tolerance. The mechanism was then exposed to the qualification vibration environment. Finally, separation testing was performed at full speed with live ordnance.All tests of the redesigned mechanism resulted in successful separation of the umbilical interface with adequate force margins and timing. The test data showed good agreement with the predictions of the Monte Carlo simulation. The simulation proved invaluable due to the number of variables affecting the separation and the uncertainty associated with each. The simulation allowed for rapid assessment of numerous trades and contingency scenarios, and can be easily reconfigured for varying commodity sets and connector layouts.

Separation↗

NASA NTRS2012

Entry, Descent, and Landing Communications for the 2011 Mars Science Laboratory

The Mars Science Laboratory (MSL), established as the most advanced rover to land on the surface of Mars to date, launched on November 26th, 2011 and arrived to the Martian Gale Crater during the night of August 5th, 2012 (PDT). MSL will investigate whether the landing region was ever suitable to support carbon-based life, and examine rocks, soil, and the atmosphere with a sophisticated suite of tools. This paper addresses the flight system requirement by which the vehicle transmitted indications of the following events using both X-band tones and UHF telemetry to allow identification of probable root causes should a mission anomaly have occurred: Heat-Rejection System (HRS) venting, completion of the cruise stage separation, turn to entry attitude, atmospheric deceleration, bank angle reversal commanded, parachute deployment, heatshield separation, radar ground acquisition, powered descent initiation, rover separation from the descent stage, and rover release. During Entry, Descent, and Landing (EDL), the flight system transmitted a UHF telemetry stream adequate to determine the state of the spacecraft (including the presence of faults) at 8 kbps initiating from cruise stage separation through at least one minute after positive indication of rover release on the surface of Mars. The flight system also transmitted X-band semaphore tones from Entry to Landing plus one minute although since MSL was occulted, as predicted, by Mars as seen from the Earth, Direct-To-Earth (DTE) communications were interrupted at approximately is approx. 5 min after Entry ( approximately 130 prior to Landing). The primary data return paths were through the Deep Space Network (DSN) for DTE and the existing Mars network of orbiting assets for UHF, which included the Mars Reconnaissance Orbiter (MRO), Mars Odyssey (ODY), and Mars Express (MEX) elements. These orbiters recorded the telemetry data stream and returned it back to Earth via the DSN. The paper also discusses the total power received during EDL and the robustness of the telecom design strategy used to ensure EDL communications coverage.

relay operations↗

NASA NTRSDate not supplied

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↗

NASA NTRSDate not supplied

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↗

NASA NTRS1998

Trace-Driven Debugging of Message Passing Programs

In this paper we report on features added to a parallel debugger to simplify the debugging of parallel message passing programs. These features include replay, setting consistent breakpoints based on interprocess event causality, a parallel undo operation, and communication supervision. These features all use trace information collected during the execution of the program being debugged. We used a number of different instrumentation techniques to collect traces. We also implemented trace displays using two different trace visualization systems. The implementation was tested on an SGI Power Challenge cluster and a network of SGI workstations.

Frumkin, Michael↗

NASA NTRS2013

Development of the Orion Crew-Service Module Umbilical Retention and Release Mechanism

The Orion Crew-Service Module umbilical retention and release mechanism supports, protects and disconnects all of the cross-module commodities between the spacecraft's crew and service modules. These commodities include explosive transfer lines, wiring for power and data, and flexible hoses for ground purge and life support systems. Initial development testing of the mechanism's separation interface resulted in binding failures due to connector misalignments. The separation interface was redesigned with a robust linear guide system, and the connector separation and boom deployment were separated into two discretely sequenced events. Subsequent analysis and testing verified that the design changes corrected the binding. This umbilical separation design will be used on Exploration Flight Test 1 (EFT-1) as well as all future Orion flights. The design is highly modular and can easily be adapted to other vehicles/modules and alternate commodity sets.

Separation↗

NASA NTRS2013

Development of the Orion Crew-Service Module Umbilical Retention and Release Mechanism

The Orion Crew-Service Module umbilical retention and release mechanism supports, protects and disconnects all of the cross-module commodities between the spacecraft's crew and service modules. These commodities include explosive transfer lines, wiring for power and data, and flexible hoses for ground purge and life support systems. Initial development testing of the mechanism's separation interface resulted in binding failures due to connector misalignments. The separation interface was redesigned with a robust linear guide system, and the connector separation and boom deployment were separated into two discretely sequenced events. Subsequent analysis and testing verified that the design changes corrected the binding. This umbilical separation design will be used on Exploration Flight Test 1 (EFT-1) as well as all future Orion flights. The design is highly modular and can easily be adapted to other vehicles/modules and alternate commodity sets.

Delap, Damon↗