Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Certified”

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 307 records · Page 17

Certification of CFD heat transfer software for turbine blade analysis

Accurate modeling of heat transfer effects is a critical component of the Turbine Branch of the Turbomachinery and Propulsion Systems Division. Being able to adequately predict and model heat flux, coolant flows, and peak temperatures are necessary for the analysis of high pressure turbine blades. To that end, the primary goal of my internship this summer will be to certify the reliability of the CFD program GlennHT for the purpose of turbine blade heat transfer analysis. GlennHT is currently in use by the engineers in the Turbine Branch who use the FORTRAN 77 version of the code for analysis. The program, however, has been updated to a FORTRAN 90 version which is more robust than the older code. In order for the new code to be distributed for use, its reliability must first be certified. Over the course of my internship I will create and run test cases using the FORTRAN 90 version of GlennHT and compare the results to older cases which are known to be accurate, If the results of the new code match those of the sample cases then the newer version will be one step closer to certification for distribution. In order to complete these it will first be necessary to become familiar with operating a number of other programs. Among them are GridPro, which is used to create a grid mesh around a blade geometry, and FieldView, whose purpose is to graphically display the results from the GlennHT program. Once enough familiarity is established with these programs to render them useful, then the work of creating and running test scenarios will begin. The work is additionally complicated by a transition in computer hardware. Most of the working computers in the Turbine Branch are Silicon Graphics machines, which will soon be replaced by LINUX PC's. My project is one of the first to make use the new PC's. The change in system architecture however, has created several software related issues which have greatly increased the time and effort investments required by the project.Although complications with the project continue to arise, it is expected that the goal of my internship can still be achieved within the remaining time period. Critical steps have been achieved and test scenarios can now be designed and run. At the completion of my internship, the FORTRAN 90 version of GlennHT should be well on its way to certification.

Jordan, William A.↗

Certification Testing Approach for Propulsion System Design

The Certification of Propulsion Systems is costly and complex which involves development and qualification testing. The desire of the certification process is to assure all requirements can be demonstrated to be compliant. The purpose of this paper is to address the technical design concerns of certifying a system for flight. The authors of this paper have experience the lessons learned from supporting the Shuttle Program for Main Propulsion and On Orbit Propulsions Systems. They have collaborated design concerns for certifying propulsion systems. Presented are Pressurization, Tankage, Feed System and Combustion Instability concerns. Propulsion System Engineers are challenged with the dilemma for testing new systems to specific levels to reduce risk yet maintain budgetary targets. A methodical approach is presented to define the types of test suitable to address the technical issues for qualifying systems for retiring the risk levels.

Rodriguez, Henry↗

Certification Testing Approach for Propulsion System Design

The Certification of Propulsion Systems is costly and complex, involving development and qualification testing. The desire of the certification process is to assure all requirements can be demonstrated to be compliant. The purpose of this paper is to address the technical design concerns of certifying a propulsion system for flight. Presented are Pressurization, Tankage, Feed System and Combustion Instability concerns. Propulsion System Engineers are challenged with the dilemma for testing new systems to specific levels to reduce risk yet maintain budgetary targets. A methodical approach is presented to define the types of test suitable to address the technical issues for qualifying systems for retiring the risk levels. Experience of the lessons learned from supporting the Shuttle Program for Main Propulsion and On Orbit Propulsions Systems as well as previous collaborations on design concerns for certifying propulsion systems are utilized to address design concerns and verification approaches.

Rodriguez, Henry↗

Testing Functions of One and Two Arguments

Software to evaluate functions of one or two arguments is too often tested or certified, or the accuracy assessed, by ad hoc methods. Systematic methods to test, certify or assess the accuracy of single- or double-precision functions of one or two arguments, and supporting software, are described here.

software software evaluation arguments↗

Manufacturing of Igniters for NHB 8060.1 Testing

The purpose of this WJI is to incorporate a standard procedure to prepare, certify, and ship standard NHB 8060.1B and NHB 8060.1C igniters for flammability testing and to update LJI-320-35-18. The operations are divided into five parts as follows: A. Preparing the igniter mix; B. Extruding the igniters; C. Curing, cutting, and weighing the igniters; D. Certifying the igniters and E. Packaging, storing, and shipping the igniters

