Engineering PapersSearch

SEARCH · Engineering Papers

Results for “Engineering - Other instrumentation”

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 55 records · Page 3

Microscopic Measurement: Need for Nuclear Material Sample Specimen Characterization Capability

The Surveillance, Fabrication, and Off-Site Operations team at Lawrence Livermore National Laboratory is beginning an update to the nuclear material machining lab in Superblock. Plutonium and other nuclear materials tend to accelerate the aging process for equipment and machines that would otherwise be maintainable for long lives. They have their lifespans shortened from deteriorated seals, embrittled polymer components, accelerated corrosion, and damage to electronics from exposure to radioactive materials. The cost of installation of equipment into a glove box (GB) tends to outstrip the cost of the equipment itself. Due to the magnification of cost, the historical approach to equipment installs has been to purchase and install the highest-quality and most robust equipment available to maximize time between failures and updates. To make room for the installation of a new lathe, the inspection GB is being moved to a different location within the machining lab. As part of the overall effort, the equipment within the inspection GB is being revisited. Current measurement capabilities are antiquated and starting to become problematic due to age. Advances in metrology are sought for more comprehensive characterization of scientific samples. This document aims to identify several options for the replacement of current measurement equipment and identify a system for purchase and eventual installation. The intention is not to select the cheapest system, but rather to identify a system that best meets the needs of both the operators and principal investigators (PI). Following the convention of the SYSM-5620 Design Thinking and System Engineering, it was determined that a laser confocal measurement system from Keyence is the most suitable option for our programmatic need. Form factor, capability, and maintainability were considered. Along with stakeholder input, to ensure the best decision for the Nuclear Material Technology Program.

36 MATERIALS SCIENCE

The Mars Reconnaissance Orbiter mission operations: architecture and approach

The Mars Reconnaissance Orbiter (MRO) was launched on August 12, 2005 by an Atlas V launch vehicle from Cape Canaveral Air Force Station. MRO will carry a rich set of science instruments to Mars and provide global, regional survey, and targeted observations. In addition, a set of engineering instruments providing optical navigation, Ka band telecommunication and UHF relay services to future Mars missions are part of the MRO payload.

MRO

The Mars Reconnaissance Orbiter Mission Operations: Architecture and Approach

The Mars Reconnaissance Orbiter (MRO) was launched on August 12, 2005 by an Atlas V launch vehicle from Cape Canaveral Air Force Station. MRO will carry a rich set of science instruments to Mars and provide global, regional survey, and targeted observations. In addition, a set of engineering instruments providing optical navigation, Ka band telecommunication and UHF relay services to future Mars missions are part of the MRO payload. During the mission, the MRO operations teams are presented with two major challenges - unprecedented high data rate and data volumes, and complex science planning and resource sharing. MRO has the capability to communicate with earth at a maximum of six Megabits per second (> 50 times any previous Mars missions). With the current Deep Space Network (DSN) contact schedule of 19 eight-hour tracks per week, the baseline mission plan is for MRO to return 34 Terabits of raw science data during the two year primary science phase. Each of the science instruments has its unique requirements for global mapping, regional survey, and targeted observations. Some instruments prefer nadir-only observations, while others require off-nadir observations (especially for stereo viewing). The requirements from these Mars viewing instruments presented a significant challenge for the operations team to design the complex science planning and resource sharing/allocation process. This paper describes what MRO project is implementing to solve these challenges.

Mars Reconnaissance Orbiter (MRO)

Modeling of Highly Instrumented Honeywell Turbofan Engine Tested with Ice Crystal Ingestion in the NASA Propulsion System Laboratory

The Propulsion Systems Laboratory (PSL), an altitude test facility at NASA Glenn Research Center, has been used to test a highly instrumented turbine engine at simulated altitude operating conditions. This is a continuation of the PSL testing that successfully duplicated the icing events that were experienced in a previous engine (serial LF01) during flight through ice crystal clouds, which was the first turbofan engine tested in PSL. This second model of the ALF502R-5A serial number LF11 is a highly instrumented version of the previous engine. The PSL facility provides a continuous cloud of ice crystals with controlled characteristics of size and concentration, which are ingested by the engine during operation at simulated altitudes. Several of the previous operating points tested in the LF01 engine were duplicated to confirm repeatability in LF11. The instrumentation included video cameras to visually illustrate the accretion of ice in the low pressure compressor (LPC) exit guide vane region in order to confirm the ice accretion, which was suspected during the testing of the LF01. Traditional instrumentation included static pressure taps in the low pressure compressor inner and outer flow path walls, as well as total pressure and temperature rakes in the low pressure compressor region. The test data was utilized to determine the losses and blockages due to accretion in the exit guide vane region of the LPC. Multiple data points were analyzed with the Honeywell Customer Deck. A full engine roll back point was modeled with the Numerical Propulsion System Simulation (NPSS) code. The mean line compressor flow analysis code with ice crystal modeling was utilized to estimate the parameters that indicate the risk of accretion, as well as to estimate the degree of blockage and losses caused by accretion during a full engine roll back point. The analysis provided additional validation of the icing risk parameters within the LPC, as well as the creation of models for estimating the rates of blockage growth and losses.

