Search NASA⌕ Search

SEARCH · Search NASA

Results for “Spacecraft Crew 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.

195 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

SLS Flight Software Testing: Using a Modified Agile Software Testing Approach

NASA's Space Launch System (SLS) is an advanced launch vehicle for a new era of exploration beyond earth's orbit (BEO). The world's most powerful rocket, SLS, will launch crews of up to four astronauts in the agency's Orion spacecraft on missions to explore multiple deep-space destinations. Boeing is developing the SLS core stage, including the avionics that will control vehicle during flight. The core stage will be built at NASA's Michoud Assembly Facility (MAF) in New Orleans, LA using state-of-the-art manufacturing equipment. At the same time, the rocket's avionics computer software is being developed here at Marshall Space Flight Center in Huntsville, AL. At Marshall, the Flight and Ground Software division provides comprehensive engineering expertise for development of flight and ground software. Within that division, the Software Systems Engineering Branch's test and verification (T&V) team uses an agile test approach in testing and verification of software. The agile software test method opens the door for regular short sprint release cycles. The idea or basic premise behind the concept of agile software development and testing is that it is iterative and developed incrementally. Agile testing has an iterative development methodology where requirements and solutions evolve through collaboration between cross-functional teams. With testing and development done incrementally, this allows for increased features and enhanced value for releases. This value can be seen throughout the T&V team processes that are documented in various work instructions within the branch. The T&V team produces procedural test results at a higher rate, resolves issues found in software with designers at an earlier stage versus at a later release, and team members gain increased knowledge of the system architecture by interfacing with designers. SLS Flight Software teams want to continue uncovering better ways of developing software in an efficient and project beneficial manner. Through agile testing, there has been increased value through individuals and interactions over processes and tools, improved customer collaboration, and improved responsiveness to changes through controlled planning. The presentation will describe agile testing methodology as taken with the SLS FSW Test and Verification team at Marshall Space Flight Center.

Bolton, Albanie T.↗
NASA NTRS2018

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.↗
NASA NTRS2016

Intern Abstract for Spring 2016

The Human Interface Branch - EV3 - is evaluating Organic lighting-emitting diodes (OLEDs) as an upgrade for current displays on future spacecraft. OLEDs have many advantages over current displays. Conventional displays require constant backlighting which draws a lot of power, but with OLEDs they generate light themselves. OLEDs are lighter, and weight is always a concern with space launches. OLEDs also grant greater viewing angles. OLEDs have been in the commercial market for almost ten years now. What is not known is how they will perform in a space-like environment; specifically deep space far away from the Earth's magnetosphere. In this environment, the OLEDs can be expected to experience vacuum and galactic radiation. The intern's responsibility has been to prepare the OLED for a battery of tests. Unfortunately, it will not be ready for testing at the end of the internship. That being said much progress has been made: a) Developed procedures to safely disassemble the tablet. b) Inventoried and identified critical electronic components. c) 3D printed a testing apparatus. d) Wrote software in Python that will test the OLED screen while being radiated. e) Built circuits to restart the tablet and the test pattern, and ensure it doesn't fall asleep during radiation testing. f) Built enclosure that will house all of the electronics Also, the intern has been working on a way to take messages from a simulated Caution and Warnings system, process said messages into packets, send audio packets to a multicast address that audio boxes are listening to, and output spoken audio. Currently, Cautions and Warnings use a tone to alert crew members of a situation, and then crew members have to read through their checklists to determine what the tone means. In urgent situations, EV3 wants to deliver concise and specific alerts to the crew to facilitate any mitigation efforts on their part. Significant progress was made on this project: a) Open channel with the simulated Caution and Warning system to acquire messages. b) Configure audio boxes. c) Grab pre-recorded audio files. d) Packetize the audio stream. A third project that was assigned to implement LED indicator modules for an Omnibus project. The Omnibus project is investigating better ways designing lighting for the interior of spacecraft-both spacecraft lighting and avionics box status lighting indication. The current scheme contains too much of the blue light spectrum that disrupts the sleep cycle. The LED indicator modules are to simulate the indicators running on a spacecraft. Lighting data will be gathered by human factors personal and use in a model underdevelopment to model spacecraft lighting. Significant progress was made on this project: Designed circuit layout a) Tested LEDs at LETF. b) Created GUI for the indicators. c) Created code for the Arduino to run that will illuminate the indicator modules.

