Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Mission 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 1,207 records · Page 67
All sourcesNASA NTRSDOE OSTI
NASA NTRS1997

AMOS: Generic Planetary Mission Ops

The spacecraft control community is focusing increasing attention on various forms of architectures. Studies on software architectures and related technologies have been commissioned by DOD programs. The purpose of planning a series of annual workshops is to bring together participants working in the Spacecraft Ground System (SGS) domain. The overall intent of these workshops is to expedite the transition to common consensus-based open software architectures for SGSs.

workshops SGS technologies↗
NASA NTRS1974

Earth Observatory Satellite system definition study. Report 7: EOS system definition report

The Earth Observatory Satellite (EOS) study is summarized to show the modular design of a general purpose spacecraft, a mission peculiar segment which performs the EOS-A mission, an Operations Control Center, a Data Processing Facility, and a design for Low Cost Readout Stations. The study verified the practicality and feasibility of the modularized spacecraft with the capability of supporting many missions in the Earth Observation spectrum. The various subjects considered in the summary are: (1) orbit/launch vehicle tradeoff studies and recommendations, (2) instrument constraints and interfaces, (3) design/cost tradeoff and recommendations, (4) low cost management approach and recommendations, (5) baseline system description and specifications, and (6) space shuttle utilization and interfaces.

Source record↗
NASA NTRSDate not supplied

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗
NASA NTRSDate not supplied

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗
NASA NTRS2004

Hardware-In-The-Loop Testing of Continuous Control Algorithms for a Precision Formation Flying Demonstration Mission

A sample mission sequence is defined for a low earth orbit demonstration of Precision Formation Flying (PFF). Various guidance navigation and control strategies are discussed for use in the PFF experiment phases. A sample PFF experiment is implemented and tested in a realistic Hardware-in-the-Loop (HWIL) simulation using the Formation Flying Test Bed (FFTB) at NASA's Goddard Space Flight Center.

Naasz, Bo J.↗
NASA NTRS1973

The development and demonstration of hybrid programmable attitude control electronics

In the course of extended life attitude control system (ELACS) research sponsored by NASA a hybrid programable attitude control electronics (HYPACE) concept was developed and demonstrated. The wide variety of future planetary missions demanded a new control approach to accommodate the automatic fault tolerance and long the life requirements of such missions. HYPACE provides an adaptable, analog/digital design approach that permits preflight and in-flight accommodation of mission changes, component performance variations, and spacecraft changes, through programing. This enabled broad multimission flexibility of application in a cost effective manner. Previously, flight control computers have not been not flown on planetary missions because of weight and power problems. These problems were resolved in the design of HYPACE. The HYPACE design, which was demonstrated in breadboard form on a single-axis gas-bearing spacecraft simulation, uses a single control channel to perform the attitude control functions sequentially, thus significantly reducing the number of component parts over hard-wired designs.

Smith, L. S.↗
NASA NTRS1999

Mars Pathfinder and Mars Global Surveyor Outreach Compilation

This videotape is a compilation of the best NASA JPL (Jet Propulsion Laboratory) videos of the Mars Pathfinder and Mars Global Surveyor missions. The mission is described using animation and narration as well as some actual footage of the entire sequence of mission events. Included within these animations are the spacecraft orbit insertion; descent to the Mars surface; deployment of the airbags and instruments; and exploration by Sojourner, the Mars rover. JPL activities at spacecraft control during significant mission events are also included at the end. The spacecraft cameras pan the surrounding Mars terrain and film Sojourner traversing the surface and inspecting rocks. A single, brief, processed image of the Cydonia region (Mars face) at an oblique angle from the Mars Global Surveyor is presented. A description of the Mars Pathfinder mission, instruments, landing and deployment process, Mars approach, spacecraft orbit insertion, rover operation are all described using computer animation. Actual color footage of Sojourner as well as a 360 deg pan of the Mars terrain surrounding the spacecraft is provided. Lower quality black and white photography depicting Sojourner traversing the Mars surface and inspecting Martian rocks also is included.

Source record↗
NASA NTRS1990

An augmented MMS MACS for the Topex/Poseidon mission and beyond

