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 667 records · Page 37

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASAs Space Launch System

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex systems engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model-based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model-based algorithms and their development lifecycle from inception through FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS, GNC, and others. One of the principal functions of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - the ARINC 6535-partitioned Operating System, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

AVGS, AR and D for Satellites, ISS, the Moon, Mars and Beyond

With the continuous need to rotate crew and re-supply the International Space Station (ISS) and the desire to return humans to the Moon and for the first time, place humans on Mars, NASA must develop a more robust and highly reliable capability to perform Autonomous Rendezvous and Capture (AR&C) because, unlike the Apollo missions, NASA plans to send the entire crew to the Lunar or Martian surface and must be able to dock with the Orion spacecraft upon return. In 1997, NASA developed the Video Guidance Sensor (VGS) which was flown and tested on STS-87 and STS-95. In 2001, NASA designed and built a more enhanced version of the VGS, called the Advanced Video Guidance Sensor (AVGS). The AVGS offered significant technology improvements to the precursor VGS design. This paper will describe the AVGS as it was in the DART mission of 2005 and the Orbital Express mission of 2007. The paper will describe the capabilities and design concepts of the AVGS as it was flown on the DART 2005 Mission and the DARPA Orbital Express Mission slated to fly in 2007. The paper will cover the Flight Software, problems encountered, testing for Orbital Express and where NASA is going in the future.

Hintze, Geoffrey C.↗

Feasibility of expert systems to enhance Space Station subsystem controllers

Results are described from a project to build a prototype expert system for automated fault isolation and correction of a regenerative CO2 removal device that is typical of functions of the air revitalization group in the Space Station environmental control and life support system (ECLSS). The software was developed using one of the powerful commercial knowledge engineering environments. The goal of the project was to evaluate the feasibility of using a software development environment to rapidly design, construct, test, and change expert system software. The use of expert systems to enhance automatic controllers and the use of information on device design and on device troubleshooting and repair procedures in developing expert systems are discussed.

Malin, J. T.↗

Implementation of Autonomous Control Technology for Plant Growth Chambers

The Kennedy Space Center has significant infrastructure for research using controlled environment plant growth chambers. Such research supports development of bioregenerative life support technology for long-term space missions. Most of the existing chambers in Hangar L and Little L will be moved to the new Space Experiment Research and Processing Laboratory (SERPL) in the summer of 2003. The impending move has created an opportunity to update the control system technologies to allow for greater flexibility, less labor for set-up and maintenance, better diagnostics, better reliability and easier data retrieval. Part of these improvements can be realized using hardware which communicates through an ethernet connection to a central computer for supervisory control but can be operated independently of the computer during routine run-time. Both the hardware and software functionality of an envisioned system were tested on a prototype plant growth chamber (CEC-4) in Hangar L. Based upon these tests, recommendations for hardware and software selection and system design for implementation in SERPL are included.

Costello, Thomas A.↗

Algorithm-Based Fault Tolerance for Numerical Subroutines

A software library implements a new methodology of detecting faults in numerical subroutines, thus enabling application programs that contain the subroutines to recover transparently from single-event upsets. The software library in question is fault-detecting middleware that is wrapped around the numericalsubroutines. Conventional serial versions (based on LAPACK and FFTW) and a parallel version (based on ScaLAPACK) exist. The source code of the application program that contains the numerical subroutines is not modified, and the middleware is transparent to the user. The methodology used is a type of algorithm- based fault tolerance (ABFT). In ABFT, a checksum is computed before a computation and compared with the checksum of the computational result; an error is declared if the difference between the checksums exceeds some threshold. Novel normalization methods are used in the checksum comparison to ensure correct fault detections independent of algorithm inputs. In tests of this software reported in the peer-reviewed literature, this library was shown to enable detection of 99.9 percent of significant faults while generating no false alarms.

Tumon, Michael↗

A multiarchitecture parallel-processing development environment

