Search NASA⌕ Search

SEARCH · Search NASA

Results for “engineering knowledge integration”

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.

445 records · Page 25

Solar Dynamics Observatory Guidance, Navigation, and Control System Overview

The Solar Dynamics Observatory (SDO) was designed and built at the Goddard Space Flight Center, launched from Cape Canaveral on February 11, 2010, and reached its final geosynchronous science orbit on March 16, 2010. The purpose of SDO is to observe the Sun and continuously relay data to a dedicated ground station. SDO remains Sun-pointing throughout most of its mission for the instruments to take measurements of the Sun. The SDO attitude control system (ACS) is a single-fault tolerant design. Its fully redundant attitude sensor complement includes sixteen coarse Sun sensors (CSSs), a digital Sun sensor (DSS), three two-axis inertial reference units (IRUs), and two star trackers (STs). The ACS also makes use of the four guide telescopes included as a part of one of the science instruments. Attitude actuation is performed using four reaction wheels assemblies (RWAs) and eight thrusters, with a single main engine used to provide velocity-change thrust for orbit raising. The attitude control software has five nominal control modes, three wheel-based modes and two thruster-based modes. A wheel-based Safehold running in the attitude control electronics box improves the robustness of the system as a whole. All six modes are designed on the same basic proportional-integral-derivative attitude error structure, with more robust modes setting their integral gains to zero. This paper details the final overall design of the SDO guidance, navigation, and control (GN&C) system and how it was used in practice during SDO launch, commissioning, and nominal operations. This overview will include the ACS control modes, attitude determination and sensor calibration, the high gain antenna (HGA) calibration, and jitter mitigation operation. The Solar Dynamics Observatory mission is part of the NASA Living With a Star program, which seeks to understand the changing Sun and its effects on the Solar System, life, and society. To this end, the SDO spacecraft carries three Sun-observing instruments: Helioseismic and Magnetic Imager (HMI), led by Stanford University; Atmospheric Imaging Assembly (AIA), led by Lockheed Martin Space and Astrophysics Laboratory; and Extreme Ultraviolet Variability Experiment (EVE), led by the University of Colorado. The basic mission is to observe the Sun for a very high percentage of the 5-year mission (10-year goal) with long stretches of uninterrupted observations and with constant, high-data-rate transmission to a dedicated ground station to be located in White Sands, New Mexico. These goals guided the design of the spacecraft bus that will carry and service the three-instrument payload. Overarching design goals for the bus are geosynchronous orbit, near-constant Sun observations with the ability to fly through eclipses, and constant HGA contact with the dedicated ground station. A three-axis stabilized ACS is needed both to point at the Sun accurately and to keep the roll about the Sun vector correctly positioned with respect to the solar north pole. This roll control is especially important for the magnetic field imaging of HM I. The mission requirements have several general impacts on the ACS design. Both the AIA and HMI instruments are very sensitive to the blurring caused by jitter. Each has an image stabilization system (ISS) with some ability to filter out high frequency motion, but below the bandwidth of the ISS the control system must compensate for disturbances within the ACS bandwidth or avoid exciting jitter at higher frequencies. Within the ACS bandwidth, the control requirement imposed by AIA is to place the center of the solar disk no more than 2 arc sec, 3 , from a body-defined target based on one of the GTs that accompany the instrument. This body-defined target, called the science reference boresight (SRB), was determined from the postlaunch orientation of the GTs by averaging the bounding telescope boresights for pitch to get a pitch SRB coordinate, and by averaging the bounding boresights for yaw toet the yaw SRB coordinate. The location of this SRB in the 0.5-deg field-of-view for each GT then becomes the central target for each telescope; one GT is selected for use as the ACS controlling guide telescope (CGT) at any given time. Fine Sun-pointing is effected based on this SRB for all three instruments when the Sun is within the linear range of the CGT. In addition to limiting jitter, HMI science requires averaging several observations, making the instrument sensitive to low frequency motion that induces differential motion between each observation. This requires the spacecraft attitude to be stable about the roll axis to approximately 10 arcsec over a ten-minute period. Instrument calibrations require that the spacecraft point the SRB up to 2.5 degrees in pitch and yaw away from the center of the Sun, placing the Sun outside the field-of-view of the guide telescopes. In such instances, when the GTs cannot provide the definitive target for the ACS, on-board attitude determination combined with ephemeris prediction of the Sun direction must provide the definitive target. EVE is capable of observing the Sun with less dependence on attitude control. However, the ground data processing needs for calibrations result in the most strict attitude knowledge requirements for the mission: [35,70,70] arcsec, 3 , of knowledge with respect to the center of the solar disk. In addition to driving the ACS sensor selection, the knowledge requirements, which have their effect primarily during Inertial mode calibrations, drive the accuracy requirements for the solar ephemeris. The need to achieve and maintain geosynchronous orbit (GEO) drove the need for high-efficiency propulsive systems and appropriate attitude control. The main engine provided high specific impulse for the maneuvers to attain GEO, while the smaller ACS thrusters managed the disturbance torques of the larger engine and provided the capability for much smaller adjustment burns on orbit. SDO s large solar profile means that solar radiation pressure is a large torque disturbance, and the momentum buildup from this disturbance and the GEO altitude drives the ACS to use thrusters to manage vehicle momentum. The demanding data capture budget for the mission, however, requires SDO to avoid frequent thruster maneuvers, while concerns about on-orbit jitter restrict the maximum desired wheel speeds desired from the RWAs. The plan for on-orbit wheel speed and momentum management will be discussed as well as what is now being done in operation after the jitter environment was characterized. The SDO ACS hardware complement is single-fault tolerant. Two main processors carry virtually identical copies of the command and data handling and ACS software, and two identical attitude control electronics (ACE) boxes carry Coldfire processors with contingency ACS software and other hardware interface cards; the ACE structure allows reaction wheels to be commanded by the Sun-pointing Safehold independent of the Mil Std 1553 data bus. The sixteen Adcole CSSs are grouped into primary and backup sets of eight sensors, each set providing the ability to calculate a sun vector. Each set of eight eyes provides full 4 -steradian coverage. The Adcole DSS comprises an optics head and a separate electronics box providing a 1553 data interface. The electronics box is mounted inside the Faraday cage created by the spacecraft bus module. The DSS head with its 32- deg square FOV is mounted on the instrument module with its boresight along the spacecraft X axis, nearly aligned with the Sun during observations. Adcole has designed the DSS calibration parameters so that the accuracy is 0.24 arcminutes within 10 deg of the boresight, and diminishes to 3 arcminutes as the Sun moves towards the edges of its FOV . This DSS calibration scheme provides higher accuracy attitude determination over the range of the instrument calibration maneuvers.

