SEARCH · Engineering Papers

Results for “System Operations”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,657 records · Page 92

All sources NASA NTRS DOE OSTI

NASA NTRS2007

Imaging Sensor Flight and Test Equipment Software

The Lightning Imaging Sensor (LIS) is one of the components onboard the Tropical Rainfall Measuring Mission (TRMM) satellite, and was designed to detect and locate lightning over the tropics. The LIS flight code was developed to run on a single onboard digital signal processor, and has operated the LIS instrument since 1997 when the TRMM satellite was launched. The software provides controller functions to the LIS Real-Time Event Processor (RTEP) and onboard heaters, collects the lightning event data from the RTEP, compresses and formats the data for downlink to the satellite, collects housekeeping data and formats the data for downlink to the satellite, provides command processing and interface to the spacecraft communications and data bus, and provides watchdog functions for error detection. The Special Test Equipment (STE) software was designed to operate specific test equipment used to support the LIS hardware through development, calibration, qualification, and integration with the TRMM spacecraft. The STE software provides the capability to control instrument activation, commanding (including both data formatting and user interfacing), data collection, decompression, and display and image simulation. The LIS STE code was developed for the DOS operating system in the C programming language. Because of the many unique data formats implemented by the flight instrument, the STE software was required to comprehend the same formats, and translate them for the test operator. The hardware interfaces to the LIS instrument using both commercial and custom computer boards, requiring that the STE code integrate this variety into a working system. In addition, the requirement to provide RTEP test capability dictated the need to provide simulations of background image data with short-duration lightning transients superimposed. This led to the development of unique code used to control the location, intensity, and variation above background for simulated lightning strikes at user-selected locations.

Freestone, Kathleen↗

NASA NTRS2012

Lunar Reconnaissance Orbiter (LRO) Command and Data Handling Flight Electronics Subsystem

A document describes a high-performance, modular, and state-of-the-art Command and Data Handling (C&DH) system developed for use on the Lunar Reconnaissance Orbiter (LRO) mission. This system implements a complete hardware C&DH subsystem in a single chassis enclosure that includes a processor card, 48 Gbytes of solid-state recorder memory, data buses including MIL-STD-1553B, custom RS-422, SpaceWire, analog collection, switched power services, and interfaces to the Ka-Band and S-Band RF communications systems. The C&DH team capitalized on extensive experience with hardware and software with PCI bus design, SpaceWire networking, Actel FPGA design, digital flight design techniques, and the use of VxWorks for the real-time operating system. The resulting hardware architecture was implemented to meet the LRO mission requirements. The C&DH comprises an enclosure, a backplane, a low-voltage power converter, a single-board computer, a communications interface board, four data storage boards, a housekeeping and digital input/output board, and an analog data acquisition board. The interfaces between the C&DH and the instruments and avionics are connected through a SpaceWire network, a MIL-STD-1553 bus, and a combination of synchronous and asynchronous serial data transfers over RS-422 and LVDS (low-voltage differential-signaling) electrical interfaces. The C&DH acts as the spacecraft data system with an instrument data manager providing all software and internal bus scheduling, ingestion of science data, distribution of commands, and performing science operations in real time.

Nguyen, Quang↗

NASA NTRS1976

DSS 14 operating noise temperature during Helios 1 near-sun tracking

When spacecraft are tracked near the line-of-sight of the sun, the ground antenna sidelobes see the solar noise. The solar noise increases the ground system operating noise temperature and degrades the downlink RF reception performance. At specific antenna azimuthal angles relative to the sun, noise peaks and nulls occur periodically throughout a day's tracking pass due to the quadripod support leg-generated sidelobes. This article documents this effect while tracking Helios 1, illustrates the time of the peaks, and compares the predicted time of the noise temperature peaks with the measured data.

Stelzried, C. T.↗

NASA NTRS1987

UNIX-based data management system for the Mobile Satellite Propagation Experiment (PiFEx)

