Search NASA⌕ Search

SEARCH · Search NASA

Results for “FIRE ALARMS”

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.

64 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Design and Development of Functionally Effective Human-Machine Interfaces for Firing Room Displays

This project involves creating software for support equipment used on the Space l aunch System (SLS). The goal is to create applications and displays that will be used to remotely operate equipment from the firing room and will continue to support the SLS launch vehicle to the extent of its program. These displays include design practices that help to convey information effectively, such as minimizing distractions at normal operating state and displaying intentional distractions during a warning or alarm state. The general practice for creating an operator display is to reduce the detail of unimportant aspects of the display and promote focus on data and dynamic information. These practices include using minimalist design, using muted tones for background colors, using a standard font at a readable text size, displaying alarms visible for Immediate attention, grouping data logically, and displaying data appropriately varying on the type of data. Users of these displays are more likely to stay focused on operating for longer periods by using design practices that reduce eye strain and fatigue. Effective operator displays will improve safety by reducing human errors during operation, which will help prevent catastrophic accidents. This report entails the details of my work on developing remote displays for the Hypergolics ground system. Before developing a prototype display, the design and requirements of the system are outlined and compiled into a document. Then each subsystem has schematic representations drawn tha.t meet the specifications detailed in the document. The schematics are then used as the outline to create display representations of each subsystem. Each display is first tested individually. Then the displays are integrated with a prototype of the master system, and they are tested in a simulated environment then retested in the real environment. Extensive testing is important to ensure the displays function reliably as intended.

Cho, Henry↗
NASA NTRS2019

Surface Emissivity Impacts on GOES-R Series Multi-Spectral Imagery Applications

Value-added imagery products from the GOES-R series Advanced Baseline Imager are used to identify features of interest for operational forecasters, including: blowing dust, smoke, volcanic ash, cloud cover, atmospheric moisture, biomass fires and snow cover. These features each have a specific spectral signal that algorithms are designed to detect, but those signals are not always unique to just a single feature. Sometimes, the surface can mimic the spectral signal associated with an atmospheric feature of interest, creating a false alarm in a value-added product which negatively impacts interpretation of that product. This case study focuses on one such situation where areas of desert in the southwestern United States mimic the positive value associated with low clouds in the Brightness Temperature Difference (BTD) between the 10.35 μm and 3.9 μm channels, producing a false alarm. In order to characterize these “false alarm” areas, this study uses the cloud-cleared background product from the Cooperative Institute for Research in the Atmosphere (CIRA) to create a dataset of the cloud-free surface. Previous results have shown that cloud-cleared backgrounds of the 10.35 μm-3.9 μm BTD have successfully identified areas of positive BTDs in the cloud-free environment, proving that it is a property of the surface emissivity and a true “false alarm”. This study builds on that previous research to further characterize the seasonality of the “false-alarm” regions and to catalogue how they impact interpretation of multi-spectral imagery products from the GOES-R series ABI, especially the Nighttime Microphysics RGB created by NASA Short-term Prediction Research and Transition (SPoRT) Center.

Burke, Angela↗
NASA NTRS1997

Dynamics Questions Associated with the AERCam Sprint Free-Flyer