Morgenstern, Wendy M.↗

Automatic Testcase Generation for Flight Software

The TacSat3 project is applying Integrated Systems Health Management (ISHM) technologies to an Air Force spacecraft for operational evaluation in space. The experiment will demonstrate the effectiveness and cost of ISHM and vehicle systems management (VSM) technologies through onboard operation for extended periods. We present two approaches to automatic testcase generation for ISHM: 1) A blackbox approach that views the system as a blackbox, and uses a grammar-based specification of the system's inputs to automatically generate *all* inputs that satisfy the specifications (up to prespecified limits); these inputs are then used to exercise the system. 2) A whitebox approach that performs analysis and testcase generation directly on a representation of the internal behaviour of the system under test. The enabling technologies for both these approaches are model checking and symbolic execution, as implemented in the Ames' Java PathFinder (JPF) tool suite. Model checking is an automated technique for software verification. Unlike simulation and testing which check only some of the system executions and therefore may miss errors, model checking exhaustively explores all possible executions. Symbolic execution evaluates programs with symbolic rather than concrete values and represents variable values as symbolic expressions. We are applying the blackbox approach to generating input scripts for the Spacecraft Command Language (SCL) from Interface and Control Systems. SCL is an embedded interpreter for controlling spacecraft systems. TacSat3 will be using SCL as the controller for its ISHM systems. We translated the SCL grammar into a program that outputs scripts conforming to the grammars. Running JPF on this program generates all legal input scripts up to a prespecified size. Script generation can also be targeted to specific parts of the grammar of interest to the developers. These scripts are then fed to the SCL Executive. ICS's in-house coverage tools will be run to measure code coverage. Because the scripts exercise all parts of the grammar, we expect them to provide high code coverage. This blackbox approach is suitable for systems for which we do not have access to the source code. We are applying whitebox test generation to the Spacecraft Health INference Engine (SHINE) that is part of the ISHM system. In TacSat3, SHINE will execute an on-board knowledge base for fault detection and diagnosis. SHINE converts its knowledge base into optimized C code which runs onboard TacSat3. SHINE can translate its rules into an intermediate representation (Java) suitable for analysis with JPF. JPF will analyze SHINE's Java output using symbolic execution, producing testcases that can provide either complete or directed coverage of the code. Automatically generated test suites can provide full code coverage and be quickly regenerated when code changes. Because our tools analyze executable code, they fully cover the delivered code, not just models of the code. This approach also provides a way to generate tests that exercise specific sections of code under specific preconditions. This capability gives us more focused testing of specific sections of code.

