SEARCH · Engineering Papers

Results for “COMMAND SYSTEM”

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,189 records · Page 66

All sources NASA NTRS DOE OSTI

NASA NTRS1978

Building Specifications

The building in the top photo is the new home of the National Permanent Savings Bank in Washington, D.C., designed by Hartman-Cox Architects. Its construction was based on a money-saving method of preparing building specifications which derived from NASA technology developed to obtain quality construction while holding down cost of launch facilities, test centers and other structures. Written technical specifications spell out materials and components to be used on construction projects and identify the quality tests each item must pass. Specifications can have major impact on construction costs. Poorly formulated specifications can lead to unacceptable construction which must be replaced, unnecessarily high materials costs, safety hazards, disputes and often additional costs due to delays and litigation. NASA's Langley Research Center developed a novel approach to providing accurate, uniform, cost-effective specifications which can be readily updated to incorporate new building technologies. Called SPECSINTACT, it is a computerized - system accessible to all NASA centers involved in construction programs. The system contains a comprehensive catalog of master specifications applicable to many types of construction. It enables designers of any structure to call out relevant sections from computer storage and modify them to fit the needs of the project at hand. Architects and engineers can save time by concentrating their efforts on needed modifications rather than developing all specifications from scratch. Successful use of SPECSINTACT has led to a number of spinoff systems. One of the first was MASTERSPEC, developed from NASA's experience by Production Systems for Architects and Engineers, Inc., an organization established by the American Institute of Architects. MASTERSPEC, used in construction of the bank building pictured, follows the same basic format as SPECSINTACT and can be used in either automated or manual modes. The striking appearance of the bank building shows that, while MASTERSPEC saves time and money, its use involves no sacrfice in architectural design freedom. The Naval Engineering Facilities Command employs an automated specifications system based on SPECSINTACT. The Public Buildings Service of the General Services Administration used SPECSINTACT as a starting point in a plan to make its guideline specifications available to architects and engineers on a nationwide computer network. Public Technology, Inc., a NASA Technology Application Team, is working with Production Systems for Architects and Engineers, Inc., to promote widespread use of the system by state and local governments for cost benefits to taxpayers.

Source record↗

DOE OSTI2020

Phase Shift Control of a Three-Phase Inverter for Balanced Secondary Currents in Misaligned Three-Phase Inductive Power Transfer Systems

This paper presents a strategy for generating fundamental reference voltage commands for a double-sided LCC tuned three-phase wireless power transfer (WPT) system to achieve balanced output currents when the receiver and transmitter are not perfectly aligned. Formulas for translating the normalized fundamental current commands into phase-shift commands for two of the phase legs in a two-level three-phase inverter are derived. The methodology is validated through circuit simulations performed using coupler models derived from finite-element simulations. Simulation results for a 1.5 k W system design are included, which indicate near perfect correction of imbalance in the secondary currents for a typical misalignment case.

Pries, Jason↗

NASA NTRS1993

EOS ground data systems: A description and interface overview

The Earth Observing System (EOS) is planned as a space-based measurement system, earth-science research program, and data and information system (EOSDIS). It will consist of several high data rate spacecraft with multiple earth sensing instruments which provide investigators with a thorough, longterm view of the earth's environment. Up to seven spacecraft may be supported at once, either in operational, checkout, or testing phases; and the average data rate from the EOS satellites in orbit at any one time is expected to be from 18 to 60 Mbps. Providing the data processing and flight operations support for EOS will be the EOSDIS Core System (ECS). The ECS will command and control the spacecraft; process and store the EOS data; provide access to the data for years; and support researchers. The data processing aspects of the ECS consist of a collection of Distributed Active Archive Centers (DAAC's) which perform the product generation, data archive and distribution, and information management services. Flight operations aspects will be provided by the EOS Operations Center, by instrument control centers, and by widely distributed instrument support terminals. The communications and system management aspects will be provided by the EOSDIS Science Network and the System Management Center. In addition to the EOS satellite data, other data sets from earlier earth science missions are also to be added to designated DAAC's. Other ground data systems which will provide support to EOS for acquiring, transporting, processing, and distributing the transformed spacecraft data are currently being defined or are being upgraded for the EOS era. These systems include the Space Network consisting of the Tracking and Data Relay Satellite System (TDRSS), the TDRSS Ground Terminals, and the Network Control Center as well as the night Dynamics Facility, the EOS Data and Operations System, and EOS Communications. This paper briefly describes data handling by the ECS, the support data systems, their interfaces, and their roles.

Smith, Gene↗

NASA NTRS1991

NASA Goddard Space Flight Center Robotic Processing System Program Automation Systems, volume 2

