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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS1999

Acting on Information: Representing Actions That Manipulate Information

Information manipulation is the creation of new information based on existing information sources. This paper discusses problems that arise when planning for information manipulation, and proposes a novel action representation, called ADLIM, that addresses these problems, including: How to represent information in a way sufficient to express the effects of actions that modify the information. I present a simple, yet expressive, representation of information goals and effects that generalizes earlier work on representing sensing actions; How to concisely represent actions that copy information, or produce new information that is based on existing information sources. I show how this is a generalization of the frame problem, and present a solution based on generalized frame effects; and How to generate a pipeline of information-processing commands that will produce an output containing exactly the desired information. I present a new approach to goal regression.

Golden, Keith↗
NASA NTRS2004

Space-Based Telemetry And Range Safety Flight Demonstration #1

The basic ability of STARS to maintain a satellite communications link with TDRSS satellites during dynamic aircraft flights was successfully demonstrated during FD 1. The Range Safety and Range User systems' link margins were measured. The ability to acquire/reacquire and maintain lock between a high-dynamic vehicle and a satellite-based system was demonstrated. The Range Safety system simultaneously received and processed command links from space and ground transmitters and provided near real-time Range Safety telemetry to DFRC, which then sent it in near real time to KSC, GSFC, and WFF for monitoring. The GPS receiver maintained track except during extremely dynamic maneuvers. The Range User system sent data at three different data rates. There were excellent cooperation and support from the different Centers, contractors, and Ranges. A large amount of data was recorded and extensive post-flight analysis was performed. The Range User TDRSS link margin met or exceeded the predicted performance at three different data rates. The Range Safety launch-head link margins generally agreed with the predicted performance. The UPS positions and velocities agreed with those from tracking radar to within about 20 m and a few rn/s. The link margins for the Range Safety TDRSS telemetry link were less than expected. The link margin for one TDRSS command link LPT channel was occasionally much less than the other. Additional post-flight testing has yet to identify the root causes of these results. There were many lessons learned from this first set of test flights. The most important one is that more time and testing are needed for each step to deal with the inevitable problems. It is vital that these lessons be among the primary areas of study that will carry over from FD#1 to FD#2, which is currently scheduled for early FY05 at DFRC and will use a specially designed Ku-band phased array antenna for the Range User system. The next series of flight demonstrations scheduled for late 2004 at DFRC will incorporate many lessons learned from FD#1. A specially designed Ku-band phased array antenna will be used with the Range User system. A test flight on a hypersonic vehicle is planned by the end of 2006.

Demspm. Erol↗
NASA NTRS1975

Digital command system

The correct processing of the Digital Command System (DCS), which provides a limited real-time means of controlling specific flight program functions, was verified. The ability of the flight program to correctly read and process DCS commands was verified. Tests made by the flight program after reading the contents of the command decoder register to establish the validity of the received data were verified through the following: DCS mode command verification, DCS data command verification, DCS data validation, and DCS error message. The operation of the following DCS commands accepted and processed by the flight program was tested: time base update, navigation update, generalized switch selector, memory dump, terminate, execute generalized maneuver, return to nominal timeline, ECS water control valve logic inhibit, execute maneuver, execute alternate sequence, targeting load, ladder magnitude limit, S-IVB/IU de-orbit, compressed data dump, and remove inhibit on the extraction maneuver.

Source record↗
NASA NTRS1974

Apollo experience report the command and service module milestone review process

The sequence of the command and service module milestone review process is given, and the Customer Acceptance Readiness Review and Flight Readiness Review plans are presented. Contents of the System Summary Acceptance Documents for the two formal spacecraft reviews are detailed, and supplemental data required for presentation to the review boards are listed. Typical forms, correspondence, supporting documentation, and minutes of a board meeting are included.

Brendle, H. L.↗
NASA NTRS1985

Spacecraft commanding for unmanned planetary missions - The uplink process

A general description of the command generation process for unmanned planetary missions is presented. Emphasis is given to those mission characteristics which significantly affect the cost of the uplink process including: the level of mission activity; mission strategies; permissible risk; and spacecraft design. Pertinent examples of the command generation procedures used in the Voyager, Mariner, and Viking programs are given in order to illustrate the different stages of the uplink process.

Linick, T. D.↗
NASA NTRS2008

Cassini's Maneuver Automation Software (MAS) Process: How to Successfully Command 200 Navigation Maneuvers