A new method is presented for handling data resulting from Mobile Satellite propagation experiments such as the Pilot Field Experiment (PiFEx) conducted by JPL. This method uses the UNIX operating system and C programming language. The data management system is implemented on a VAX minicomputer. The system automatically divides the large data file housing data from various experiments under a predetermined format into various individual files containing data from each experiment. The system also has a number of programs written in C and FORTRAN languages to allow the researcher to obtain meaningful quantities from the data at hand.

Kantak, Anil V.↗

NASA NTRS1974

Apollo experience report: Command and service module electrical power distribution on subsystem

A review of the design philosophy and development of the Apollo command and service modules electrical power distribution subsystem, a brief history of the evolution of the total system, and some of the more significant components within the system are discussed. The electrical power distribution primarily consisted of individual control units, interconnecting units, and associated protective devices. Because each unit within the system operated more or less independently of other units, the discussion of the subsystem proceeds generally in descending order of complexity; the discussion begins with the total system, progresses to the individual units of the system, and concludes with the components within the units.

Munford, R. E.↗

NASA NTRS1974

Acoustic positioning for space processing experiments

An acoustic positioning system is described that is adaptable to a range of processing chambers and furnace systems. Operation at temperatures exceeding 1000 C is demonstrated in experiments involving the levitation of liquid and solid glass materials up to several ounces in weight. The system consists of a single source of sound that is beamed at a reflecting surface placed a distance away. Stable levitation is achieved at a succession of discrete energy minima contained throughout the volume between the reflector and the sound source. Several specimens can be handled at one time. Metal discs up to 3 inches in diameter can be levitated, solid spheres of dense material up to 0.75 inches diameter, and liquids can be freely suspended in l-g in the form of near-spherical droplets up to 0.25 inch diameter, or flattened liquid discs up to 0.6 inches diameter. Larger specimens may be handled by increasing the size of the sound source or by reducing the sound frequency.

Whymark, R. R.↗

NASA NTRS1975

A summary of ERTS-1 data collection system applications

Geographically, applications were made over nearly the entire area where direct readout could be accomplished using the data acquisition stations in the ERTS-1 system. The extreme areas included Iceland, the Canadian Arctic, Alaska, Hawaii and Central America. In the discipline sense the majority of applications were in the water resources area with other applications being formally and informally reported in meteorology, oceanography, volcano surveillance and forestry. Installation and maintenance of the data collection platforms, as is true with nearly all new systems, was not accomplished without difficulty. On the whole, however, it has gone well enough so that it is agreed that it is a system which is amenable to installation in a variety of physical situations and the installation is accomplished with an ease commensurate with eventual use in an operational system.

Salomonson, V. V.↗

NASA NTRS1978

Digital Fly-By-Wire Flight Control Validation Experience

The experience gained in digital fly-by-wire technology through a flight test program being conducted by the NASA Dryden Flight Research Center in an F-8C aircraft is described. The system requirements are outlined, along with the requirements for flight qualification. The system is described, including the hardware components, the aircraft installation, and the system operation. The flight qualification experience is emphasized. The qualification process included the theoretical validation of the basic design, laboratory testing of the hardware and software elements, systems level testing, and flight testing. The most productive testing was performed on an iron bird aircraft, which used the actual electronic and hydraulic hardware and a simulation of the F-8 characteristics to provide the flight environment. The iron bird was used for sensor and system redundancy management testing, failure modes and effects testing, and stress testing in many cases with the pilot in the loop. The flight test program confirmed the quality of the validation process by achieving 50 flights without a known undetected failure and with no false alarms.

Szalai, K. J.↗

NASA NTRS1979

NASA advanced communications systems analysis

The purpose of the paper is to investigate and study in-depth market and system analysis for improving satellite communications. The analyses fall into two categories: the broad, scoping efforts intended to screen potential candidates and studies to develop viable operational system configurations and identify critical technology elements. To illustrate the approach, the results of 30/20 GHz study efforts which have been under way in the past few years are reviewed in detail.

Ward, J. J.↗

NASA NTRS1985

Space Station crew workload - Station operations and customer accommodations

