Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “builders”

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 577 records · Page 32

Process control and recovery in the Link Monitor and Control Operator Assistant

This paper describes our approach to providing process control and recovery functions in the Link Monitor and Control Operator Assistant (LMCOA). The focus of the LMCOA is to provide semi-automated monitor and control to support station operations in the Deep Space Network. The LMCOA will be demonstrated with precalibration operations for Very Long Baseline Interferometry on a 70-meter antenna. Precalibration, the task of setting up the equipment to support a communications link with a spacecraft, is a manual, time consuming and error-prone process. One problem with the current system is that it does not provide explicit feedback about the effects of control actions. The LMCOA uses a Temporal Dependency Network (TDN) to represent an end-to-end sequence of operational procedures and a Situation Manager (SM) module to provide process control, diagnosis, and recovery functions. The TDN is a directed network representing precedence, parallelism, precondition, and postcondition constraints. The SM maintains an internal model of the expected and actual states of the subsystems in order to determine if each control action executed successfully and to provide feedback to the user. The LMCOA is implemented on a NeXT workstation using Objective C, Interface Builder and the C Language Integrated Production System.

Lee, Lorrine↗

Simplified propeller design for low-powered airplanes

The object of this report is to furnish the designer and builder of small airplanes a simple system for designing the propeller and making the drawing. An empirical design method is used, based on tests of model propellers in a wind tunnel and full scale tests of propellers in flight.

Weick, Fred E↗

Meteore 63 commercial seaplane

Societe Provencale de Constructions Aeronautiques, builder of the "Meteore 63" has constructed a three engine (biplane) seaplane which has met conditions for a seaworthy certificate of the first class.

SEAPLANES - S P C A "METEORE" 63↗

Engines and propellers for powered gliders and light airplanes

The object of the present paper is to consider the interaction of engine, propeller, and airplane for the low-power range. The discussion is presented in a form so as to provide the engine builder with a basis in his selection in the type of engine required, a suitable selection being possible only in connection with considerations on the best possible propeller.

Gropp, H↗

Program For Systematic Documentation Of Tasks

Task Analysis Report Generation Tool (TARGET) computer program is graphical-interface software tool used to capture procedural knowledge and translate knowledge into hierarchical report. Designed to help programmer document expert's task, enabling programmer to build expert-system computer program that helps others perform task. Flexibility key element of design and of knowledge-acquisition session. Easy to use and tailored to accommodate users ranging from novice to experienced builder of expert systems. Written in C language.

Ortiz, Christopher John↗

GUIs in the MIDAS environment

MIDAS (Munich Image Data Analysis System) is the image processing system developed at ESO for astronomical data reduction. MIDAS is used for off-line data reduction at ESO and many astronomical institutes all over Europe. In addition to a set of general commands, enabling to process and analyze images, catalogs, graphics and tables, MIDAS includes specialized packages dedicated to astronomical applications or to specific ESO instruments. Several graphical interfaces are available in the MIDAS environment: XHelp provides an interactive help facility, and XLong and XEchelle enable data reduction of long-slip and echelle spectra. GUI builders facilitate the development of interfaces. All ESO interfaces comply to the ESO User Interfaces Common Conventions which secures an identical look and feel for telescope operations, data analysis, and archives.

Ballester, P.↗

Writing instrument interfaces with xf/tktcl

Tcl is an embedded control language written in C, running primarily under Unix and with an interpreted C look-and-feel. Tk is an X11 toolkit based on tcl. Xf is an application builder for tk. The entire package is public domain and available from sprite.berkeley.edu. This paper discusses the use of tk to develop a user interface for OSIRIS, an infrared camera/spectrograph now operational on the OSU Perkins 1.8m telescope. The good and bad features of the development process are described.

Henden, A. A.↗

Expanding the KATE toolbox

KATE (Knowledge-based Autonomous Test Engineer) is a model-based software system developed in the Artificial Intelligence Laboratory at the Kennedy Space Center for monitoring, fault detection, and control of launch vehicles and ground support systems. In order to bring KATE to the level of performance, functionality, and integratability needed for firing room applications, efforts are underway to implement KATE in the C++ programming language using an X-windows interface. Two programs which were designed and added to the collection of tools which comprise the KATE toolbox are described. The first tool, called the schematic viewer, gives the KATE user the capability to view digitized schematic drawings in the KATE environment. The second tool, called the model editor, gives the KATE model builder a tool for creating and editing knowledge base files. Design and implementation issues having to do with these two tools are discussed. It will be useful to anyone maintaining or extending either the schematic viewer or the model editor.