Bushnell, David Henry↗

CLINICAL DECISION SUPPORT: PATH TO FUNCTIONAL REQUIREMENTS

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

clinical decision support↗

Clinical Decision Support: Path to Functional Requirements

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

Clinical decision support↗

Hardware Development Process for Human Research Facility Applications

The simple goal of the Human Research Facility (HRF) is to conduct human research experiments on the International Space Station (ISS) astronauts during long-duration missions. This is accomplished by providing integration and operation of the necessary hardware and software capabilities. A typical hardware development flow consists of five stages: functional inputs and requirements definition, market research, design life cycle through hardware delivery, crew training, and mission support. The purpose of this presentation is to guide the audience through the early hardware development process: requirement definition through selecting a development path. Specific HRF equipment is used to illustrate the hardware development paths. The source of hardware requirements is the science community and HRF program. The HRF Science Working Group, consisting of SCientists from various medical disciplines, defined a basic set of equipment with functional requirements. This established the performance requirements of the hardware. HRF program requirements focus on making the hardware safe and operational in a space environment. This includes structural, thermal, human factors, and material requirements. Science and HRF program requirements are defined in a hardware requirements document which includes verification methods. Once the hardware is fabricated, requirements are verified by inspection, test, analysis, or demonstration. All data is compiled and reviewed to certify the hardware for flight. Obviously, the basis for all hardware development activities is requirement definition. Full and complete requirement definition is ideal prior to initiating the hardware development. However, this is generally not the case, but the hardware team typically has functional inputs as a guide. The first step is for engineers to conduct market research based on the functional inputs provided by scientists. CommerCially available products are evaluated against the science requirements as well as modifications needed to meet program requirements. Options are consolidated and the hardware development team reaches a hardware development decision point. Within budget and schedule constraints, the team must decide whether or not to complete the hardware as an in-house, subcontract with vendor, or commercial-off-the-shelf (COTS) development. An in-house development indicates NASA personnel or a contractor builds the hardware at a NASA site. A subcontract development is completed off-site by a commercial company. A COTS item is a vendor product available by ordering a specific part number. The team evaluates the pros and cons of each development path. For example, in-bouse developments utilize existing corporate knowledge regarding bow to build equipment for use in space. However, technical expertise would be required to fully understand the medical equipment capabilities, such as for an ultrasound system. It may require additional time and funding to gain the expertise that commercially exists. The major benefit of subcontracting a hardware development is the product is delivered as an end-item and commercial expertise is utilized. On the other hand, NASA has limited control over schedule delays. The final option of COTS or modified COTS equipment is a compromise between in-house and subcontracts. A vendor product may exist that meets all functional requirements but req uires in-house modifications for successful operation in a space environment. The HRF utilizes equipment developed using all of the paths described: inhouse, subcontract, and modified COTS.

Bauer, Liz↗

Thin-Film Embedded Sensors for Battery Health Monitoring