The International Space Station will require the development of small robotic vehicles for such tasks as external inspection, monitoring of extravehicular activities (EVA's) and station build-up, and providing additional lighting at EVA worksites. The Autonomous EVA Robotic Camera (AERCam) family of free-flyers is currently being developed at NASA Johnson Space Center to perform these functions; the first member of the family is the AERCam Sprint vehicle. Many interesting dynamical questions are associated with the Sprint free-flyer. For instance, the reaction of a vehicle which is nearly spherically symmetric (such as Sprint) to a stuck-on thruster is significantly more complicated than that obtained for an idealized, perfectly spherical, spacecraft model. In particular, the real spacecraft will experience a form of forced nutation, with convergence towards either its major or minor principal axis, depending on both the applied torque and the mass properties of the vehicle. Furthermore, the body-fixed jet force vector may have a significant component along this principal axis, so giving rise to a considerable net linear acceleration of the spacecraft. The large velocity that can result is very important, as it may lead to collision with the nearby Orbiter, and is completely overlooked in the idealized analysis. This report will firstly briefly describe the stuck-on thruster dynamics of the real vehicle, and outline how the small products of inertia of the spacecraft determine the time constants of the motion. Secondly, the dynamical effects of a failed-off jet on the Sprint free-flyer will be described in more detail, and compared with the stuck-on thruster case. This will help to show whether the two malfunctions should be dealt with differently in flight. Finally, the stuck-on thruster detection software (known as the uncommanded motion algorithm) that is proposed to be flown on the Sprint vehicle will be analyzed, and all possible perturbation sources that may tend to give rise to false stuck-on thruster alarms quantified. It will be shown that false alarms can be triggered by discrete events such as a failed-off thruster, a glancing collision with Orbiter structure, or thruster saturation. They can also be triggered by a combination of errors introduced by constantly present sources such as thrust level errors, thruster misalignment, inertial cross-coupling, angular rate sensor noise, and structural vibrations induced by thruster firings. Based on this fact, the original plan to have the spacecraft enter safe mode whenever the uncommanded motion algorithm is triggered does not appear to be advisable. A better approach seems to be to provide the Sprint pilot with a warning whenever uncommanded motion is detected, and then allow the crew to determine whether safing the vehicle is appropriate.

Williams, Trevor↗
NASA NTRS2004

The GOES-R Lightning Mapper Sensor

The Lightning Mapper Sensor on GOES-R builds on previous measurements of lightning from low earth orbit by the OTD (Optical Transient Detector) and LIS (Lightning Imaging Sensor) sensors. Unlike observations from low earth orbit, the GOES-R platform will allow continuous monitoring of lightning activity over the Continental United States and southern Canada, Central and South America, and portions of the Atlantic and Pacific Oceans. The LMS will detect total (cloud-to-ground and intracloud) lightning at storm scale resolution (approx. 8 km) using a highly sensitive Charge Coupled Device (CCD) detector array. Discrimination between lightning optical transients and a bright sunlit background scene is accomplished by employing spectral, spatial, and temporal filtering along with a background subtraction technique. The result is 24 hour detection capability of total lightning. These total lightning observations can be made available to users within about 20 seconds. Research indicates a number of ways that total lightning observations from LMS could benefit operational activities, including 1) potential increases in lead times and reduced false alarms for severe thunderstorm and tornado Warnings, 2) improved routing of &rail around thunderstorms, 3) support for spacecraft launches and landings, 4) improved ability to monitor tropical cyclone intensity, 5) ability to monitor thunderstorm intensification/weakening during radar outages or where radar coverage is poor, 6) better identification of deep convection for the initialization of numerical prediction models, 7) improved forest fire forecasts, 8) identification of convective initiation, 9) identification of heavy convective snowfall, and 10) enhanced temporal resolution of storm evolution (1 minute) than is available from radar observations. Total lightning data has been used in an operational environment since July 2003 at the Huntsville, Alabama National Weather Service office. Total lightning measurements are obtained by the North Alabama Lightning Mapping Array (LMA) and have successfully been used in warning decisions. Every 2 minutes, total lightning counts in 2 km by 2 km horizontal, 1 km vertical grids are available to forecasters on an AWIPS (Advanced Weather Interactive Processing System) workstation. Experience with the LMA total lightning data is used to illustrate the potential use of LMS data that would be available to forecasters across the US. This abstract is for submission as a presentation to the National Weather Association Annual Meeting to be held 16-21 October 2004 in Portland, OR. This abstract will be published in the conference proceedings.

Buechler, Dennis↗
NASA NTRS2007

ISS Destiny Laboratory Smoke Detection Model

