Search NASA⌕ Search

SEARCH · Search NASA

Results for “hardware testing”

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 1,045 records · Page 58

Evaluation of methods for determining hardware projected life

An investigation of existing methods of predicting hardware life is summarized by reviewing programs having long life requirements, current research efforts on long life problems, and technical papers reporting work on life predicting techniques. The results indicate that there are no accurate quantitative means to predict hardware life for system level hardware. The effectiveness of test programs and the cause of hardware failures is considered.

Source record↗

Long life assurance study for manned spacecraft long life hardware. Volume 5: Long life assurance test and study recommendations

A study was conducted to establish the guidelines to be applied to the selection of equipment for manned spacecraft systems. Recommendations for expansion of the original study are submitted. The subjects considered are: (1) designing to severe dynamic requirements; (2) analysis of in-space failures due to life limitations; (3) accelerated testing of semiconductors; (4) fan life verification; (5) testing of solid tantalum capacitors; (6) testing of teflon valve seats; and (7) electromigration model verification.

Source record↗

Strategy in space flight experiments

The main topics of the workshop were the evaluation of both the need for flight testing of solar array hardware and the opportunities for such testing. Spacecraft charging effects, array dynamics, cost-effectiveness, and methods of flight planning were also discussed.

Marvin, Dean↗

Development of an Ion Thruster and Power Processor for New Millennium's Deep Space 1 Mission

The NASA Solar Electric Propulsion Technology Applications Readiness Program (NSTAR) will provide a single-string primary propulsion system to NASA's New Millennium Deep Space 1 Mission which will perform comet and asteroid flybys in the years 1999 and 2000. The propulsion system includes a 30-cm diameter ion thruster, a xenon feed system, a power processing unit, and a digital control and interface unit. A total of four engineering model ion thrusters, three breadboard power processors, and a controller have been built, integrated, and tested. An extensive set of development tests has been completed along with thruster design verification tests of 2000 h and 1000 h. An 8000 h Life Demonstration Test is ongoing and has successfully demonstrated more than 6000 h of operation. In situ measurements of accelerator grid wear are consistent with grid lifetimes well in excess of the 12,000 h qualification test requirement. Flight hardware is now being assembled in preparation for integration, functional, and acceptance tests.

Sovey, James S.↗

Zero Gravity Research Facility User's Guide

The Zero Gravity Research Facility (ZGF) is operated by the Space Experiments Division of the NASA John H. Glenn Research Center (GRC) for investigators sponsored by the Microgravity Science and Applications Division of NASA Headquarters. This unique facility has been utilized by scientists and engineers for reduced gravity experimentation since 1966. The ZGF has provided fundamental scientific information, has been used as an important test facility in the space flight hardware design, development, and test process, and has also been a valuable source of data in the flight experiment definition process. The purpose of this document is to provide information and guidance to prospective researchers regarding the design, buildup, and testing of microgravity experiments.

Thompson, Dennis M.↗

Extravehicular mobility unit training and astronaut injuries

BACKGROUND: Astronaut spacewalk training can result in a variety of symptom complaints and possible injuries. This study quantified and characterized signs, symptoms, and injuries resulting from extravehicular activity spacesuit training at NASA's Neutral Buoyancy Laboratory, Johnson Space Center, Houston, TX, immersion facility. METHODS: We identified the frequency and incidence of symptoms by location, mechanisms of injury, and effective countermeasures. Recommendations were made to improve injury prevention, astronaut training, test preparation, and training hardware. At the end of each test, a questionnaire was completed documenting signs and symptoms, mechanisms of injury, and countermeasures. RESULTS: Of the 770 tests, there were 190 in which suit symptoms were reported (24.6%). There were a total of 352 reported suit symptom comments. Of those symptoms, 166 were in the hands (47.16%), 73 were in the shoulders (20.7%), and 40 were in the feet (11.4%). Others ranged from 6.0% to 0.28%, respectively, from the legs, arms, neck, trunk, groin, and head. Causal mechanisms for the hands included moisture and hard glove contacts resulting in fingernail injuries; in the shoulders, hard contact with suit components and strain mechanisms; and in the feet, hard boot contact. The severity of symptoms was highest in the shoulders, hands, and feet. CONCLUSIONS: Most signs and symptoms were mild, self-limited, of brief duration, and were well controlled by available countermeasures. Some represented the potential for significant injury with consequences affecting astronaut health and performance. Correction of extravehicular activity training-related injuries requires a multidisciplinary approach to improve prevention, medical intervention, astronaut training, test planning, and suit engineering.

