Search NASA⌕ Search

SEARCH · Search NASA

Results for “developments”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 1,027 records · Page 57

Rigging Test Bed Enables Development of Multi-Stage Decelerator Extraction

The Low Density Supersonic Decelerator (LDSD) project developed a Parachute Deployment System (PDS) for use on its Supersonic Flight Dynamics Tests (SFDT). The PDS involves a multi-stage pilot driven extraction of a supersonic parachute. The uncertainties and complexities of developing the design for the lines and rigging of the PDS were addressed through testing in the Rigging Test Bed (RTB). The RTB provided a facility capable of simulating a variety of extraction scenarios with full scale hardware on the ground. Through more than 100 tests conducted in the facility, a wealth of data and experience were gained that fueled the PDS development. The utility of this testing and the lessons learned are presented in this paper. The goal is to inform the development of similar systems in the future and highlight the value and flexibility this type of testing offers rapid hardware development. The RTB provided a great compliment to the analytical models greatly compressing what would have otherwise been a very lengthy analytical effort or potentially much expanded flight test campaign.

Kenig, Sivan J.↗

Using A Model-Based Systems Engineering Approach For Exploration Medical System Development

NASA's Human Research Program's Exploration Medical Capabilities (ExMC) element is defining the medical system needs for exploration class missions. ExMC's Systems Engineering (SE) team will play a critical role in successful design and implementation of the medical system into exploration vehicles. The team's mission is to "Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds." Development of the medical system is being conducted in parallel with exploration mission architecture and vehicle design development. Successful implementation of the medical system in this environment will require a robust systems engineering approach to enable technical communication across communities to create a common mental model of the emergent engineering and medical systems. Model-Based Systems Engineering (MBSE) improves shared understanding of system needs and constraints between stakeholders and offers a common language for analysis. The ExMC SE team is using MBSE techniques to define operational needs, decompose requirements and architecture, and identify medical capabilities needed to support human exploration. Systems Modeling Language (SysML) is the specific language the SE team is utilizing, within an MBSE approach, to model the medical system functional needs, requirements, and architecture. Modeling methods are being developed through the practice of MBSE within the team, and tools are being selected to support meta-data exchange as integration points to other system models are identified. Use of MBSE is supporting the development of relationships across disciplines and NASA Centers to build trust and enable teamwork, enhance visibility of team goals, foster a culture of unbiased learning and serving, and be responsive to customer needs. The MBSE approach to medical system design offers a paradigm shift toward greater integration between vehicle and the medical system and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. Here, we describe the methods and approach to building this integrated model.

Hanson, A.↗

NASA's Advanced TPS Materials and Technology Development: Multi-Functional Materials and Systems for Space Exploration

NASA's future missions will be more demanding. They require materials to be mass efficient, robust, multi-functional, scalable and able to be integrated with other subsystems to enable innovative missions to accomplish future science missions. Thermal protection systems and materials (TPSM) are critical for the robotic and human exploration of the solar system when it involves entry. TPSM is a single string system with no back-up. Mass efficiency and robustness are required. Integration of TPSM with the aeroshell is both a challenge and an opportunity. Since 2010, NASA's Space Technology Mission Directorate has invested in innovative new materials and systems across a spectrum of game changing technologies. In this keynote address, we plan to highlight and present our successful approaches utilized in developing four different materials and system technologies that use innovative new manufacturing techniques to meet mission needs. 3-D weaving and felt manufacturing allowed us to successfully propose new ways of addressing TPSM challenges. In the 3-D MAT project, we developed and delivered a multi-functional TPS materials solution, in under three years that is an enabler for Lunar Capable Orion Spacecraft. Under the HEEET project, we are developing a robust heat-shield that can withstand extreme entry conditions, both thermally and mechanically, for entry at Venus, Saturn or higher speed sample return missions. The improved efficiency of HEEET allows science missions entry at much reduced G'loads enabling delicate science instruments to be used. The ADEPT concept is a foldable and deployable entry system and the critical component is a multi-functional fabric that is foldable and deployable and also functions as a mechanical aeroshell and a TPS. The fourth technology we will highlight involves felt to address integration challenges of rigid ablative system such as PICA that was used on MSL. The felt technology allows us to develop a compliant TPS for easy integration. The above four technology developments have focused on mission infusion as the success criteria. These technologies are in different stages of mission infusion. These innovations have led to new mission concepts to be proposed in the future. In our keynote address we will present approaches we have employed throughout the project to create the bridge to transition from low TRL to mission infusion and to overcome the traditional TRL valley of death.

