Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “mission interfaces”

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 NTRS1973

Science sequence design

The activities of the following members of the Navigation Team are recorded: the Science Sequence Design Group, responsible for preparing the final science sequence designs; the Advanced Sequence Planning Group, responsible for sequence planning; and the Science Recommendation Team (SRT) representatives, responsible for conducting the necessary sequence design interfaces with the teams during the mission. The interface task included science support in both advance planning and daily operations. Science sequences designed during the mission are also discussed.

Koskela, P. E.↗
NASA NTRS1972

Atmosphere explorer missions C, D, and E. Spacecraft experiment interface definition study

The Atmosphere Explorer Missions C, D, & E Spacecraft/Experiment Interface Definition Study is discussed. The objectives of the study included an analysis of the accommodation requirements of the experiments for the three missions, an assessment of the overall effect of these requirements on the spacecraft system design and performance, and the detailed definition of all experiment/spacecraft electrical, mechanical, and environmental interfaces. In addition, the study included the identification and definition of system characteristics required to ensure compatibility with the consolidated STADAN and MSFN communications networks.

Source record↗
NASA NTRS2013

Hypersonic Inflatable Aerodynamic Decelerator (HIAD) Technology Development Overview

The successful flight of the Inflatable Reentry Vehicle Experiment (IRVE)-3 has further demonstrated the potential value of Hypersonic Inflatable Aerodynamic Decelerator (HIAD) technology. This technology development effort is funded by NASA's Space Technology Mission Directorate (STMD) Game Changing Development Program (GCDP). This paper provides an overview of a multi-year HIAD technology development effort, detailing the projects completed to date and the additional testing planned for the future. The effort was divided into three areas: Flexible Systems Development (FSD), Mission Advanced Entry Concepts (AEC), and Flight Validation. FSD consists of a Flexible Thermal Protection Systems (FTPS) element, which is investigating high temperature materials, coatings, and additives for use in the bladder, insulator, and heat shield layers; and an Inflatable Structures (IS) element which includes manufacture and testing (laboratory and wind tunnel) of inflatable structures and their associated structural elements. AEC consists of the Mission Applications element developing concepts (including payload interfaces) for missions at multiple destinations for the purpose of demonstrating the benefits and need for the HIAD technology as well as the Next Generation Subsystems element. Ground test development has been pursued in parallel with the Flight Validation IRVE-3 flight test. A larger scale (6m diameter) HIAD inflatable structure was constructed and aerodynamically tested in the National Full-scale Aerodynamics Complex (NFAC) 40ft by 80ft test section along with a duplicate of the IRVE-3 3m article. Both the 6m and 3m articles were tested with instrumented aerodynamic covers which incorporated an array of pressure taps to capture surface pressure distribution to validate Computational Fluid Dynamics (CFD) model predictions of surface pressure distribution. The 3m article also had a duplicate IRVE-3 Thermal Protection System (TPS) to test in addition to testing with the Aerocover configuration. Both the Aerocovers and the TPS were populated with high contrast targets so that photogrammetric solutions of the loaded surface could be created. These solutions both refined the aerodynamic shape for CFD modeling and provided a deformed shape to validate structural Finite Element Analysis (FEA) models. Extensive aerothermal testing has been performed on the TPS candidates. This testing has been conducted in several facilities across the country. The majority of the testing has been conducted in the Boeing Large Core Arc Tunnel (LCAT). HIAD is continuing to mature testing methodology in this facility and is developing new test sample fixtures and control methodologies to improve understanding and quality of the environments to which the samples are subjected. Additional testing has been and continues to be performed in the NASA LaRC 8ft High Temperature Tunnel, where samples up to 2ft by 2ft are being tested over representative underlying structures incorporating construction features such as sewn seams and through-thickness quilting. With the successful completion to the IRVE-3 flight demonstration, mission planning efforts are ramping up on the development of the HIAD Earth Atmospheric Reenty Test (HEART) which will demonstrate a relevant scale vehicle in relevant environments via a large-scale aeroshell (approximately 8.5m) entering at orbital velocity (approximately 7km/sec) with an entry mass on the order of 4MT. Also, the Build to Print (BTP) hardware built as a risk mitigation for the IRVE-3 project to have a "spare" ready to go in the event of a launch vehicle delivery failure is now available for an additional sub-orbital flight experiment. Mission planning is underway to define a mission that can utilize this existing hardware and help the HIAD project further mature this technology.

Hughes, Stephen J.↗
NASA NTRS2012

A Generalized Timeline Representation, Services, and Interface for Automating Space Mission Operations

Most use a timeline based representation for operations modeling. Most model a core set of state, resource types. Most provide similar capabilities on this modeling to enable (semi) automated schedule generation. In this paper we explore the commonality of : representation and services for these timelines. These commonalities offer potential to be harmonized to enable interoperability, re-use.

timeline-based systems↗
NASA NTRS2012

A Generalized Timeline Representation, Services, and Interface for Automating Space Mission Operations