Non-programmatic↗

Testing Microshutter Arrays Using Commercial FPGA Hardware

NASA is developing micro-shutter arrays for the Near Infrared Spectrometer (NIRSpec) instrument on the James Webb Space Telescope (JWST). These micro-shutter arrays allow NIRspec to do Multi Object Spectroscopy, a key part of the mission. Each array consists of 62414 individual 100 x 200 micron shutters. These shutters are magnetically opened and held electrostatically. Individual shutters are then programmatically closed using a simple row/column addressing technique. A common approach to provide these data/clock patterns is to use a Field Programmable Gate Array (FPGA). Such devices require complex VHSIC Hardware Description Language (VHDL) programming and custom electronic hardware. Due to JWST's rapid schedule on the development of the micro-shutters, rapid changes were required to the FPGA code to facilitate new approaches being discovered to optimize the array performance. Such rapid changes simply could not be made using conventional VHDL programming. Subsequently, National Instruments introduced an FPGA product that could be programmed through a Labview interface. Because Labview programming is considerably easier than VHDL programming, this method was adopted and brought success. The software/hardware allowed the rapid change the FPGA code and timely results of new micro-shutter array performance data. As a result, numerous labor hours and money to the project were conserved.

Rapchun, David↗

System Testing of Ground Cooling System Components

This internship focused primarily upon software unit testing of Ground Cooling System (GCS) components, one of the three types of tests (unit, integrated, and COTS/regression) utilized in software verification. Unit tests are used to test the software of necessary components before it is implemented into the hardware. A unit test determines that the control data, usage procedures, and operating procedures of a particular component are tested to determine if the program is fit for use. Three different files are used to make and complete an efficient unit test. These files include the following: Model Test file (.mdl), Simulink SystemTest (.test), and autotest (.m). The Model Test file includes the component that is being tested with the appropriate Discrete Physical Interface (DPI) for testing. The Simulink SystemTest is a program used to test all of the requirements of the component. The autotest tests that the component passes Model Advisor and System Testing, and puts the results into proper files. Once unit testing is completed on the GCS components they can then be implemented into the GCS Schematic and the software of the GCS model as a whole can be tested using integrated testing. Unit testing is a critical part of software verification; it allows for the testing of more basic components before a model of higher fidelity is tested, making the process of testing flow in an orderly manner.

Unit Test↗

Developing Avionics Hardware and Software for Rocket Engine Testing

My summer was spent working as an intern at Kennedy Space Center in the Propulsion Avionics Branch of the NASA Engineering Directorate Avionics Division. The work that I was involved with was part of Rocket University's Project Neo, a small scale liquid rocket engine test bed. I began by learning about the layout of Neo in order to more fully understand what was required of me. I then developed software in LabView to gather and scale data from two flowmeters and integrated that code into the main control software. Next, I developed more LabView code to control an igniter circuit and integrated that into the main software, as well. Throughout the internship, I performed work that mechanics and technicians would do in order to maintain and assemble the engine.

liquid rocket↗

Replacement of Hydrochlorofluorocarbon (HCFC) -225 Solvent for Cleaning and Verification Sampling of NASA Propulsion Oxygen Systems Hardware, Ground Support Equipment, and Associated Test Systems

Since the 1990's, NASA's rocket propulsion test facilities at Marshall Space Flight Center (MSFC) and Stennis Space Center (SSC) have used hydrochlorofluorocarbon-225 (HCFC-225), a Class II ozone-depleting substance, to safety clean and verify the cleanliness of large scale propulsion oxygen systems and associated test facilities. In 2012 through 2014, test laboratories at MSFC, SSC, and Johnson Space Center-White Sands Test Facility collaborated to seek out, test, and qualify an environmentally preferred replacement for HCFC-225. Candidate solvents were selected, a test plan was developed, and the products were tested for materials compatibility, oxygen compatibility, cleaning effectiveness, and suitability for use in cleanliness verification and field cleaning operations. Honewell Soltice (TradeMark) Performance Fluid (trans-1-chloro-3,3, 3-trifluoropropene) was selected to replace HCFC-225 at NASA's MSFC and SSC rocket propulsion test facilities.

Burns, H. D.↗

Replacement of Hydrochlorofluorocarbon (HCFC) -225 Solvent for Cleaning and Verification Sampling of NASA Propulsion Oxygen Systems Hardware, Ground Support Equipment, and Associated Test Systems