TPS↗

Launch Control System Software Development System Automation Testing

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This system requires high quality testing that will measure and test the capabilities of the system. For the past two years, the Exploration and Operations Division at Kennedy Space Center (KSC) has assigned a group including interns and full-time engineers to develop automated tests to save the project time and money. The team worked on automating the testing process for the SCCS GUI that would use streamed simulated data from the testing servers to produce data, plots, statuses, etc. to the GUI. The software used to develop automated tests included an automated testing framework and an automation library. The automated testing framework has a tabular-style syntax, which means the functionality of a line of code must have the appropriate number of tabs for the line to function as intended. The header section contains either paths to custom resources or the names of libraries being used. The automation library contains functionality to automate anything that appears on a desired screen with the use of image recognition software to detect and control GUI components. The data section contains any data values strictly created for the current testing file. The body section holds the tests that are being run. The function section can include any number of functions that may be used by the current testing file or any other file that resources it. The resources and body section are required for all test files; the data and function sections can be left empty if the data values and functions being used are from a resourced library or another file. To help equip the automation team with better tools, the Project Lead of the Automated Testing Team, Jason Kapusta, assigned the task to install and train an optical character recognition (OCR) tool to Brandon Echols, a fellow intern, and I. The purpose of the OCR tool is to analyze an image and find the coordinates of any group of text. Some issues that arose while installing the OCR tool included the absence of certain libraries needed to train the tool and an outdated software version. We eventually resolved the issues and successfully installed the OCR tool. Training the tool required many images and different fonts and sizes, but in the end the tool learned to accurately decipher the text in the images and their coordinates. The OCR tool produced a file that contained significant metadata for each section of text, but only the text and coordinates of the text was required for our purpose. The team made a script to parse the information we wanted from the OCR file to a different file that would be used by automation functions within the automated framework. Since a majority of development and testing for the automated test cases for the GUI in question has been done using live simulated data on the workstations at the Launch Control Center (LCC), a large amount of progress has been made. As of this writing, about 60% of all of automated testing has been implemented. Additionally, the OCR tool will help make our automated tests more robust due to the tool's text recognition being highly scalable to different text fonts and text sizes. Soon we will have the whole test system automated, allowing for more full-time engineers working on development projects.

Automation↗

NASA's In-Space Manufacturing Project: Development of a Multimaterial, Multiprocess Fabrication Laboratory for the International Space Station

NASA's long term goal is to send humans to Mars. Over the next two decades, NASA will work with private industry to develop and demonstrate the technologies and capabilities needed to support exploration of the red planet by humans and ensure their safe return to earth. To accomplish this goal, NASA is employing a capability driven approach to its human spaceflight strategy. This approach will develop a suite of evolving capabilities which provide specific functions to solve exploration challenges. One challenge that is critical to sustainable and safer exploration is the ability to manufacture and recycle materials in space. This paper provides an overview of NASA's in-space manufacturing project, its past and current activities, and how technologies under development will ultimately culminate in a multimaterial, multiprocess fabrication laboratory ('FabLab') to be deployed on the International Space Station in the early 2020s. ISM is a critical capability for the long endurance missions NASA seeks to undertake in the coming decades. An unanticipated failure that can be adapted for in low earth orbit may result in a loss of mission in transit to Mars. In order to have a suite of functional ISM capabilities that are compatible with NASA's exploration timeline, ISM must be equipped with the resources necessary to develop these technologies and deploy them for testing prior to the scheduled de-orbit of ISS in 2024. The paper will discuss the phased approach to FabLab development, desired capabilities, and requirements for the hardware. The FabLab will move NASA and private industry significantly closer to changing historical paradigms for human spaceflight where all materials used in space are launched from earth. While the FabLab will be tested on ISS, the system is ultimately intended for use in a deep space habitat or transit vehicle.

Prater, T.↗

Development of Guidelines for In-Situ Repair of SLS-Class Composite Flight Hardware

