Search NASA⌕ Search

SEARCH · Search NASA

Results for “test system test”

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 487 records · Page 27

Design, Fabrication, and Testing of an Auxiliary Cooling System for Jet Engines

This report summarizes the technical effort of the Active Cooling for Enhanced Performance (ACEP) program sponsored by NASA. It covers the design, fabrication, and integrated systems testing of a jet engine auxiliary cooling system, or turbocooler, that significantly extends the use of conventional jet fuel as a heat sink. The turbocooler is designed to provide subcooled cooling air to the engine exhaust nozzle system or engine hot section. The turbocooler consists of three primary components: (1) a high-temperature air cycle machine driven by engine compressor discharge air, (2) a fuel/ air heat exchanger that transfers energy from the hot air to the fuel and uses a coating to mitigate fuel deposits, and (3) a high-temperature fuel injection system. The details of the turbocooler component designs and results of the integrated systems testing are documented. Industry Version-Data and information deemed subject to Limited Rights restrictions are omitted from this document.

Leamy, Kevin↗

The DOE ETV-1 Electric Test Vehicle. Phase 3: Performance Testing and system evaluation

Engineering tests were conducted in order to characterize overall system performance and component efficiencies within the system environment. A dynamometer was used in order to minimize the ambient effects and large uncertainties present in track testing. Extensive test requirements were defined and procedures were carefully controlled in order to maintain a high degree of credibility. Limited track testing was performed in order to corroborate the dynamometer results. Test results include an energy flow analysis through the major subsystems and incorporate the aerodynamic and rolling losses under cyclic and various steady speed conditions. The major output from all relevant dynamometer and track tests is also included.

Kurtz, D.↗

Drunk Driver Testing

Systems Technology, Inc. developed a technique to study/measure behavioral changes brought on by long term isolation is now being used in a system for determining whether a driver is too drunk to drive. Device is intended to discourage intoxicated drivers from taking to the road by advising them they are in no condition to operate a vehicle. System is being tested experimentally in California.

Source record↗

Test stand system for vacuum chambers

A test stand system for supporting test items in a vacuum chamber is described. The system consists of a frame adapted to conform to the inside of the vacuum chamber and supporting a central vertical shaft. The shaft rotates on bearings located at each end of the shaft. Several vertically spaced plates which fixed to the vertical shaft may be adjusted for height to support the test equipment as required. The test equipment may be rotated during tests without disturbing the vacuum by a manually actuated drive external to the vacuum chamber.

Newman, D. F.↗

Advanced Ground Systems Maintenance Cryogenics Test Lab Control System Upgrade Project

This project will outfit the Simulated Propellant Loading System (SPLS) at KSC's Cryogenics Test Laboratory with a new programmable logic control system. The control system upgrade enables the Advanced Ground Systems Maintenace Element Integration Team and other users of the SPLS to conduct testing in a controls environment similar to that used at the launch pad.

Technology Portfolio System↗

Genetic toxicity studies of organic chemicals found as contaminants in spacecraft cabin atmospheres

Astronauts can be exposed during spaceflight to organic chemical contaminants in the spacecraft cabin atmosphere. Toxic exposures may cause lesions in the cellular DNA which are subsequently expressed as sister-chromatid exchanges (SCE). Analysis of SCE is a sensitive short term assay techinque to detect and quantitate exposures to DNA damaging (mutagenic) substances. The increase in SCE incidence over baseline (control) levels is generally proportional to the concentration of the mutagen and to the duration of exposure. The BHK-21 baby hamster kidney cell line was the in vitro test system used. Test organics were added to the culture media for 18 hrs, in concentrations ranging from one to 20 ppm. Acetaldehyde and carbon disulfide were chosen for this study since they have occurred as atmospheric contaminants in many of the STS flights, and have been reported to have toxic and mutagenic effects in various test systems. Glutaraldehyde was chosen because few data are available on the mutagenicity of this common fixative, which is carried on STS flights for use in biological experiments. Acetaldehyde was a very strong inducer of SCE at concentrations of 2 ppm and above. Glutaraldehyde and carbon disulfide failed to induce SCE.

Torres, Joseph, Jr.↗

Health maintenance facility system effectiveness testing

The Medical Simulations Working Group conducted a series of medical simulations to evaluate the proposed Health Maintenance Facility (HMF) Preliminary Design Review (PDR) configuration. The goal of these simulations was to test the system effectiveness of the HMF PDR configurations. The objectives of the medical simulations are to (1) ensure fulfillment of requirements with this HMF design, (2) demonstrate the conformance of the system to human engineering design criteria, and (3) determine whether undesirable design or procedural features were introduced into the design. The simulations consisted of performing 6 different medical scenarios with the HMF mockup in the KRUG laboratory. The scenarios included representative medical procedures and used a broad spectrum of HMF equipment and supplies. Scripts were written and simulations performed by medical simulations working group members under observation from others. Data were collected by means of questionnaires, debriefings, and videotapes. Results were extracted and listed in the individual reports. Specific issues and recommendations from each simulation were compiled into the individual reports. General issues regarding the PDR design of the HMF are outlined in the summary report.

