SEARCH · Engineering Papers

Results for “Commanding”

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 739 records · Page 41

All sources NASA NTRS DOE OSTI

NASA NTRS1991

Design and piloted simulation evaluation of integrated flight/propulsion controls for STOVL aircraft

Integrated flight/propulsion control systems have been designed for operation of STOVL aircraft over the low speed powered-lift flight envelope. The control system employs command modes for attitude, flightpath angle and flightpath acceleration during transition, and translational velocity command for hover and vertical landing. The command modes and feedback control are implemented in the form of a state-rate feedback implicit model follower to achieve the desired flying qualities and to suppress the effects of external disturbances and variations in the aircraft characteristics over the low speed envelope. A nonlinear inverse system was used to translate the output from these commands and feedback control into commands for the various aerodynamic and propulsion control effectors that are employed in powered-lift flight. Piloted evaluations of these STOVL integrated control designs have been conducted on Ames Research Center's Vertical Motion Simulator to assess flying qualities over the low-speed flight envelope. Results indicate that Level 1 flying qualities are achieved with this control system concept for each of these low-speed operations over a wide range of wind, atmospheric turbulence, and visibility conditions.

Franklin, James A.↗

NASA NTRS1992

Control system and method for prosthetic devices

A control system and method for prosthetic devices is provided. The control system comprises a transducer for receiving movement from a body part for generating a sensing signal associated with that movement. The sensing signal is processed by a linearizer for linearizing the sensing signal to be a linear function of the magnitude of the distance moved by the body part. The linearized sensing signal is normalized to be a function of the entire range of body part movement from the no-shrug position of the movable body part through the full-shrug position of the movable body part. The normalized signal is divided into a plurality of discrete command signals. The discrete command signals are used by typical converter devices which are in operational association with the prosthetic device. The converter device uses the discrete command signals for driving the movable portions of the prosthetic device and its sub-prosthesis. The method for controlling a prosthetic device associated with the present invention comprises the steps of receiving the movement from the body part, generating a sensing signal in association with the movement of the body part, linearizing the sensing signal to be a linear function of the magnitude of the distance moved by the body part, normalizing the linear signal to be a function of the entire range of the body part movement, dividing the normalized signal into a plurality of discrete command signals, and implementing the plurality of discrete command signals for driving the respective movable prosthesis device and its sub-prosthesis.

Bozeman, Richard J., Jr.↗

NASA NTRS1992

A new programming metaphor for image processing procedures