Williams, James↗

Pressure Effects on the Self-Extinguishment Limits of Aerospace Materials

The Orion Crew Exploration Vehicle Module (CM) is being designed to operate in an atmosphere of up to 30% oxygen at a pressure of 10.2 psia for lunar missions. Spacecraft materials selection is based on an upward flammability test conducted in a closed chamber under the worst expected conditions of pressure and oxygen concentration. Material flammability depends on both oxygen concentration and pressure but, since oxygen concentration is the primary driver, all materials are certified in the 30% oxygen, 10.2 psia environment. Extensive data exist from the Shuttle Program at this condition which used relatively the same test methodology as currently used in the Constellation Program. When the CM returns to Earth, a snorkel device will be activated after splashdown to provide outside air to the crew; however, for operational reasons, it is desirable to maximize the time the crew is able to breathe cabin air before the snorkel device is activated. To maximize this time, it has been proposed to raise the partial pressure of oxygen in the CM immediately before reentry while maintaining the total cabin pressure at 14.7 psia. In addition, it has been proposed to leak-test the Orion CM with ambient air at a maximum pressure of 17.3 psia. No data exist to assess how high the cabin oxygen concentration can be at 14.7 psia or 17.3 psia. One is to re-test a large number of materials at these pressures at a significant cost. However, since the maximum oxygen concentration (MOC) at which a material will self-extinguish has been determined for a variety of spacecraft materials as a function of pressure, a second alternative is to use existing data to estimate the MOC at 14.7 psia and 17.3 psia. This data will be examined in this paper and an analysis presented to determine the oxygen concentrations at the increased pressures that will result in self-extinguishment of a material. This analysis showed that the oxygen concentration for the Orion CM at 14.7 psia cannot be set higher than 25.6% without potentially invalidating the materials flammability certification in 30% oxygen at 10.2 psia for some materials. Materials certified under these conditions would still be self-extinguishing in ambient air at 17.3 psia. alternative

Hirsch, David B.↗

Real-Time Simulation of Ares I Launch Vehicle

The Ares Real-Time Environment for Modeling, Integration, and Simulation (ARTEMIS) has been developed for use by the Ares I launch vehicle System Integration Laboratory (SIL) at the Marshall Space Flight Center (MSFC). The primary purpose of the Ares SIL is to test the vehicle avionics hardware and software in a hardware-in-the-loop (HWIL) environment to certify that the integrated system is prepared for flight. ARTEMIS has been designed to be the real-time software backbone to stimulate all required Ares components through high-fidelity simulation. ARTEMIS has been designed to take full advantage of the advances in underlying computational power now available to support HWIL testing. A modular real-time design relying on a fully distributed computing architecture has been achieved. Two fundamental requirements drove ARTEMIS to pursue the use of high-fidelity simulation models in a real-time environment. First, ARTEMIS must be used to test a man-rated integrated avionics hardware and software system, thus requiring a wide variety of nominal and off-nominal simulation capabilities to certify system robustness. The second driving requirement - derived from a nationwide review of current state-of-the-art HWIL facilities - was that preserving digital model fidelity significantly reduced overall vehicle lifecycle cost by reducing testing time for certification runs and increasing flight tempo through an expanded operational envelope. These two driving requirements necessitated the use of high-fidelity models throughout the ARTEMIS simulation. The nature of the Ares mission profile imposed a variety of additional requirements on the ARTEMIS simulation. The Ares I vehicle is composed of multiple elements, including the First Stage Solid Rocket Booster (SRB), the Upper Stage powered by the J- 2X engine, the Orion Crew Exploration Vehicle (CEV) which houses the crew, the Launch Abort System (LAS), and various secondary elements that separate from the vehicle. At launch, the integrated vehicle stack is composed of these stages, and throughout the mission, various elements separate from the integrated stack and tumble back towards the earth. ARTEMIS must be capable of simulating the integrated stack through the flight as well as propagating each individual element after separation. In addition, abort sequences can lead to other unique configurations of the integrated stack as the timing and sequence of the stage separations are altered.

Tobbe, Patrick↗

