SEARCH · Search NASA

Results for “COTS actives”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

106 records · Page 6

All sources NASA NTRS DOE OSTI

NASA NTRS2010

Verification Challenges of Dynamic Testing of Space Flight Hardware

The Six Degree-of-Freedom Dynamic Test System (SDTS) is a test facility at the National Aeronautics and Space Administration (NASA) Johnson Space Center in Houston, Texas for performing dynamic verification of space structures and hardware. Some examples of past and current tests include the verification of on-orbit robotic inspection systems, space vehicle assembly procedures and docking/berthing systems. The facility is able to integrate a dynamic simulation of on-orbit spacecraft mating or demating using flight-like mechanical interface hardware. A force moment sensor is utilized for input to the simulation during the contact phase, thus simulating the contact dynamics. While the verification of flight hardware presents many unique challenges, one particular area of interest is with respect to the use of external measurement systems to ensure accurate feedback of dynamic contact. There are many commercial off-the-shelf (COTS) measurement systems available on the market, and the test facility measurement systems have evolved over time to include two separate COTS systems. The first system incorporates infra-red sensing cameras, while the second system employs a laser interferometer to determine position and orientation data. The specific technical challenges with the measurement systems in a large dynamic environment include changing thermal and humidity levels, operational area and measurement volume, dynamic tracking, and data synchronization. The facility is located in an expansive high-bay area that is occasionally exposed to outside temperature when large retractable doors at each end of the building are opened. The laser interferometer system, in particular, is vulnerable to the environmental changes in the building. The operational area of the test facility itself is sizeable, ranging from seven meters wide and five meters deep to as much as seven meters high. Both facility measurement systems have desirable measurement volumes and the accuracies vary within the respective volumes. In addition, because this is a dynamic facility with a moving test bed, direct line-of-sight may not be available at all times between the measurement sensors and the tracking targets. Finally, the feedback data from the active test bed along with the two external measurement systems must be synchronized to allow for data correlation. To ensure the desired accuracy and resolution of these systems, calibration of the systems must be performed regularly. New innovations in sensor technology itself are periodically incorporated into the facility s overall measurement scheme. In addressing the challenges of the measurement systems, the facility is able to provide essential position and orientation data to verify the dynamic performance of space flight hardware.

Winnitoy, Susan↗

NASA NTRS2010

Web Design for Space Operations: An Overview of the Challenges and New Technologies Used in Developing and Operating Web-Based Applications in Real-Time Operational Support Onboard the International Space Station, in Astronaut Mission Planning and Mission Control Operations

The International Space Station (ISS) Operations Planning Team, Mission Control Centre and Mission Automation Support Network (MAS) have all evolved over the years to use commercial web-based technologies to create a configurable electronic infrastructure to manage the complex network of real-time planning, crew scheduling, resource and activity management as well as onboard document and procedure management required to co-ordinate ISS assembly, daily operations and mission support. While these Web technologies are classified as non-critical in nature, their use is part of an essential backbone of daily operations on the ISS and allows the crew to operate the ISS as a functioning science laboratory. The rapid evolution of the internet from 1998 (when ISS assembly began) to today, along with the nature of continuous manned operations in space, have presented a unique challenge in terms of software engineering and system development. In addition, the use of a wide array of competing internet technologies (including commercial technologies such as .NET and JAVA ) and the special requirements of having to support this network, both nationally among various control centres for International Partners (IPs), as well as onboard the station itself, have created special challenges for the MCC Web Tools Development Team, software engineers and flight controllers, who implement and maintain this system. This paper presents an overview of some of these operational challenges, and the evolving nature of the solutions and the future use of COTS based rich internet technologies in manned space flight operations. In particular this paper will focus on the use of Microsoft.s .NET API to develop Web-Based Operational tools, the use of XML based service oriented architectures (SOA) that needed to be customized to support Mission operations, the maintenance of a Microsoft IIS web server onboard the ISS, The OpsLan, functional-oriented Web Design with AJAX

Khan, Ahmed↗

NASA NTRS2003

XML: James Webb Space Telescope Database Issues, Lessons, and Status

This paper will present the current concept using extensible Markup Language (XML) as the underlying structure for the James Webb Space Telescope (JWST) database. The purpose of using XML is to provide a JWST database, independent of any portion of the ground system, yet still compatible with the various systems using a variety of different structures. The testing of the JWST Flight Software (FSW) started in 2002, yet the launch is scheduled for 2011 with a planned 5-year mission and a 5-year follow on option. The initial database and ground system elements, including the commands, telemetry, and ground system tools will be used for 19 years, plus post mission activities. During the Integration and Test (I&T) phases of the JWST development, 24 distinct laboratories, each geographically dispersed, will have local database tools with an XML database. Each of these laboratories database tools will be used for the exporting and importing of data both locally and to a central database system, inputting data to the database certification process, and providing various reports. A centralized certified database repository will be maintained by the Space Telescope Science Institute (STScI), in Baltimore, Maryland, USA. One of the challenges for the database is to be flexible enough to allow for the upgrade, addition or changing of individual items without effecting the entire ground system. Also, using XML should allow for the altering of the import and export formats needed by the various elements, tracking the verification/validation of each database item, allow many organizations to provide database inputs, and the merging of the many existing database processes into one central database structure throughout the JWST program. Many National Aeronautics and Space Administration (NASA) projects have attempted to take advantage of open source and commercial technology. Often this causes a greater reliance on the use of Commercial-Off-The-Shelf (COTS), which is often limiting. In our review of the database requirements and the COTS software available, only very expensive COTS software will meet 90% of requirements. Even with the high projected initial cost of COTS, the development and support for custom code over the 19-year mission period was forecasted to be higher than the total licensing costs. A group did look at reusing existing database tools and formats. If the JWST database was already in a mature state, the reuse made sense, but with the database still needing to handing the addition of different types of command and telemetry structures, defining new spacecraft systems, accept input and export to systems which has not been defined yet, XML provided the flexibility desired. It remains to be determined whether the XML database will reduce the over all cost for the JWST mission.

