Search NASA⌕ Search

SEARCH · Search NASA

Results for “operations spacecraft control”

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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

Lessons Learned from Engineering a Multi-Mission Satellite Operations Center

NASA's Small Explorers (SMEX) satellites have surpassed their designed science-lifetimes and their flight operations teams are now facing the challenge of continuing operations with reduced funding. At present, these missions are being re-engineered into a fleet-oriented ground system at Goddard Space Flight Center (GSFC). When completed, this ground system will provide command and control of four SMEX missions and will demonstrate fleet automation and control concepts. As a path-finder for future mission consolidation efforts, this ground system will also demonstrate new ground-based technologies that show promise of supporting longer mission lifecycles and simplifying component integration. One of the core technologies being demonstrated in the SMEX Mission Operations Center is the GSFC Mission Services Evolution Center (GMSEC) architecture. The GMSEC architecture uses commercial Message Oriented Middleware with a common messaging standard to realize a higher level of component interoperability, allowing for interchangeable components in ground systems. Moreover, automation technologies utilizing the GMSEC architecture are being evaluated and implemented to provide extended lights-out operations. This mode of operation will provide routine monitoring and control of the heterogeneous spacecraft fleet. The operational concepts being developed will reduce the need for staffed contacts and is seen as a necessity for fleet management. This paper will describe the experiences of the integration team throughout the re-enginering effort of the SMEX ground system. Additionally, lessons learned will be presented based on the team's experiences with integrating multiple missions into a fleet-automated ground system.

Madden, Maureen↗
NASA NTRS2012

General Purpose Data-Driven System Monitoring for Space Operations

Modern space propulsion and exploration system designs are becoming increasingly sophisticated and complex. Determining the health state of these systems using traditional methods is becoming more difficult as the number of sensors and component interactions grows. Data-driven monitoring techniques have been developed to address these issues by analyzing system operations data to automatically characterize normal system behavior. The Inductive Monitoring System (IMS) is a data-driven system health monitoring software tool that has been successfully applied to several aerospace applications. IMS uses a data mining technique called clustering to analyze archived system data and characterize normal interactions between parameters. This characterization, or model, of nominal operation is stored in a knowledge base that can be used for real-time system monitoring or for analysis of archived events. Ongoing and developing IMS space operations applications include International Space Station flight control, spacecraft vehicle system health management, launch vehicle ground operations, and fleet supportability. As a common thread of discussion this paper will employ the evolution of the IMS data-driven technique as related to several Integrated Systems Health Management (ISHM) elements. Thematically, the projects listed will be used as case studies. The maturation of IMS via projects where it has been deployed or is currently being integrated to aid in fault detection will be described. The paper will also explain how IMS can be used to complement a suite of other ISHM tools, providing initial fault detection support for diagnosis and recovery

Space Propulsion↗
NASA NTRS1999

Results of Liquid Motion Experiment Analyzed

About half of all scientific and commercial spacecraft spin during some part of their mission. Although spinning has many benefits (increasing stability, controlling the location of liquid propellants, and distributing solar heat loads), it also creates problems because a precession (or wobble) motion is unavoidable. For modern spacecraft, by far the largest source of wobble is energy dissipation in the liquid of partially filled tanks. The liquid s energy dissipation cannot, however, be quantified adequately by any ground test. Current analytical models are also inadequate because fundamental data on fluid motion in low gravity are needed to validate them. Consequently, spacecraft attitude-control systems are designed and operated very conservatively. Nonetheless, spacecraft often still perform poorly in orbit, and some have been lost because of a rapid increase of the wobble rate. The Liquid Motion Experiment (LME) was designed to provide spacecraft designers accurate data on the wobble dynamics of spacecraft that contain large quantities of mobile liquids. LME, which was flown on the space shuttle mission STS-84, was built under contract to the NASA Lewis Research Center by the Southwest Research Institute of San Antonio, Texas. Major accomplishments for 1998 include reduction of the flight data and publication of the experimental results. LME was essentially a spin table that created a realistic nutation motion of scale-model tanks containing liquid. Two spherical and two cylindrical transparent tanks were tested simultaneously, and three sets of such tanks were employed to vary liquid viscosity, fill level, and propellant management device (PMD) design. All the tanks were approximately 4.5 in. in diameter. The primary test measurements were the radial and tangential torques exerted on the tanks by the liquid. These torques could not be measured on the ground because of the masking effects of gravity.

Chato, David J.↗
NASA NTRS2012

Spacecraft/Rover Hybrids for the Exploration of Small Solar System Bodies: NASA NIAC - Phase I Study

