SEARCH · Engineering Papers
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.
This short course provides information on what systems engineering is and how the systems engineer guides requirements, interfaces with the discipline leads, and resolves technical issues. There are many system-wide issues that either impact or are impacted by the thermal subsystem. This course will introduce these issues and illustrate them with real life examples.
This paper discusses the detailed design of an XML databinding framework for aircraft engine simulation. The framework provides an object interface to access and use engine data. while at the same time preserving the meaning of the original data. The Language independent representation of engine component data enables users to move around XML data using HTTP through disparate networks. The application of this framework is demonstrated via a web-based turbofan propulsion system simulation using the World Wide Web (WWW). A Java Servlet based web component architecture is used for rendering XML engine data into HTML format and dealing with input events from the user, which allows users to interact with simulation data from a web browser. The simulation data can also be saved to a local disk for archiving or to restart the simulation at a later time.
A major subsystem aboard the Shuttle Orbiter, the Remote Manipulator System (RMS) provides the capability to deploy and retrieve free-flying satellites, support attached payload operations, and aid in crewmember rescue from a disabled vehicle should the requirement arise. The Remote Manipulator System consists of 15.3-m (50 ft) articulated booms, end effectors, operator workstation, and closed circuit video, power and control subsystems. The manipulator booms (or arms) and end effectors are located in the Orbiter payload bay and operated from inside the cabin by one crewmember. This paper is primarily concerned with the design and development of the RMS operator's workstation, the man-machine engineering features and interfaces, and man-in-the-loop simulations and testing results obtained to date by the National Aeronautics and Space Administration (NASA).
An inlet technology development program for future supersonic cruise aircraft is in progress. Areas being emphasized are inlet aerodynamic and control system design requirements for efficient and reliable operation. Off-design conditions, such as angle of incidence, starting, and noise abatement are major considerations. Flow analysis procedures are being developed to predict the internal inviscid and viscous flows in axisymmtric supersonic inlets for these operating conditions. Also under development are control systems that will have significant interfaces with the engine control system, the flight control system, and the airframe avionics system. The analytical methods are being supported and validated with representative experiments.
The functions that a space station could serve are outlined and details of the data systems requirements are discussed. The data system design will be guided by an overall space systems plan, and will feature distributed, layered architecture, user friendliness, hierarchical control, technology transparency, standard interfaces, and automated engineering tools. The station would begin with a limited core capability and evolve to serve functions defined thereafter. The automation of the engineering tools will be necessary to permit an optimized, minimized crew to control all functions of the space station, while at the same time freeing the crew from being actively involved in maintaining the nominal life support functions of the equipment. One major criterion is that the software must be error free, while another is adaptibility to changing space station configurations and demands.
In an overview of the Data Reduction System, three major steps are examined. First, the raw data tapes were selected from the onboard recorders. These tapes should provide the best quality data for the data reduction software system. These tapes contained 352 channels of data, plus the monitor channels recorded in 8 bit Pulsed Coded Modulation (PCM) words. The next step consists of transcribing the PCM tapes from 8 bit serial digital data to 8 bit parallel digital data. This puts the data in the correct format for processing. The transcription process was accomplished here at LaRC in the Central Data Transportation Facility (CDTF). The last step in this 3 step process is to process the data through the reduction system developed for the Impact Dynamic Research Facility in the early part of 1980. Processing system criteria, system interface routines, and engineering units program that reads digitized data from tapes, and file management programs are discussed.
A fielded expert system automates equipment fault isolation and recommends corrective maintenance action for Air Force jet engines. The knowledge based diagnostics tool was developed as an expert system interface to the Comprehensive Engine Management System, Increment IV (CEMS IV), the standard Air Force base level maintenance decision support system. XMAM (trademark), the Expert Maintenance Tool, automates procedures for troubleshooting equipment faults, provides a facility for interactive user training, and fits within a diagnostics information feedback loop to improve the troubleshooting and equipment maintenance processes. The application of expert diagnostics to the Air Force A-10A aircraft TF-34 engine equipped with the Turbine Engine Monitoring System (TEMS) is presented.
This paper focuses on the application of expert systems technology to the automatic detection, verification and correction of anomalous rocket engine operations through interfacing with an intelligent adaptive control system. The design of a reliable and intelligent propulsion control and monitoring system is outlined which includes the architecture of an Integrated Expert System (IES) serving as the core component. The IES functions include automatic knowledge acquisition, integrated knowledge base, and fault diagnosis and prediction methodology. The results of fault analysis and diagnostic techniques are presented for an example fault in the SSME main combustion chamber injectors.
The last two decades have witnessed a rapid growth in the introduction of automatic devices into aircraft cockpits, and eleswhere in human-machine systems. This was motivated in part by the assumption that when human functioning is replaced by machine functioning, human error is eliminated. Experience to date shows that this is far from true, and that automation does not replace humans, but changes their role in the system, as well as the types and severity of the errors they make. This altered role may lead to fewer, but more critical errors. Intervention strategies to prevent these errors, or ameliorate their consequences include basic human factors engineering of the interface, enhanced warning and alerting systems, and more intelligent interfaces that understand the strategic intent of the crew and can detect and trap inconsistent or erroneous input before it affects the system.
The Thermal Synthesizer System (TSS), which is being developed to meet the thermal analysis needs of Space Station Freedom and of the proposed Space Exploration Initiative missions, is examined. The key requirements and design goals to be met by TSS are summarized, and the software engineering and user interface design philosophy are reviewed. The basic architecture for all applications within TSS is described. An overview is given of the main features of each of the applications of TSS.
We describe the implementation of a large scale disk array controller and subsystem incorporating over 100 high performance 3.5 inch disk drives. It is designed to provide 40 MB/s sustained performance and 40 GB capacity in three 19 inch racks. The array controller forms an integral part of a file server that attaches to a Gb/s local area network. The controller implements a high bandwidth interconnect between an interleaved memory, an XOR calculation engine, the network interface (HIPPI), and the disk interfaces (SCSI). The system is now functionally operational, and we are tuning its performance. We review the design decisions, history, and lessons learned from this three year university implementation effort to construct a truly large scale system assembly.
Recent hardware development work at NASA's Marshall Space Flight Center creates and argument for the use of a holistic design approach as opposed to a piece part design approach. A piece part design approach being one where individual pieces are developed to their finished state having to meet certain interface and human engineering requirements without much consideration to the final product as a whole. A holistic design approach being one where the final product is evaluated early and frequently during the design process, and individual parts are developed with consideration to how they interact a whole,and how they interact with the user and environment. Examples from the development of the Materials Science Research Rack - 1 will illustrate: a design failure due to piece part design; a design save, due to a failure of piece part design, but saved by evaluating the design holistically; and a design success due to a holistic design approach.
As humans venture farther from earth for longer durations, it will become essential for those on the journey to have significant control over the scheduling of their own activities as well as the activities of their companion systems and robots. However, there are many reasons why the crew will not do all the scheduling; timelines will be the result of collaboration with ground personnel. Emerging technologies such as in-space message buses, delay-tolerant networks, and in-space internet will be the carriers on which the collaboration rides. Advances in scheduling technology, in the areas of task modeling, scheduling engines, and user interfaces will allow the crew to become virtual scheduling experts. New concepts of operations for producing the timeline will allow the crew and the ground support to collaborate while providing safeguards to ensure that the mission will be effectively accomplished without endangering the systems or personnel.
An 'open specification' for Space Project Mission Operations Control Architectures is under development in the Spacecraft Control Working Group of the American Institute for Aeronautics and Astro- nautics. This architecture identifies 5 basic elements incorporated in the design of similar operations systems: Data, System Management, Control Interface, Decision Support Engine, & Space Messaging Service.
As humans venture farther from Earth for longer durations, it will become essential for those on the journey to have significant control over the scheduling of their own activities as well as the activities of their companion systems and robots. However, the crew will not do all the scheduling; timelines will be the result of collaboration with ground personnel. Emerging technologies such as in-space message buses, delay-tolerant networks, and in-space internet will be the carriers on which the collaboration rides. Advances in scheduling technology, in the areas of task modeling, scheduling engines, and user interfaces will allow the crew to become virtual scheduling experts. New concepts of operations for producing the timeline will allow the crew and the ground support to collaborate while providing safeguards to ensure that the mission will be effectively accomplished without endangering the systems or personnel.
As humans venture farther from Earth for longer durations, it will become essential for those on the journey to have significant control over the scheduling of their own activities as well as the activities of their companion systems and robots. However, the crew will not do all the scheduling; timelines will be the result of collaboration with ground personnel. Emerging technologies such as in-space message buses, delay-tolerant networks, and in-space internet will be the carriers on which the collaboration rides. Advances in scheduling technology, in the areas of task modeling, scheduling engines, and user interfaces will allow the crew to become virtual scheduling experts. New concepts of operations for producing the timeline will allow the crew and the ground support to collaborate while providing safeguards to ensure that the mission will be effectively accomplished without endangering the systems or personnel.
Rocket engine testing is important throughout a program s life and is essential to the overall success of the program. Space Shuttle Main Engine (SSME) testing can be divided into three phases: development, certification, and operational. Development tests are conducted on the basic design and are used to develop safe start and shutdown transients and to demonstrate mainstage operation. This phase helps form the foundation of the program, demands navigation of a very steep learning curve, and yields results that shape the final engine design. Certification testing involves multiple engine samples and more aggressive test profiles that explore the boundaries of the engine to vehicle interface requirements. The hardware being tested may have evolved slightly from that in the development phase. Operational testing is conducted with mature hardware and includes acceptance testing of flight assets, resolving anomalies that occur in flight, continuing to expand the performance envelope, and implementing design upgrades. This paper will examine these phases of testing and their importance to the SSME program. Examples of tests conducted in each phase will also be presented.
In order to achieve the ambitious objectives of the Mars 2020 (M2020) mission, in particular the ability to autonomously traverse more challenging terrains more efficiently, new surface mobility software was developed for Enhanced Navigation (ENav). That decision was made early in the project, before most of the new surface flight software (FSW) existed, which created a need for a separate framework where the new navigation algorithms could be quickly prototyped and tested, before more realistic FSW-based testbeds became available. The JPL robotics team chose the Robot Operating System [1] (ROS) as the environment in which to test the new ENav algorithms. This made it possible to write the algorithms in the C language required by the FSW, so they could be directly ported over to the flight module later on, while leveraging all the C++ libraries and tools provided by ROS for simulation and testing. The ENav algorithms were developed as a separate C library, and stubs were used to replace any FSW-specific code, such as Event Reporting (EVRs) and data products (DPs). A ROS simulator was developed to generate a rich set of varied 3D terrains representative of the candidate Mars landing sites and simulate the physics of the rover motion, the point cloud perceived by the rover’s stereo vision system, and the new thinking-while-driving (TWD) navigation logic which directs the rover to drive autonomously to user-specified waypoints. To simulate the rover motion and perception, a ROS node was developed that uses a software library called HyperDrive Sim (HDSim), which is a wrapper for the Rover Sequencing and Visualization Program [2] (RSVP). That library provides roverterrain settling, realistic slip modelling, and camera rendering capability based on the rover’s NavCam machine vision models. To simulate the navigation logic, a ROS node was created that initializes and runs the ENav algorithms in a way that mimics the FSW execution, while also providing the capability to load and replay data products, including re-running the recorded inputs through the ENav algorithms for testing. An engineering Graphical User Interface (GUI) was also developed to visualize various elements, such as the rover pose during the drive, the simulated and perceived terrain, the selected local and global paths to the goal, the evaluated candidate paths and the reasons why they were rejected, the keep-in and keep-out zones (KIOZs), etc. Finally, an advanced Monte Carlo (MC) framework that can run many simulations in parallel on the Cloud and automatically generate reports that capture the key ENav performance metrics was developed to evaluate the system in a statisticallymeaningful way. This paper provides an overview of the ROSbased simulator used for testing the M2020 ENav algorithms.