The augmented Modular Attitude Control Subsystem (MACS) is described, with emphasis on the significant hardware modifications that have been incorporated into the Landsat MMS (Multimission Modular Spacecraft) MACS design to satisfy the Topex/Poseidon mission attitude control and determination requirements. Particular attention is given to a modification consisting in the addition of an earth pointing safe hold mode utilizing yaw coarse sun sensors to provide a yaw-slew capability for maintaining adequate illumination of the solar array. The design utility of this augmented MACS module for future spacecraft applications is pointed out.

Williams, R. J.↗
NASA NTRS1993

Cryogenic propellant thermal control system design considerations, analyses, and concepts applied to a Mars human exploration mission

This paper analyzes, defines, and sizes cryogenic storage thermal control systems that meet the requirements of future NASA Mars human exploration missions. The design issues of this system include the projection of the existing Multilayer Insulation data base for cryogenic storage to much thicker (10 cm or more) insulation systems, the unknown heat leak from mechanical interfaces, and the thermal and structural performance effects of the large tank sizes required for a Mars mission. Acknowledging these unknown effects, heat loss projections are made based on extrapolation of the existing data base. The results indicate that hydrogen, methane, and oxygen are feasible propellants, and that the best suited thermal control sytems are 'thick' MLI, thermodynamic vent sytems, cryocoolers, and vacuum jackets.

Plachta, David W.↗
NASA NTRS2018

Compact Low Power Avionics for the Europa Lander Concept and Other Missions to Ocean Worlds

This paper presents the results of NASA’s game-changing technology development entitled “Ultra Low Temperature Electronics” which represents a paradigm shift in spacecraft avionics development. The project has developed compact avionics technologies to address the Command & Data Handling (CDH), Power and Motor Control needs for mission concepts to ocean worlds such as a potential Europa Lander. We addressed this need by developing the key technologies necessary to develop a next generation compact avionics package. The key technologies that we developed significantly reduce the size, weight, power, and cost (SWAP-C) of the avionics package. These technologies will also allow extreme-environment missions to last longer in their environment by reducing the power and energy requirement to keep the avionics warm.

Bolotin, Gary↗
NASA NTRS1992

Fault tolerant capabilities of the Cosmic Background Explorer attitude control system

The Cosmic Background Explorer (COBE), which was launched November 18, 1989 from Vandenberg Air Force Base aboard a Delta rocket, has been classified by the scientific community as a major success with regards to the field of cosmology theory. Despite a number of anomalies which have occurred during the mission, the attitude control system (ACS) has performed remarkably well. This is due in large part to the fault tolerant capabilities that were designed into the ACS. A unique triaxial control system orientated in the spacecraft's transverse plane provides the ACS the ability to safely survive various sensor and actuator failures. Features that help to achieve this fail-operational system include component cross-strapping and autonomous control electronics switching. This design philosophy was of utmost importance because of the constraint placed upon the ACS to keep the spinning observatory and its cryogen-cooled science instruments pointing away from the sun. Even though the liquid helium was depleted within the expected twelve months from launch, it is still very much desirable to avoid any thermal disturbances upon the remaining functional instruments.

Placanica, Samuel J.↗
NASA NTRS1979

A review of Spacelab mission management approach

The Spacelab development program is a joint undertaking of the NASA and ESA. The paper addresses the initial concept of Spacelab payload mission management, the lessons learned, and modifications made as a result of the actual implementation of Spacelab Mission 1. The discussion covers mission management responsibilities, program control, science management, payload definition and interfaces, integrated payload mission planning, integration requirements, payload specialist training, payload and launch site integration, payload flight/mission operations, and postmission activities. After 3.5 years the outlined overall mission manager approach has proven to be most successful. The approach does allow the mission manager to maintain the lowest overall mission cost.

Craft, H. G., Jr.↗
NASA NTRS1999

A Preliminary Model for Spacecraft Propulsion Performance Analysis Based on Nuclear Gain and Subsystem Mass-Power Balances