Since the 1990's, when the Class I Ozone Depleting Substance (ODS) chlorofluorocarbon-113 (CFC-113) was banned, NASA's rocket propulsion test facilities at Marshall Space Flight Center (MSFC) and Stennis Space Center (SSC) have relied upon hydrochlorofluorocarbon-225 (HCFC-225) to safely clean and verify the cleanliness of large scale propulsion oxygen systems. Effective January 1, 2015, the production, import, export, and new use of HCFC-225, a Class II ODS, was prohibited by the Clean Air Act. In 2012 through 2014, leveraging resources from both the NASA Rocket Propulsion Test Program and the Defense Logistics Agency - Aviation Hazardous Minimization and Green Products Branch, test labs at MSFC, SSC, and Johnson Space Center's White Sands Test Facility (WSTF) collaborated to seek out, test, and qualify a replacement for HCFC-225 that is both an effective cleaner and safe for use with oxygen systems. Candidate solvents were selected and a test plan was developed following the guidelines of ASTM G127, Standard Guide for the Selection of Cleaning Agents for Oxygen Systems. Solvents were evaluated for materials compatibility, oxygen compatibility, cleaning effectiveness, and suitability for use in cleanliness verification and field cleaning operations. Two solvents were determined to be acceptable for cleaning oxygen systems and one was chosen for implementation at NASA's rocket propulsion test facilities. The test program and results are summarized. This project also demonstrated the benefits of cross-agency collaboration in a time of limited resources.

Mitchell, Mark A.↗

NASA's Space Launch System: Progress Report

After more than four decades exploring the space environment from low Earth orbit and developing long-duration spaceflight operational experience with the International Space Station (ISS), NASA is once again preparing to send explorers into deep space. Development, test and manufacturing is now underway on the launch vehicle, the crew spacecraft and the ground processing and launch facilities to support human and robotic missions to the moon, Mars and the outer solar system. The enabling launch vehicle for these ambitious new missions is the Space Launch System (SLS), managed by NASA's Marshall Space Flight Center (MSFC). Since the program began in 2011, the design has passed Critical Design Review, and extensive development, test and flight hardware has been produced by every major element of the SLS vehicle. Testing continues on engines, boosters, tanks and avionics. While the program has experienced engineering challenges typical of a new development, it continues to make steady progress toward the first SLS mission in roughly two years and a sustained cadence of missions thereafter. This paper will discuss these and other technical and SLS programmatic successes and challenges over the past year and provide a preview of work ahead before first flight.

Cook, Jerry↗

ATLAS Flight Science Receiver Algorithms

This is the basis document for the ATLAS Receiver Algorithms. ATLAS is the single instrument on the ICESat-2 mission. The Receiver (Rx) Algorithms select the signal location in real-time and instruct the hardware to telemeter a vertical band of received time-tags about this signal location. The algorithms are implemented in the Flight Software (FSW) and in the hardware of the Photon Counting Electronics (PCE) cards. The sole purpose of the algorithms is to reduce the telemetry data volume to fit within the downlink constraint while maximizing the probability of downlinking surface signal. All versions of the Receiver Algorithms from version 2.8 onward incorporate our best knowledge of the ATLAS hardware at this time. It presents algorithms that, based on current Simulator testing, satisfy all of the requirements for the Rx Algorithms. Testing during ATLAS Instrument Integration and Testing with the hardware and software implementation of the Rx Algorithms revealed characteristics and responses that required changes to the Rx Algorithms and this document, which are captured in the change record below.All relevant documentation for the Receiver Algorithms can be found on the ICESat-2 Technical Data Management System (TDMS) under the ATLAS Algorithms subsystem.The launch version of the FSW (version 3.1.0) is based upon version 3.7c of this document.

Mcgarry, Jan L.↗

Hydrogen Peroxide-Water-Ethanol-Monopropellant Blend for CubeSat Propulsion

