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 973 records · Page 54

Medical System Concept of Operations for Mars Exploration Mission-11: Exploration Medical Capability (ExMC) Element - Human Research Program

NASA’s exploration missions to Mars will have durations of 2-3 years and will take humans farther away from Earth than ever before. This will result in a paradigm shift for mission planning, spacecraft design, human systems integration, and in-flight medical care. Constraints on real-time communication, resupply, and medical evacuation are major architectural drivers. These constraints require medical system development to be tightly integrated with mission and vehicle design to provide crew autonomy and enable mission success. This concept of operations provides a common vision of medical care for developing a medical system for Mars exploration missions. It documents an overview of the stakeholder needs and goals of a medical system and provides examples of the types of activities the system will be used for during the mission. Development of the concept of operations considers mission variables such as distance from Earth, duration of mission, time to definitive medical care, communication protocols between crewmembers and ground support, personnel capabilities and skill sets, medical hardware and software, and medical data management. The information provided in this document informs the ExMC Systems Engineering effort to define the functions to be provided by the medical system. In addition, this concept of operations will inform the subsequent systems engineering process of developing technical requirements, system architectures, interfaces, and verification and validation approaches for the medical system. This document supports the closure of ExMC Gap Med01: We do not have a concept of operations for medical care during exploration missions, corresponding to the ExMC-managed human system risk: Risk of Adverse Health Outcomes & Decrements in Performance due to Inflight Medical Conditions. This document is applicable to the ExMC Element Systems Engineering process and may be used for collaboration within the Human Research Program.

Urbina, Michelle↗

Interfacing Space Communications and Navigation Network Simulation with Distributed System Integration Laboratories (DSIL)

NASA's planned Lunar missions will involve multiple NASA centers where each participating center has a specific role and specialization. In this vision, the Constellation program (CxP)'s Distributed System Integration Laboratories (DSIL) architecture consist of multiple System Integration Labs (SILs), with simulators, emulators, testlabs and control centers interacting with each other over a broadband network to perform test and verification for mission scenarios. To support the end-to-end simulation and emulation effort of NASA' exploration initiatives, different NASA centers are interconnected to participate in distributed simulations. Currently, DSIL has interconnections among the following NASA centers: Johnson Space Center (JSC), Kennedy Space Center (KSC), Marshall Space Flight Center (MSFC) and Jet Propulsion Laboratory (JPL). Through interconnections and interactions among different NASA centers, critical resources and data can be shared, while independent simulations can be performed simultaneously at different NASA locations, to effectively utilize the simulation and emulation capabilities at each center. Furthermore, the development of DSIL can maximally leverage the existing project simulation and testing plans. In this work, we describe the specific role and development activities at JPL for Space Communications and Navigation Network (SCaN) simulator using the Multi-mission Advanced Communications Hybrid Environment for Test and Evaluation (MACHETE) tool to simulate communications effects among mission assets. Using MACHETE, different space network configurations among spacecrafts and ground systems of various parameter sets can be simulated. Data that is necessary for tracking, navigation, and guidance of spacecrafts such as Crew Exploration Vehicle (CEV), Crew Launch Vehicle (CLV), and Lunar Relay Satellite (LRS) and orbit calculation data are disseminated to different NASA centers and updated periodically using the High Level Architecture (HLA). In addition, the performance of DSIL under different traffic loads with different mix of data and priorities are evaluated.

Traffic Measuring and Monitoring↗

Towards a Decision Support System for Space Flight Operations

The Mission Operations Directorate (MOD) at the Johnson Space Center (JSC) has put in place a Model Based Systems Engineering (MBSE) technological framework for the development and execution of the Flight Production Process (FPP). This framework has provided much added value and return on investment to date. This paper describes a vision for a model based Decision Support System (DSS) for the development and execution of the FPP and its design and development process. The envisioned system extends the existing MBSE methodology and technological framework which is currently in use. The MBSE technological framework currently in place enables the systematic collection and integration of data required for building an FPP model for a diverse set of missions. This framework includes the technology, people and processes required for rapid development of architectural artifacts. It is used to build a feasible FPP model for the first flight of spacecraft and for recurrent flights throughout the life of the program. This model greatly enhances our ability to effectively engage with a new customer. It provides a preliminary work breakdown structure, data flow information and a master schedule based on its existing knowledge base. These artifacts are then refined and iterated upon with the customer for the development of a robust end-to-end, high-level integrated master schedule and its associated dependencies. The vision is to enhance this framework to enable its application for uncertainty management, decision support and optimization of the design and execution of the FPP by the program. Furthermore, this enhanced framework will enable the agile response and redesign of the FPP based on observed system behavior. The discrepancy of the anticipated system behavior and the observed behavior may be due to the processing of tasks internally, or due to external factors such as changes in program requirements or conditions associated with other organizations that are outside of MOD. The paper provides a roadmap for the three increments of this vision. These increments include (1) hardware and software system components and interfaces with the NASA ground system, (2) uncertainty management and (3) re-planning and automated execution. Each of these increments provide value independently; but some may also enable building of a subsequent increment.

