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 523 records · Page 29
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

A Description of the Software Element of the NASA EME Flight Tests

In support of NASA's Fly-By-Light/Power-By-Wire (FBL/PBW) program, a series of flight tests were conducted by NASA Langley Research Center in February, 1995. The NASA Boeing 757 was flown past known RF transmitters to measure both external and internal radiated fields. The aircraft was instrumented with strategically located sensors for acquiring data on shielding effectiveness and internal coupling. The data are intended to support computational and statistical modeling codes used to predict internal field levels of an electromagnetic environment (EME) on aircraft. The software was an integral part of the flight tests, as well as the data reduction process. The software, which provided flight test instrument control, data acquisition, and a user interface, executes on a Hewlett Packard (HP) 300 series workstation and uses BP VEEtest development software and the C programming language. Software tools were developed for data processing and analysis, and to provide a database organized by frequency bands, test runs, and sensors. This paper describes the data acquisition system on board the aircraft and concentrates on the software portion. Hardware and software interfaces are illustrated and discussed. Particular attention is given to data acquisition and data format. The data reduction process is discussed in detail to provide insight into the characteristics, quality, and limitations of the data. An analysis of obstacles encountered during the data reduction process is presented.

Koppen, Sandra V.↗
NASA NTRS2018

NOS3: NASA Operational Simulator for Small Satellites

The NASA Operational Simulator for Small Satellites (NOS3) is a suite of open-source software tools to aid in areas such as software development, integration & test (I&T), mission operations/training, verification and validation (V&V), and software systems check-out. NOS3 provides a software development environment, a multi-target build system, operational interface/ground software, dynamics and environment simulations, and software-based hardware models. NOS3 has just recently been open-sourced by NASA and is available for immediate use. It enables the development of flight software (FSW) early in the project life cycle when hardware availability is limited. Small satellite development suffers from extensive lead times on many of the commercial-off-the-shelf (COTS) components as well as limited funding for engineering test units (ETUs). To alleviate the need to provide a hardware test-bed for each developer/tester, NOS3 hardware models are based upon characteristic data or manufacturer's data sheets for each individual component. The NOS3 hardware models' fidelity is such that FSW executes unaware that physical hardware is not present. This allows FSW binaries to be compiled for both the simulation environment and the flight computer without changing the FSW source code. For hardware models that provide data which is dependent upon the environment and spacecraft dynamics, such as a GPS receiver or magnetometer, an open-source tool from NASA GSFC (42 Spacecraft Simulator) is used to provide the necessary data. The underlying infrastructure used to transfer messages between FSW and the hardware models can also be used to monitor, intercept, and inject messages, which has proven to be beneficial for V&V of larger missions such as James Webb Space Telescope (JWST). As hardware is selected and becomes available, drivers can be added to the NOS3 environment to enable hardware-in-the-loop (HWIL) testing. When strict time synchronization is not vital, any number of combinations of hardware components and software-based models can be tested. NOS3 was actively used for FSW development and component testing of the Simulation-to-Flight 1 (STF-1) CubeSat and the Lunar IceCube CubeSat. As NOS3 matures, hardware models have been added for common small satellite components such as GPS receivers, electrical power systems and batteries, and antenna systems.

Suder, Mark↗
NASA NTRS1989

The use of real-time, hardware-in-the-loop simulation in the design and development of the new Hughes HS601 spacecraft attitude control system

