Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “interface engineering”

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 325 records · Page 18

Engine/airframe interface dynamics experience

Problems of engine/drive system torsional stability, engine and output shaft critical speeds, and engine vibration at helicopter rotor order frequencies are discussed, and test data and analyses presented. Also presented is a rotor/drive system dynamics problem not directly related to the engine.

Fredrickson, C.↗

Advanced life support study

Summary reports on each of the eight tasks undertaken by this contract are given. Discussed here is an evaluation of a Closed Ecological Life Support System (CELSS), including modeling and analysis of Physical/Chemical Closed Loop Life Support (P/C CLLS); the Environmental Control and Life Support Systems (ECLSS) evolution - Intermodule Ventilation study; advanced technologies interface requirements relative to ECLSS; an ECLSS resupply analysis; the ECLSS module addition relocation systems engineering analysis; an ECLSS cost/benefit analysis to identify rack-level interface requirements of the alternate technologies evaluated in the ventilation study, with a comparison of these with the rack level interface requirements for the baseline technologies; advanced instrumentation - technology database enhancement; and a clean room survey and assessment of various ECLSS evaluation options for different growth scenarios.

Source record↗

Bioinspired Honeycomb Core Design: An Experimental Study of the Role of Corner Radius, Coping, and Interface

The honeybee’s nest has inspired the design of engineering honeycomb core that primarily abstract the hexagonal cell shape and exploit its mass minimizing properties to construct lightweight panels. This work explored three additional design features that are part of the natural honeybee comb but have not been traditionally considered as design features of interest in honeycomb design: the radius at the corner of each cell, the coping at the top of the cell walls, and the interface between cell arrays. These features were first characterized in natural honeycomb using optical and X-ray techniques, and then incorporated into honeycomb core design, and fabricated using an additive manufacturing process. The honeycomb cores were then tested in out-of-plane compression and bending, and since all three design features added mass to the overall structure, all metrics were examined per unit mass to assess performance gains. The study concluded that the addition of an interface increases specific flexural modulus but has little benefit in out-of-plane compression; coping radius positively impacts specific flexural strength; but that the corner radius has no significant effect in bending, and actually is slightly detrimental for out-of-plane compression testing.

honeycomb↗

MASCOT - MATLAB Stability and Control Toolbox

MASCOT software was created to provide the conceptual aircraft designer accurate predictions of air vehicle stability and control characteristics. The code takes as input mass property data in the form of an inertia tensor, aerodynamic loading data, and propulsion (i.e. thrust) loading data. Using fundamental non-linear equations of motion, MASCOT then calculates vehicle trim and static stability data for any desired flight condition. Common predefined flight conditions are included. The predefined flight conditions include six horizontal and six landing rotation conditions with varying options for engine out, crosswind and sideslip, plus three takeoff rotation conditions. Results are displayed through a unique graphical interface developed to provide stability and control information to the conceptual design engineers using a qualitative scale indicating whether the vehicle has acceptable, marginal, or unacceptable static stability characteristics. This software allows the user to prescribe the vehicle s CG location, mass, and inertia tensor so that any loading configuration between empty weight and maximum take-off weight can be analyzed. The required geometric and aerodynamic data as well as mass and inertia properties may be entered directly, passed through data files, or come from external programs such as Vehicle Sketch Pad (VSP). The current version of MASCOT has been tested with VSP used to compute the required data, which is then passed directly into the program. In VSP, the vehicle geometry is created and manipulated. The aerodynamic coefficients, stability and control derivatives, are calculated using VorLax, which is now available directly within VSP. MASCOT has been written exclusively using the technical computing language MATLAB . This innovation is able to bridge the gap between low-fidelity conceptual design and higher-fidelity stability and control analysis. This new tool enables the conceptual design engineer to include detailed static stability and trim constraints in the conceptual design loop. The unique graphical interface developed for this tool presents the stability data in a format that is understandable by the conceptual designer, yet also provides the detailed quantitative results if desired.