Smoke transport and detection were modeled numerically in the ISS Destiny module using the NIST, Fire Dynamics Simulator code. The airflows in Destiny were modeled using the existing flow conditions and the module geometry included obstructions that simulate the currently installed hardware on orbit. The smoke source was modeled as a 0.152 by 0.152 m region that emitted smoke particulate ranging from 1.46 to 8.47 mg/s. In the module domain, the smoke source was placed in the center of each Destiny rack location and the model was run to determine the time required for the two smoke detectors to alarm. Overall the detection times were dominated by the circumferential flow, the axial flow from the intermodule ventilation and the smoke source strength.

Brooker, John E.↗
NASA NTRS1999

Recent Developments in Chemically Reactive Sensors for Propellants

Propellant system leaks can pose a significant hazard in aerospace operations. For example, a leak in the hydrazine supply system of the shuttle auxiliary power unit (APU) has resulted in hydrazine ignition and fire in the aft compartment of the shuttle. Sensors indicating the location of a leak could provide valuable information required for operational decisions. WSTF has developed a small, single-use sensor for detection of propellant leaks. The sensor is composed of a thermistor bead coated with a substance which is chemically reactive with the propellant. The reactive thermistor is one of a pair of closely located thermistors, the other being a reference. On exposure to the propellant, the reactive coating responds exothermically to it and increases the temperature of the coated-thermistor by several degrees. The temperature rise is sensed by a resistive bridge circuit, and an alarm is registered by data acquisition software. The concept is general and has been applied to sensors for hydrazine, monomethylhydrazine, unsym-dimethylhydrazine, ammonia, hydrogen peroxide, ethanol, and dinitrogen tetroxide. Responses of these sensors to humidity, propellant concentration, distance from the liquid leak, and ambient pressure levels arc presented. A multi-use sensor has also been developed for hydrazine based on its catalytic reactivity with noble metals.

Davis, Dennis D.↗
NASA NTRS1999

A Hydrazine Leak Sensor Based on Chemically Reactive Thermistors

Leaks in the hydrazine supply system of the Shuttle APU can result in hydrazine ignition and fire in the aft compartment of the Shuttle. Indication of the location of a leak could provide valuable information required for operational decisions. WSTF has developed a small, single use sensor for detection of hydrazine leaks. The sensor is composed of a thermistor bead coated with copper(II) oxide (CuO) dispersed in a clay or alumina binder. The CuO-coated thermistor is one of a pair of closely located thermistors, the other being a reference. On exposure to hydrazine the CuO reacts exothermically with the hydrazine and increases the temperature of the coated-thermistor by several degrees. The temperature rise is sensed by a resistive bridge circuit and an alarm registered by data acquisition software. Responses of this sensor to humidity changes, hydrazine concentration, binder characteristics, distance from a liquid leak, and ambient pressure levels as well as application of this sensor concept to other fluids are presented.

Davis, Dennis D.↗
NASA NTRS2004

Genesis failure investigation report : JPL Failure Review Board, Avionics Sub-Team

On January 7, 2001, the Genesis spacecraft lifted off from Cape Canaveral. Its mission was to collect solar wind samples and return those samples to Earth for detailed analysis by scientists. The mission proceeded successfully for three-and-a-half years. On September 8, 2004, the spacecraft approached Earth, pointed the Sample Return Capsule (SRC) at its entry target, and then fired pyros that jettisoned the SRC. The SRC carried the valuable samples collected over the prior 29 months. The SRC also contained the requisite hardware (mechanisms, parachutes, and electronics) to manage the process of entry, descent, and landing (EDL). After entering Earthas atmosphere, the SRC was expected to open a drogue parachute. This should have been followed by a pyro event to release the drogue chute, and then by a pyro event to deploy the main parachute at an approximate elevation of 6.7 kilometers. As the SRC descended to the Utah landing site, helicopters were in position to capture the SRC before the capsule touched down. On September 8, 2004, observers of the SRCas triumphant return became concerned as the NASA announcer fell silent, and then became even more alarmed as they watched the spacecraft tumble as it streaked across the sky. Long-distance cameras clearly showed that the drogue parachute had not deployed properly. On September 9, 2004, General Eugene Tattini, Deputy Director of the Jet Propulsion Laboratory formed a Failure Review Board (FRB). This board was charged with investigating the cause of the Genesis mishap in close concert with the NASA Mishap Investigation Board (MIB). The JPL-FRB was populated with experts from within and external to the Jet Propulsion Laboratory. The JPL-FRB participated with the NASA-MIB through all phases of the investigation, working jointly and concurrently as one team to discover the facts of the mishap.