Hybrid or all-electric aircraft are being developed as the next generation of aircraft to both allow new forms of aviation and decrease environmental impact. Since these types of aircraft are based on high-capacity battery technology, safe operation of these batteries becomes increasingly important. In particular, the potential for battery failure due to uncontrolled chemical reactions resulting in thermal runaway, catastrophic failure, and battery fires must be addressed in order for such battery technology to have the level of safety needed for standard aviation implementation. Efforts to ensure battery safety often involve engineering solutions that seek to contain rather than prevent such events by early detection. Such approaches increase the system weight and decrease the power per unit mass provided by the battery system. Existing methods for measuring battery parameters to determine the battery state-of-health are limited. These methods include electrical measurements of the cell current and/or voltage output as well as temperature measurements taken externally on the cell surface. Such external temperature measurements are limited in their ability to provide early warning of impending battery failure. In response, an effort to develop sensors operating internal to battery for health monitoring has been ongoing in the NASA Sensor-based Prognostics to Avoid Runaway Reactions & Catastrophic Ignition (SPARRCI) project. The basic approach associated with this sensor work is the deposition of thin film sensors on the battery separator located between the anode and cathode of the battery. These thin film sensors are then monitored to determine changes in battery parameters and health. Microfabrication techniques are employed to minimize the overall impact of the sensors on battery operation through the implementation of sensors with minimal size, weight, and power consumption. The thickness of the films, which are fabricated through physical vapor deposition (sputtering), are on the order of thousands of angstroms and can have minimal surface area. Thin film sensors for system health management have been implemented for a many decades on complex components for aerospace applications. However, the application of thin films of this type on a battery separator for internal battery monitoring applications has not previously been demonstrated to our knowledge. This paper describes the development of sensors for the internal battery monitoring through the use of thin film sensor technology. Thin metal films were successfully deposited on a battery separator polymer material with good adherence and electrical continuity. Multiple types of sensors have been deposited, as well as lead connections from the sensor to the edge of the separator material. The ability of these thin film sensors immersed in electrolyte to perform multiple types of battery parameter measurements has been demonstrated. For example, a multiparameter sensor system measured multiple properties simultaneously inside of a pouch cell over a wide temperature range. Further, real time measurement of interior temperature changes in a battery pouch cell with an integrated interior temperature sensor was demonstrated. These changes include detecting a fault in the battery (shorting) in situ with rapid response time (less than a minute) corresponding to a more limited response by a temperature sensor mounted externally. Other aspects of monitoring battery health were also explored, such as real-time measurement of simulated dendrite growth/metal deposition by sensor on separator material demonstrated. Future efforts will include improvements in the durability of the sensor structure to allow introduction of the approach into standard battery fabrication techniques. Overall, this work is a step forward in providing a method to prevent catastrophic battery failures and provide a foundation for safer, lighter, and higher energy batteries for the electric aircraft industry.

thin film battery health↗

ESMD Space Grant Faculty Report

The strength of the Exploration Systems Mission Directorate ESMD Faculty Project lies in its ability to meet National Aeronautics Space Administration NASA's Strategic Educational Outcome 1 by developing a sustainable and long-term integration of student involvement at academic institutions with all NASA Centers. This outcome is achieved by a three-fold approach: 1) by collecting Senior Design projects pertaining to Constellation work performed at each of the ten NASA Centers, 2) by engaging students at Minority Serving Institutions in the art of systems engineering and systems design of technologies required for space exploration, and 3) by identifying potential internships at each Center relative to exploration that provide students who are supported by their institutional Space Grant to engage in on-going mission-level and explorative systems designs. The objectives of the ESMD Faculty Project are to: 1. Aid the Centers (both Education Offices and associated technical organizations) in providing relevant opportunities for the ESMD Space Grant Program to support student and faculty in Senior Design projects 2. Enable better matches between the ESMD work required and what the Space Grant Consortia can do to effectively contribute to NASA programs 3. Provide the Space Grant Consortia an opportunity to strengthen relations with the NASA Centers 4. Develop better collective understanding of the U.S. Space Exploration Policy by the Center, Space Grant, faculty, Education Office, and students 5. Enable Space Grant institution faculty to better prepare their students to meet current and future NASA needs 6. Enable the Center Education Offices to strengthen their ties to their technical organizations and Space Grant Consortia 7. Aid KSC in gaining a greater and more detailed understanding of each of the Center activities Senior Design projects are intended to stimulate undergraduate students on current NASA activities related to lunar, Mars, and other planetary missions and to bring out innovative and novel ideas that can be used to complement those currently under development at respective NASA Centers. Additionally, such academic involvement would better the prospects for graduating seniors to pursue graduate studies and to seek careers in the space industry with a strong sense for systems engineering and understanding of design concepts. Internships, on the other hand, are intended to provide hands-on experience to students by engaging them in diverse state-of-the-art technology development, prototype bread-boarding, computer modeling and simulations, hardware and software testing, and other activities that provide students a strong perspective of NASA's vision and mission in enhancing the knowledge of Earth and space planetary sciences. Ten faculty members, each from a Space Grant Consortium-affiliated university, worked at ten NASA Centers for five weeks between June 2 and July 3, 2008. The project objectives listed above were achieved. In addition to collecting data on Senior Design ideas and identifying possible internships that would benefit NASA/ESMD, the faculty fellows promoted and collected data when required for other ESMD-funded programs and helped the Center's Education Office, as,needed. 4

Guo, Jiang↗

Resource Prospector (RP) - Early Prototyping and Development

