Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “System 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 1,063 records · Page 59
All sourcesNASA NTRSDOE OSTI
NASA NTRS1992

SITE project. Phase 1: Continuous data bit-error-rate testing

The Systems Integration, Test, and Evaluation (SITE) Project at NASA LeRC encompasses a number of research and technology areas of satellite communications systems. Phase 1 of this project established a complete satellite link simulator system. The evaluation of proof-of-concept microwave devices, radiofrequency (RF) and bit-error-rate (BER) testing of hardware, testing of remote airlinks, and other tests were performed as part of this first testing phase. This final report covers the test results produced in phase 1 of the SITE Project. The data presented include 20-GHz high-power-amplifier testing, 30-GHz low-noise-receiver testing, amplitude equalization, transponder baseline testing, switch matrix tests, and continuous-wave and modulated interference tests. The report also presents the methods used to measure the RF and BER performance of the complete system. Correlations of the RF and BER data are summarized to note the effects of the RF responses on the BER.

Fujikawa, Gene↗
NASA NTRS1994

Basic principles of flight test instrumentation engineering, volume 1, issue 2

Volume 1 of the AG 300 series on ´Flight Test Instrumentation´ gives a general introduction to the basic principles of flight test instrumentation. The other volumes in the series provide more detailed treatments of selected topics on flight test instrumentation. Volume 1, first published in 1974, has been used extensively as an introduction for instrumentation courses and symposia, as well as being a reference work on the desk of most flight test and instrumentation engineers. It is hoped that this second edition, fully revised, will be used with as much enthusiasm as the first edition. In this edition a flight test system is considered to include both the data collection and data processing systems. In order to obtain an optimal data flow, the overall design of these two subsystems must be carefully matched; the detail development and the operation may have to be done by separate groups of specialists. The main emphasis is on the large automated instrumentation systems used for the initial flight testing of modern military and civil aircraft. This is done because there, many of the problems, which are discussed here, are more critical. It does not imply, however, that smaller systems with manual data processing are no longer used. In general, the systems should be designed to provide the required results at the lowest possible cost. For many tests which require only a few parameters, relatively simple systems are justified, especially if no complex equipment is available to the user. Although many of the aspects discussed in this volume apply to both small and large systems, aspects of the smaller systems are mentioned only when they are of special interest. The volume has been divided into three main parts. Part 1 defines the main starting points for the design of a flight test instrumentation system, as seen from the points of view of the flight test engineer and the instrumentation engineer. In Part 2 the discussion is concentrated on those aspects which apply to each individual measuring channel, and in Part 3 the main emphasis is on the integration of the individual data channels into one data collection system and on those aspects of the data processing which apply to the complete system.

channels (data transmission)↗
NASA NTRS2006

Crew Launch Vehicle (CLV) Avionics and Software Integration Overview

On January 14, 2004, the President of the United States announced a new plan to explore space and extend a human presence across our solar system. The National Aeronautics and Space Administration (NASA) established the Exploration Systems Mission Directorate (ESMD) to develop and field a Constellation Architecture that will bring the Space Exploration vision to fruition. The Constellation Architecture includes a human-rated Crew Launch Vehicle (CLV) segment, managed by the Marshall Space Flight Center (MSFC), comprised of the First Stage (FS), Upper Stage (US), and Upper Stage Engine (USE) elements. The CLV s purpose is to provide safe and reliable crew and cargo transportation into Low Earth Orbit (LEO), as well as insertion into trans-lunar trajectories. The architecture's Spacecraft segment includes, among other elements, the Crew Exploration Vehicle (CEV), managed by the Johnson Space Flight Center (JSC), which is launched atop the CLV. MSFC is also responsible for CLV and CEV stack integration. This paper provides an overview of the Avionics and Software integration approach (which includes the Integrated System Health Management (ISHM) functions), both within the CLV, and across the CEV interface; it addresses the requirements to be met, logistics of meeting those requirements, and the roles of the various groups. The Avionics Integration and Vehicle Systems Test (ANST) Office was established at the MSFC with system engineering responsibilities for defining and developing the integrated CLV Avionics and Software system. The AIVST Office has defined two Groups, the Avionics and Software Integration Group (AVSIG), and the Integrated System Simulation and Test Integration Group (ISSTIG), and four Panels which will direct trade studies and analyses to ensure the CLV avionics and software meet CLV system and CEV interface requirements. The four panels are: 1) Avionics Integration Panel (AIP), 2) Software Integration Panel, 3) EEE Panel, and 4) Systems Simulation and Test Panel. Membership on the groups and panels includes the MSFC representatives from the requisite engineering disciplines, the First Stage, the Upper Stage, the Upper Stage Engine projects, and key personnel from other NASA centers. The four panels will take the results of trade studies and analyses and develop documentation in support of Design Analysis Cycle Reviews and ultimately the System Requirements Review.