Detter, Ryan↗

NASA NTRS2015

NASA Propulsion Sub-System Concept Studies and Risk Reduction Activities for Resource Prospector Lander

NASA's exploration roadmap is focused on developing technologies and performing precursor missions to advance the state of the art for eventual human missions to Mars. One of the key components of this roadmap is various robotic missions to Near-Earth Objects, the Moon, and Mars to fill in some of the strategic knowledge gaps. The Resource Prospector (RP) project is one of these robotic precursor activities in the roadmap. RP is a multi-center and multi-institution project to investigate the polar regions of the Moon in search of volatiles. The mission is rated Class D and is approximately 10 days, assuming a five day direct Earth to Moon transfer. Because of the mission cost constraint, a trade study of the propulsion concepts was conducted with a focus on available low-cost hardware for reducing cost in development, while technical risk, system mass, and technology advancement requirements were also taken into consideration. The propulsion system for the lander is composed of a braking stage providing a high thrust to match the lander's velocity with the lunar surface and a lander stage performing the final lunar descent. For the braking stage, liquid oxygen (LOX) and liquid methane (LCH4) propulsion systems, derived from the Morpheus experimental lander, and storable bi-propellant systems, including the 4th stage Peacekeeper (PK) propulsion components and Space Shuttle orbital maneuvering engine (OME), and a solid motor were considered for the study. For the lander stage, the trade study included miniaturized Divert Attitude Control System (DACS) thrusters (Missile Defense Agency (MDA) heritage), their enhanced thruster versions, ISE-100 and ISE-5, and commercial-off-the-shelf (COTS) hardware. The lowest cost configuration of using the solid motor and the PK components while meeting the requirements was selected. The reference concept of the lander is shown in Figure 1. In the current reference configuration, the solid stage is the primary provider of delta-V. It will generate 15,000-lbf of thrust with a single burn of ~ 80's seconds. The lander stage is a bi-propellant, pressure-regulated, pulsing liquid propulsion system to perform all other functions.

Trinh, Huu P.↗

NASA NTRS2011

Ground Processing Affordability for Space Vehicles

Launch vehicles and most of their payloads spend the majority of their time on the ground. The cost of ground operations is very high. So, why so often is so little attention given to ground processing during development? The current global space industry and economic environment are driving more need for efficiencies to save time and money. Affordability and sustainability are more important now than ever. We can not continue to treat space vehicles as mere science projects. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability which are not available for ELV's (Expendable Launch Vehicles). More human-rated vehicles are being developed, with the retirement of the Space Shuttles, and for a new global space race, yet these cost more than the many unmanned vehicles of today. We can learn many lessons on affordability from RLV's. DFO (Design for Operations) considers ground operations during design, development, and manufacturing-before the first flight. This is often minimized for space vehicles, but is very important. Vehicles are designed for launch and mission operations. You will not be able to do it again if it is too slow or costly to get there. Many times, technology changes faster than space products such that what is launched includes outdated features, thus reducing competitiveness. Ground operations must be considered for the full product Lifecycle, from concept to retirement. Once manufactured, launch vehicles along with their payloads and launch systems require a long path of processing before launch. Initial assembly and testing always discover problems to address. A solid integration program is essential to minimize these impacts, as was seen in the Constellation Ares I-X test rocket. For RLV's, landing/recovery and post-flight turnaround activities are performed. Multi-use vehicles require reconfiguration. MRO (Maintenance, Repair, and Overhaul) must be well-planned--- even for the unplanned problems. Defect limits and standard repairs need to be in-place as well as easily added. Many routine inspections and maintenance can be like an aircraft overhaul. Modifications and technology upgrades should be expected. Another factor affecting ground operations efficiency is trending. It is essential for RLV's, and also useful for ELV's which fly the same or similar models again. Good data analysis of technical and processing performance will determine fixes and improvements needed for safety, design, and future processing. Collecting such data on new or low-frequency vehicles is a challenge. Lessons can be learned from the Space Shuttle, or even the Concorde aircraft. For all of the above topics, efficient business systems must be established for comprehensive program management and good throughput. Drawings, specifications, and manuals for an entire launch vehicle are often in different formats from multiple vendors, plus they have proprietary constraints. Nonetheless, the integration team must ensure that all data needed is compatible and visible to each appropriate team member. Ground processing systems for scheduling, tracking, problem resolution, etc. must be well laid-out. The balance between COTS (commercial off the shelf) and custom software is difficult. Multiple customers, vendors, launch sites, and landing sites add to the complexity of efficient IT (Information Technology) tools.

Ingalls, John↗

NASA NTRS2018

NOS3: NASA Operational Simulator for Small Satellites