The Resource Prospector (RP) is an In-Situ Resource Utilization (ISRU) technology demonstration mission under study by the NASA Human Exploration and Operations Mission Directorate's (HEOMD) Advanced Exploration Systems (AES) Division. The mission, currently planned to launch in 2020, will demonstrate extraction of oxygen from lunar regolith to validate ISRU capability. The mission will address key Strategic Knowledge Gaps (SKGs) for robotic and human exploration to the Moon, Near Earth Asteroids (NEAs), and ultimately Mars, as well as meet the strategic goals of the Global Exploration Roadmap (GER), offered by the International Space Exploration Coordination Group (ISECG). In this roadmap, the use of local resources is specifically addressed relating to human exploration. RP will provide knowledge to inform the selection of future mission destinations, support the development of exploration systems, and reduce the risk associated with human exploration. Expanding human presence beyond low-Earth orbit to asteroids and Mars will require the maximum possible use of local materials, so-called in-situ resources. The moon presents a unique destination to conduct robotic investigations that advance ISRU capabilities, as well as providing significant exploration and science value. Lunar regolith contains useful resources such as oxygen, water, silicon, and light metals, like aluminum and titanium. Oxygen can be separated from the regolith for life support (breathable air), or used to create rocket propellant (oxidizer). Regolith can be used to protect against radiation exposure, be processed into solar cells, or used to manufacture construction materials such as bricks and glass. RP will characterize the constituents and distribution of water and other volatiles at the poles of the Moon, enabling innovative uses of local resources, in addition to validating ISRU capabilities. This capability, as well as a deeper understanding of regolith, will be valuable in the exploration of near-Earth asteroids (NEAs) and Mars. In order to reduce risk and explore system designs, the RP project is attempting two-fold approaches to development as it looks towards flight. We continue to explore flight planning, requirements, and interfaces definition by using Engineering Test Units (ETUs), looking towards lunar deployment, while also using fiscal year 2015 to develop, build and test an earth-terrestrial prototype rover and payload system. This terrestrial prototype, called "RP15", is built to both inform the system design, and to be a partnership advocacy tool for this unique mission. RP15 must be affordable within the resource and time constraints of fiscal year 2015, while working to the following Needs, Goals, and Objectives provided by HEOMD/AES: 1. Demonstrate rover mobility in a 1g environment 2. The Surface Segment (prototype rover + payload system) shall represent the flight system concept with as much fidelity as affordable (limited by cost and schedule) - Surface Segment shall be the approximate size/dimension/footprint -Surface Segment shall package all the expected devices (instruments, systems, etc.), even if some facets are mocked-up due to time/cost constraints -Overall Surface Segment fidelity negotiable to make achievable 3. Priority should be given to illustrating mission functionality over support functionality, which exists solely to support mission functionality This paper will provide an overview of RP project developments, including the design and build, capturing the development and initial integrated testing of RP15 in relevant environments.

Lunar↗

Resource Prospector Instrumentation for Lunar Volatiles Prospecting, Sample Acquisition and Processing

Data gathered from lunar missions within the last two decades have significantly enhanced our understanding of the volatile resources available on the lunar surface, specifically focusing on the polar regions. Several orbiting missions such as Clementine and Lunar Prospector have suggested the presence of volatile ices and enhanced hydrogen concentrations in the permanently shadowed regions of the moon. The Lunar Crater Observation and Sensing Satellite (LCROSS) mission was the first to provide direct measurement of water ice in a permanently shadowed region. These missions with other orbiting assets have laid the groundwork for the next step in the exploration of the lunar surface; providing ground truth data of the volatiles by mapping the distribution and processing lunar regolith for resource extraction. This next step is the robotic mission Resource Prospector (RP). Resource Prospector is a lunar mission to investigate 'strategic knowledge gaps' (SKGs) for in-situ resource utilization (ISRU). The mission is proposed to land in the lunar south pole near a permanently shadowed crater. The landing site will be determined by the science team with input from broader international community as being near traversable landscape that has a high potential of containing elevated concentrations of volatiles such as water while maximizing mission duration. A rover will host the Regolith & Environment Science and Oxygen & Lunar Volatile Extraction (RESOLVE) payload for resource mapping and processing. The science instruments on the payload include a 1-meter drill, neutron spectrometer, a near infrared spectrometer, an operations camera, and a reactor with a gas chromatograph-mass spectrometer for volatile analysis. After the RP lander safely delivers the rover to the lunar surface, the science team will guide the rover team on the first traverse plan. The neutron spectrometer (NS) and near infrared (NIR) spectrometer instruments will be used as prospecting tools to guide the traverse path. The NS will map the water-equivalent hydrogen concentration as low as 0.5% by weight to an 80 centimeter depth as the rover traverses the lunar landscape. The NIR spectrometer will measure surficial H2O/OH as well as general mineralogy. When the prospecting instruments identify a potential volatile-rich area during the course of a traverse, the prospect is then mapped out and the most promising location identified. An augering drill capable of sampling to a depth of 100 centimeters will excavate regolith for analysis. A quick assay of the drill cuttings will be made using an operations camera and NIR spectrometer. With the water depth confirmed by this first auguring activity, a regolith sample may be extracted for processing. The drill will deliver the regolith sample to a crucible that will be sealed and heated. Evolved volatiles will be measured by a gas chromatograph-mass spectrometer and the water will be captured and photographed. RP is a solar powered mission, which given the polar location translates to a relatively short mission duration on the order of 4-15 days. This short mission duration drives the concept of operations, instrumentation, and data analysis towards critical real time analysis and decision support. Previous payload field tests have increased the fidelity of the hardware, software, and mission operations. Current activities include a mission level field test to optimize interfaces between the payload and rover as well as better understand the interaction of the science and rover teams during the mission timeline. This paper will include the current status of the science instruments on the payload as well as the integrated field test occurring in fall of 2015. The concept of operations will be discussed, including the real time science and engineering decision-making process based on the critical data from the instrumentation. The path to flight will be discussed with the approach to this ambitious low cost mission.