Lunar and Meteorite Sample Education Disk Program - Space Rocks for Classrooms, Museums, Science Centers, and Libraries

NASA is eager for students and the public to experience lunar Apollo samples and meteorites first hand. Lunar rocks and soil, embedded in Lucite disks, are available for educators to use in their classrooms, museums, science centers, and public libraries for education activities and display. The sample education disks are valuable tools for engaging students in the exploration of the Solar System. Scientific research conducted on the Apollo rocks reveals the early history of our Earth-Moon system and meteorites reveal much of the history of the early solar system. The rocks help educators make the connections to this ancient history of our planet and solar system and the basic processes accretion, differentiation, impact and volcanism. With these samples, educators in museums, science centers, libraries, and classrooms can help students and the public understand the key questions pursued by many NASA planetary missions. The Office of the Curator at Johnson Space Center is in the process of reorganizing and renewing the Lunar and Meteorite Sample Education Disk Program to increase reach, security and accountability. The new program expands the reach of these exciting extraterrestrial rocks through increased access to training and educator borrowing. One of the expanded opportunities is that trained certified educators from science centers, museums, and libraries may now borrow the extraterrestrial rock samples. Previously the loan program was only open to classroom educators so the expansion will increase the public access to the samples and allow educators to make the critical connections to the exciting exploration missions taking place in our solar system. Each Lunar Disk contains three lunar rocks and three regolith soils embedded in Lucite. The anorthosite sample is a part of the magma ocean formed on the surface of Moon in the early melting period, the basalt is part of the extensive lunar mare lava flows, and the breccias sample is an important example of the violent impact history of the Moon. The disks also include two regolith soils and orange glass from a pyroclastic deposit. Each Meteorite Disk contains two ordinary chondrites, one carbonaceous chondrite, one iron, one stony iron, and one achondrite. These samples will help educators share the early history of the solar system with students and the public. Educators may borrow either lunar or meteorite disks and the accompanying education materials through the Johnson Space Center Curatorial Office. In trainings provided by the NASA Aerospace Education Services Program specialists, educators certified to borrow the disk learn about education resources, the proper use of the samples, and the special security for care and shipping of the disks. The Lunar and Meteorite Sample Education Disk Program will take NASA exploration to more people. Getting Space Rocks out to the public and inspiring the public about new space exploration is the focus of the NASA disk loan program.

Allen, Jaclyn↗

Space Shuttle Day-of-Launch Trajectory Design and Verification

A top priority of any launch vehicle is to insert as much mass into the desired orbit as possible. This requirement must be traded against vehicle capability in terms of dynamic control, thermal constraints, and structural margins. The vehicle is certified to a specific structural envelope which will yield certain performance characteristics of mass to orbit. Some envelopes cannot be certified generically and must be checked with each mission design. The most sensitive envelopes require an assessment on the day-of-launch. To further minimize vehicle loads while maximizing vehicle performance, a day-of-launch trajectory can be designed. This design is optimized according to that day s wind and atmospheric conditions, which will increase the probability of launch. The day-of-launch trajectory verification is critical to the vehicle's safety. The Day-Of-Launch I-Load Uplink (DOLILU) is the process by which the Space Shuttle Program redesigns the vehicle steering commands to fit that day's environmental conditions and then rigorously verifies the integrated vehicle trajectory's loads, controls, and performance. The Shuttle methodology is very similar to other United States unmanned launch vehicles. By extension, this method would be similar to the methods employed for any future NASA launch vehicles. This presentation will provide an overview of the Shuttle's day-of-launch trajectory optimization and verification as an example of a more generic application of dayof- launch design and validation.

Harrington, Brian E.↗

Projection Operator: A Step Towards Certification of Adaptive Controllers