To keep Cassini on its complex trajectory, more than 200 orbit trim maneuvers (OTMs) have been planned from July 2004 to July 2010. With only a few days between many of these OTMs, the operations process of planning and executing the necessary commands had to be automated. The resulting Maneuver Automation Software (MAS) process minimizes the workforce required for, and maximizes the efficiency of, the maneuver design and uplink activities. The MAS process is a well-organized and logically constructed interface between Cassini's Navigation (NAV), Spacecraft Operations (SCO), and Ground Software teams. Upon delivery of an orbit determination (OD) from NAV, the MAS process can generate a maneuver design and all related uplink and verification products within 30 minutes. To date, all 112 OTMs executed by the Cassini spacecraft have been successful. MAS was even used to successfully design and execute a maneuver while the spacecraft was in safe mode.

Yang, Genevie Velarde↗
NASA NTRS2006

Lessons Learned from Daily Uplink Operations during the Deep Impact Mission

The Deep Impact mission to comet Tempel-1 produced some of the more spectacular science results ever collected by a spacecraft. On July 4, 2005 the Deep Impact Flyby vehicle observed the Deep Impact Impactor vehicle's collision with the comet. 24 hours earlier the Flyby vehicle released the Impactor vehicle into the path of comet Tempel-1. The process to command the spacecraft was a challenge to the entire flight operations team. This paper presents an overview of the process used prepare command products for uplink and the lessons that were learned from this process.

mission operations↗
NASA NTRS2012

Automated Sequence Processor: Something Old, Something New

High productivity required for operations teams to meet schedules Risk must be minimized. Scripting used to automate processes. Scripts perform essential operations functions. Automated Sequence Processor (ASP) was a grass-roots task built to automate the command uplink process System engineering task for ASP revitalization organized. ASP is a set of approximately 200 scripts written in Perl, C Shell, AWK and other scripting languages.. ASP processes/checks/packages non-interactive commands automatically.. Non-interactive commands are guaranteed to be safe and have been checked by hardware or software simulators.. ASP checks that commands are non-interactive.. ASP processes the commands through a command. simulator and then packages them if there are no errors.. ASP must be active 24 hours/day, 7 days/week..

Automated↗
NASA NTRS2008

Converting from DDOR SASF to APF

A computer program called ddor_sasf2apf converts delta-door (delta differential one-way range) request from an SASF (spacecraft activity sequence file) format to an APF (apgen plan file) format for use in the Mars Reconnaissance Orbiter (MRO) missionplanning- and-sequencing process. The APF is used as an input to APGEN/AUTOGEN in the MRO activity- planning and command-sequencegenerating process to sequence the delta-door (DDOR) activity. The DDOR activity is a spacecraft tracking technique for determining spacecraft location. The input to ddor_sasf2apf is an input request SASF provided by an observation team that utilizes DDOR. ddor_sasf2apf parses this DDOR SASF input, rearranging parameters and reformatting the request to produce an APF file for use in AUTOGEN and/or APGEN. The benefit afforded by ddor_sasf2apf is to enable the use of the DDOR SASF file earlier in the planning stage of the command-sequence-generating process and to produce sequences, optimized for DDOR operations, that are more accurate and more robust than would otherwise be possible.

Gladden, Roy E.↗
NASA NTRS2000

The NASA Spacecraft Transponding Modem