Meshkat, Leila↗

Compact Holographic Data Storage

NASA's future missions would require massive high-speed onboard data storage capability to Space Science missions. For Space Science, such as the Europa Lander mission, the onboard data storage requirements would be focused on maximizing the spacecraft's ability to survive fault conditions (i.e., no loss in stored science data when spacecraft enters the 'safe mode') and autonomously recover from them during NASA's long-life and deep space missions. This would require the development of non-volatile memory. In order to survive in the stringent environment during space exploration missions, onboard memory requirements would also include: (1) survive a high radiation environment (1 Mrad), (2) operate effectively and efficiently for a very long time (10 years), and (3) sustain at least a billion write cycles. Therefore, memory technologies requirements of NASA's Earth Science and Space Science missions are large capacity, non-volatility, high-transfer rate, high radiation resistance, high storage density, and high power efficiency. JPL, under current sponsorship from NASA Space Science and Earth Science Programs, is developing a high-density, nonvolatile and rad-hard Compact Holographic Data Storage (CHDS) system to enable large-capacity, high-speed, low power consumption, and read/write of data in a space environment. The entire read/write operation will be controlled with electrooptic mechanism without any moving parts. This CHDS will consist of laser diodes, photorefractive crystal, spatial light modulator, photodetector array, and I/O electronic interface. In operation, pages of information would be recorded and retrieved with random access and high-speed. The nonvolatile, rad-hard characteristics of the holographic memory will provide a revolutionary memory technology meeting the high radiation challenge facing the Europa Lander mission. Additional information is contained in the original extended abstract.

Chao, T. H.↗

OSIRIS-REx, Returning the Asteroid Sample

This paper addresses the technical aspects of the sample return system for the upcoming Origins, Spectral Interpretation, Resource Identification, and Security-Regolith Explorer (OSIRIS-REx) asteroid sample return mission. The overall mission design and current implementation are presented as an overview to establish a context for the technical description of the reentry and landing segment of the mission.The prime objective of the OSIRIS-REx mission is to sample a primitive, carbonaceous asteroid and to return that sample to Earth in pristine condition for detailed laboratory analysis. Targeting the near-Earth asteroid Bennu, the mission launches in September 2016 with an Earth reentry date of September 24, 2023.OSIRIS-REx will thoroughly characterize asteroid Bennu providing knowledge of the nature of near-Earth asteroids that is fundamental to understanding planet formation and the origin of life. The return to Earth of pristine samples with known geologic context will enable precise analyses that cannot be duplicated by spacecraft-based instruments, revolutionizing our understanding of the early Solar System. Bennu is both the most accessible carbonaceous asteroid and one of the most potentially Earth-hazardous asteroids known. Study of Bennu addresses multiple NASA objectives to understand the origin of the Solar System and the origin of life and will provide a greater understanding of both the hazards and resources in near-Earth space, serving as a precursor to future human missions to asteroids.This paper focuses on the technical aspects of the Sample Return Capsule (SRC) design and concept of operations, including trajectory design and reentry retrieval. Highlights of the mission are included below.The OSIRIS-REx spacecraft provides the essential functions for an asteroid characterization and sample return mission: attitude control propulsion power thermal control telecommunications command and data handling structural support to ensure successful rendezvous with Bennu characterization of Bennus properties delivery of the sampler to the surface, and return of the spacecraft to the vicinity of the Earth sample collection, performed by the Touch-and-Go Sample Acquisition Mechanism (TAGSAM), to acquire a regolith sample from the surface Earth re-entry and SRC recovery. Following sample collection, OSIRIS-REx drifts away from Bennu until the Asteroid Departure Maneuver is commanded on March 4, 2021, sending OSIRIS-REx on a ballistic return cruise to Earth. No additional large deterministic maneuvers are required to return the SRC to Earth. During the cruise, tracking and trajectory correction maneuvers (TCMs) are performed as necessary to precisely target the entry corridor. As OSIRIS-REx approaches Earth, the reentry plans are reviewed starting about a year before arrival, and preparations begin. The spacecraft is targeted away from the Earth until 7 days before entry. The final two trajectory correction maneuvers bring the spacecraft on target toward the Utah Test and Training Range (UTTR), with sufficient time for contingency resolution. The SRC releases 4 hours prior to atmospheric entry interface and, using the Stardust capsule heritage design, employs a traditional drogue and main parachute descent system for a soft touchdown.