Kenny, Sean↗

Flow Matching Results of an MHD Energy Bypass System on a Supersonic Turbojet Engine Using the Numerical Propulsion System Simulation (NPSS) Environment

Flow matching has been successfully achieved for an MHD energy bypass system on a supersonic turbojet engine. The Numerical Propulsion System Simulation (NPSS) environment helped perform a thermodynamic cycle analysis to properly match the flows from an inlet employing a MHD energy bypass system (consisting of an MHD generator and MHD accelerator) on a supersonic turbojet engine. Working with various operating conditions (such as the applied magnetic field, MHD generator length and flow conductivity), interfacing studies were conducted between the MHD generator, the turbojet engine, and the MHD accelerator. This paper briefly describes the NPSS environment used in this analysis. This paper further describes the analysis of a supersonic turbojet engine with an MHD generator/accelerator energy bypass system. Results from this study have shown that using MHD energy bypass in the flow path of a supersonic turbojet engine increases the useful Mach number operating range from 0 to 3.0 Mach (not using MHD) to a range of 0 to 7.0 Mach with specific net thrust range of 740 N-s/kg (at ambient Mach = 3.25) to 70 N-s/kg (at ambient Mach = 7). These results were achieved with an applied magnetic field of 2.5 Tesla and conductivity levels in a range from 2 mhos/m (ambient Mach = 7) to 5.5 mhos/m (ambient Mach = 3.5) for an MHD generator length of 3 m.

Benyo, Theresa L.↗

A dish-Stirling solar-thermal power system

This paper presents results of a preliminary design/economic study of a first-generation point focusing distributed receiver solar-thermal electric system optimized for application to industrial and small community power plants at power levels up to 10 MWe. Power conversion is provided by small Stirling cycle engines mounted at the focus of paraboloidal solar concentrators. The output of multiple power modules (concentrator, receiver, engine, and electric generator) is collected by means of a conventional electrical system and interfaced with a utility grid. Based on the United Stirling P-75 engine, a 1 MWe system employing mass-produced components (100,000 modules/year) could produce electricity at costs competitive with those projected for electricity generated by more conventional means, e.g. with fossil fuels.

Pons, R. L.↗

MSLICE Science Activity Planner for the Mars Science Laboratory Mission

MSLICE (Mars Science Laboratory InterfaCE) is the tool used by scientists and engineers on the Mars Science Laboratory rover mission to visualize the data returned by the rover and collaboratively plan its activities. It enables users to efficiently and effectively search all mission data to find applicable products (e.g., images, targets, activity plans, sequences, etc.), view and plan the traverse of the rover in HiRISE (High Resolution Imaging Science Experiment) images, visualize data acquired by the rover, and develop, model, and validate the activities the rover will perform. MSLICE enables users to securely contribute to the mission s activity planning process from their home institutions using off-the-shelf laptop computers. This software has made use of several plug-ins (software components) developed for previous missions [e.g., Mars Exploration Rover (MER), Phoenix Mars Lander (PHX)] and other technology tasks. It has a simple, intuitive, and powerful search capability. For any given mission, there is a huge amount of data and associated metadata that is generated. To help users sort through this information, MSLICE s search interface is provided in a similar fashion as major Internet search engines. With regard to the HiRISE visualization of the rover s traverse, this view is a map of the mission that allows scientists to easily gauge where the rover has been and where it is likely to go. The map also provides the ability to correct or adjust the known position of the rover through the overlaying of images acquired from the rover on top of the HiRISE image. A user can then correct the rover s position by collocating the visible features in the overlays with the same features in the underlying HiRISE image. MSLICE users can also rapidly search all mission data for images that contain a point specified by the user in another image or panoramic mosaic. MSLICE allows the creation of targets, which provides a way for scientists to collaboratively name features on the surface of Mars. These targets can also be used to convey instrument-pointing information to the activity plan. The software allows users to develop a plan of what they would like the rover to accomplish for a given time period. When developing the plan, the user can input constraints between activities or groups of activities. MSLICE will enforce said constraints and ensure that all mission flight rules are satisfied.

