Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Ground Support System”

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 757 records · Page 42

Customizing the JPL Multimission Ground Data System: Lessons learned

The Multimission Ground Data System (MGDS) at NASA's Jet Propulsion Laboratory has brought improvements and new technologies to mission operations. It was designed as a generic data system to meet the needs of multiple missions and avoid re-inventing capabilities for each new mission and thus reduce costs. It is based on adaptable tools that can be customized to support different missions and operations scenarios. The MGDS is based on a distributed client/server architecture, with powerful Unix workstations, incorporating standards and open system architectures. The distributed architecture allows remote operations and user science data exchange, while also providing capabilities for centralized ground system monitor and control. The MGDS has proved its capabilities in supporting multiple large-class missions simultaneously, including the Voyager, Galileo, Magellan, Ulysses, and Mars Observer missions. The Operations Engineering Lab (OEL) at JPL has been leading Customer Adaptation Training (CAT) teams for adapting and customizing MGDS for the various operations and engineering teams. These CAT teams have typically consisted of only a few engineers who are familiar with operations and with the MGDS software and architecture. Our experience has provided a unique opportunity to work directly with the spacecraft and instrument operations teams and understand their requirements and how the MGDS can be adapted and customized to minimize their operations costs. As part of this work, we have developed workstation configurations, automation tools, and integrated user interfaces at minimal cost that have significantly improved productivity. We have also proved that these customized data systems are most successful if they are focused on the people and the tasks they perform and if they are based upon user confidence in the development team resulting from daily interactions. This paper will describe lessons learned in adapting JPL's MGDS to fly the Voyager, Galileo, and Mars Observer missions. We will explain how powerful, existing ground data systems can be adapted and packaged in a cost effective way for operations of small and large planetary missions. We will also describe how the MGDS was adapted to support operations within the Galileo Spacecraft Testbed. The Galileo testbed provided a unique opportunity to adapt MGDS to support command and control operations for a small autonomous operations team of a handful of engineers flying the Galileo Spacecraft flight system model.

Murphy, Susan C.↗

Evolution of NASA's Near-Earth Tracking and Data Relay Satellite System (TDRSS)

NASA's Tracking and Data Relay Satellite System (TDRSS) is now in its 23rd year of operations and its spacecraft fleet includes three second-generation spacecraft launched since the year 2000; a figure illustrates the first generation TDRSS spacecraft. During this time frame the TDRSS has provided communications relay support to a broad range of missions, with emphasis on low-earth-orbiting (LEO) spacecraft that include unmanned science spacecraft (e.g., Hubble Space Telescope), and human spaceflight (Space Shuttle and Space Station). Furthermore, the TDRSS has consistently demonstrated its uniqueness and adaptability in several ways. First, its S- and K-band services, combined with its multi-band/steerable single-access (SA) antennas and ground-based configuration flexibility, have permitted the mission set to expand to unique users such as scientific balloons and launch vehicles. Second, the bent-pipe nature of the system has enabled the introduction of new/improved services via technology insertion and upgrades at each of the ground terminals; a specific example here is the Demand Access Service (DAS), which, for example, is currently providing science-alert support to NASA science missions Third, the bent-pipe nature of the system, combined with the flexible ground-terminal signal processing architecture has permitted the demonstration/vaIidation of new techniques/services/technologies via a real satellite channel; over the past 10+ years these have, for example, included demonstrations/evaluations of emerging modulation/coding techniques. Given NASA's emerging Exploration plans, with missions beginning later this decade and expanding for decades to come, NASA is currently planning the development of a seamless, NASA-wide architecture that must accommodate missions from near-earth to deep space. Near-earth elements include Ground-Network (GN) and Near-Earth Relay (NER) components and both must efficiently and seamlessly support missions that encompass: earth orbit, including dedicated science missions and lunar support/cargo vehicles; earth/moon transit; lunar in-situ operations; and other missions within approximately 2 million km of earth (e.g., at the sun/earth libration points). Given that the NER is an evolution of TDRSS, one element of this NASA-wide architecture development activity is a trade study of future NER architecture candidates. The present paper focuses on trade study aspects associated with the NER, highlights study elements, and provides representative interim results.

Flaherty, Roger↗

Flight Experiment Demonstration System (FEDS) functional description and interface document