Lloyd, Charles W.↗

Windowing System For Test And Simulation

Windowing System for Test and Simulation (WFI) computer program is Turbo-Pascal-class library enabling easy and flexible writing of data to window-type displays. Application programmer's interface simple, small, and powerful, eliminating steep learning curve of other window programming systems. Each routine specifically designed to operate in real-time testing and measurement environments or as part of simulation process. Written in Turbo Pascal v6.0 for IBM PC-series and compatible computers running MS-DOS. Turbo Pascal v6.0 or v7.0 (Borland) required to compile source code.

Katz, R.↗

Positioning System Accuracy Assessment for the Runway Incursion Prevention System Flight Test at the Dallas/Ft. Worth International Airport

NASA/Langley Research Center collaborated with the Federal Aviation Administration (FAA) to test a Runway Incursion Prevention System (RIPS) at the Dallas Fort Worth International Airport (DFW) in October 2000. The RIPS combines airborne and ground sensor data with various cockpit displays to improve pilots' awareness of traffic conditions on the airport surface. The systems tested at DFW involved surface radar and data systems that gather and send surface traffic information to a research aircraft outfitted with the RIPS software, cockpit displays, and data link transceivers. The data sent to the airborne systems contained identification and GPS location of traffic. This information was compared with the own-ship location from airborne GPS receivers to generate incursion alerts. A total of 93 test tracks were flown while operating RIPS. This report compares the accuracy of the airborne GPS systems that gave the own-ship position of the research aircraft for the 93 test tracks.

Quach, Cuong C.↗

Two-terminator RF adapter for background/environment noise measurement

A two-terminator RF adapter for background noise measurement in a test environment comprises a system test port comprising a system test port termination and a system test port connector to connect to a system under test; and a data acquisition port, comprising a data acquisition port termination and a data acquisition port connector to connect to a data acquisition system.

Kolski, Jeffrey↗

Tethered Space Satellite-1 (TSS-1): Technical Roundabouts

In the early 1990's US and Italian scientists collaborated to study the electrodynamics of dragging a satellite on a tether through the electrically charged portion of Earth's atmosphere called the ionosphere. An electrical current induced in the long wire could be used for power and thrust generation for a satellite. Other tether uses include momentum exchange, artificial gravity, deployment of sensors or antennas, and gravity-gradient stabilization for satellites. Before the Tethered Space Satellite (TSS-1), no long tether had ever been flown, so many questions existed on how it would actually behave. The TSS consisted of a satellite with science experiments attached to a 12.5 mile long, very thin (0.10 inch diameter) copper wire assembly wound around a spool in the deployer reel mechanism. With the Space Shuttle at an altitude of 160 nautical miles above earth, the satellite was to be deployed by raising it from the Shuttle bay on a boom facing away from Earth. Once cleared of the bay, the deployer mechanism was to slowly feed out the 12-plus miles of tether. Scientific data would be collected throughout the operation, after which the satellite would be reeled back in. Pre-flight testing system level tests involved setting up a tether receiver to catch the 12.5 mile tether onto another reel as it was being unwound by the deployer reel mechanism. Testing only the reel mechanism is straightforward. This test becomes more complicated when the TSS is mounted on the flight pallet at Kennedy Space Center (KSC). The system level tests must be passed before the pallet can be installed into the Space Shuttle cargo bay. A few months before flight, the TSS payload had been integrated onto the Spacelab pallet and system level tests, including unreeling and reeling the tether, had been successfully completed. Some of this testing equipment was then shipped back to the contractor Martin Marietta. Systems-level load analyses, which cannot be run until all information about each payload is finalized, was run in parallel with the physical integration of the hardware into the Shuttle payload bay. The coupled loads analysis, as it is called, incorporates any updates to the model due to system level tests, and any changes that were found during integration. The coupled loads analysis revealed that a single bolt attaching the deployer reel mechanism to the support structure had a "negative margin" - which is an indication that it might fail during operation. Hardware certification rules do not allow for hardware to fly with negative margins, so this issue had to be resolved before the flight. Since there is conservatism in engineering analysis, there is an option to "waive" the margin requirement, and fly the experiment as is. On the other hand, a structural failure of one payload could have serious or catastrophic consequences to other payloads and possibly the mission. Minor design changes or fixes might be feasible within the payload bay prior to launch. Any major design changes that required the spooling test to validate the hardware, or for the pallet to be removed, would cause TSS not to be ready for the Shuttle launch.

O'Connor, Brian↗

Integrated Application of Active Controls (IAAC) technology to an advanced subsonic transport project: Test act system validation