Numerous automated and semi-automated planning & scheduling systems have been developed for space applications. Most of these systems are model-based in that they encode domain knowledge necessary to predict spacecraft state and resources based on initial conditions and a proposed activity plan. The spacecraft state and resources as often modeled as a series of timelines, with a timeline or set of timelines to represent a state or resource key in the operations of the spacecraft. In this paper, we first describe a basic timeline representation that can represent a set of state, resource, timing, and transition constraints. We describe a number of planning and scheduling systems designed for space applications (and in many cases deployed for use of ongoing missions) and describe how they do and do not map onto this timeline model.

Chien, Steve A.↗
NASA NTRS1978

Design concepts of the Shuttle mission simulator

The Shuttle mission simulator is designed to simulate all phases of the Space Shuttle mission from the last 30 minutes of countdown to launch, ascent, operations in orbit, deorbit, reentry, and landing with full participation by astronaut trainees and the mission control center. This paper reviews the design concepts of the simulator with attention given to the simulation hardware, crew stations, instructor/operator stations, digital computers, flight computer simulation interface device, mission control center interface, visual systems, aural cue system, mathematical modeling, digital computer complex, motion system, and the payload accommodation system.

Bird, J. D.↗
NASA NTRS1991

Telecommunications, navigation and information management concept overview for the Space Exploration Initiative program

An overview is provided of the Space Exploration Initiative (SEI) concepts for telecommunications, information systems, and navigation (TISN), and engineering and architecture issues are discussed. The SEI program data system is reviewed to identify mission TISN interfaces, and reference TISN concepts are described for nominal, degraded, and mission-critical data services. The infrastructures reviewed include telecommunications for robotics support, autonomous navigation without earth-based support, and information networks for tracking and data acquisition. Four options for TISN support architectures are examined which relate to unique SEI exploration strategies. Detailed support estimates are given for: (1) a manned stay on Mars; (2) permanent lunar and Martian settlements; short-duration missions; and (4) systematic exploration of the moon and Mars.

Bell, Jerome A.↗
NASA NTRS2016

Use of Model Payload for Europa Mission Development

This paper discusses the basis for the Model Payload and how it was used to develop the mission design, observation and data acquisition strategy, needed spacecraft capabilities, spacecraft-payload interface needs, mission system requirements and operational scenarios.

Lewis, Kari↗
NASA NTRS2016

Propellant Savings during Soyuz Undock from the International Space Station

As a vehicle continuously orbiting Earth for over a decade, the International Space Station (ISS) must be conscious of ways to conserve consumables to maximize the efficiency of cargo flights to ISS. One such consumable is propellant. As part of an ongoing effort to minimize propellant usage onboard ISS and use control moment gyroscopes as much as possible for ISS control, an effort was made in late 2014 to allow Soyuz manned vehicle undockings without requiring the use of thrusters. This method, which has been used for four Soyuz undockings, saves up to 160 kg of propellant each year. Fiona completed a B.S. is Mechanical Engienering at Washington University in St. Louis in 2009, after which she moved to Houston, TX to begin working at NASA Johnson Space Center. She currently works in the Flight Operations Directorate as an ADCO (Attitude Determination and Control Officer) flight controller and MCG (Motion Control Group) instructor. Her responsibilities include operating the motion control systems of the ISS in Mission Control, interfacing with Russian colleagues, mentoring and teaching flight controller trainees, and training astronauts for their missions to ISS.

Turett, Fiona↗
NASA NTRS2012

Mars Express Forward Link Capabilities for the Mars Relay Operations Service (MaROS)

This software provides a new capability for landed Mars assets to perform forward link relay through the Mars Express (MEX) European Union orbital spacecraft. It solves the problem of standardizing the relay interface between lander missions and MEX. The Mars Operations Relay Service (MaROS) is intended as a central point for relay planning and post-pass analysis for all Mars landed and orbital assets. Through the first two phases of implementation, MaROS supports relay coordination through the Odyssey orbiter and the Mars Reconnaissance Orbiter (MRO). With this new software, MaROS now fully integrates the Mars Express spacecraft into the relay picture. This new software generates and manages a new set of file formats that allows for relay request to MEX for forward and return link relay, including the parameters specific to MEX. Existing MEX relay planning interactions were performed via email exchanges and point-to-point file transfers. By integrating MEX into MaROS, all transactions are managed by a centralized service for tracking and analysis. Additionally, all lander missions have a single, shared interface with MEX and do not have to integrate on a mission-by mission basis. Relay is a critical element of Mars lander data management. Landed assets depend largely upon orbital relay for data delivery, which can be impacted by the availability and health of each orbiter in the network. At any time, an issue may occur to prevent relay. For this reason, it is imperative that all possible orbital assets be integrated into the overall relay picture.

Allard, Daniel A.↗
NASA NTRS2008

G-Guidance Interface Design for Small Body Mission Simulation

