Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “command process”

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 271 records · Page 15

Combining and connecting linear, multi-input, multi-output subsystem models

The mathematical background for combining and connecting linear, multi-input, multi-output subsystem models into an overall system model is provided. Several examples of subsystem configurations are examined in detail. A description of a MATRIX (sub x) command file to aid in the process of combining and connecting these subsystem models is contained.

Duke, E. L.↗

Sequencing Voyager II for the Uranus encounter

The process of developing the programmed sequence of events necessary for the Voyager 2 spacecraft to return desired data from its Uranus encounter is discussed. The major steps in the sequence process are reviewed, and the elements of the Mission Sequence Software are described. The design phase and the implementation phase of the sequence process are discussed, and the Computer Command Subsystem architecture is examined in detail. The software's role in constructing the sequences and converting them into onboard programs is elucidated, and the problems unique to the Uranus encounter sequences are considered.

Morris, R. B.↗

Definition of common support equipment and space station interface requirements for IOC model technology experiments

A study was conducted to identify the common support equipment and Space Station interface requirements for the IOC (initial operating capabilities) model technology experiments. In particular, each principal investigator for the proposed model technology experiment was contacted and visited for technical understanding and support for the generation of the detailed technical backup data required for completion of this study. Based on the data generated, a strong case can be made for a dedicated technology experiment command and control work station consisting of a command keyboard, cathode ray tube, data processing and storage, and an alert/annunciator panel located in the pressurized laboratory.

Russell, Richard A.↗

Determining robot actions for tasks requiring sensor interaction

The performance of non-trivial tasks by a mobile robot has been a long term objective of robotic research. One of the major stumbling blocks to this goal is the conversion of the high-level planning goals and commands into the actuator and sensor processing controls. In order for a mobile robot to accomplish a non-trivial task, the task must be described in terms of primitive actions of the robot's actuators. Most non-trivial tasks require the robot to interact with its environment; thus necessitating coordination of sensor processing and actuator control to accomplish the task. The main contention is that the transformation from the high level description of the task to the primitive actions should be performed primarily at execution time, when knowledge about the environment can be obtained through sensors. It is proposed to produce the detailed plan of primitive actions by using a collection of low-level planning components that contain domain specific knowledge and knowledge about the available sensors, actuators, and sensor/actuator processing. This collection will perform signal and control processing as well as serve as a control interface between an actual mobile robot and a high-level planning system. Previous research has shown the usefulness of high-level planning systems to plan the coordination of activities such to achieve a goal, but none have been fully applied to actual mobile robots due to the complexity of interacting with sensors and actuators. This control interface is currently being implemented on a LABMATE mobile robot connected to a SUN workstation and will be developed such to enable the LABMATE to perform non-trivial, sensor-intensive tasks as specified by a planning system.

Budenske, John↗

Adaptive truss structure

This paper discusses the research in adaptive structures conducted at NASA Langley Research Center. The objective in the research program on adaptive truss structures is to develop an integrated approach for the design, test, and evaluation of adaptive trusses. An adaptive structure must include sensors for measuring some of the states of the mechanism, a controller that processes the sensor information and generates command signals, and a device that will cause the struts in the mechanism to change length. Based on the results of the research program, it is concluded that alternative designs for future space applications are offered, and adaptive truss has been demonstrated to be effective for vibration suppression.

Horner, C. G.↗

Preparing the DSN operations concepts

Operations concepts are prepared to support a specific application and can, therefore, be classified accordingly. Studies of NASA and military operations concepts suggest three major types: data services, customer services, and systems oriented. Data services concepts concentrate on data types (e.g., telemetry and command) and how these data are processed and delivered to the user. Such concepts are normally used by data-processing centers to describe data-coding schemes and data formats. Customer services concepts concentrate on the customers' requirements and describe how these requirements are met using the systems available to the operation. Project centers use such concepts to describe the various types of data as they flow from the source (e.g., a spacecraft) to the end user (i.e., the customer). Systems oriented concepts concentrate on the use of systems for processing and delivering customer data. This paper examines the latter type and the 'concepts' that are inherent within them.

Salazar, A. J.↗

Control Software