The purpose of composite repair development at KSC (John F. Kennedy Space Center) is to provide support to the CTE (Composite Technology for Exploration) project. This is a multi-space center effort with the goal of developing bonded joint technology for SLS (Space Launch System) -scale composite hardware. At KSC, effective and efficient repair processes need to be developed to allow for any potential damage to composite components during transport or launch preparation. The focus of the composite repair development internship during the spring of 2018 was on the documentation of repair processes and requirements for process controls based on techniques developed through hands-on work with composite test panels. Three composite test panels were fabricated for the purpose of repair and surface preparation testing. The first panel included a bonded doubler and was fabricated to be damaged and repaired. The second and third panels were both fabricated to be cut into lap-shear samples to test the strength of bond of different surface preparation techniques. Additionally, jointed composite test panels were impacted at MSFC (Marshall Space Flight Center) and analyzed for damage patterns. The observations after the impact tests guided the repair procedure at KSC to focus on three repair methods. With a finalized repair plan in place, future work will include the strength testing of different surface preparation techniques, demonstration of repair methods, and repair of jointed composite test panels being impacted at MSFC.

Weber, Thomas P., Jr.↗

Current EBC Development and Testing at NASA

SiC SiC Ceramic Matrix Composites (CMCs) are a game changer for advanced power generation equipment because of their high temperature capability, oxidation resistance, and light weight that translate to significant reduction in fuel consumption and emission. Limitations of SiC SiC CMCs include surface recession and component cracking and associated chemical and physical degradation in the CMC. The solution pursued to mitigate surface recession of SiC SiC CMCs is the incorporation of coating systems that provide surface protection, which has become known as an Environmental Barrier Coating (EBC). The development of EBCs for the protection of SiC SiC CMCs was a continuation of coating development work for corrosion protection of silicon-based monolithics. The first and second generation EBCs developed in mid 1990s-early 2000s laid the foundation for current EBCs. Environmental degradation that limits EBC life includes surface recession by steam, oxidation in steam environments, and CMAS-EBC reactions. Many engine tests have been conducted since late 1990s and a first CMC component entered into service in 2016 in a commercial engine. The introduction of CMCs represents significant challenges as failure of the EBC means rapid reduction in component life. A reliable lifing method and engine-relevant testing methods to validate life need to be developed. This paper will current activities on EBC development and testing at NASA.

CMC↗

Development of an Optical Slice for an RF and Optical Software Defined Radio

A key component in the Integrated Radio and Optical Communications project at the National Aeronautics and Space Administration's (NASA) Glenn Research Center (GRC) is the radio frequency (RF) and optical software defined radio (SDR). A NASA RF SDR might consist of a general purpose processor to run the Space Telecommunications Radio System (STRS) Architecture for radio command and control, a reconfigurable signal processing device such as a field programmable gate array (FPGA) which houses the waveform, and a digital to analog converter for (DAC) transmitting data. Prior to development, SDR architecture trades on how to combine the RF and optical elements were studied. A modular architecture with physically separate RF and optical hardware slices was chosen and the optical slice of an SDR was designed and developed. The Harris AppSTAR("TM") platform, which consists of an FPGA processing platform with a mezzanine card targeted for RF communications, was used as the base platform in prototyping the optical slice. A serially concatenated pulse position modulation (SCPPM) optical waveform was developed. The waveform follows the standard described in the Consultative Committee for Space Data Systems (CCSDS) Optical Communions Coding and Synchronization Red Book. A custom optical mezzanine printed circuit board card was developed at NASA GRC for optical transmission. The optical mezzanine card replaces the DAC, which is used in the transmission of RF signals. This paper describes RF and optical SDR architecture trades, the Harris AppSTAR("TM") platform, the design of the SCPPM waveform, and the development of the optical mezzanine card.

optical communications↗

Development of the European Service Module Propulsion Subsystem for the Multi-Purpose Crew Vehicle

Hardware Heritage Schedule limitations and budget constraints drove the need for extensive use of heritage hardware designs. In some cases (OMS and TVC) flight hardware reuse (from Shuttle) was required,and will be delta-qualified for use on Orion Primary sources of heritage: ATV Shuttle Orion CM PSS Ariane 5 EPS Targeted Development Testing Component development testing was performed to address the highest risk areas of heritage design compliance with Orion requirements Assembly level development testing was performed to understand complex assemblies and component interactions Heritage Direct re-use of assets from Shuttle Orbiters, all assets have varying flight history. Orion Use Used by Orion to gimbal the main engine during major translational maneuvers Development Testing Random vibration on controller box (lead to card retention design mod) Design Changes (only as required) Circuit board retention in controller box (single instance from Shuttle flight history) New, longer harnesses Basic Specs(8) fixed position engines Thrust: 105 lbf Nozzle area ratio: 164:1 Orion Use Nominally used for separation maneuvers and mid-course correction maneuvers In contingency scenario (failed main engine), used for major translational maneuvers Drives the need for long continuous duration firing Drives the need for off-pulsing (to steer) Control authority requires 50 duty cycle Development Testing Random Vibration (added vibration isolation bracket) Hot fire, duty cycle (changed MR)

