Search NASA⌕ Search

SEARCH · Search NASA

Results for “Software Testing”

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 577 records · Page 32

Powering OSCAR

Recycling waste has been an issue on Earth for decades. The OSCAR project seeks to find ways to make sure that it does not become an issue in space. The main focus of OSCAR is the combustion of waste and reclamation of gaseous products in microgravity. The first phase of testing relies on a ground rig that operates both under normal (Earth) gravity and in drop tower tests that briefly simulate a microgravity environment. In the second phase, a test will be performed during a suborbital flight were the experiment will be carried out in microgravity. Throughout the spring term, interns have played an integral part in continuing the progress made by the project. They performed work in upgrading the electrical and mechanical systems that make up OSCAR. They made multiple improvements to the test rig's operating software to improve readability and usability. They prepared and edited documents that were vital to the engineering process. And, they were responsible for performing lab tests and refining the lab operations document and procedure. The interns were a big help in maintaining the rigorous test schedule. OSCAR, which stands for Orbital Syngas Commodity Augmentation Reactor, is to find a way to turn astronaut waste into chemical energy. The two parts of this are important: finding a way to dispose of waste generated in space, and seeing if there is a way to recycle that waste into chemical energy. The importance of the disposal aspect is that there is currently no way to dispose of, or recycle, waste that is created in space other than jettisoning it (which is what the ISS does via empty supply capsules). As manned missions go deeper into space, that method will no longer be viable, as a craft would essentially be littering the space and planets that they visit. Energy reclamation is also important because of the high monetary and spatial costs of sending supplies on space missions. Every little bit extra that can be reused out of what is sent can save room and funds for other supplies. The facet of this problem that the OSCAR project is focusing on is how to combust waste in zero gravity. Combustion in the presence of gravity is one of those things that is taken for granted. When something burns on Earth, the flames rise above the fuel as oxygen flows from underneath. In microgravity, the flames surround the object completely, which restricts the amount of oxygen that can reach the fuel, and retards the combustion. OSCAR uses a vortex reaction chamber to counter this phenomenon. The OSCAR test rig will eventually be tested on a suborbital flight to see if it is an effective solution to the issue in real-world conditions. Currently, there is a prototype test rig that is fully functional. This rig has been previously tested in a 2 second drop test at Glenn Research Center’s (GRC) Zero Gravity Facility (ZGF). (The free-fall conditions of the drop mimic microgravity, if only for a brief period of time). This session’s focus was on upgrading the test rig and software, updating the paperwork, performing additional lab tests, and readying the rig for the five second drop test, again at GRC. II. Upgrades The state of the testing rig at the start of the session was in between its configurations for the two second drop tower and the five second drop tower. The rig needed upgrades to address various insufficiencies that either were discovered during the two second campaign or were a direct result of the differences between the two drop tower setups. The main differences that had to be handled were the increase in shock loads from 30g to 65g, a difference in drop indicating signal (on the falling edge of a pulse instead of a change from high to low), and the ambient pressure of the test apparatus (the two second tower dropped the rig in atmosphere, while the five second tower drops in vacuum).

Cauvel, Thomas↗

Developing a space network interface simulator: The NTS approach

This paper describes the approach used to redevelop the Network Control Center (NCC) Test System (NTS), a hardware and software facility designed to make testing of the NCC Data System (NCCDS) software efficient, effective, and as rigorous as possible prior to operational use. The NTS transmits and receives network message traffic in real-time. Data transfer rates and message content are strictly controlled and are identical to that of the operational systems. NTS minimizes the need for costly and time-consuming testing with the actual external entities (e.g., the Hubble Space Telescope (HST) Payload Operations Control Center (POCC) and the White Sands Ground Terminal). Discussed are activities associated with the development of the NTS, lessons learned throughout the project's lifecycle, and resulting productivity and quality increases.

Hendrzak, Gary E.↗

Development of SEDS data system flight software

