Search NASA⌕ Search

SEARCH · Search NASA

Results for “spacecraft data 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 541 records · Page 30

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↗

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↗

Overview of Umbilical Extravehicular Activity (EVA) Interfaces in Life Support Systems on Spacecraft Vehicles and Applications for the Crew Exploration Vehicle (CEV)

Extravehicular Activities (EVAs) for manned spacecraft vehicles have been performed for contingencies and nominal operations numerous times throughout history. This paper will investigate how previous U.S. manned spacecraft vehicles provided life support to crewmembers performing the EVA. Specifically defined are umbilical interfaces with respect to crewmember cooling, drinking water, air (or oxygen), humidity control, and carbon dioxide removal. As historical data is available, the need for planned versus contingency EVAs in previous vehicles as well as details for a nominal EVA day versus a contingency EVA day will be discussed. The hardware used to provide the cooling, drinking water, air (or oxygen), humidity control, and carbon dioxide removal, and the general functions of that hardware, will also be detailed, as information is available. The Crew Exploration Vehicle (CEV or Orion) EVA interfaces will be generically discussed to provide a glimpse of how similar they are to the EVA interfaces in previous vehicles. Conclusions on strategies that should be used for CEV based on previous spacecraft EVA interfaces will be made in the form of questions and recommendations.

Peterson, Laurie J.↗

Thermal study of interface between the Orbiter cold plate and typical Shuttle spacecraft payload flight electronics

Spacelab provides a set of Freon line plumbing and cold plates for experiment equipments which are located in the Shuttle pallet and which need active thermal control. The reported study deals with the thermal problem of attaching a Command and Data Handling module with various electronic boxes whose combined footprints on the baseplate are much larger than the cold plate. A description of two modules and the cold plate assembly in the pallet is presented and a thermal model description is provided. The method employed in modeling heat pipes-honey-comb matrix is based upon an effective conductance between the heat pipe vapor and the walls of the heat pipe. The considered thermal models and a computer program are used to perform steady-state thermal analyses. The temperature gradients in the large module baseplate attached to the small cold plate are predicted as a function of the interface plate thickness.

Hwangbo, H.↗

3D simulation of LISM oxygen flux with PUIs inside of heliosphere

The structure of the heliospheric interface has attracted increasing attention with continual improvements in modelling and observations, during the last half decade. The Interstellar Boundary Explore (IBEX) spacecraft is returning important data that require a theoretical model of Heliosphere to ensure proper interpretation. Furthermore, we develop a framework for understanding the measurements of heavier-than-hydrogen atoms by IBEX in terms of a 3D MHD-neutral numerical solution of the sun's interaction with the interstellar medium, combined with a test particle approach for heavy atoms and ions.

79 ASTRONOMY AND ASTROPHYSICS↗

A Distributed Simulation Software System for Multi-Spacecraft Missions

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

Burns, Richard↗

An Internet Protocol-Based Software System for Real-Time, Closed-Loop, Multi-Spacecraft Mission Simulation Applications

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

Davis, George↗

Orbital Debris Engineering Model (ORDEM) v.3

