SEARCH · Search NASA

Results for “System Level Verification”

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

SourceResearch connectionFrom yearThrough year

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

At least 235 records · Page 13

All sources NASA NTRS DOE OSTI

NASA NTRS1982

Development of a static feed water electrolysis system

A one person level oxygen generation subsystem was developed and production of the one person oxygen metabolic requirements, 0.82 kg, per day was demonstrated without the need for condenser/separators or electrolyte pumps. During 650 hours of shakedown, design verification, and endurance testing, cell voltages averaged 1.62 V at 206 mA/sq cm and at average operating temperature as low as 326 K, virtually corresponding to the state of the art performance previously established for single cells. This high efficiency and low waste heat generation prevented maintenance of the 339 K design temperature without supplemental heating. Improved water electrolysis cell frames were designed, new injection molds were fabricated, and a series of frames was molded. A modified three fluid pressure controller was developed and a static feed water electrolysis that requires no electrolyte in the static feed compartment was developed and successfully evaluated.

Schubert, F. H.↗

NASA NTRS2012

Model-Based Verification and Validation of Spacecraft Avionics

Our simulation was able to mimic the results of 30 tests on the actual hardware. This shows that simulations have the potential to enable early design validation - well before actual hardware exists. Although simulations focused around data processing procedures at subsystem and device level, they can also be applied to system level analysis to simulate mission scenarios and consumable tracking (e.g. power, propellant, etc.). Simulation engine plug-in developments are continually improving the product, but handling time for time-sensitive operations (like those of the remote engineering unit and bus controller) can be cumbersome.