pressure fed↗

Development of an Optical Slice for an RF and Optical Software Defined Radio

A key component in the Integrated Radio and Optical Communications project at the National Aeronautics and Space Administration's (NASA) Glenn Research Center (GRC) is the radio frequency (RF) and optical software defined radio (SDR). A NASA RF SDR might consist of a general purpose processor to run the Space Telecommunications Radio System (STRS) Architecture for radio command and control, a reconfigurable signal processing device such as a field programmable gate array (FPGA) which houses the waveform, and a digital to analog converter (DAC) for transmitting data. Prior to development, SDR architecture trades on how to combine the RF and optical elements were studied. A modular architecture with physically separate RF and optical hardware slices was chosen and the optical slice of an SDR was designed and developed. The Harris AppSTARTM platform, which consists of an FPGA processing platform with a mezzanine card targeted for RF communications, was used as the base platform in prototyping the optical slice. A serially concatenated pulse position modulation (SCPPM) optical waveform was developed. The waveform follows the standard described in the Consultative Committee for Space Data Systems (CCSDS) Optical Communications Coding and Synchronization Red Book. A custom optical mezzanine printed circuit board card was developed at NASA GRC for optical transmission. The optical mezzanine card replaces the DAC, which is used in the transmission of RF signals. This paper describes RF and optical SDR architecture trades, the Harris AppSTAR platform, the design of the SCPPM waveform, and the development of the optical mezzanine card.

Nappier, Jennifer M.↗

Development and Qualification of the Primary Structure of the Orion European Service Module