solar wind↗
NASA NTRS2004

Genesis failure investigation report

On January 7, 2001, the Genesis spacecraft lifted off from Cape Canaveral. Its mission was to collect solar wind samples and return those samples to Earth for detailed analysis by scientists. The mission proceeded successfully for three-and-a-half years. On September 8, 2004, the spacecraft approached Earth, pointed the Sample Return Capsule (SRC) at its entry target, and then fired pyros that jettisoned the SRC. The SRC carried the valuable samples collected over the prior 29 months. The SRC also contained the requisite hardware (mechanisms, parachutes, and electronics) to manage the process of entry, descent, and landing (EDL). After entering Earth’s atmosphere, the SRC was expected to open a drogue parachute. This should have been followed by a pyro event to release the drogue chute, and then by a pyro event to deploy the main parachute at an approximate elevation of 6.7 kilometers. As the SRC descended to the Utah landing site, helicopters were in position to capture the SRC before the capsule touched down. On September 8, 2004, observers of the SRC’s triumphant return became concerned as the NASA announcer fell silent, and then became even more alarmed as they watched the spacecraft tumble as it streaked across the sky. Long-distance cameras clearly showed that the drogue parachute had not deployed properly.

UNKNOWN↗
NASA NTRS2010

World, We Have Problems: Simulation for Large Complex, Risky Projects, and Events

Prior to a spacewalk during the NASA STS/129 mission in November 2009, Columbia Broadcasting System (CBS) correspondent William Harwood reported astronauts, "were awakened again", as they had been the day previously. Fearing something not properly connected was causing a leak, the crew, both on the ground and in space, stopped and checked everything. The alarm proved false. The crew did complete its work ahead of schedule, but the incident reminds us that correctly connecting hundreds and thousands of entities, subsystems and systems, finding leaks, loosening stuck valves, and adding replacements to very large complex systems over time does not occur magically. Everywhere major projects present similar pressures. Lives are at - risk. Responsibility is heavy. Large natural and human-created disasters introduce parallel difficulties as people work across boundaries their countries, disciplines, languages, and cultures with known immediate dangers as well as the unexpected. NASA has long accepted that when humans have to go where humans cannot go that simulation is the sole solution. The Agency uses simulation to achieve consensus, reduce ambiguity and uncertainty, understand problems, make decisions, support design, do planning and troubleshooting, as well as for operations, training, testing, and evaluation. Simulation is at the heart of all such complex systems, products, projects, programs, and events. Difficult, hazardous short and, especially, long-term activities have a persistent need for simulation from the first insight into a possibly workable idea or answer until the final report perhaps beyond our lifetime is put in the archive. With simulation we create a common mental model, try-out breakdowns of machinery or teamwork, and find opportunity for improvement. Lifecycle simulation proves to be increasingly important as risks and consequences intensify. Across the world, disasters are increasing. We anticipate more of them, as the results of global warming prove more and more ominous-glaciers melting in Bolivia, floods in Saudi Arabia, the Maldives sinking and salt rising along the Nile. Fear grows about potential asteroid crashes and nightly television images raise awareness of victims of floods, hurricanes, cyclones and typhoons, fire, tornado, tsunami, bombings, landslides, and cross-boundary criminality. The Red Cross says that disasters impact 250 million people each year. That means that 700,000 people are having a very bad day today. Modeling and simulation is and must be part of the solution.

Elfrey, Priscilla↗