Monell, Donald W.↗
NASA NTRS1992

Cryogenic leak testing of tube fittings/valves

A high pressure and variable temperature cryogenic leak testing system was conceived and designed in order to conduct leakage testing of pipe fittings/valves in liquid hydrogen supply lines of the Space Shuttle. The system can create a continuous testing environment of variable temperature, 5.5 to about 300 K, and variable pressure, 0.01 to about 70 x 10 exp 5 Pa, with a large sample space, 90 mm diameter x 228 mm length, and at low operating cost. In terms of cryogenic leak testing the system has a special capability for extensive applications. The system comprised a variable temperature cryostat, a high pressure sample chamber, a vacuum pumping station, gas flow control system, pressure and temperature control systems, and leak detecting and measuring systems. A general discussion of cryogenic leak testing methods is also presented.

Jia, L. X.↗
DOE OSTI2021

JLAB LLRF 3.0 Development and Tests

The Jefferson Lab LLRF 3.0 system is being developed to replace legacy LLRF systems in the CEBAF accelerator. The new design builds upon 25 years of design and operational RF control experience, and our recent collaboration in the design of the LCLSII LLRF system. The new cavity control algorithm is a fully functional phase and amplitude locked Self Exciting Loop (SEL). This paper discusses the progress of the LLRF 3.0 hardware design, FPGA firmware development, User Datagram Protocol (UDP) operation, and recent LLRF 3.0 system tests on the CEBAF Booster cryomodule in the Upgrade Injector Test Facility (UITF).

Plawski, T. E.↗
NASA NTRS1988

A flexible telemetry processor for spacecraft testing

In the past, telemetry data systems in support of JPL flight projects were designed specifically for each mission. The Magellan System Test Data Processing Subsystem (STDPS) marks a departure from these past designs. For the first time, a reusable telemetry-processing subsystem has been designed that is flexible enough to meet the spacecraft-testing requirements of the present project, and can be easily changed for future projects as well. These changes are all accomplished through a user-friendly, menu-oriented interface. Extensive software reprogramming is no longer required.

Leng, Christopher↗
NASA NTRS1975

Urine sampling and collection system optimization and testing

A Urine Sampling and Collection System (USCS) engineering model was developed to provide for the automatic collection, volume sensing and sampling of urine from each micturition. The purpose of the engineering model was to demonstrate verification of the system concept. The objective of the optimization and testing program was to update the engineering model, to provide additional performance features and to conduct system testing to determine operational problems. Optimization tasks were defined as modifications to minimize system fluid residual and addition of thermoelectric cooling.

Fogal, G. L.↗
NASA NTRS1983

Testing and error analysis of a real-time controller

Inexpensive ways to organize and conduct system testing that were used on a real-time satellite network control system are outlined. This system contains roughly 50,000 lines of executable source code developed by a team of eight people. For a small investment of staff, the system was thoroughly tested, including automated regression testing, before field release. Detailed records were kept for fourteen months, during which several versions of the system were written. A separate testing group was not established, but testing itself was structured apart from the development process. The errors found during testing are examined by frequency per subsystem by size and complexity as well as by type. The code was released to the user in March, 1983. To date, only a few minor problems found with the system during its pre-service testing and user acceptance has been good.