A description is given of the hardware and software of a multiprocessor test bed - the second generation Hypercluster system. The Hypercluster architecture consists of a standard hypercube distributed-memory topology, with multiprocessor shared-memory nodes. By using standard, off-the-shelf hardware, the system can be upgraded to use rapidly improving computer technology. The Hypercluster's multiarchitecture nature makes it suitable for researching parallel algorithms in computational field simulation applications (e.g., computational fluid dynamics). The dedicated test-bed environment of the Hypercluster and its custom-built software allows experiments with various parallel-processing concepts such as message passing algorithms, debugging tools, and computational 'steering'. Such research would be difficult, if not impossible, to achieve on shared, commercial systems.

Townsend, Scott↗

Delivery of Colloid Micro-Newton Thrusters for the Space Technology 7 Mission

Two flight-qualified clusters of four Colloid Micro-Newton Thruster (CMNT) systems have been delivered to the Jet Propulsion Laboratory (JPL). The clusters will provide precise spacecraft control for the drag-free technology demonstration mission, Space Technology 7 (ST7). The ST7 mission is sponsored by the NASA New Millennium Program and will demonstrate precision formation flying technologies for future missions such as the Laser Interferometer Space Antenna (LISA) mission. The ST7 disturbance reduction system (DRS) will be on the ESA LISA Pathfinder spacecraft using the European gravitational reference sensor (GRS) as part of the ESA LISA Technology Package (LTP). Developed by Busek Co. Inc., with support from JPL in design and testing, the CMNT has been developed over the last six years into a flight-ready and flight-qualified microthruster system, the first of its kind. Recent flight-unit qualification tests have included vibration and thermal vacuum environmental testing, as well as performance verification and acceptance tests. All tests have been completed successfully prior to delivery to JPL. Delivery of the first flight unit occurred in February of 2008 with the second unit following in May of 2008. Since arrival at JPL, the units have successfully passed through mass distribution, magnetic, and EMI/EMC measurements and tests as part of the integration and test (I&T) activities including the integrated avionics unit (IAU). Flight software sequences have been tested and validated with the full flight DRS instrument successfully to the extent possible in ground testing, including full functional and 72 hour autonomous operations tests. Delivery of the cluster assemblies along with the IAU to ESA for integration into the LISA Pathfinder spacecraft is planned for the summer of 2008 with a planned launch and flight demonstration in late 2010.

Precision Formation Flying↗

Digital control of high-intensity acoustic testing

To eliminate previous system instabilities and control high-intensity acoustic tests, a digital control vibration test system is modified by a software change. Three systems for the control of acoustic testing are compared: a hybrid digital/analog system, a digital vibration system, and the same digital vibration system modified by a software change to allow acoustic testing. It is shown that the hybrid system and the modified vibration system exhibit almost equal performance, although the hybrid system performs testing twice as fast. The development of a specialized acoustic test control system is justified since it costs far less than the general-purpose vibration control system. However, the latter is much easier to set up for a test, which is important in preventing overtesting of valuable spacecraft components.

Slusser, R. A.↗

Fault Tree Based Diagnosis with Optimal Test Sequencing for Field Service Engineers

When field service engineers go to customer sites to service equipment, they want to diagnose and repair failures quickly and cost effectively. Symptoms exhibited by failed equipment frequently suggest several possible causes which require different approaches to diagnosis. This can lead the engineer to follow several fruitless paths in the diagnostic process before they find the actual failure. To assist in this situation, we have developed the Fault Tree Diagnosis and Optimal Test Sequence (FTDOTS) software system that performs automated diagnosis and ranks diagnostic hypotheses based on failure probability and the time or cost required to isolate and repair each failure. FTDOTS first finds a set of possible failures that explain exhibited symptoms by using a fault tree reliability model as a diagnostic knowledge to rank the hypothesized failures based on how likely they are and how long it would take or how much it would cost to isolate and repair them. This ordering suggests an optimal sequence for the field service engineer to investigate the hypothesized failures in order to minimize the time or cost required to accomplish the repair task. Previously, field service personnel would arrive at the customer site and choose which components to investigate based on past experience and service manuals. Using FTDOTS running on a portable computer, they can now enter a set of symptoms and get a list of possible failures ordered in an optimal test sequence to help them in their decisions. If facilities are available, the field engineer can connect the portable computer to the malfunctioning device for automated data gathering. FTDOTS is currently being applied to field service of medical test equipment. The techniques are flexible enough to use for many different types of devices. If a fault tree model of the equipment and information about component failure probabilities and isolation times or costs are available, a diagnostic knowledge base for that device can be developed easily.