This paper presents an overview of the development and qualification test campaign for the primary structure of the European Service Module of ORION, the NASA spacecraft which will serve the future human exploration missions to the Moon, Mars and beyond. Under an agreement between NASA and ESA, the ORION will be powered by a European Service Module (ESM), providing also water and oxygen for astronauts' life sustainability. The development and qualification of the European Service Module (ESM) is under ESA responsibility with Airbus Defense and Space as the prime contractor. Thales Alenia Space Italia is responsible for design development, manufacturing, assembly and qualification of the Structure subsystem. The European Service Module, installed onto the launch adapter, shall support the crew module with its adapter and a launch abort system. It shall sustain: - A combination of global and local launch loads during lift off and ascent phases, - On orbit loads induced by engine firing for orbital transfers and attitude control. The ESM structure is based on a core made of Composite Fiber Reinforced Polymer (CFRP) sandwich panels complemented by aluminum alloy platforms, longerons and secondary structures. A development campaign has been implemented in order to define and validate composite parts' strength allowable values for design: coupon tests at material level, test at component level up to breadboards tests performed on main structural components (composite to metallic joints, and at panels' discontinuities). An incremental approach as defined in [1] has been followed. A qualification static test campaign at primary structure assembly level has been implemented in order to validate the design against static stiffness and ultimate strength as well as to correlate the structural Finite Element Model (FEM) used for sizing and confirm the margins of safety. The tests have been performed successfully by Thales Alenia Space Italia (TAS-I) on two flight representative structural models (STA1, STA2), in Turin facilities (Italy) between August 2015 and March 2017, with engineering support of technical representatives from Airbus, ESA, NASA and LMCO. The main development and qualification test activities and associated results are presented and discussed in the paper

Structural Testing↗

Development of the Electrostatic Precipitator (ESP) for Mars and Electrodynamic Dust Shield (EDS)

Kennedy Space Center's Swamp Works is a fast-paced and diverse technology development laboratory that aims to advance commercial and government capabilities to colonize extraterrestrial environments. As a part of Swamp Works, the Electrostatic and Surface Physics Laboratory (ESPL) is currently developing new technologies that will further NASA's capabilities to colonize lunar and Martian environments. At the ESPL, the objective of the overall project is to aid in the dust mitigation of robotic and human exploration missions to the moon and Mars. The moon and Mars are covered with layers of dust, which can make long-term exploration missions very difficult. The team at the ESPL is developing an electrostatic precipitator (ESP) to aid in the reduction of interference from airborne Martian dust on equipment. The ESP is designed to mitigate the dust in an intake of CO2-rich dusty gas (i.e., the Martian atmosphere). The ESP is essentially a cylindrical tube with a coaxial wire electrode. Applying a high voltage through this electrode induces a corona discharge (a glowing plasma that envelops the electrode), which is used to charge the inflowing dust. The electric field caused by the corona pushes the charged dust to the walls of the precipitator, preventing the dust to flow out of the tube. Environmental dust can make long-term exploration missions very difficult, and settled dust is no exception. Settled lunar or Martian dust can hinder the performance and lifetime of equipment. For example, dust can settle on the solar panels of a lunar or Martian rover, decreasing its performance while increasing its charging time. To address this, the team at the ESPL is also developing an electrodynamic dust shield (EDS), which is designed to remove lunar or Martian dust from the surfaces of equipment. The EDS uses a non-uniform electric field to generate a dielectrophoretic force, which pushes the particles away from the surface of the shield. A number of dust shields will be tested on the exterior of the International Space Station (ISS) via MISSE-11, a flight payload to the ISS that will test the effects of long-term exposure to space on materials. During my internship at the ESPL, I aided in the development of these technologies. For the ESP, I helped characterize the electrical properties of various geometries and helped redesign the hardware of the testbed (the precipitator used to test this technology in the lab). To characterize the electrical properties of the ESP, I ran various tests of the precipitator, which consisted of varying the environmental conditions and geometry of the testbed. Analyzing the electrical properties of the ESP in various environmental conditions is necessary to characterize its collection efficiency, since it will be used in the dusty Martian environment. For the EDS, I helped analyze the dielectric strength of the surface of the shield via high-voltage testing. A dielectrically strong surface will help the shield survive the harsh environment of space, which will enable it to have both lunar and Martian applications.

Corona Discharge↗

Hybridized Agile Software Development of Flight Control Team Tools for International Space Station's Payload Operations Integration Center

Ground systems operations at the National Aeronautics and Space Administration's (NASA) Payload Operations and Integration Function (POIF) is increasing, via the High Operations Tempo (HOT) initiative, its ability to support more science activities with a fourth crew member on the International Space Station (ISS). The Flight Control Team's need to support this increased crew presence mandated the need for a series of software tools to better handle the increasing pace of payload science operations. The overall need was clear from the outset, but the full scope and user experience for each tool, were not as well understood, so establishing a fixed set of initial requirements was not feasible. An Agile Software Development (ASD) paradigm takes advantage of uncertainty, and plans for it, so it was deemed the most appropriate approach to create room for exploring novel concepts, and to mount a rapid and flexible response to inevitiably changing requirements. It facilitated the need for unprecedented collaboration between the Product Team (i.e. users from the Flight Control Team) and the Development Team (i.e. POIC systems engineers, developers, testers). This is a process shift in the development, test, and release of software from one that is prescriptive to one that is adaptive, which is necessary for these tools to have longevity. The application of ASD to the product development lifecycle permitted the timely incorporation of customer feedback, and, allowed for continuous quality improvements. This resulted in a suite of tools that are efficient, user-friendly, and enable POIF ground systems to support the increasing pace of payload science operations. ASD is not as much a set of prescriptive processes as it is a shift in mindset; one that moves from planning against change, to planning for change, thereby iteratively growing software towards user-defined value.

Albers, Cerese M.↗

ADEPT SR-1 Development and Testing

The Adaptable Deployable Entry and Placement Technology (ADEPT) Sounding Rocket One (SR-1) fight test will be the first sub-orbital flight of Nano-ADEPT. Nano-ADEPT is a deployable heatshield for secondary payload missions desiring to re-enter the Earth's atmosphere or deliver small science payloads to Mars or Venus. Two units have been built and tested in preparation of launch: one designated the "Spare" unit and one the "Flight" unit. The general development approach has been to perform all procedures on the Spare prior to performing them on Flight. This approach has served the project well, allowing for procedures to be rapidly developed and tested on spare hardware where mistakes are less consequential. Conversely, when schedule constraints have come up, the approach has allowed the project to rapidly pivot to an approach where Flight drives the critical path rather than Spare. This approach has enabled relatively rapid development of Flight where technical risk is balanced with schedule realism. This presentation will describe the various tests that have been performed on Nano-ADEPT Spare and Flight units to prepare for the sub-orbital flight. The purpose is to communicate the development approach we took for this low-cost, moderate-risk flight test and hopefully engage the EDL community in a wider discussion of risk-balanced approaches toward flight hardware development of secondary payload atmospheric entry systems.

Smith, Brandon↗

NASA SPLICE Project: Development and Testing of Precision Landing GN&C Technologies

NASA's technology advancement needs for entry, descent and landing call for high-precision, high-rate sensors that can improve navigation accuracy and vehicle control performance. Higher landing accuracy is required for any future human lander missions, and likely, for most robotic missions 1,2. Sensors and algorithms that significantly reduce navigation errors and can image the local terrain will enable landing at locations of high scientific interest that would otherwise pose significant risk to the vehicle. The Safe and Precise Landing-Integrated Capabilities Evolution project, or SPLICE, is developing precision landing and hazard avoidance (PL&HA) technologies for NASA and for potential commercial space flight missions. SPLICE technologies include sensors, algorithms, advanced space flight computing capabilities, and simulation tools used to integrate and study guidance, navigation, and control (GN&C) system performance. SPLICE efforts include hardware-in-the-loop (HWIL) simulation testing, ground testing, and flight testing, including reuse of hardware from the CoOperative Blending of Autonomous Landing Technologies (COBALT) suborbital flight-test payload3,4. Two of the precise navigation sensors that are being developed and matured within SPLICE are LiDARs. Since 2006, NASA Langley has been developing a Navigation Doppler LiDAR (NDL) for precise velocity measurements, and SPLICE is building an NDL engineering test unit (ETU) that will be brought up to TRL 6 following environmental and high-speed1,2 testing. NASA Goddard is developing a Hazard Detection LiDAR (HD LiDAR) engineering development unit (EDU) for SPLICE that has relevance to future human and robotic lander missions. The HD LiDAR will be flight test and matured to TRL 5.

Restrepo, Carolina I.↗

Challenges in Development of Online Visualization and Analysis Tools for Satellite Data

Over the years, various online visualization and analysis tools have been developed to facilitate satellite data access and help scientific users around the world to conduct research and develop applications (e.g., data product evaluation, what-if questions, etc.). For those who are new to satellite data products, using them can be a daunting task due to many obstacles in data processing such as data formats, complex data structures, special software packages, unfamiliar terminology, etc., especially when one is not sure whether a dataset is suitable for his/er research project. Even for experienced users, developing software for data processing and analysis can be a costly and time-consuming task. Online visualization tools can overcome many of these difficulties and allow users to focus on scientific questions. For example, Giovanni (the Geospatial Interactive Online Visualization and Analysis Infrastructure, https://giovanni.gsfc.nasa.gov), developed by the NASA Goddard Earth Sciences Data and Information Services Center (GES DISC), allows access over 1900 satellite and model variables in 82 measurement groups of 8 disciplines without downloading data and software. Main features include basic functions for data analysis and visualization, data provenance, output data in different formats (ASCII, NetCDF, GeoTIFF), and more. Over the years, ~1700 peer-reviewed publications in different disciplines have been benefited from Giovanni in research activities (e.g. initial investigation, what-if questions, product evaluation). Despite the success of online visualization and analysis tools, challenges and new opportunities still exist and more can be done with new requirements and technology. Examples are: a) how to increase the efficiency of dataset search by enhancing intuitive aspects; b) how to facilitate interdisciplinary research; c) how to provide data quality information; d) how to engage users to participate in data quality assessment; and more. NASA Earth Observing System Data and Information System (EOSDIS) satellite-based data products are processed at various levels ranging from Level 0 to Level 4. While most users use data products at higher levels (Level-3 and 4), products at lower levels are still important for case studies, algorithm development, ground validation, etc. In this presentation, we will use Giovanni as an example to present and discuss challenges and near-future opportunities for satellite data online visualization and analysis tools.

Liu, Zhong↗

Using the cFS Command and Data Dictionary (CCDD) to Automate Software Development on Habulous

Final paper is attached. The NASA developed Core Flight System (cFS) is a reusable software architecture that has been used on multiple spaceflight missions. By using this framework, missions are able to reuse code from other missions, as well as leverage deployment onto similar computer architectures (i.e. not "reinvent the wheel" on each new mission). The success in the cFS concept can be seen in the large number of projects using cFS at FSW-2018. The Habulous project is an Earth-based testbed, used for hardware and software that may one day be used on a future space habitat unit, with many participating groups from various NASA centers and aerospace organizations around the country. The distributed nature of the various teams mean that defining (and following) an interface definition is critical on the project. Additionally, since various groups use various types of computer hardware (32/64-bit, big/little endian, Linux/VxWorks/Windows) many additional complications exist in interfacing all the various components into a final integrated system. cFS is used on the majority the flight software (FSW) in running in Habulous. But some subsystems have elected to not use cFS, and use a software bridge (called SBN_lib) to interact with the other cFS nodes in Habulous. In order to most efficiently develop the FSW, a central database is used to define and store each message sent by cFS. A Command and Data Dictionary (CDD) is something nearly universal on spacecraft, but as a team we worked to develop the CDD before the SW development was complete, and not treat it like "as built" documentation. To manage the CDD, the cFS Command and Data Dictionary (CCDD) tool was chosen (available from NASA as open source software). The CCDD tool has successfully been used to automate/autocode a large amount of software used on Habulous, as we are hoping to use it to define even more items in the future (time-triggered Ethernet (TTE) network maps, CPU scheduling). Additionally, Habulous has been exploring the use of cFS on wildly heterogeneous CPUs, and how to coordinate all those various machines using/extending the software bus – network (SBN) application in cFS, as well as TTE to coordinate message passing between various synchronized machines. The major topics to be covered in the presentation are: (1) Updating to the CCSDS_v2 extended headers (and using CPU# as subsystem ID). (2) Managing all the message identification numbers for each cFS message sent/received on any of the various CPUs. (3) Using the CCDD information to automatically generate the C-header files that define the structure for all software bus (SB) commands/telemetry messages. (4) Using the CCDD to automatically generate XML Telemetry and Command Exchange (XTCE) files, which streams display production/integration/testing in a web based display architecture (5) Extending/customizing SBN to pass messages among computers on multiple networks. (6) Using "Protobetter" inside SBN to manage different endian-ness/architectures. (7) Using SBN_lib to allow non-cFS node to communicate with cFS nodes. (8) Developing TTE network and schedule tables for all the various CPUs to use.

Hirsh, Robert L.↗

NASA's Role in Gas Turbine Technology Development: Accelerating Technical Progress via Collaboration Between Academia, Industry, and Government Agencies

Given the maturity of the gas turbine engine since its invention and also considering the limited and flattened level of resources expected to be allocated for NASA aeronautics research and development, we ask the question are NASA technology investments still needed to enable future turbine engine-based propulsion systems? If so, what is NASA’s unique role to justify NASA’s investment? To address this topic, we will first review the accomplishments and the impact that NASA Glenn Research Center has made on turbine engine technologies over the last 78 years. Specifically, this paper discusses NASA’s role and contributions to turbine engine development, specific to both 1) NASA’s role in conducting experiments to understand flow physics and provide relevant benchmark validation experiments for Computational Fluid Dynamics (CFD) code development, validation, and assessment; and 2) the impact of technologies resulting from NASA collaborations with industry, academia, and other government agencies. Note that the scope of the discussion is limited to the NASA technology contributions with which the author was intimately associated, and does not represent the entirety of the NASA contributions to turbine engine technology. The specific research, development, and demonstrations discussed herein were selected to both 1) provide a comprehensive review and reference list of the technology and its impact, and 2) identify NASA’s unique role and highlight how NASA’s involvement resulted in additional benefit to the gas turbine engine community. Secondly, we will discuss current NASA collaborations that are in progress and provide a status of the results. Finally, we discuss the challenges anticipated for future turbine engine-based propulsion systems for civil aviation and identify potential opportunities for collaboration where NASA involvement would be beneficial. Ultimately, the gas turbine engine community will decide if NASA involvement is needed to contribute to the development of the design and analysis tools, databases, and technology demonstration programs to meet these challenges for future turbine engine-based propulsion systems.

Suder, Kenneth L.↗