ISRU↗

The importance of properties in modeling

Casting and welding of superalloys, stainless steel and titanium alloys are processes which can be improved through modeling of heat flow, fluid flow, residual stress development, and microstructural evolution. These simulations require inputs of thermophysical data, some of which involves the partially or totally liquid state. In particular, these processes involve melting, flow in the liquid, and solidification. Modeling of such processes can lead to an improved understanding of defects such as shrinkage, inclusions, cracks, incomplete filling (or penetration), macrosegregation, improper grain structure, and deviations from dimensional specifications. Effective modeling can shorten process development time and improve quality. An approach to these problems is to develop efficient models; validate through correlations with thermal, distortion, and microstructural data; run parametric studies; extract knowledge based rules; and apply to adaptive closed loop control systems. With the appropriate pre- and post-processing, such analyses can be made 'user friendly'. This would include graphical user interfaces as well as realistic images and color maps. In such form, these models can be used for sensitivity analyses, which are useful in defining appropriate sensors and in the development of control strategies. Such modeling can be done at several levels, e.g., the MARO level, modeling large scale phenomena such as heat and fluid flow or material deformation; the MICRO level, modeling the development of dendrites, grains or precipitates; or at the NANO level, modeling point defects, dislocations, stacking faults, etc. There are many computational issues associated with these simulations, e.g. computational efficiency and accuracy. In addition, there are many materials issues, not the least of which is the availability of accurate high temperature thermophysical data for complex alloys. This would include latent heat of fusion, temperature dependent heat capacity and thermal conductivity (for liquid and solid), viscosity, surface tension, thermal expansion, mechanical properties, etc. Preliminary data is frequently gathered from the literature; however, this is often not available for modern alloys. If additional data are required, measurements can be used; however, these are costly, time consuming and can be erroneous due to a lack of testing standards or impure materials. Microstructural predictors can be extracted from thermal information, e.g. cooling rate and thermal gradient; the prediction of microstructure is dependent on solidus and liquidus temperature, mushy zone permeability, the solidification curve, volume changes, phase transformations, alloying effects (such as surface tension or viscosity), mold/metal reactions, metal/environment reactions, etc. Defect maps may be needed to predict the onset of shrinkage, hot cracking or 'freckling'. Constants may be needed for stress relaxation, dendrite coarsening, vaporization, etc. Visualization was used as a tool to better comprehend complex data sets associated with the analysis of directional solidification (including crystal growth) and welding. Examples include not only isotherms, but also cooling rate, growth rate and thermal gradient. The latter two are not single valued scalars, but rather time and space dependent vector fields. Efficient models were developed for both casting and welding to predict heat flow and the relationship to dendrite and grain growth. These codes include many of the non-linear effects, e.g. radiation, which dominate these processes. The home-built FDM code(s) were designed to be useful not only to the scientist, but also to the process engineer. Special output can be requested to compare directly to experimental data. Visualization procedures were developed to visualize critical results, e.g. fusion zone width at the surface opposite that where the arc is applied ('penetration'). Both elaborate and simplified distortion analyses were carried out. It is clear that extensive mechanical property data are critical in order to accurately predict residual stress patterns. A scheme is currently being developed to integrate these modeling tools into a set of control algorithms; however, the success of this approach is critically dependent on the availability of accurate high temperature thermophysical data.