Iverson, David L.↗

Control System Development for A Zero Boil-Off Hydrogen Storage Demonstration With Two-Stage Active Cooling

A NASA team is designing and building a test article to demonstrate the long duration storage of liquid hydrogen via active cooling (cryocoolers) while implementing a two-stage cooling approach. This activity is one of a large portfolio of NASA’s Space Technology Mission Directorate funded activities which focuses on the technology maturation needed for long duration storage of cryogenic liquid in-space. The current state-of-the-art for liquid hydrogen storage on-orbit is on the order of hours while NASA’s planned missions require storage for months, or even years. To enable such a long duration, Zero Boil-Off conditions must be achieved which requires passive technologies to minimize environmental heat loads, but also active cooling to intercept and reject the remaining heat to deep space. The implementation of active cooling results in a significant amount of dry mass added to the vehicle. Utilizing a Two-Stage Cooling approach, analysis and testing to date indicates the Zero Boil-Off of liquid hydrogen can be achieved with less mass and electrical power relative to a single-stage cooling approach where only one cryocooler is used. This activity will demonstrate the fully integrated suite of technologies needed to enable the Two-Stage Cooling approach which includes Multi-Layer Insulation blankets, Low Conductivity Structures, a Tube-On-Tank Heat Exchanger, Tube-On-Shield Heat Exchanger and a Two-Stage Cryogenerator (both 90 Kelvin and 20 Kelvin) with each stage having an independently controlled circulation loop. The bulk of the heat load is intercepted by the 90 Kelvin loop via a thin foil heat exchanger internal to the insulation blankets (also known as a Broad Area Cooling Shield), with the remainder removed at cryofluid temperature (20 Kelvin) by tubes directly welded to the outer tank surface. In this paper, we examine the challenges of controlling the system, and describe the development of control algorithms and software for future testing with liquid hydrogen. The interactions between the cryofans which control circulation loop mass flow rates, electrical heaters which vary the cryocooler lift to simulate the operation of variable-lift flight units, tank heaters which can vary the overall heat load, and the effects of changes in circulation loop pressure as temperatures change, can be complex and must be well understood to maintain steady-state propellant conditions and achieve Zero Boil-Off. Parallel PID loops and watchdog programs implemented on the user interface system will help bring the systems to steady state operation and keep them at selected operating points within acceptable error, while avoiding runaway feedback loops.

cryogenics↗

A Requirements-Driven Optimization Method for Acoustic Treatment Design

Acoustic treatment designers are able to attenuate specific noise sources inside turbofan engines. Subject to practical considerations, liner design variables may be manipulated to achieve a target attenuation spectrum. But, characteristics of the ideal attenuation spectrum can be difficult to know. Many multidisciplinary system effects govern how engine noise sources contribute to community noise. Given a hardwall fan noise source to be suppressed, and using an analytical certification noise model to compute a community noise measure of merit, the optimal attenuation spectrum can be derived using multidisciplinary systems analysis methods. The subject of this paper is an analytic method that derives the ideal target attenuation spectrum that minimizes noise perceived by observers on the ground. Software is developed and used to test and validate the method on a simple, notional source. With experience gained from minimizing noise of the simple source, the software is tested against a realistic hardwall fan source.

aircraft noise↗

Astrobee: Completed, Current, and Future Research using Free Flying Robots on the International Space Station