The primary objective of the Test Active Control Technology (ACT) System laboratory tests was to verify and validate the system concept, hardware, and software. The initial lab tests were open loop hardware tests of the Test ACT System as designed and built. During the course of the testing, minor problems were uncovered and corrected. Major software tests were run. The initial software testing was also open loop. These tests examined pitch control laws, wing load alleviation, signal selection/fault detection (SSFD), and output management. The Test ACT System was modified to interface with the direct drive valve (DDV) modules. The initial testing identified problem areas with DDV nonlinearities, valve friction induced limit cycling, DDV control loop instability, and channel command mismatch. The other DDV issue investigated was the ability to detect and isolate failures. Some simple schemes for failure detection were tested but were not completely satisfactory. The Test ACT System architecture continues to appear promising for ACT/FBW applications in systems that must be immune to worst case generic digital faults, and be able to tolerate two sequential nongeneric faults with no reduction in performance. The challenge in such an implementation would be to keep the analog element sufficiently simple to achieve the necessary reliability.

Source record↗

HST battery test expert systems

During the testing of nickel-cadmium and nickel-hydrogen batteries for the Hubble Space Telescope, an urgent need for data management was recognized. Testing of these batteries generates much needed data that is used for vital decision making, such as when to recondition, change the charging scheme, or adjust the workload of the batteries. To solve this problem, an expert system called NICBES was developed. NICBES can recognize a testbed anomaly, identify the malfunctioning component, recommend a course of action, evaluate battery status, and provide decision support. A description of NICBES and some of its enhancements are given.

Johnson, Yvette B.↗

Flight control system design factors for applying automated testing techniques

The principal design features and operational experiences of the X-29 forward-swept-wing aircraft and F-18 high alpha research vehicle (HARV) automated test systems are discussed. It is noted that operational experiences in developing and using these automated testing techniques have highlighted the need for incorporating target system features to improve testability. Improved target system testability can be accomplished with the addition of nonreal-time and real-time features. Online access to target system implementation details, unobtrusive real-time access to internal user-selectable variables, and proper software instrumentation are all desirable features of the target system. Also, test system and target system design issues must be addressed during the early stages of the target system development. Processing speeds of up to 20 million instructions/s and the development of high-bandwidth reflective memory systems have improved the ability to integrate the target system and test system for the application of automated testing techniques. It is concluded that new methods of designing testability into the target systems are required.

Sitz, Joel R.↗

Wear Test of the 12.5-kW Advanced Electric Propulsion System Engineering Test Unit Hall Thruster

This work presents a summary of the first wear test of the 12.5 kW Advanced Electric Propulsion System Engineering Test Unit 2 (AEPS ETU-2) thruster produced by Aerojet Rocketdyne. The ETU-2 Wear Test accumulated approximately 730 hours of operation split between the nominal 600 V/12.5 kW condition and the 300 V/6.25 kW condition previously identified as the worst-case erosion condition.

Jason D. Frieman↗

Launch Control System Software Development System Automation Testing

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This system requires high quality testing that will measure and test the capabilities of the system. For the past two years, the Exploration and Operations Division at Kennedy Space Center (KSC) has assigned a group including interns and full-time engineers to develop automated tests to save the project time and money. The team worked on automating the testing process for the SCCS GUI that would use streamed simulated data from the testing servers to produce data, plots, statuses, etc. to the GUI. The software used to develop automated tests included an automated testing framework and an automation library. The automated testing framework has a tabular-style syntax, which means the functionality of a line of code must have the appropriate number of tabs for the line to function as intended. The header section contains either paths to custom resources or the names of libraries being used. The automation library contains functionality to automate anything that appears on a desired screen with the use of image recognition software to detect and control GUI components. The data section contains any data values strictly created for the current testing file. The body section holds the tests that are being run. The function section can include any number of functions that may be used by the current testing file or any other file that resources it. The resources and body section are required for all test files; the data and function sections can be left empty if the data values and functions being used are from a resourced library or another file. To help equip the automation team with better tools, the Project Lead of the Automated Testing Team, Jason Kapusta, assigned the task to install and train an optical character recognition (OCR) tool to Brandon Echols, a fellow intern, and I. The purpose of the OCR tool is to analyze an image and find the coordinates of any group of text. Some issues that arose while installing the OCR tool included the absence of certain libraries needed to train the tool and an outdated software version. We eventually resolved the issues and successfully installed the OCR tool. Training the tool required many images and different fonts and sizes, but in the end the tool learned to accurately decipher the text in the images and their coordinates. The OCR tool produced a file that contained significant metadata for each section of text, but only the text and coordinates of the text was required for our purpose. The team made a script to parse the information we wanted from the OCR file to a different file that would be used by automation functions within the automated framework. Since a majority of development and testing for the automated test cases for the GUI in question has been done using live simulated data on the workstations at the Launch Control Center (LCC), a large amount of progress has been made. As of this writing, about 60% of all of automated testing has been implemented. Additionally, the OCR tool will help make our automated tests more robust due to the tool's text recognition being highly scalable to different text fonts and text sizes. Soon we will have the whole test system automated, allowing for more full-time engineers working on development projects.

Automation↗

Propulsion system ground testing

The objective is to provide management visibility relative to the roles of simulation and propulsion system testing for future development programs through assessment of current propulsion related simulation capabilities and review of contributions from propulsion system test programs. The presentation is represented by viewgraphs.

Wood, Charles C.↗