Gibson, William↗
NASA NTRS2015

Evaluation of the Oxygen Concentrator Prototypes: Pressure Swing Adsorption Prototype and Electrochemical Prototype

An oxygen concentrator is needed to provide enriched oxygen in support of medical contingency operations for future exploration human spaceflight programs. It would provide continuous oxygen to an ill or injured crew member in a closed cabin environment. Oxygen concentration technology is being pursued to concentrate oxygen from the ambient environment so oxygen as a consumable resource can be reduced. Because oxygen is a critical resource in manned spaceflight, using an oxygen concentrator to pull oxygen out of the ambient environment instead of using compressed oxygen can provide better optimization of resources. The overall goal of this project is to develop an oxygen concentrator module that minimizes the hardware mass, volume, and power footprint while still performing at the required clinical capabilities. Should a medical event occur that requires patient oxygenation, the release of 100 percent oxygen into a small closed cabin environment can rapidly raise oxygen levels to the vehicles fire limit. The use of an oxygen concentrator to enrich oxygen from the ambient air and concentrate it to the point where it can be used for medical purposes means no oxygen is needed from the ultra-high purity (99.5+% O2) oxygen reserve tanks. By not adding oxygen from compressed tanks to the cabin environment, oxygen levels can be kept below the vehicle fire limit thereby extending the duration of care provided to an oxygenated patient without environmental control system intervention to keep the cabin oxygen levels below the fire limits. The oxygen concentrator will be a Food and Drug Administration (FDA) clearable device. A demonstration unit for the International Space Station (ISS) is planned to verify the technology and provide oxygen capability. For the ISS, the demonstration unit should not exceed 10 kg (approximately 22 lb), which is the soft stowage mass limit for launch on resupply vehicles for the ISS. The unit's size should allow for transport within the spacecraft to an ill crewmember. The user interface needs to be designed for ease of use by the local care provider and with consideration to the limited amount of training available to the astronaut corps for medical equipment and procedures.

Gilkey, Kelly M.↗
NASA NTRS2013

NASA Tech Briefs, April 2013

Topics covered include: Fully Integrated, Miniature, High-Frequency Flow Probe Utilizing MEMS Leadless SOI Technology; Nanoscale Surface Plasmonics Sensor With Nanofluidic Control; Advanced Dispersed Fringe Sensing Algorithm for Coarse Phasing Segmented Mirror Telescopes; Neural Network Back-Propagation Algorithm for Sensing Hypergols; Bulk Moisture and Salinity Sensor; Change-Based Satellite Monitoring Using Broad Coverage and Targetable Sensing; Circularly Polarized Microwave Antenna Element with Very Low Off-Axis Cross-Polarization; Ultra-Low Heat-Leak, High-Temperature Superconducting Current Leads for Space Applications; Flash Cracking Reactor for Waste Plastic Processing; An Automated Safe-to-Mate (ASTM) Tester; Wireless Chalcogenide Nanoionic-Based Radio-Frequency Switch; Compute Element and Interface Box for the Hazard Detection System; DOT Transmit Module; Composite Aerogel Multifoil Protective Shielding; Li-Ion Electrolytes with Improved Safety and Tolerance to High-Voltage Systems; Polymer-Reinforced, Non-Brittle, Lightweight Cryogenic Insulation; Controlled, Site-Specific Functionalization of Carbon Nanotubes with Diazonium Salts; Regenerable Sorbent for CO2 Removal; Sprayable Aerogel Bead Compositions With High Shear Flow Resistance and High Thermal Insulation Value; Lexan Linear Shaped Charge Holder with Magnets and Backing Plate; Robotic Ankle for Omnidirectional Rock Anchors; Wind, Wave, and Tidal Energy Without Power Conditioning; An Active Heater Control Concept to Meet IXO Type Mirror Module Thermal-Structural Distortion Requirement; Waterless Clothes-Cleaning Machine; Integrated Electrical Wire Insulation Repair System; LVGEMS Time-of-Flight Mass Spectrometry on Satellites; Surface Inspection Tool for Optical Detection of Surface Defects; Per-Pixel, Dual-Counter Scheme for Optical Communications; Certification-Based Process Analysis; Surface Navigation Using Optimized Waypoints and Particle Swarm Optimization; Smart-Divert Powered Descent Guidance to Avoid the Backshell Landing Dispersion Ellipse; Estimating Foreign-Object-Debris Density from Photogrammetry Data; Adaptive Sampling of Spatiotemporal Phenomena with Optimization Criteria; Building a 2.5D Digital Elevation Model From 2D Imagery; Eyes on the Earth 3D; Target Trailing With Safe Navigation for Maritime Autonomous Surface Vehicles; Adams-Based Rover Terramechanics and Mobility Simulator - ARTEMIS; ISTP CDF Skeleton Editor; Uplink Summary Generator (ULSGEN) Version 1.0; Robotics On-Board Trainer (ROBoT); Software Engineering Tools for Scientific Models; Automatic Data Filter Customization Using a Genetic Algorithm; Tracker Toolkit; Towards Efficient Scientific Data Management Using Cloud Storage; On a Formal Tool for Reasoning About Flight Software Cost Analysis; A Nanostructured Composites Thermal Switch Controls Internal and External Short Circuit in Lithium Ion Batteries; Spacecraft Crew Cabin Condensation Control; and Functional Near-Infrared Spectroscopy Signals Measure Neuronal Activity in the Cortex.