After four years on the International Space Station (ISS), the Astrobee Research Facility, has completed over 130 Test Sessions logging over 1000 hours of operations. Managed by the NASA ISS Program OZ office and supported by NASA Ames Research Center (ARC) in California, the Astrobee Team maintains three identical free-flying Astrobee robots for research on the ISS. As a technology demonstration platform, the Astrobee Robots are available for Guest Scientists to use for a spectrum of research capabilities. Astrobee, propelled by battery-operated fans, is designed to autonomously operate throughout most of the USOS (US Orbital Segment), with the objective of minimizing astronaut support. Astrobee carries a suite of six cameras, a two degree-of-freedom (DOF) arm with a gripper that can grasp ISS handrails and other objects, and three payload bays that provide power and data for guest science hardware. Astrobee can autonomously execute hours-long flight plans or be teleoperated from the ground or by astronauts. While the Astrobee Team continues to improve mapping and autonomous flight capabilities, one of the main goals of Astrobee Robots is to provide research opportunities for Guest Scientists. The Astrobee Robot Software (ARS) makes extensive use of the open-source Robot Operating System (ROS). The ARS can be used interchangeably with an Astrobee Simulator or as Astrobee’s onboard software. ARS features include autonomous docking and perching, real-time teleoperations from the ground, plan based autonomous tasks, multi Astrobee communication, among other capabilities. Through simulation software and ground testing laboratories, the Astrobee Team is available to support Guest Scientists during development and testing and lead real-time ISS operations. Guest Scientists can participate in this research opportunity following the Guest Science Lifecycle (GSL) shown in Figure 1: Guest Science Lifecycle below. The Astrobee Team and Guest Scientists have complete research including Gecko materials studies, RFID and sound sensing capabilities, student Robotics Programming Challenges, and Free Flyer formation flight investigations. Current science with the Astrobee Robots includes Free Flyer self-toss studies, new docking capabilities, advanced mapping resolution capabilities, and high resolution panoramic imagery. Future Guest scientists and Astrobee Team research will focus on robotics applications for future NASA missions such as Gateway and Artemis and potential experiments involving human-robot interactions. This presentation will focus on four main subjects, 1) completed, current, and future planned research using the Astrobee robots, 2) how Guest Scientist get from conception to the ISS, 3) Astrobee Facility resources available for Guest Science ground testing and real-time ISS operations support, and 4) lessons learned from four years of ISS operations.

Astrobee↗

Command and Control System Software Development

With the first launch of the National Aeronautics and Space Administration's Space Launch System heavy-lift expendable launch vehicle and Lockheed Martin's Orion Multi-Purpose Crew Vehicle scheduled for the year 2020, there exists a need to complete development of a new command and control system that will provide systems monitoring and launch control for NASA's Exploration Missions. One remaining task necessary for completion of this command and control system is to create and maintain comprehensive unit tests of the control system software packages. These tests should verify that the implementation of all required and desired functionality works as intended. This testing infrastructure is mostly in place, but the control system's open source automation server still reports software "bugs" (possible flaws or failures which may lead to unintended behavior) and intermittently failing unit tests. Since code correctness is of critical importance for human rated software systems, I was assigned to diagnose the root cause of failing unit tests, eliminate non-determinism in these tests, and fix bugs as reported by the automation server.

GUI↗

STRS Radio Service Software for NASA's SCaN Testbed

NASAs Space Communication and Navigation(SCaN) Testbed was launched to the International Space Station in 2012. The objective is to promote new software defined radio technologies and associated software application reuse, enabled by this first flight of NASAs Space Telecommunications Radio System(STRS) architecture standard. Pre-launch testing with the testbeds software defined radios was performed as part of system integration. Radio services for the JPL SDR were developed during system integration to allow the waveform application to operate properly in the space environment, especially considering thermal effects. These services include receiver gain control, frequency offset, IQ modulator balance, and transmit level control. Development, integration, and environmental testing of the radio services will be described. The added software allows the waveform application to operate properly in the space environment, and can be reused by future experimenters testing different waveform applications. Integrating such services with the platform provided STRS operating environment will attract more users, and these services are candidates for interface standardization via STRS.

Mortensen, Dale J.↗

Systems Architecture for Fully Autonomous Space Missions