The features of the Space Station which permit crew members to utilize work time for payload operations are discussed. The user orientation, modular design, nonstressful flight regime, in space construction, on board control, automation and robotics, and maintenance and servicing of the Space Station are examined. The proposed crew size, skills, and functions as station operator and mission specialists are described. Mission objectives and crew functions, which include performing material processing, life science and astronomy experiments, satellite and payload equipment servicing, systems monitoring and control, maintenance and repair, Orbital Maneuvering Vehicle and Mobile Remote Manipulator System operations, on board planning, housekeeping, and health maintenance and recreation, are studied.

Shinkle, G. L.↗

NASA NTRS1987

Telepresence work station system definition study, part 2

This study effort has shown that the development of a space robotic servicing system is totally feasible. More importantly, many of the key elements of such a system are currently available as the result of previous and ongoing technical efforts. In many cases, decisions remain to be made concerning tradeoffs between options available to satisfy system technology requirements. The primary recommendation resulting from this study is for the development of a flight test bed system that could be used to establish a performance database to assist some of the necessary technical decisions described in the study package. A properly design flight test bed system would prove tremendously useful in terms of rapidly evaluating technology in a realistic setting and would be a great benefit in the development of the operational system.

Source record↗

NASA NTRS1989

Mars Rover and Sample Return Mission design

The current reference Mars Rover and Sample Return mission is described. Technical issues are outlined, including high-resolution image acquisition and reconstruction, approach navigation, ground and flight systems operational complexity, rover autonomy, autonomous rendezvous and docking in Mars orbit, aerocapture and aeromaneuver, estimating the probability of mission success, and end-to-end information system design. Focus is placed on lander hazard identification and avoidance, pinpoint landing guidance and control, Mars ascent vehicle guidance and control, planetary protection and quarantine, sample acquisition and preservation, project management and control, systems requirements and interface control, and costing. In addition, program issues such as international participation, fiscal constraints, and launch-vehicle availability are considered.

Kwok, Johnny H.↗

NASA NTRS1991

High performance computing system for flight simulation at NASA Langley

The computer architecture and components used in the NASA Langley Advanced Real-Time Simulation System (ARTSS) are briefly described and illustrated with diagrams and graphs. Particular attention is given to the advanced Convex C220 processing units, the UNIX-based operating system, the software interface to the fiber-optic-linked Computer Automated Measurement and Control system, configuration-management and real-time supervisor software, ARTSS hardware modifications, and the current implementation status. Simulation applications considered include the Transport Systems Research Vehicle, the Differential Maneuvering Simulator, the General Aviation Simulator, and the Visual Motion Simulator.

Cleveland, Jeff I., II↗

NASA NTRS1992

Design of an Ada expert system shell for the VHSIC avionic modular flight processor

The Embedded Computer System Expert System Shell (ES Shell) is an Ada-based expert system shell developed at the Avionics Laboratory for use on the VHSIC Avionic Modular Processor (VAMP) running under the Ada Avionics Real-Time Software (AARTS) Operating System. The ES Shell provides the interface between the expert system and the avionics environment, and controls execution of the expert system. Testing of the ES Shell in the Avionics Laboratory's Integrated Test Bed (ITB) has demonstrated its ability to control a non-deterministic software application executing on the VAMP's which can control the ITB's real-time closed-loop aircraft simulation. The results of these tests and the conclusions reached in the design and development of the ES Shell have played an important role in the formulation of the requirements for a production-quality expert system inference engine, an ingredient necessary for the successful use of expert systems on the VAMP embedded avionic flight processor.

Fanning, F. Jesse↗

NASA NTRS1996

Cricket: A Mapped, Persistent Object Store

This paper describes Cricket, a new database storage system that is intended to be used as a platform for design environments and persistent programming languages. Cricket uses the memory management primitives of the Mach operating system to provide the abstraction of a shared, transactional single-level store that can be directly accessed by user applications. In this paper, we present the design and motivation for Cricket. We also present some initial performance results which show that, for its intended applications, Cricket can provide better performance than a general-purpose database storage system.

Shekita, Eugene↗

NASA NTRS1999

Situation Awareness and Levels of Automation