One of the major barriers to wider use of adaptive controllers in commercial aviation is the lack of appropriate certification procedures. In order to be certified by the Federal Aviation Administration (FAA), an aircraft controller is expected to meet a set of guidelines on functionality and reliability while not negatively impacting other systems or safety of aircraft operations. Due to their inherent time-variant and non-linear behavior, adaptive controllers cannot be certified via the metrics used for linear conventional controllers, such as gain and phase margin. Projection Operator is a robustness augmentation technique that bounds the output of a non-linear adaptive controller while conforming to the Lyapunov stability rules. It can also be used to limit the control authority of the adaptive component so that the said control authority can be arbitrarily close to that of a linear controller. In this paper we will present the results of applying the Projection Operator to a Model-Reference Adaptive Controller (MRAC), varying the amount of control authority, and comparing controller s performance and stability characteristics with those of a linear controller. We will also show how adjusting Projection Operator parameters can make it easier for the controller to satisfy the certification guidelines by enabling a tradeoff between controller s performance and robustness.

Larchev, Gregory V.↗

Generating Customized Verifiers for Automatically Generated Code

Program verification using Hoare-style techniques requires many logical annotations. We have previously developed a generic annotation inference algorithm that weaves in all annotations required to certify safety properties for automatically generated code. It uses patterns to capture generator- and property-specific code idioms and property-specific meta-program fragments to construct the annotations. The algorithm is customized by specifying the code patterns and integrating them with the meta-program fragments for annotation construction. However, this is difficult since it involves tedious and error-prone low-level term manipulations. Here, we describe an annotation schema compiler that largely automates this customization task using generative techniques. It takes a collection of high-level declarative annotation schemas tailored towards a specific code generator and safety property, and generates all customized analysis functions and glue code required for interfacing with the generic algorithm core, thus effectively creating a customized annotation inference algorithm. The compiler raises the level of abstraction and simplifies schema development and maintenance. It also takes care of some more routine aspects of formulating patterns and schemas, in particular handling of irrelevant program fragments and irrelevant variance in the program structure, which reduces the size, complexity, and number of different patterns and annotation schemas that are required. The improvements described here make it easier and faster to customize the system to a new safety property or a new generator, and we demonstrate this by customizing it to certify frame safety of space flight navigation code that was automatically generated from Simulink models by MathWorks' Real-Time Workshop.

Denney, Ewen↗

Space Shuttle Day-of-Launch Trajectory Design Operations

A top priority of any launch vehicle is to insert as much mass into the desired orbit as possible. This requirement must be traded against vehicle capability in terms of dynamic control, thermal constraints, and structural margins. The vehicle is certified to specific structural limits which will yield certain performance characteristics of mass to orbit. Some limits cannot be certified generically and must be checked with each mission design. The most sensitive limits require an assessment on the day-of-launch. To further minimize vehicle loads while maximizing vehicle performance, a day-of-launch trajectory can be designed. This design is optimized according to that day s wind and atmospheric conditions, which increase the probability of launch. The day-of-launch trajectory design and verification process is critical to the vehicle s safety. The Day-Of-Launch I-Load Update (DOLILU) is the process by which the National Aeronautics and Space Administration's (NASA) Space Shuttle Program tailors the vehicle steering commands to fit that day s environmental conditions and then rigorously verifies the integrated vehicle trajectory s loads, controls, and performance. This process has been successfully used for almost twenty years and shares many of the same elements with other launch vehicles that execute a day-of-launch trajectory design or day-of-launch trajectory verification. Weather balloon data is gathered at the launch site and transmitted to the Johnson Space Center s Mission Control. The vehicle s first stage trajectory is then adjusted to the measured wind and atmosphere data. The resultant trajectory must satisfy loads and controls constraints. Additionally, these assessments statistically protect for non-observed dispersions. One such dispersion is the change in the wind from the last measured balloon to launch time. This process is started in the hours before launch and is repeated several times as the launch count proceeds. Should the trajectory design not meet all constraint criteria, Shuttle would be No-Go for launch. This Shuttle methodology is very similar to other unmanned launch vehicles. By extension, this method would likely be employed for any future NASA launch vehicle. This paper will review the Shuttle s day-of-launch trajectory optimization and verification operations as an example of a more generic application of day-of-launch design and validation. With Shuttle s retirement, it is fitting to document the current state of this critical process and capture lessons learned to benefit current and future launch vehicle endeavors.

Harrington, Brian E.↗

NASA Musculoskeletal Space Medicine and Reconditioning Program