Powell, Mark W.↗

Hardware interface for isolation of vibrations in flexible manipulators: Development and applications

NASA's Langley Research Center (LaRC) is addressing the problem of isolating the vibrations of the Shuttle remote manipulator system (RMS) from its end-effector and/or payload by modeling an RMS flat-floor simulator with a dynamic payload. Analysis of the model can lead to control techniques that will improve the speed, accuracy, and safety of the RMS in capturing satellites and eventually facilitate berthing with the space station. Rockwell International Corporation, also involved in vibration isolation, has developed a hardware interface unit to isolate the end-effector from the vibrations of an arm on a Shuttle robotic tile processing system (RTPS). To apply the RTPS isolation techniques to long-reach arms like the RMS, engineers have modeled the dynamics of the hardware interface unit with simulation software. By integrating the Rockwell interface model with the NASA LaRC RMS simulator model, investigators can study the use of a hardware interface to isolate dynamic payloads from the RMS. The interface unit uses both active and passive compliance and damping for vibration isolation. Thus equipped, the RMS could be used as a telemanipulator with control characteristics for capture and berthing operations. The hardware interface also has applications in industry.

Manouchehri, Davoud↗

Low-Cost, User-Friendly, Rapid Analysis of Dynamic Data System Established

An issue of primary importance to the development of new jet and certain other airbreathing combined-cycle powered aircraft is the advancement of airframe-integrated propulsion technologies. Namely, engine inlets and their systems and subsystems are required to capture, convert, and deliver the atmospheric airflow demanded by such engines across their operating envelope in a form that can be used to provide efficient, stable thrust. This must be done while also minimizing aircraft drag and weight. Revolutionary inlet designs aided by new technologies are needed to enable new missions. An unwanted byproduct of pursuing these inlet technologies is increased time-variant airflow distortion. Such distortions reduce propulsion system stability, performance, operability, and life. To countermand these limitations and fully evaluate the resulting configurations, best practices dictate that this distortion be experimentally measured at large scale and analyzed. The required measurements consist of those made by an array of high-response pressure transducers located in the flow field at the aerodynamic interface plane (AIP) between the inlet and engine. Although the acquisition of the necessary pitot-pressure time histories is relatively straight-forward, until recent years, the analysis has proved to be very time-consuming, tedious, and expensive. To transform the analysis of these data into a tractable and timely proposition, researchers at the NASA Glenn Research Center created and established the Rapid Analysis of Dynamic Data (RADD) system. The system provides complete, near real-time analysis of time-varying inlet airflow distortion datasets with report quality output. This fully digital approach employs Institute of Electrical and Electronics Engineers (IEEE) binary data file format standardization to establish data-acquisition-system-independent processing on low cost personal computers. Features include invalid instrumentation code-out, logging, and multiple replacement schemes as needed for each channel of instrumentation. The AIP pressure distribution can be interpolated to simulate measurements by alternate AIP probe arrays, if desired. In addition, the RADD system provides for the application of filters that can be used to focus the analysis on the frequency range of interest.

Arend, David J.↗

Principles to Products: Toward Realizing MOS 2.0