reentry↗

Utilizing Testing Frameworks for Launch Control Systems Continuous Integration

Command and control software is an integral part of the launch procedure. The most important part of this type of software is its ability to communicate well with the user and relay information in a correctly formatted way such that the user can understand the data. There is a tool that aides the communication between the different parts of the system, and effectively, the user. This instrument is capable of taking several complex values and ensuring that they are correctly sorted into their distinctive message values and distributed properly among the different facets of the system. This tool will easily translate and publish the data inside of messages in the system to something that is readable and understandable. The tool also allows for transmission of the recorded data to the user, effectively ensuring the communication between different components of the system. As well as keeping track of messages and ensuring that the information contained within each of them reaches the correct location, this tool has the ability to keep track of its own statistics and determine how many messages passed in were erroneous and how many were successfully transmitted. It is able to check and see what the total message failure count is when an invalid message is given, as well as the number of different messages and their respective types passed into the tool. This tool is of great value to the new Space Launch System (SLS). As such, the tool must be thoroughly tested with test cases that, although improbable, are possible, where the tool may not function properly. Testing an interface this complex is necessary to ensure mission safety and create unlikely scenarios where the tool would work as intended, and stretch its limits to test that even under the most uncommon conditions it would still continue to function. This software will be an important part of the control system for the newest spacecraft which will fly deeper into space than humans have ever travelled. It will fly beyond the moon, into deep space to Mars and perhaps set the groundwork for a manned mission even further to create more opportunities for interplanetary and even interstellar travel by humans. This mission relies heavily on software and hardware to ensure the safety of the humans that will be on board and therefore must be checked, exhausting each and every different situation, such that there is not a doubt surrounding the well-being of the humans aboard the rocket. That is why testing is such an important part of the mission. It provides evidence that the systems aboard the rocket and on the launch pad are safe.

Unit Testing↗

Development of a Space Radiation Monte-Carlo Computer Simulation Based on the FLUKE and Root Codes

The radiation environment in space is a complex problem to model. Trying to extrapolate the projections of that environment into all areas of the internal spacecraft geometry is even more daunting. With the support of our CERN colleagues, our research group in Houston is embarking on a project to develop a radiation transport tool that is tailored to the problem of taking the external radiation flux incident on any particular spacecraft and simulating the evolution of that flux through a geometrically accurate model of the spacecraft material. The output will be a prediction of the detailed nature of the resulting internal radiation environment within the spacecraft as well as its secondary albedo. Beyond doing the physics transport of the incident flux, the software tool we are developing will provide a self-contained stand-alone object-oriented analysis and visualization infrastructure. It will also include a graphical user interface and a set of input tools to facilitate the simulation of space missions in terms of nominal radiation models and mission trajectory profiles. The goal of this project is to produce a code that is considerably more accurate and user-friendly than existing Monte-Carlo-based tools for the evaluation of the space radiation environment. Furthermore, the code will be an essential complement to the currently existing analytic codes in the BRYNTRN/HZETRN family for the evaluation of radiation shielding. The code will be directly applicable to the simulation of environments in low earth orbit, on the lunar surface, on planetary surfaces (including the Earth) and in the interplanetary medium such as on a transit to Mars (and even in the interstellar medium). The software will include modules whose underlying physics base can continue to be enhanced and updated for physics content, as future data become available beyond the timeframe of the initial development now foreseen. This future maintenance will be available from the authors of FLUKA as part of their continuing efforts to support the users of the FLUKA code within the particle physics community. In keeping with the spirit of developing an evolving physics code, we are planning as part of this project, to participate in the efforts to validate the core FLUKA physics in ground-based accelerator test runs. The emphasis of these test runs will be the physics of greatest interest in the simulation of the space radiation environment. Such a tool will be of great value to planners, designers and operators of future space missions, as well as for the design of the vehicles and habitats to be used on such missions. It will also be of aid to future experiments of various kinds that may be affected at some level by the ambient radiation environment, or in the analysis of hybrid experiment designs that have been discussed for space-based astronomy and astrophysics. The tool will be of value to the Life Sciences personnel involved in the prediction and measurement of radiation doses experienced by the crewmembers on such missions. In addition, the tool will be of great use to the planners of experiments to measure and evaluate the space radiation environment itself. It can likewise be useful in the analysis of safe havens, hazard migration plans, and NASA's call for new research in composites and to NASA engineers modeling the radiation exposure of electronic circuits. This code will provide an important complimentary check on the predictions of analytic codes such as BRYNTRN/HZETRN that are presently used for many similar applications, and which have shortcomings that are more easily overcome with Monte Carlo type simulations. Finally, it is acknowledged that there are similar efforts based around the use of the GEANT4 Monte-Carlo transport code currently under development at CERN. It is our intention to make our software modular and sufficiently flexible to allow the parallel use of either FLUKA or GEANT4 as the physics transport engine.