The NASA Operational Simulator for Small Satellites (NOS3) is a suite of open-source software tools to aid in areas such as software development, integration & test (I&T), mission operations/training, verification and validation (V&V), and software systems check-out. NOS3 provides a software development environment, a multi-target build system, operational interface/ground software, dynamics and environment simulations, and software-based hardware models. NOS3 has just recently been open-sourced by NASA and is available for immediate use. It enables the development of flight software (FSW) early in the project life cycle when hardware availability is limited. Small satellite development suffers from extensive lead times on many of the commercial-off-the-shelf (COTS) components as well as limited funding for engineering test units (ETUs). To alleviate the need to provide a hardware test-bed for each developer/tester, NOS3 hardware models are based upon characteristic data or manufacturer's data sheets for each individual component. The NOS3 hardware models' fidelity is such that FSW executes unaware that physical hardware is not present. This allows FSW binaries to be compiled for both the simulation environment and the flight computer without changing the FSW source code. For hardware models that provide data which is dependent upon the environment and spacecraft dynamics, such as a GPS receiver or magnetometer, an open-source tool from NASA GSFC (42 Spacecraft Simulator) is used to provide the necessary data. The underlying infrastructure used to transfer messages between FSW and the hardware models can also be used to monitor, intercept, and inject messages, which has proven to be beneficial for V&V of larger missions such as James Webb Space Telescope (JWST). As hardware is selected and becomes available, drivers can be added to the NOS3 environment to enable hardware-in-the-loop (HWIL) testing. When strict time synchronization is not vital, any number of combinations of hardware components and software-based models can be tested. NOS3 was actively used for FSW development and component testing of the Simulation-to-Flight 1 (STF-1) CubeSat and the Lunar IceCube CubeSat. As NOS3 matures, hardware models have been added for common small satellite components such as GPS receivers, electrical power systems and batteries, and antenna systems.

Suder, Mark↗

NASA NTRS2006

Non Radiation Hardened Microprocessors in Spaced Based Remote Sensing Systems

The CALIPSO (Cloud-Aerosol Lidar and Infrared Pathfinder Satellite Observations) mission is a comprehensive suite of active and passive sensors including a 20Hz 230mj Nd:YAG lidar, a visible wavelength Earth-looking camera and an imaging infrared radiometer. CALIPSO flies in formation with the Earth Observing System Post-Meridian (EOS PM) train, provides continuous, near-simultaneous measurements and is a planned 3 year mission. CALIPSO was launched into a 98 degree sun synchronous Earth orbit in April of 2006 to study clouds and aerosols and acquires over 5 gigabytes of data every 24 hours. The ground track of one CALIPSO orbit as well as high and low intensity South Atlantic Anomaly outlines is shown. CALIPSO passes through the SAA several times each day. Spaced based remote sensing systems that include multiple instruments and/or instruments such as lidar generate large volumes of data and require robust real-time hardware and software mechanisms and high throughput processors. Due to onboard storage restrictions and telemetry downlink limitations these systems must pre-process and reduce the data before sending it to the ground. This onboard processing and realtime requirement load may mean that newer more powerful processors are needed even though acceptable radiation-hardened versions have not yet been released. CALIPSO's single board computer payload controller processor is actually a set of four (4) voting non-radiation hardened COTS Power PC 603r's built on a single width VME card by General Dynamics Advanced Information Systems (GDAIS). Significant radiation concerns for CALIPSO and other Low Earth Orbit (LEO) satellites include the South Atlantic Anomaly (SAA), the north and south poles and strong solar events. Over much of South America and extending into the South Atlantic Ocean the Van Allen radiation belts dip to just 200-800km and spacecraft entering this area are subjected to high energy protons and experience higher than normal Single Event Upset (SEU) and Single Event Latch-up (SEL) rates. Although less significant, spacecraft flying in the area around the poles experience similar upsets. Finally, powerful solar proton events in the range of 10MeV/10pfu to 100MeV/1pfu as are forecasted and tracked by NOAA's Space Environment Center in Colorado can result in Single Event Upset (SEU), Single Event Latch-up (SEL) and permanent failures such as Single Event Gate Rupture (SEGR) in some technologies. (Galactic Cosmic Rays (GCRs) are another source, especially for gate rupture) CALIPSO mitigates common radiation concerns in its data handling through the use of redundant processors, radiation-hardened Application Specific Integrated Circuits (ASIC), hardware-based Error Detection and Correction (EDAC), processor and memory scrubbing, redundant boot code and mirrored files. After presenting a system overview this paper will expand on each of these strategies. Where applicable, related on-orbit data collected since the CALIPSO initial boot on May 4, 2006 will be noted.

Decoursey, Robert J.↗

NASA NTRS2016

NASA Operational Simulator for Small Satellites: Tools for Software Based Validation and Verification of Small Satellites