A preliminary model for spacecraft propulsion performance analysis based on nuclear gain and subsystem mass-power balances are presented in viewgraph form. For very fast missions with straight-line trajectories, it has been shown that mission trip time is proportional to the cube root of alpha. Analysis of spacecraft power systems via a power balance and examination of gain vs. mass-power ratio has shown: 1) A minimum gain is needed to have enough power for thruster and driver operation; and 2) Increases in gain result in decreases in overall mass-power ratio, which in turn leads to greater achievable accelerations. However, subsystem mass-power ratios and efficiencies are crucial: less efficient values for these can partially offset the effect of nuclear gain. Therefore, it is of interest to monitor the progress of gain-limited subsystem technologies and it is also possible that power-limited systems with sufficiently low alpha may be competitive for such ambitious missions. Topics include Space flight requirements; Spacecraft energy gain; Control theory for performance; Mission assumptions; Round trips: Time and distance; Trip times; Vehicle acceleration; and Minimizing trip times.

Chakrabarti, Suman↗
NASA NTRS2001

Spacecraft Thermal Control

Thermal control of the spacecraft is typically achieved by removing heat from the spacecraft parts that tend to overheat and adding heat to the parts that tend get too cold. The equipment on the spacecraft can get very hot if it is exposed to the sun or have internal heat generation. The pans also can get very cold if they are exposed to the cold of deep space. The spacecraft and instruments must be designed to achieve proper thermal balance. The combination of the spacecraft's external thermal environment, its internal heat generation (i.e., waste heat from the operation of electrical equipment), and radiative heat rejection will determine this thermal balance. It should also be noted that this is seldom a static situation, external environmental influences and internal heat generation are normally dynamic variables which change with time. Topics discussed include thermal control system components, spacecraft mission categories, spacecraft thermal requirements, space thermal environments, thermal control hardware, launch and flight operations, advanced technologies for future spacecraft,

Birur, Gajanana C.↗
NASA NTRS2021

FRESCO: A Framework for Spacecraft Systems Autonomy

Achieving the science exploration and defense goals of the following decades will require flight systems capable of operations with limited operator contact, system mode changes and retasking based on sensor data, and complex robotic operations. To support these capabilities, increasingly autonomous flight systems are required that can perform dedicated mission functions, e.g. payload targeting and communications, and system-level functions, e.g. planning and goal monitoring. Architecting an autonomous system requires a well-reasoned, self-consistent framework to avoid \textit{ad hoc} design choices that will introduce complexity and risk. The Framework for Robust Execution and Scheduling of Commands On-Board, FRESCO, is the result of lessons learned in developing a software architecture to enable autonomous solar system exploration. FRESCO generalizes this work to offer a modular, software-agnostic approach to developing verifiable architecture for autonomous space systems. FRESCO specifies guiding principles, functions, interfaces, and interactions from which mission-specific autonomous control architectures can be derived. FRESCO is a principled framework relying on explicit, state-based goal definitions, centralized management of state knowledge, clearly separated control boundaries, and hierarchical reasoning. Using components from FRESCO reference architecture, an autonomous decision-making architecture can be designed for spacecraft which can then be mapped to flight software architecture. FRESCO is flexibly defined to enable autonomous control of flight systems built using extensive software and hardware heritage. Finally, FRESCO-derived architectures support a spectrum of operator/spacecraft interactions, ranging from traditional commanding to goal-driven commanding with the ability to change mission goals autonomously. FRESCO has been used in defining the autonomy architectures for the ASTERIA mission and have been demonstrated in laboratory and software simulation for small body rendezvous and in-space servicing missions.

Kolcio, Ksenia↗
NASA NTRS1985

Precision space structures

NASA large space structures efforts to date aimed towards large, flexible antenna-like structures (30-100M) with relatively long wavelengths (1-30cm) and moderate disturbances leading to some structure-control interaction. Potential missions in the OPTICS regime require small reflectors/mirrors, short wavelengths (visible to 100 microns), very tight tolerances in surface, alignment, pointing stability, as well as the potential of considerable on-board disturbances. For optics systems: figure/surface control can be quasi-static, active/passive isolation schemes are possible, vibration control is necessary, and the attitude control system can be low BW - Ground testing of reflectors and mirrors is more feasible than with antennas.

Soosaar, K.↗