This is a report on the Operations Revitalization Initiative, part of the ongoing NASA-funded Advanced Multi-Mission Operations Systems (AMMOS) program. We are implementing products that significantly improve efficiency and effectiveness of Mission Operations Systems (MOS) for deep-space missions. We take a multi-mission approach, in keeping with our organization's charter to "provide multi-mission tools and services that enable mission customers to operate at a lower total cost to NASA." Focusing first on architectural fundamentals of the MOS, we review the effort's progress. In particular, we note the use of stakeholder interactions and consideration of past lessons learned to motivate a set of Principles that guide the evolution of the AMMOS. Thus guided, we have created essential patterns and connections (detailed in companion papers) that are explicitly modeled and support elaboration at multiple levels of detail (system, sub-system, element...) throughout a MOS. This architecture is realized in design and implementation products that provide lifecycle support to a Mission at the system and subsystem level. The products include adaptable multi-mission engineering documentation that describes essentials such as operational concepts and scenarios, requirements, interfaces and agreements, information models, and mission operations processes. Because we have adopted a model-based system engineering method, these documents and their contents are meaningfully related to one another and to the system model. This means they are both more rigorous and reusable (from mission to mission) than standard system engineering products. The use of models also enables detailed, early (e.g., formulation phase) insight into the impact of changes (e.g., to interfaces or to software) that is rigorous and complete, allowing better decisions on cost or technical trades. Finally, our work provides clear and rigorous specification of operations needs to software developers, further enabling significant gains in productivity.

AMMOS↗

Flight Software Dictionary Development for the Mars2020 Rover

The Mars2020 project, developed and operated by the Jet Propulsion Laboratory (JPL), successfully landed the Perseverance rover and its flying companion Ingenuity on the surface of Mars on February 18th 2021. Perseverance combines heritage and cutting-edge flight software and hardware to accomplish crucial mission requirements related to Martian surface sampling. The design, development, and operation of NASA’s large strategic science missions require the ability to communicate spacecraft capabilities to hundreds of engineers across multiple disciplines. The interaction between flight and ground software development, Verification and Validation (V&V), Assembly, Test, and Launch Operations (ATLO), and management each demand quick understanding of unique slices of information for each discipline. This information includes the current capabilities of the flight system as well as future capabilities and their status as they are developed and tested. Despite the fundamental and critical nature of this information, the flight software dictionaries used to track it are a stumbling block for many projects. These dictionaries provide the cornerstone for the interpretation of data sent from the spacecraft, allowing for quick comprehension by engineers on the ground. During both spacecraft development and operations, flight software dictionary management includes significant challenges due to the large number of interfacing systems and the subtle yet distinct needs of each.The engineering of flight software dictionaries for Mars2020 had numerous challenges, most-notably: parallel dictionary development to support simultaneous separate flight software build campaigns for each mission phase (cruise and surface), managing requests for operations-enabling information without perturbing the heritage interface with the rover, and the introduction of new tools by the dictionary stakeholders that forced the dictionary team to innovate and redesign the heritage tool chain. These challenges generated guiding principles for the dictionary development effort: emphasize coding best practices and unit testing in the dictionary code development tool chain, use institutionally provided COTS (commercial-off-the-shelf) tools whenever possible, and maintain the heritage flight-ground interface all while advancing operations-enabling information via a loosely coupled interface.Throughout development and operations, the Mars2020 dictionary toolchain included IBM DOORS Next Generation, GitHub, Microsoft Excel, Docker, Jenkins, and a significant custom-built Python codebase. Significant interfaces included JPL’s command and control software, heritage flight software team tools and processes, and the many cloud-based ground tools developed for the mission.This paper will discuss the requirements for the Mars2020 dictionary development, the development team’s response to those requirements, lessons learned throughout the process, steps taken towards automated deliveries and continuous integration of stakeholder inputs, potential toolchain improvements for Mars2020, and key takeaways that could be applied to future missions.

Pyrzak, Guy↗

Characterization of Side Load Phenomena Using Measurement of Fluid/Structure Interaction

During ground-tests of most production rocket engines over the last 30 years, large asymmetric transient side loads coming from the nozzle and related steady-state vibrational loads within the nozzle have been measured. The widely varying magnitude of these loads has been large enough to fail interfacing components as well as nozzles in these engines. This paper will discuss a comprehensive test and analysis program that has been undertaken to develop a methodology to accurately predict the character and magnitude of this loading. The project to-date has incorporated analytical modeling of both the fluid flow and the nozzle structure and testing of both full-scale and sub-scale rocket nodes. Examination of the test data indicates that one of the two-nodal diameter structural modes may be interacting with flow separation from the nozzle inside-wall in a self-excited or aeroelastic vibration phenomenon. If verified, this observation will be used to develop a methodology for design and analysis. A fuller understanding of the characteristics of this vibration will provide an increase in the accuracy and confidence of side load predictions, which will be critical for the successful construction of the next generation of low-cost, reliable rocket engines.

