Search NASA⌕ Search

SEARCH · Search NASA

Results for “Test guidelines”

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 595 records · Page 33

Observations of fallibility in applications of modern programming methodologies

Errors, inconsistencies, or confusing points are noted in a variety of published algorithms, many of which are being used as examples in formulating or teaching principles of such modern programming methodologies as formal specification, systematic construction, and correctness proving. Common properties of these points of contention are abstracted. These properties are then used to pinpoint possible causes of the errors and to formulate general guidelines which might help to avoid further errors. The common characteristic of mathematical rigor and reasoning in these examples is noted, leading to some discussion about fallibility in mathematics, and its relationship to fallibility in these programming methodologies. The overriding goal is to cast a more realistic perspective on the methodologies, particularly with respect to older methodologies, such as testing, and to provide constructive recommendations for their improvement.

Gerhart, S. L.↗

Rotor burst protection program: Experimentation to provide guidelines for the design of turbine rotor burst fragment containment rings

Empirical guidelines for the design of minimum weight turbine rotor disk fragment containment rings made from a monolithic metal were generated by experimentally establishing the relationship between a variable that provides a measure of containment ring capability and several other variables that both characterized the configurational aspects of the rotor fragments and containment ring, and had been found from exploratory testing to have had significant influence on the containment process. Test methodology and data analysis techniques are described. Results are presented in graphs and tables.

Mangano, G. J.↗

A Wind Tunnel Study on the Mars Pathfinder (MPF) Lander Descent Pressure Sensor

The primary focus of this study was to determine the accuracy of the Mars Pathfinder lander local pressure readings in accordance with the actual ambient atmospheric pressures of Mars during parachute descent. In order to obtain good measurements, the plane of the lander pressure sensor opening should ideally be situated so that it is parallel to the freestream. However, due to two unfavorable conditions, the sensor was positioned in locations where correction factors are required. One of these disadvantages is due to the fact that the parachute attachment point rotated the lander's center of gravity forcing the location of the pressure sensor opening to be off tangent to the freestream. The second and most troublesome factor was that the lander descends with slight oscillations that could vary the amplitude of the sensor readings. In order to accurately map the correction factors required at each sensor position, an experiment simulating the lander descent was conducted in the Martian Surface Wind Tunnel at NASA Ames Research Center. Using a 115 scale model at Earth ambient pressures, the test settings provided the necessary Reynolds number conditions in which the actual lander was possibly subjected to during the descent. In the analysis and results of this experiment, the readings from the lander sensor were converted to the form of pressure coefficients. With a contour map of pressure coefficients at each lander oscillatory position, this report will provide a guideline to determine the correction factors required for the Mars Pathfinder lander descent pressure sensor readings.

Soriano, J. Francisco↗

Mars Sample Handling Protocol Workshop Series: Workshop 2

Numerous NASA reports and studies have identified Planetary Protection (PP) as an important part of any Mars sample return mission. The mission architecture, hardware, on-board experiments, and related activities must be designed in ways that prevent both forward- and back-contamination and also ensure maximal return of scientific information. A key element of any PP effort for sample return missions is the development of guidelines for containment and analysis of returned sample(s). As part of that effort, NASA and the Space Studies Board (SSB) of the National Research Council (NRC) have each assembled experts from a wide range of scientific fields to identify and discuss issues pertinent to sample return. In 1997, the SSB released its report on recommendations for handling and testing of returned Mars samples. In particular, the NRC recommended that: a) samples returned from Mars by spacecraft should be contained and treated as potentially hazardous until proven otherwise, and b) rigorous physical, chemical, and biological analyses [should] confirm that there is no indication of the presence of any exogenous biological entity. Also in 1997, a Mars Sample Quarantine Protocol workshop was convened at NASA Ames Research Center to deal with three specific aspects of the initial handling of a returned Mars sample: 1) biocontainment, to prevent 'uncontrolled release' of sample material into the terrestrial environment; 2) life detection, to examine the sample for evidence of organisms; and 3) biohazard testing, to determine if the sample poses any threat to terrestrial life forms and the Earth's biosphere. In 1999, a study by NASA's Mars Sample Handling and Requirements Panel (MSHARP) addressed three other specific areas in anticipation of returning samples from Mars: 1) sample collection and transport back to Earth; 2) certification of the samples as non-hazardous; and 3) sample receiving, curation, and distribution. To further refine the requirements for sample hazard testing and the criteria for subsequent release of sample materials from quarantine, the NASA Planetary Protection Officer convened an additional series of workshops beginning in March 2000. The overall objective of these workshops was to develop comprehensive protocols to assess whether the returned materials contain any biological hazards, and to safeguard the purity of the samples from possible terrestrial contamination. This document is the report of the second Workshop in the Series. The information herein will ultimately be integrated into a final document reporting the proceedings of the entire Workshop Series along with additional information and recommendations.