Realtime simulation and hardware-in-the-loop testing is being used extensively in all phases of the design, development, and testing of the attitude control system (ACS) for the new Hughes HS601 satellite bus. Realtime, hardware-in-the-loop simulation, integrated with traditional analysis and pure simulation activities is shown to provide a highly efficient and productive overall development program. Implementation of high fidelity simulations of the satellite dynamics and control system algorithms, capable of real-time execution (using applied Dynamics International's System 100), provides a tool which is capable of being integrated with the critical flight microprocessor to create a mixed simulation test (MST). The MST creates a highly accurate, detailed simulated on-orbit test environment, capable of open and closed loop ACS testing, in which the ACS design can be validated. The MST is shown to provide a valuable extension of traditional test methods. A description of the MST configuration is presented, including the spacecraft dynamics simulation model, sensor and actuator emulators, and the test support system. Overall system performance parameters are presented. MST applications are discussed; supporting ACS design, developing on-orbit system performance predictions, flight software development and qualification testing (augmenting the traditional software-based testing), mission planning, and a cost-effective subsystem-level acceptance test. The MST is shown to provide an ideal tool in which the ACS designer can fly the spacecraft on the ground.

Slafer, Loren I.↗
NASA NTRS2018

Leveraging Commercial Software Defined Radio for Low Cost Deep Space Testing

In a typical space mission development life cycle, there is a stage where the spacecraft needs to test against the ground station for interface compatibility to ensure that the spacecraft will be properly tracked after launch. This testing normally requires the spacecraft team to bring their flight equipment to the ground station facility. While recognizing that testing with actual flight or engineering module is the most preferred option because of maximum fidelity, there are occasion when the use of actual flight hardware is a logistically challenge because of spacecraft development. Having another test tool that can emulate the spacecraft signal – by recording the signal transmitted by the spacecraft and regenerate an RF signal for ground system testing - would be very useful. It is even more an attractive option if such spacecraft emulator is inexpensive and highly portable. In this paper, we describe a low-cost, light-weight recorder/playback assembly (RPA) that supports deep space missions testing. The equipment leverages on commercially available software defined radios (SDR) and public-domain software. The RPA has been used to support two missions. One effort is to validate that the Uchinoura 34-m tracking station of the Japanese Aerospace Exploration Agency (JAXA) would be able to track the upcoming NASA Exploration Mission 1 (EM-1) spacecraft, scheduled for launch in 2019. The second effort is to help with the testing and certification of the 21-m antenna ground station at the Morehead State University (MSU) in Kentucky, United States, prior to the time when the Lunar IceCube spacecraft is ready for actual compatibility testing. The RPA also enables students/staff training of the new ground station, using the RPA signal as test input into the system. This low-cost test signal allows the MSU team to save money on not having to develop a full-scale self-generated telemetry test signal source.

White, Leslie↗
NASA NTRS1987

Biaxial thermo-mechanical fatigue

Stress-strain and durability information is often desirable for situations in which strain and temperature are changing simultaneously. To obtain such information, strain controlled uniaxial push-pull tests have typically been done. In order to control the mechanical strain, it is necessary in such tests to compute the mechanical strain from the total measured strain using measured temperature and the thermal expansion properties of the specimen. A system for conducting torsional thermomechanical tests is described which has the great advantage that the torsional strain is unaffected by the changing temperature and thus real time computations of quantities is not required for control of the test and the mechanical strain need not be determined from the subtraction of two measured qnantities as is the case in the uniaxial test. In addition to describing torsional thermomechanical tests, guidelines for software to be used in running biaxial thermomechanical tests will also be presented.

Jordan, Eric H.↗
NASA NTRS2001

Life Testing of the Hollow Cathode Plasma Contactor for the ProSEDS Mission

The Propulsive Small Expendable Deployer System (ProSEDS) mission is designed to provide an on-orbit demonstration of the electrodynamic propulsion capabilities of tethers in space. The ProSEDS experiment will be a secondary payload on a Delta 11 unmanned expendable booster. A 5-km conductive tether is attached to the Delta 11 second stage and collects current from the low Earth orbit (LEO) plasma. A hollow cathode plasma contactor emits the collected electrons from the Delta II, completing the electrical circuit with the ambient plasma. The current flowing through the tether generates thrust based on the Lorentz Force Law. The thrust will be generated opposite to the velocity vector, slowing down the spacecraft and causing it to de-orbit in approximately 14 days compared to the normal 6 months. A 10-km non-conductive tether is between the conductive tether and an endmass containing several scientific instruments. The ProSEDS mission lifetime was set at I day because most of the primary objectives can be met in that time. The extended ProSEDS mission will be for as many days as possible, until the Delta 11 second stage burns up or the tether is severed by a micrometeoroid or space debris particle. The Hollow Cathode Plasma Contactor (HCPC) unit has been designed for a 12-day mission. Because of the science requirements to measure the background ambient plasma, the HCPC must operate on a duty cycle. Later in the ProSEDS mission, the HCPC is operated in a manner to allow charging of the secondary battery. Due to the unusual operating requirements by the ProSEDS mission, a development unit of the HCPC was built for thorough testing. This developmental unit was tested for a simulated ProSEDS mission, with measurements of the ability to start and stop during the duty cycle. These tests also provided valuable data for the ProSEDS software requirements. Qualification tests of the HCPC flight hardware are also discussed.

Vaughn, Jason A.↗
NASA NTRS1991

Development of a calibrated software reliability model for flight and supporting ground software for avionic systems

The object of this project was to develop and calibrate quantitative models for predicting the quality of software. Reliable flight and supporting ground software is a highly important factor in the successful operation of the space shuttle program. The models used in the present study consisted of SMERFS (Statistical Modeling and Estimation of Reliability Functions for Software). There are ten models in SMERFS. For a first run, the results obtained in modeling the cumulative number of failures versus execution time showed fairly good results for our data. Plots of cumulative software failures versus calendar weeks were made and the model results were compared with the historical data on the same graph. If the model agrees with actual historical behavior for a set of data then there is confidence in future predictions for this data. Considering the quality of the data, the models have given some significant results, even at this early stage. With better care in data collection, data analysis, recording of the fixing of failures and CPU execution times, the models should prove extremely helpful in making predictions regarding the future pattern of failures, including an estimate of the number of errors remaining in the software and the additional testing time required for the software quality to reach acceptable levels. It appears that there is no one 'best' model for all cases. It is for this reason that the aim of this project was to test several models. One of the recommendations resulting from this study is that great care must be taken in the collection of data. When using a model, the data should satisfy the model assumptions.

Lawrence, Stella↗
NASA NTRS1976

IPCS implications for future supersonic transport aircraft

The Integrated Propulsion Control System (IPCS) demonstrates control of an entire supersonic propulsion module - inlet, engine afterburner, and nozzle - with an HDC 601 digital computer. The program encompasses the design, build, qualification, and flight testing of control modes, software, and hardware. The flight test vehicle is an F-111E airplane. The L.H. inlet and engine will be operated under control of a digital computer mounted in the weapons bay. A general description and the current status of the IPCS program are given.

Billig, L. O.↗
NASA NTRS1978

Digital Fly-By-Wire Flight Control Validation Experience

The experience gained in digital fly-by-wire technology through a flight test program being conducted by the NASA Dryden Flight Research Center in an F-8C aircraft is described. The system requirements are outlined, along with the requirements for flight qualification. The system is described, including the hardware components, the aircraft installation, and the system operation. The flight qualification experience is emphasized. The qualification process included the theoretical validation of the basic design, laboratory testing of the hardware and software elements, systems level testing, and flight testing. The most productive testing was performed on an iron bird aircraft, which used the actual electronic and hydraulic hardware and a simulation of the F-8 characteristics to provide the flight environment. The iron bird was used for sensor and system redundancy management testing, failure modes and effects testing, and stress testing in many cases with the pilot in the loop. The flight test program confirmed the quality of the validation process by achieving 50 flights without a known undetected failure and with no false alarms.

Szalai, K. J.↗
NASA NTRS1984

Investigation of a nozzle instability on an F100 engine equipped with a digital electronic engine control

An instability in the nozzle of the F100 engine, equipped with a digital electronic engine control (DEEC), was observed during a flight evaluation on an F-15 aircraft. The instability occurred in the upper left hand corner (ULMC) of the flight envelope during augmentation. The instability was not predicted by stability analysis, closed-loop simulations of the the engine, or altitude testing of the engine. The instability caused stalls and augmentor blowouts. The nozzle instability and the altitude testing are described. Linear analysis and nonlinear digital simulation test results are presented. Software modifications on further flight test are discussed.

Burcham, F. W., Jr.↗
NASA NTRS1994

SpaceHab 1 maintenance experiment

The SpaceHab 1 flight on STS-57 served as a test platform for evaluation of two space station payloads. The first payload evaluated a space station maintenance concept using a sweep signal generator and a 48-channel logic analyzer to perform fault detection and isolation. Crew procedures files, test setup diagram files, and software to configure the test equipment were created on the ground and uplinked on the astronauts' voice communication circuit to perform tests in flight. In order to use these files, the portable computer was operated in a multi-window configuration. The test data transmitted to the ground allowing the ground staff to identify the cause of the fault and provide the crew with the repair procedures and diagrams. The crew successfully repaired the system under test. The second payload investigated hand soldering and de-soldering of standard components on printed circuit (PC) boards in zero gravity. It also used a new type of intra-vehicular foot restraints which uses the neutral body posture in zero-g to provide retention of the crew without their conscious attention.

Bohannon, Jackie W.↗
NASA NTRS2009

System for Automated Calibration of Vector Modulators

Vector modulators are used to impose baseband modulation on RF signals, but non-ideal behavior limits the overall performance. The non-ideal behavior of the vector modulator is compensated using data collected with the use of an automated test system driven by a LabVIEW program that systematically applies thousands of control-signal values to the device under test and collects RF measurement data. The technology innovation automates several steps in the process. First, an automated test system, using computer controlled digital-to-analog converters (DACs) and a computer-controlled vector network analyzer (VNA) systematically can apply different I and Q signals (which represent the complex number by which the RF signal is multiplied) to the vector modulator under test (VMUT), while measuring the RF performance specifically, gain and phase. The automated test system uses the LabVIEW software to control the test equipment, collect the data, and write it to a file. The input to the Lab - VIEW program is either user-input for systematic variation, or is provided in a file containing specific test values that should be fed to the VMUT. The output file contains both the control signals and the measured data. The second step is to post-process the file to determine the correction functions as needed. The result of the entire process is a tabular representation, which allows translation of a desired I/Q value to the required analog control signals to produce a particular RF behavior. In some applications, corrected performance is needed only for a limited range. If the vector modulator is being used as a phase shifter, there is only a need to correct I and Q values that represent points on a circle, not the entire plane. This innovation has been used to calibrate 2-GHz MMIC (monolithic microwave integrated circuit) vector modulators in the High EIRP Cluster Array project (EIRP is high effective isotropic radiated power). These calibrations were then used to create correction tables to allow the commanding of the phase shift in each of four channels used as a phased array for beam steering of a Ka-band (32-GHz) signal. The system also was the basis of a breadboard electronic beam steering system. In this breadboard, the goal was not to make systematic measurements of the properties of a vector modulator, but to drive the breadboard with a series of test patterns varying in phase and amplitude. This is essentially the same calibration process, but with the difference that the data collection process is oriented toward collecting breadboard performance, rather than the measurement of output from a network analyzer.

Lux, James↗
NASA NTRS2016

Intern Abstract for Spring 2016

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

Gibson, William↗
NASA NTRS2023

Fitting Leak Test Report: Ground-Based Cryogenic Leak Test of Fittings for Cryogenic Fluid Management

EXECUTIVE SUMMARY Mechanically connected joints used in cryogenic fluid lines as part of space flight elements need to survive launch vibrations and remain leak-free to minimize the loss of on-board commodity and hazardous gas accumulation. In 2020, a cryogenic test apparatus was developed which can evaluate the leak performance of pressurized threaded fluid fittings. The fittings were mounted in the TVAC and cooled to cryogenic test temperature and pressurized with helium while the leak rate was measured using a calibrated GHe leak detector. The test articles for the initial proof of concept testing were ¼ and 1 inch Swagelok VCR fittings with three different types of seal rings copper, nickel, and Ni. Each fitting configuration (size/seal material) was subjected to two consecutive cryogenic thermal cycles, followed by exposure to a launch vibration profile at ambient temperature, after which two additional TVAC cycle tests were performed. The testing reported here is a continuation of the 2020 tests with a statistically significant large number of samples and test runs. Three Swagelok VCR fitting sizes were tested ¼, ½ and 1 inch, and five (5) samples of each fitting size, each sample was tested with SST and Ni seal rings (Total of 30 unique test articles). Each test article was subjected to four (4) thermal cycles. Half of these cycles were performed before vibration testing and half were performed after vibration testing. The vibration testing was performed to evaluate the ability of the fittings to survive launch-type vibration profiles and remain leak-free. Leak checking of each fitting was completed at temperatures between 20K – 30K. The test procedure in Section 8.0 was designed to facilitate a qualification test program by allowing a higher test throughput rate coupled with repeatable test profiles. Results were very positive and show that out of the 30 samples they all passed with leak rates a factor of 2-3 lower than the established 10-6sccs GHe leak threshold. The result showed the Ni seals had lower leak rate, but the SST was more rugged. There were two deviations where damage to the Ni seal ring during assembly resulted in a leaky fitting, this is discussed in Section 10.7 Test Deviations. These fittings show great promise for space flight use and further testing is recommended to fully qualify the fittings per the ASTM F1387-19 and/or other relevant NASA specifications. The test equipment hardware and software capability developed for this testing is generic and not restricted to VCR fittings. It can be employed to evaluate/qualify the leak performance of other types of fittings and a wide range of other cryogenic fluid components such as valves, gages, connectors, etc.

Cryogenic↗
NASA NTRS1976

Digital flight control for the NASA 737 airplane

A brief description of the hardware and software for the digital flight control computers for the NASA 737 airplane is given. Software modules include the basic executive, scheduler, redundancy management, software signal selection, system test, mode logic, pitch axis flight control program and the lateral axis flight control program. A more detailed description of the software development effort is given for the digital flight control software. The software development tasks discussed are: software requirements, development, documentation, control, lab evaluation and formal lab tests. The software development costs are identified and conclusions are drawn concerning the software development effort required to support digital flight control for commercial jet transport applications.

Malcom, L. G.↗
NASA NTRS1990

Application of industry-standard guidelines for the validation of avionics software

The application of industry standards to the development of avionics software is discussed, focusing on verification and validation activities. It is pointed out that the procedures that guide the avionics software development and testing process are under increased scrutiny. The DO-178A guidelines, Software Considerations in Airborne Systems and Equipment Certification, are used by the FAA for certifying avionics software. To investigate the effectiveness of the DO-178A guidelines for improving the quality of avionics software, guidance and control software (GCS) is being developed according to the DO-178A development method. It is noted that, due to the extent of the data collection and configuration management procedures, any phase in the life cycle of a GCS implementation can be reconstructed. Hence, a fundamental development and testing platform has been established that is suitable for investigating the adequacy of various software development processes. In particular, the overall effectiveness and efficiency of the development method recommended by the DO-178A guidelines are being closely examined.

Hayhurst, Kelly J.↗
NASA NTRS1986

An experiment in software reliability

The results of a software reliability experiment conducted in a controlled laboratory setting are reported. The experiment was undertaken to gather data on software failures and is one in a series of experiments being pursued by the Fault Tolerant Systems Branch of NASA Langley Research Center to find a means of credibly performing reliability evaluations of flight control software. The experiment tests a small sample of implementations of radar tracking software having ultra-reliability requirements and uses n-version programming for error detection, and repetitive run modeling for failure and fault rate estimation. The experiment results agree with those of Nagel and Skrivan in that the program error rates suggest an approximate log-linear pattern and the individual faults occurred with significantly different error rates. Additional analysis of the experimental data raises new questions concerning the phenomenon of interacting faults. This phenomenon may provide one explanation for software reliability decay.

Dunham, J. R.↗
NASA NTRS1985

Collected software engineering papers, volume 3

Topics addressed include: software technology evaluation programs; collection of valid software engineering data; test processes using structural coverage; prototype expert system for software engineering management; use of an environment characteristic software metric set; software modulation; software development by analysis of change; and independent verification and validation.

Source record↗