A model of the manmade orbital debris environment is required by spacecraft designers, mission planners, and others in order to understand and mitigate the effects of the environment on their spacecraft or systems. A manmade environment is dynamic, and can be altered significantly by intent (e.g., the Chinese anti-satellite weapon test of January 2007) or accident (e.g., the collision of Iridium 33 and Cosmos 2251 spacecraft in February 2009). Engineering models are used to portray the manmade debris environment in Earth orbit. The availability of new sensor and in situ data, the re-analysis of older data, and the development of new analytical and statistical techniques has enabled the construction of this more comprehensive and sophisticated model. The primary output of this model is the flux [#debris/area/time] as a function of debris size and year. ORDEM may be operated in spacecraft mode or telescope mode. In the former case, an analyst defines an orbit for a spacecraft and "flies" the spacecraft through the orbital debris environment. In the latter case, an analyst defines a ground-based sensor (telescope or radar) in terms of latitude, azimuth, and elevation, and the model provides the number of orbital debris traversing the sensor's field of view. An upgraded graphical user interface (GUI) is integrated with the software. This upgraded GUI uses project-oriented organization and provides the user with graphical representations of numerous output data products. These range from the conventional flux as a function of debris size for chosen analysis orbits (or views), for example, to the more complex color-contoured two-dimensional (2D) directional flux diagrams in local spacecraft elevation and azimuth.

Matney, Mark↗

Hawkeye Ocean Color Instrument – Performance Summary

Hawkeye is an ocean color instrument that is part of the SeaHawk satellite developed for SOCON, the Sustained Ocean Color Observations using Nanosatellites program funded by the Gordon and Betty Moore Foundation and managed by the University of North Carolina – Wilmington (UNC-W). HawkEye has spectral characteristics similar to SeaWiFS, but with 8 times finer resolution and a smaller field of view more appropriate for lakes, rivers, and near-shore terrestrial environments. With a volume of only 10 X 10 X 10 cm (a CubeSat 1U), it can produce 8 bands of image data in a single pass, each with 1800 x 6000 pixels, with a resolution of 120 meters per pixel. This paper will present a short summary of instrument design, the spacecraft interface, and “lessons learned” during this effort. Scientists considering using linear arrays in a pushbroom mode for remote sensing will find this useful. Much of the discussion will center on optical performance, such as flat field calibration, polarization effects, stray light, out-of-band response, and exposure linearity. Images from field tests will be shown.The Hawkeye instrument is an ocean color measuring instrument designed to fly on the SeaHawk satellite developed for SOCON, the Sustained Ocean Color Observations using Nanosatellites program funded by the Gordon and Betty Moore Foundation and managed by the University of North Carolina – Wilmington (UNC-W). The Hawkeye instrument measures ocean color in 8 spectral bands, similar to SeaWiFS, except Band 7, which is shifted to a slightly lower wavelength to avoid the oxygen absorption feature that a wider band overlapped on SeaWiFS. The instrument is approximately 1/3rd the volume of the entire satellite, which is a 3U Cubesat manufactured by Clydespace in Glasgow, Scotland. The purpose of this instrument is to ascertain the quality of ocean color data possible with such a small, inexpensive instrument and bus. The nominal orbit is 540 km, and the nominal pixel geometric instantaneous field of view (GIFOV) 120 meters on a side. Each band will produce an image 1800 x 6000 pixels in size, for a total field of view of 216 X 720 km.2) DESIGN CONCEPTThe Hawkeye instrument uses linear arrays in pushbroom mode to collect data over a two dimensional area. The instrument has 4 linear CCD arrays, the Onsemi KLI-4104, to collect the 8 bands of data. Figure 1 illustrates the optical design for two bands, sharing a single array.

Hawkeye↗

Maneuver Automation Software

The Maneuver Automation Software (MAS) automates the process of generating commands for maneuvers to keep the spacecraft of the Cassini-Huygens mission on a predetermined prime mission trajectory. Before MAS became available, a team of approximately 10 members had to work about two weeks to design, test, and implement each maneuver in a process that involved running many maneuver-related application programs and then serially handing off data products to other parts of the team. MAS enables a three-member team to design, test, and implement a maneuver in about one-half hour after Navigation has process-tracking data. MAS accepts more than 60 parameters and 22 files as input directly from users. MAS consists of Practical Extraction and Reporting Language (PERL) scripts that link, sequence, and execute the maneuver- related application programs: "Pushing a single button" on a graphical user interface causes MAS to run navigation programs that design a maneuver; programs that create sequences of commands to execute the maneuver on the spacecraft; and a program that generates predictions about maneuver performance and generates reports and other files that enable users to quickly review and verify the maneuver design. MAS can also generate presentation materials, initiate electronic command request forms, and archive all data products for future reference.

Uffelman, Hal↗

Analysis of Advanced Modular Power Systems (AMPS) for Deep Space Exploration

The Advanced Modular Power Systems (AMPS) project is developing a modular approach to spacecraft power systems for exploration beyond Earth orbit. AMPS is intended to meet the need of reducing the cost of design development, test and integration and also reducing the operational logistics cost of supporting exploration missions. AMPS seeks to establish modular power building blocks with standardized electrical, mechanical, thermal and data interfaces that can be applied across multiple exploration vehicles. The presentation discusses the results of a cost analysis that compares the cost of the modular approach against a traditional non-modular approach.

Exploration↗

3D Orbit Visualization for Earth-Observing Missions

This software visualizes orbit paths for the Orbiting Carbon Observatory (OCO), but was designed to be general and applicable to any Earth-observing mission. The software uses the Google Earth user interface to provide a visual mechanism to explore spacecraft orbit paths, ground footprint locations, and local cloud cover conditions. In addition, a drill-down capability allows for users to point and click on a particular observation frame to pop up ancillary information such as data product filenames and directory paths, latitude, longitude, time stamp, column-average dry air mole fraction of carbon dioxide, and solar zenith angle. This software can be integrated with the ground data system for any Earth-observing mission to automatically generate daily orbit path data products in Google Earth KML format. These KML data products can be directly loaded into the Google Earth application for interactive 3D visualization of the orbit paths for each mission day. Each time the application runs, the daily orbit paths are encapsulated in a KML file for each mission day since the last time the application ran. Alternatively, the daily KML for a specified mission day may be generated. The application automatically extracts the spacecraft position and ground footprint geometry as a function of time from a daily Level 1B data product created and archived by the mission s ground data system software. In addition, ancillary data, such as the column-averaged dry air mole fraction of carbon dioxide and solar zenith angle, are automatically extracted from a Level 2 mission data product. Zoom, pan, and rotate capability are provided through the standard Google Earth interface. Cloud cover is indicated with an image layer from the MODIS (Moderate Resolution Imaging Spectroradiometer) aboard the Aqua satellite, which is automatically retrieved from JPL s OnEarth Web service.