Pinsky, L. S.↗

Towards a decision support system for space flight operations

The Mission Operations Directorate (MOD) at the Johnson Space Center (JSC) has put in place a Model Based Systems Engineering (MBSE) technological framework for the development and execution of the Flight Production Process (FPP). This framework has provided much added value and return on investment to date. This paper describes a vision for a model based Decision Support System (DSS) for the development and execution of the FPP and its design and development process. The envisioned system extends the existing MBSE methodology and technological framework which is currently in use. The MBSE technological framework currently in place enables the systematic collection and integration of data required for building an FPP model for a diverse set of missions. This framework includes the technology, people and processes required for rapid development of architectural artifacts. It is used to build a feasible FPP model for the first flight of spacecraft and for recurrent flights throughout the life of the program. This model greatly enhances our ability to effectively engage with a new customer. It provides a preliminary work breakdown structure, data flow information and a master schedule based on its existing knowledge base. These artifacts are then refined and iterated upon with the customer for the development of a robust end-to-end, high-level integrated master schedule and its associated dependencies. The vision is to enhance this framework to enable its application for uncertainty management, decision support and optimization of the design and execution of the FPP by the program. Furthermore, this enhanced framework will enable the agile response and redesign of the FPP based on observed system behavior. The differences between the anticipated system behavior and the observed behavior may be due to the processing of tasks internally, or due to external factors such as changes in program requirements or conditions associated with other organizations that are outside of MOD. The paper provides a roadmap for the four increments of this vision. These increments include (1) the existing capabilities (2) hardware and software system components and interfaces with the NASA ground system, (3) uncertainty management and (4) re-planning and automated execution. Each of these increments provides value independently; but some may also enable building of a subsequent increment.

Ruszkowski, James↗

THE CHANDRA VARIABLE GUIDE STAR CATALOG

Variable stars have been identified among the optical-wavelength light curves of guide stars used for pointing control of the Chandra X-ray Observatory. We present a catalog of these variable stars along with their light curves and ancillary data. Variability was detected to a lower limit of 0.02 mag amplitude in the 4000-10000 A range using the photometrically stable Aspect Camera on board the Chandra spacecraft. The Chandra Variable Guide Star Catalog (VGUIDE) contains 827 stars, of which 586 are classified as definitely variable and 241 are identified as possibly variable. Of the 586 definite variable stars, we believe 319 are new variable star identifications. Types of variables in the catalog include eclipsing binaries, pulsating stars, and rotating stars. The variability was detected during the course of normal verification of each Chandra pointing and results from analysis of over 75,000 guide star light curves from the Chandra mission. The VGUIDE catalog represents data from only about 9 years of the Chandra mission. Future releases of VGUIDE will include newly identified variable guide stars as the mission proceeds. An important advantage of the use of space data to identify and analyze variable stars is the relatively long observations that are available. The Chandra orbit allows for observations up to 2 days in length. Also, guide stars were often used multiple times for Chandra observations, so many of the stars in the VGUIDE catalog have multiple light curves available from various times in the mission. The catalog is presented as both online data associated with this paper and as a public Web interface. Light curves with data at the instrumental time resolution of about 2 s, overplotted with the data binned at 1 ks, can be viewed on the public Web interface and downloaded for further analysis. VGUIDE is a unique project using data collected during the mission that would otherwise be ignored. The stars available for use as Chandra guide stars are generally 6-11 mag and are commonly spectral types A and later. Due to the selection of guide stars entirely for positional convenience, this catalog avoids the possible bias of searching for variability in objects where it is to be expected. Statistics of variability compared to spectral type indicate the expected dominance of A-F stars as pulsators. Eclipsing binaries are consistently 20%-30% of the detected variables across all spectral types.