The NASA Operational Simulator for Small Satellites (NOS3) is a suite of tools to aid in areas such as software development, integration test (IT), mission operations training, verification and validation (VV), and software systems check-out. NOS3 provides a software development environment, a multi-target build system, an operator interface-ground station, dynamics and environment simulations, and software-based hardware models. NOS3 enables the development of flight software (FSW) early in the project life cycle, when access to hardware is typically not available. For small satellites there are extensive lead times on many of the commercial-off-the-shelf (COTS) components as well as limited funding for engineering test units (ETU). Considering the difficulty of providing a hardware test-bed to each developer tester, hardware models are modeled based upon characteristic data or manufacturers data sheets for each individual component. The fidelity of each hardware models is such that FSW executes unaware that physical hardware is not present. This allows binaries to be compiled for both the simulation environment, and the flight computer, without changing the FSW source code. For hardware models that provide data dependent on the environment, such as a GPS receiver or magnetometer, an open-source tool from NASA GSFC (42 Spacecraft Simulation) is used to provide the necessary data. The underlying infrastructure used to transfer messages between FSW and the hardware models can also be used to monitor, intercept, and inject messages, which has proven to be beneficial for VV of larger missions such as James Webb Space Telescope (JWST). As hardware is procured, drivers can be added to the environment to enable hardware-in-the-loop (HWIL) testing. When strict time synchronization is not vital, any number of combinations of hardware components and software-based models can be tested. The open-source operator interface used in NOS3 is COSMOS from Ball Aerospace. For testing, plug-ins are implemented in COSMOS to control the NOS3 simulations, while the command and telemetry tools available in COSMOS are used to communicate with FSW. NOS3 is actively being used for FSW development and component testing of the Simulation-to-Flight 1 (STF-1) CubeSat. As NOS3 matures, hardware models have been added for common CubeSat components such as Novatel GPS receivers, ClydeSpace electrical power systems and batteries, ISISpace antenna systems, etc. In the future, NASA IVV plans to distribute NOS3 to other CubeSat developers and release the suite to the open-source community.

Verification↗

NASA NTRS2020

PHALANX: Expendable Projectile Sensor Networks for Planetary Exploration

Technologies enabling long-term, wide-ranging measurement in hard-to-reach areas are a critical need for planetary science inquiry. Phenomena of interest include flows or variations in volatiles, gas composition or concentration, particulate density, or even simply temperature. Improved measurement of these processes enables understanding of exotic geologies and distributions or correlating indicators of trapped water or biological activity. However, such data is often needed in unsafe areas such as caves, lava tubes, or steep ravines not easily reached by current spacecraft and planetary robots. To address this capability gap, we have developed miniaturized, expendable sensors which can be ballistically lobbed from a robotic rover or static lander - or even dropped during a flyover. These projectiles can perform sensing during flight and after anchoring to terrain features. By augmenting exploration systems with these sensors, we can extend situational awareness, perform long-duration monitoring, and reduce utilization of primary mobility resources, all of which are crucial in surface missions. We call the integrated payload that includes a cold gas launcher, smart projectiles, planning software, network discovery, and science sensing: PHALANX. In this paper, we introduce the mission architecture for PHALANX and describe an exploration concept that pairs projectile sensors with a rover “mothership.” Science use cases explored include reconnaissance using ballistic cameras, volatiles detection, and building timelapse maps of temperature and illumination conditions. Strategies to autonomously coordinate constellations of deployed sensors to self-discover and localize with peer ranging (i.e. a “local GPS”) are summarized, thus providing communications infrastructure beyond-line-of-sight (BLOS) of the rover. Capabilities were demonstrated through both simulation and physical testing with a terrestrial prototype. The approach to developing a terrestrial prototype is discussed, including design of the launching mechanism, projectile optimization, micro-electronics fabrication, and sensor selection. Results from early testing and characterization of commercial-off-the-shelf (COTS) components are reported. Nodes were subjected to successful burn-in tests over 48 hours at full logging duty cycle. Integrated field tests were conducted in the Roverscape, a half-acre planetary analog environment at NASA Ames, where we tested up to 10 sensor nodes simultaneously coordinating with an exploration rover. Ranging accuracy has been demonstrated to be within +/-10cm over 20m using commodity radios when compared to high-resolution laser scanner ground truthing. Evolution of the design, including progressive miniaturization of the electronics and iterated modifications of the enclosure housing for streamlining and optimized radio performance are described. Finally, lessons learned to date, gaps toward eventual flight mission implementation, and continuing future development plans are discussed.

Dille, Michael↗

NASA NTRS2008

Evolution and Reengineering of NASA's Flight Dynamics Facility (FDF)

The NASA Goddard Space Flight Center's Flight Dynamics Facility (FDF) is a multimission support facility that performs ground navigation and spacecraft trajectory design services for a wide range of scientific satellites. The FDF also supports the NASA Space Network by providing orbit determination and tracking data evaluation services for the Tracking Data Relay Satellite System (TDRSS). The FDF traces its history to early NASA missions in the 1960's, including navigation support to the Apollo lunar missions. Over its 40 year history, the FDF has undergone many changes in its architecture, services offered, missions supported, management approach, and business operation. As a fully reimbursable facility (users now pay 100% of all costs for FDF operations and sustaining engineering activities), the FDF has faced significant challenges in recent years in providing mission critical products and services at minimal cost while defining and implementing upgrades necessary to meet future mission demands. This paper traces the history of the FDF and discusses significant events in the past that impacted the FDF infrastructure and/or business model, and the events today that are shaping the plans for the FDF in the next decade. Today's drivers for change include new mission requirements, the availability of new technology for spacecraft navigation, and continued pressures for cost reduction from FDF users. Recently, the FDF completed an architecture study based on these drivers that defines significant changes planned for the facility. This paper discusses the results of this study and a proposed implementation plan. As a case study in how flight dynamics operations have evolved and will continue to evolve, this paper focuses on two periods of time (1992 and the present) in order to contrast the dramatic changes that have taken place in the FDF. This paper offers observations and plans for the evolution of the FDF over the next ten years. Finally, this paper defines the mission model of the future for the FDF based on NASA's current mission list and planning for the Constellation Program. As part of this discussion the following are addressed: the relevance and benefits of a multi-mission facility for NASA's navigation operations in the future; anticipated technologies affecting ground orbit determination; continued incorporation of Commercial Off-the-shelf (COTS) software into the FDF; challenges of a business model that relies entirely on user fees to fund facility upgrades; anticipated changes in flight dynamics services required; and considerations for defining architecture upgrades given a set of cost drivers.