Most image processing systems, besides an Application Program Interface (API) which lets users write their own image processing programs, also feature a higher level of programmability. Traditionally, this is a command or macro language, which can be used to build large procedures (scripts) out of simple programs or commands. This approach, a legacy of the teletypewriter has serious drawbacks. A command language is clumsy when (and if! it attempts to utilize the capabilities of a multitasking or multiprocessor environment, it is but adequate for real-time data acquisition and processing, it has a fairly steep learning curve, and the user interface is very inefficient,. especially when compared to a graphical user interface (GUI) that systems running under Xll or Windows should otherwise be able to provide. ll these difficulties stem from one basic problem: a command language is not a natural metaphor for an image processing procedure. A more natural metaphor - an image processing factory is described in detail. A factory is a set of programs (applications) that execute separate operations on images, connected by pipes that carry data (images and parameters) between them. The programs function concurrently, processing images as they arrive along pipes, and querying the user for whatever other input they need. From the user's point of view, programming (constructing) factories is a lot like playing with LEGO blocks - much more intuitive than writing scripts. Focus is on some of the difficulties of implementing factory support, most notably the design of an appropriate API. It also shows that factories retain all the functionality of a command language (including loops and conditional branches), while suffering from none of the drawbacks outlined above. Other benefits of factory programming include self-tuning factories and the process of encapsulation, which lets a factory take the shape of a standard application both from the system and the user's point of view, and thus be used as a component of other factories. A bare-bones prototype of factory programming was implemented under the PcIPS image processing system, and a complete version (on a multitasking platform) is under development.

Smirnov, O. M.↗

NASA NTRS1993

A direct application of the non-linear inverse transformation flight control system design on a STOVL aircraft

The nonlinear inverse transformation flight control system design method is applied to the Lockheed Ft. Worth Company's E-7D short takeoff and vertical land (STOVL) supersonic fighter/attack aircraft design with a modified General Electric F110 engine which has augmented propulsive lift capability. The system is fully augmented to provide flight path control and velocity control, and rate command attitude hold for angular axes during the transition and hover operations. In cruise mode, the flight control system is configured to provide direct thrust command, rate command attitude hold for pitch and roll axes, and sideslip command with turn coordination. A control selector based on the nonlinear inverse transformation method is designed specifically to be compatible with the propulsion system's physical configuration which has a two dimensional convergent-divergent aft nozzle, a vectorable ventral nozzle, and a thrust augmented ejector. The nonlinear inverse transformation is used to determine the propulsive forces and nozzle deflections, which in combination with the aerodynamic forces and moments (including propulsive induced contributions), and gravitational force, are required to achieve the longitudinal and vertical acceleration commands. The longitudinal control axes are fully decoupled within the propulsion system's performance envelope. A piloted motion-base flight simulation was conducted on the Vertical Motion Simulator (VMS) at NASA Ames Research Center to examine the handling qualities of this design. Based on results of the simulation, refinements to the control system have been made and will also be covered in the report.

Chung, W. W.↗

NASA NTRS1994

SEQ-GEN: A comprehensive multimission sequencing system

SEQ-GEN is a user-interactive computer program used to plan and generate a sequence of commands for spacecraft. Desired activities are specified by the user of SEQ-GEN; SEQ-GEN in turn expands these activities, deriving the spacecraft commands necessary to accomplish the desired activities. SEQ-GEN models the effects on the spacecraft of the commands, predicting the state as a function of time, flagging any conflicts and rule violations. These states, conflicts, and violations are viewable both graphically and textually at the user's request. SEQ-GEN also displays the entire sequence graphically, showing each requested activity as a bar on its graphical timeline. SEQ-GEN immediately revalidates the sequence, updating its models and calculations along with its displays based on these changes. Because it has the ability to recalculate spacecraft states immediately, the user is able to perform 'what-if' sessions easily. SEQ-GEN, a multimission tool, is adaptable to any flight project. A flight project writes its adaptation files containing project unique information including in its simplest form, only spacecraft commands. For more involved projects the adaptation files may also contain flight and mission rules, description of the spacecraft and ground models, and the definition of activities. SEQ-GEN operates at whatever level of detail the adaptation files imply. Simple adaptations are straight forward to do. There is, however, no limit to the complexity of activity definitions or of spacecraft models: both may involve unlimited logical decision points. Commands and activities may involve any number of parameters of a wide variety of data types, including integer, float, time, boolean, and character strings. SEQ-GEN will be used by the Mars Pathfinder, Cassini, and VIM (Voyager Interstellar Mission) project in an effort to speed up adaptation time and to keep sequence generation costs down. SEQ-GEN is hosted on UNIX workstations. It uses MOTIF and X for windowing, and was designed and coded in an object-oriented style in the language C++.

Salcedo, Jose↗

NASA NTRS1994

Implementation of a low-cost, commercial orbit determination system

Traditional satellite and launch control systems have consisted of custom solutions requiring significant development and maintenance costs. These systems have typically been designed to support specific program requirements and are expensive to modify and augment after delivery. The expanding role of space in today's marketplace combined with the increased sophistication and capabilities of modern satellites has created a need for more efficient, lower cost solutions to complete command and control systems. Recent technical advances have resulted in commercial-off-the-shelf products which greatly reduce the complete life-cycle costs associated with satellite launch and control system procurements. System integrators and spacecraft operators have, however, been slow to integrate these commercial based solutions into a comprehensive command and control system. This is due, in part, to a resistance to change and the fact that many available products are unable to effectively communicate with other commercial products. The United States Air Force, responsible for the health and safety of over 84 satellites via its Air Force Satellite Control Network (AFSCN), has embarked on an initiative to prove that commercial products can be used effectively to form a comprehensive command and control system. The initial version of this system is being installed at the Air Force's Center for Research Support (CERES) located at the National Test Facility in Colorado Springs, Colorado. The first stage of this initiative involved the identification of commercial products capable of satisfying each functional element of a command and control system. A significant requirement in this product selection criteria was flexibility and ability to integrate with other available commercial products. This paper discusses the functions and capabilities of the product selected to provide orbit determination functions for this comprehensive command and control system.

Corrigan, Jim↗

NASA NTRS1995

Control method for prosthetic devices

A control system and method for prosthetic devices is provided. The control system comprises a transducer for receiving movement from a body part for generating a sensing signal associated with that movement. The sensing signal is processed by a linearizer for linearizing the sensing signal to be a linear function of the magnitude of the distance moved by the body part. The linearized sensing signal is normalized to be a function of the entire range of body part movement from the no-shrug position of the moveable body part. The normalized signal is divided into a plurality of discrete command signals. The discrete command signals are used by typical converter devices which are in operational association with the prosthetic device. The converter device uses the discrete command signals for driving the moveable portions of the prosthetic device and its sub-prosthesis. The method for controlling a prosthetic device associated with the present invention comprises the steps of receiving the movement from the body part, generating a sensing signal in association with the movement of the body part, linearizing the sensing signal to be a linear function of the magnitude of the distance moved by the body part, normalizing the linear signal to be a function of the entire range of the body part movement, dividing the normalized signal into a plurality of discrete command signals, and implementing the plurality of discrete command signals for driving the respective moveable prosthesis device and its sub-prosthesis.

Bozeman, Richard J., Jr.↗

NASA NTRS1996

Control System for Prosthetic Devices

A control system and method for prosthetic devices is provided. The control system comprises a transducer for receiving movement from a body part for generating a sensing signal associated with that of movement. The sensing signal is processed by a linearizer for linearizing the sensing signal to be a linear function of the magnitude of the distance moved by the body part. The linearized sensing signal is normalized to be a function of the entire range of body part movement from the no-shrug position of the moveable body part through the full-shrg position of the moveable body part. The normalized signal is divided into a plurality of discrete command signals. The discrete command signals are used by typical converter devices which are in operational association with the prosthetic device. The converter device uses the discrete command signals for driving the moveable portions of the prosthetic device and its sub-prosthesis. The method for controlling a prosthetic device associated with the present invention comprises the steps of receiving the movement from the body part, generating a sensing signal in association with the movement of the body part, linearizing the sensing signal to be a linear function of the magnitude of the distance moved by the body part, normalizing the linear signal to be a function of the entire range of the body part movement, dividing the normalized signal into a plurality of discrete command signals, and implementing the plurality of discrete command signals for driving the respective moveable prosthesis device and its sub-prosthesis.

Bozeman, Richard J.↗

NASA NTRS1997

The Volume Grid Manipulator (VGM): A Grid Reusability Tool

This document is a manual describing how to use the Volume Grid Manipulation (VGM) software. The code is specifically designed to alter or manipulate existing surface and volume structured grids to improve grid quality through the reduction of grid line skewness, removal of negative volumes, and adaption of surface and volume grids to flow field gradients. The software uses a command language to perform all manipulations thereby offering the capability of executing multiple manipulations on a single grid during an execution of the code. The command language can be input to the VGM code by a UNIX style redirected file, or interactively while the code is executing. The manual consists of 14 sections. The first is an introduction to grid manipulation; where it is most applicable and where the strengths of such software can be utilized. The next two sections describe the memory management and the manipulation command language. The following 8 sections describe simple and complex manipulations that can be used in conjunction with one another to smooth, adapt, and reuse existing grids for various computations. These are accompanied by a tutorial section that describes how to use the commands and manipulations to solve actual grid generation problems. The last two sections are a command reference guide and trouble shooting sections to aid in the use of the code as well as describe problems associated with generated scripts for manipulation control.

Alter, Stephen J.↗

NASA NTRS1997

Moving-Base Simulation Evaluation of Control/Display Integration Issues for ASTOVL Aircraft

A moving-base simulation has been conducted on the Vertical Motion Simulator at Ames Research Center using a model of an advanced, short takeoff and vertical landing (STOVL) lift fan fighter aircraft. This experiment expanded on investigations during previous simulations with this STOVL configuration with the objective of evaluating (1) control law modifications over the low speed flight envelope, (2) integration of the throttle inceptor with flight control laws that provide direct thrust command for conventional flight, vertical and short takeoff, and flightpath or vertical velocity command for transition, hover, and vertical landing, (3) control mode blending for pitch, roll, yaw, and flightpath control during transition from wing-borne to jet-borne flight, and (4) effects of conformal versus nonconformal presentation of flightpath and pursuit guidance symbology on the out-the-window display for low speed STOVL operations. Assessments were made for takeoff, transition, hover, and landing, including precision hover and landing aboard an LPH-type amphibious assault ship in the presence of winds and rough seas. Results yielded Level 1 pilot ratings for the flightpath and vertical velocity command modes for a range of land-based and shipboard operation and were consistent with previous experience with earlier control laws and displays for this STOVL concept. Control mode blending was performed over speed ranges in accord with the pilot's tasks and with the change of the basic aircraft's characteristics between wing-borne and hover flight. Blending of yaw control from heading command in hover to sideslip command in wing-borne flight performed over a broad speed range helped reduce yaw transients during acceleration through the low speed regime. Although the pilots appreciated conformality of flightpath and guidance symbols with the external scene during the approach, increased sensitivity of the symbols for lateral path tracking elevated the pilots' control activity in the presence of turbulence. The pilots preferred the choice of scaling that was originally established during the display development and in-flight evaluations.

Franklin, James A.↗

NASA NTRS1998

Secure Web-based Ground System User Interfaces over the Open Internet

A prototype has been developed which makes use of commercially available products in conjunction with the Java programming language to provide a secure user interface for command and control over the open Internet. This paper reports successful demonstration of: (1) Security over the Internet, including encryption and certification; (2) Integration of Java applets with a COTS command and control product; (3) Remote spacecraft commanding using the Internet. The Java-based Spacecraft Web Interface to Telemetry and Command Handling (Jswitch) ground system prototype provides these capabilities. This activity demonstrates the use and integration of current technologies to enable a spacecraft engineer or flight operator to monitor and control a spacecraft from a user interface communicating over the open Internet using standard World Wide Web (WWW) protocols and commercial off-the-shelf (COTS) products. The core command and control functions are provided by the COTS Epoch 2000 product. The standard WWW tools and browsers are used in conjunction with the Java programming technology. Security is provided with the current encryption and certification technology. This system prototype is a step in the direction of giving scientist and flight operators Web-based access to instrument, payload, and spacecraft data.

Langston, James H.↗

NASA NTRS2000

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

NASA NTRS2000

Reusable Launch Vehicle Control In Multiple Time Scale Sliding Modes

A reusable launch vehicle control problem during ascent is addressed via multiple-time scaled continuous sliding mode control. The proposed sliding mode controller utilizes a two-loop structure and provides robust, de-coupled tracking of both orientation angle command profiles and angular rate command profiles in the presence of bounded external disturbances and plant uncertainties. Sliding mode control causes the angular rate and orientation angle tracking error dynamics to be constrained to linear, de-coupled, homogeneous, and vector valued differential equations with desired eigenvalues placement. Overall stability of a two-loop control system is addressed. An optimal control allocation algorithm is designed that allocates torque commands into end-effector deflection commands, which are executed by the actuators. The dual-time scale sliding mode controller was designed for the X-33 technology demonstration sub-orbital launch vehicle in the launch mode. Simulation results show that the designed controller provides robust, accurate, de-coupled tracking of the orientation angle command profiles in presence of external disturbances and vehicle inertia uncertainties. This is a significant advancement in performance over that achieved with linear, gain scheduled control systems currently being used for launch vehicles.

Shtessel, Yuri↗

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 NTRS2002

Procedure for Tooth Contact Analysis of a Face Gear Meshing With a Spur Gear Using Finite Element Analysis

A procedure was developed to perform tooth contact analysis between a face gear meshing with a spur pinion using finite element analysis. The face gear surface points from a previous analysis were used to create a connected tooth solid model without gaps or overlaps. The face gear surface points were used to create a five tooth face gear Patran model (with rim) using Patran PCL commands. These commands were saved in a series of session files suitable for Patran input. A four tooth spur gear that meshes with the face gear was designed and constructed with Patran PCL commands. These commands were also saved in a session files suitable for Patran input. The orientation of the spur gear required for meshing with the face gear was determined. The required rotations and translations are described and built into the session file for the spur gear. The Abaqus commands for three-dimensional meshing were determined and verified for a simplified model containing one spur tooth and one face gear tooth. The boundary conditions, loads, and weak spring constraints were determined to make the simplified model work. The load steps and load increments to establish contact and obtain a realistic load was determined for the simplified two tooth model. Contact patterns give some insight into required mesh density. Building the two gears in two different local coordinate systems and rotating the local coordinate systems was verified as an easy way to roll the gearset through mesh. Due to limitation of swap space, disk space and time constraints of the summer period, the larger model was not completed.

Bibel, George↗

NASA NTRS2002

STS 107 Shuttle Press Kit: Providing 24/7 Space Science Research

Space shuttle mission STS-107, the 28th flight of the space shuttle Columbia and the 113th shuttle mission to date, will give more than 70 international scientists access to both the microgravity environment of space and a set of seven human researchers for 16 uninterrupted days. Columbia's 16-day mission is dedicated to a mixed complement of competitively selected and commercially sponsored research in the space, life and physical sciences. An international crew of seven, including the first Israeli astronaut, will work 24 hours a day in two alternating shifts to carry out experiments in the areas of astronaut health and safety; advanced technology development; and Earth and space sciences. When Columbia is launched from Kennedy Space Center's Launch Pad 39A it will carry a SPACEHAB Research Double Module (RDM) in its payload bay. The RDM is a pressurized environment that is accessible to the crew while in orbit via a tunnel from the shuttle's middeck. Together, the RDM and the middeck will accommodate the majority of the mission's payloads/experiments. STS-107 marks the first flight of the RDM, though SPACEHAB Modules and Cargo Carriers have flown on 17 previous space shuttle missions. Astronaut Rick Husband (Colonel, USAF) will command STS-107 and will be joined on Columbia's flight deck by pilot William 'Willie' McCool (Commander, USN). Columbia will be crewed by Mission Specialist 2 (Flight Engineer) Kalpana Chawla (Ph.D.), Mission Specialist 3 (Payload Commander) Michael Anderson (Lieutenant Colonel, USAF), Mission Specialist 1 David Brown (Captain, USN), Mission Specialist 4 Laurel Clark (Commander, USN) and Payload Specialist 1 Ilan Ramon (Colonel, Israeli Air Force), the first Israeli astronaut. STS-107 marks Husband's second flight into space - he served as pilot during STS-96, a 10-day mission that saw the first shuttle docking with the International Space Station. Husband served as Chief of Safety for the Astronaut Office until his selection to command the STS-107 crew. Anderson and Chawla will also be making their second spaceflights. Anderson first flew on STS-89 in January 1998 (the eighth Shuttle-Mir docking mission) while Chawla flew on STS-87 in November 1997 (the fourth U.S. Microgravity Payload flight). McCool, Brown, Clark and Ramon will be making their first flights into space.

Source record↗

NASA NTRS2003

TOPEX NASA Altimeter Operations Handbook, September 1992

This operations handbook identifies the commands for the NASA radar altimeter for the TOPEX/Poseidon spacecraft, defines the functions of these commands, and provides supplemental reference material for use by the altimeter operations personnel. The main emphasis of this document is placed on command types, command definitions, command sequences, and operational constraints. Additional document sections describe uploadable altimeter operating parameters, the telemetry stream data contents (for both the science and the engineering data), the Missions Operations System displays, and the spacecraft and altimeter health monitors.

Hancock, David W., III↗

NASA NTRS2004

Telescience Resource Kit Software Capabilities and Future Enhancements

The Telescience Resource Kit (TReK) is a suite of PC-based software applications that can be used to monitor and control a payload on board the International Space Station (ISS). This software provides a way for payload users to operate their payloads from their home sites. It can be used by an individual or a team of people. TReK provides both local ground support system services and an interface to utilize remote services provided by the Payload Operations Integration Center (POIC). by the POIC and to perform local data functions such as processing the data, storing it in local files, and forwarding it to other computer systems. TReK can also be used to build, send, and track payload commands. In addition to these features, work is in progress to add a new command management capability. This capability will provide a way to manage a multi- platform command environment that can include geographically distributed computers. This is intended to help those teams that need to manage a shared on-board resource such as a facility class payload. The environment can be configured such that one individual can manage all the command activities associated with that payload. This paper will provide a summary of existing TReK capabilities and a description of the new command management capability. For example, 7'ReK can be used to receive payload data distributed

Schneider, Michelle↗