This document presents a functional description of the Flight Experiment Demonstration System (FEDS) and of interfaces between FEDS and external hardware and software. FEDS is a modification of the Automated Orbit Determination System (AODS). FEDS has been developed to support a ground demonstration of microprocessor-based onboard orbit determination. This document provides an overview of the structure and logic of FEDS and details the various operational procedures to build and execute FEDS. It also documents a microprocessor interface between FEDS and a TDRSS user transponder and describes a software simulator of the interface used in the development and system testing of FEDS.

Belcher, R. C.↗

Advanced Composite Solar Sail System (ACS3): Mechanisms and Lessons Learned from a CubeSat Solar Sail Deployer

This is an overview of the National Aeronautics and Space Administration (NASA) Advanced Composite Solar Sail System (ACS3) technology demonstration project mechanisms, their development, the testing they underwent, as well as the lessons learned in those activities. This overview includes an overall description of the primary deployment mechanisms and ground support equipment (GSE) needed for packaging the solar sail system.

Mechanisms↗

Advanced Composite Solar Sail System (ACS3): Mechanisms and Lessons Learned from a CubeSat Solar Sail Deployer

This is an overview of the National Aeronautics and Space Administration (NASA) Advanced Composite Solar Sail System (ACS3) technology demonstration project mechanisms, their development, the testing they underwent, as well as the lessons learned in those activities. This overview includes an overall description of the primary deployment mechanisms and ground support equipment (GSE) needed for packaging the solar sail system.

Mechanisms↗

Defining Pupil Knowledge Requirements for Roman Space Telescope Integrated Payload Assembly Testing

This thesis examines the use of phase retrieval to characterize an optical system under testing conditions with pupil knowledge error. The purpose of this research is to define pupil knowledge requirements for the integrated payload testing of the Roman Space Telescope (RST). I have conducted a Monte Carlo study to determine how uncertainty in the location of the ground support equipment relative to the payload will affect the ability to use image-based wavefront sensing during the test to characterize system alignment. This test will be conducted in the Space Environment Simulator (SES) with the presence of Wavefront Error (WFE) due to gravity sag on the primary mirror. In this study, I incrementally decentered a piece of ground support equipment, the SubAperture Metrology System (SAMS), and evaluated how the phase retrieval algorithm attempted to fit the wavefront with the pupil mismatch. The results of this study are a factor in the overall Integrated Payload Assembly (IPA) testing WFE budget.

Roman Space Telescope↗

Formulation of detailed consumables management models for the development (preoperational) period of advanced space transportation system: Executive summary

Formulation of models required for the mission planning and scheduling function and establishment of the relation of those models to prelaunch, onboard, ground support, and postmission functions for the development phase of space transportation systems (STS) was conducted. The preoperational space shuttle is used as the design baseline for the subject model formulations. Analytical models were developed which consist of a mission planning processor with appropriate consumables data base and a method of recognizing potential constraint violations in both the planning and flight operations functions. A flight data file for storage/retrieval of information over an extended period which interfaces with a flight operations processor for monitoring of the actual flights was examined.

Torian, J. G.↗

Enterprise Mission Integration for Artemis Lunar Missions

Mission integration is an iterative process by which a specific mission is formulated, refined, planned, and executed within the established vehicle(s), architecture, and ground systems design. Mission integration includes the people, vehicle(s) and ground hardware/software, products, processes, analyses, schedules, facilities, Certification of Flight Readiness, etc. The Artemis Mission Integration Task Team (MITT) developed a series of products and processes to support the complex mission integration across various Programs within the Artemis Mission Campaign (Orion, Space Launch Systems, Exploration Ground Systems, Gateway, Human Landing System, and Extravehicular Activity and Human Surface Mobility). The Moon to Mars (M2M) Program is referred to as ‘the enterprise’ as it includes both the M2M organization and the Programs supporting the Artemis Mission Campaign. Artemis Mission Integration has five phases: mission capability, mission definition, mission preparation, mission execution, and post-mission assessment. This paper focuses on one of the enterprise-level mission checkpoints as a kick-off to the Mission Preparation phase, the Mission Integration Review (MIR), which occurs 18-24 months prior to launch. The MIR helps to confirm the defined mission technical baseline is within the existing analyzed design envelope. Details are provided on the identification of dependencies, issues, or gaps for mission-specific objectives and requirements, as well as the definition of the analysis, training, mission execution products, facilities, and detailed supporting operations requirements. The MIR was held for both Artemis I and II and this paper aims to share with the aerospace community its value as we prepare for upcoming Artemis Missions.

