Results for “Unit Testing” — Page 9

NASA NTRS1972

Precision Pointing Control System (PPCS) star tracker test

Tests performed on the TRW precision star tracker are described. The unit tested was a two-axis gimballed star tracker designed to provide star LOS data to an accuracy of 1 to 2 sec. The tracker features a unique bearing system and utilizes thermal and mechanical symmetry techniques to achieve high precision which can be demonstrated in a one g environment. The test program included a laboratory evaluation of tracker functional operation, sensitivity, repeatibility, and thermal stability.

Source record↗

NASA NTRS2014

Pressure Analysis for LAVA-OVEN

The Lunar Advanced Volatiles Analysis (LAVA) and the Oxygen Volatiles Extraction Node (OVEN) are subsystems included in the Regolith Environment Science, and Oxygen Lunar Volatiles Extraction (RESOLVE) payload bound for the Moon in 2019. This Resource Prospector Mission (RPM) has the objective of landing on a shadowed region of the Moons South Pole to collect data and determine whether the resources could be effectively used for space exploration systems. The quantification of the resources will help understand if it can adequately minimize materials carried from Earth by: providing life support, propellants, construction materials or energy supply to the payload or crew. This paper outlines the procedures done for the pressure analysis of the LAVA-OVEN (LOVEN) Integration Testing. The pressure analysis quantifies how much gases and water are present in the sample tested during the Engineering Testing Unit (ETU) phase of instrument development. Ultimately the purpose of these tests is to improve the estimate of the amount of water in each Lunar sample and reduce the time necessary for this estimate. The governing principle that was used for the analysis is the Ideal Gas Law, PV=nRT where P stands for pressure, V for volume, n for number of moles, R being the gas constant and T for temperature. We also estimate the errors involved in these measured and derived quantities since a key objective of the mission is to estimate the quantity of volatiles present in the lunar samples introduced into OVEN.

Lunar↗

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 NTRS2019

GRCop-42 Development and Hot-fire Testing Using Additive Manufacturing Powder Bed Fusion for Channel-Cooled Combustion Chambers

GRCop-42 is a high conductivity, high-strength dispersion strengthened copper-alloy for use in high heat flux applications such as liquid rocket engine combustion devices. This alloy is part of the family of NASA-developed GRCop, copper-chrome-niobium alloys. GRCop alloys were developed for harsh environments specific to regeneratively-cooled combustion chambers and nozzles with good oxidation resistance. Significant development was completed on the GRCop-84 and GRCop-42 alloys in the extruded wrought form demonstrating feasibility for combustion chambers. NASA has recently developed a process for additive manufacturing, specifically Powder Bed Fusion (PBF) or Selective Laser Melting (SLM), of GRCop-42 to establish parameters, characterize the material, and complete testing of components with complex internal features. This evolution of the GRCop-42 was based on the successful predecessor development work using GRCop-84 with the motivation of establishing a new copper-alloy option for use in NASA, government, and industry programs with SLM. A few advantages have been shown with the GRCop-42 that include higher conductivity and faster build speeds over the GRCop-84, and a simplified powder supply chain. Initial property development has shown that it is possible to produce high density builds with strengths equivalent to wrought GRCop-42 and a conductivity greater than GRCop-84. The GRCop-42 has completed process development and initial properties have been established. Several demonstrator combustion chambers have also been fabricated with the SLM GRCop-42 that include integral channels and closeouts. Additional test units have been fabricated and are completing substantial hot-fire testing to demonstrate performance of the material, process, and design.

Gradl, Paul R.↗

NASA NTRS2018

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

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

Restrepo, Carolina I.↗

NASA NTRS2009

A Summary of Closed Brayton Cycle Development Activities at NASA

NASA has been involved in the development of Closed Brayton Cycle (CBC) power conversion technology since the 1960's. CBC systems can be coupled to reactor, isotope, or solar heat sources and offer the potential for high efficiency, long life, and scalability to high power. In the 1960's and 1970's, NASA and industry developed the 10 kW Brayton Rotating Unit (BRU) and the 2 kW mini-BRU demonstrating technical feasibility and performance, In the 1980's, a 25 kW CBC Solar Dynamic (SD) power system option was developed for Space Station Freedom and the technology was demonstrated in the 1990's as part of the 2 kW SO Ground Test Demonstration (GTD). Since the early 2000's, NASA has been pursuing CBC technology for space reactor applications. Before it was cancelled, the Jupiter Icy Moons Orbiter (HMO) mission was considering a 100 kWclass CBC system coupled to a gas-cooled fission reactor. Currently, CBC technology is being explored for Fission Surface Power (FSP) systems to provide base power on the moon and Mars. These recent activities have resulted in several CBC-related technology development projects including a 50 kW Alternator Test Unit, a 20 kW Dual Brayton Test Loop, a 2 kW Direct Drive Gas Brayton Test Loop, and a 12 kW FSP Power Conversion Unit design.