Real-Time Innovations, Inc. (RTI) collaborated with Ames Research Center, the Jet Propulsion Laboratory and Stanford University to leverage NASA research to produce ControlShell software. RTI is the first "graduate" of Ames Research Center's Technology Commercialization Center. The ControlShell system was used extensively on a cooperative project to enhance the capabilities of a Russian-built Marsokhod rover being evaluated for eventual flight to Mars. RTI's ControlShell is complex, real-time command and control software, capable of processing information and controlling mechanical devices. One ControlShell tool is StethoScope. As a real-time data collection and display tool, StethoScope allows a user to see how a program is running without changing its execution. RTI has successfully applied its software savvy in other arenas, such as telecommunications, networking, video editing, semiconductor manufacturing, automobile systems, and medical imaging.

Source record↗

Space-based Science Operations Grid Prototype

Grid technology is the up and coming technology that is enabling widely disparate services to be offered to users that is very economical, easy to use and not available on a wide basis. Under the Grid concept disparate organizations generally defined as "virtual organizations" can share services i.e. sharing discipline specific computer applications, required to accomplish the specific scientific and engineering organizational goals and objectives. Grids are emerging as the new technology of the future. Grid technology has been enabled by the evolution of increasingly high speed networking. Without the evolution of high speed networking Grid technology would not have emerged. NASA/Marshall Space Flight Center's (MSFC) Flight Projects Directorate, Ground Systems Department is developing a Space-based Science Operations Grid prototype to provide to scientists and engineers the tools necessary to operate space-based science payloads/experiments and for scientists to conduct public and educational outreach. In addition Grid technology can provide new services not currently available to users. These services include mission voice and video, application sharing, telemetry management and display, payload and experiment commanding, data mining, high order data processing, discipline specific application sharing and data storage, all from a single grid portal. The Prototype will provide most of these services in a first step demonstration of integrated Grid and space-based science operations technologies. It will initially be based on the International Space Station science operational services located at the Payload Operations Integration Center at MSFC, but can be applied to many NASA projects including free flying satellites and future projects. The Prototype will use the Internet2 Abilene Research and Education Network that is currently a 10 Gb backbone network to reach the University of Alabama at Huntsville and several other, as yet unidentified, Space Station based science experimenters. There is an international aspect to the Grid involving the America's Pathway (AMPath) network, the Chilean REUNA Research and Education Network and the University of Chile in Santiago that will further demonstrate how extensive these services can be used. From the user's perspective, the Prototype will provide a single interface and logon to these varied services without the complexity of knowing the where's and how's of each service. There is a separate and deliberate emphasis on security. Security will be addressed by specifically outlining the different approaches and tools used. Grid technology, unlike the Internet, is being designed with security in mind. In addition we will show the locations, configurations and network paths associated with each service and virtual organization. We will discuss the separate virtual organizations that we define for the varied user communities. These will include certain, as yet undetermined, space-based science functions and/or processes and will include specific virtual organizations required for public and educational outreach and science and engineering collaboration. We will also discuss the Grid Prototype performance and the potential for further Grid applications both space-based and ground based projects and processes. In this paper and presentation we will detail each service and how they are integrated using Grid

Bradford, Robert N.↗

Modeling the Scheduling of Eye Movements and Manual Responses in Performing a Sequence of Discrete Tasks

Common tasks in daily life are often accomplished by a sequence of actions that interleave information acquisition through the eyes and action execution by the hands. How are eye movements coordinated with the release of manual responses and how may their coordination be represented at the level of component mental operations? We have previously presented data from a typing-like task requiring separate choice responses to a series of five stimuli. We found a consistent pattern of results in both motor and ocular timing, and hypothesized possible relationships among underlying components. Here we report a model of that task, which demonstrates how the observed timing of eye movements to successive stimuli could be accounted for by assuming systems: an open-loop system generating saccades at a periodic rate, and a closed-loop system commanding a saccade based on stimulus processing. We relate this model to models of reading and discuss the motivation for dual control.

Wu, Shu-Chieh↗

Focal Plane Alignment Utilizing Optical CMM

