Search NASA⌕ Search

SEARCH · Search NASA

Results for “prototyped verification system”

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 145 records · Page 8

System Design Package for SIMS Prototype System 3, Solar Heating and Domestic Hot Water

A collation of documents and drawings are presented that describe a prototype solar heating and hot water system using liquid flat plate collectors and a gas or electric furnace energy subsystem. The system was designed for installation into a single-family dwelling. The description, performance specification, subsystem drawings, verification plan/procedure, and hazard analysis of the system are packaged for evaluation of the system with information sufficient to assemble a similar system.

Source record↗

Task Analysis Technologies at KSC

Project objective: (1) Form an integrated team of NASA. USA, Boeing, and Dynacs researches. (2) Create a user friendly software prototype that assists an analyst in performing a human factors process failure modes and effects analysis (HF-PFMEA). (3)Perform four task analyses on center: cargo late access task analysis (NASA/Boeing team); payload test and verification system task analysis (NASA/Boeing team); slammer cover installation operations task analysis (NASA/USA team); ATDC LOX pump acceptance test procedure task analysis (NASA/Dynacs team).

Carstens, Deborah S.↗

Design and Verification of a Distributed Communication Protocol

The safety of remotely operated vehicles depends on the correctness of the distributed protocol that facilitates the communication between the vehicle and the operator. A failure in this communication can result in catastrophic loss of the vehicle. To complicate matters, the communication system may be required to satisfy several, possibly conflicting, requirements. The design of protocols is typically an informal process based on successive iterations of a prototype implementation. Yet distributed protocols are notoriously difficult to get correct using such informal techniques. We present a formal specification of the design of a distributed protocol intended for use in a remotely operated vehicle, which is built from the composition of several simpler protocols. We demonstrate proof strategies that allow us to prove properties of each component protocol individually while ensuring that the property is preserved in the composition forming the entire system. Given that designs are likely to evolve as additional requirements emerge, we show how we have automated most of the repetitive proof steps to enable verification of rapidly changing designs.

Munoz, Cesar A.↗

Thermal Management Design for the X-33 Lifting Body

The X-33 Advantage Technology Demonstrator offers a rare and exciting opportunity in Thermal Protection System development. The experimental program incorporates the latest design innovation in re-useable, low life cycle cost, and highly dependable Thermal Protection materials and constructions into both ground based and flight test vehicle validations. The unique attributes of the X-33 demonstrator for design application validation for the full scale Reusable Launch Vehicle, (RLV), are represented by both the configuration of the stand-off aeroshell, and the extreme exposures of sub-orbital hypersonic re-entry simulation. There are several challenges of producing a sub-orbital prototype demonstrator of Single Stage to Orbit/Reusable Launch Vehicle (SSTO/RLV) operations. An aggressive schedule with budgetary constraints precludes the opportunity for an extensive verification and qualification program of vehicle flight hardware. However, taking advantage of off the shelf components with proven technologies reduces some of the requirements for additional testing. The effects of scale on thermal heating rates must also be taken into account during trajectory design and analysis. Described in this document are the unique Thermal Protection System (TPS) design opportunities that are available with the lifting body configuration of the X-33. The two principal objectives for the TPS are to shield the primary airframe structure from excessive thermal loads and to provide an aerodynamic mold line surface. With the relatively benign aeroheating capability of the lifting body, an integrated stand-off aeroshell design with minimal weight and reduced procurement and operational costs is allowed. This paper summarizes the design objectives of the X-33 TPS, the flight test requirements driven configuration, and design benefits. Comparisons are made of the X-33 flight profiles and Space Shuttle Orbiter, and lifting body Reusable Launch Vehicle aerothermal environments. The X-33 TPS is based on a design to cost configuration concept. Only RLV critical technologies are verified to conform to cost and schedule restrictions. The one-off prototype vehicle configuration has evolved to minimize the tooling costs by reducing the number of unique components. Low cost approaches such as a composite/blanket leeward aeroshell and the use of Shuttle technology are implemented where applicable. The success of the X-33 will overcome the ballistic re-entry TPS mindset. The X-33 TPS is tailored to an aircraft type mission while maintaining sufficient operational margins. The flight test program for the X-33 will demonstrate that TPS for the RLV is not simply a surface insulation but rather an integrated aeroshell system.

Bouslog, S.↗

The development of a non-cryogenic nitrogen/oxygen supply system

Development of the hydrazine/water electrolysis process in a manned spacecraft to provide metabolic oxygen and both oxygen and nitrogen for cabin leakage makeup was studied. Electrode development efforts were directed to stability, achieved with catalyst additives and improved processing techniques, and a higher hydrazine conversion efficiency, achieved by reducing catalyst loading on the cathodes. Extensive testing of the one-man breadboard N2/02 system provided complete characterization of cabin atmosphere control aspects. A detailed design of a prototype modular N2/02 unit was conducted. The contact heat exchanger which is an integral component of this design was fabricated and sucessfully design-verification tested.