Stengle, Thomas↗

NASA NTRS2009

Low Cost Rapid Response Spacecraft, (LCRRS): A Research Project in Low Cost Spacecraft Design and Fabrication in a Rapid Prototyping Environment

The Low Cost Rapid Response Spacecraft (LCRRS) is an ongoing research development project at NASA Ames Research Center (ARC), Moffett Field, California. The prototype spacecraft, called Cost Optimized Test for Spacecraft Avionics and Technologies (COTSAT) is the first of what could potentially be a series of rapidly produced low-cost satellites. COTSAT has a target launch date of March 2009 on a SpaceX Falcon 9 launch vehicle. The LCRRS research system design incorporates use of COTS (Commercial Off The Shelf), MOTS (Modified Off The Shelf), and GOTS (Government Off The Shelf) hardware for a remote sensing satellite. The design concept was baselined to support a 0.5 meter Ritchey-Chretien telescope payload. This telescope and camera system is expected to achieve 1.5 meter/pixel resolution. The COTSAT team is investigating the possibility of building a fully functional spacecraft for $500,000 parts and $2,000,000 labor. Cost is dramatically reduced by using a sealed container, housing the bus and payload subsystems. Some electrical and RF designs were improved/upgraded from GeneSat-1 heritage systems. The project began in January 2007 and has yielded two functional test platforms. It is expected that a flight-qualified unit will be finished in December 2008. Flight quality controls are in place on the parts and materials used in this development with the aim of using them to finish a proto-flight satellite. For LEO missions the team is targeting a mission class requiring a minimum of six months lifetime or more. The system architecture incorporates several design features required by high reliability missions. This allows for a true skunk works environment to rapidly progress toward a flight design. Engineering and fabrication is primarily done in-house at NASA Ames with flight certifications on materials. The team currently employs seven Full Time Equivalent employees. The success of COTSATs small team in this effort can be attributed to highly cross trained engineering team. The engineers on the team are capable of functioning in two to three engineering disciplines which allows highly efficient interdisciplinary engineering collaboration. NASA Ames is actively proposing mission concepts to use the COTSAT platform to accomplish science. If the COTSAT team validates this approach, it will allow the possibility for remote sensing missions to produce a high science yield for minimal cost and reduced schedule. Another aim of this approach is to yield an accelerated pathway from a Phase A study to mission launch. Leaders in the aerospace industry have shown interest in this methodology. Several visits and tours have been given in the lab. Although the concept of low-cost development is initially met with skepticism from some within the prohibitive aerospace industry, the project's efforts have been highly praised for the accomplishments met within a limited time and budget. Overall the development has progressed tremendously well and the team is answering critical questions for current and future low-cost small satellite developments. COTSAT subsystems are not limited to a specific weight class and could be adapted to produce smaller platforms and to fit various launch vehicles.

Spremo, Stevan↗

NASA NTRS2001

Automating Trend Analysis for Spacecraft Constellations

Spacecraft trend analysis is a vital mission operations function performed by satellite controllers and engineers, who perform detailed analyses of engineering telemetry data to diagnose subsystem faults and to detect trends that may potentially lead to degraded subsystem performance or failure in the future. It is this latter function that is of greatest importance, for careful trending can often predict or detect events that may lead to a spacecraft's entry into safe-hold. Early prediction and detection of such events could result in the avoidance of, or rapid return to service from, spacecraft safing, which not only results in reduced recovery costs but also in a higher overall level of service for the satellite system. Contemporary spacecraft trending activities are manually intensive and are primarily performed diagnostically after a fault occurs, rather than proactively to predict its occurrence. They also tend to rely on information systems and software that are oudated when compared to current technologies. When coupled with the fact that flight operations teams often have limited resources, proactive trending opportunities are limited, and detailed trend analysis is often reserved for critical responses to safe holds or other on-orbit events such as maneuvers. While the contemporary trend analysis approach has sufficed for current single-spacecraft operations, it will be unfeasible for NASA's planned and proposed space science constellations. Missions such as the Dynamics, Reconnection and Configuration Observatory (DRACO), for example, are planning to launch as many as 100 'nanospacecraft' to form a homogenous constellation. A simple extrapolation of resources and manpower based on single-spacecraft operations suggests that trending for such a large spacecraft fleet will be unmanageable, unwieldy, and cost-prohibitive. It is therefore imperative that an approach to automating the spacecraft trend analysis function be studied, developed, and applied to missions such as DRACO with the intent that mission operations costs be significantly reduced. The goal of the Constellation Spacecraft Trend Analysis Toolkit (CSTAT) project is to serve as the pathfinder for a fully automated trending system to support spacecraft constellations. The development approach to be taken is evolutionary. In the first year of the project, the intent is to significantly advance the state of the art in current trending systems through improved functionality and increased automation. In the second year, the intent is to add an expert system shell, likely through the adaptation of an existing commercial-off-the-shelf (COTS) or government-off-the-shelf (GOTS) tool to implement some level of the trending intelligence that humans currently provide in manual operations. In the third year, the intent is to infuse the resulting technology into a near-term constellation or formation-flying mission to test it and gain experience in automated trending. The lessons learned from the real missions operations experience will then be used to improve the system, and to ultimately incorporate it into a fully autonomous, closed-loop mission operations system that is truly capable of supporting large constellations. In this paper, the process of automating trend analysis for spacecraft constellations will be addressed. First, the results of a survey on automation in spacecraft mission operations in general, and in trending systems in particular will be presented to provide an overview of the current state of the art. Next, a rule-based model for implementing intelligent spacecraft subsystem trending will be then presented, followed by a survey of existing COTS/GOTS tools that could be adapted for implementing such a model. The baseline design and architecture of the CSTAT system will be presented. Finally, some results obtained from initial software tests and demonstrations will be presented.