The Small Expendable-tether Deployer System (SEDS) is being built for a 1991 flight on a Delta launch vehicle. SEDS will deploy a 50 lb instrument satellite as an end mass at the end of a 20 km tether. The objective of the experiment is to test the SEDS design concept by demonstrating that the system will satisfactorily deploy the full 20 km tether without stopping prematurely, come to a smooth stop on application of the brake, and cut the tether at the proper time after it swings to the vertical. SEDS will also collect data that will be used to test the accuracy of tether dynamics models for this type of deployment. Radar tracking is planned. In addition, the SEDS on-board computer system will record, store, and continuously transmit data over the Delta II S-band telemetry channel. Initial testing of the software under simulated flight conditions was performed. These tests used both assembly language routines running on SEDS data systems and C-language routines on an IBM-PC. As the software now stands relatively few additions are needed before the entire set of flight software is complete.

Pierson, William E.↗

Software engineering project management - A state-of-the-art report

The management of software engineering projects in the aerospace industry was investigated. The survey assessed such features as contract type, specification preparation techniques, software documentation required by customers, planning and cost-estimating, quality control, the use of advanced program practices, software tools and test procedures, the education levels of project managers, programmers and analysts, work assignment, automatic software monitoring capabilities, design and coding reviews, production times, success rates, and organizational structure of the projects.

Thayer, R. H.↗

Experiments in fault tolerant software reliability

The reliability of voting was evaluated in a fault-tolerant software system for small output spaces. The effectiveness of the back-to-back testing process was investigated. Version 3.0 of the RSDIMU-ATS, a semi-automated test bed for certification testing of RSDIMU software, was prepared and distributed. Software reliability estimation methods based on non-random sampling are being studied. The investigation of existing fault-tolerance models was continued and formulation of new models was initiated.

Mcallister, David F.↗

Utilizing Code Generation from Models for Electric Aircraft Motor Controller Flight Software

The processes followed to develop and test safety-critical flight software significantly increase development effort and overhead in comparison to both non-safety-critical and non-flight software. Generating code from models can be used to reduce development effort; however, the processes for using code generation to develop flight software are relatively immature. This work presents an approach for developing safety-critical flight software utilizing code generation from models to reduce development time and effort. The presented use-case is of electric aircraft motor control software developed for NASA's X-57 Maxwell aircraft.

flight software↗

A progress report on a NASA research program for embedded computer systems software

The paper presents the results of the second stage of the Multipurpose User-oriented Software Technology (MUST) program. Four primary areas of activities are discussed: programming environment, HAL/S higher-order programming language support, the Integrated Verification and Testing System (IVTS), and distributed system language research. The software development environment is provided by the interactive software invocation system. The higher-order programming language (HOL) support chosen for consideration is HAL/S mainly because at the time it was one of the few HOLs with flight computer experience and it is the language used on the Shuttle program. The overall purpose of IVTS is to provide a 'user-friendly' software testing system which is highly modular, user controlled, and cooperative in nature.

Foudriat, E. C.↗

SDO FlatSat Facility

The goal of the Solar Dynamics Observatory (SDO) is to understand and, ideally, predict the solar variations that influence life and society. It's instruments will measure the properties of the Sun and will take hifh definition images of the Sun every few seconds, all day every day. The FlatSat is a high fidelity electrical and functional representation of the SDO spacecraft bus. It is a high fidelity test bed for Integration & Test (I & T), flight software, and flight operations. For I & T purposes FlatSat will be a driver to development and dry run electrical integration procedures, STOL test procedures, page displays, and the command and telemetry database. FlatSat will also serve as a platform for flight software acceptance and systems testing for the flight software system component including the spacecraft main processors, power supply electronics, attitude control electronic, gimbal control electrons and the S-band communications card. FlatSat will also benefit the flight operations team through post-launch flight software code and table update development and verification and verification of new and updated flight operations products. This document highlights the benefits of FlatSat; describes the building of FlatSat; provides FlatSat facility requirements, access roles and responsibilities; and, and discusses FlatSat mechanical and electrical integration and functional testing.