A new deep space transponder is being developed by the Jet Propulsion Laboratory for NASA. The Spacecraft Transponding Modem (STM) implements the standard transponder functions and the channel service functions that have previously resided in spacecraft Command/Data Subsystems. The STM uses custom ASICs, MMICs, and MCMs to reduce the active device parts count to 70, mass to I kg, and volume to 524 cc. The first STMs will be flown on missions launching in the 2003 time frame. The STM tracks an X-band uplink signal and provides both X-band and Ka-band downlinks, either coherent or non-coherent with the uplink. A NASA standard Command Detector Unit is integrated into the STM, along with a codeblock processor and a hardware command decoder. The decoded command codeblocks are output to the spacecraft command/data subsystem. Virtual Channel 0 (VC-0) (hardware) commands are processed and output as critical controller (CRC) commands. Downlink telemetry is received from the spacecraft data subsystem as telemetry frames. The STM provides the following downlink coding options: the standard CCSDS (7-1/2) convolutional coding, ReedSolomon coding with interleave depths one and five, (15-1/6) convolutional coding, and Turbo coding with rates 1/3 and 1/6. The downlink symbol rates can be linearly ramped to match the G/T curve of the receiving station, providing up to a 1 dB increase in data return. Data rates range from 5 bits per second (bps) to 24 Mbps, with three modulation modes provided: modulated subcarrier (3 different frequencies provided), biphase-L modulated direct on carrier, and Offset QPSK. Also, the capability to generate one of four non-harmonically related telemetry beacon tones is provided, to allow for a simple spacecraft status monitoring scheme for cruise phases of missions. Three ranging modes are provided: standard turn around ranging, regenerative pseudo-noise (PN) ranging, and Differential One-way Ranging (DOR) tones. The regenerative ranging provides the capability of increasing the ground received ranging SNR by up to 30 dB. Two different avionics interfaces to the command/data subsystem's data bus are provided: a MIL STD 1553B bus or an industry standard PCI interface. Digital interfaces provide the capability to control antenna selection (e.g., switching between high gain and low gain antennas) and antenna pointing (for future steered Ka-band antennas).

Berner, Jeff B.↗
NASA NTRS1996

The Influence of Future Command, Control, Communications, and Computers (C4) on Doctrine and the Operational Commander's Decision-Making Process

Future C4 systems will alter the traditional balance between force and information, having a profound influence on doctrine and the operational commander's decision making process. The Joint Staff's future vision of C4 is conceptualized in 'C4I for the Warrior' which envisions a joint C4I architecture providing timely sensor to shoot information direct to the warfighter. C4 system must manage and filter an overwhelming amount of information; deal with interoperability issues; overcome technological limitations; meet emerging security requirements; and protect against 'Information Warfare.' Severe budget constraints necessitate unified control of C4 systems under singular leadership for the common good of all the services. In addition, acquisition policy and procedures must be revamped to allow new technologies to be fielded quickly; and the commercial marketplace will become the preferred starting point for modernization. Flatter command structures are recommended in this environment where information is available instantaneously. New responsibilities for decision making at lower levels are created. Commanders will have to strike a balance between exerting greater control and allowing subordinates enough flexibility to maintain initiative. Clearly, the commander's intent remains the most important tool in striking this balance.

Mayer, Michael G.↗
NASA NTRS2006

Control Software for Advanced Video Guidance Sensor

Embedded software has been developed specifically for controlling an Advanced Video Guidance Sensor (AVGS). A Video Guidance Sensor is an optoelectronic system that provides guidance for automated docking of two vehicles. Such a system includes pulsed laser diodes and a video camera, the output of which is digitized. From the positions of digitized target images and known geometric relationships, the relative position and orientation of the vehicles are computed. The present software consists of two subprograms running in two processors that are parts of the AVGS. The subprogram in the first processor receives commands from an external source, checks the commands for correctness, performs commanded non-image-data-processing control functions, and sends image data processing parts of commands to the second processor. The subprogram in the second processor processes image data as commanded. Upon power-up, the software performs basic tests of functionality, then effects a transition to a standby mode. When a command is received, the software goes into one of several operational modes (e.g. acquisition or tracking). The software then returns, to the external source, the data appropriate to the command.

Howard, Richard T.↗
NASA NTRS1989

Laboratory process control using natural language commands from a personal computer

PC software is described which provides flexible natural language process control capability with an IBM PC or compatible machine. Hardware requirements include the PC, and suitable hardware interfaces to all controlled devices. Software required includes the Microsoft Disk Operating System (MS-DOS) operating system, a PC-based FORTRAN-77 compiler, and user-written device drivers. Instructions for use of the software are given as well as a description of an application of the system.

Will, Herbert A.↗
NASA NTRS1980

Eight microprocessor-based instrument data systems in the Galileo Orbiter spacecraft

Instrument data systems consist of a microprocessor, 3K bytes of Read Only Memory and 3K bytes of Random Access Memory. It interfaces with the spacecraft data bus through an isolated user interface with a direct memory access bus adaptor, and/or parallel data from instrument devices such as registers, buffers, analog to digital converters, multiplexers, and solid state sensors. These data systems support the spacecraft hardware and software communication protocol, decode and process instrument commands, generate continuous instrument operating modes, control the instrument mechanisms, acquire, process, format, and output instrument science data.

Barry, R. C.↗