Mary Anne Plaza↗

Mission operations and data systems

A communications system for performing the basic functions of mission operations, orbit and attitude determination, and data processing is described. A block diagram is provided to show the relationships of these functions with the spacecraft in orbit and the experiments to be conducted on board the spacecraft. Specific areas of application are discussed as follows: (1) software operating systems for the ATS-F satellite testing and ground support, (2) inversion of the RAE-1 satellite (Explorer 38 satellite) in orbit, (3) ALSEP differential Doppler tracking, (4) minitrack calibration using satellite data, (5) angles-only orbit extraction, and (6) image processing system performance prediction and product quality evaluation techniques. Block diagrams of the various systems are provided to show the steps involved in the operations.

Source record↗

Integrated Vehicle Ground Vibration Testing in Support of Launch Vehicle Loads and Controls Analysis

All structural systems possess a basic set of physical characteristics unique to that system. These unique physical characteristics include items such as mass distribution and damping. When specified, they allow engineers to understand and predict how a structural system behaves under given loading conditions and different methods of control. These physical properties of launch vehicles may be predicted by analysis or measured by certain types of tests. Generally, these properties are predicted by analysis during the design phase of a launch vehicle and then verified by testing before the vehicle becomes operational. A ground vibration test (GVT) is intended to measure by test the fundamental dynamic characteristics of launch vehicles during various phases of flight. During the series of tests, properties such as natural frequencies, mode shapes, and transfer functions are measured directly. These data will then be used to calibrate loads and control systems analysis models for verifying analyses of the launch vehicle. NASA manned launch vehicles have undergone ground vibration testing leading to the development of successful launch vehicles. A GVT was not performed on the inaugural launch of the unmanned Delta III which was lost during launch. Subsequent analyses indicated had a GVT been performed, it would have identified instability issues avoiding loss of the vehicle. This discussion will address GVT planning, set-up, execution and analyses, for the Saturn and Shuttle programs, and will also focus on the current and on-going planning for the Ares I and V Integrated Vehicle Ground Vibration Test (IVGVT).

Askins, Bruce R.↗

Microprocessor control and networking for the amps breadboard

Future space missions will require more sophisticated power systems, implying higher costs and more extensive crew and ground support involvement. To decrease this human involvement, as well as to protect and most efficiently utilize this important resource, NASA has undertaken major efforts to promote progress in the design and development of autonomously managed power systems. Two areas being actively pursued are autonomous power system (APS) breadboards and knowledge-based expert system (KBES) applications. The former are viewed as a requirement for the timely development of the latter. Not only will they serve as final testbeds for the various KBES applications, but will play a major role in the knowledge engineering phase of their development. The current power system breadboard designs are of a distributed microprocessor nature. The distributed nature, plus the need to connect various external computer capabilities (i.e., conventional host computers and symbolic processors), places major emphasis on effective networking. The communications and networking technologies for the first power system breadboard/test facility are described.

Floyd, Stephen A.↗

NASDA satellite mission operation system and operations

NASDA has recently developed a new tracking and control system as a basis for future satellite mission operation. It is named type-I Space Operations and Data Systems (type-I SODS). The software of this system is separated into three parts: operation and control system, network system, and support and information system. The operation control system treats telemetry and command operations. The network system controls the communication line and ground station equipments to connect the satellite and the operation control system. The support and information system provides to other systems necessary information. JERS-1 which was launched in February of this year is the first satellite operated by type-l SODS. We explain the architecture and operation methods of this system using JERS-1 mission operations.

Yamaya, Kousaku↗

Ammonia Stability in a Simulated Trace Contaminant Rich Cabin Environment

The off-gassing of ammonia from hardware and metabolic sources presents a unique challenge to trace contaminant control system design, driving process flowrates to meet crewed air quality requirements. Accurately simulating representative trace contaminant cabin loads during ground testing is necessary to validate component design as well as understand potential contaminant propagation across life-support system process interface boundaries. This effort is complicated by the observed temporal concentration instability of gaseous ammonia in ground test chambers. To this end, ammonia concentration decay rates were characterized under controlled environmental conditions to better understand underlying phenomena and quantify incidental mass losses. The suspected chemical interaction between ammonia and trace acetaldehyde was investigated and its effect on species quantification was examined by both gas chromatography-mass spectrometry and Fourier-transform infrared spectroscopy. Recommendations for ground test procedures were made in order to best compensate for undesirable ammonia mass losses and mitigate test artifacts.