Amason, David L.↗

NASA software specification and evaluation system: Software verification/validation techniques

NASA software requirement specifications were used in the development of a system for validating and verifying computer programs. The software specification and evaluation system (SSES) provides for the effective and efficient specification, implementation, and testing of computer software programs. The system as implemented will produce structured FORTRAN or ANSI FORTRAN programs, but the principles upon which SSES is designed allow it to be easily adapted to other high order languages.

Source record↗

An Automated Stall-Speed Warning System

The NASA Dryden Flight Research Facility embarked upon a project with the United States Army Aviation Engineering Flight Activity (USAAEFA) to develop and test a stall-speed warning system. NASA designed and built an automated stall-speed warning system which presents both airspeed and stall speed to the pilot. The airspeed and stall speed are computed in real time by monitoring the basic aerodynamic parameters {dynamic pressure, horizontal and vertical accelerations, and pressure altitude) and other parameters (elevator and flap positions, engine torques, and fuel flow). In addition, an aural warning at predetermined stall margins is presented to the pilot through a voice synthesizer. Once the system was designed and installed in the aircraft, a flight-test program of less than 20 hr was anticipated to determine the stall-speed software coefficients. These coefficients would then be inserted in the system's software and then test flown over a period of about 10 hr for the purposes of evaluation.

Pilot↗

An Automated Stall-Speed Warning System

The NASA Dryden Flight Research Facility embarked upon a project with the United States Army Aviation Engineering Flight Activity (USAAEFA) to develop and test a stall-speed warning system. NASA designed and built an automated stall-speed warning system which presents both airspeed and stall speed to the pilot. The airspeed and stall speed are computed in real time by monitoring the basic aerodynamic parameters (dynamic pressure, horizontal and vertical accelerations, and pressure altitude) and other parameters (elevator and flap positions, engine torques, and fuel flow). In addition, an aural warning at predetermined stall margins is presented to the pilot through a voice synthesizer. Once the system was designed and installed in the aircraft, a flight-test program of less than 20 hr was anticipated to determine the stall-speed software coefficients. These coefficients would then be inserted in the system's software and then test flown over a period of about 10 hr for the purposes of evaluation.

Dynamic Pressure↗

Avionics Simulation, Development and Software Engineering

During this reporting period, all technical responsibilities were accomplished as planned. A close working relationship was maintained with personnel of the MSFC Avionics Department Software Group (ED14), the MSFC EXPRESS Project Office (FD31), and the Huntsville Boeing Company. Accomplishments included: performing special tasks; supporting Software Review Board (SRB), Avionics Test Bed (ATB), and EXPRESS Software Control Panel (ESCP) activities; participating in technical meetings; and coordinating issues between the Boeing Company and the MSFC Project Office.

Source record↗

Electrical Impedance Tomography Technology: 2013 Center Innovation Fund Final Report

Electrical impedance tomography is a medical noninvasive imaging technology which has advantages over other medical imaging technologies for medically safe long term real time internal imaging monitoring applications in human patients. The technology is much more compact, portable, low power and potentially more low cost compared to other medical image technologies, making it very well suited for medical aerospace and spaceflight applications. EIT technology’s main drawback has been low image resolution, and consequently improving EIT resolution is the primary research goal, as well as increasing imaging speed for real time animation imaging. In a relatively short time the BERL group has brought together design plans, technical resources and has built and tested hardware with the purpose of improving EIT imaging technology. EIT prototype system development plans and system designs have been made to target needed EIT technical improvement in electronic and computer hardware as well as EIT software technology. New hardware design and fabrication resources and technologies have been brought together through resourceful use of existing equipment and software at BERL, and a significant advance has been made in custom electronic hardware prototyping capabilities in collaboration with EFAL, for mutual benefit for both NASA KSC laboratories. BERL has gained significant EIT software capability and tested EIT imaging algorithm code through collaboration with an internationally recognized EIT software development and research forum. A new custom workstation has been developed, built and tested using internal resources, equipment and expertise, that includes a new state-of-the-art massively parallel technology that is commercially available. Custom prototype hardware has been designed and tested, a high priority electronic design, key to improving electronic performance and image quality, has been researched and tested in four designs, with a summary of test results of the selected design illustrated here. The selected design performance exceeds the developed EIT design hardware specifications.