Savolaine, C. G.↗
NASA NTRS2022

Simulating Mars: Enabling Testing of the Perseverance Rover Sampling and Caching Subsystem on Earth

The development of the Sampling and Caching Subsystem (SCS) on the JPL Perseverance Rover lies at the intersection of testing, robotics, and geology. The SCS team established three primary system test campaigns and venues to aid in the development of SCS through verification and validation testing – Qualification Model Dirty Testing (QMDT) to provide a venue for testing in a Martian environment, Vehicle System Testbed (VSTB) for testing while integrated with the mobility subsystem on Martian-like terrain, and the Flight Software Testbed (FSWTB) for conducting tests using the flight motor controllers and software system on a hexapod which had the ability to simulate rover tilt. Each venue contributed a vital piece to the SCS building blocks. However, the QMDT venue operating within a 10-ft diameter Thermal Vacuum chamber to simulate Martian environment provided a sui generis opportunity to fine tune the entire sampling and caching process while building the team’s knowledge base about rock drillability, system life, and target selection. On Earth, because Martian rocks are not readily available, the development team must utilize geoanalogs to the rocks and regolith on Mars. Geologists on the team helped establish a set of standard rock types to use for Mars missions, like Basalt, Sandstone, Mudstone, Gypsum, and other related geoanalogs. These geoanalogs are characterized with a standard suite of tests for density, compressibility, and other characteristics to categorize potential drillability. This concept of drillability is what links the geoanalogs on Earth to the samples we collect on Mars. With the simulant characteristics defined, these geoanalog rocks are ready to be drilled into as we do on the Martian surface. A key aspect of interacting with the surface on Mars is rock target identification and selection. The Perseverance robotic system uses the on-board cameras, instrumentation, and software to collect enough information to identify potential scientific targets. With the targets identified, SCS can place the Corer and abrade the surface or collect a sample. For a ground test activity like QMDT, the test team did not have all of the camera and instrumentation systems that the rover does, so the team developed ground test equivalents to process a rock, build a target map, and define the target. The team constructed a Rock Scanning Station to build a 3D point cloud of the rock. This point cloud was then processed and evaluated with predefined and programmed criteria in a Target Downselect Tool. A primary output of the Target Downselect Tool is a defined target that can be uploaded directly to the robotic software system to simulate and build the robotic sequences used in tests. With these insights and programmatic definition of targets, the QMDT test team was able to make the same decisions that the Perseverance surface operations team does. In addition, valuable lessons learned from developing the target selection ground tools and using them were implemented into the tools used for surface operations.

Kim, Junggon↗
NASA NTRS1975

Holographic system for nondestructive testing

A description is given of a holographic system for nondestructive testing. The system is comprised of a mirror which illuminates the test object surface; the mirror is positionable to direct illumination on an object at varying angles with respect to a line normal to the surface of the object. In this manner holograms may be produced with varying degrees of sensitivity enabling optimum observation of dimensions of deformation of an object occurring between test exposures.

Kurtz, R. L.↗
NASA NTRS2019

Orion Capsule Parachute Assembly System (CPAS) Overload Testing Approach and Results