79 ASTRONOMY AND ASTROPHYSICS↗

Constraints on Vesta's Interior Structure Using Gravity and Shape Models from the Dawn Mission

We use the shape and gravity field of Vesta determined from observations of the Dawn spacecraft to place constraints on the asteroid's interior structure. We compute a three-layer interior structure model by minimizing the power of the residual gravity anomaly. The densities of the mantle and crust are based on constraints derived from the Howardite-Eucrite-Diogenite (HED) meteorites. Vesta's present-day shape is not in hydrostatic equilibrium. The Rheasilvia and Veneneia impact basins have a large effect on Vesta's shape and are the main source of deviation from hydrostatic shape. Constraining a pre-giant-impact rotation rate and orientation of the spin axis from an ellipsoidal fit to the parts of Vesta unaffected by the giant impacts, and using the theory of figure, we can constrain the shape of the core. Our solution for Vesta's crust-mantle interface reveals a belt of thick crust around Rheasilvia and Veneneia. The thinnest crust is in the floor of the two basins and in the Vestalia Terra region. Our solution does not reveal an uplift of the crust-mantle boundary to the surface in the largest basins. This, together with the lack of olivine detected by the Visible and Infrared Spectrometer (VIR) data in Rheasilvia and Veneneia, indicates that Vesta's presumed olivine mantle was either not brought to the surface by these large impacts or was covered by ejecta from subsequent impacts.

Interiors↗

Automating Surface Attitude Positioning and Pointing Operations for Mars 2020

The Surface Attitude Positioning and Pointing (SAPP) subsystem of the Mars Perseverance rover keeps track of the rover’s position and attitude on the surface of Mars. The SAPP Downlink Engineering Operations team members receive data from the rover on a daily basis. They must interpret the data to make sure the rover is staying safe and to support uplink planning. The SAPP team keeps track of the error growth in the rover’s attitude estimate due to noise in the Rover Inertial Measurement Unit’s (RIMU) gyroscopes used to propagate that attitude estimate whenever the rover is moving. Whenever this error grows to a particular threshold, SAPP is responsible for updating the onboard attitude knowledge using the RIMU’s accelerometers to estimate rover roll and pitch and sun imaging to estimate rover yaw, thereby reducing this attitude estimation error. Accurate attitude estimation is required so that the rover can successfully point its High Gain Antenna (HGA) to receive information from Earth and as a backup to the Mars orbiters used for sending data from the rover to Earth, point instruments on its Remote Sensing Mast (RSM), and support safe movement and placement of instruments by the rover’s ARM relative to the Martian surface. The Mars 2020 Engineering Operations team has been working to increase the operational efficiency of the mission and eventually move to a five-hour timeline for daily operations. In pursuit of this goal, the SAPP Engineering Operations team has automated their downlink process by developing a centralized Jupyter notebook to analyze the data received daily from the rover. The SAPP downlink Jupyter notebook automatically collects the data relevant to the SAPP subsystem and visualizes this information in plots and tables that can be easily read by downlink operators to aid them in assessing the status of the subsystem. Various Application Programming Interfaces (APIs) have been incorporated into the downlink daily notebook to automate the collection and posting of data, such as gathering and posting data products to the cloud. The SAPP team has also developed a SAPP downlink software library that includes functions to aid the notebook in processing data. In addition to assessing the SAPP subsystem on a daily basis, operators need to assess the long-term trending behavior of the subsystem over time. An automated trending process has been developed to collect information from the daily notebooks in order to plot and analyze that data in a centralized place. These daily and trending processes have expedited the SAPP downlink assessment and laid the groundwork to completely automate the SAPP downlink process so that SAPP operators are unnecessary unless something unexpected occurs. This paper will provide an overview of the functions that the SAPP subsystem carries out on a daily basis, and will then dive into the automations that have been developed for daily and trending downlink assessment. An assessment of the downlink efficiency will be provided, along with a summary of lessons learned and work to go. Finally, the authors will discuss how these types of automated spacecraft health assessments could be more broadly used within mission operations.

Zarifian, Anais↗

Orion Entry Display Feeder and Interactions with the Entry Monitor System