Rummel, John D.↗

Repair of Electronics for Long Duration Spaceflight

To reduce mission risk, long duration spaceflight and exploration activities will require greater degrees of self-sufficiency with regards to repair capability than have ever been employed before in space exploration. The current repair paradigm of replacing Orbital Replacement Units (ORUs) of malfunctioning avionics and electronic hardware will be impractical, since carrying all of the spares that could possibly be needed for a long duration mission would require upmass and volume at unprecedented and unacceptable levels. A strategy of component-level repair for electronics, however, could significantly reduce the mass and volume necessary for spares and enhance mission safety via a generic contingency capability. This approach is already used to varying degrees by the U.S. Navy, where vessels at sea experience some similar constraints such as the need for self sufficiency for moderately long time periods, and restrictions on volume of repair spares and infrastructure. The concept of conducting component-level repairs of electronics in spacecraft requires the development of design guidelines for future avionics (to enable repair), development of diagnostic techniques to allow an astronaut to pinpoint the faulty component aboard a vastly complex vehicle, and development of tools and methodologies for dealing with the physical processes of replacing the component. This physical process includes tasks such as conformal coating removal and replacement, component removal, replacement, and alignment--all in the difficulty of a reduced gravity environment. Further, the gravitational effects on the soldering process must be characterized and accounted for to ensure reliability of the newly repaired components. The Component-Level Electronics-Assembly Repair (CLEAR) project under the NASA Supportability program was established to develop and demonstrate the practicality of this repair approach. CLEAR involves collaborative efforts between NASA s Glenn Research Center, Langley Research Center, Johnson Space Center, the National Center for Space Exploration Research, and the U.S. Navy. The project goals are 1) develop and demonstrate a manually-operated electronics repair capability to be conducted in a spacecraft environment; and 2) develop guidelines for designs of electronics that facilitates component-level repair for future space exploration efforts. This multi-faceted program utilizes a cross-disciplinary approach to examine pre- and post-repair diagnostics, conformal coating removal and replacement, component soldering, and electronics design for supportability. These areas are investigated by a combination of trade studies, ground based testing, reduced gravity aircraft testing, and actual spaceflight testing on the International Space Station (ISS) in multiple experiments. This paper details the efforts of this program, with emphasis on early trade study results, ground-based efforts, and two upcoming ISS experiments.

Pettegrew, Richard D.↗

Laser ignition application in a space experiment

A laser ignition system is proposed for the Combustion Experiment Module on an orbiting spacecraft. The results of a design study are given using the scheduled 'Flame Ball Experiment' as the design guidelines. Three laser ignition mechanisms and wavelengths are evaluated. A prototype laser is chosen and its specifications are given, followed by consideration of the beam optical arrangement, the ignition power requirement, the laser ignition system weight, size, reliability, and laser cooling and power consumption. Electromagnetic interference to the onboard electronics caused by the laser ignition process is discussed. Finally, ground tests are suggested.

Liou, Larry C.↗

Strain Gage Selection Criteria for Textile Composite Materials

This report will provide a review of efforts to establish a set of strain gage selection guidelines for textile reinforced composite materials. A variety of strain gages were evaluated in the study to determine the sensitivity of strain measurements to the size of the strain gage. The strain gages were chosen to provide a range of gage lengths and widths. The gage aspect ratio (the length-to-width ratio) was also varied. The gages were tested on a diverse collection of textile composite laminates. Test specimens featured eleven different textile architectures: four 2-D triaxial braids, six 3-D weaves, and one stitched uniweave architecture. All specimens were loaded in uniaxial tension. The materials' moduli were measured in both the longitudinal (parallel to the O deg. yarns) and the transverse (perpendicular to the O deg. yarns) directions. The results of these measurements were analyzed to establish performance levels for extensometers and strain gages on textile composite materials. Conclusions are expressed in a summary that discusses instrumentation practices and defines strain gage selection criteria.

Masters, John E.↗

Semi-Automated Diagnosis, Repair, and Rework of Spacecraft Electronics

