Future Avionics for X2K
Explore the source record for details and available documents.
avionics Deep Space System↗
SEARCH · Search NASA
Results for “Space Avionics”
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.
Standard user data services for spacecraft applications
Explore the source record for details and available documents.
standard interaces↗
Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions
The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.
Krihak, M.↗
Medical Data Architecture Platform and Recommended Requirements for A Medical Data System for Exploration Missions
Minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions.In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.
Krihak, M.↗
Survival of spacecraft-associated microorganisms under simulated Martian UV irradiation
Spore-forming microbes recovered from spacecraft surfaces and assembly facilities were exposed to simulated Martian UV irradiation. The effects of UVA (315 to 400 nm), UVA_B (280 to 400 nm), and the full UV spectrum (200 to 400 nm) on the survival of microorganisms were studied at UV intensities expected to strike the surfaces of Mars. Microbial species isolated from the surfaces of several spacecraft, including Mars Odyssey, X-2000 (avionics), and the International Space Station, and their assembly facilities were identified using 16S rRNA gene sequencing. Forty-three Bacillus spore lines were screened, and 19 isolates showed resistance to UVC irradiation (200 to 280 nm) after exposure to 1,000 J m_2 of UVC irradiation at 254 nm using a low-pressure mercury lamp. Spores of Bacillus species isolated from spacecraft-associated surfaces were more resistant than a standard dosimetric strain, Bacillus subtilis 168. In addition, the exposure time required for UVA_B irradiation to reduce the viable spore numbers by 90% was 35-fold longer than the exposure time required for the full UV spectrum to do this, confirming that UVC is the primary biocidal bandwidth. Among the Bacillus species tested, spores of a Bacillus pumilus strain showed the greatest resistance to all three UV bandwidths, as well as the total spectrum. The resistance to simulated Mars UV irradiation was strain specific; B. pumilus SAFR-032 exhibited greater resistance than all other strains tested. The isolation of organisms like B. pumilus SAFR-032 and the greater survival of this organism (sixfold) than of the standard dosimetric strains should be considered when the anitation capabilities of UV irradiation are determined.
Venkateswaran, Kasthuri↗
Radiation and Fault Tolerance for Neuromorphic Computing
• The solar wind emanating from the sun is a stream of energetic electrons and protons and ions that are the primary ionizing radiation contributions. • The Earth’s magnetosphere significantly reduces radiation exposure and mutes the effects of solar flares out to 65K Km orbital altitude. • The radiation environment is highly dependent upon mission profile: for example geosynchronous orbits can see 50 times the radiation dose of a polar orbit due to reduction of atmospheric/magnetospheric shielding. • In LEO, the magnetosphere shields the Earth by creating trapped Van Allen radiation belts consisting of electrons and protons, which create a challenging radiation environment confined to specific regions. • Even for LEO, radiation dose can vary by a factor of 30 or more from a quiet sun to a solar flare. • Galactic Cosmic Rays (GCRs) are also present at very high energy, but at low rates. • Radiation effects on semiconductors are highly dependent upon particles species, energy and flux. • Therefore, radiation tolerance requirements will vary with mission profile and duration.
Space Radiation↗
A Cost Effective System Design Approach for Critical Space Systems
NASA-JSC required an avionics platform capable of serving a wide range of applications in a cost-effective manner. In part, making the avionics platform cost effective means adhering to open standards and supporting the integration of COTS products with custom products. Inherently, operation in space requires low power, mass, and volume while retaining high performance, reconfigurability, scalability, and upgradability. The Universal Mini-Controller project is based on a modified PC/104-Plus architecture while maintaining full compatibility with standard COTS PC/104 products. The architecture consists of a library of building block modules, which can be mixed and matched to meet a specific application. A set of NASA developed core building blocks, processor card, analog input/output card, and a Mil-Std-1553 card, have been constructed to meet critical functions and unique interfaces. The design for the processor card is based on the PowerPC architecture. This architecture provides an excellent balance between power consumption and performance, and has an upgrade path to the forthcoming radiation hardened PowerPC processor. The processor card, which makes extensive use of surface mount technology, has a 166 MHz PowerPC 603e processor, 32 Mbytes of error detected and corrected RAM, 8 Mbytes of Flash, and I Mbytes of EPROM, on a single PC/104-Plus card. Similar densities have been achieved with the quad channel Mil-Std-1553 card and the analog input/output cards. The power management built into the processor and its peripheral chip allows the power and performance of the system to be adjusted to meet the requirements of the application, allowing another dimension to the flexibility of the Universal Mini-Controller. Unique mechanical packaging allows the Universal Mini-Controller to accommodate standard COTS and custom oversized PC/104-Plus cards. This mechanical packaging also provides thermal management via conductive cooling of COTS boards, which are typically designed for convection cooling methods.
Abbott, Larry Wayne↗
Fault tolerant testbed evaluation, phase 1
In recent years, avionics systems development costs have become the driving factor in the development of space systems, military aircraft, and commercial aircraft. A method of reducing avionics development costs is to utilize state-of-the-art software application generator (autocode) tools and methods. The recent maturity of application generator technology has the potential to dramatically reduce development costs by eliminating software development steps that have historically introduced errors and the need for re-work. Application generator tools have been demonstrated to be an effective method for autocoding non-redundant, relatively low-rate input/output (I/O) applications on the Space Station Freedom (SSF) program; however, they have not been demonstrated for fault tolerant, high-rate I/O, flight critical environments. This contract will evaluate the use of application generators in these harsh environments. Using Boeing's quad-redundant avionics system controller as the target system, Space Shuttle Guidance, Navigation, and Control (GN&C) software will be autocoded, tested, and evaluated in the Johnson (Space Center) Avionics Engineering Laboratory (JAEL). The response of the autocoded system will be shown to match the response of the existing Shuttle General Purpose Computers (GPC's), thereby demonstrating the viability of using autocode techniques in the development of future avionics systems.
Caluori, V., Jr.↗
Flight Crew Survey Responses from the Interval Management (IM) Avionics Phase 2 Flight Test
The Interval Management (IM) Avionics Phase 2 flight test used three aircraft over a nineteen day period to operationally evaluate a prototype IM avionics. Quantitative data were collected on aircraft state data and IM spacing algorithm performance, and qualitative data were collected through end-of-scenario and end-of-day flight crew surveys. The majority of the IM operations met the performance goals established for spacing accuracy at the Achieve-by Point and the Planned Termination Point, however there were operations that did not meet goals for a variety of reasons. While the positive spacing accuracy results demonstrate the prototype IM avionics can contribute to the overall air traffic goal, critical issues were also identified that need to be addressed to enhance IM performance. The first category was those issues that impacted the conduct and results of the flight test, but are not part of the IM concept or procedures. These included the design of arrival and approach procedures was not ideal to support speed as the primary control mechanism, the ground-side of the Air Traffic Management Technology Demonstration (ATD-1) integrated concept of operations was not part of the flight test, and the high workload to manually enter the information required to conduct an IM operation. The second category was issues associated with the IM spacing algorithm or flight crew procedures. These issues include the high frequency of IM speed changes and reversals (accelerations), a mismatch between the deceleration rate used by the spacing algorithm and the actual aircraft performance, and some spacing error calculations were sensitive to normal operational variations in aircraft airspeed or altitude which triggered additional IM speed changes. Once the issues in these two categories are addressed, the future IM avionics should have considerable promise supporting the goals of improving system throughput and aircraft efficiency.
Baxley, Brian T.↗
Analysis of debris from Spacelab Space Life Sciences-1
Airborne microbiological and particulate contamination generated aboard Spacelab modules is a potential safety hazard. In order to shed light on the characteristics of these contaminants, microbial and chemical/particulate analyses were performed on debris vacuumed from cabin and avionics air filters in the Space Life Sciences-1 (SLS-1) module of the Space Transportation System 40 (STS-40) mission 1 month after landing. The debris was sorted into categories (e.g., metal, nonmetal, hair/fur, synthetic fibers, food particles, insect fragments, etc.). Elemental analysis of particles was done by energy dispersive analysis of x rays (metals) and Fourier transform infrared spectroscopy (nonmetals). Scanning electron micrographs were done of most particles. Microbiological samples were grown on R2A culture medium and identified. Clothing fibers dominated the debris by volume. Other particles, all attributed to the crew, resulted from abrasions and impacts during missions operations (e.g., paint chips, plastic, electronic scraps and clothing fibers). All bacterial species identified are commonly found in the atmosphere or on the human body. Bacillus sp. was the most frequently seen bacterium. One of the bacterial species, Enterobacter agglomerans, could cause illness in crew members with depressed immune systems.
Caruso, S. V.↗
Investigation of HZETRN 2010 as a Tool for Single Event Effect Qualification of Avionics Systems
NASA's future missions are focused on deep space for human exploration that do not provide a simple emergency return to Earth. In addition, the deep space environment contains a constant background Galactic Cosmic Ray (GCR) radiation exposure, as well as periodic Solar Particle Events (SPEs) that can produce intense amounts of radiation in a short amount of time. Given these conditions, it is important that the avionics systems for deep space human missions are not susceptible to Single Event Effects (SEE) that can occur from radiation interactions with electronic components. The typical process to minimizing SEE effects is through using heritage hardware and extensive testing programs that are very costly. Previous work by Koontz, et al. [1] utilized an analysis-based method for investigating electronic component susceptibility. In their paper, FLUKA, a Monte Carlo transport code, was used to calculate SEE and single event upset (SEU) rates. This code was then validated against in-flight data. In addition, CREME-96, a deterministic code, was also compared with FLUKA and in-flight data. However, FLUKA has a long run-time (on the order of days), and CREME-96 has not been updated in several years. This paper will investigate the use of HZETRN 2010, a deterministic transport code developed at NASA Langley Research Center, as another tool that can be used to analyze SEE and SEU rates. The benefits to using HZETRN over FLUKA and CREME-96 are that it has a very fast run time (on the order of minutes) and has been shown to be of similar accuracy as other deterministic and Monte Carlo codes when considering dose [2, 3, 4]. The 2010 version of HZETRN has updated its treatment of secondary neutrons and thus has improved its accuracy over previous versions. In this paper, the Linear Energy Transfer (LET) spectra are of interest rather than the total ionizing dose. Therefore, the LET spectra output from HZETRN 2010 will be compared with the FLUKA and in-flight data to validate HZETRN 2010 as a computational tool for SEE qualification by analysis. Furthermore, extrapolation of these data to interplanetary environments at 1 AU will be investigated to determine whether HZETRN 2010 can be used successfully and confidently for deep space mission analyses.
Rojdev, Kristina↗
NASA JSC EV2 Intern Spring 2016 - Jennie Chung
Exploration Mission 2 (EM-2) is a mission to resume the manned exploration of the Solar System. This mission is the first crewed mission of NASA’s Orion on the Space Launch System. The target for EM-2 is to perform a flyby of a captured asteroid in lunar orbit, which NASA plans to launch in 2023. As an intern working with EV-2 – Avionics Systems Division in Johnson Space Center, we are developing flight instrumentation systems for EM-2 (MISL & RFID). The Modular Integrated Stackable Layer (MISL) is a compact space-related computer system that is modular, scalable and reconfigurable. The RFID (radio frequency identification) sensors are used to take lower frequency (TC) type measurements and be able to stream data real-time to an RF (radio frequency) interrogator upon demand. Our job, in EV-2, is to certify, test, manufacture/assemble and deliver flight EM-2 DFI System (MISL & RFID). Our goal is to propose a development effort to design low-mass wire and wireless data acquisition and sensor solutions for EM-2 DFI (Development Flight Instrumentation). The team is tasked to provide the most effective use of 75 pounds to acquire DFI data and to collect sensor data for 100-200 high priority DFI channels (mass driven).
Chung, Jennie↗
Results from an Interval Management (IM) Flight Test and Its Potential Benefit to Air Traffic Management Operations
NASA's first Air Traffic Management Technology Demonstration (ATD-1) subproject successfully completed a 19-day flight test of an Interval Management (IM) avionics prototype. The prototype was built based on IM standards, integrated into two test aircraft, and then flown in real-world conditions to determine if the goals of improving aircraft efficiency and airport throughput during high-density arrival operations could be met. The ATD-1 concept of operation integrates advanced arrival scheduling, controller decision support tools, and the IM avionics to enable multiple time-based arrival streams into a high-density terminal airspace. IM contributes by calculating airspeeds that enable an aircraft to achieve a spacing interval behind the preceding aircraft. The IM avionics uses its data (route of flight, position, etc.) and Automatic Dependent Surveillance-Broadcast (ADS-B) state data from the Target aircraft to calculate this airspeed. The flight test demonstrated that the IM avionics prototype met the spacing accuracy design goal for three of the four IM operation types tested. The primary issue requiring attention for future IM work is the high rate of IM speed commands and speed reversals. In total, during this flight test, the IM avionics prototype showed significant promise in contributing to the goals of improving aircraft efficiency and airport throughput.
Baxley, Brian↗
Microbiological analysis of debris from Space Transportation System (STS)-55 Spacelab D-2
Filter debris from the Spacelab module D-2 of STS-55 was analyzed for microbial contamination. Debris from cabin and avionics filters was collected by Kennedy Space Center personnel on May 8, 1993, 2 days postflight. Debris weights were similar to those of previous Spacelab missions. Approximately 5.1E+5 colony forming units per gram of debris were enumerated from the cabin and avionics filter debris, respectively. these numbers were similar in previous missions for which the entire contents were analyzed without sorting of the material. Bacterial diversity was small compared to previous missions, with no gram negative bacteria isolated. Only one bacterial species, Corynebacterium pseudodiphtheriticum, was not isolated previously by the laboratory from Spacelab debris. This organism is a normal inhabitant of the pharynx. A table listing all species of bacteria isolated by the laboratory from previous Spacelab air filters debris collection is provided.
Huff, T. L.↗
Comparison of Communication Architectures for Spacecraft Modular Avionics Systems
This document is a survey of publicly available information concerning serial communication architectures used, or proposed to be used, in aeronautic and aerospace applications. It focuses on serial communication architectures that are suitable for low-latency or real-time communication between physically distributed nodes in a system. Candidates for the study have either extensive deployment in the field, or appear to be viable for near-term deployment. Eleven different serial communication architectures are considered, and a brief description of each is given with the salient features summarized in a table in appendix A. This survey is a product of the Propulsion High Impact Avionics Technology (PHIAT) Project at NASA Marshall Space Flight Center (MSFC). PHIAT was originally funded under the Next Generation Launch Technology (NGLT) Program to develop avionics technologies for control of next generation reusable rocket engines. After the announcement of the Space Exploration Initiative, the scope of the project was expanded to include vehicle systems control for human and robotics missions. As such, a section is included presenting the rationale used for selection of a time-triggered architecture for implementation of the avionics demonstration hardware developed by the project team
Gwaltney, D. A.↗
Transitioning Autonomous Systems Technology Research to a Flight Software Environment
NASA has developed methods and algorithms for autonomous spacecraft operations,including automated planning and scheduling, fault diagnostics and impact determination,procedure management and display. Making the transition from technology research tooperational flight software requires overcoming significant technical, programmatic andcultural challenges. Technology research is aimed at developing methods that performspecific functions correctly, but the resulting software may not be designed for flightprocessors with limited CPU, memory and network resources, and may not be easilyintegrated into spacecraft flight software. Our objective in the Autonomous Systems andOperations Project is to make significant strides toward the transformation from technologyto operational use. Our focus was twofold: maturing research grade autonomy software intoa flight software environment using broadly accepted languages and tools; and integratingautonomy applications with each other and with representative systems and their data andcommand interfaces. For a target flight software environment, we chose Core FlightSoftware, developed by Goddard Space Flight Center as a common operating systemindependent framework. Our hardware integration environment was provided by theIntegrated Power and Avionics Systems (iPAS) Lab at Johnson Space Center, in whichvarious subsystem development has been conducted to address engineering challenges forthe vehicles and systems required for long-duration missions into the solar system. The iPASand its network of connected facilities provides realistic subsystem hardware or simulationsof spacecraft power, life support, guidance, navigation and control, and command and datahandling subsystems. Interfaces between autonomy applications and the subsystems beingassessed and controlled were developed, assessed and refined. The hardware and softwareenvironment using CFS and the iPAS facility has proven to be a highly flexible and realisticenvironment in which to rapidly integrate applications in an iterative, low cost setting. Usingthe integration environment we have developed, we will turn our focus to performance andsizing analysis to determine the computational requirements for full-scale deployment ofautonomy technology. Scalability of reasoners and the spacecraft models upon which theyoperate, and robustness across the full range of spacecraft conditions and environments willbe explored and improved. We are making significant contributions to the future programsthat will build the spacecraft that will take humans beyond the Earth-Moon system, in whichprogram Systems Engineers will be able to accurately and confidently design in accurate,robust and mature autonomous operations systems.
Flight Software↗
System level verification applying the Space Shuttle experience to the Space Station
The applicability of the verification process for the Shuttle guidance, navigation and control (GNC) and data management system (DMS) for the development of the Space Station are described. Shuttle avionics hardware/software integration was delayed to finalize the hardware design before detailed definition and testing of the software. A block diagram is provided of the flight simulation laboratory used to test the GNC programs before flight data were available. The Station will have distributed computers, unlike the Orbiter, and will only be assembled fully in space. Standardized integration simulation test equipment are being defined to guide the development of hardware and software. The simulation capability may become part of nominal in-flight operations to initiate new capabilities as they are added to the Station. The Station GNC and DMS systems development will be somewhat simplified relative to those of the Shuttle because ascent and reentry will not be considered for the Station.
Gilbert, David W.↗
Advanced Microelectronics Technologies for Future Small Satellite Systems
Future small satellite systems for both Earth observation as well as deep-space exploration are greatly enabled by the technological advances in deep sub-micron microelectronics technologies. Whereas these technological advances are being fueled by the commercial (non-space) industries, more recently there has been an exciting new synergism evolving between the two otherwise disjointed markets. In other words, both the commercial and space industries are enabled by advances in low-power, highly integrated, miniaturized (low-volume), lightweight, and reliable real-time embedded systems. Recent announcements by commercial semiconductor manufacturers to introduce Silicon On Insulator (SOI) technology into their commercial product lines is driven by the need for high-performance low-power integrated devices. Moreover, SOI has been the technology of choice for many space semiconductor manufacturers where radiation requirements are critical. This technology has inherent radiation latch-up immunity built into the process, which makes it very attractive to space applications. In this paper, we describe the advanced microelectronics and avionics technologies under development by NASA's Deep Space Systems Technology Program (also known as X2000). These technologies are of significant benefit to both the commercial satellite as well as the deep-space and Earth orbiting science missions. Such a synergistic technology roadmap may truly enable quick turn-around, low-cost, and highly capable small satellite systems for both Earth observation as well as deep-space missions.
Alkalai, Leon↗