Systems Modeling Language (SysML↗

NASA NTRS2020

Environmental Verification of NASA’s Europa Clipper Mission

NASA’s Jet Propulsion Laboratory (JPL) and its partner are planning a mission to explore an icy moon of Jupiter, Europa. The objective of the planned Europa Clipper mission is to gain insight into the key ingredients for this potentially habitable world. This mission will conduct investigations using a suite of remote sensing and in-situ fields and particles instruments, and a two-channel ice-penetrating radar. Among its science objectives are to produce high-resolution images of Europa's surface, determine its composition, look for signs of recent or ongoing activity, measure the thickness of the ice shell, search for subsurface lakes, and determine the depth and salinity of Europa's ocean. Europa Clipper is expected to encounter very challenging environments. These environments include radiation, dynamics, thermal, and electromagnetics, which have been translated into a set of environmental requirements that are levied onto the Europa Clipper flight system design. This paper describes how the environmental requirements are specified and verified for each flight component and at which level of integration. A couple of examples will be provided to illustrate the process by which a comprehensive set of verification activities is specified and performed for individual subsystems and instruments to ensure mission success.

Man, Kin Fung↗

NASA NTRS2014

Spot: A Programming Language for Verified Flight Software

The C programming language is widely used for programming space flight software and other safety-critical real time systems. C, however, is far from ideal for this purpose: as is well known, it is both low-level and unsafe. This paper describes Spot, a language derived from C for programming space flight systems. Spot aims to maintain compatibility with existing C code while improving the language and supporting verification with the SPIN model checker. The major features of Spot include actor-based concurrency, distributed state with message passing and transactional updates, and annotations for testing and verification. Spot also supports domain-specific annotations for managing spacecraft state, e.g., communicating telemetry information to the ground. We describe the motivation and design rationale for Spot, give an overview of the design, provide examples of Spot's capabilities, and discuss the current status of the implementation.

validation↗

NASA NTRS2019

SAFE50 Reference Design Study for Large-Scale High-Density Low-Altitude UAS Operations in Urban Areas

Enabling safe, routine, and high-density flight operations of small UAS at low-altitude over heavily populated urban centers presents a difficult challenge for emerging UAS Traffic Management (UTM) system concepts. Urban operations by definition involve flight over people, property, and infrastructure. Low-altitude urban environments - such as urban canyons â€“ are one of the most difficult areas for UTM to consider. Mission concepts require routine operations in a cluttered radio-frequency (RF) environment with degraded or denied Global Positioning System (GPS) reception. Flights with any appreciable distance will be beyond visual and communications line-of-sight from ground operators. Timely detection and response to emergencies and onboard failures, which is critical for safe aircraft operation, will be difficult. This work seeks to establish a feasible reference autonomy architecture for autonomous vehicles in an urban UTM system, then verifying and validating this architecture within a complete UTM concept point-design and systems analysis study. In this paper, we present the results from the NASA SAFE50 conceptual design and systems study that investigates the trade-space of urban UTM operations. This advanced conceptual design study develops a feasible, verified, validated point-design solution. The SAFE50 point-design concept places emphasis on advanced, highly-autonomous, and highly-capable vehicles that favors intelligent onboard autonomy over direct human control with today's technologies and operating in today's urban environments. This paper focuses on an general overview of the design study, highlighting decisions made in the architectural solution. This paper will presents a summary of the study, architectures, and requirements. We present an overview of the architecture designs as derived from the top-level UTM system. The point-design has been implemented in both simulation and through flight testing of hardware design prototypes. The results from simulation and flight testing as part of the verification and validation process of the reference design study.

Ippolito, Corey A.↗

NASA NTRS2019

Psyche Early Project Verification & Validation Planning Development

The Psyche mission to the asteroid (16) Psyche was selected as the fourteenth mission in the Discovery program in January 2017. The Psyche mission will determine if (16) Psyche is the core of a larger differentiated body. As part of the development of this mission a Verification and Validation (V&V) engineer was assigned early in the project’s design Phase B. This paper will discuss some of the strategies that the Psyche team is using to take full advantage of the early planning for V&V on flight projects and specifically how the Psyche mission is approaching these tasks. This paper will discuss the effects of having a V&V mindset on: 1) The Psyche requirements development process, and how focusing not only on how the team will verify these requirements but also on developing the tools necessary to track and monitor that verification feeds back into the requirement development process. 2) The Psyche testbed development, and how using a verification mindset is useful for identifying holes in the testbed development process, including the required testbed speed and how to think about testbed certification early in the process while encouraging trades and developing relationships with the testbed team. 3) Developing new V&V Tools for Psyche, and how developing tools early in the project development process means that they can influence the development of other requirement and scheduling tools. 4) Verification Activity Planning, which is typically done to a preliminary level during Phase B of the project, and is important for understanding the major testing that is needed to ensure that the system as built represents the design. On Psyche we are not only focused on bringing this planning to a preliminary level, we are also developing a V&V focused schedule to help us de-conflict V&V activities that may require similar resources early on in the program’s development. 5) Validation Planning, for which we are working with the testbed and model development teams to ensure that their models can be effectively validated and that the plans to do so are in place. In this paper we will describe how the Psyche mission is approaching each of these V&V areas and identify lessons that can be taken by other space missions trying to decide how much effort should be put into V&V early in the project lifecycle.

Solish, Benjamin↗

NASA NTRS2016

James Webb Space Telescope (JWST) Integrated Science Instruments Module (ISIM) Cryo-Vacuum (CV) Test Campaign Summary

JWST Integrated Science Instruments Module (ISIM) completed its system-level space simulation testing program at the NASA Goddard Space Flight Center (GSFC). In March 2016, ISIM was successfully delivered to the next level of integration with the Optical Telescope Element (OTE), to form OTIS (OTE + ISIM), after concluding a series of three cryo-vacuum (CV) tests. During these tests, the complexity of the mission has generated challenging requirements that demand highly reliable system performance and capabilities from the Space Environment Simulator (SES) vacuum chamber. The first test served as a risk reduction test; the second test provided the initial verification of the fully-integrated flight instruments; and the third test verified the system in its final flight configuration following mechanical environmental tests (vibration and acoustics). From one test to the next, shortcomings of the facility were uncovered and associated improvements in operational capabilities and reliability of the facility were required to enable the project to verify system-level requirements. This paper: (1) provides an overview of the integrated mechanical and thermal facility systems required to achieve the objectives of JWST ISIM testing, (2) compares the overall facility performance and instrumentation results from the three ISIM CV tests, and (3) summarizes lessons learned from the ISIM testing campaign.