Simulation

A simulation evaluation of the engine monitoring and control system display

The Engine Monitoring and Control System (E-MACS) display is a new concept for an engine instrument display, the purpose of which is to provide an enhanced means for a pilot to control and monitor aircraft engine performance. It provides graphically-presented information about performance capabilities, current performance, and engine component or subsystem operational conditions relative to nominal conditions. The concept was evaluated by sixteen pilot-subjects against a traditional, state-of-the-art electronic engine display format. The results of this evaluation showed a substantial pilot preference for the E-MACS display relative to the traditional display. The results of the failure detection portion of the evaluation showed a 100 percent detection rate for the E-MACS display relative to a 57 percent rate for the traditional display. From these results, it is concluded that by providing this type of information in the cockpit, a reduction in pilot workload and an enhanced ability for detecting degraded or off-nominal conditions is probable, thus leading to an increase in operational safety.

Abbott, Terence S.

A High-Fidelity Simulation of a Generic Commercial Aircraft Engine and Controller

A new high-fidelity simulation of a generic 40,000 lb thrust class commercial turbofan engine with a representative controller, known as CMAPSS40k, has been developed. Based on dynamic flight test data of a highly instrumented engine and previous engine simulations developed at NASA Glenn Research Center, this non-proprietary simulation was created especially for use in the development of new engine control strategies. C-MAPSS40k is a highly detailed, component-level engine model written in MATLAB/Simulink (The MathWorks, Inc.). Because the model is built in Simulink, users have the ability to use any of the MATLAB tools for analysis and control system design. The engine components are modeled in C-code, which is then compiled to allow faster-than-real-time execution. The engine controller is based on common industry architecture and techniques to produce realistic closed-loop transient responses while ensuring that no safety or operability limits are violated. A significant feature not found in other non-proprietary models is the inclusion of transient stall margin debits. These debits provide an accurate accounting of the compressor surge margin, which is critical in the design of an engine controller. This paper discusses the development, characteristics, and capabilities of the C-MAPSS40k simulation

May, Ryan D.

On-Orbit Performance of the Spitzer Space Telescope: Science Meets Engineering

The Spitzer Space Telescope operated for over 16 years in an Earth-trailing solar orbit, returning not only a wealth of scientific data but also, as a by-product, spacecraft and instrument engineering data that will be of interest to future mission planners. These data will be particularly useful because Spitzer operated in an environment essentially identical to that at the L2 LaGrange point, where many future astrophysics missions will operate. In particular, the radiative cooling demonstrated by Spitzer has been adopted by other infrared space missions, from JWST to SPHEREx. We aim to facilitate the utility of the Spitzer engineering data by collecting the more unique and potentially useful portions into a single, readily accessible publication. We avoid discussion of less unique systems, such as the telecom, flight software, and electronics systems, and do not address the innovations in mission and science operations that the Spitzer team initiated. These and other items of potential interest are addressed in references supplied in an appendix to this paper.

Spitzer

Monitoring harmful gases

Instruments are developed for monitoring presence of hydrazine and nitrogen dioxide in air. Nitrogen dioxide and hydrazine are highly toxic and explosive substances used in propellants for rocket engines. Instruments discussed are inexpensive and most useful for detecting above substances in concentrations as low as few parts per million.

Helms, W. R.

Engine systems analysis results of the Space Shuttle Main Engine redesigned powerhead initial engine level testing

Engineers regularly analyze SSME ground test and flight data with respect to engine systems performance. Recently, a redesigned SSME powerhead was introduced to engine-level testing in part to increase engine operational margins through optimization of the engine internal environment. This paper presents an overview of the MSFC personnel engine systems analysis results and conclusions reached from initial engine level testing of the redesigned powerhead, and further redesigns incorporated to eliminate accelerated main injector baffle and main combustion chamber hot gas wall degradation. The conclusions are drawn from instrumented engine ground test data and hardware integrity analysis reports and address initial engine test results with respect to the apparent design change effects on engine system and component operation.