Topics related to robot operated materials processing in space (RoMPS) are presented in view graph form. Some of the areas covered include: (1) mission requirements; (2) automation management system; (3) Space Transportation System (STS) Hitchhicker Payload; (4) Spacecraft Command Language (SCL) scripts; (5) SCL software components; (6) RoMPS EasyLab Command & Variable summary for rack stations and annealer module; (7) support electronics assembly; (8) SCL uplink packet definition; (9) SC-4 EasyLab System Memory Map; (10) Servo Axis Control Logic Suppliers; and (11) annealing oven control subsystem.

Dobbs, M. E.↗

NASA NTRS2009

Apollo Recovery Operations

Objectives include: a) Describe the organization of recovery force command and control and landing areas; b) Describe the function and timeline use of the Earth Landing System (ELS); c) Describe Stable 1 vs Stable 2 landing configurations and the function of the Command Module Uprighting System; d) Explain the activities of the helicopter and swimmer teams in egress and recovery of the crew; e)Explain the activities of the swimmer teams and primary recovery ship in recovery of the Command Module; and f) Describe several landing incidents that occurred during Apollo.

Interbartolo, Michael↗

NASA NTRS1978

Shuttle entry guidance

This paper describes the design of the entry guidance for the Space Shuttle Orbiter. This guidance provides the steering commands for trajectory control from initial penetration of the earth's atmosphere until the terminal area guidance is activated at an earth-relative speed of 2500 fps. At this point, the Orbiter is at a distance of about 50 nmi from the runway threshold, and at an altitude of about 80,000 ft. The entry guidance design is based on an analytic solution of the equations of motion defining the drag acceleration profile that meets the terminal criteria of the entry flight while maintaining the flight within systems and operational constraints. Guidance commands, which are based on a control law that ensures damping of oscillatory type trajectory motion, are computed to steer the Orbiter to this drag acceleration profile.

Harpold, J. C.↗

NASA NTRS1981

airborne data analysis/monitor system

An Airborne Data Analysis/Monitor System (ADAMS), a ROLM 1666 computer based system installed onboard test airplanes used during experimental testing is evaluated. In addition to the 1666 computer, the ADAMS hardware includes a DDC System 90 fixed head disk and a Miltape DD400 floppy disk. Boeing designed a DMA interface to the data acquisition system and an intelligent terminal to reduce system overhead and simplify operator commands. The ADAMS software includes RMX/RTOS and both ROLM FORTRAN and assembly language are used. The ADAMS provides real time displays that enable onboard test engineers to make rapid decisions about test conduct thus reducing the cost and time required to certify new model airplanes, and improved the quality of data derived from the test, leading to more rapid development of improvements resulting in quieter, safer, and more efficient airplanes. The availability of airborne data processing removes most of the weather and geographical restrictions imposed by telemetered flight test data systems. A data base is maintained to describe the airplane, the data acquisition system, the type of testing, and the conditions under which the test is performed.

Stephison, D. B.↗

NASA NTRS1988

Distributed cooperating processes in a mobile robot control system

A mobile inspection robot has been proposed for the NASA Space Station. It will be a free flying autonomous vehicle that will leave a berthing unit to accomplish a variety of inspection tasks around the Space Station, and then return to its berth to recharge, refuel, and transfer information. The Flying Eye robot will receive voice communication to change its attitude, move at a constant velocity, and move to a predefined location along a self generated path. This mobile robot control system requires integration of traditional command and control techniques with a number of AI technologies. Speech recognition, natural language understanding, task and path planning, sensory abstraction and pattern recognition are all required for successful implementation. The interface between the traditional numeric control techniques and the symbolic processing to the AI technologies must be developed, and a distributed computing approach will be needed to meet the real time computing requirements. To study the integration of the elements of this project, a novel mobile robot control architecture and simulation based on the blackboard architecture was developed. The control system operation and structure is discussed.

Skillman, Thomas L., Jr.↗

NASA NTRS2014

Integration of a MicroCAT Propulsion System and a PhoneSat Bus into a 1.5U CubeSat