Mason, Lee S.↗

NASA NTRS1976

Vibration testing of the JE-M-604-4-IUE rocket motor (Thiokol P/N E 28639-03)

The NASA International Ultraviolet Explorer (IUE) rocket motor (TE-M-604-4), a solid fuel, spherical rocket motor, was vibration tested in the Impact, Vibration, and Acceleration (IVA) Test Unit of the von Karman Gas Dynamics Facility (VKF). The objective of the test program was to subject the motor to qualification levels of sinusoidal and random vibration prior to the altitude firing of the motor in the Propulsion Development Test Cell (T-3), Engine Test Facility (ETF), AEDC. The vibration testing consisted of a low level sine survey from 5 to 2,000 Hz, followed by a qualification level sine sweep and qualification level random vibration. A second low level sine survey followed the qualification level testing. This sequence of testing was accomplished in each of three orthogonal axes. No motor problems were observed due to the imposition of these dynamic environments.

Alt, R. E.↗

NASA NTRSDate not supplied

Component Level Regression Testing in a Hierarchical Architecture

The Goddard Earth Observing System (GEOS) is an Earth system model consisting of a large suite of individual model components that can be coupled in a flexible manner to investigate a variety of Earth science issues. Specific GEOS model configurations are composed as a hierarchical collection of components based on the Earth System Modeling Framework (ESMF). Regression testing of GEOS is currently limited to (1) full system tests that are poor at isolating specific defects and (2) a suite of unit tests which have very limited coverage. As part of our approach to improve upon the current testing situation, we have prototyped the capability to perform regression tests on individual GEOS components by leveraging and extending existing checkpoint/restart capabilities. In our implementation, each ESMF component has 3 states: Import (what it needs to run), Export (which it needs to provide to other components), and Internal (the component state proper). By capturing, Import, Export and Internal states for a given component during a ull run of GEOS, a generic driver can then rerun the component offline and compare expected exports with those that have been saved. The hierarchical structure of GEOS introduces an interesting wrinkle when trying to test components that in turn drive interacting child components. To fully isolate a parent component, we use the approach of software mocks, in which the exports of children are also saved during the initial capture run of GEOS. Then when testing the parent component, the children components are replaced by a generic mock component that produces exports from the previously saved data and ensures that that all interdependencies among children components are satisfied.

Thomas Clune↗

NASA NTRSDate not supplied

Component Level Testing in a Hierarchical Architecture

The Goddard Earth Observing System (GEOS) is an Earth system model consisting of a large suite of individual model components that can be coupled in a flexible manner to investigate a variety of Earth science issues. Specific GEOS model configurations are composed as a hierarchical collection of components based on the Earth System Modeling Framework (ESMF). Regression testing of GEOS is currently limited to (1) full system tests that are poor at isolating specific defects and (2) a suite of unit tests which have very limited coverage. As part of our approach to improve upon the current testing situation, we have prototyped the capability to perform regression tests on individual GEOS components by leveraging and extending existing checkpoint/restart capabilities. In our implementation, each ESMF component has 3 states: Import (what it needs to run), Export (which it needs to provide to other components), and Internal (the component state proper). By capturing, Import, Export and Internal states for a given component during a ull run of GEOS, a generic driver can then rerun the component offline and compare expected exports with those that have been saved. The hierarchical structure of GEOS introduces an interesting wrinkle when trying to test components that in turn drive interacting child components. To fully isolate a parent component, we use the approach of software mocks, in which the exports of children are also saved during the initial capture run of GEOS. Then when testing the parent component, the children components are replaced by a generic mock component that produces exports from the previously saved data and ensures that that all interdependencies among children components are satisfied.

Tom Clune↗

NASA NTRS1989

A fuel cell energy storage system concept for the Space Station Freedom Extravehicular Mobility Unit

An update is given on work to design and build a Fuel Cell Energy Storage System (FCESS) bench-tested unit for the Space Station Freedom Extravehicular Mobility Unit (EMU). Fueled by oxygen and hydride-stored hydrogen, the FCESS is being considered as an alternative to the EMU zinc-silver oxide battery. Superior cycle life and quick recharge are the main attributes of FCESS. The design and performance of a nonventing, 28 V, 34 Ahr system with 7 amp rating are discussed.

Adlhart, Otto J.↗

NASA NTRS2005

Description of the Prometheus Program Alternator/Thruster Integration Laboratory (ATIL)