The G-Guidance software implements a guidance and control (G and C) algorithm for small-body, autonomous proximity operations, developed under the Small Body GN and C task at JPL. The software is written in Matlab and interfaces with G-OPT, a JPL-developed optimization package written in C that provides G-Guidance with guaranteed convergence to a solution in a finite computation time with a prescribed accuracy. The resulting program is computationally efficient and is a prototype of an onboard, real-time algorithm for autonomous guidance and control. Two thruster firing schemes are available in G-Guidance, allowing tailoring of the software for specific mission maneuvers. For example, descent, landing, or rendezvous benefit from a thruster firing at the maneuver termination to mitigate velocity errors. Conversely, ascent or separation maneuvers benefit from an immediate firing to avoid potential drift toward a second body. The guidance portion of this software explicitly enforces user-defined control constraints and thruster silence times while minimizing total fuel usage. This program is currently specialized to small-body proximity operations, but the underlying method can be generalized to other applications.

Acikmese, Behcet↗
NASA NTRS2015

Standardized Modular Power Interfaces for Future Space Explorations Missions

Earlier studies show that future human explorations missions are composed of multi-vehicle assemblies with interconnected electric power systems. Some vehicles are often intended to serve as flexible multi-purpose or multi-mission platforms. This drives the need for power architectures that can be reconfigured to support this level of flexibility. Power system developmental costs can be reduced, program wide, by utilizing a common set of modular building blocks. Further, there are mission operational and logistics cost benefits of using a common set of modular spares. These benefits are the goals of the Advanced Exploration Systems (AES) Modular Power System (AMPS) project. A common set of modular blocks requires a substantial level of standardization in terms of the Electrical, Data System, and Mechanical interfaces. The AMPS project is developing a set of proposed interface standards that will provide useful guidance for modular hardware developers but not needlessly constrain technology options, or limit future growth in capability. In 2015 the AMPS project focused on standardizing the interfaces between the elements of spacecraft power distribution and energy storage. The development of the modular power standard starts with establishing mission assumptions and ground rules to define design application space. The standards are defined in terms of AMPS objectives including Commonality, Reliability-Availability, Flexibility-Configurability and Supportability-Reusability. The proposed standards are aimed at assembly and sub-assembly level building blocks. AMPS plans to adopt existing standards for spacecraft command and data, software, network interfaces, and electrical power interfaces where applicable. Other standards including structural encapsulation, heat transfer, and fluid transfer, are governed by launch and spacecraft environments and bound by practical limitations of weight and volume. Developing these mechanical interface standards is more difficult but an essential part of defining physical building blocks of modular power. This presentation describes the AMPS projects progress towards standardized modular power interfaces.

Spacecraft Power↗
NASA NTRS2014

OPALS: Mission System Operations Architecture for an Optical Communications Demonstration on the ISS

In spring 2014, the Optical PAyload for Lasercomm Science (OPALS) will launch to the International Space Station (ISS) to demonstrate space-to-ground optical communications. During a 90-day baseline mission, OPALS will downlink high quality, short duration videos to the Optical Communications Telescope Laboratory (OCTL) in Wrightwood, California. To achieve mission success, interfaces to the ISS payload operations infrastructure are established. For OPALS, the interfaces facilitate activity planning, hazardous laser operations, commanding, and telemetry transmission. In addition, internal processes such as pointing prediction and data processing satisfy the technical requirements of the mission. The OPALS operations team participates in Operational Readiness Tests (ORTs) with external partners to exercise coordination processes and train for the overall mission. The tests have provided valuable insight into operational considerations on the ISS.

Abrahamson, Matthew J.↗
NASA NTRS1974

Viking '79 Rover study. Volume 1: Summary report

The results of a study to define a roving vehicle suitable for inclusion in a 1979 Viking mission to Mars are presented. The study focused exclusively on the 1979 mission incorporating a rover that would be stowed on and deployed from a modified Viking lander. The overall objective of the study was to define a baseline rover, the lander/rover interfaces, a mission operations concept, and a rover development program compatible with the 1979 launch opportunity. During the study, numerous options at the rover system and subsystem levels were examined and a baseline configuration was selected. Launch vehicle, orbiter, and lander performance capabilities were examined to ensure that the baseline rover could be transported to Mars using minimum-modified Viking '75 hardware and designs.

Source record↗
NASA NTRS2022

International Space Power System Interoperability Standards (ISPSIS)

This International Space Power System Interoperability Standards(ISPSIS) is the result of collaborations within the International Space Station (ISS) and Gateway memberships to establish interoperable interfaces, terminology, and techniques, to facilitate collaborative endeavors of space exploration in cislunar and deep space environments. These standards are available for international and commercial partnerships. Standards that are established and internationally recognized have been selected where possible to enable a variety of providers. Increasing hardware commonality among providers while decreasing unique configurations has the potential to reduce the traditional barriers in space exploration: overall mass and volume required to execute a mission. Standardizing interfaces reduces the scope of the development effort. The information within this document represents a set of parameters, which if accommodated in the system architecture support greater efficiencies, promote cost savings, and increase the probability of mission success. These standards are not intended to specify system details needed for implementation nor do they dictate design features behind the interface; specific requirements will be defined in unique documents.

David James Sadey↗