This study investigated a novel mission architecture for the systematic and affordable in-situ exploration of small Solar System bodies. Specifically, a mother spacecraft would deploy over the surface of a small body one, or several, spacecraft/rover hybrids, which are small, multi-faceted enclosed robots with internal actuation and external spikes. They would be capable of 1) long excursions (by hopping), 2) short traverses to specific locations (through a sequence of controlled tumbles), and 3) high-altitude, attitude-controlled ballistic flight (akin to spacecraft flight). Their control would rely on synergistic operations with the mother spacecraft (where most of hybrids' perception and localization functionalities would be hosted), which would make the platforms minimalistic and, in turn, the entire mission architecture affordable.

Mobility↗
NASA NTRS2004

CCSDS Spacecraft Monitor and Control Service Framework

This CCSDS paper presents a reference architecture and service framework for spacecraft monitoring and control. It has been prepared by the Spacecraft Monitoring and Control working group of the CCSDS Mission Operations and Information Management Systems (MOIMS) area. In this context, Spacecraft Monitoring and Control (SM&C) refers to end-to-end services between on- board or remote applications and ground-based functions responsible for mission operations. The scope of SM&C includes: 1) Operational Concept: definition of an operational concept that covers a set of standard operations activities related to the monitoring and control of both ground and space segments. 2) Core Set of Services: definition of an extensible set of services to support the operational concept together with its information model and behaviours. This includes (non exhaustively) ground systems such as Automatic Command and Control, Data Archiving and Retrieval, Flight Dynamics, Mission Planning and Performance Evaluation. 3) Application-layer information: definition of the standard information set to be exchanged for SM&C purposes.

Merri, Mario↗
NASA NTRS1994

Operator procedure verification with a rapidly reconfigurable simulator

Generating and testing procedures for controlling spacecraft subsystems composed of electro-mechanical and computationally realized elements has become a very difficult task. Before a spacecraft can be flown, mission controllers must envision a great variety of situations the flight crew may encounter during a mission and carefully construct procedures for operating the spacecraft in each possible situation. If, despite extensive pre-compilation of control procedures, an unforeseen situation arises during a mission, the mission controller must generate a new procedure for the flight crew in a limited amount of time. In such situations, the mission controller cannot systematically consider and test alternative procedures against models of the system being controlled, because the available simulator is too large and complex to reconfigure, run, and analyze quickly. A rapidly reconfigurable simulation environment that can execute a control procedure and show its effects on system behavior would greatly facilitate generation and testing of control procedures both before and during a mission. The How Things Work project at Stanford University has developed a system called DME (Device Modeling Environment) for modeling and simulating the behavior of electromechanical devices. DME was designed to facilitate model formulation and behavior simulation of device behavior including both continuous and discrete phenomena. We are currently extending DME for use in testing operator procedures, and we have built a knowledge base for modeling the Reaction Control System (RCS) of the space shuttle as a testbed. We believe that DME can facilitate design of operator procedures by providing mission controllers with a simulation environment that meets all these requirements.

Iwasaki, Yumi↗
NASA NTRS2012

CoNNeCT Baseband Processor Module Boot Code SoftWare (BCSW)

This software provides essential startup and initialization routines for the CoNNeCT baseband processor module (BPM) hardware upon power-up. A command and data handling (C&DH) interface is provided via 1553 and diagnostic serial interfaces to invoke operational, reconfiguration, and test commands within the code. The BCSW has features unique to the hardware it is responsible for managing. In this case, the CoNNeCT BPM is configured with an updated CPU (Atmel AT697 SPARC processor) and a unique set of memory and I/O peripherals that require customized software to operate. These features include configuration of new AT697 registers, interfacing to a new HouseKeeper with a flash controller interface, a new dual Xilinx configuration/scrub interface, and an updated 1553 remote terminal (RT) core. The BCSW is intended to provide a "safe" mode for the BPM when initially powered on or when an unexpected trap occurs, causing the processor to reset. The BCSW allows the 1553 bus controller in the spacecraft or payload controller to operate the BPM over 1553 to upload code; upload Xilinx bit files; perform rudimentary tests; read, write, and copy the non-volatile flash memory; and configure the Xilinx interface. Commands also exist over 1553 to cause the CPU to jump or call a specified address to begin execution of user-supplied code. This may be in the form of a real-time operating system, test routine, or specific application code to run on the BPM.

Yamamoto, Clifford K.↗
NASA NTRS1975

Digital computer control of a 30-cm mercury ion thruster