The Astronaut Strength, Conditioning, and Rehabilitation (ASCR) group is comprised of certified strength and conditioning coaches and licensed and certified athletic trainers. The ASCR group works within NASA s Space Medicine Division providing direction and supervision to the astronaut corp with regards to physical readiness throughout all phases of space flight. The ASCR group is overseen by flight surgeons with specialized training in sports medicine or physical medicine and rehabilitation. The goals of the ASCR group include 1) designing and administering strength and conditioning programs that maximize the potential for physical performance while minimizing the rate of injury, 2) providing appropriate injury management and rehabilitation services, 3) collaborating with medical, research, engineering, and mission operations groups to develop and implement safe and effective in-flight exercise countermeasures, and 4) providing a structured, individualized post-flight reconditioning program for long duration crew members. This Panel will present the current approach to the management of musculoskeletal injuries commonly seen within the astronaut corp and will present an overview of the pre-flight physical training, in-flight exercise countermeasures, and post-flight reconditioning program for ISS astronauts.

Kerstman, Eric↗

Use of Heritage Hardware on MPCV Exploration Flight Test One

Due to an aggressive schedule for the first orbital test flight of an unmanned Orion capsule, known as Exploration Flight Test One (EFT1), combined with severe programmatic funding constraints, an effort was made to identify heritage hardware, i.e., already existing, flight-certified components from previous manned space programs, which might be available for use on EFT1. With the end of the Space Shuttle Program, no current means exists to launch Multi Purpose Logistics Modules (MPLMs) to the International Space Station (ISS), and so the inventory of many flight-certified Shuttle and MPLM components are available for other purposes. Two of these items are the Shuttle Ground Support Equipment Heat Exchanger (GSE Hx) and the MPLM cabin Positive Pressure Relief Assembly (PPRA). In preparation for the utilization of these components by the Orion Program, analyses and testing of the hardware were performed. The PPRA had to be analyzed to determine its susceptibility to pyrotechnic shock, and vibration testing had to be performed, since those environments are predicted to be significantly more severe during an Orion mission than those the hardware was originally designed to accommodate. The GSE Hx had to be tested for performance with the Orion thermal working fluids, which are different from those used by the Space Shuttle. This paper summarizes the certification of the use of heritage hardware for EFT1.

Rains, George Edward↗

Use of Heritage Hardware on Orion MPCV Exploration Flight Test One

Due to an aggressive schedule for the first space flight of an unmanned Orion capsule, currently known as Exploration Flight Test One (EFT1), combined with severe programmatic funding constraints, an effort was made within the Orion Program to identify heritage hardware, i.e., already existing, flight-certified components from previous manned space programs, which might be available for use on EFT1. With the end of the Space Shuttle Program, no current means exists to launch Multi-Purpose Logistics Modules (MPLMs) to the International Space Station (ISS), and so the inventory of many flight-certified Shuttle and MPLM components are available for other purposes. Two of these items are the MPLM cabin Positive Pressure Relief Assembly (PPRA), and the Shuttle Ground Support Equipment Heat Exchanger (GSE HX). In preparation for the utilization of these components by the Orion Program, analyses and testing of the hardware were performed. The PPRA had to be analyzed to determine its susceptibility to pyrotechnic shock, and vibration testing had to be performed, since those environments are predicted to be more severe during an Orion mission than those the hardware was originally designed to accommodate. The GSE HX had to be tested for performance with the Orion thermal working fluids, which are different from those used by the Space Shuttle. This paper summarizes the activities required in order to utilize heritage hardware for EFT1.

Rains, George Edward↗

Characterization of Aerodynamic Interactions with the Mars Science Laboratory Reaction Control System Using Computation and Experiment