Michael R Lapointe↗

CFS Test Framework

NASA's Core Flight System (cFS) provides a generic flight software framework architecture for developing flight software. As the cFS framework has gained popularity over the years within the flight software community, supporting software tools have been developed to assist in the design, development, testing and verification of flight software. The cFS Test Framework (CTF) is a recently developed cFS tool with capabilities to develop and run automated test and verification scripts against flight software targets. The CTF tool parses and executes JSON-based test scripts containing test instructions, while logging and reporting the results. CTF utilizes a plugin-based architecture to allow developers to extend CTF with new test instructions, external interfaces, and custom functionality. To interface with flight software, CTF parses a set of CCSDS message definition files to create the necessary command and telemetry structures for use during the test run. Additionally, CTF also supports interfacing with multiple cFS instances, allowing a test script to verify requirements that involve multiple flight software targets. Lastly, CTF provides support for executing test scripts against FSW running on remote or embedded hardware. This allows CTF to execute the same test scripts across different target configurations throughout the development process. In this presentation, we will introduce the cFS Test Framework (CTF) architecture, discuss the history of cFS testing frameworks, and present the features and capabilities currently provided by CTF. Lastly, we will show a demo of the CTF tool being used to execute test scripts against flight software.

cfs↗

Flight and Integrated Vehicle Testing: Laying the Groundwork for the Next Generation of Space Exploration Launch Vehicles

Integrated vehicle testing will be critical to ensuring proper vehicle integration of the Ares I crew launch vehicle and Ares V cargo launch vehicle. The Ares Projects, based at Marshall Space Flight Center in Alabama, created the Flight and Integrated Test Office (FITO) as a separate team to ensure that testing is an integral part of the vehicle development process. As its name indicates, FITO is responsible for managing flight testing for the Ares vehicles. FITO personnel are well on the way toward assembling and flying the first flight test vehicle of Ares I, th Ares I-X. This suborbital development flight will evaluate the performance of Ares I from liftoff to first stage separation, testing flight control algorithms, vehicle roll control, separation and recovery systems, and ground operations. Ares I-X is now scheduled to fly in summer 2009. The follow-on flight, Ares I-Y, will test a full five-segment first stage booster and will include cryogenic propellants in the upper stage, an upper stage engine simulator, and an active launch abort system. The following flight, Orion 1, will be the first flight of an active upper stage and upper stage engine, as well as the first uncrewed flight of an Orion spacecraft into orbit. The Ares Projects are using an incremental buildup of flight capabilities prior to the first operational crewed flight of Ares I and the Orion crew exploration vehicle in 2015. In addition to flight testing, the FITO team will be responsible for conducting hardware, software, and ground vibration tests of the integrated launch vehicle. These efforts will include verifying hardware, software, and grou handling interfaces. Through flight and integrated testing, the Ares Projects will identify and mitigate risks early the United States prepares to take its next giant leaps to the Moon and beyond.

Taylor, Jim↗

Flight and Integrated Vehicle Testing: Laying the Groundwork for the Next Generation of Space Exploration Launch Vehicles