Jacob, Joseph C.↗

Overview of Graphical User Interface for ARRBOD (Acute Radiation Risk and BRYNTRN Organ Dose Projection)

Solar particle events (SPEs) pose the risk of acute radiation sickness (ARS) to astronauts, because organ doses from large SPEs may reach critical levels during extra vehicular activities (EVAs) or lightly shielded spacecraft. NASA has developed an organ dose projection model of Baryon transport code (BRYNTRN) with an output data processing module of SUMDOSE, and a probabilistic model of acute radiation risk (ARR). BRYNTRN code operation requires extensive input preparation, and the risk projection models of organ doses and ARR take the output from BRYNTRN as an input to their calculations. With a graphical user interface (GUI) to handle input and output for BRYNTRN, these response models can be connected easily and correctly to BRYNTRN in a user friendly way. The GUI for the Acute Radiation Risk and BRYNTRN Organ Dose (ARRBOD) projection code provides seamless integration of input and output manipulations required for operations of the ARRBOD modules: BRYNTRN, SUMDOSE, and the ARR probabilistic response model. The ARRBOD GUI is intended for mission planners, radiation shield designers, space operations in the mission operations directorate (MOD), and space biophysics researchers. Assessment of astronauts organ doses and ARS from the exposure to historically large SPEs is in support of mission design and operation planning to avoid ARS and stay within the current NASA short-term dose limits. The ARRBOD GUI will serve as a proof-of-concept for future integration of other risk projection models for human space applications. We present an overview of the ARRBOD GUI product, which is a new self-contained product, for the major components of the overall system, subsystem interconnections, and external interfaces.

Kim, Myung-Hee Y.↗

IUE/IRA system description

The IUE/IRA rate sensor system designed to meet the requirements of the International Ultraviolet Explorer spacecraft mission is described. The system consists of the sensor unit containing six rate sensor modules and the electronic control unit containing the rate sensor support electronics and the command/control circuitry. The inertial reference assembly formed by the combined units will provide spacecraft rate information for use in the stabilization and control system. The system is described in terms of functional description, operation redundancy performance, mechanical interface, and electrical interface. Test data obtained from the flight unit are summarized.

Jennings, J.↗

Latching Mechanism for Umbilical Connectors

Electromechanical interface transfers electric power, data and coolant from one system to another. Motor-actuated jackscrew moves connector on active half of interface to mating connector on passive half. Originally suggested for spacecraft, concept adaptable to underwater connections.

Burns, G. C.↗

Standard user data services for spacecraft applications

The Consultative Committee for Space Data Systems is an international organization of national space agencies that is branching out to provide new standards to enhanced reuse of spacecraft equiptment and software. These Spacecraft Onboard Interface (SOIF) standards will be based on the well-known Internet protocols. this paper will review the SOIF standards by looking at the services that are being proposed for SOIF.

space interfaces avionics interfaces standard inte↗

MSL MMRTG Power Modeling for Lifetime Performance Predictions

The Multi-Mission Radioisotope Thermoelectric Generator (MMRTG) has been providing power to the Mars Science Laboratory (MSL) rover, Curiosity, for surface operations since 2012. The Jet Propulsion Laboratory (JPL) has employed the Life Performance Prediction Model (LPPM) to generate predictions and outputs based upon flight data from the rover and experimental data from the thermoelectric (TE) couples. In order to make these predictions, LPPM requires various spacecraft inputs relevant to RTG performance such as fin root temperature, load voltage, general purpose heat source (GPHS) inventory, etc., combined with couple data such as thermoelectric properties, interface degradation, and sublimation properties. With tens of thousands of hours of flight data to date, LPPM can not only track performance to date, but also make predictions on the power output of the MMRTG through the 17-year end-of-design-life (EODL). These predictions are useful for mission planners and surface operators who rely on the MMRTG for power in order to perform the critical science necessary during the mission. This paper will showcase the power data extracted from the flight electronics, comparing it to the predictions and outputs generated from LPPM.

Pinkowski, Stanley↗

Planetary spacecraft - SEPS interface design

The interactions between a spacecraft which would rendezvous with the comet Tempel II, the stage, and the mission design are summarized along with solar electric propulsion system design issues. Attention is given to data communication, the spacecraft pointing control system, spacecraft power, plasma interactions, the release of a probe to study the comet Halley, and thruster usage. It was concluded that for a planetary mission design using a low-thrust stage, the control of the mission should reside in the payload spacecraft and that the power should be provided by the stage; the NASA standard 28 VDC bus is recommended.

Pless, L. C.↗