NASA's Constellation Program for Exploration of the Moon and Mars places human crews in extreme isolation in resource scarce environments. Near Earth, the discontinuation of Space Shuttle flights after 2010 will alter the up- and down-mass capacity for the International Space Station (ISS). NASA is considering new options for logistics support strategies for future missions. Aerospace systems are often composed of replaceable modular blocks that minimize the need for complex service operations in the field. Such a strategy however, implies a robust and responsive logistics infrastructure with relatively low transportation costs. The modular Orbital Replacement Units (ORU) used for ISS requires relatively large blocks of replacement hardware even though the actual failed component may really be three orders of magnitude smaller. The ability to perform in-situ repair of electronics circuits at the component level can dramatically reduce the scale of spares and related logistics cost. This ability also reduces mission risk, increases crew independence and improves the overall supportability of the program. The Component-Level Electronics Assembly Repair (CLEAR) task under the NASA Supportability program was established to demonstrate the practicality of repair by first investigating widely used soldering materials and processes (M&P) performed by modest manual means. The work will result in program guidelines for performing manual repairs along with design guidance for circuit reparability. The next phase of CLEAR recognizes that manual repair has its limitations and some highly integrated devices are extremely difficult to handle and demand semi-automated equipment. Further, electronics repairs require a broad range of diagnostic capability to isolate the faulty components. Finally repairs must pass functional tests to determine that the repairs are successful and the circuit can be returned to service. To prevent equipment demands from exceeding spacecraft volume capacity and skill demands from exceeding crew time and training limits, the CLEAR project is examining options provided by non-real time tele-operations, robotics, and a new generation of diagnostic equipment. This paper outlines a strategy to create an effective repair environment where, with the support of ground based engineers, crewmembers can diagnose, repair and test flight electronics in-situ. This paper also discusses the implications of successful tele-robotic repairs when expanded to rework and reconfiguration of used flight assets for building Constellation infrastructure elements.

Struk, Peter M.↗

Building Reliable Printed Circuit Boards - the Lessons Learned

"Printed circuit boards (PCBs) are the baseline for electronics manufacturing upon which electronic components are mounted and formed into electronic systems. PCBs are used in a variety of electronic circuits from simple one-transistor amplifiers to large super computers. A PCB serves three main functions: 1) it provides the necessary mechanical support for the components in the circuit 2) it provides the necessary electrical interconnections, and 3) it bears some form of legend which identifies the components it carries. The failure modes on the PCBs can be categorized in a hierarchical structure, in which the mechanisms and causes are site or location dependant. This one day workshop will discuss a variety of failure mechanisms that effect the functionality of PCBs. These mechanisms can be related to how PCB materials are selected, PCBs are designed, manufactured, tested and used in the field conditions. The workshop will begin with an overview of PCB manufacturing, materials and processes. With the help of examples and case studies, a wide range of failure mechanisms will be discussed, case studies are focused on digital circuits, however some failures in analog, double sided boards are also presented. The workshop then provides the guideline for selection of methodologies for identifying potential failure mechanisms based on the failure history and how a systematic root cause failure analysis of the PCB can result in prevention of future issues."

Sood, Bhanu↗

Recertification analysis and inspection planning for environmental test facilities

Program development and implementation for recertification of pressure vessels used at NASA facilities are outlined, together with inspection procedures. The recertification is carried out in three phases: analysis, inspection planning, and long term inspection plans and management. A data base was developed for each piece of equipment and the associated performance parameters. Either documentation was obtained or NDT was performed on the vessels to confirm design and Code compliance. A Failure Modes and Effects Analysis technique was used to target recurring inspection items and guidelines were drawn up for inspections of parts and systems and intervals between inspections. The steps taken in establishing the program are considered applicable in both research and industrial situations.

Rebeck, K. J.↗

Wind loads on flat plate photovoltaic array fields (nonsteady winds)

Techniques to predict the dynamic response and the structural dynamic loads of flat plate photovoltaic arrays due to wind turbulence were analyzed. Guidelines for use in predicting the turbulent portion of the wind loading on future similar arrays are presented. The dynamic response and the loads dynamic magnification factor of the two array configurations are similar. The magnification factors at a mid chord and outer chord location on the array illustrated and at four points on the chord are shown. The wind tunnel test experimental rms pressure coefficient on which magnification factors are based is shown. It is found that the largest response and dynamic magnification factor occur at a mid chord location on an array and near the trailing edge. A technique employing these magnification factors and the wind tunnel test rms fluctuating pressure coefficients to calculate design pressure loads due to wind turbulence is presented.

Miller, R. D.↗

A solution procedure for three-dimensional incompressible Navier-Stokes equation and its application