The major objective was to define the exact role of an onboard spacecraft computer in the control of ion thrusters. An initial computer control system with accurate high speed capability was designed, programmed, and tested with the computer as the sole control element for an operating ion thruster. The command functions and a code format for a spacecraft digital control system were established. A second computer control system was constructed to operate with these functions and format. A throttle program sequence was established and tested. A two thruster array was tested with these computer control systems and the results reported.

Low, C. A., Jr.↗
NASA NTRS1975

Digital computer control of a 30 cm mercury ion thruster

The major objective of this program was to define the exact role of an on-board spacecraft computer in the control of ion thrusters. An initial computer control system with accurate high speed capability was designed, programmed, and tested with the computer as the sole control element for an operating ion thruster. The command functions and a code format for a spacecraft digital control system were established. A second computer control system was constructed to operate with these functions and format. A throttle program sequence was established and tested. A two thruster array was tested with these computer control systems and the results reported.

Low, C. A., Jr.↗
NASA NTRS2002

Timeliner: Automating Procedures on the ISS

Timeliner has been developed as a tool to automate procedural tasks. These tasks may be sequential tasks that would typically be performed by a human operator, or precisely ordered sequencing tasks that allow autonomous execution of a control process. The Timeliner system includes elements for compiling and executing sequences that are defined in the Timeliner language. The Timeliner language was specifically designed to allow easy definition of scripts that provide sequencing and control of complex systems. The execution environment provides real-time monitoring and control based on the commands and conditions defined in the Timeliner language. The Timeliner sequence control may be preprogrammed, compiled from Timeliner "scripts," or it may consist of real-time, interactive inputs from system operators. In general, the Timeliner system lowers the workload for mission or process control operations. In a mission environment, scripts can be used to automate spacecraft operations including autonomous or interactive vehicle control, performance of preflight and post-flight subsystem checkouts, or handling of failure detection and recovery. Timeliner may also be used for mission payload operations, such as stepping through pre-defined procedures of a scientific experiment.

Brown, Robert↗
NASA NTRS2008

Proven and Robust Ground Support Systems - GSFC Success and Lessons Learned

Over the past fifteen years, Goddard Space Flight Center has developed several successful science missions in-house: the Wilkinson Microwave Anisotropy Probe (WMAP), the Imager for Magnetopause-to-Aurora Global Exploration (IMAGE), the Earth Observing 1 (EO-1) [1], and the Space Technology 5 (ST-5)[2] missions, several Small Explorers, and several balloon missions. Currently in development are the Solar Dynamics Observatory (SDO) [3] and the Lunar Reconnaissance Orbiter (LRO)[4]. What is not well known is that these missions have been supported during spacecraft and/or instrument integration and test, flight software development, and mission operations by two in house satellite Telemetry and Command (T & C) Systems, the Integrated Test and Operations System (ITOS) and the Advanced Spacecraft Integration and System Test (ASIST). The advantages of an in-house satellite Telemetry and Command system are primarily in the flexibility of management and maintenance - the developers are considered a part of the mission team, get involved early in the development process of the spacecraft and mission operations-control center, and provide on-site, on-call support that goes beyond Help Desk and simple software fixes. On the other hand, care must be taken to ensure that the system remains generic enough for cost effective re-use from one mission to the next. The software is designed such that many features are user-configurable. Where user-configurable options were impractical, features were designed so as to be easy for the development team to modify. Adding support for a new ground message header, for example, is a one-day effort because of the software framework on which that code rests. This paper will discuss the many features of the Goddard satellite Telemetry and Command systems that have contributed to the success of the missions listed above. These features include flexible user interfaces, distributed parallel commanding and telemetry decommutation, a procedure language, the interfaces and tools needed for a high degree of automation, and instantly accessible archives of spacecraft telemetry. It will discuss some of the problems overcome during development, including secure commanding over networks or the Internet, constellation support for the three satellites that comprise the ST-5 mission, and geographically distributed telemetry end users.

Pfarr, Barbara↗
NASA NTRS1969

Biosatellite II mission

Biosatellite B was launched from Cape Kennedy, Florida, on a two-stage DELTA launch vehicle at 6:04 p.m. on 7 September, 1967. Approximately nine minutes later the 435 kg spacecraft biological laboratory was placed into a satisfactory 315 km near-circular earth orbit, successfully separated from the launch vehicle's second stage and was designated Biosatellite II. The scientific payload consisting of thirteen selected general biology and radiation experiments were subjected to planned, carefully controlled environmental conditions during 45 hours of earth-orbital flight. The decision was made to abbreviate the scheduled 3-day mission by approximately one day because of a threatening tropical storm in the recovery area, and a problem of communication with the spacecraft from the tracking stations. Highest priority was placed on recovery which was essential to obtain the scientific results on all the experiments. The operational phase of the mission came to a successful conclusion with the deorbit of the recovery capsule, deployment of the parachute system and air recovery by the United States Air Force. The 127 kg recovery capsule was returned to biology laboratories at Hickam Air Force Base, Hawaii, for disassembly and immediate inspection and analysis of the biological materials by the experimenters. It was evident immediately that the quality of the biology was excellent and this fact gave promise of a high return of scientific data. The environmental conditions provided to the experimental material in the spacecraft, provisions for experimental controls, and operational considerations are presented as they relate to interpretation of the experimental results.