Giamei, A. F.↗

Trajectory Engineering with Modular Patched Conics for Entry Systems and TPS (TEMPEST)

Brief Presenter Biography (35 word limit): Bohdan Wesely is an Aerospace Engineer in the Entry Systems and Technology Division at Ames. He has worked on a variety of projects for NASA including integrated TPS (thermal protection system) flight hardware deliveries and testing services for commercial partners. Introduction: TEMPEST is a new trajectory analysis framework that is designed to fill the gap between dedicated flight mechanics tools and aerothermal and TPS sizing tools. The project started as an SJSU master’s thesis and has since evolved into a general conceptual design tool capable of studying a wide variety of entry problems. Development is ongoing in the Entry Systems and Technology Division at NASA ARC. Why TEMPEST: Space missions involving entry into a planetary atmosphere involve a series of unique requirements across multiple disciplines. Whether it is traditional entry descent and landing (EDL), or aerocapture, the vehicle must navigate to its target landing location or orbit state, and the TPS must protect the payload during entry. The design process typically involves iterative handoffs between various flight mechanics, flow solver, and material response level tools. During the early conceptual phase, a wide variety of feasible trajectories are simulated in a Monte Carlo scenario which broadly satisfy the mission or landing requirements. Next, computational fluid dynamics (CFD), direct simulation Monte Carlo (DSMC), and other flow solver analyses are performed at various key trajectory points to generate an aero-database, heating and TPS design requirements also emerge at this stage. At this point, with updated aerodynamics from the various flow solvers, trajectories can be re-run, this in turn can change the required freestream conditions for the CFD tools, and as a project progresses, these analyses converge, and uncertainty is reduced. However, there is always a “hand-off” occurring between two inherently coupled phenomena. Analysis Description: One of the goals with TEMPEST is to use a variety of first principles estimation methods coupled with an atmosphere model to predict vehicle aerothermodynamics across the entire flight regime while propagating a 3 or 6 degree of freedom (DoF) trajectory. Aerodynamics methods include modified Newtonian, Maxwell and Cercignani- Lampis-Lord (CLL) for continuum, transitional, and free molecular flow regimes. Aerothermodynamics include boundary layer and reference enthalpy methods, and Mutation++ for non-equilibrium chemistry modeling. TEMPEST is also capable of stitching multiple trajectory segments together to study mission scenarios like multi-pass aerocapture and aero-gravity assists. Most of the program is implemented in MATLAB using modern system objects, it relies on several C++ shared libraries for supporting tools like Gmsh, the Global Reference Atmospheric Model (GRAM), and Mutation++. The various first principles aerothermal estimation methods are discretized across either a structured axisymmetric panel mesh or an unstructured tri-mesh generated from an open-source tool such as Gmsh, this allows solutions on the same mesh to be compared across tools such as CB-Aero. CFD Coupling. A physics-aware, gaussian process CFD anchoring scheme is proposed to adjust the various first principles methods as a CFD database is populated. One goal for this anchoring module is to inform the project where CFD should be run. Full knowledge of the entire trajectory, atmosphere, and aerothermodynamics allows for easier identification of high sensitivity areas and uncertainty quantification. While the first principles effects are well known and proven accurate in existing tools such as CB- Aero and Cart3D, a physics aware CFD anchoring scheme increases tool credibility across a project lifecycle. Material Response Modeling. Correct TPS sizing is critical for optimizing mass for science payloads and ensuring mission success. The process typically involves a thermal analysis along the trajectory with surface heating environments as a boundary condition. Several design constraints are maximum bondline temperature and maximum recession with various margining techniques. The material response tool FIAT, developed out of NASA Ames, is currently being integrated into the TEMPEST environment. TPS recession, shape change, mass loss, and mass property alteration are all factors that can perturb an entry trajectory. For missions like Mars 2020, recession was minimal and was safely handled separately as a post process. For missions such as Jupiter Galileo with a high TPS mass fraction or asteroid entries, recession plays a major role. The proposed fully coupled scheme is to use an epoch-based approach where the trajectory integration is halted after a recession threshold, the energy balance and FIAT are solved at each panel, the mesh, aerodynamics, and mass properties are updated, and the trajectory continues. Several computational tradeoffs have been made during the development of TEMPEST to limit the cost of a single trajectory and preserve its utility as a conceptual, rapid iteration tool. Conclusion: Development of TEMPEST is ongoing and the project is still in its infancy. This talk aims to showcase its unique capabilities to support future NASA entry systems missions.

