Search NASA⌕ Search

SEARCH · Search NASA

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 487 records · Page 27
All sourcesNASA NTRSDOE OSTI
NASA NTRS1993

Toward an Autonomous Feature-based Pointing System for Planetary Missions

Although the analytical groundwork for understanding two-dimensional object images and various aspects of computer vision has been laid, we have not yet applied these concepts to automating the process of obtaining science images during space exploration missions. Our current approach in specifying pointing-command sequences relies heavily on target predicts, based on predicted target and spacecraft ephemerides, that propagate the target position as a function of time during pointing operations.

Computer↗
NASA NTRSDate not supplied

MUSTANG: A Workhorse for NASA Spaceflight Avionics

The Modular Unified Space Technology Avionics for Next Generation (MUSTANG) is a small integrated Avionics system including Command and Data Handling (C&DH), Power System Electronics (PSE), Attitude Control System Interfaces (ACS), and Propulsion Electronics. The MUSTANG Avionics Architecture is built upon many years of knowledge capture and lessons learned at the Goddard Space Flight Center. With a motivation towards modularity and keeping board redesign costs to a minimum, MUSTANG offers flexibility in features with a backplane-less design and allows the user to choose the options (cards) needed for their system. It incorporates a distributed power system that provides secondary power to all its subcomponents reducing the number of primary services needed for an Avionics. MUSTANG can be integrated into one system or divided into several smaller components. MUSTANG supports redundancy and cross-strap ability for a more robust and reliable Avionics system. A variation of MUSTANG exists for Instrument Electronics called iMUSTANG and allows the user to select functionality applicable to the instrument electronics. MUSTANG is not meant to replace Avionics for all spacecraft. There are limitations due to its relatively compact size, but the MUSTANG design has proven broadly applicable on many spacecraft and instrument bus avionics architectures.

MUSTANG↗
NASA NTRS2021

Combined Cycle Engine Large-Scale Inlet for Mode Transition Studies: System Identification Rack Software Design

This report describes the development of the system identification (SysID) rack custom application code. This code is used to automate the system identification experimental processes for the National Aeronautics and Space Administration (NASA) Combined Cycle Engine Large-Scale Inlet for Mode Transition Experiments testbed. This series of experiments took place in the NASA Glenn Research Center (GRC) 10 foot by 10 foot (10x10) Supersonic Wind Tunnel (SWT) test facility. The SysID code was developed to apply command signals to testbed actuators, receive actuator feedback signals, and acquire sensor data which is used to identify the dynamics of the experimental processes. This code development and the process identification experiments were conducted during Phase-2 testing at various operating points. These points were predefined from data collected during the Phase-1 testbed characterization experiments. The developed SysID code was executed on a NASA designed and built real-time data acquisition (DAQ) and controls (SysID) rack. This report focuses on the development of the SysID rack real-time DAQ and control hardware and the custom application code used to automate the system identification process. The implementation of this reliable and efficient data acquisition and controls development tool is demonstrated by presenting an example of experimental data collected to be used for system identification.

R Thomas↗
NASA NTRS2006

Gesture-Controlled Interfaces for Self-Service Machines

Gesture-controlled interfaces are software- driven systems that facilitate device control by translating visual hand and body signals into commands. Such interfaces could be especially attractive for controlling self-service machines (SSMs) for example, public information kiosks, ticket dispensers, gasoline pumps, and automated teller machines (see figure). A gesture-controlled interface would include a vision subsystem comprising one or more charge-coupled-device video cameras (at least two would be needed to acquire three-dimensional images of gestures). The output of the vision system would be processed by a pure software gesture-recognition subsystem. Then a translator subsystem would convert a sequence of recognized gestures into commands for the SSM to be controlled; these could include, for example, a command to display requested information, change control settings, or actuate a ticket- or cash-dispensing mechanism. Depending on the design and operational requirements of the SSM to be controlled, the gesture-controlled interface could be designed to respond to specific static gestures, dynamic gestures, or both. Static and dynamic gestures can include stationary or moving hand signals, arm poses or motions, and/or whole-body postures or motions. Static gestures would be recognized on the basis of their shapes; dynamic gestures would be recognized on the basis of both their shapes and their motions. Because dynamic gestures include temporal as well as spatial content, this gesture- controlled interface can extract more information from dynamic than it can from static gestures.

Cohen, Charles J.↗
NASA NTRS1987

How to feed a spacecraft

The uplink process between ground computers and the spacecraft computer is examined. Data is uplinked to a spacecraft by a load (a sequence of preplanned commands) or by real-time commands; the differences between these two types of uplinks are discussed. The sequencing of a load involves: (1) request generation, (2) request integration, (3) reference generation, and (4) transmitting the load. The functions of each of the sequencing steps are described. The development of new sequencing methods using expert systems and AI is being studied. A symbolic processing software which has the ability to transmit data typed into a computer in English was developed. Consideration is given to the composition, capabilities of the parser, and application of the symbolic processing software to the Comet Renedezvous Asteroid Flyby spacecraft.

Mclaughlin, William↗
NASA NTRS2001

On-Orbit ACDS Performance of the Landsat 7 Spacecraft