Sander, Erik J.

Telemetry Metrics: Monitoring Data Quality in the Spacecraft Ground Data System

During the launch of Mars Odyssey, ground data system (GDS) engineers experienced a glitch in the ground data system that caused us to re-evaluate how we looked at spacecraft telemetry, particularly during the spacecraft development period and for critical spacecraft events in flight. Spacecraft telemetry told the subsystem and instrument engineers about the health and status of the spacecraft, but there was surprisingly little information about how well the ground data system was doing in getting information from the spacecraft to the engineers.The problem for the Mars Odyssey launch was with a single channel not updating as often as expected. Spacecraft engineers considered calling off the Launch but eventually decided that this particular channel did not provide information that was crucial for launch. It was only after the post launch acquisition of the Odyssey signal that ground data system engineers heard there had been a concern about the channel....

Mars

An inventory of aeronautical ground research facilities. Volume 2: Air breathing engine test facilities

The inventory covers free jet and direct connect altitude cells, sea level static thrust stands, sea level test cells with ram air, and propulsion wind tunnels. Free jet altitude cells and propulsion wind tunnels are used for evaluation of complete inlet-engine-exhaust nozzle propulsion systems under simulated flight conditions. These facilities are similar in principal of operation and differ primarily in test section concept. The propulsion wind tunnel provides a closed test section and restrains the flow around the test specimen while the free jet is allowed to expand freely. A chamber of large diameter about the free jet is provided in which desired operating pressure levels may be maintained. Sea level test cells with ram air provide controlled, conditioned air directly to the engine face for performance evaluation at low altitude flight conditions. Direct connect altitude cells provide a means of performance evaluation at simulated conditions of Mach number and altitude with air supplied to the flight altitude conditions. Sea level static thrust stands simply provide an instrumented engine mounting for measuring thrust at zero airspeed. While all of these facilities are used for integrated engine testing, a few provide engine component test capability.

Pirrello, C. J.

SIM-Lite Update

Discussion focus on: SIM-Lite Instrument Update - 6m baseline, 50cm, approximately 900M cost; Technology Update - Systematic errors and floor; SIM-Lite terrestrial planet discovery capability; Double blind multiple planet study summary; and the changing landscape of exoplanet science and the role of SIM-Lite. Slides include technology to flight component engineering; instrumental systematic errors; ultra deep search for Earth clones; double blind test, astrometric detection of Earths in multiplanet systems; the current era of exoplanet science and where SIM-Lite fits in; the next frontier and where SIM-Lite fits in, why SIM is unique in discovering Earths; imaging planet status is uncertain without masses and ages; SIM role in establishing how planetary systems form and evolve; and SIM probes of broad planet mass range around young stars.

exoplanets

JT15D simulated flight data evaluation

The noise characteristics of the JT15D turbofan engine was analyzed with the objectives of: (1) assessing the state-of-art ability to simulate flight acoustic data using test results acquired in wind tunnel and outdoor (turbulence controlled) environments; and (2) predicting the farfield noise directivity of the blade passage frequency (BPF) tonal components using results from rotor blade mounted dynamic pressure instrumentation. Engine rotor tip speeds at subsonic, transonic, and supersonic conditions were evaluated. The ability to simulate flight results was generally within 2-3 dB for both outdoor and wind tunnel acoustic results. Some differences did occur in the broadband noise level and in the multiple-pure-tone harmonics at supersonic tip speeds. The prediction of blade passage frequency tone directivity from dynamic pressure measurements was accomplished for the three tip speed conditions. Predictions were made of the random and periodic components of the tone directivity. The technique for estimating the random tone component used hot wire data to establish a correlation between dynamic pressure and turbulence intensity. This prediction overestimated the tone level by typically 10 dB with the greatest overestimates occurring at supersonic conditions.

Holm, R. G.

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)

Investigation of Flow Instabilities in the Inlet Ducts of DP-1C VTOL Aircraft