The Orion spacecraft is designed to return astronauts to a landing within 10 km of the intended landing target from low Earth orbit, lunar direct-entry, and lunar skip-entry trajectories. Al pile the landing is nominally controlled autonomously, the crew can fly precision entries manually in the event of an anomaly. The onboard entry displays will be used by the crew to monitor and manually fly the entry, descent, and landing, while the Entry Monitor System (EMS) will be used to monitor the health and status of the onboard guidance and the trajectory. The entry displays are driven by the entry display feeder, part of the Entry Monitor System (EMS). The entry re-targeting module, also part of the EMS, provides all the data required to generate the capability footprint of the vehicle at any point in the trajectory, which is shown on the Primary Flight Display (PFD). It also provides caution and warning data and recommends the safest possible re-designated landing site when the nominal landing site is no longer within the capability of the vehicle. The PFD and the EMS allow the crew to manually fly an entry trajectory profile from entry interface until parachute deploy having the flexibility to manually steer the vehicle to a selected landing site that best satisfies the priorities of the crew. The entry display feeder provides data from the ENIS and other components of the GNC flight software to the displays at the proper rate and in the proper units. It also performs calculations that are specific to the entry displays and which are not made in any other component of the flight software. In some instances, it performs calculations identical to those performed by the onboard primary guidance algorithm to protect against a guidance system failure. These functions and the interactions between the entry display feeder and the other components of the EMS are described.

Baird, Darren↗

Creating the Deep Space Environment for Testing the James Webb Space Telescope (JWST) at NASA Johnson Space Center's Chamber A

Chamber A is the largest thermal vacuum chamber at the Johnson Space Center and is one of the largest space environment chambers in the world. The chamber is 19.8 m (65 ft) in diameter and 36.6 m (120 ft) tall and is equipped with cryogenic liquid nitrogen panels (shrouds) and gaseous helium shrouds to create a simulated space environment. It was originally designed and built in the mid 1960 s to test the Apollo Command and Service Module and several manned tests were conducted on that spacecraft, contributing to the success of the program. The chamber has been used since that time to test spacecraft active thermal control systems, Shuttle DTO, DOD, and ESA hardware in simulated Low Earth Orbit (LEO) conditions. NASA is now moving from LEO towards exploration of locations with environments approaching those of deep space. Therefore, Chamber A has undergone major modifications to enable it to simulate these deeper space environments. Environmental requirements were driven, and modifications were funded by the James Webb Space Telescope program, and this telescope which will orbit Solar/Earth L2, will be the first test article to benefit from the chamber s new capabilities. To accommodate JWST, the Chamber A high vacuum system has been modernized, additional LN2 shrouds have been installed, the liquid nitrogen system has been modified to remove dependency on electrical power and increase its reliability, a new helium shroud/refrigeration system has been installed to create a colder more stable and uniform heat sink, and the controls have been updated to increase the level of automation and improve operator interfaces. Testing of these major modifications was conducted in August of 2012 and this initial test was very successful, with all major systems exceeding their performance requirements. This paper will outline the changes in overall environmental requirements, discuss the technical design data that was used in the decisions leading to the extensive modifications, and describe the new capabilities of the chamber.

Homan, Jonathan L.↗

Creating the Deep Space Environment for Testing the James Webb Space Telescope at NASA Johnson Space Center's Chamber A

Chamber A is the largest thermal vacuum chamber at the Johnson Space Center and is one of the largest space environment chambers in the world. The chamber is 19.8 m (65 ft.) in diameter and 36.6 m (120 ft.) tall and is equipped with cryogenic liquid nitrogen panels (shrouds) and gaseous helium shrouds to create a simulated space environment. It was originally designed and built in the mid 1960 s to test the Apollo Command and Service Module and several manned tests were conducted on that spacecraft, contributing to the success of the program. The chamber has been used since that time to test spacecraft active thermal control systems, Shuttle DTO, DOD, and ESA hardware in simulated Low Earth Orbit (LEO) conditions. NASA is now moving from LEO towards exploration of locations with environments approaching those of deep space. Therefore, Chamber A has undergone major modifications to enable it to simulate these deeper space environments. Environmental requirements were driven, and modifications were funded by the James Webb Space Telescope program, and this telescope, which will orbit Solar/Earth L2, will be the first test article to benefit from the chamber s new capabilities. To accommodate JWST, the Chamber A high vacuum system has been modernized, additional LN2 shrouds have been installed, the liquid nitrogen system has been modified to minimize dependency on electrical power and increase its reliability, a new helium shroud/refrigeration system has been installed to create a colder more stable and uniform heat sink, and the controls have been updated to increase the level of automation and improve operator interfaces. Testing of these major modifications was conducted in August of 2012 and this initial test was very successful, with all major systems exceeding their performance requirements. This paper will outline the changes in overall environmental requirements, discuss the technical design data that was used in the decisions leading to the extensive modifications, and describe the new capabilities of the chamber.