Yew, Calinda↗

NASA NTRS2011

Achieving Maximum Integration Utilizing Requirements Flow Down

A robust and experienced systems engineering team is essential for a successful program. It is often a challenge to build a core systems engineering team early enough in a program to maximize integration and assure a common path for all supporting teams in a project. Ares I was no exception. During the planning of IVGVT, the team had many challenges including lack of: early identification of stakeholders, team training in NASA s system engineering practices, solid requirements flow down and a top down documentation strategy. The IVGVT team started test planning early in the program before the systems engineering framework had been matured due to an aggressive schedule. Therefore the IVGVT team increased their involvement in the Constellation systems engineering effort. Program level requirements were established that flowed down to IVGVT aligning all stakeholders to a common set of goals. The IVGVT team utilized the APPEL REQ Development Management course providing the team a NASA focused model to follow. The IVGVT team engaged directly with the model verification and validation process to assure that a solid set of requirements drove the need for the test event. The IVGVT team looked at the initial planning state, analyzed the current state and then produced recommendations for the ideal future state of a wide range of systems engineering functions and processes. Based on this analysis, the IVGVT team was able to produce a set of lessons learned and to provide suggestions for future programs or tests to use in their initial planning phase.

Archiable, Wes↗

NASA NTRS1991

Experimental verification of nanometer level optical pathlength control on a flexible structure

This paper describes an experimental facility being developed for demonstration and validation of control concepts arising out of NASA's Control Structure Interaction program. The facility is meant to be a ground testbed with relevance to a broad class of precision optical space systems. The objective of the experimental program is to investigate a multilayer control approach to the maintenance of nanometer-level optical pathlength stability in the presence of external disturbances and multiple structural resonances. The facility is designed to explore the effect of applying, separately and in combinations, structural vibration suppression, vibration isolation, and active optical articulation. This paper describes the testbed facility, the structure, optics, sensors, actuators, and real-time computer and program development environment. Initial optical articulation experimental results are presented.

O'Neal, Michael↗

NASA NTRS1998

Development and Testing of Automatically Generated ACS Flight Software for the MAP Spacecraft

By integrating the attitude determination and control system (ACS) analysis and design, flight software development, and flight software testing processes, it is possible to improve the overall spacecraft development cycle, as well as allow for more thorough software testing. One of the ways to achieve this integration is to use code-generation tools to automatically generate components of the ACS flight software directly from a high-fidelity (HiFi) simulation. In the development of the Microwave Anisotropy Probe (MAP) spacecraft, currently underway at the NASA Goddard Space Flight Center, approximately 1/3 of the ACS flight software was automatically generated. In this paper, we will examine each phase of the ACS subsystem and flight software design life cycle: analysis, design, and testing. In the analysis phase, we scoped how much software we would automatically generate and created the initial interface. The design phase included parallel development of the HiFi simulation and the hand-coded flight software components. Everything came together in the test phase, in which the flight software was tested, using results from the HiFi simulation as one of the bases of comparison for testing. Because parts of the spacecraft HiFi simulation were converted into flight software, more care needed to be put into its development and configuration control to support both the HiFi simulation and flight software. The components of the HiFi simulation from which code was generated needed to be designed based on the fact that they would become flight software. This process involved such considerations as protecting against mathematical exceptions, using acceptable module and parameter naming conventions, and using an input/output interface compatible with the rest of the flight software. Maintaining good configuration control was an issue for the HiFi simulation and the flight software, and a way to track the two systems was devised. Finally, an integrated test approach was devised to support flight software testing at both the unit- and build-test levels using the HiFi simulation to generate data for performance verification. Another benefit of the simulation and code-generation application used on the MAP project is that it supported bringing flight software and test data into the HiFi simulation environment. It was possible to integrate parts of the hand-coded flight software into the HiFi simulation, and also possible to import flight software test data for comparison and performance verification. This capability was used to incorporate the flight software Kalman filter into the HiFi simulation. This enabled us to greatly increase the amount of testing that could be done on the filter, because we could exert a greater degree of control over the software-only simulation than over the flight software test environment. Also, since the simulation could be used to run the Kalman filter faster than real time, our testing efficiency was greatly increased. We will conclude our discussion with a summary of the lessons learned thus far using automatically- generated code for the MAP project, and the spacecraft status as we work towards our scheduled launch in the year 2000.