Greenough, B. M.↗

Making intelligent systems team players. A guide to developing intelligent monitoring systems

This reference guide for developers of intelligent monitoring systems is based on lessons learned by developers of the DEcision Support SYstem (DESSY), an expert system that monitors Space Shuttle telemetry data in real time. DESSY makes inferences about commands, state transitions, and simple failures. It performs failure detection rather than in-depth failure diagnostics. A listing of rules from DESSY and cue cards from DESSY subsystems are included to give the development community a better understanding of the selected model system. The G-2 programming tool used in developing DESSY provides an object-oriented, rule-based environment, but many of the principles in use here can be applied to any type of monitoring intelligent system. The step-by-step instructions and examples given for each stage of development are in G-2, but can be used with other development tools. This guide first defines the authors' concept of real-time monitoring systems, then tells prospective developers how to determine system requirements, how to build the system through a combined design/development process, and how to solve problems involved in working with real-time data. It explains the relationships among operational prototyping, software evolution, and the user interface. It also explains methods of testing, verification, and validation. It includes suggestions for preparing reference documentation and training users.

Land, Sherry A.↗

Independent Verification and Validation of Complex User Interfaces: A Human Factors Approach

The Usability Testing and Analysis Facility (UTAF) at the NASA Johnson Space Center has identified and evaluated a potential automated software interface inspection tool capable of assessing the degree to which space-related critical and high-risk software system user interfaces meet objective human factors standards across each NASA program and project. Testing consisted of two distinct phases. Phase 1 compared analysis times and similarity of results for the automated tool and for human-computer interface (HCI) experts. In Phase 2, HCI experts critiqued the prototype tool's user interface. Based on this evaluation, it appears that a more fully developed version of the tool will be a promising complement to a human factors-oriented independent verification and validation (IV&V) process.

Whitmore, Mihriban↗

Verification and Validation in a Rapid Software Development Process

The high cost of software production is driving development organizations to adopt more automated design and analysis methods such as rapid prototyping, computer-aided software engineering (CASE) tools, and high-level code generators. Even developers of safety-critical software system have adopted many of these new methods while striving to achieve high levels Of quality and reliability. While these new methods may enhance productivity and quality in many cases, we examine some of the risks involved in the use of new methods in safety-critical contexts. We examine a case study involving the use of a CASE tool that automatically generates code from high-level system designs. We show that while high-level testing on the system structure is highly desirable, significant risks exist in the automatically generated code and in re-validating releases of the generated code after subsequent design changes. We identify these risks and suggest process improvements that retain the advantages of rapid, automated development methods within the quality and reliability contexts of safety-critical projects.

Callahan, John R.↗

Emulation of Core Flight System Applications for Flight Software Development and Validation

The Mars Sample Return (MSR) campaign is an unprecedented attempt in the return of Martian samples back to Earth. The ascent from the surface will be performed by the Mars Ascent Vehicle (MAV), a critical element in the mission that National Aeronautics and Space Administration (NASA) Marshall Space Flight Center (MSFC) is developing. To this end, innovations in flight software development, verification, and validation are occurring. The MAV flight computer will run Core Flight System (cFS), an open-source software environment developed by NASA Goddard Space Flight Center (GSFC). NASA Marshall’s MAV Mission and Fault Management (M&FM) Team has implemented an emulation of two applications of this architecture: Limit Checker and Stored Command. Using an emulation of the functionalities of these applications allows for rapid prototyping of table-based algorithms. Further, M&FM is leveraging an in-house, low-fidelity but high-throughput State Analysis Model (SAM), an integrated MATLAB Stateflow Plant and Software model. This model is run in parallel with the cFS emulation for full flyout testing of the M&FM algorithms, verification of intent of these algorithms, and for future auto-generation of application-ingestible M&FM tables. The tables can then be delivered to the MAV Flight Software (FSW) team in a seamless process, reducing the cost of traditional FSW development and the risk of starting M&FM FSW development at later points in the NASA program life cycle.

Cody Wheeler↗

Emulation of Core Flight System Applications for Flight Software Development and Validation