Brown, Andrew M.↗

User Interface Technology for Formal Specification Development

Formal specification development and modification are an essential component of the knowledge-based software life cycle. User interface technology is needed to empower end-users to create their own formal specifications. This paper describes the advanced user interface for AMPHION1 a knowledge-based software engineering system that targets scientific subroutine libraries. AMPHION is a generic, domain-independent architecture that is specialized to an application domain through a declarative domain theory. Formal specification development and reuse is made accessible to end-users through an intuitive graphical interface that provides semantic guidance in creating diagrams denoting formal specifications in an application domain. The diagrams also serve to document the specifications. Automatic deductive program synthesis ensures that end-user specifications are correctly implemented. The tables that drive AMPHION's user interface are automatically compiled from a domain theory; portions of the interface can be customized by the end-user. The user interface facilitates formal specification development by hiding syntactic details, such as logical notation. It also turns some of the barriers for end-user specification development associated with strongly typed formal languages into active sources of guidance, without restricting advanced users. The interface is especially suited for specification modification. AMPHION has been applied to the domain of solar system kinematics through the development of a declarative domain theory. Testing over six months with planetary scientists indicates that AMPHION's interactive specification acquisition paradigm enables users to develop, modify, and reuse specifications at least an order of magnitude more rapidly than manual program development.

Lowry, Michael↗

Digital Human Modeling

The development of models to represent human characteristics and behaviors in human factors is broad and general. The term "model" can refer to any metaphor to represent any aspect of the human; it is generally used in research to mean a mathematical tool for the simulation (often in software, which makes the simulation digital) of some aspect of human performance and for the prediction of future outcomes. This section is restricted to the application of human models in physical design, e.g., in human factors engineering. This design effort is typically human interface design, and the digital models used are anthropometric. That is, they are visual models that are the physical shape of humans and that have the capabilities and constraints of humans of a selected population. They are distinct from the avatars used in the entertainment industry (movies, video games, and the like) in precisely that regard: as models, they are created through the application of data on humans, and they are used to predict human response; body stresses workspaces. DHM enable iterative evaluation of a large number of concepts and support rapid analysis, as compared with use of physical mockups. They can be used to evaluate feasibility of escape of a suited astronaut from a damaged vehicle, before launch or after an abort (England, et al., 2012). Throughout most of human spaceflight, little attention has been paid to worksite design for ground workers. As a result of repeated damage to the Space Shuttle which adversely affected flight safety, DHM analyses of ground assembly and maintenance have been developed over the last five years for the design of new flight systems (Stambolian, 2012, Dischinger and Dunn Jackson, 2014). The intent of these analyses is to assure the design supports the work of the ground crew personnel and thereby protect the launch vehicle. They help the analyst address basic human factors engineering questions: can a worker reach the task site from the work platform provided; can she or he see the task site; can she or he control tools, which, if dropped, might damage the system? Figure 7.3.1 provides an example of such analysis for a future NASA launch vehicle. [figure 7.3.1 here] In-space systems for operation by astronauts have long been targets for DHM analysis, given the focus on mission success and concerns for astronaut safety. Figure 7.3.2 illustrates the analysis of the design to support astronaut tasks for an International Space Station glovebox. [Figure 7.3.2 here] Use by

Dischinger, H. Charles, Jr.↗

CAIDA CUI Confirmation for OMRS & LCC SOCRRATES Emulator and iSEE Upgrade, Operations, & Analysis