The Project Prometheus Alternator Electric Thruster Integration Laboratory's (ATIL) primary two objectives are to obtain test data to influence the power conversion and electric propulsion systems design, and to assist in developing the primary power quality specifications prior to system Preliminary Design Review (PDR). ATIL is being developed in stages or configurations of increasing fidelity and complexity in order to support the various phases of the Prometheus program. ATIL provides a timely insight of the electrical interactions between a representative Permanent Magnet Generator, its associated control schemes, realistic electric system loads, and an operating electric propulsion thruster. The ATIL main elements are an electrically driven 100 kWe Alternator Test Unit (ATU), an alternator controller using parasitic loads, and a thruster Power Processing Unit (PPU) breadboard. This paper describes the ATIL components, its development approach, preliminary integration test results, and current status.

Baez, Anastacio N.↗

NASA NTRSDate not supplied

NASA Progress on the Development and Qualification of a 12-kW Hall-Effect, Solar Electric Propulsion Thruster

The National Aeronautics and Space Administration (NASA) continues to evolve the human exploration approach for beyond low-Earth orbit and in a manner involving international, academic, and industry partners. The center of this approach is NASA’s Gateway program that will establish a permanent human presence in lunar orbit for human cislunar science, operations, and lunar surface access to eventually land the next American astronauts on the south pole of the Moon. In support of the effort, NASA’s Space Technology Mission Directorate (STMD) began a project to increase the state of the art for the Hall-Effect Solar Electric Propulsion (SEP) technology. The resulting Advanced Electric Propulsion System (AEPS) project has developed a 12 kW Hall-effect thruster in support of the Gateway program. The project is managed by the NASA Glenn Research Center (GRC), supported by the NASA Jet Propulsion Laboratory (JPL) with development, qualification & flight hardware all supplied by L3 Harris Aerojet Rocketdyne (AR). Development of the 12-kW Hall thruster electric propulsion system began with maturation of the Hall Effect Rocket with Magnetic Shielding (HERMeS) Technology Demonstration Units (TDUs). The technology development was then transitioned to AR via the AEPS contract, which built and tested two Engineering Test Unit (ETU) thrusters and multiple critical components. The project transitioned to the production of the three flight thrusters and entered qualification testing at the component and thruster levels.

Electric Propulsion↗

NASA NTRSDate not supplied

NASA Progress on the Development and Qualification of a 12-kW Hall-Effect, Solar Electric Propulsion Thruster

The National Aeronautics and Space Administration (NASA) continues to evolve the human exploration approach for beyond low-Earth orbit and in a manner involving international, academic, and industry partners. The center of this approach is NASA’s Gateway program that will establish a permanent human presence in lunar orbit for human cislunar science, operations, and lunar surface access to eventually land the next American astronauts on the south pole of the Moon. In support of the effort, NASA’s Space Technology Mission Directorate (STMD) began a project to increase the state of the art for the Hall-Effect Solar Electric Propulsion (SEP) technology. The resulting Advanced Electric Propulsion System (AEPS) project has developed a 12 kW Hall-effect thruster in support of the Gateway program. The project is managed by the NASA Glenn Research Center (GRC), supported by the NASA Jet Propulsion Laboratory (JPL) with development, qualification & flight hardware all supplied by L3 Harris Aerojet Rocketdyne (AR). Development of the 12-kW Hall thruster electric propulsion system began with maturation of the Hall Effect Rocket with Magnetic Shielding (HERMeS) Technology Demonstration Units (TDUs). The technology development was then transitioned to AR via the AEPS contract, which built and tested two Engineering Test Unit (ETU) thrusters and multiple critical components. The project transitioned to the production of the three flight thrusters and entered qualification testing at the component and thruster levels.

Electric Propulsion↗

NASA NTRS1978

Orbital servicing of space platforms

NASA-MSFC is planning systems for the orbital servicing and maintenance of large geosynchronous platforms. The goal is to devise methods to maintain, update, and/or replace the basic spacecraft housekeeping equipment as well as the onboard mission equipment. The planning has passed through the feasibility demonstration level. A hard engineering test unit of such an on-orbit servicing system, complete with control system, is being tested and evaluated by MSFC.

Turner, J. R.↗

NASA NTRS1993

Automating test case generation for coverages required by FAA standard DO-178B

Coverage testing techniques are required by the FAA for various levels of subsystem criticality at the unit testing level. Higher levels of criticality require coverage schemes that frequently require more and more test cases, particularly when the number of conditions in a decision grows. For example, if we have a decision with n conditions of the form: if (/ci/ or /c2/ or .... or /cn/) then there are 2(n) possible combinations of condition outcomes. Given the enormous number of inputs that may be required to satisfy different coverages, and given that there are no automated tools for determining these inputs (to our knowledge), we will show how one alternative testing technique, mutation testing, can be coerced into generating inputs that satisfy a code coverage scheme X, i.e., if we modify the rules for mutant generation during mutation testing, this technique will provide test cases that satisfy X.