The Mars Sample Return (MSR) campaign is an unprecedented attempt in the return of Martian samples back to Earth. The ascent from the surface will be performed by the Mars Ascent Vehicle (MAV), a critical element in the mission that National Aeronautics and Space Administration (NASA) Marshall Space Flight Center (MSFC) is developing. To this end, innovations in flight software development, verification, and validation are occurring. The MAV flight computer will run Core Flight System (cFS), an open-source software environment developed by NASA Goddard Space Flight Center (GSFC). NASA Marshall’s MAV Mission and Fault Management (M&FM) Team has implemented an emulation of two applications of this architecture: Limit Checker and Stored Command. Using an emulation of the functionalities of these applications allows for rapid prototyping of table-based algorithms. Further, M&FM is leveraging an in-house, low-fidelity but high-throughput State Analysis Model (SAM), an integrated MATLAB Stateflow Plant and Software model. This model is run in parallel with the cFS emulation for full flyout testing of the M&FM algorithms, verification of intent of these algorithms, and for future auto-generation of application-ingestible M&FM tables. The tables can then be delivered to the MAV Flight Software (FSW) team in a seamless process, reducing the cost of traditional FSW development and the risk of starting M&FM FSW development at later points in the NASA program life cycle.

Cody Wheeler↗

Ground-based implementation and verification of control laws for tethered satellites

Davis and Banerjee (1990) have developed a tethered-spacecraft system model in which out-of-plane librations are damped, using a length-rate control after the tether has been deployed. Attention is presently given to the implementation of such control schemes to prototype hardware designed for space flight. A prototype reel mechanism has been constructed for use in the Getaway Tether Experiment; both the Davis and Banerjee control scheme and a converted tension-control law have been implemented with tether length and length rate available as feedback.

Gwaltney, David A.↗

Study of plate-fin heat exchanger and cold plate for the active thermal control system of Space Station

Plate-fin heat exchangers will be employed in the Active Thermal Control System of Space Station Freedom. During ground testing of prototypic heat exchangers, certain anomalous behaviors have been observed. Diagnosis has been conducted to determine the cause of the observed behaviors, including a scrutiny of temperature, pressure, and flow rate test data, and verification calculations based on such data and more data collected during the ambient and thermal/vacuum tests participated by the author. The test data of a plate-fin cold plate have been also analyzed. Recommendation was made with regard to further tests providing more useful information of the cold plate performance.

Chyu, MING-C.↗

A microcontroller-based three degree-of-freedom manipulator testbed

A wheeled exploratory vehicle is under construction at the Mars Mission Research Center at North Carolina State University. In order to serve as more than an inspection tool, this vehicle requires the ability to interact with its surroundings. A crane-type manipulator, as well as the necessary control hardware and software, has been developed for use as a sample gathering tool on this vehicle. The system is controlled by a network of four Motorola M68HC11 microcontrollers. Control hardware and software were developed in a modular fashion so that the system can be used to test future control algorithms and hardware. Actuators include three stepper motors and one solenoid. Sensors include three optical encoders and one cable tensiometer. The vehicle supervisor computer provides the manipulator system with the approximate coordinates of the target object. This system maps the workspace surrounding the given location by lowering the claw, along a set of evenly spaced vertical lines, until contact occurs. Based on this measured height information and prior knowledge of the target object size, the system determines if the object exists in the searched area. The system can find and retrieve a 1.25 in. diameter by 1.25 in. tall cylinder placed within the 47.5 sq in search area in less than 12 minutes. This manipulator hardware may be used for future control algorithm verification and serves as a prototype for other manipulator hardware.

Brown, Robert Michael, Jr.↗

Development and marketing of a prosthetic urinary control valve system

An implantable prosthetic for the control of urinary incontinence was developed and marketed. Three phases are presented: bench development studies, animal trials, and human clinical trials. This work was performed under the direction of a Research Team at Rochester General Hospital (RGH). Bench trials were completed on prototype hardware and provided early verification of the device's ability to withstand repeated cyclic testing. Configurational variants were evaluated and a preferred design concept was established. Silicone rubber (medical grade) was selected as the preferred material for the prosthesis.

Tenney, J. B., Jr.↗

Medical Data Architecture Platform and Recommended Requirements for A Medical Data System for Exploration Missions

Minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions.In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗

Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗

Space Shuttle OMS engine valve technology

Valve technology program to determine shutoff valve concepts suitable for the Orbital Maneuvering System (OMS) engine of the Space Shuttle. The tradeoff studies selected the electric torque motor operated dual poppet and ball valves as the most desirable valve concepts for the OMS Engine Shutoff Valve. A prototype of one of these concepts was built and subjected to a design verification program. A number of unique features were designed to include the required contamination insensitivity, operating fluid compatibility, decontamination capability, minimum maintenance requirement and long service life capability.

Wichmann, H.↗

System design package for SIMS prototype system 4, solar heating and domestic hot water

The system consisted of a modular designed prepackaged solar unit, containing solar collectors, a rock storage container, blowers, dampers, ducting, air-to-water heat exchanger, DHW preheat tank, piping, and system controls. The system was designed to be installed adjacent to a small single family dwelling. The description, performance specification, subsystem drawings, verification plan/procedure, and hazard analysis of the system were packaged for evaluation.

Source record↗