An implicit, finite-difference procedure is presented for numerically solving viscous incompressible flows. For convenience of applying the present method to three-dimensional problems, primitive variables, namely the pressure and velocities, are used. One of the major difficulties in solving incompressible flows that use primitive variables is caused by the pressure field solution method which is used as a mapping procedure to obtain a divergence-free velocity field. The present method is designed to accelerate the pressure-field solution procedure. This is achieved by the method of pseudocompressibility in which the time derivative pressure term is introduced into the mass conservation equation. The pressure wave propagation and the spreading of the viscous effect is investigated using simple test problems. The present study clarifies physical and numerical characteristics of the pseudo-compressible approach in simulating incompressible flows. Computed results for external and internal flows are presented to verify the present procedure. The present algorithm has been shown to be very robust and accurate if the selection of the pseudo-compressibility parameter has been made according to the guidelines given.

Kwak, D.↗

LDA seeding system for the Langley Low Turbulence Pressure Tunnel

A Laser Velocimetry (LV) seeding system was specifically developed for the Langley Low Turbulence Wind Tunnel (LTPT), and it has been successfully used for LV measurements in two major tests (Juncture Flow Experiment and Gortler Experiment). The LTPT is capable of operating at Mach numbers from 0.05 to 0.50 and unit Reynolds numbers from 100,000 to 15,000,000 per foot. The test section is 3 feet wide and 7.5 feet high. The turbulence level in the test section is relatively low because of the high contraction ratio and because of the nine turbulence reduction screens in the settling chamber. A primary requirement of the seeding system was that the seeding material not contaminate or damage in any way these screens. Both solid and liquid seeding systems were evaluated, and the results are presented. They can provide some guidelines for setting up seeding systems in other similar tunnels.

Scheiman, J.↗

Long life assurance study for manned spacecraft long life hardware. Volume 4: Special long life assurance studies

Guidelines for the selection of equipment to be used for manned spacecraft in order to assure a five year maintenance-free service life were developed. A special study was conducted to determine the adequacy of the procedures used to determine the quality and effectiveness of various components. The subjects examined are: (1) temperature cycling for acceptance of electronic assemblies; (2) accelerated testing techniques; (3) electronic part screening techniques; (4) electronic part derating practices; (5) vibration life extension of printed circuit board assemblies; and (6) tolerance funnelling and test requirements.

Source record↗

Sealed silver oxide zinc cells for orbiting and planetary missions.

Several test programs were carried out to determine the performance and limitations of sealed, silver oxide zinc cells for (1) 24-hr synchronous orbits, (2) orbits that would require a maximum of six cycles per day, and (3) missions to other planets requiring maintenance of maximum capacity for probe operations during planet encounter. The results are summarized to provide power system designers with guidelines bearing on capacity maintenance during cycling, cycle life, charged stand effects, and internal pressure characteristics. The life of zinc silver oxide cells is shown to be limited to one to two years over the temperature range of 0 to 24 C.

Hennigan, T. J.↗

Data Applicability of Heritage and New Hardware For Launch Vehicle Reliability Models

Bayesian reliability requires the development of a prior distribution to represent degree of belief about the value of a parameter (such as a component's failure rate) before system specific data become available from testing or operations. Generic failure data are often provided in reliability databases as point estimates (mean or median). A component's failure rate is considered a random variable where all possible values are represented by a probability distribution. The applicability of the generic data source is a significant source of uncertainty that affects the spread of the distribution. This presentation discusses heuristic guidelines for quantifying uncertainty due to generic data applicability when developing prior distributions mainly from reliability predictions.

Al Hassan, Mohammad↗

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗

Unshrouded Centrifugal Turbopump Impeller Design Methodology

Turbopump weight continues to be a dominant parameter in the trade space for reduction of engine weight. Space Shuttle Main Engine weight distribution indicates that the turbomachinery make up approximately 30% of the total engine weight. Weight reduction can be achieved through the reduction of envelope of the turbopump. Reduction in envelope relates to an increase in turbopump speed and an increase in impeller head coefficient. Speed can be increased until suction performance limits are achieved on the pump or due to alternate constraints the turbine or bearings limit speed. Once the speed of the turbopump is set the impeller tip speed sets the minimum head coefficient of the machine. To reduce impeller diameter the head coefficient must be increased. A significant limitation with increasing head coefficient is that the slope of the head-flow characteristic is affected and this can limit engine throttling range. Unshrouded impellers offer a design option for increased turbopump speed without increasing the impeller head coefficient. However, there are several issues with regard to using an unshrouded impeller: there is a pump performance penalty due to the front open face recirculation flow, there is a potential pump axial thrust problem from the unbalanced front open face and the back shroud face, and since test data is very limited for this configuration, there is uncertainty in the magnitude and phase of the rotordynamic forces due to the front impeller passage. The purpose of the paper is to discuss the design of an unshrouded impeller and to examine the hydrodynamic performance, axial thrust, and rotordynamic performance. The design methodology will also be discussed. This work will help provide some guidelines for unshrouded impeller design.

Prueger, George H.↗