Landsat 7 is part of NASA's Earth Science Enterprise (ESE). The ESE is committed to developing an understanding of the total Earth system, the effects of natural and human-induced changes on the global environment, and how natural processes affect humans and how humans affect them. The Landsat 7 satellite consists of the spacecraft bus which was provided under a NASA contract with Lockheed Martin Missiles and Space in Philadelphia, PA, and the Enhanced Thematic Mapper-Plus (ETM+) instrument, procured under a NASA contract with Raytheon Santa Barbara Remote Sensing, in Santa Barbara, CA. The Landsat 7 Attitude Control and Determination System (ACDS) provides many essential functions for the operation of the spacecraft bus and for ETM+. The ACDS maintains the required attitude and orbit at the degree of accuracy necessary for power generation, command and telemetry, thermal balance, image acquisition, Gimbaled X-Band Antenna (GXA) pointing and data for image post-processing. Descriptions of the Landsat 7 mission and the ACDS modes and requirements are presented. A brief summary of significant events of the on-orbit initialization and validation period are provided. Finally, the Landsat 7 product generation system is described and the impact that the ACDS performance has on the ground based image processing system is explored.

Sabelhaus, Phillip↗
NASA NTRS1991

NAVSPASUR orbital processing for satellite break-up events

Satellite breakups via explosion or collision can instantly increase the trackable orbiting population by up to several hundred objects, temporarily perturbing the routine space surveillance operations at U.S. Space Command (USSPACWCOM) and the Naval Space Surveillance Center (NAVSPASUR). This paper is a survey of some of the procedures and techniques used by NAVSPASUR to respond to such events. First, the overall data flow at NAVSPASUR is described highlighting the places at which human analysts may intervene with special processing. So-called manual intervention is required in a variety of non-nominal situations, including breakups. Second, a description is given of some of the orbital analysis and other software tools available to NAVSPASUR analysts. These tools were developed in-house over the past thirty years and can be employed in a highly flexible manner. The basic design philosophy for these tools was to implement simple concepts as efficiently as possible and to allow the analyst maximum use of his personal expertise. Finally, several historical breakup scenarios are discussed briefly. These scenarios provide examples of the types of questions that are fairly easy to answer in the present operational environment, as well as examples of questions that are very difficult to answer.

Schumacher, Paul W., Jr.↗
NASA NTRS1993

Mission Operations and Command Assurance: Automating an Operations TQM Task

A long-term program is in progress at JPL to reduce cost and risk of mission operations through defect prevention and error management. A major element of this program, Mission Operations and Command Assurance (MO&QA), provides a system level function on flight projects to instill quality in mission operations. MO&CA embodies the Total Quality Management (TQM) principle of Continuous Process Inprovement (CPI) and uses CPI in applying automation to mission operations to reduce risk and costs. MO&CA has led efforts to apply and has implemented automation in areas that impact the daily flight project environment including Incident Surprise Anomoly tracking and reporting; command data verification, tracking, and reporting; and command support data usage. MO&CA's future work in automation will take into account that future missions systems must be designed to avoid increasing error through the introduction of automation, while adapting to the demands of smaller flight teams.

automation↗
NASA NTRS2020

Analysis of the Accuracy of Actuation Electronics in the Laser Interferometer Space Antenna Pathfinder

The Laser Interferometer Space Antenna Pathfinder (LPF) main observable, labelled∆g, is the differential force per unit mass acting on the two test masses in free fall condition, after the contribution of all non-gravitational forces have been compensated. At low frequencies the differential force is compensated by an applied electrostatic actuation force,which then must be subtracted from the measured acceleration to obtain∆g. Any inaccuracy in the actuation force contaminates the residual acceleration. This study investigates the accuracy of the electrostatic actuation system and its impact on the LPF main observable. It is shown that the inaccuracy is mainly caused by the rounding errors in the waveform processing and also by the random error caused by the analog to digital converter (ADC) random noise in the control loop. Both errors are one order of magnitude smaller than the resolution of the commanded voltages. We developed a simulator based on the LPF design to compute the close-to-reality actuation voltages and consequently, the resulting actuation forces. The simulator is applied in post-processing the LPF data.

M. Armano↗
DOE OSTI2024

Julienne v1.0.0

Julienne is a compiler-portable unit-testing framework for Fortran software projects, including those that use the parallel/accelerator-programming features of Fortran 2023. Julienne achieves portability across compilers through minimalism and isolation. The minimal design ensures that Julienne uses only features supported by the majority of Fortran compilers. The isolation through zero dependencies ensures that no other projects block Julienne from building with a particular compiler. Julienne also contains with additional services that support its unit-testing code. These include functions for manipulating strings, command lines and input/output format strings; and a user-defined collective subroutine for verifying that all processes pass a test in parallel testing. Julienne's name derives from the term for vegetables sliced into thin strings: julienne vegetables. Julienne captures the authors' most frequently used thin slice of the Veggies and Sourcery software repositories while avoiding certain compiler limitations of the those two packages.

Rouson, Damian↗
NASA NTRS1977

Robotics control using isolated word recognition of voice input

