Search NASA⌕ Search

SEARCH · Search NASA

Results for “ARENA Test Bed”

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.

5 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1992

CONE - An STS-based cryogenic fluid management experiment

An overview of the CONE program is presented which includes a definition of the technology addressed by CONE and a baseline experiment set, a description of the experimental and support subsystems, interface requirements between the STS and the experiment carrier (Hitchhiker M), and the reusability and expansion capacity for additional experiment flights. CONE evaluates three primary technologies: the active thermodynamic vent system, the passive thermodynamic vent system, and liquid acquisition device performance. The cryogenic fluid management technology database that the system offers will allow for efficient subcritical cryogenic system designs for operation in a low-gravity environment. This system maximizes the balance between existing component technology and the need for the development of a cryogenic-fluid-management (CFM) test bed to investigate and demonstrate methods of storage and handling arenas.

Bell, R. S.↗
NASA NTRS1993

Stanford Aerospace Research Laboratory research overview

Over the last ten years, the Stanford Aerospace Robotics Laboratory (ARL) has developed a hardware facility in which a number of space robotics issues have been, and continue to be, addressed. This paper reviews two of the current ARL research areas: navigation and control of free flying space robots, and modelling and control of extremely flexible space structures. The ARL has designed and built several semi-autonomous free-flying robots that perform numerous tasks in a zero-gravity, drag-free, two-dimensional environment. It is envisioned that future generations of these robots will be part of a human-robot team, in which the robots will operate under the task-level commands of astronauts. To make this possible, the ARL has developed a graphical user interface (GUI) with an intuitive object-level motion-direction capability. Using this interface, the ARL has demonstrated autonomous navigation, intercept and capture of moving and spinning objects, object transport, multiple-robot cooperative manipulation, and simple assemblies from both free-flying and fixed bases. The ARL has also built a number of experimental test beds on which the modelling and control of flexible manipulators has been studied. Early ARL experiments in this arena demonstrated for the first time the capability to control the end-point position of both single-link and multi-link flexible manipulators using end-point sensing. Building on these accomplishments, the ARL has been able to control payloads with unknown dynamics at the end of a flexible manipulator, and to achieve high-performance control of a multi-link flexible manipulator.

Ballhaus, W. L.↗
NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George↗
NASA NTRS2014

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto-Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner- TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders

Plattsmier, George I.↗
NASA NTRS1993

Space Shuttle main engine OPAD: The search for a hardware enhanced plume

The process of applying spectroscopy to the Space Shuttle Main Engine (SSME) for plume diagnostics, as it exists today, originated at Marshall Space Flight Center in Huntsville, Alabama, and its implementation was assured largely through the efforts of Sverdrup AEDC, in Tullahoma, Tennessee. This team continues to lead and guide efforts in the plume diagnostics arena. The process, Optical Plume Anomaly Detection (OPAD), formed the basis for various activities in the development of ground-based systems as well as the development of in-flight plume spectroscopy. OPAD currently provides and will continue to provide valuable information relative to future systems definitions, instrumentation development, code validation, and data diagnostic processing. OPAD is based on the detection of anomalous atomic and molecular species in the SSME plume using two complete, stand-alone optical spectrometers. To-date OPAD has acquired data on 44 test firings of the SSME at the Technology Test Bed (TTB) at MSFC. The purpose of this paper will be to provide an introduction to the OPAD system by discussing the process of obtaining data as well as the methods of examining and interpreting the data. It will encompass such issues as selection of instrumentation correlation of data to nominal engine operation, investigation of SSME component erosion via OPAD spectral data, necessity and benefits of plume seeding, application of artificial intelligence (AI) techniques to data analysis, and the present status of efforts to quantify specie erosion utilizing standard plume and chemistry codes as well as radiative models currently under development.

Powers, W. T.↗