Thomas, Stan J.↗

A data distribution strategy for the 1990s (files are not enough)

Virtually all of the data distribution strategies being contemplated for the EOSDIS era revolve around the use of files. Most, if not all, mass storage technologies are based around the file model. However, files may be the wrong primary abstraction for supporting scientific users in the 1990s and beyond. Other abstractions more closely matching the respective scientific discipline of the end user may be more appropriate. JPL has built a unique multimission data distribution system based on a strategy of telemetry stream emulation to match the responsibilities of spacecraft team and ground data system operators supporting our nations suite of planetary probes. The current system, operational since 1989 and the launch of the Magellan spacecraft, is supporting over 200 users at 15 remote sites. This stream-oriented data distribution model can provide important lessons learned to builders of future data systems.

Tankenson, Mike↗

Interface issues for on-board propulsion systems

Integration issues associated with the use of new chemical and electric propulsion technologies are a primary concern to the user community. Experience indicates that integration impacts must be addressed to the satisfaction of both spacecraft builders and operators prior to the acceptance of new propulsion systems. The NASA Lewis Research Center (LeRC) conducts an aggressive program to develop and transfer new propulsion technologies and this includes a major effort to identify and address integration issues associated with their use. This paper provides an overview of integration issues followed by a brief description of the spacecraft integration program at LeRC.

Curran, Frank M.↗

New Developments and Research Findings: NASA Hydrazine Arcjets

In 1984, the market for commercial geosynchronous communications satellites (comsats) was expanding and there was strong competition between spacecraft builders for market share. The propellant required for the north-south stationkeeping (NSSK) function was a major mission limiter, and the small chemical and resistojet systems then in use were at or near their physical limits. Thus, conditions were right for the development of a high performance NSSK system, and after an extensive survey of both propulsion technologies and the aerospace community, the NASA program chose hydrazine arcjets for development. A joint government/industry development program ensued which culminated in the acceptance of arcjet technology. NASA efforts included fundamental feasibility assessments, hardware development and verification, and multiple efforts aimed at the demonstration of critical operational characteristics of arcjet systems. Throughout the program, constant contact with the user community was maintained to determine system requirements. Both contracted and cooperative programs with industry were supported. First generation, kW-class arcjets are now operational for NSSK on the Telstar 401 satellite launched in December of 1993 and are baselined for use on multiple future satellite series (Intelsat 8, AsiaSat, Echostar). Arcjet development efforts are now focusing on the development of both high performance (600 s), 2 kW thrusters for application on next generation comsats and low power (Pe approximately 0.5 kW) for a variety of applications on power limited satellites. This paper presents a review of the NASA's role in the development of hydrazine arcjets with a focus on approaches, lessons learned, and the future.

Curren, Francis M.↗

A software architecture for automating operations processes

The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible output through interactive on-screen graphics. The OEL has developed the software for building these process-oriented graphical user interface (GUI) shells. The OEL Shell development system (OEL Shell) is an extension of JPL's Widget Creation Library (WCL). The OEL Shell system can be used to easily build user interfaces for running complex processes, applications with extensive command-line interfaces, and tool-integration tasks. The interface shells display a logical process flow using arrows and box graphics. They also allow a user to select which output products are desired and which input sources are needed, eliminating the need to know which program and its associated command-line parameters must be executed in each case. The shells have also proved valuable for use as operations training tools because of the OEL Shell hypertext help environment. The OEL toolkit approach is guided by several principles, including the use of ASCII text file interfaces with a multimission format, Perl scripts for mission-specific adaptation code, and programs that include a simple command-line interface for batch mode processing. Projects can adapt the interface shells by simple changes to the resources configuration file. This approach has allowed the development of sophisticated, automated software systems that are easy, cheap, and fast to build. This paper will discuss our toolkit approach and the OEL Shell interface builder in the context of a real operations process example. The paper will discuss the design and implementation of a Ulysses toolkit for generating the mission sequence of events. The Sequence of Events Generation (SEG) system provides an adaptable multimission toolkit for producing a time-ordered listing and timeline display of spacecraft commands, state changes, and required ground activities.