The NASA Goddard Space Flight Center is working to develop a revolutionary new system architecture concept in support of fully autonomous missions. As part of GSFC's contribution to the New Millenium Program (NMP) Space Technology 7 Autonomy and on-Board Processing (ST7-A) Concept Definition Study, the system incorporates the latest commercial Internet and software development ideas and extends them into NASA ground and space segment architectures. The unique challenges facing the exploration of remote and inaccessible locales and the need to incorporate corresponding autonomy technologies within reasonable cost necessitate the re-thinking of traditional mission architectures. A measure of the resiliency of this architecture in its application to a broad range of future autonomy missions will depend on its effectiveness in leveraging from commercial tools developed for the personal computer and Internet markets. Specialized test stations and supporting software come to past as spacecraft take advantage of the extensive tools and research investments of billion-dollar commercial ventures. The projected improvements of the Internet and supporting infrastructure go hand-in-hand with market pressures that provide continuity in research. By taking advantage of consumer-oriented methods and processes, space-flight missions will continue to leverage on investments tailored to provide better services at reduced cost. The application of ground and space segment architectures each based on Local Area Networks (LAN), the use of personal computer-based operating systems, and the execution of activities and operations through a Wide Area Network (Internet) enable a revolution in spacecraft mission formulation, implementation, and flight operations. Hardware and software design, development, integration, test, and flight operations are all tied-in closely to a common thread that enables the smooth transitioning between program phases. The application of commercial software development techniques lays the foundation for delivery of product-oriented flight software modules and models. Software can then be readily applied to support the on-board autonomy required for mission self-management. An on-board intelligent system, based on advanced scripting languages, facilitates the mission autonomy required to offload ground system resources, and enables the spacecraft to manage itself safely through an efficient and effective process of reactive planning, science data acquisition, synthesis, and transmission to the ground. Autonomous ground systems in turn coordinate and support schedule contact times with the spacecraft. Specific autonomy software modules on-board include mission and science planners, instrument and subsystem control, and fault tolerance response software, all residing within a distributed computing environment supported through the flight LAN. Autonomy also requires the minimization of human intervention between users on the ground and the spacecraft, and hence calls for the elimination of the traditional operations control center as a funnel for data manipulation. Basic goal-oriented commands are sent directly from the user to the spacecraft through a distributed internet-based payload operations "center". The ensuing architecture calls for the use of spacecraft as point extensions on the Internet. This paper will detail the system architecture implementation chosen to enable cost-effective autonomous missions with applicability to a broad range of conditions. It will define the structure needed for implementation of such missions, including software and hardware infrastructures. The overall architecture is then laid out as a common thread in the mission life cycle from formulation through implementation and flight operations.

Esper, Jamie↗

Implementation of Real-Time Hardware in the Loop Simulation for WAVE Instrument Avionics

The Regolith and Environment Science and Oxygen and Lunar Volatile Extraction (RESOLVE) payload will lead the Resource Prospector rover to hydrogen-rich locations on the moon supporting NASA's in-situ resource utilization (ISRU) mission. The Water Analysis and Volatile Extraction (WAVE) system will be responsible for heating up regolith samples and analyzing their volatiles in a vaporized state. Given the space environment, testing flight hardware and software using the scientific instruments can be costly and time consuming, which can hold back progress involving the instruments. A hardware-in-the-loop (HITL) simulation will test the Avionics Data Acquisition as well as the Instrument Interface Unit, through simulating sensors and actuators involved in supporting the WAVE instruments. HITL is a platform for testing and developing WAVE's avionics and software, where the simulation plant will imitate the LAVA and OVEN instruments, thus allowing for an accessible, efficient, and replicable testing environment.

Al Qaraghuli, Ali↗

(Quickly) Testing the Tester via Path Coverage

The configuration complexity and code size of an automated testing framework may grow to a point that the tester itself becomes a significant software artifact, prone to poor configuration and implementation errors. Unfortunately, testing the tester by using old versions of the software under test (SUT) may be impractical or impossible: test framework changes may have been motivated by interface changes in the tested system, or fault detection may become too expensive in terms of computing time to justify running until errors are detected on older versions of the software. We propose the use of path coverage measures as a "quick and dirty" method for detecting many faults in complex test frameworks. We also note the possibility of using techniques developed to diversify state-space searches in model checking to diversify test focus, and an associated classification of tester changes into focus-changing and non-focus-changing modifications.

evaluation of test systems↗

Atmosphere Explorer control system software (version 1.0)

The basic design is described of the Atmosphere Explorer Control System (AECS) software used in the testing, integration, and flight contol of the AE spacecraft and experiments. The software performs several vital functions, such as issuing commands to the spacecraft and experiments, receiving and processing telemetry data, and allowing for extensive data processing by experiment analysis programs. The major processing sections are: executive control section, telemetry decommutation section, command generation section, and utility section.

Villasenor, A.↗