ODonnell, James R., Jr.↗

NASA NTRS2011

Early Oscillation Detection for DC/DC Converter Fault Diagnosis

The electrical power system of a spacecraft plays a very critical role for space mission success. Such a modern power system may contain numerous hybrid DC/DC converters both inside the power system electronics (PSE) units and onboard most of the flight electronics modules. One of the faulty conditions for DC/DC converter that poses serious threats to mission safety is the random occurrence of oscillation related to inherent instability characteristics of the DC/DC converters and design deficiency of the power systems. To ensure the highest reliability of the power system, oscillations in any form shall be promptly detected during part level testing, system integration tests, flight health monitoring, and on-board fault diagnosis. The popular gain/phase margin analysis method is capable of predicting stability levels of DC/DC converters, but it is limited only to verification of designs and to part-level testing on some of the models. This method has to inject noise signals into the control loop circuitry as required, thus, interrupts the DC/DC converter's normal operation and increases risks of degrading and damaging the flight unit. A novel technique to detect oscillations at early stage for flight hybrid DC/DC converters was developed.

Wang, Bright L.↗

NASA NTRS2014

Independent Verification of Mars-GRAM 2010 with Mars Climate Sounder Data

The Mars Global Reference Atmospheric Model (Mars-GRAM) is an engineering-level atmospheric model widely used for diverse mission and engineering applications. Applications of Mars-GRAM include systems design, performance analysis, and operations planning for aerobraking, entry, descent and landing, and aerocapture. Atmospheric influences on landing site selection and long-term mission conceptualization and development can also be addressed utilizing Mars-GRAM. Mars-GRAM's perturbation modeling capability is commonly used, in a Monte Carlo mode, to perform high-fidelity engineering end-to-end simulations for entry, descent, and landing. Mars-GRAM is an evolving software package resulting in improved accuracy and additional features. Mars-GRAM 2005 has been validated against Radio Science data, and both nadir and limb data from the Thermal Emission Spectrometer (TES). From the surface to 80 km altitude, Mars-GRAM is based on the NASA Ames Mars General Circulation Model (MGCM). Above 80 km, Mars-GRAM is based on the University of Michigan Mars Thermospheric General Circulation Model (MTGCM). The most recent release of Mars-GRAM 2010 includes an update to Fortran 90/95 and the addition of adjustment factors. These adjustment factors are applied to the input data from the MGCM and the MTGCM for the mapping year 0 user-controlled dust case. The adjustment factors are expressed as a function of height (z), latitude and areocentric solar longitude (Ls).

Justh, Hilary L.↗

NASA NTRS2017

Designing to Sample the Unknown: Lessons from OSIRIS-REx Project Systems Engineering

On September 8, 2016, the third NASA New Frontiers mission launched on an Atlas V 411. The Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) will rendezvous with asteroid Bennu in 2018, collect a sample in 2020, and return that sample to Earth in September 2023. The development team has overcome a number of challenges in order to design and build a system that will make contact with an unexplored, airless, low-gravity body. This paper will provide an overview of the mission, then focus in on the system-level challenges and some of the key system-level processes. Some of the lessons here are unique to the type of mission, like discussion of operating at a largely-unknown, low-gravity object. Other lessons, particularly from the build phase, have broad implications. The OSIRIS-REx risk management process was particularly effective in achieving an on-time and under-budget development effort. The systematic requirements management and verification and the system validation also helped identify numerous potential problems. The final assessment of the OSIRIS-REx performance will need to wait until the sample is returned in 2023, but this post-launch assessment will capture some of the key systems-engineering lessons from the development team.