In many applications, an optical detector has to be located relative to mechanical reference points. One solution is to specify stringent requirements on (1) mounting the optical detector relative to the chip carrier, (2) soldering the chip carrier onto the printed circuit board (PCB), and (3) installing the PCB to the mechanical structure of the subsystem. Figure 1 shows a sketch of an optical detector mounted relative to mechanical reference with high positional accuracy. The optical detector is typically a fragile wafer that cannot be physically touched by any measurement tool. An optical coordinate measuring machine (CMM) can be used to position optical detectors relative to mechanical reference points. This approach will eliminate all requirements on positional tolerances. The only requirement is that the PCB is manufactured with oversized holes. An exaggerated sketch of this situation is shown in Figure 2. The sketch shows very loose tolerances on mounting the optical detector in the chip carrier, loose tolerance on soldering the chip carrier to the PCB, and finally large tolerance on where the mounting screws are located. The PCB is held with large screws and oversized holes. The PCB is mounted loosely so it can move freely around. The optical CMM measures the mechanical reference points. Based on these measurements, the required positions of the optical detector corners can be calculated. The optical CMM is commanded to go to the position where one detector corner is supposed to be. This is indicated with the cross-hairs in Figure 2(a). This figure is representative of the image of the optical CMM monitor. Using a suitable tapping tool, the PCB is manually tapped around until the corner of the optical detector is at the crosshairs of the optical CMM. The CMM is commanded to another corner, and the process is repeated a number of times until all corners of the optical detector are within a distance of 10 to 30 microns of the required position. The situation is sketched in Figure 2(b) (the figure also shows the tapping tool and where to tap). At this point the fasteners for the PCB are torqued slightly so the PCB can still move. The PCB location is adjusted again with the tapping tool. This process is repeated 3 to 4 times until the final torque is achieved. The oversized mounting holes are then filled with a liquid bonding agent to secure the board in position (not shown in the sketch). A 10- to 30-micron mounting accuracy has been achieved utilizing this method..

Liebe, Carl Christian↗

Command and Control Software Development

The future of the National Aeronautics and Space Administration (NASA) depends on its innovation and efficiency in the coming years. With ambitious goals to reach Mars and explore the vast universe, correct steps must be taken to ensure our space program reaches its destination safely. The interns in the Exploration Systems and Operations Division at the Kennedy Space Center (KSC) have been tasked with building command line tools to ease the process of managing and testing the data being produced by the ground control systems while its recording system is not in use. While working alongside full-time engineers, we were able to create multiple programs that reduce the cost and time it takes to test the subsystems that launch rockets to outer space.

Wallace, Michael↗

Development of an Optical Slice for an RF and Optical Software Defined Radio

A key component in the Integrated Radio and Optical Communications project at the National Aeronautics and Space Administration's (NASA) Glenn Research Center (GRC) is the radio frequency (RF) and optical software defined radio (SDR). A NASA RF SDR might consist of a general purpose processor to run the Space Telecommunications Radio System (STRS) Architecture for radio command and control, a reconfigurable signal processing device such as a field programmable gate array (FPGA) which houses the waveform, and a digital to analog converter for (DAC) transmitting data. Prior to development, SDR architecture trades on how to combine the RF and optical elements were studied. A modular architecture with physically separate RF and optical hardware slices was chosen and the optical slice of an SDR was designed and developed. The Harris AppSTAR("TM") platform, which consists of an FPGA processing platform with a mezzanine card targeted for RF communications, was used as the base platform in prototyping the optical slice. A serially concatenated pulse position modulation (SCPPM) optical waveform was developed. The waveform follows the standard described in the Consultative Committee for Space Data Systems (CCSDS) Optical Communions Coding and Synchronization Red Book. A custom optical mezzanine printed circuit board card was developed at NASA GRC for optical transmission. The optical mezzanine card replaces the DAC, which is used in the transmission of RF signals. This paper describes RF and optical SDR architecture trades, the Harris AppSTAR("TM") platform, the design of the SCPPM waveform, and the development of the optical mezzanine card.

optical communications↗

Development of an Optical Slice for an RF and Optical Software Defined Radio

A key component in the Integrated Radio and Optical Communications project at the National Aeronautics and Space Administration's (NASA) Glenn Research Center (GRC) is the radio frequency (RF) and optical software defined radio (SDR). A NASA RF SDR might consist of a general purpose processor to run the Space Telecommunications Radio System (STRS) Architecture for radio command and control, a reconfigurable signal processing device such as a field programmable gate array (FPGA) which houses the waveform, and a digital to analog converter (DAC) for transmitting data. Prior to development, SDR architecture trades on how to combine the RF and optical elements were studied. A modular architecture with physically separate RF and optical hardware slices was chosen and the optical slice of an SDR was designed and developed. The Harris AppSTARTM platform, which consists of an FPGA processing platform with a mezzanine card targeted for RF communications, was used as the base platform in prototyping the optical slice. A serially concatenated pulse position modulation (SCPPM) optical waveform was developed. The waveform follows the standard described in the Consultative Committee for Space Data Systems (CCSDS) Optical Communications Coding and Synchronization Red Book. A custom optical mezzanine printed circuit board card was developed at NASA GRC for optical transmission. The optical mezzanine card replaces the DAC, which is used in the transmission of RF signals. This paper describes RF and optical SDR architecture trades, the Harris AppSTAR platform, the design of the SCPPM waveform, and the development of the optical mezzanine card.