Source record↗
NASA NTRS2011

Development of the Sasquatch Drop Test Footprint Tool

The Crew Exploration Vehicle Parachute Assembly System (CPAS) is the parachute system for NASA s Orion spacecraft. CPAS is currently in the design and testing phase of development. The test program consists of numerous drop tests, wherein a test article rigged with parachutes is extracted or released from an aircraft. During such tests, range safety is paramount, as is the recoverability of the parachutes and test article. It is crucial to establish an aircraft release point that will ensure that the article and all items released from it will land in safe locations. Early in the CPAS project, a legacy tool (previously used on the X-38 project) was used to determine a safe release point and to predict the landing locations (the footprint) of the payload and all released objects. Due to increasing test complexity and the need for a more flexible tool, a new footprint predictor tool, called Sasquatch, was created in MATLAB. This tool takes in a simulated trajectory for the test article, information about all released objects, and atmospheric wind data (simulated or actual) to calculate the trajectories of the released objects. Dispersions are applied to the landing locations of those objects, taking into account the variability of winds, aircraft release point, and object descent rate. A safe aircraft release point is determined based on the landing locations of the payload and released objects. The release point, landing locations, and dispersions are plotted on a simple map of the drop zone for easy reference. To date, Sasquatch has been used for thirteen drop tests. Comparing the predictions with actual test results has allowed for significant improvements in the tool s predictive capabilities, especially the incorporation of a well-correlated horizontal throw model. Intended future improvements to the tool include tighter dispersions on the landing locations, Monte Carlo capability, direct input from trajectory simulations, and a graphical user interface.

Bledsoe, Kristin J.↗
NASA NTRS2010

Ares I-X Ground Diagnostic Prototype