Asteroid↗

NASA NTRS2024

xEMU Thermal Vacuum Testing Overview

The Exploration Extravehicular Mobility Unit (xEMU) project was the culimation of over a decade of spacesuit development that was performed in-house at the NASA Johnson Space Center. This project reached a level where almost fully completed development fidelity spacesuits had been designed, assembled and tested in an integrated configuration. The xEMU Development-Verification-Test (DVT) hardware was assembled into two different xEMU test articles and underwent a series of thermal-vacuum tests at the Johnson Space Center’s Chamber B. These tests not only gathered data on thermal performance, but also exercised the life support system, communication system, suit information systems, and suit avionics. This complex test has and will continue to produce many meaningful reports ranging from component level test results (for example on spacesuit boots), test design of heater cages to simulate thermal environments for a spacesuit test article, and higher level thermal performance of subsystems (such as the Portable Life Support System) or the entire assembly. This paper provides an overview of the test configuration and also top level results from this highly successful integrated test of the xEMU.

PLSS↗

NASA NTRSDate not supplied

xEMU Thermal Vacuum Testing Overview

PLSS↗

NASA NTRS2008

Integrated System Test Approaches for the NASA Ares I Crew Launch Vehicle

NASA is maturing test and evaluation plans leading to flight readiness of the Ares I crew launch vehicle. Key development, qualification, and verification tests are planned . Upper stage engine sea-level and altitude testing. First stage development and qualification motors. Upper stage structural and thermal development and qualification test articles. Main Propulsion Test Article (MPTA). Upper stage green run testing. Integrated Vehicle Ground Vibration Testing (IVGVT). Aerodynamic characterization testing. Test and evaluation supports initial validation flights (Ares I-Y and Orion 1) and design certification.

Cockrell, Charles↗

NASA NTRS1990

A noise assessment and prediction system

A system has been designed to provide an assessment of noise levels that result from testing activities at Aberdeen Proving Ground, Md. The system receives meteorological data from surface stations and an upper air sounding system. The data from these systems are sent to a meteorological model, which provides forecasting conditions for up to three hours from the test time. The meteorological data are then used as input into an acoustic ray trace model which projects sound level contours onto a two-dimensional display of the surrounding area. This information is sent to the meteorological office for verification, as well as the range control office, and the environmental office. To evaluate the noise level predictions, a series of microphones are located off the reservation to receive the sound and transmit this information back to the central display unit. The computer models are modular allowing for a variety of models to be utilized and tested to achieve the best agreement with data. This technique of prediction and model validation will be used to improve the noise assessment system.

Olsen, Robert O.↗

NASA NTRS2008

Using Optically Stimulated Electron Emission as an Inspection Method to Monitor Surface Contamination

During redesign of the Space Shuttle reusable solid rocket motor (RSRM), NASA amended the contract with ATK Launch Systems (then Morton Thiokol Inc.) with Change Order 966 to implement a contamination control and cleanliness verification method. The change order required: (1) A quantitative inspection method (2) A written record of actual contamination levels versus a known reject level (3) A method that is more sensitive than existing methods of visual and black light inspection. Black light inspection is only useful for inspection of contaminants that fluoresce near the 365 nm spectral line and is not useful for inspection of most silicones that will not produce strong fluorescence. Black light inspection conducted by a qualified inspector under controlled light is capable of detecting Conoco HD-2 grease in gross amounts and is very subjective due to operator sensitivity. Optically stimulated electron emission (OSEE), developed at the Materials and Process Laboratory at Marshall Space Flight Center (MSFC), was selected to satisfy Change Order 966. OSEE offers several important advantages over existing laboratory methods with similar sensitivity, e.g., spectroscopy and nonvolatile residue sampling, which provide turn around time, real time capability, and full coverage inspection capability. Laboratory methods require sample gathering and in-lab analysis, which sometimes takes several days to get results. This is not practical in a production environment. In addition, these methods do not offer full coverage inspection of the large components

Lingbloom, Mike S.↗