Bohdan O Wesely↗

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

Miniature Exercise Device-2 (MED-2): Preliminary ISS Evaluation Results for a Compact Motorized Resistive and Aerobic Rowing Exercise Device

Future human missions beyond Low Earth Orbit (LEO) will require onboard equipment to provide exercise capabilities for the crew to counter the adverse physiological effects of long-duration microgravity. To accomplish this within the physical constraints of a space vehicle or transit module, a single miniature device that provides both resistive and aerobic exercise modalities is required. To meet this need, Johnson Space Center’s (JSC) Software, Robotics, and Simulation Division (ER) developed the Miniature Exercise Device-2 (MED-2). MED-2 integrates a torque-controlled servomotor and a series-elastic actuator to provide highly-controllable load profiles and a large magnitude output performance in a very small package. This innovative technology is derived from years of JSC/ER design, development and operational experience with cutting-edge robotics, motor controllers, software and actuator/sensor miniaturization, including Robonaut 2 and MED-1. MED-2 was presented at the 2016 ISS R&D Conference. This is an update now that the last of six crewmembers will have completed planned MED-2 sessions on the International Space Station (ISS) in May 2018.Current state-of-the-art ISS exercise equipment consists of two treadmills, a resistive exercise device and two cycle ergometers with a total mass of several thousand pounds and a total volume of several cubic yards. This equipment has proven vital to mitigate the musculoskeletal and cardiovascular degradation effects of microgravity. However, due to the large operational volume and mass of these ISS devices, tailoring them for smaller vehicles, such as Orion, is not possible. In addition, each of the current ISS devices targets a single specific modality. Compared to the existing spaceflight (and even terrestrial) exercise equipment, MED-2 is a new archetype altogether. The combined features of compact size, multi-modality and high-performance is attributable to its innovative series elastic actuator and motor controller. Following its arrival on ISS in 2016, MED-2 was evaluated in two parts. The first and shorter evaluation was an engineering functional checkout of the hardware. As this was a novel exercise device previously never used on ISS, the initial checkout assessed the operation of the hardware and ensured the motion and dynamic range of the crew did not present any collision or other hazards. The second portion of the study collected the heart rates, kinematics and utilized operational volumes of six astronauts to determine the quality of both the resistive and aerobic exercise modalities as delivered by MED-2. Investigators from JSC Biomedical Research and Environmental Science Division (SK) and Glenn Research Center are currently evaluating the data and preparing preliminary results. For the resistive exercise modality, MED-2 demonstrated a range of constant resistive loads from 10-150 lbf. With a displacement range of 84 inches, the MED-2 accommodates users from 5th percentile Japanese female through 95th percentile American male for all of its certified exercises. The displacement measurement accuracy has also been verified within 2.5 percent full range. The crew was able to successfully perform all prescribed resistive exercises, except Goblet Squats which were not feasible with a constant load profile. For the aerobic exercise modality, MED-2 simulated a rowing motion with prescribed and user-selected resistance levels. It has demonstrated rates up to 60 strokes per minute on the ground. MED-2 loads and displacements performance are the same as those cited for the resistive modality. Although each of the crew was able to perform the prescribed aerobic rowing sets, there was considerable variability in the rowing motion among different crewmembers. Also, as expected, the crew was unable to get the full benefits of a typical terrestrial rowing stroke because the current configuration does not allow the user to reach past their feet. These observations have already informed the requirements for other microgravity rowing devices currently in development. One of the unique features of the MED-2 device is the intuitive touch-screen control system. This One Portal graphical user interface (GUI) was developed based on JSC/ER’s heritage knowledge and experience of developing and sustaining the current ISS exercise equipment. Through this interface, the crew easily performed prepared prescriptions as well as had the ability to adjust exercise modality, load and other exercise details such as number of repetitions and number of sets. This touch-screen and GUI fulfilled the MED-2 project goal to simplify the interaction between the user and the device. Furthermore, the extent to which MED-2 utilizes a touchscreen and GUI to control exercise equipment is unmatched among the existing ISS exercise devices. As a motorized device, MED-2 technology can provide a customizable force profile that can be varied as a function of strap displacement, strap velocity or a combination of these and other variables. During 2017, JSC/ER developed and flight-certified a resistive exercise algorithm that mimics the 1-G inertial effects of free-weights and enables adjustable eccentric-to-concentric loading ratios. Subsequent development will explore varying the load profiles and incorporating additional exercises beyond the current list of certified movements.

Exercise↗