Automating prelaunch diagnostics for launch vehicles offers three potential benefits. First, it potentially improves safety by detecting faults that might otherwise have been missed so that they can be corrected before launch. Second, it potentially reduces launch delays by more quickly diagnosing the cause of anomalies that occur during prelaunch processing. Reducing launch delays will be critical to the success of NASA's planned future missions that require in-orbit rendezvous. Third, it potentially reduces costs by reducing both launch delays and the number of people needed to monitor the prelaunch process. NASA is currently developing the Ares I launch vehicle to bring the Orion capsule and its crew of four astronauts to low-earth orbit on their way to the moon. Ares I-X will be the first unmanned test flight of Ares I. It is scheduled to launch on October 27, 2009. The Ares I-X Ground Diagnostic Prototype is a prototype ground diagnostic system that will provide anomaly detection, fault detection, fault isolation, and diagnostics for the Ares I-X first-stage thrust vector control (TVC) and for the associated ground hydraulics while it is in the Vehicle Assembly Building (VAB) at John F. Kennedy Space Center (KSC) and on the launch pad. It will serve as a prototype for a future operational ground diagnostic system for Ares I. The prototype combines three existing diagnostic tools. The first tool, TEAMS (Testability Engineering and Maintenance System), is a model-based tool that is commercially produced by Qualtech Systems, Inc. It uses a qualitative model of failure propagation to perform fault isolation and diagnostics. We adapted an existing TEAMS model of the TVC to use for diagnostics and developed a TEAMS model of the ground hydraulics. The second tool, Spacecraft Health Inference Engine (SHINE), is a rule-based expert system developed at the NASA Jet Propulsion Laboratory. We developed SHINE rules for fault detection and mode identification. The prototype uses the outputs of SHINE as inputs to TEAMS. The third tool, the Inductive Monitoring System (IMS), is an anomaly detection tool developed at NASA Ames Research Center and is currently used to monitor the International Space Station Control Moment Gyroscopes. IMS automatically "learns" a model of historical nominal data in the form of a set of clusters and signals an alarm when new data fails to match this model. IMS offers the potential to detect faults that have not been modeled. The three tools have been integrated and deployed to Hangar AE at KSC where they interface with live data from the Ares I-X vehicle and from the ground hydraulics. The outputs of the tools are displayed on a console in Hangar AE, one of the locations from which the Ares I-X launch will be monitored. The full paper will describe how the prototype performed before the launch. It will include an analysis of the prototype's accuracy, including false-positive rates, false-negative rates, and receiver operating characteristics (ROC) curves. It will also include a description of the prototype's computational requirements, including CPU usage, main memory usage, and disk usage. If the prototype detects any faults during the prelaunch period then the paper will include a description of those faults. Similarly, if the prototype has any false alarms then the paper will describe them and will attempt to explain their causes.

Schwabacher, Mark↗
NASA NTRS2015

SPHERES: From Ground Development to Operations on ISS

SPHERES (Synchronized Position Hold Engage and Reorient Experimental Satellites) is an internal International Space Station (ISS) Facility that supports multiple investigations for the development of multi-spacecraft and robotic control algorithms. The SPHERES Facility on ISS is managed and operated by the SPHERES National Lab Facility at NASA Ames Research Center (ARC) at Moffett Field California. The SPHERES Facility on ISS consists of three self-contained eight-inch diameter free-floating satellites which perform the various flight algorithms and serve as a platform to support the integration of experimental hardware. To help make science a reality on the ISS, the SPHERES ARC team supports a Guest Scientist Program (GSP). This program allows anyone with new science the possibility to interface with the SPHERES team and hardware. In addition to highlighting the available SPHERES hardware on ISS and on the ground, this presentation will also highlight ground support, facilities, and resources available to guest researchers. Investigations on the ISS evolve through four main phases: Strategic, Tactical, Operations, and Post Operations. The Strategic Phase encompasses early planning beginning with initial contact by the Principle Investigator (PI) and the SPHERES program who may work with the PI to assess what assistance the PI may need. Once the basic parameters are understood, the investigation moves to the Tactical Phase which involves more detailed planning, development, and testing. Depending on the nature of the investigation, the tactical phase may be split into the Lab Tactical Phase or the ISS Tactical Phase due to the difference in requirements for the two destinations. The Operations Phase is when the actual science is performed; this can be either in the lab, or on the ISS. The Post Operations Phase encompasses data analysis and distribution, and generation of summary status and reports. The SPHERES Operations and Engineering teams at ARC is composed of experts who can guide the Payload Developer (PD) and Principle Investigator (PI) in reaching critical milestones to make their science a reality using the SPHERES platform. From performing integrated safety and verification assessments, to assisting in developing crew procedures and operations products, to organizing, planning, and executing all test sessions, to helping manage data products, the SPHERES team at ARC is available to support microgravity research with the SPEHRES Guest Scientist Program.

ISS Research↗
NASA NTRS2018

Flight Plasma Diagnostics for High-Power, Solar-Electric Deep-Space Spacecraft