On August 5 , 2012, the Mars Science Laboratory (MSL) entry capsule successfully entered Mars' atmosphere and landed the Curiosity rover in Gale Crater. The capsule used a reaction control system (RCS) consisting of four pairs of hydrazine thrusters to fly a guided entry. The RCS provided bank control to fly along a flight path commanded by an onboard computer and also damped unwanted rates due to atmospheric disturbances and any dynamic instabilities of the capsule. A preliminary assessment of the MSL's flight data from entry showed that the capsule flew much as predicted. This paper will describe how the MSL aerodynamics team used engineering analyses, computational codes and wind tunnel testing in concert to develop the RCS system and certify it for flight. Over the course of MSL's development, the RCS configuration underwent a number of design iterations to accommodate mechanical constraints, aeroheating concerns and excessive aero/RCS interactions. A brief overview of the MSL RCS configuration design evolution is provided. Then, a brief description is presented of how the computational predictions of RCS jet interactions were validated. The primary work to certify that the RCS interactions were acceptable for flight was centered on validating computational predictions at hypersonic speeds. A comparison of computational fluid dynamics (CFD) predictions to wind tunnel force and moment data gathered in the NASA Langley 31-Inch Mach 10 Tunnel was the lynch pin to validating the CFD codes used to predict aero/RCS interactions. Using the CFD predictions and experimental data, an interaction model was developed for Monte Carlo analyses using 6-degree-of-freedom trajectory simulation. The interaction model used in the flight simulation is presented.

Schoenenberger, Mark↗

Design of Test Support Hardware for Advanced Space Suits

As a member of the Space Suit Assembly Development Engineering Team, I designed and built test equipment systems to support the development of the next generation of advanced space suits. During space suit testing it is critical to supply the subject with two functions: (1) cooling to remove metabolic heat, and (2) breathing air to pressurize the space suit. The objective of my first project was to design, build, and certify an improved Space Suit Cooling System for manned testing in a 1‐G environment. This design had to be portable and supply a minimum cooling rate of 2500 BTU/hr. The Space Suit Cooling System is a robust, portable system that supports very high metabolic rates. It has a highly adjustable cool rate and is equipped with digital instrumentation to monitor the flowrate and critical temperatures. It can supply a variable water temperature down to 34 deg., and it can generate a maximum water flowrate of 2.5 LPM. My next project was to design and build a Breathing Air System that was capable of supply facility air to subjects wearing the Z‐2 space suit. The system intakes 150 PSIG breathing air and regulates it to two operating pressures: 4.3 and 8.3 PSIG. It can also provide structural capabilities at 1.5x operating pressure: 6.6 and 13.2 PSIG, respectively. It has instrumentation to monitor flowrate, as well as inlet and outlet pressures. The system has a series of relief valves to fully protect itself in case of regulator failure. Both projects followed a similar design methodology. The first task was to perform research on existing concepts to develop a sufficient background knowledge. Then mathematical models were developed to size components and simulate system performance. Next, mechanical and electrical schematics were generated and presented at Design Reviews. After the systems were approved by the suit team, all the hardware components were specified and procured. The systems were then packaged, fabricated, and thoroughly tested. The next step was to certify the equipment for manned used, which included generating a Hazard Analysis and giving a presentation to the Test Readiness Review Board. Both of these test support systems will perform critical roles in the development of next‐generation space suits. They will used on a regular basis to test the NASA's new Z‐2 Space Suit. The Space Suit Cooling System is now the primary cooling system for all advanced suit tests.

Watters, Jeffrey A.↗

Salt Spray Test to Determine Galvanic Corrosion Levels of Electroless Nickel Connectors Mounted on an Aluminum Bracket

During preliminary vehicle design reviews, requests were made to change flight termination systems from an electroless nickel (EN) connector coating to a zinc-nickel (ZN) plating. The reason for these changes was due to a new NASA-STD-6012 corrosion requirement where connectors must meet the performance requirement of 168 hr of exposure to salt spray. The specification for class F connectors, MIL-DTL-38999, certifies the EN coating will meet a 48-hr salt spray test, whereas the ZN is certified to meet a 168-hr salt spray test. The ZN finish is a concern because Marshall Space Flight Center has no flight experience with ZN-finished connectors, and MSFC-STD-3012 indicates that zinc and zinc alloys should not be used. The purpose of this test was to run a 168-hr salt spray test to verify the electrical and mechanical integrity of the EN connectors and officially document the results. The salt spray test was conducted per ASTM B117 on several MIL-DTL-38999 flight-like connectors mounted to an aluminum 6061-T6 bracket that was alodined. The configuration, mounting techniques, electrical checks, and materials used were typical of flight and ground support equipment.

Rolin, T. D.↗