Homan, Jonathan L.↗

Creating the Deep Space Environment for Testing the James Webb Space Telescope at the Johnson Space Center's Chamber A

Chamber A is the largest thermal vacuum chamber at the Johnson Space Center and is one of the largest space environment chambers in the world. The chamber is 19.8 m (65 ft) in diameter and 36.6 m (120 ft) tall and is equipped with cryogenic liquid nitrogen panels (shrouds) and gaseous helium shrouds to create a simulated space environment. It was originally designed and built in the mid 1960's to test the Apollo Command and Service Module and several manned tests were conducted on that spacecraft, contributing to the success of the program. The chamber has been used since that time to test spacecraft active thermal control systems, Shuttle DTO, DOD, and ESA hardware in simulated Low Earth Orbit (LEO) conditions. NASA is now moving from LEO towards exploration of locations with environments approaching those of deep space. Therefore, Chamber A has undergone major modifications to enable it to simulate these deeper space environments. Environmental requirements were driven, and the modifications were funded, by the James Webb Space Telescope program, and this telescope which will orbit Solar/Earth L2, will be the first test article to benefit from the chamber s new capabilities. To accommodate JWST, the Chamber A high vacuum system has been modernized, additional LN2 shrouds have been installed, the liquid nitrogen system has been modified to remove dependency on electrical power and increase its reliability, a new helium shroud/refrigeration system has been installed to create a colder more stable and uniform heat sink and, the controls have been updated to increase the level of automation and improve operator interfaces. Testing of these major modifications was conducted in August 2012 and this initial test was very successful, with all major systems exceeding their performance requirements. This paper will outline the changes in the overall environmental requirements, discuss the technical design data that was used in the decisions leading to the extensive modifications, and describe the new capabilities of the chamber.

Homan, Jonathan L.↗

Ground Segment Operations Concept for the Orion Artemis-2 Optical Communications System

The ACCESS Project (formerly Space Network) will implement an optical communications ground segment to support the Orion Artemis II Optical Communications (O2O) demonstration as part of the next manned human spaceflight mission to the moon, Artemis II. O2O implements laser communication (lasercomm) technology for operational use on the Orion series of spacecraft, as a development test objective (DTO), in order to demonstrate the feasibility and operational utility of lasercomm for human spaceflight missions. O2O consists of three segments: Space Segment, Ground Segment, and Operations Segment. The Space Segment consists of the Space Terminal Element and the Orion spacecraft. The Space Terminal Element effort is managed by the GSFC Laser-Enhanced Mission Communications Navigation and Operational Services (LEMNOS) project in collaboration with MIT Lincoln Laboratory. The Ground Segment consists of an optical ground terminal (GT) at the White Sands Complex (WSC), which is being developed in collaboration with MIT Lincoln Laboratory, the Ground Segment Operations and Analysis (GSOA) element and Ground Data Element (GDE), and a second optical GT in the Optical Communications Telescope Laboratory (OCTL) at the JPL Table Mountain Facility. The Operations Segment consists of the Artemis II Mission Control Center (MCC), the Lasercomm Space Terminal Console (LSTC), and the Lasercomm Link Planning & Analysis Center (LPAC), all located at the Johnson Space Center (JSC). O2O utilizes pulse-position modulation (PPM) direct-to-earth services resulting in an 80 Mbps downlink data rate from lunar orbit. The O2O concept of operations is to provide optical services for a minimum of 1 hour per day for each day of the Artemis II mission. O2O will utilize a 10-20 Mbps uplink data rate and 40-260 Mbps downlink data rate, depending on the Artemis II mission phase. The ACCESS project will also provide a centralized mission data interface for user data distribution and storage to the MCC and perform planning and scheduling of services in coordination with the Operations Segment for the O2O Ground Segment. The O2O Ground Segment will support the following O2O mission phases: Pre-Mission Planning; Daily Operations Planning; Event Execution; and Post-Pass Reporting. O2O will be used to exchange data files between Orion and the MCC and to distribute real-time video through the optical downlink service to the MCC; which would not be possible without the high-bandwidth link that O2O will provide to Orion. In this paper, I will discuss the O2O Ground Segment development approach and how it will support these critical O2O functions: plan and schedule the contact; acquire and track the optical link; flow information bidirectionally; distribute information; and control and accommodate the system.