NASA’s Asteroid Redirect Robotic Mission (ARRM) mission concept plans included a set of plasma and space environment instruments, the Plasma Diagnostic Package (PDP), to fulfill ARRM requirements for technology extensibility to future missions. The PDP objectives were divided into the classes of 1) Plasma thruster dynamics, 2) Solar array-specific environmental effects, 3) Plasma environmental spacecraft effects, and 4) Energetic particle spacecraft environment. A reference design approach and interface requirements for ARRM’s PDP was generated by the PDP team at JPL and GRC. The reference design consisted of redundant single-string avionics located on the ARRM spacecraft bus as well as solar array, driving and processing signals from multiple copies of several types of plasma, effects, and environments sensors distributed over the spacecraft and array. The reference design sensor types were derived in part from sensors previously developed for USAF Research Laboratory (AFRL) plasma effects campaigns such as those aboard TacSat-2 in 2007 and AEHF-2 in 2012. ARRM project leadership also encouraged the PDP team to convene a team of topical subject matter experts from across the country to review and confirm the reference design and to consider effective alternatives and/or enhancements to the reference design. This activity was proposed and accepted as an interactive, informal JPL “A-team” study and a cadre of 25 participants gathered in early 2017 for discussions. The outcome of the two-day A-team study was that the PDP reference design would allow the most important induced-environment unknowns to be measured in the appropriate space environment. Another outcome addressed technology developments of new or improved space plasma environmental sensors. The A-team study concluded that selected developments would lead to improved measurements that could efficiently provide important and otherwise unavailable information about plasma thruster operation in the space environment as well as the plasma induced spacecraft environment. Specifically, the A-team group recommended greater sensor diversity, by inclusion of deployed sensor capabilities in the thruster plume, or by occasional gimbaling of the thruster(s) toward the sensor arrays. The A-team also recommended developing high-speed probes, optical plasma probes, energy selective probes, and direct erosion/deposition sensors, among others; and recommended the inclusion of cameras as well as, since ARRM was to be recovered in cis-lunar orbit by a crewed mission, astronaut assessments of thruster induced environments and collection of sample coupons. Overall, the PDP A-team study provided a clear, consensus supported validation of the reference design PDP approach and pointed out important directions for future flight plasma sensor development.

Choi, Maria↗
NASA NTRS2009

A Review of the MLAS Parachute Systems

The NASA Engineering and Safety Center (NESC) is developing the Max Launch Abort System (MLAS) as a risk-mitigation design should problems arise with the baseline Orion spacecraft launch abort design. The Max in MLAS is dedicated to Max Faget, the renowned NASA spacecraft designer. The MLAS flight test vehicle consists of boost skirt, coast skirt and the MLAS fairing which houses a full scale boilerplate Orion Crew Module (CM). The objective of the flight test is to prove that the CM can be released from the MLAS fairing during pad abort conditions without detrimental recontact between the CM and fairing, achieving performance similar to the Orion launch abort system. The boost and coast skirts provide the necessary thrust and stability to achieve the flight test conditions and are released prior to the test -- much like the Little Joe booster was used in the Apollo Launch Escape System tests. To achieve the test objective, two parachutes are deployed from the fairing to reorient the CM/fairing to a heatshield first orientation. The parachutes then provide the force necessary to reduce the total angle of attack and body angular rates required for safe release of the CM from the fairing. A secondary test objective after CM release from the fairing is to investigate the removal of the CM forward bay cover (FBC) with CM drogue parachutes for the purpose of attempting to synchronously deploying a set of CM main parachutes. Although multiple parachute deployments are used in the MLAS flight test vehicle to complete its objective, there are only two parachute types employed in the flight test. Five of the nine parachutes used for MLAS are 27.6 ft D(sub 0) ribbon parachutes, and the remaining four are standard G-12 cargo parachutes. This paper presents an overview of the 27.6 ft D(sub 0) ribbon parachute system employed on the MLAS flight test vehicle for coast skirt separation, fairing reorientation, and as drogue parachutes for the CM after separation from the fairing. Discussion will include: the process used to select this design, previously proven as a spin/stall recovery parachute; descriptions of all components of the parachute system; the minor modifications necessary to adapt the parachute to the MLAS program; the techniques used to analyze the parachute for the multiple roles it performs; a discussion of the rigging techniques used to interface the parachute system to the vehicle; and a brief description of how the evolution of the program affected parachute usage and analysis. An overview of the Objective system, rationale for the MLAS approach and the future of the program will also be presented. We hope to have flight test results to report at the time of the Conference Presentation.