The qualification of the Orion Capsule Parachute Assembly System (CPAS) system includes exposure to loads and dynamic pressures above the required values as validation of the parachutes' structural integrity. As outlined in the certification plan, each of the four parachutes of the system are to be subjected to 110% of their respective maximum dynamic pressure requirements. The Main and Drogue parachutes have satisfied this overload condition in drop testing and due to cost and schedule constraints, the Forward Bay Cover Parachute (FBCP) and Pilot parachute were subjected to the overload condition in the ground testing described in this document. The test objectives and pass/fail criteria were established and require the parachutes to achieve and maintain a target riser load (associated with a minimum of 110% dynamic pressure overload) for a minimum of three seconds while sustaining no failures of any structural members (vent hoop, radials, suspension line) or any damage which propagates into catastrophic failure of the canopy. Considering the assumptions and limitations associated with the ground testing (primarily non-uniform flow field of the ground test system and variations in parachute manufacturing), a method of establishing the desired overload condition was determined by the technical community and covers the 2-sigma bounds of the drag area distribution derived from drop testing. On June 27, 2017 the testing was executed at the High Velocity Airflow System (HiVAS) facility located at the Weapon Survivability Laboratory (WSL) at the Naval Air Warfare Center, Weapons Division (NAWCWD) China Lake. Engineering Development Unit (EDU) parachutes were used as pathfinders to gain experience with achieving the test conditions. Additional runs were executed to measure the airflow at the same location as the canopy skirt, although this data is not required to satisfy the test objectives and parachute pass/fail criteria. The qualification parachutes were successfully exposed to the target conditions and sustained only minor damage.

Daum, Jared S.↗
NASA NTRS2008

Integrated Testing Approaches for the NASA Ares I Crew Launch Vehicle

The Ares I crew launch vehicle is being developed by the U.S. National Aeronautics and Space Administration (NASA) to provide crew and cargo access to the International Space Station (ISS) and, together with the Ares V cargo launch vehicle, serves as a critical component of NASA's future human exploration of the Moon. During the preliminary design phase, NASA defined and began implementing plans for integrated ground and flight testing necessary to achieve the first human launch of Ares I. The individual Ares I flight hardware elements - including the first stage five segment booster (FSB), upper stage, and J-2X upper stage engine - will undergo extensive development, qualification, and certification testing prior to flight. Key integrated system tests include the upper stage Main Propulsion Test Article (MPTA), acceptance tests of the integrated upper stage and upper stage engine assembly, a full-scale integrated vehicle ground vibration test (IVGVT), aerodynamic testing to characterize vehicle performance, and integrated testing of the avionics and software components. The Ares I-X development flight test will provide flight data to validate engineering models for aerodynamic performance, stage separation, structural dynamic performance, and control system functionality. The Ares I-Y flight test will validate ascent performance of the first stage, stage separation functionality, validate the ability of the upper stage to manage cryogenic propellants to achieve upper stage engine start conditions, and a high-altitude demonstration of the launch abort system (LAS) following stage separation. The Orion 1 flight test will be conducted as a full, un-crewed, operational flight test through the entire ascent flight profile prior to the first crewed launch.

Taylor, James L.↗
NASA NTRS2010

Monitoring System for Storm Readiness and Recovery of Test Facilities: Integrated System Health Management (ISHM) Approach

Severe weather events are likely occurrences on the Mississippi Gulf Coast. It is important to rapidly diagnose and mitigate the effects of storms on Stennis Space Center's rocket engine test complex to avoid delays to critical test article programs, reduce costs, and maintain safety. An Integrated Systems Health Management (ISHM) approach and technologies are employed to integrate environmental (weather) monitoring, structural modeling, and the suite of available facility instrumentation to provide information for readiness before storms, rapid initial damage assessment to guide mitigation planning, and then support on-going assurance as repairs are effected and finally support recertification. The system is denominated Katrina Storm Monitoring System (KStorMS). Integrated Systems Health Management (ISHM) describes a comprehensive set of capabilities that provide insight into the behavior the health of a system. Knowing the status of a system allows decision makers to effectively plan and execute their mission. For example, early insight into component degradation and impending failures provides more time to develop work around strategies and more effectively plan for maintenance. Failures of system elements generally occur over time. Information extracted from sensor data, combined with system-wide knowledge bases and methods for information extraction and fusion, inference, and decision making, can be used to detect incipient failures. If failures do occur, it is critical to detect and isolate them, and suggest an appropriate course of action. ISHM enables determining the condition (health) of every element in a complex system-of-systems or SoS (detect anomalies, diagnose causes, predict future anomalies), and provide data, information, and knowledge (DIaK) to control systems for safe and effective operation. ISHM capability is achieved by using a wide range of technologies that enable anomaly detection, diagnostics, prognostics, and advise for control: (1) anomaly detection algorithms and strategies, (2) fusion of DIaK for anomaly detection (model-based, numerical, statistical, empirical, expert-based, qualitative, etc.), (3) diagnostics/prognostics strategies and methods, (4) user interface, (5) advanced control strategies, (6) integration architectures/frameworks, (7) embedding of intelligence. Many of these technologies are mature, and they are being used in the KStorMS. The paper will describe the design, implementation, and operation of the KStorMS; and discuss further evolution to support other needs such as condition-based maintenance (CBM).