Davis, George↗

NASA NTRSDate not supplied

In-Situ Reaction Monitoring for Lunar Applications Utilizing a Single Quadrupole Residual Gas Analyzer

With a revived focus to create a permeant presence on the moon and in preparation for future Mars exploration, it is imperative that all re-sources are utilized to their fullest potential. In-Situ Resource Utilization (ISRU) will be critical for future mission success as it would enable independent operation of missions while minimally relying on the complex supply chain created between the Earth, moon and Mars. One of the most critical resources that have been identified for ISRU is the creation of liquid oxygen (O2) for not only breathable air, but also for rocket fuel. On the moon and potentially Mars, one of the most O2 rich resources is in the presence of regolith. Although there are numerous minerals within regolith and various processes to extract O2, this is not the scope of this paper. Since the O2 extraction method can vary, a critical standardized analytical method is needed to verify O2 (or oxygenated precursor compounds) for extraction efficiency and purity. Our group utilizes a modified consumer off-the-shelf (COTS), Residual Gas Analyzer (RGA) Single Quadrupole Mass Spectrometer (QMS). Due to the current field mission requirements, the gas analysis module will need to rely only on mass-to-charge ratios (m/z) and peak intensities to differentiate and quantitate targeted gas-phase reactants or products, i.e. carbon monoxide (CO), carbon dioxide (CO2), methane (CH4) and hydrogen (H2). However, due to solar wind implanted volatiles and various other compounds present in lunar regolith, such as nitrogen (N2), helium (He), and deuterium (D2), deconvolution and quantification of isobaric compounds becomes quite difficult. Specifically, the presence of N2 makes quantification of CO, an oxygenated precursor, difficult due to both compounds having a peak at m/z 28. Approaches to differentiate isobaric components: Initially, the solution to overcome isobaric overlap was to use isotopic ratios, particularly be-tween carbon-13 and nitrogen-15. Although limited literature discuss isotopic composition and attempt to quantify the ratios, variation is particularly high and limited to a few lunar regolith samples. The following were identified as potential approaches to quantify isobaric species, N2 and CO, using our RGA. Threshold Ionization. CO and N2 both have peaks at m/z 28, but only N2 is capable of producing a peak at m/z 7. While a N2 peak at m/z 7 is generally rare, instrument parameters can be optimized in order to maximize the peak intensity. Typically a standard ionization energy of 70 eV is used to monitor a batch process and would produce reliable results for a majority of the reactants or products that we are interested in quantifying. However, to analyze the rare molecular fragment of N2 (N2+ at m/z 7), a different ionization energy may be beneficial. Threshold Ionization Mass Spectrometry (TIMS) will be explored to optimize the N2+ peak at m/z 7 by varying parameters such as ionization energy and pressure. Therefore, a quantitative value at m/z 7 will be used to determine the product gas concentration of N2, which will be subtracted from the total concentration determined at m/z 28 enabling us to approximate the amount of CO. Secondary Detector (infrared gas detector, IR). Another approach to quantitate and differentiate be-tween isobaric components is to leverage alternative modes of detection. Unlike mass spectrometry, which generally uses a separation step prior to analysis (i.e. gas chromatography), IR produces energy that is specifically absorbed depending on the bond and configuration of the molecule. This technique could be leveraged since it is generally only active on non-symmetric molecules, i.e. CO. Utilizing concentrations of CO determined from another detector could help correct concentrations of CO obtained from the QMS. However, the inclusion of another detector adds additional mission requirements, such as power, software changes and avionics updates that add additional cost and schedule requirements.

mass spectrometry↗

NASA NTRS2024

ISS Technology Demonstrations for Future Spaceflight Medical Systems