optical communications↗

Neighbors on the Red Planet: Mars Science Laboratory Relay Coordination Post InSight Arrival

The Mars Science Laboratory (MSL) strategic communications planning toolset selects orbiter relay opportunities that the rover will use for transmitting data back to Earth. The toolset was extensively reworked in preparation for the Interior Exploration using Seismic Investigations, Geodesy and Heat Transport's (InSight) arrival at Mars in November 2018 and the regular use of Mars Atmosphere and Volatile Evolution (MAVEN) and Trace Gas Orbiter (TGO) orbiters as relay assets in addition to Mars Reconnaissance Orbiter (MRO) and 2001 Mars Odyssey (ODY). Overflight selection criteria was automated in the new toolset to take into account overflight deconfliction and down-selection as well as tactical timeline planning impacts and total data return. This was done while remaining flexible and configurable for changing mission priorities. As the Curiosity rover ages, the MSL planning team must overcome issues such as reduced budgets, memory bank anomalies, and reduced power availability. These are some examples of factors that affect the strategic communications planning toolset. In addition to adapting to evolving internal mission needs, the toolset must also be flexible to changes in the relay planning interface with other landers. The concept of shared relay or “split passes” was introduced when InSight began operating on Mars just 600 kilometers away and at the same longitude as MSL. This proximity meant that orbiters could now communicate with two landers during the same relay session. Over time, this new operational use-case became common practice as InSight and MSL settled into relay planning negotiations. Today, many TGO relay sessions are shared between MSL and InSight. As more orbiters pursue integrating this capability into nominal relay operations, and more landers arrive on Mars, the strategic communications process and toolsets increases in complexity. Development of a single tool that schedules relay sessions for all orbiters and landers simultaneously may become necessary as the number of Martian spacecraft increases. Examples of how toolset selection criteria and capabilities have helped or hindered MSL planning will be presented. Ongoing improvements to MSL toolsets and processes, as well as to shared relay tools such as Mars Relay Operations Service (MaROS) and General Telecom Predictor (GTP) are also discussed in this paper. Examples of how toolset selection criteria and capabilities have helped or hindered MSL planning will be presented. Ongoing improvements to MSL toolsets and processes, as well as to shared relay tools such as Mars Relay Operations Service (MaROS) and General Telecom Predictor (GTP) are also discussed in this paper.

Vandermey, Nancy↗

Trajectory Design Considerations for Exploration Mission 1

Exploration Mission 1 (EM-1) will be the first mission to send an uncrewed Orion Multi-Purpose Crew Vehicle (MPCV) to cislunar space in the fall of 2019. EM-1 was originally conceived as a lunar free-return mission, but was later changed to a Distant Retrograde Orbit (DRO) mission as a precursor to the Asteroid Redirect Mission. To understand the required mission performance (i.e., propellant requirement), a series of trajectory optimization runs was conducted using JSC's Copernicus spacecraft trajectory optimization tool. In order for the runs to be done in a timely manner, it was necessary to employ a parallelization approach on a computing cluster using a new trajectory scan tool written in Python. Details of the scan tool are provided and how it is used to perform the scans and post-process the results. Initially, a scan of daily due east launched EM-1 DRO missions in 2018 was made. Valid mission opportunities are ones that do not exceed the useable propellant available to perform the required burns. The initial scan data showed the propellant and delta-V performance patterns for each launch period. As questions were raised from different subsystems (e.g., power, thermal, communications, flight operations, etc.), the mission parameters or data that were of interest to them were added to the scan output data file. The additional data includes: (1) local launch and landing times in relation to sunrise and sunset, (2) length of eclipse periods during the in-space portion of the mission, (3) Earth line of sight from cislunar space, (4) Deep Space Network field of view looking towards cislunar space, and (5) variation of the downrange distance from Earth entry interface to splashdown. Mission design trades can also be performed based on the information that the additional data shows. For example, if the landing is in darkness, but the recovery operations team desires a landing in daylight, then an analysis is performed to determine how to change the mission design to meet this request. Also, subsystems request feasibility of alternate or contingency mission designs, such as adding an Orion main engine checkout burn or Orion completing all of its burns using only its auxiliary thrusters. This paper examines and presents the evolving trade studies that incorporate subsystem feedback and demonstrate the feasibility of these constrained mission trajectory designs and contingencies.

Dawn, Timothy F.↗