Nappier, Jennifer M.↗

NEXT Single String Integration Tests in Support of the Double Asteroid Redirection Test Mission

A system integration test has been performed utilizing a prototype model NEXT ion thruster, an engineering model power processing unit, and a laboratory model command and data handling system. The objectives of the test were to: a) verify that the integrated system meets performance requirements, b) demonstrate that the integrated system is functional across the anticipated thermal, power processor, and Xe propellant ranges for the DART mission, and to c) evaluate fault detection and operation of the command and data handling system. Measurements made during this test included: thruster performance, PPU input voltages, PPU electrical and thermal telemetry, software states, and fault flags. Additionally, a far-field electrostatic probe diagnostic was used to infer relative changes in the thrust vector across the various propellant flow splits. This manuscript presents the results of these tests, which include integrated ion propulsion system demonstrations of performance, details on the execution of DART flight algorithms, and software fault handling.

Thomas, Robert E.↗

NEXT Single String Integration Tests in Support of the Double Asteroid Redirection Test Mission

A system integration test has been performed utilizing a prototype model NEXT ion thruster, an engineering model power processing unit, and a laboratory model command and data handling system. The objectives of the test were to: a) verify that the integrated system meets performance requirements, b) demonstrate that the integrated system is functional across the anticipated thermal, power processor, and Xe propellant ranges for the DART mission, and to c) evaluate fault detection and operation of the command and data handling system. Measurements made during this test included: thruster performance, PPU input voltages, PPU electrical and thermal telemetry, software states, and fault flags. Additionally, a far-field electrostatic probe diagnostic was used to infer relative changes in the thrust vector across the various propellant flow splits. This manuscript presents the results of these tests, which include integrated ion propulsion system demonstrations of performance, details on the execution of DART flight algorithms, and software fault handling.

Thomas, Robert↗

Atmosphere Explorer control system software (version 2.0)

The Atmosphere Explorer Control System (AECS) was developed to provide automatic computer control of the Atmosphere Explorer spacecraft and experiments. The software performs several vital functions, such as issuing commands to the spacecraft and experiments, receiving and processing telemetry data, and allowing for extensive data processing by experiment analysis programs. The AECS was written for a 48K XEROX Data System Sigma 5 computer, and coexists in core with the XDS Real-time Batch Monitor (RBM) executive system. RBM is a flexible operating system designed for a real-time foreground/background environment, and hence is ideally suited for this application. Existing capabilities of RBM have been used as much as possible by AECS to minimize programming redundancy. The most important functions of the AECS are to send commands to the spacecraft and experiments, and to receive, process, and display telemetry data.

Mocarsky, W.↗

MPST Software: grl_pef_check

This innovation is a tool used to verify and validate spacecraft sequences at the predicted events file (PEF) level for the GRAIL (Gravity Recovery and Interior Laboratory, see http://www.nasa. gov/mission_pages/grail/main/index. html) mission as part of the Multi-Mission Planning and Sequencing Team (MPST) operations process to reduce the possibility for errors. This tool is used to catch any sequence related errors or issues immediately after the seqgen modeling to streamline downstream processes. This script verifies and validates the seqgen modeling for the GRAIL MPST process. A PEF is provided as input, and dozens of checks are performed on it to verify and validate the command products including command content, command ordering, flight-rule violations, modeling boundary consistency, resource limits, and ground commanding consistency. By performing as many checks as early in the process as possible, grl_pef_check streamlines the MPST task of generating GRAIL command and modeled products on an aggressive schedule. By enumerating each check being performed, and clearly stating the criteria and assumptions made at each step, grl_pef_check can be used as a manual checklist as well as an automated tool. This helper script was written with a focus on enabling the user with the information they need in order to evaluate a sequence quickly and efficiently, while still keeping them informed and active in the overall sequencing process. grl_pef_check verifies and validates the modeling and sequence content prior to investing any more effort into the build. There are dozens of various items in the modeling run that need to be checked, which is a time-consuming and errorprone task. Currently, no software exists that provides this functionality. Compared to a manual process, this script reduces human error and saves considerable man-hours by automating and streamlining the mission planning and sequencing task for the GRAIL mission.

Call, Jared A.↗