Throughout the history of human spaceflight, crewmembers have experienced various in-flight medical conditions including illness and injury. Planned missions to the Moon and Mars will require capabilities to maintain the health of future space travelers. Mass, power, and volume available in the vehicles and habitats for these missions will be severely constrained; resupply of resources will be limited or non-existent, as will opportunities for evacuation to Earth. Furthermore, ground-based support will be hampered by communication latencies and blackouts. These vehicle and mission constraints will necessitate a medical system that has been efficiently planned, providing on-board procedural guidance in addition to a variety of medical devices and consumable resources. Medical capabilities required for the diagnosis and treatment of potential medical conditions during future spaceflight missions may include real-time health monitoring, medical imaging, and biomarker analyses ( e.g., blood or urine). Terrestrial medicine shares these needs, thus many of these medical capabilities could likely be satisfied by Commercial-Off-The-Shelf (COTS) devices and methodologies; however, in some cases the unique space environment and increased mission duration will drive the need to modify technologies and the way care is provided. NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) Element and Mars Campaign Office’s Exploration Medical Integrated Product Team (XMIPT) are working together to decrease medical risk during exploration missions. Flight-tested medical diagnostic and treatment technologies are necessary to effectively manage medical conditions relevant to exploration missions while meeting vehicle constraints, integrating with medical decision-support tools, and enabling increasingly Earth-independent operations. Several projects have leveraged the ISS as a testbed for exploration, including 1) i n- situ blood analysis, 2) medical inventory, 3) intravenous fluid generation, and 4) autonomous medical procedure guidance. Management of several in-flight medical conditions, such as bacterial and viral infections and acute radiation syndrome, is dramatically improved with ability to assess blood cell populations, electrolytes, and metabolites. I n December 2020 and January 2021 ExMC performed an ISS technology demonstration (Tech Demo) of the HemoCue® WBC DIFF analyzer (HemoCue, Brea, CA), a COTS device that was modified to enable functionality in a spaceflight environment. This Tech Demo marked the first time that hematology measurements were successfully performed real-time in microgravity. Also modified and demonstrated was the reusable Handheld Electrolytes and Lab Technology for Humans (rHEALTH) ONE analyzer (rHEALTH, Bedford, MA), which uses flow cytometry and sheath-based hydrodynamic focusing methodologies. The rHEALTH ONE ISS Tech Demo in May 2022 demonstrated test results obtained in-flight matched those on the ground. NASA currently relies on crew self-reporting to manage and maintain medical inventory on ISS.The ability to maintain an accurate inventory becomes more critical during long duration missions since the crew will need to be increasingly autonomous in finding and utilizing medical items, including those scenarios when alternative treatments need to be considered due to limited or no resupply. HRP’s Medical Consumables Tracking (MCT) project was developed by ZIN Technologies, Inc. (Cleveland, OH), and demonstrated real-time tracking of medical supplies aboard the ISS between December 2016 and July 2018. The MCT system design utilized Radio Frequency Identification Device (RFID) technology to perform automated inventory and was installed in the Crew Health Care System (CHeCS) Resupply Stowage Rack (RSR). The challenge of limited shelf life, exacerbated by the lack of resupply opportunities, affects a plethora of medical system components including consumables, pharmaceuticals, and intravenous (IV) fluid. In 2010, ExMC funded ZIN Technologies, Inc. (Cleveland, OH), to develop the Intravenous Fluid Generation (IVGEN) system. IV fluids were successfully generated with IVGEN using the potable water supply on ISS during ISS Expedition 23. The XMIPT is in the process of developing a miniaturized version of the original IVGEN hardware for a future Tech Demo aboard the ISS. Current ISS medical operations rely heavily on preflight training and real-time remote guidance, both of which become impractical or impossible for exploration missions. The primary goal of the Autonomous Medical Officer Support (AMOS) Software Tech Demos on ISS was to confirm telemedical proof-of-concept for autonomous medical imaging in an operational setting. This novel software tool shifts emphasis from preflight training and real-time remote guidance to in-flight just-in-time instruction, a new and necessary paradigm for crew medical autonomy. AMOS introduces a novel, streamlined skill management concept for exploration missions featuring comprehensive training and guidance modules for ultrasound examinations using the ISS Ultrasound 2 (a modified GE Vivid-q™; General Electric HealthCare, Chicago, IL). With no prior crew training or remote guidance, two Tech Demos on the ISS (April 2020 and June 2022) resulted in high quality, clinically useful image sets. We will provide a review of historical, current, and planned medical devices and technologies considered for inclusion within future spaceflight medical systems and summarize hardware development activities and medical device tech demos conducted on the ISS.

Astronaut health and performance↗

NASA NTRSDate not supplied

Power Hibernation for Low-Cost Solar Powered Lunar Missions