A speech input/output system is presented that can be used to communicate with a task oriented system. Human speech commands and synthesized voice output extend conventional information exchange capabilities between man and machine by utilizing audio input and output channels. The speech input facility is comprised of a hardware feature extractor and a microprocessor implemented isolated word or phrase recognition system. The recognizer offers a medium sized (100 commands), syntactically constrained vocabulary, and exhibits close to real time performance. The major portion of the recognition processing required is accomplished through software, minimizing the complexity of the hardware feature extractor.

Weiner, J. M.↗
NASA NTRS1991

Controlling Laboratory Processes From A Personal Computer

Computer program provides natural-language process control from IBM PC or compatible computer. Sets up process-control system that either runs without operator or run by workers who have limited programming skills. Includes three smaller programs. Two of them, written in FORTRAN 77, record data and control research processes. Third program, written in Pascal, generates FORTRAN subroutines used by other two programs to identify user commands with device-driving routines written by user. Also includes set of input data allowing user to define user commands to be executed by computer. Requires personal computer operating under MS-DOS with suitable hardware interfaces to all controlled devices. Also requires FORTRAN 77 compiler and device drivers written by user.

Will, H.↗
NASA NTRS1991

Recent manufacturing advances for spiral bevel gears

The U.S. Army Aviation Systems Command (AVSCOM), through the Propulsion Directorate at NASA LRC, has recently sponsored projects to advance the manufacturing process for spiral bevel gears. This type of gear is a critical component in rotary-wing propulsion systems. Two successfully completed contracted projects are described. The first project addresses the automated inspection of spiral bevel gears through the use of coordinate measuring machines. The second project entails the computer-numerical-control (CNC) conversion of a spiral bevel gear grinding machine that is used for all aerospace spiral bevel gears. The results of these projects are described with regard to the savings effected in manufacturing time.

Handschuh, Robert F.↗
NASA NTRS1992

Nonlinear Maneuver Autopilot

Trajectory-control laws based on singular-perturbation theory and nonlinear dynamical modeling. Nonlinear maneuver autopilot commands flight-test trajectories of F-15 airplane. Underlying theory of controller enables separation of variables processed in fast and slow control loops, reducing amount of computation required.

Menon, P. K. A.↗
NASA NTRS1990

STS-41 Space Shuttle mission report

The STS-41 Space Shuttle Program Mission Report contains a summary of the vehicle subsystem activities on this thirty-sixth flight of the Space Shuttle and the eleventh flight of the Orbiter vehicle, Discovery (OV-103). In addition to the Discovery vehicle, the flight vehicle consisted of an External Tank (ET) (designated as ET-39/LWT-32), three Space Shuttle main engines (SSME's) (serial numbers 2011, 2031, and 2107), and two Solid Rocket Boosters (SRB's), designated as BI-040. The primary objective of the STS-41 mission was to successfully deploy the Ulysses/inertial upper stage (IUS)/payload assist module (PAM-S) spacecraft. The secondary objectives were to perform all operations necessary to support the requirements of the Shuttle Backscatter Ultraviolet (SSBUV) Spectrometer, Solid Surface Combustion Experiment (SSCE), Space Life Sciences Training Program Chromosome and Plant Cell Division in Space (CHROMEX), Voice Command System (VCS), Physiological Systems Experiment (PSE), Radiation Monitoring Experiment - 3 (RME-3), Investigations into Polymer Membrane Processing (IPMP), Air Force Maui Optical Calibration Test (AMOS), and Intelsat Solar Array Coupon (ISAC) payloads. The sequence of events for this mission is shown in tabular form. Summarized are the significant problems that occurred in the Orbiter subsystems during the mission. The official problem tracking list is presented. In addition, each Orbiter problem is cited in the subsystem discussion.

Camp, David W.↗
NASA NTRS1992

An integrated dexterous robotic testbed for space applications

An integrated dexterous robotic system was developed as a testbed to evaluate various robotics technologies for advanced space applications. The system configuration consisted of a Utah/MIT Dexterous Hand, a PUMA 562 arm, a stereo vision system, and a multiprocessing computer control system. In addition to these major subsystems, a proximity sensing system was integrated with the Utah/MIT Hand to provide capability for non-contact sensing of a nearby object. A high-speed fiber-optic link was used to transmit digitized proximity sensor signals back to the multiprocessing control system. The hardware system was designed to satisfy the requirements for both teleoperated and autonomous operations. The software system was designed to exploit parallel processing capability, pursue functional modularity, incorporate artificial intelligence for robot control, allow high-level symbolic robot commands, maximize reusable code, minimize compilation requirements, and provide an interactive application development and debugging environment for the end users. An overview is presented of the system hardware and software configurations, and implementation is discussed of subsystem functions.

Li, Larry C.↗
NASA NTRS1992

ROMPS critical design review. Volume 2: Robot module design documentation

The robot module design documentation for the Remote Operated Materials Processing in Space (ROMPS) experiment is compiled. This volume presents the following information: robot module modifications; Easylab commands definitions and flowcharts; Easylab program definitions and flowcharts; robot module fault conditions and structure charts; and C-DOC flow structure and cross references.

Dobbs, M. E.↗