Biosatellite 2 Project↗
NASA NTRS1978

Spacecraft charging control by thermal, field emission with lanthanum-hexaboride emitters

Thermal, field emitters of lanthanum (or perhaps cerium) hexaboride (LaB6) with temperature variability up to about 1500K are suggested for spacecraft charging control. Such emitters operate at much lower voltages with considerably more control and add plasma-diagnostic versatility. These gains should outweigh the additional complexity of providing heat for the LaB6 thermal, field emitter.

Morris, J. F.↗
NASA NTRS1994

Space/ground systems as cooperating agents

Within NASA and the European Space Agency (ESA) it is agreed that autonomy is an important goal for the design of future spacecraft and that this requires on-board artificial intelligence. NASA emphasizes deep space and planetary rover missions, while ESA considers on-board autonomy as an enabling technology for missions that must cope with imperfect communications. ESA's attention is on the space/ground system. A major issue is the optimal distribution of intelligent functions within the space/ground system. This paper describes the multi-agent architecture for space/ground systems (MAASGS) which would enable this issue to be investigated. A MAASGS agent may model a complete spacecraft, a spacecraft subsystem or payload, a ground segment, a spacecraft control system, a human operator, or an environment. The MAASGS architecture has evolved through a series of prototypes. The paper recommends that the MAASGS architecture should be implemented in the operational Dutch Utilization Center.

Grant, T. J.↗
NASA NTRS1997

Applied Research Study

The purpose of this project was to study the feasibility of reusing major components of a software system that had been used to control the operations of a spacecraft launched in the 1980s. The study was done in the context of a ground data processing system that was to be rehosted from a large mainframe to an inexpensive workstation. The study concluded that a systematic approach using inexpensive tools could aid in the reengineering process by identifying a set of certified reusable components. The study also developed procedures for determining duplicate versions of software, which were created because of inadequate naming conventions. Such procedures reduced reengineering costs by approximately 19.4 percent.

Leach, Ronald J.↗
NASA NTRS1998

Automating Mission Scheduling for Space-Based Observatories

In this paper we describe the use of our planning and scheduling framework, HSTS, to reduce the complexity of science mission planning. This work is part of an overall project to enable a small team of scientists to control the operations of a spacecraft. The present process is highly labor intensive. Users (scientists and operators) rely on a non-codified understanding of the different spacecraft subsystems and of their operating constraints. They use a variety of software tools to support their decision making process. This paper considers the types of decision making that need to be supported/automated, the nature of the domain constraints and the capabilities needed to address them successfully, and the nature of external software systems with which the core planning/scheduling engine needs to interact. HSTS has been applied to science scheduling for EUVE and Cassini and is being adapted to support autonomous spacecraft operations in the New Millennium initiative.

Pell, Barney↗
NASA NTRSDate not supplied

Final Report of the COSPAR Meeting Series on Knowledge Gaps in Planetary Protection for Crewed Missions to Mars

The international scientific community has, through a Committee on Space Research (COSPAR) meeting series, participated in a seven-year review of knowledge gaps in planetary protection for crewed missions to Mars. This meeting series first identified a prioritized list of knowledge gaps that, if addressed, would permit development of an implementable planetary protection policy for the initial crewed Mars mission. Next, a consideration of the available venues (ground, LEO, deep space, planetary surfaces) yielded a roadmap of potential future investigations needed to close the knowledge gaps. Finally, the meeting series evaluated topic-specific measurements that are essential to establishing the figures of merit needed for hardware engineering design requirements. The three main topic threads considered within the meeting series were: microbial and human health monitoring; natural transport of terrestrial biological contamination on Mars, and; technologies and operations for contamination control (of spacecraft systems). Participants at the meeting series included engineers, scientists, managers and various subject matter experts from space agencies, academic and research institutions, commercial companies, and other government departments. This paper provides a detailed summary review of the findings of the meeting series, including descriptions of the basis for each of the figures of merit (where they were identified), and considerations of how planetary protection implementation and policy for crewed missions may progress from the current state of the art.

J Andy Spry↗