Voas, Jeffrey M.↗

NASA NTRS1992

Ground Systems Development Environment (GSDE) software configuration management

This report presents a review of the software configuration management (CM) plans developed for the Space Station Training Facility (SSTF) and the Space Station Control Center. The scope of the CM assessed in this report is the Systems Integration and Testing Phase of the Ground Systems development life cycle. This is the period following coding and unit test and preceding delivery to operational use. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the SSTF and the SSCC, and the target systems for SSCC and SSTF. This is the last report in the series. The focus of this report is on the CM plans developed by the contractors for the Mission Systems Contract (MSC) and the Training Systems Contract (TSC). CM requirements are summarized and described in terms of operational software development. The software workflows proposed in the TSC and MSC plans are reviewed in this context, and evaluated against the CM requirements defined in earlier study reports. Recommendations are made to improve the effectiveness of CM while minimizing its impact on the developers.

Church, Victor E.↗

NASA NTRS2015

Resource Prospector (RP) - Early Prototyping and Development

The Resource Prospector (RP) is an In-Situ Resource Utilization (ISRU) technology demonstration mission under study by the NASA Human Exploration and Operations Mission Directorate's (HEOMD) Advanced Exploration Systems (AES) Division. The mission, currently planned to launch in 2020, will demonstrate extraction of oxygen from lunar regolith to validate ISRU capability. The mission will address key Strategic Knowledge Gaps (SKGs) for robotic and human exploration to the Moon, Near Earth Asteroids (NEAs), and ultimately Mars, as well as meet the strategic goals of the Global Exploration Roadmap (GER), offered by the International Space Exploration Coordination Group (ISECG). In this roadmap, the use of local resources is specifically addressed relating to human exploration. RP will provide knowledge to inform the selection of future mission destinations, support the development of exploration systems, and reduce the risk associated with human exploration. Expanding human presence beyond low-Earth orbit to asteroids and Mars will require the maximum possible use of local materials, so-called in-situ resources. The moon presents a unique destination to conduct robotic investigations that advance ISRU capabilities, as well as providing significant exploration and science value. Lunar regolith contains useful resources such as oxygen, water, silicon, and light metals, like aluminum and titanium. Oxygen can be separated from the regolith for life support (breathable air), or used to create rocket propellant (oxidizer). Regolith can be used to protect against radiation exposure, be processed into solar cells, or used to manufacture construction materials such as bricks and glass. RP will characterize the constituents and distribution of water and other volatiles at the poles of the Moon, enabling innovative uses of local resources, in addition to validating ISRU capabilities. This capability, as well as a deeper understanding of regolith, will be valuable in the exploration of near-Earth asteroids (NEAs) and Mars. In order to reduce risk and explore system designs, the RP project is attempting two-fold approaches to development as it looks towards flight. We continue to explore flight planning, requirements, and interfaces definition by using Engineering Test Units (ETUs), looking towards lunar deployment, while also using fiscal year 2015 to develop, build and test an earth-terrestrial prototype rover and payload system. This terrestrial prototype, called "RP15", is built to both inform the system design, and to be a partnership advocacy tool for this unique mission. RP15 must be affordable within the resource and time constraints of fiscal year 2015, while working to the following Needs, Goals, and Objectives provided by HEOMD/AES: 1. Demonstrate rover mobility in a 1g environment 2. The Surface Segment (prototype rover + payload system) shall represent the flight system concept with as much fidelity as affordable (limited by cost and schedule) - Surface Segment shall be the approximate size/dimension/footprint -Surface Segment shall package all the expected devices (instruments, systems, etc.), even if some facets are mocked-up due to time/cost constraints -Overall Surface Segment fidelity negotiable to make achievable 3. Priority should be given to illustrating mission functionality over support functionality, which exists solely to support mission functionality This paper will provide an overview of RP project developments, including the design and build, capturing the development and initial integrated testing of RP15 in relevant environments.

Lunar↗

NASA NTRS2014

SCCS System SW Development

The original project to be completed, GenSim, was a Generic Simulator for Application Control Language scripts. This would mock the systems on which the scripts were meant to be run on so that you could run tests without access to the machine. Soon after the project was started, a different project took priority. Unit testing the Application Services Framework code became the focus of the team because of approaching deadlines. Communication was very important to ensure that code wasn't being duplicated and to keep the team up to date with what mock files are available to them. Because of this, daily meetings were conducted until the testing was complete.

computer programming↗