An investigation of flow instabilities in the inlet ducts of a two-engine vertical takeoff and landing aircraft DP-1C is described in this report. Recent tests revealed that the engines stall during run ups while the aircraft is operating on the ground. These pop stalls occurred at relatively low power levels, sometimes as low as 60 percent of the engine full speed. Inability to run the engines up to the full speed level is attributed to in-ground effects associated with hot gas ingestion. Such pop stalls were never experienced when the aircraft was tested on a elevated grid platform, which ensured that the aircraft was operating in out-of-the-ground-effect conditions. Based on available information on problems experienced with other vertical takeoff and landing aircraft designs, it was assumed that the engine stalls were caused by partial ingestion of hot gases streaming forward from the main exit nozzle under the aircraft inlets, which are very close to the ground. It was also suggested that the nose wheel undercarriage, located between the inlets, may generate vortices or an unstable wake causing intense mixing of hot exit gases with incoming inlet flow, which would enhance the hot gas ingestion. After running a short three-day series of tests with fully instrumented engine inlets, it is now believed the most probable reason for engine pop stalls are random ingestions of a vortex generated between the two streams moving in opposite directions: outbound hot gas stream from the main nozzle close to the ground and inbound inlet flow above. Originally, the vortex is in a horizontal plane. However, at a certain velocity ratio of these two streams, the vortex attaches either to the ground or the aircraft surface at one end and the other end is swallowed by one of the aircraft inlets. Once the vortex enters the inlet duct, a puff of hot air can be sucked through the vortex core into the engine, which causes a serious inlet flow field distortion followed by an engine stall. Once the engine stalls, the outflow from the inlet pushes the vortex away and the engine resumes normal operation. This hypothesis needs to be verified experimentally; e.g., by extensive smoke flow visualization ahead of the aircraft inlets.

Lepicovsky, Jan

History and Logic Model NASA Goddard Space Flight Center Instrument and Payload Systems Engineering Technical Performance Study

Historically, some NASA missions have exceeded schedule and cost commitments. Studies suggest technical performance is a contributor. The 1980 NASA Project Management Study concluded, "one of the most significant contributors to cost and schedule growth is inadequate definition of technical and management aspects of a program..." (as cited in GAO/NSIAD-93-97, p. 11). The 1991 NASA Roles and Missions Report identified a "need for increased emphasis on technological readiness and requirements on the front end of a program" (as cited in GAO/NSIAD-93-97, p. 11). The 1992 NASA Program Costs Report stated that NASA officials identified, among other things, "insufficient definition studies... [and] program redesigns and technical complexities" as reasons for cost and schedule overruns (GAO/NSAID-93-97, p. 11). The 2002 Task Force on Acquisition of National Security Space Programs found "requirements definition and control issues, unhealthy cost bias in proposal evaluation, widespread lack of budget reserves required to implement high risk programs on schedule, and an overall underappreciation of the importance of appropriately staffed and trained system engineering staff to manage the technologically demanding and unique aspects of space programs" (DoD, 2003, p.i.) In 2007, The NASA Office of the Chief Engineer chartered the NASA Instrument Capability Study (NICS) “to determine whether NASA instrument developers are facing challenges that impact the capability to design and build quality instruments or whether there are flaws in the acquisition strategy evidenced by schedule delays, cost overruns, and increased technical risk via design deficiencies. The... team was also chartered to determine if occurrences [are]... isolated cases or if there are generic issues... If the issues [are] found to be generic, the team [is] to offer solutions to recover such capability" (NICS Report, 2008, p. vi). The 2008 NICS Report, led by Goddard Space Flight Center (GSFC), identified challenges to instrument technical performance consistent with findings from previous reports. In 2017, the Instrument Project Division (IPD) Implementation Study was initiated to determine if there was a change in meeting schedule and cost commitments after implementing certain NICS recommendations. In 2018, the Instrument Technical Performance Study was initiated to determine the current state of Instrument Technical Performance in the GSFC Payload & Instrument Systems Engineering Branch. The purpose of the combined studies is to answer the question, "Is there a relationship between meeting NASA scientific instrument technical success and meeting schedule and cost commitments? If yes, what is the relationship?" References Department of Defense Office of the Under Secretary of Defense for Acquisition, Technology, and Logistics. (2003). The report of the defense science board/ air force scientific advisory board joint task force on acquisition of national security space programs. Washington DC. Government Accounting Office. (1992). NASA program costs: Space missions require substantially more funding than initially estimated. GAO/NSIAD-93-97. Washington DC. National Aeronautics and Space Administration, National Oceanic and Atmospheric Agency, Department of Defense. (2008). The NASA instrument capability study final report. NP-2008-11-058-GSFC. Washington DC.

Robbins, Geraldine