Miller, Kevin J.↗

America's foremost early astronomer

The life of 18th century astronomer, craftsman, and partriot David Rittenhouse is detailed. As a craftsman, he distinguished himself as one of the foremost builders of clocks. He also built magnetic compasses and surveying instruments. The finest examples of his craftsmanship are considered two orreries, mechanical solar systems. In terms of astronomical observations, his best-known contribution was his observation of the transit of Venus in 1769. Rittenhouse constructed the first diffraction grating. Working as Treasurer of Pennsylvania throughout the Revolution, he became the first director of the Mint in 1792. Astronomical observations in later life included charting the position of Uranus after its discovery.

Rubincam, David Parry↗

Planetary and deep space requirements for photovoltaic solar arrays

In the past 25 years, the majority of interplanetary spacecraft have been powered by nuclear sources. However, as the emphasis on smaller, low cost missions gains momentum, the majority of missions now being planned will use photovoltaic solar arrays. This will present challenges to the solar array builders, inasmuch as planetary requirements usually differ from earth orbital requirements. In addition, these requirements often differ greatly, depending on the specific mission; for example, inner planets vs. outer planets, orbiters vs. flybys, spacecraft vs. landers, and so on. Also, the likelihood of electric propulsion missions will influence the requirements placed on solar array developers. The paper will discuss representative requirements for a range of planetary missions now in the planning stages. Insofar as inner planets are concerned, a Mercury orbiter is being studied with many special requirements. Solar arrays would be exposed to high temperatures and a potentially high radiation environment, and will need to be increasingly pointed off sun as the vehicle approaches Mercury. Identification and development of cell materials and arrays at high incidence angles will be critical to the design. Missions to the outer solar system that have been studied include a Galilean orbiter and a flight to the Kuiper belt. While onboard power requirements would be small (as low as 10 watts), the solar intensity will require relatively large array areas. As a result, such missions will demand extremely compact packaging and low mass structures to conform to launch vehicle constraints. In turn, the large are, low mass designs will impact allowable spacecraft loads. Inflatable array structures, with and without concentration, and multiband gap cells will be considered if available. In general, the highest efficiency cell technologies operable under low intensity, low temperature conditions are needed. Solar arrays will power missions requiring as little as approximately 100 watts, up to several kilowatts (at Earth) in the case of solar electric propulsion missions. Thus, mass and stowage volume minimization will be required over a range of array sizes. Concentrator designs, inflatable structures, and the combination of solar arrays with the telecommunications system have been proposed. Performance, launch vehicle constraints, an cost will be the principal parameters in the design trade space. Other special applications will also be discussed, including requirements relating to planetary landers and probes. In those cases, issues relating to shock loads on landing, operability in (possibly dusty) atmospheres, and extreme temperature cycles must be considered, in addition to performance, stowed volume, and costs.

Bankston, C. P.↗

Adaptation of a Control Center Development Environment for Industrial Process Control

In the control center, raw telemetry data is received for storage, display, and analysis. This raw data must be combined and manipulated in various ways by mathematical computations to facilitate analysis, provide diversified fault detection mechanisms, and enhance display readability. A development tool called the Graphical Computation Builder (GCB) has been implemented which provides flight controllers with the capability to implement computations for use in the control center. The GCB provides a language that contains both general programming constructs and language elements specifically tailored for the control center environment. The GCB concept allows staff who are not skilled in computer programming to author and maintain computer programs. The GCB user is isolated from the details of external subsystem interfaces and has access to high-level functions such as matrix operators, trigonometric functions, and unit conversion macros. The GCB provides a high level of feedback during computation development that improves upon the often cryptic errors produced by computer language compilers. An equivalent need can be identified in the industrial data acquisition and process control domain: that of an integrated graphical development tool tailored to the application to hide the operating system, computer language, and data acquisition interface details. The GCB features a modular design which makes it suitable for technology transfer without significant rework. Control center-specific language elements can be replaced by elements specific to industrial process control.

Killough, Ronnie L.↗