Taylor, Anthony P.↗
NASA NTRS2008

NASA's Ares I and Ares V Launch Vehicles -- Effective Space Operations Through Efficient Ground Operations

The United States (U.S.) plans to return to the Moon by 2020, with the development of a new human-rated space transportation system to replace the Space Shuttle, which is due for retirement in 2010 after it completes its missions of building the International Space Station and servicing the Hubble Space Telescope. Powering the future of space-based scientific exploration will be the Ares I Crew Launch Vehicle, which will transport the Orion Crew Exploration Vehicle to orbit where it will rendezvous with the Lunar Lander. which will be delivered by the Ares V Cargo Launch Vehicle. This new transportation infrastructure, developed by the National Aeronautics and Space Administration (NASA), will allow astronauts to leave low-Earth orbit for extended lunar exploration and preparation for the first footprint on Mars. All space-based operations begin and are controlled from Earth. NASA's philosophy is to deliver safe, reliable, and cost-effective solutions to sustain a multi-billion-dollar program across several decades. Leveraging 50 years of lessons learned, NASA is partnering with private industry, while building on proven hardware experience. This paper will discuss how the Engineering Directorate at NASA's Marshall Space Flight Center is working with the Ares Projects Office to streamline ground operations concepts and reduce costs. Currently, NASA's budget is around $17 billion, which is less than 1 percent of the U.S. Federal budget. Of this amount, NASA invests approximately $4.5 billion each year in Space Shuttle operations, regardless of whether the spacecraft is flying or not. The affordability requirement is for the Ares I to reduce this expense by 50 percent, in order to allow NASA to invest more in space-based scientific operations. Focusing on this metric, the Engineering Directorate provides several solutions-oriented approaches, including Lean/Six Sigma practices and streamlined hardware testing and integration, such as assembling major hardware elements before shipping to the Kennedy Space Center for launch operations. This paper provides top-level details for several cost saving initiatives, including both process and product improvements that will result in space transportation systems that are designed with operations efficiencies in mind. The Engineering Directorate provides both the intellectual capital embodied in an experienced workforce and unique facilities in which to validate the information technology tools that allow a nationwide team to collaboratively connect across miles that separate them and the engineering disciplines that integrate various piece parts into a whole system. As NASA transforms ground-based operations, it also is transitioning its workforce from an era of intense hands-on labor to a new one of mechanized conveniences and robust hardware with simpler interfaces. Ensuring that space exploration is on sound footing requires that operations efficiencies be designed into the transportation system and implemented in the development stage. Applying experience gained through decades of ground and space op'erations, while using value-added processes and modern business and engineering tools, is the philosophy upon which a new era of exploration will be built to solve some of the most pressing exploration challenges today -- namely, safety, reliability, and affordability.

Dumbacher, Daniel L.↗
NASA NTRS2002

Automated fault-management in a simulated spaceflight micro-world

BACKGROUND: As human spaceflight missions extend in duration and distance from Earth, a self-sufficient crew will bear far greater onboard responsibility and authority for mission success. This will increase the need for automated fault management (FM). Human factors issues in the use of such systems include maintenance of cognitive skill, situational awareness (SA), trust in automation, and workload. This study examine the human performance consequences of operator use of intelligent FM support in interaction with an autonomous, space-related, atmospheric control system. METHODS: An expert system representing a model-base reasoning agent supported operators at a low level of automation (LOA) by a computerized fault finding guide, at a medium LOA by an automated diagnosis and recovery advisory, and at a high LOA by automate diagnosis and recovery implementation, subject to operator approval or veto. Ten percent of the experimental trials involved complete failure of FM support. RESULTS: Benefits of automation were reflected in more accurate diagnoses, shorter fault identification time, and reduced subjective operator workload. Unexpectedly, fault identification times deteriorated more at the medium than at the high LOA during automation failure. Analyses of information sampling behavior showed that offloading operators from recovery implementation during reliable automation enabled operators at high LOA to engage in fault assessment activities CONCLUSIONS: The potential threat to SA imposed by high-level automation, in which decision advisories are automatically generated, need not inevitably be counteracted by choosing a lower LOA. Instead, freeing operator cognitive resources by automatic implementation of recover plans at a higher LOA can promote better fault comprehension, so long as the automation interface is designed to support efficient information sampling.