During the first year of this project, a taxonomy of theoretical levels of automation (LOAs) was applied to the advanced commercial aircraft by categorizing actual modes of McDonald Douglas MD-11 autoflight system operation in terms of the taxonomy. As well, high LOAs included in the taxonomy (e.g., supervisory control) were modeled in the context of MD-11 autoflight systems through development of a virtual flight simulator. The flight simulator was an integration of a re-configurable simulator developed by the Georgia Institute Technology and new software prototypes of autoflight system modules found in the MD-11 cockpit. In addition to this work, a version of the Situation Awareness Global Assessment Technique (SAGAT) was developed for application to commercial piloting tasks. A software package was developed to deliver the SAGAT and was integrated with the virtual flight simulator.

Kaber, David B.↗

NASA NTRS2000

Developing CORBA-Based Distributed Scientific Applications from Legacy Fortran Programs

Recent progress in distributed object technology has enabled software applications to be developed and deployed easily such that objects or components can work together across the boundaries of the network, different operating systems, and different languages. A distributed object is not necessarily a complete application but rather a reusable, self-contained piece of software that co-operates with other objects in a plug-and-play fashion via a well-defined interface. The Common Object Request Broker Architecture (CORBA), a middleware standard defined by the Object Management Group (OMG), uses the Interface Definition Language (IDL) to specify such an interface for transparent communication between distributed objects. Since IDL can be mapped to any programming language, such as C++, Java, Smalltalk, etc., existing applications can be integrated into a new application and hence the tasks of code re-writing and software maintenance can be reduced. Many scientific applications in aerodynamics and solid mechanics are written in Fortran. Refitting these legacy Fortran codes with CORBA objects can increase the codes reusability. For example, scientists could link their scientific applications to vintage Fortran programs such as Partial Differential Equation(PDE) solvers in a plug-and-play fashion. Unfortunately, CORBA IDL to Fortran mapping has not been proposed and there seems to be no direct method of generating CORBA objects from Fortran without having to resort to manually writing C/C++ wrappers. In this paper, we present an efficient methodology to integrate Fortran legacy programs into a distributed object framework. Issues and strategies regarding the conversion and decomposition of Fortran codes into CORBA objects are discussed. The following diagram shows the conversion and decomposition mechanism we proposed. Our goal is to keep the Fortran codes unmodified. The conversion- aided tool takes the Fortran application program as input and helps programmers generate C/C++ header file and IDL file for wrapping the Fortran code. Programmers need to determine by themselves how to decompose the legacy application into several reusable components based on the cohesion and coupling factors among the functions and subroutines. However, programming effort still can be greatly reduced because function headings and types have been converted to C++ and IDL styles. Most Fortran applications use the COMMON block to facilitate the transfer of large amount of variables among several functions. The COMMON block plays the similar role of global variables used in C. In the CORBA-compliant programming environment, global variables can not be used to pass values between objects. One approach to dealing with this problem is to put the COMMON variables into the parameter list. We do not adopt this approach because it requires modification of the Fortran source code which violates our design consideration. Our approach is to extract the COMMON blocks and convert them into a structure-typed attribute in C++. Through attributes, each component can initialize the variables and return the computation result back to the client. We have tested successfully the proposed conversion methodology based on the f2c converter. Since f2c only translates Fortran to C, we still needed to edit the converted code to meet the C++ and IDL syntax. For example, C++/IDL requires a tag in the structure type, while C does not. In this paper, we identify the necessary changes to the f2c converter in order to directly generate the C++ header and the IDL file. Our future work is to add GUI interface to ease the decomposition task by simply dragging and dropping icons.

Sang, Janche↗

NASA NTRSDate not supplied

Development of Space Mission Integrated Operations Scenarios

Integrated Operations Scenarios (IOS) describe nominal operations planned for a space mission. Operational scenarios are key to an operations concept, as they help identify issues and drivers on the operations system. This paper covers the tools, processes, and inputs that feed into an IOS product, and how IOS iterations during a mission lifecycle can buy down operational risks. A case used for this paper is nominal operations for an initial crewed Artemis mission that includes cross-program sequence of tasks required to accomplish end to end functions from launch through transit, on-orbit operations, to safely return to Earth. An IOS product serves as a reference for discussions during requirements development, task and risk analyses, concept of operations development, and as foundation to prepare space mission flight plans.

integrated operations scenarios↗