Integrated vehicle testing will be critical to ensuring proper vehicle integration of the Ares I crew launch vehicle and Ares V cargo launch vehicle. The Ares Projects, based at Marshall Space Flight Center in Alabama, created the Flight and Integrated Test Office (FITO) as a separate team to ensure that testing is an integral part of the vehicle development process. As its name indicates, FITO is responsible for managing flight testing for the Ares vehicles. FITO personnel are well on the way toward assembling and flying the first flight test vehicle of Ares I, the Ares I-X. This suborbital development flight will evaluate the performance of Ares I from liftoff to first stage separation, testing flight control algorithms, vehicle roll control, separation and recovery systems, and ground operations. Ares I-X is now scheduled to fly in summer 2009. The follow-on flight, Ares I-Y, will test a full five-segment first stage booster and will include cryogenic propellants in the upper stage, an upper stage engine simulator, and an active launch abort system. The following flight, Orion 1, will be the first flight of an active upper stage and upper stage engine, as well as the first uncrewed flight of an Orion spacecraft into orbit. The Ares Projects are using an incremental buildup of flight capabilities prior to the first operational crewed flight of Ares I and the Orion crew exploration vehicle in 2015. In addition to flight testing, the FITO team will be responsible for conducting hardware, software, and ground vibration tests of the integrated launch vehicle. These efforts will include verifying hardware, software, and ground handling interfaces. Through flight and integrated testing, the Ares Projects will identify and mitigate risks early as the United States prepares to take its next giant leaps to the Moon and beyond.

Taylor, J. L.↗

Evaluation of Visualization Software

Visualization software is widely used in scientific and engineering research. But computed visualizations can be very misleading, and the errors are easy to miss. We feel that the software producing the visualizations must be thoroughly evaluated and the evaluation process as well as the results must be made available. Testing and evaluation of visualization software is not a trivial problem. Several methods used in testing other software are helpful, but these methods are (apparently) often not used. When they are used, the description and results are generally not available to the end user. Additional evaluation methods specific to visualization must also be developed. We present several useful approaches to evaluation, ranging from numerical analysis of mathematical portions of algorithms to measurement of human performance while using visualization systems. Along with this brief survey, we present arguments for the importance of evaluations and discussions of appropriate use of some methods.

Globus, Al↗

Simulation of Non-Acoustic Combustion Instability in a Hybrid Rocket Motor

A transient model of a hybrid motor was formulated to study the cause and elimination of non-acoustic combustion instability. The transient model was used to simulate four key tests out of a series of seventeen hybrid motor tests conducted by Thiokol, Rocketdyne and Martin Marietta at NASA/Marshall Space Flight Center (NASA/MSFC). These tests were performed under the Hybrid Propulsion Technology for Launch Vehicle Boosters (HPTLVB) program. The first test resulted in stable combustion. The second test resulted in large-amplitude, 6.5 Hz chamber pressure oscillations that gradually damped away by the end of the test. The third test resulted in large-amplitude, 7.5 Hz chamber pressure oscillations that were sustained throughout the test. The seventh test resulted in the elimination of combustion instability with the installation of an orifice immediately upstream of the injector. The formulation and implementation of the model are the scope of this presentation. The current model is an independent continuation of modeling presented previously by joint Thiokol-Rocketdyne collaborators Boardman, Hawkins, Wassom, and Claflin. The previous model simulated an unstable IR&D hybrid motor test performed by Thiokol. There was very good agreement between the model and the test data. Like the previous model, the current model was developed using Matrix-x simulation software. However, the tests performed at NASA/MSFC under the HPTLVB program were actually simulated. In the current model, the hybrid motor consisting of the liquid oxygen (LOX) injector, the multi-port solid fuel grain and the nozzle was simulated. Also, simulated in the model was the LOX feed system consisting of the tank, venturi, valve and feed lines. All components of the hybrid motor and LOX feed system are treated by a lumped-parameter approach. Agreement between the results of the transient model and the actual test data was very good. This agreement between simulated and actual test data indicated that the combustion instability in the hybrid motor was due to two causes. The first cause was a LOX feed system of insufficient stiffness. The second cause was a LOX injector with an impedance or pressure drop that was too low to provide damping against the feed system oscillations. Also, it was discovered that testing with a new grain of solid fuel sustained the combustion instability. However, testing with a used grain of solid fuel caused the combustion instability to gradually decay.

Rocker, Marvin↗