NASA Discipline Space Human Factors↗
NASA NTRS2011

Performance Comparison of Wireless Sensor Network Standard Protocols in an Aerospace Environment: ISA100.11a and ZigBee

Wireless Sensor Networks (WSNs) can provide a substantial benefit in spacecraft systems, reducing launch weight and providing unprecedented flexibility by allowing instrumentation capabilities to grow and change over time. Achieving data transport reliability on par with that of wired systems, however, can prove extremely challenging in practice. Fortunately, much progress has been made in developing standard WSN radio protocols for applications from non-critical home automation to mission-critical industrial process control. The relative performances of candidate protocols must be compared in representative aerospace environments, however, to determine their suitability for spaceflight applications. In this paper, we will present the results of a rigorous laboratory analysis of the performance of two standards-based, low power, low data rate WSN protocols: ZigBee Pro and ISA100.11a. Both are based on IEEE 802.15.4 and augment that standard's specifications to build complete, multi-hop networking stacks. ZigBee Pro targets primarily the home and office automation markets, providing an ad-hoc protocol that is computationally lightweight and easy to implement in inexpensive system-on-a-chip components. As a result of this simplicity, however, ZigBee Pro can be susceptible to radio frequency (RF) interference. ISA100.11a, on the other hand, targets the industrial process control market, providing a robust, centrally-managed protocol capable of tolerating a significant amount of RF interference. To achieve these gains, a coordinated channel hopping mechanism is employed, which entails a greater computational complexity than ZigBee and requires more sophisticated and costly hardware. To guide future aerospace deployments, we must understand how well these standards relatively perform in analog environments under expected operating conditions. Specifically, we are interested in evaluating goodput -- application level throughput -- in a representative crewed environment in the presence of varying levels of 802.11g Wi-Fi traffic. To do so, we use the NASA Johnson Space Center Wireless Habitat Testbed (WHT), a metallic, habitation-sized module designed for co-existence testing of wireless systems. In its quiescent state, the sealed WHT provides an RF-quiet environment to which we can selectively add interfering systems; it also provides a realistic level of multi-path self-interference for systems under investigation. In our test, we deploy two representative five node networks, configured in a star topology with all nodes reporting directly to a WSN gateway. Each ZigBee network WSN node is built using a Texas Instruments (TI) CC2530 system-on-a-chip radio running TI's ZigBee Pro Z-stack. Each ISA100.11a network node is built using a Nivis VersaNode 210 system-on-a-chip radio. In both cases, radios interface with TI MSP430-F5438 microcontroller implementing a common test application. Interference is provided by a D-link 802.11g Wi-Fi router transporting traffic generated using the Iperf network testing tool. For the single-channel ZigBee network, effects of both direct and indirect Wi-Fi interference are evaluated. For the channel-hopping ISA100.11a network, effects of interference from multiple Wi-Fi routers configured in non-overlapping 802.11g channels are evaluated. Our results show that, in general, the more lightweight ZigBee network performs well at low interference levels, but performance degrades as interference increases. Conversely, the more complex and costly ISA100.11a network continues to perform well as Wi-Fi interference levels increase.

Wagner, Raymond S.↗
NASA NTRS2018

Orion Optical Navigation Progress Toward Exploration: Mission 1