NASA Ames Research Center and the George Washington University have developed an electric propulsion subsystem that can be integrated into the PhoneSat bus. Experimental tests have shown a reliable performance by firing three different thrusters at various frequencies in vacuum conditions. The three thrusters were controlled by a SmartPhone that was running the PhoneSat software. The subsystem is fully operational and it requires low average power to function (about 0.1 W). The interface consists of a microcontroller that sends a trigger pulses to the PPU (Plasma Processing Unit), which is responsible for the thruster operation. Frequencies ranging from 1 to 50Hz have been tested, showing a strong flexibility. A SmartPhone acts as the main user interface for the selection of commands that control the entire system. The micro cathode arc thruster MicroCAT provides a high 1(sub sp) of 3000s that allows a 4kg satellite to obtain a (delta)V of 300m/s. The system mass is only 200g with a total of volume of 200(cu cm). The propellant is based on a solid cylinder made of Titanium, which is the cathode at the same time. This simplicity in the design avoids miniaturization and manufacturing problems. The characteristics of this thruster allow an array of MicroCATs to perform attitude control and orbital correcton maneuvers that will open the door for the implementation of an extensive collection of new mission concepts and space applications for CubeSats. NASA Ames is currently working on the integration of the system to fit the thrusters and PPU inside a 1.5U CubeSat together with the PhoneSat bus into a 1.5U CubeSat. This satellite is intended to be deployed from the ISS in 2015 and test the functionality of the thrusters by spinning the satellite around its long axis and measure the rotational speed with the phone byros. This test flight will raise the TRL of the propulsion system from 5 to 7 and will be a first test for further CubeSats with propulsion systems, a key subsystem for long duration or interplanetary CubeSat missions.

PhoneSat↗

NASA NTRS1997

A Long Range Science Rover For Future Mars Missions

This paper describes the design and implementation currently underway at the Jet Propulsion Laboratory of a long range science rover for future missions to Mars. The small rover prototype, called Rocky 7, is capable of long traverse. autonomous navigation. and science instrument control, carries three science instruments, and can be commanded from any computer platform and any location using the World Wide Web. In this paper we describe the mobility system, the sampling system, the sensor suite, navigation and control, onboard science instruments. and the ground command and control system.

Hayati, Samad↗

NASA NTRS2004

Error Correction, Control Systems and Fuzzy Logic

This paper will be a discussion on dealing with errors. While error correction and communication is important when dealing with spacecraft vehicles, the issue of control system design is also important. There will be certain commands that one wants a motion device to execute. An adequate control system will be necessary to make sure that the instruments and devices will receive the necessary commands. As it will be discussed later, the actual value will not always be equal to the intended or desired value. Hence, an adequate controller will be necessary so that the gap between the two values will be closed.

Smith, Earl B.↗

NASA NTRS2009

Apollo Spacecraft and Saturn V Launch Vehicle Pyrotechnics/Explosive Devices

The Apollo Mission employs more than 210 pyrotechnic devices per mission.These devices are either automatic of commanded from the Apollo spacecraft systems. All devices require high reliability and safety and most are classified as either crew safety critical or mission critical. Pyrotechnic devices have a wide variety of applications including: launch escape tower separation, separation rocket ignition, parachute deployment and release and electrical circuit opening and closing. This viewgraph presentation identifies critical performance, design requirements and safety measures used to ensure quality, reliability and performance of Apollo pyrotechnic/explosive devices. The major components and functions of a typical Apollo pyrotechnic/explosive device are listed and described (initiators, cartridge assemblies, detonators, core charges). The presentation also identifies the major locations and uses for the devices on: the Command and Service Module, Lunar Module and all stages of the launch vehicle.

Interbartolo, Michael↗

NASA NTRS2005

Latency in Visionic Systems: Test Methods and Requirements

A visionics device creates a pictorial representation of the external scene for the pilot. The ultimate objective of these systems may be to electronically generate a form of Visual Meteorological Conditions (VMC) to eliminate weather or time-of-day as an operational constraint and provide enhancement over actual visual conditions where eye-limiting resolution may be a limiting factor. Empirical evidence has shown that the total system delays or latencies including the imaging sensors and display systems, can critically degrade their utility, usability, and acceptability. Definitions and measurement techniques are offered herein as common test and evaluation methods for latency testing in visionics device applications. Based upon available data, very different latency requirements are indicated based upon the piloting task, the role in which the visionics device is used in this task, and the characteristics of the visionics cockpit display device including its resolution, field-of-regard, and field-of-view. The least stringent latency requirements will involve Head-Up Display (HUD) applications, where the visionics imagery provides situational information as a supplement to symbology guidance and command information. Conversely, the visionics system latency requirement for a large field-of-view Head-Worn Display application, providing a Virtual-VMC capability from which the pilot will derive visual guidance, will be the most stringent, having a value as low as 20 msec.

Bailey, Randall E.↗

NASA NTRS1980

Verification of the Space Shuttle ascent flight control

The unique avionics design features of the Space Shuttle ascent flight control are described, along with the test article, test equipment, and test techniques used to verify the ascent flight control prior to commitment to the first orbital flight test. The ascent mission profiles are described, noting that upon ignition of the solid rocket boosters the Shuttle vehicle will rise vertically until achieving tower clearance. The Space Shuttle vehicle uses an integrated avionics system with the Orbiter avionics providing the command, control, and monitoring for the total mated Shuttle vehicle. The sensors and the actuator systems are discussed; the method of ascent flight control system verification is described, and it is concluded that the need for an advanced avionics integration and verification laboratory was recognized early in the program to provide maximum support to all program requirements.