This internship has focused on providing solutions for the Customer Avionics Interface Development and Analysis (CAIDA) subsystem. The main emulator that has been used during this internship is the Software-Only CEV (Crew Exploration Vehicle) Risk Reduction Analysis and Test Engineering Simulator (SOCRRATES). This emulator uses advanced math and physics methods to simulate specific points in a mission, such as ascent, entry, and orbit. Exploration Ground Systems (EGS) must ensure that all KSC based ground systems can be properly integrated with the flight vehicle software, therefore, the Modeling and Simulation Branch (NE-XM) of the KSC (Kennedy Space Center) Engineering Directorate supports a virtual environment that simulates the interface between ground systems and the flight vehicle. A primary component in assuring that is knowing whether the emulators have incorporated the correct CUIs (Compact Unique Identifiers) into their system, as well as understanding both the static and dynamic responses of the individual CUIs. Also, an effort for verification of Operational Maintenance Requirements Specifications (OMRS) and Launch Commit Criteria (LCC) that are supported by SOCRRATES for the Orion Crew Module were part of the project tasks this semester. This internship also focused on comparing two different simulation Commercial-off-the-shelf (COTS) products and to determine whether or not a COTS package was a viable replacement for the current software that the iSEE (Immersive Simulations and Engineering Environment) lab uses. Upon research and testing, I found that this software was not feasible for the lab. It could not easily load CAD (Computer-Aided Design) or CREO models, give live feedback while the user is in the environment, and was not compatible with a virtual reality headset, all of which are necessary for the lab.

Bundy, Caleb↗

Systems engineering for very large systems

Very large integrated systems have always posed special problems for engineers. Whether they are power generation systems, computer networks or space vehicles, whenever there are multiple interfaces, complex technologies or just demanding customers, the challenges are unique. 'Systems engineering' has evolved as a discipline in order to meet these challenges by providing a structured, top-down design and development methodology for the engineer. This paper attempts to define the general class of problems requiring the complete systems engineering treatment and to show how systems engineering can be utilized to improve customer satisfaction and profit ability. Specifically, this work will focus on a design methodology for the largest of systems, not necessarily in terms of physical size, but in terms of complexity and interconnectivity.

Lewkowicz, Paul E.↗

Systems Engineering Tutorial with Case Studies

Due to the ever-growing number of complex technical problems facing our world, a Systems Engineering approach is needed to assist in successful design, build and implementation of solutions. The interdisciplinary technical structure of current systems, technical processes representing System Design, Technical Management and Product Realization are instrumental in the development and integration of new technologies into mainstream applications. This tutorial will demonstrate the application of Systems Engineering tools to these types of problems. Learning objectives include, understanding how to develop and engineer a conceptual system; understand the importance of teams, communication, requirements definition, interface control, and focus on deliverables; useful tools and techniques for each aspect of the System Engineering process including Model Based Systems Engineering which will be touched upon lightly. Some hands-on problems will be pursued especially in requirements development which is always key to a successful project. Case studies will be presented to assist in the learning process.

Systems Engineering↗

Shuttle LOX loading transient study. Task 2 milestone report. National space and technology laboratories (NSTL) LOX loading facility analysis

Transient thermodynamic analyses were made of the LOX loading system proposed for the space shuttle main propulsion test article (MPTA). This system is made up of a LOX replenish system and a main LOX line which include the barge tank, the lines, pumps, and valves between the barge and the orbiter (ORB) ground service equipment (GSE) interface, the MPTA fill system, the space shuttle main engine (SSME) chilldown bleed system, and the GSE vent system. System analyses include predictions of system performance sensitivity to operating sequence and LOX flowrate, temperature, and quality at the ORB/GSE interface. The transient thermodynamic conditions at the SSME feed line entrance, ET entrance (tank bottom), and the SSME bleed/GSE vent TEE are also included. The analyses are based on continuous SSME bleed flow during GSE facility chilldown.

Glasgow, V. L.↗