Figueroa, Fernando↗
NASA NTRS1987

Portable Test And Monitoring System For Wind-Tunnel Models

Portable system developed to test and monitor instrumentation used in wind-tunnel models. Self-contained and moves easily to model, either before or after model installed in wind tunnel. System is 44 1/2 in. high, 22 in. wide, and 17 in. deep and weighs 100 lb. Primary benefits realized with portable test and monitoring system associated with saving of time.

Poupard, Charles A.↗
NASA NTRS2005

A Tool for Requirements-Based Programming

Absent a general method for mathematically sound, automated transformation of customer requirements into a formal model of the desired system, developers must resort to either manual application of formal methods or to system testing (either manual or automated). While formal methods have afforded numerous successes, they present serious issues, e.g., costs to gear up to apply them (time, expensive staff), and scalability and reproducibility when standards in the field are not settled. The testing path cannot be walked to the ultimate goal, because exhaustive testing is infeasible for all but trivial systems. So system verification remains problematic. System or requirements validation is similarly problematic. The alternatives available today depend on either having a formal model or pursuing enough testing to enable the customer to be certain that system behavior meets requirements. The testing alternative for non-trivial systems always have some system behaviors unconfirmed and therefore is not the answer. To ensure that a formal model is equivalent to the customer s requirements necessitates that the customer somehow fully understands the formal model, which is not realistic. The predominant view that provably correct system development depends on having a formal model of the system leads to a desire for a mathematically sound method to automate the transformation of customer requirements into a formal model. Such a method, an augmentation of requirements-based programming, will be briefly described in this paper, and a prototype tool to support it will be described. The method and tool enable both requirements validation and system verification for the class of systems whose behavior can be described as scenarios. An application of the tool to a prototype automated ground control system for NASA mission is presented.

Rash, James L.↗
NASA NTRS1996

Forced response testing of an axi-centrifugal turboshaft engine

Dynamic data from tests of a T55-L-712 engine are presented. Engine stall/surge data were analyzed using digital signal processing techniques. In addition, forced response testing (system identification studies) was done at various engine speeds. Forced response testing was done using eight jet ejectors approximately equally circumferentially spaced about the compressor front face. This paper presents some preliminary results for the ground idle (approximately 60% of design speed) point. Brief descriptions of the jet injection system, the test matrix, and analysis techniques used are presented. Results of these analyses indicate a substantial transfer of energy across the compressor first stage at some frequencies and that the ejectors are effective in modifying the local flow conditions in front of the first compressor stage.

Owen, A. Karl↗
NASA NTRS1996

Forced Response Testing of an Axi-Centrifugal Turboshaft Engine

Dynamic data from tests of a T55-L,712 engine are presented. Engine stall/surge data were analyzed using digital signal processing techniques. In addition, forced response testing (system identification studies) was done at various engine speeds. Forced response testing was done using eight jet ejectors approximately equally circumferentially spaced about the compressor front face. This paper presents some preliminary results for the ground idle (approximately 60% of design speed) point. Brief descriptions of the jet injection system, the test matrix, and analysis techniques used are presented. Results of these analyses indicate a substantial transfer of energy across the compressor first stage at some frequencies and that the ejectors are effective in modifying the local flow conditions in front of the first compressor stage.

Owen, A. Karl↗