Chambers, T. V.↗

NASA NTRS1990

Development Status: Automation Advanced Development Space Station Freedom Electric Power System

Electric power system automation for Space Station Freedom is intended to operate in a loop. Data from the power system is used for diagnosis and security analysis to generate Operations Management System (OMS) requests, which are sent to an arbiter, which sends a plan to a commander generator connected to the electric power system. This viewgraph presentation profiles automation software for diagnosis, scheduling, and constraint interfaces, and simulation to support automation development. The automation development process is diagrammed, and the process of creating Ada and ART versions of the automation software is described.

Dolce, James L.↗

NASA NTRS2003

The Livingstone Model of a Main Propulsion System

Livingstone is a discrete, propositional logic-based inference engine that has been used for diagnosis of physical systems. We present a component-based model of a Main Propulsion System (MPS) and say how it is used with Livingstone (L2) in order to implement a diagnostic system for integrated vehicle health management (IVHM) for the Propulsion IVHM Technology Experiment (PITEX). We start by discussing the process of conceptualizing such a model. We describe graphical tools that facilitated the generation of the model. The model is composed of components (which map onto physical components), connections between components and constraints. A component is specified by variables, with a set of discrete, qualitative values for each variable in its local nominal and failure modes. For each mode, the model specifies the component's behavior and transitions. We describe the MPS components' nominal and fault modes and associated Livingstone variables and data structures. Given this model, and observed external commands and observations from the system, Livingstone tracks the state of the MPS over discrete time-steps by choosing trajectories that are consistent with observations. We briefly discuss how the compiled model fits into the overall PITEX architecture. Finally we summarize our modeling experience, discuss advantages and disadvantages of our approach, and suggest enhancements to the modeling process.

Bajwa, Anupa↗

NASA NTRS2016

Feasibility of Varying Geo-Fence Around an Unmanned Aircraft Operation Based on Vehicle Performance and Wind

Managing trajectory separation is critical to ensuring accessibility, efficiency, and safety in the unmanned airspace. The notion of geo-fences is an emerging concept, where distance buffers enclose individual trajectories and areas of operation in order to manage the airspace. Currently, the Air Traffic Management system for commercial travel defines static distance buffers around the aircraft; however, commercial UASs are envisioned to operate in significantly closer proximity to other UAS requiring a geo-fence for spacing operations. The geo-fence size can be determined based on vehicle performance characteristics, state of the airspace, weather, and other unforeseen events such as emergency or disaster response. Calculation of the geo-fence size could be determined as part of pre-flight planning and during real-time operations. A largely non-homogeneous fleet of UASs will be operating in low altitude and will likely be commercially developed. Due to intellectual property concerns, the operators may not provide detailed specifications of the control system to UTM. In addition, the huge variety of UAS makes modeling each control system prohibitive and flight data for these vehicles may not exist. Therefore, a generalized, simple geo-fence sizing algorithm must be developed such that it does not rely on detailed knowledge of the vehicle control system, accounts for the presence of urban winds, and is sufficiently accurate. In this work, two simple models are investigated to determine its feasibility as an adequate means for calculating the geo-fence size. The vehicle data used in this work are provided by UAS manufactures who have partnered with NASA's UTM project and some publicly available websites. The first model utilizes wind data processed from the NOAA HRRR (Hourly Rapid Refresh) product and Sonar Annemometer data provided by San Jose State. The second model utilizes OpenFOAM which is a CFD code used to generate a wind field for flow around a single building. The key vehicle performance parameters can include UAS response time to disturbances, command to actuation latency, control system rate limits, time to recovery to desired path, and aerodynamics. It was found that the first model provides an initial understanding of geo-fence sizing, but does not provide enough accuracy to provide UTM with an efficient means of scheduling vehicles. The results of the second model reveal that modeling UAS controls systems with a linearized plant and gain scheduled PID controller does not allow capture the UAS flight dynamics within a significant envelope of the wind disturbances.

uncertainty↗

NASA NTRS1983

Human Factors Considerations in System Design

Human factors considerations in systems design was examined. Human factors in automated command and control, in the efficiency of the human computer interface and system effectiveness are outlined. The following topics are discussed: human factors aspects of control room design; design of interactive systems; human computer dialogue, interaction tasks and techniques; guidelines on ergonomic aspects of control rooms and highly automated environments; system engineering for control by humans; conceptual models of information processing; information display and interaction in real time environments.

Christine M Mitchell↗