Because the surface of the Moon drops to cryogenic temperatures, no solar-powered lunar spacecraft have reliably operated beyond a single lunar day. Passive thermal control cannot keep a spacecraft sufficiently warm for the 354-hour lunar night, and active thermal control requires a dramatic increase in battery mass at the expense of payload mass. Extreme conditions seen on the lunar surface suggest a radioisotope solution is ideal, but mass, cost, and schedule are inconsistent with low-cost frequent flight intent of the commercial lunar payload services (CLPS) program. To solve the issue of lunar night survivability without radioisotope sources of power and heat, a lunar power hibernation approach is being developed at the Glenn Research Center, which exploits the ability of common 18650 Lithium-ion cells to passively survive cryogenic freeze-thaw cycles and recover without apparent performance degradation. A key aspect of this hibernation approach is the use of cryogenically operable electronics that safely manage the restoration of the battery thermal environment at lunar dawn. A spacecraft utilizing this strategy will operate into the lunar night on batteries until the state of charge or spacecraft temperature reaches a predetermined threshold. At this point, systems are shut down and the battery is isolated from the main bus to prevent charge or discharge during the freezing and thawing transitions. The system remains passive until lunar dawn, where temperatures can reach as low as 50 K. All electronics must be tolerant to these conditions. When the solar arrays are finally illuminated at lunar dawn, the main bus power electronics will initiate a “cold start” and begin regulating array power. The main bus electronics must be designed to operate at cryogenic temperatures. Array power is used to warm the battery and passive electronics back to operational temperatures. Once batteries are returned to normal temperatures, diagnostics and precharging is performed, as needed, and the battery is reconnected. The overall spacecraft system reboots and returns to nominal operations until lunar night returns. To assure that we can develop batteries suited for many hibernation freeze/thaw cycles, STMD Space Technology Research Grant Program (STRG) has selected two principal investigators that will thoroughly characterize of the Li-ion cell through the freeze-thaw process, investigate degradation mechanisms, and identify potential diagnostic techniques. STMD STRG is also funding an investigation of Gallium-Nitride semiconductors for cryogenic power applications. This work includes physics-informed modeling that considers cryogenic conductivity, carrier mobility, and quantum effects that govern semiconductor performance at cryogenic temperatures. These models can enable engineers to develop accurate cryogenic simulation models that assist in the design of power controls stable over the entire lunar surface temperature range. Meanwhile, Glenn is performing cryogenic testing of batteries and electronics, establishing design guidelines for power applications in extreme cold lunar environment, and potentially developing a hibernation technology demonstrator. The hibernation approach will enable low-cost lunar robotic missions to extend their operating lifetime to many months while minimizing development costs and impact on payload capacity. The need for cryogenically operable electronics is restricted to only main bus power and battery controls, as the majority of systems simply need to passively tolerate cryogenic temperatures. This allows developers to continue to exploit the cost savings of legacy and COTS hardware with minimum modification. For these reasons, lunar power hibernation is a viable near-term solution for lunar night survivability for solar powered commercial landers.

Space power↗

NASA NTRS2022

SpaceVPX Interoperability Assessment

The existing VMEbus (VersaModular Eurocard bus) International Trade Association (VITA)-78 industry standard, also known as SpaceVPX, is an avionics board- and chassis-level standard derived from the OpenVPX standard as defined in VITA-65. While VITA-65 defines backplane and board-level profiles from COTS vendors to ensure interoperability of products used in developing systems and subsystems, the VITA-78 standard defines SpaceVPX to incorporate fault tolerance features that are required by many spaceflight systems. However, VITA-78 allows so much flexibility that interoperability between modules cannot be assured. This assessment provides guidelines on the use of, and extensions to, the VITA-78 standard to enable avionics interoperability for future NASA missions. The assessment team was comprised of subject matter experts (SMEs) from Goddard Space Flight Center (GSFC), the Jet Propulsion Laboratory (JPL), Johnson Space Center (JSC), and Langley Research Center (LaRC). The team included valuable external consulting support from a SME who was a key participant in the development of the VITA-78 standard. The team had extensive collaboration with the NASA Space Technology Mission Directorate (STMD) High Performance Spaceflight Computing (HPSC) project, specifically in the development of SpaceVPX interconnect findings, observations, and NESC recommendations. To provide an understanding of the breadth of implementations that SpaceVPX must accommodate, multiple NASA use cases were analyzed to assess the requirements for SpaceVPX implementations across a wide range of NASA missions (Appendix C). Applications included crewed missions, science missions, and orbital and surface robotic systems. Product surveys were conducted to assess the level of industry support for SpaceVPX, applications, and the variations in their implementations (Appendix D). In-depth analysis was conducted in the areas of: (a) power management and distribution, (b) form factors and daughtercards, (c) interconnect, and (d) fault tolerance. Leveraging the use cases, product surveys, and SMEs from multiple NASA Centers, these areas were analyzed to determine the range of implementations permitted by the VITA-78 standard and potential interoperability issues. Applicable findings and NESC recommendations were provided for each area. During this assessment, there were multiple opportunities to engage with other agencies to learn about their interest in SpaceVPX, their strategies for implementing SpaceVPX-based systems, and their internal development efforts. These engagements also generated findings and NESC recommendations. Based on this assessment analysis, NESC recommendations were made regarding the feature set and module profiles to support NASA SpaceVPX implementations. This feature set includes restrictions on features in VITA-78, and extensions to the standard. Key recommendations in this area include the use of 10 Gigabit Ethernet and Peripheral Component Interconnect Express (PCIe) as high bandwidth interconnect on the backplane, the retention of SpaceWire interconnect for control functions, and support for 3U (unit) and 6U, form factors for NASA systems. Restrictions were proposed on the usage of user-defined signals to promote interoperability, and specific power managements and distribution schemes for 3U systems. Beyond the technical implementation of SpaceVPX, recommendations were made on areas that warrant further investigation. Primary among these is the recommendation for NASA to collaborate with other space-going agencies and industry to incorporate recommendations into a future ‘dot spec’ of VITA-78. This would ensure wide adoption and availability of the modules that comply with the specification. The assessment includes appendices with candidate module profiles that can be considered as a starting point for this activity, and example systems based on the recommendations. Follow-on studies are recommended for architectures beyond SpaceVPX to address potential enhancements including condensed set of interconnect, software required to implement protocol layers on the interconnect (and other features), alternative power architectures, and system-level testability.

SpaceVPX↗