Wingless Flight: The Lifting Body Story

Wingless Flight tells the story of the most unusual flying machines ever flown, the lifting bodies. It is my story about my friends and colleagues who committed a significant part of their lives in the 1960s and 1970s to prove that the concept was a viable one for use in spacecraft of the future. This story, filled with drama and adventure, is about the twelve-year period from 1963 to 1975 in which eight different lifting-body configurations flew. It is appropriate for me to write the story, since I was the engineer who first presented the idea of flight-testing the concept to others at the NASA Flight Research Center. Over those twelve years, I experienced the story as it unfolded day by day at that remote NASA facility northeast of los Angeles in the bleak Mojave Desert. Benefits from this effort immediately influenced the design and operational concepts of the winged NASA Shuttle Orbiter. However, the full benefits would not be realized until the 1990s when new spacecraft such as the X-33 and X-38 would fully employ the lifting-body concept. A lifting body is basically a wingless vehicle that flies due to the lift generated by the shape of its fuselage. Although both a lifting reentry vehicle and a ballistic capsule had been considered as options during the early stages of NASA's space program, NASA initially opted to go with the capsule. A number of individuals were not content to close the book on the lifting-body concept. Researchers including Alfred Eggers at the NASA Ames Research Center conducted early wind-tunnel experiments, finding that half of a rounded nose-cone shape that was flat on top and rounded on the bottom could generate a lift-to-drag ratio of about 1.5 to 1. Eggers' preliminary design sketch later resembled the basic M2 lifting-body design. At the NASA Langley Research Center, other researchers toyed with their own lifting-body shapes. Meanwhile, some of us aircraft-oriented researchers at the, NASA Flight Research Center at Edwards Air Force Base (AFB) in California were experiencing our own fascination with the lifting-body concept. A model-aircraft builder and private pilot on my own time, I found the lifting-body idea intriguing. I built a model based on Eggers' design, tested it repeatedly, made modifications in its control and balance characteristics along the way, then eventually presented the concept to others at the Center, using a film of its flights that my wife, Donna and I had made with our 8-mm home camera.

Reed, R. Dale↗

NASA Scope and Subject Category Guide

This guide provides a simple, effective tool to assist aerospace information analysts and database builders in the high-level subject classification of technical materials. Each of the 76 subject categories comprising the classification scheme is presented with a description of category scope, a listing of subtopics, cross references, and an indication of particular areas of NASA interest. The guide also includes an index of nearly 3,000 specific research topics cross referenced to the subject categories. The portable document format (PDF) version of the guide contains links in the index from each input subject to its corresponding categories. In addition to subject classification, the guide can serve as an aid to searching databases that use the classification scheme, and is also an excellent selection guide for those involved in the acquisition of aerospace literature. The CD-ROM contains both HTML and PDF versions.

Source record↗

Planetary and Deep Space Requirements for Photovoltaic Solar Arrays

In the past 25 years, the majority of interplanetary spacecraft have been powered by nuclear sources. However, as the emphasis on smaller, low cost missions gains momentum, more deep space missions now being planned have baselined photovoltaic solar arrays due to the low power requirements (usually significantly less than 100 W) needed for engineering and science payloads. This will present challenges to the solar array builders, inasmuch as planetary requirements usually differ from earth orbital requirements. In addition, these requirements often differ greatly, depending on the specific mission; for example, inner planets vs. outer planets, orbiters vs. flybys, spacecraft vs. landers, and so on. Also, the likelihood of electric propulsion missions will influence the requirements placed on solar array developers. This paper will discuss representative requirements for a range of planetary and deep space science missions now in the planning stages. We have divided the requirements into three categories: Inner planets and the sun; outer planets (greater than 3 AU); and Mars, cometary, and asteroid landers and probes. Requirements for Mercury and Ganymede landers will be covered in the Inner and Outer Planets sections with their respective orbiters. We will also discuss special requirements associated with solar electric propulsion (SEP). New technology developments will be needed to meet the demanding environments presented by these future applications as many of the technologies envisioned have not yet been demonstrated. In addition, new technologies that will be needed reside not only in the photovoltaic solar array, but also in other spacecraft systems that are key to operating the spacecraft reliably with the photovoltaics.

Bankston, C. P.↗