Optical navigation of human spacecraft was proposed on Gemini and implemented successfully on Apollo as a means of autonomously operating the vehicle in the event of lost communication with controllers on Earth. It shares a history with the "method of lunar distances" that was used in the 18th century and gained some notoriety after its use by Captain James Cook during his 1768 Pacific voyage of the HMS Endeavor. The Orion emergency return system utilizing optical navigation has matured in design over the last several years, and is currently undergoing the final implementation and test phase in preparation for Exploration Mission 1 (EM-1) in 2019. The software development is being worked as a Government Furnished Equipment (GFE) project delivered as an application within the Core Flight Software of the Orion camera controller module. The mathematical formulation behind the initial ellipse fit in the image processing is detailed in Christian. The non-linear least squares refinement then follows the technique of Mortari as an estimation process of the planetary limb using the sigmoid function. The Orion optical navigation system uses a body fixed camera, a decision that was driven by mass and mechanism constraints. The general concept of operations involves a 2-hour pass once every 24 hours, with passes specifically placed before all maneuvers to supply accurate navigation information to guidance and targeting. The pass lengths are limited by thermal constraints on the vehicle since the OpNav attitude generally deviates from the thermally stable tail-to-sun attitude maintained during the rest of the orbit coast phase. Calibration is scheduled prior to every pass due to the unknown nature of thermal effects on the lens distortion and the mounting platform deformations between the camera and star trackers. The calibration technique is described in detail by Christian, et al. and simultaneously estimates the Brown-Conrady coefficients and the Star Tracker/Camera interlock angles. Accurate attitude information is provided by the star trackers during each pass. Figure 1 shows the various phases of lunar return navigation when the vehicle is in autonomous operation with lost ground communication. The midcourse maneuvers are placed to control the entry interface conditions to the desired corridor for safe landing. The general form of optical navigation on Orion is where still images of the Moon or Earth are processed to find the apparent angular diameter and centroid in the camera focal plane. This raw data is transformed into range and bearing angle measurements using planetary data and precise star tracker inertial attitude. The measurements are then sent to the main flight computer's Kalman filter to update the onboard state vector. The images are, of course, collected over an arc to converge the state and estimate velocity. The same basic technique was used by Apollo to satisfy loss-of-comm, but Apollo used manual crew sightings with a vehicle-integral sextant instead of autonomously processing optical imagery. The software development is past its Critical Design Review, and is progressing through test and certification for human rating. In support of this, a hardware-in-the-loop test rig was developed in the Johnson Space Center Electro-Optics Lab to exercise the OpNav system prior to integrated testing on the Orion vehicle. Figure 2 shows the rig, which the test team has dubbed OCILOT (Orion Camera In the Loop Optical Testbed). Analysis performed to date shows a delivery that satisfies an allowable entry corridor as shown in Figure 3.

Holt, Greg N.↗
NASA NTRS2005

Diagnostic instrumentation aboard ISS: just-in-time training for non-physician crewmembers

INTRODUCTION: The performance of complex tasks on the International Space Station (ISS) requires significant preflight crew training commitments and frequent skill and knowledge refreshment. This report documents a recently developed "just-in-time" training methodology, which integrates preflight hardware familiarization and procedure training with an on-orbit CD-ROM-based skill enhancement. This "just-in-time" concept was used to support real-time remote expert guidance to complete ultrasound examinations using the ISS Human Research Facility (HRF). METHODS: An American and Russian ISS crewmember received 2 h of "hands on" ultrasound training 8 mo prior to the on-orbit ultrasound exam. A CD-ROM-based Onboard Proficiency Enhancement (OPE) interactive multimedia program consisting of memory enhancing tutorials, and skill testing exercises, was completed by the crewmember 6 d prior to the on-orbit ultrasound exam. The crewmember was then remotely guided through a thoracic, vascular, and echocardiographic examination by ultrasound imaging experts. RESULTS: Results of the CD-ROM-based OPE session were used to modify the instructions during a complete 35-min real-time thoracic, cardiac, and carotid/jugular ultrasound study. Following commands from the ground-based expert, the crewmember acquired all target views and images without difficulty. The anatomical content and fidelity of ultrasound video were adequate for clinical decision making. CONCLUSIONS: Complex ultrasound experiments with expert guidance were performed with high accuracy following limited preflight training and multimedia based in-flight review, despite a 2-s communication latency. In-flight application of multimedia proficiency enhancement software, coupled with real-time remote expert guidance, facilitates the successful performance of ultrasound examinations on orbit and may have additional terrestrial and space applications.

Inservice Training/methods↗