Monopropellant propulsion that provides high performance and low hazards compared to state-of-art hydrazine are being investigated under NASA, DOD and commercially sponsored green propellant research and development programs. This NASAeffort looks at phosphate stabilized 50% hydrogen peroxide/water –ethanol blends to evaluate their stability and combustion behavior in submillimeter diameter microtube combustion apparatus for cubesat propulsion applications. Exploratory 7-day stabilitytests find no pressure rise in a sealed test tube environment at room temperature indicating at least short term stability of the mixture. Temperature rise during combustion testing in resistively heated nickel microtube apparatus shows that micro-combustion is achieved in the tube. Propellant density is approximately 1.2 g/cm3compared to 1.0 g/cm3for hydrazine. Theoretical specific impulse of the stoichiometric blend is 219 s at a chamber pressure of 20 psia and an area ratio of 30:1. Density-specific impulseof this blendis263 swhile hydrazine is only about 215-220 sin small reaction control system thrusters. This provides about 20-22% more density-specific impulse for the cubesat compared to hydrazine. The theoreticalcombustion temperature is2168°F, whichis thermally compatible with stainless steel materials of constructionand the nickel catalystused in the tests. Combustion test results are given for stoichiometric, as well as fuel-leanand fuel-richpropellant formulations. Thesetests focus on thermally and catalytically supported combustionin the microtube, whichrequires a microtube preheat temperature of about 900°F and sufficient residence time to achieve combustion that is stable and anchored in the tubewithout blowing through the tube unreacted. Thrust class is expected to be in the 10 mN range based on flow rate and estimated specific impulse.Power requirements are generally below 25 Wto heat the tube. Steady state combustion testing is typically conducted for 3 minutes and shows littledegradation of the hardware over multiple test cyclesindicating thatthere is little catalyst degradation over time and littlecatalyst deactivation due tothe phosphate stabilizer inthe hydrogen peroxide.

Monopropellant↗

Computing Risk of Pyrotechnic Devices Using Lot Acceptance Testing

This paper presents an application of statistical engineering to solve the problem of determining the effects of reducing test sample sizes and environment levels in lot acceptance testing (LAT) of ordnance devices used by NASA and DoD space systems. Unlike environmental testing of dedicated qualification hardware, ordnance devices have a test-like-you-fly exception and use lot acceptance sampling or LAT. LAT is performed by randomly selecting a predefined number of devices from an individual lot and exposing them to a more severe dynamic shock and vibration testing environments than flight (sometimes as high as 6 decibels over flight environments) and then performing a destructive test on the device. Recent trends have been suggested to reduce LAT costs by reducing environment test levels or the number of devices per LAT, or both. A method is given here to compute flight risk, so the proposed methods can be compared by subject matter experts to the baseline LAT methods. In addition, this method can be used to determine the best methods to include in future LAT standards for pyrotechnic devices.

Computing Risk↗

Design, Development and Test Challenges: Separation Mechanisms for the Orion Pad Abort-1 Flight Test

On May 6, 2010, NASA launched the first successful integrated flight test, Pad Abort-1, of the Orion Project from the White Sands Missile Range in Las Cruces, New Mexico. This test demonstrated the ability to perform an emergency pad abort of a full-scale 4.8 m diameter, 8200 kg crew capsule. During development of the critical separation mechanisms for this flight test, various challenges were overcome related to environments definition, installation complications, separation joint retraction speed, thruster ordnance development issues, load path validation and significant design loads increases. The Launch Abort System retention and release (LAS R&R) mechanism consisted of 6 discrete structural connections between the LAS and the crew module (CM) simulator, each of which had a preloaded tension tie, Superbolt torque-nut and frangible nut. During the flight test, the frangible nuts were pyrotechnically split, permitting the CM to separate from the LAS. The LAS separation event was the driving case in the shock environment for many co-located hardware items. During development testing, it was necessary to measure the source shock during the separation event so the predicted shock environment could be validated and used for certification testing of multiple hardware items. The Lockheed Martin test team measured the source separation shock due to the LAS R&R function, which dramatically decreased the predicted environment by 90% at 100 Hz. During development testing a hydraulic tensioner was used to preload the joint; however, the joint relaxation with the tensioner proved unsatisfactory so the design was modified to include a Superbolt torque-nut. The observed preload creep during lab testing was 4% after 30 days, with 2.5% occurring in the first 24 hours. The conversion of strain energy (preload) to kinetic energy (retraction) was measured to be 50-75%. Design features and careful monitoring of multiple strain gauges on each tension tie allowed a pure tensile load to be applied after stacking at the launch pad. Following installation, preload in each joint was monitored for 24 hours. Due to unforeseen complications and the influence of temperature on the portable data acquisition system, the team encountered difficulty in tracking the joint relaxation. In some cases, bond-line failure of the strain gauges occurred.

Dinsel, Alison↗