Kayatin, Matthew J.↗

The Standard Autonomous File Server, a Customized, Off-the-Shelf Success Story

The Standard Autonomous File Server (SAFS), which includes both off-the-shelf hardware and software, uses an improved automated file transfer process to provide a quicker, more reliable, prioritized file distribution for customers of near real-time data without interfering with the assets involved in the acquisition and processing of the data. It operates as a stand-alone solution, monitoring itself, and providing an automated fail-over process to enhance reliability. This paper will describe the unique problems and lessons learned both during the COTS selection and integration into SAFS, and the system's first year of operation in support of NASA's satellite ground network. COTS was the key factor in allowing the two-person development team to deploy systems in less than a year, meeting the required launch schedule. The SAFS system his been so successful, it is becoming a NASA standard resource, leading to its nomination for NASA's Software or the Year Award in 1999.

Semancik, Susan K.↗

Customer Avionics Interface Development and Analysis (CAIDA) Lab DEWESoft Display Creation

The Customer Avionics Interface Development and Analysis (CAIDA) Lab supports the testing of the Launch Control System (LCS), NASA's command and control system for the Space Launch System (SLS), Orion Multi-Purpose Crew Vehicle (MPCV), and ground support equipment. The objectives of the year-long internship were to support day-to-day operations of the CAIDA Lab, create prelaunch and tracking displays for Orion's Exploration Flight Test 1 (EFT-1), and create a program to automate the creation of displays for SLS and MPCV to be used by CAIDA and the Record and Playback Subsystem (RPS).

DEWESoft↗

Customer Avionics Interface Development and Analysis (CAIDA): Software Developer for Avionics Systems

The Customer Avionics Interface Development and Analysis (CAIDA) supports the testing of the Launch Control System (LCS), NASA's command and control system for the Space Launch System (SLS), Orion Multi-Purpose Crew Vehicle (MPCV), and ground support equipment. The objective of the semester-long internship was to support day-to-day operations of CAIDA and help prepare for verification and validation of CAIDA software.

Mitchell, Sherry L.↗

Earth Independent Medical Operations (EIMO)

Inherent in interplanetary space travel are unprecedented challenges that could threaten mission success and negatively impact crew health and performance. Return to definitive care is essentially untenable and resources will be constrained with practically no re-supply capability. Access to ground-based medical expertise will be significantly delayed under nominal conditions with exacerbation during conjunction or prolonged dust storms. Taken together, these challenges necessitate the development of a progressively autonomous medical operational support system to assist the crew medical officer (CMO). While support from ground based medical experts will remain indispensable for pre-mission planning, the approach to management of acute/emergent medical contingencies will require a gradual transition of medical care and decision making from terrestrial to space-based assets, enabling support of astronaut health and performance and reducing overall mission risk. To progressively enable EIMO, a series of meetings were convened with subject matter experts from within NASA, academia and industry to facilitate mapping of the path to support autonomous medical operations. Topics explored in these meetings included the scope of data (storage capacity, usage, transmission rate and bandwidth, computing capacity), CMO training, supply and resource management and task load balance. Recommendations from these meetings will inform the EIMO Concept of Operations and definition of the associated requirements culminating in updates to the NASA 3001 standards. The EIMO project team will work with stakeholders to conceptualize a clinical decision support system (CDSS) to assist the CMO in response to medical contingencies when terrestrial support is delayed or otherwise unavailable. The CDSS will be a system of systems that will utilize data from numerous input vectors. Successful deployment of the CDSS will facilitate medical decision making while decreasing the cognitive load leading to an improvement in task load balancing. Additional benefits of the envisioned CDSS include assistance with inventory management, locating resources, storage/retrieval of medical records, highlighting trends in recorded data, in addition to providing a consult for diagnosis and treatment. More advanced features might include passive monitoring to identify early warning signs of behavioral or medical anomalies to possibly pre-empt onset of conditions that would compromise crew health and performance.

Benjamin Easter↗