Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Design verification”

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,135 records · Page 63
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Depth Dose Distribution Study within a Phantom Torso after Irradiation with a Simulated Solar Particle Event at NSRL

The adequate knowledge of the radiation environment and the doses incurred during a space mission is essential for estimating an astronaut's health risk. The space radiation environment is complex and variable, and exposures inside the spacecraft and the astronaut's body are compounded by the interactions of the primary particles with the atoms of the structural materials and with the body itself Astronauts' radiation exposures are measured by means of personal dosimetry, but there remains substantial uncertainty associated with the computational extrapolation of skin dose to organ dose, which can lead to over- or underestimation of the health risk. Comparisons of models to data showed that the astronaut's Effective dose (E) can be predicted to within about a +10% accuracy using space radiation transport models for galactic cosmic rays (GCR) and trapped radiation behind shielding. However for solar particle event (SPE) with steep energy spectra and for extra-vehicular activities on the surface of the moon where only tissue shielding is present, transport models predict that there are large differences in model assumptions in projecting organ doses. Therefore experimental verification of SPE induced organ doses may be crucial for the design of lunar missions. In the research experiment "Depth dose distribution study within a phantom torso" at the NASA Space Radiation Laboratory (NSRL) at BNL, Brookhaven, USA the large 1972 SPE spectrum was simulated using seven different proton energies from 50 up to 450 MeV. A phantom torso constructed of natural bones and realistic distributions of human tissue equivalent materials, which is comparable to the torso of the MATROSHKA phantom currently on the ISS, was equipped with a comprehensive set of thermoluminescence detectors and human cells. The detectors are applied to assess the depth dose distribution and radiation transport codes (e.g. GEANT4) are used to assess the radiation field and interactions of the radiation field with the phantom torso. Lymphocyte cells are strategically embedded at selected locations at the skin and internal organs and are processed after irradiation to assess the effects of shielding on the yield of chromosome damage. The initial focus of the present experiment is to correlate biological results with physical dosimetry measurements in the phantom torso. Further on, the results of the passive dosimetry within the anthropomorphic phantoms represent the best tool to generate reliable data to benchmark computational radiation transport models in a radiation field of interest. The presentation will give first results of the physical dose distribution, the comparison with GEANT4 computer simulations based on a Voxel model of the phantom, and a comparison with the data from the chromosome aberration study.

Berger, Thomas↗
NASA NTRS2010

Distributed Observer Network

The Distributed Observer network (DON) is a NASA-collaborative environment that leverages game technology to bring three-dimensional simulations to conventional desktop and laptop computers in order to allow teams of engineers working on design and operations, either individually or in groups, to view and collaborate on 3D representations of data generated by authoritative tools such as Delmia Envision, Pro/Engineer, or Maya. The DON takes models and telemetry from these sources and, using commercial game engine technology, displays the simulation results in a 3D visual environment. DON has been designed to enhance accessibility and user ability to observe and analyze visual simulations in real time. A variety of NASA mission segment simulations [Synergistic Engineering Environment (SEE) data, NASA Enterprise Visualization Analysis (NEVA) ground processing simulations, the DSS simulation for lunar operations, and the Johnson Space Center (JSC) TRICK tool for guidance, navigation, and control analysis] were experimented with. Desired functionalities, [i.e. Tivo-like functions, the capability to communicate textually or via Voice-over-Internet Protocol (VoIP) among team members, and the ability to write and save notes to be accessed later] were targeted. The resulting DON application was slated for early 2008 release to support simulation use for the Constellation Program and its teams. Those using the DON connect through a client that runs on their PC or Mac. This enables them to observe and analyze the simulation data as their schedule allows, and to review it as frequently as desired. DON team members can move freely within the virtual world. Preset camera points can be established, enabling team members to jump to specific views. This improves opportunities for shared analysis of options, design reviews, tests, operations, training, and evaluations, and improves prospects for verification of requirements, issues, and approaches among dispersed teams.

Conroy, Michael↗
NASA NTRS2012

Integrated Formal Analysis of Timed-Triggered Ethernet

We present new results related to the verification of the Timed-Triggered Ethernet (TTE) clock synchronization protocol. This work extends previous verification of TTE based on model checking. We identify a suboptimal design choice in a compression function used in clock synchronization, and propose an improvement. We compare the original design and the improved definition using the SAL model checker.

Dutertre, Bruno↗
NASA NTRS2011

Telemetry and Science Data Software System

The Telemetry and Science Data Software System (TSDSS) was designed to validate the operational health of a spacecraft, ease test verification, assist in debugging system anomalies, and provide trending data and advanced science analysis. In doing so, the system parses, processes, and organizes raw data from the Aquarius instrument both on the ground and while in space. In addition, it provides a user-friendly telemetry viewer, and an instant pushbutton test report generator. Existing ground data systems can parse and provide simple data processing, but have limitations in advanced science analysis and instant report generation. The TSDSS functions as an offline data analysis system during I&T (integration and test) and mission operations phases. After raw data are downloaded from an instrument, TSDSS ingests the data files, parses, converts telemetry to engineering units, and applies advanced algorithms to produce science level 0, 1, and 2 data products. Meanwhile, it automatically schedules upload of the raw data to a remote server and archives all intermediate and final values in a MySQL database in time order. All data saved in the system can be straightforwardly retrieved, exported, and migrated. Using TSDSS s interactive data visualization tool, a user can conveniently choose any combination and mathematical computation of interesting telemetry points from a large range of time periods (life cycle of mission ground data and mission operations testing), and display a graphical and statistical view of the data. With this graphical user interface (GUI), the data queried graphs can be exported and saved in multiple formats. This GUI is especially useful in trending data analysis, debugging anomalies, and advanced data analysis. At the request of the user, mission-specific instrument performance assessment reports can be generated with a simple click of a button on the GUI. From instrument level to observatory level, the TSDSS has been operating supporting functional and performance tests and refining system calibration algorithms and coefficients, in sync with the Aquarius/SAC-D spacecraft. At the time of this reporting, it was prepared and set up to perform anomaly investigation for mission operations preceding the Aquarius/SAC-D spacecraft launch on June 10, 2011.

Bates, Lakesha↗
NASA NTRS2013

Control Requirements to Support Manual Piloting Capability

The manual piloting requirements specified under the NASA Constellation Program involved Cooper-Harper ratings, which are a qualitative and subjective evaluation from experienced pilots. This type of verification entails a significant investment of resources to assess a completed design and is not one that can easily or meaningfully be applied upfront in the design phase. The evolution of the Multi-Purpose Crew Vehicle Program to include an independently developed propulsion system from an international partner makes application of Cooper-Harper based design requirements inadequate. To mitigate this issue, a novel solution was developed to reformulate the necessary piloting capability into quantifiable requirements. A trio of requirements was designed which specify control authority, precision, and impulse residuals enabling propulsion design within specified guidance and control boundaries. These requirements have been evaluated against both the existing Orion design and the proposed ESA design and have been found to achieve the desired specificity. The requirement set is capable of being applied to the development of other spacecraft in support of manual piloting.

Merancy, Nujoud↗
NASA NTRS2016

Post-Test Inspection of NASA's Evolutionary Xenon Thruster Long Duration Test Hardware: Ion Optics

A Long Duration Test (LDT) was initiated in June 2005 as a part of NASA's Evolutionary Xenon Thruster (NEXT) service life validation approach. Testing was voluntarily terminated in February 2014, with the thruster accumulating 51,184 hours of operation, processing 918 kg of xenon propellant, and delivering 35.5 MN-s of total impulse. The post-test inspection objectives for the ion optics were derived from the original NEXT LDT test objectives, such as service life model validation, and expanded to encompass other goals that included verification of in situ measurements, test issue root causes, and past design changes. The ion optics cold grid gap had decreased only by an average of 7% of pretest center grid gap, so efforts to stabilize NEXT grid gap were largely successful. The upstream screen grid surface exhibited a chamfered erosion pattern. Screen grid thicknesses were ≥ 86% of the estimated pretest thickness, indicating that the screen grid has substantial service life remaining. Deposition was found on the screen aperture walls and downstream surfaces that was primarily composed of grid material and back-sputtered carbon, and this deposition likely caused the minor decreases in screen grid ion transparency during the test. Groove depths had eroded through up to 35% of the accelerator grid thickness. Minimum accelerator aperture diameters increased only by about 5-7% of the pretest values and downstream surface diameters increased by about 24-33% of the pretest diameters. These results suggest that increasing the accelerator aperture diameters, improving manufacturing tolerances, and masking down the perforated diameter to 36 cm were successful in reducing the degree of accelerator aperture erosion at larger radii.

Ion Thruster↗
NASA NTRS2021

Post-test Inspection of NASA’s Evolutionary Xenon Thruster Long Duration Test Hardware: Ion Optics

A Long Duration Test (LDT) was initiated in June 2005 as a part of NASA’s Evolutionary Xenon Thruster (NEXT) service life validation approach. Testing was voluntarily terminated in February 2014, with the thruster accumulating 51,184 hours of operation, processing 918 kg of xenon propellant, and delivering 35.5 MN-s of total impulse. The post-test inspection objectives for the ion optics were derived from the original NEXT LDT test objectives, such as service life model validation, and expanded to encompass other goals that included verification of in situ measurements, test issue root causes, and past design changes. The ion optics cold grid gap had decreased only by an average of 7% of pretest center grid gap, so efforts to stabilize NEXT grid gap were largely successful. The upstream screen grid surface exhibited a chamfered erosion pattern. Screen grid thicknesses were ≥ 86% of the estimated pretest thickness, indicating that the screen grid has substantial service life remaining. Deposition was found on the screen aperture walls and downstream surfaces that was primarily composed of grid material and back-sputtered carbon, and this deposition likely caused the minor decreases in screen grid ion transparency during the test. Groove depths had eroded through up to 35% of the accelerator grid thickness. Minimum accelerator aperture diameters increased only by about 5-7% of the pretest values and downstream surface diameters increased by about 24-33% of the pretest diameters. These results suggest that increasing the accelerator aperture diameters, improving manufacturing tolerances, and masking down the perforated diameter to 36 cm were successful in reducing the degree of accelerator aperture erosion at larger radii.

George C. Soulas↗
NASA NTRSDate not supplied

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy M. Mclaughlin↗
NASA NTRSDate not supplied

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy McLaughlin↗
NASA NTRSDate not supplied

Developmental and Cryogenic Thermal Vacuum (TVAC) Testing Lessons Learned

Developmental thermal vacuum (TVAC) testing is a critical step in maturing hardware designs and validating performance prior to flight qualification. Unlike qualification or acceptance testing, developmental testing provides flexibility to explore design margins, uncover integration challenges, and refine test approaches before formal verification activities begin. This presentation highlights the value of developmental testing while sharing common pitfalls encountered during developmental TVAC campaigns. Lessons learned from hands-on testing experience, including extensive developmental testing at cryogenic temperatures, will be shared in this presentation. Topics include test planning and preparation, instrumentation strategies, contamination control considerations, troubleshooting unexpected anomalies, and approaches for staying on schedule while meeting test objectives. The audience will gain practical insights and best practices that can improve test efficiency, reduce risk, and enhance the overall success of future developmental TVAC efforts.

Mackenzie Byrnes↗
NASA NTRS2010

Application of Diagnostic Analysis Tools to the Ares I Thrust Vector Control System

The NASA Ares I Crew Launch Vehicle is being designed to support missions to the International Space Station (ISS), to the Moon, and beyond. The Ares I is undergoing design and development utilizing commercial-off-the-shelf tools and hardware when applicable, along with cutting edge launch technologies and state-of-the-art design and development. In support of the vehicle s design and development, the Ares Functional Fault Analysis group was tasked to develop an Ares Vehicle Diagnostic Model (AVDM) and to demonstrate the capability of that model to support failure-related analyses and design integration. One important component of the AVDM is the Upper Stage (US) Thrust Vector Control (TVC) diagnostic model-a representation of the failure space of the US TVC subsystem. This paper first presents an overview of the AVDM, its development approach, and the software used to implement the model and conduct diagnostic analysis. It then uses the US TVC diagnostic model to illustrate details of the development, implementation, analysis, and verification processes. Finally, the paper describes how the AVDM model can impact both design and ground operations, and how some of these impacts are being realized during discussions of US TVC diagnostic analyses with US TVC designers.

Maul, William A.↗
NASA NTRS2022

Europa Clipper Payload Verification and Validation: Avionics-Instrument Interface Test Campaign

NASA's Europa Clipper mission will investigate Jupiter's icy moon Europa using a payload suite consisting of nine instruments to address a range of scientific objectives concerning Europa's habitability. As the project proceeds past its Critical Design Review, confidence is being built in the system's ability to achieve mission objectives through the implementation of a rigorous payload verification and validation (V&V) program. As part of this payload V&V program, instrument box-level testing was performed by the payload team to verify select instrument-avionics interface requirements. This testing was performed at JPL using the avionics testbed's Bulk Data Storage Emulator (BDSEM) with visiting instrument Test Models. This paper summarizes the Data Link test campaign involving roughly four days of functional testing per instrument, including planning, testing methods, types of issues found, and the requirement closure process. Detail is also provided on the development, deployment, and validation of a standardized analysis tool used in data reviews. This testing verified requirements related to commanding rates, loss of link, packet format, clock counters, loopback test capability, and SpaceWire jitter and skew margins. Additional risk reduction testing of basic commanding, counter behavior, science data collection and transfer, and interface swapping was also performed. Because the BDSEM venue was not originally designed to be a run for record venue, the process of characterizing venue fidelity and establishing suitability for requirement closure using data collected in this venue will also be addressed.In order to close requirements, an extensible tool was developed to post-process instrument command and telemetry data from their original binary to a human-readable format and give visibility to errors detected within the data, such as packets with Cyclic Redundancy Check errors. This tool, called payload-packet-parser, is a Python 3.9 command line tool built using a variety of open-source Python libraries. Payload-packet-parser was designed to support parsing command and telemetry packets for all Europa Clipper instruments and additional analysis tools were developed for verification of specific information interface requirements. This test campaign, including post-processing using a single parsing and verification toolset, allowed for early interface testing, alleviating testing burdens on instrument teams and buying down risk on the instrument-avionics interface by finding hardware and software issues and idiosyncrasies prior to integration with system test venues. Over twenty issues were discovered across the payload, resulting in software updates and instrument rework well in advance of any system impacts. This paper concludes with an assessment of benefits and costs of this type of testing and lessons learned.

Montanez, Leticia↗
NASA NTRS2003

Requirements Development for the NASA Advanced Engineering Environment (AEE)

The requirements development process for the Advanced Engineering Environment (AEE) is presented. This environment has been developed to allow NASA to perform independent analysis and design of space transportation architectures and technologies. Given the highly collaborative and distributed nature of AEE, a variety of organizations are involved in the development, operations and management of the system. Furthermore, there are additional organizations involved representing external customers and stakeholders. Thorough coordination and effective communication is essential to translate desired expectations of the system into requirements. Functional, verifiable requirements for this (and indeed any) system are necessary to fulfill several roles. Requirements serve as a contractual tool, configuration management tool, and as an engineering tool, sometimes simultaneously. The role of requirements as an engineering tool is particularly important because a stable set of requirements for a system provides a common framework of system scope and characterization among team members. Furthermore, the requirements provide the basis for checking completion of system elements and form the basis for system verification. Requirements are at the core of systems engineering. The AEE Project has undertaken a thorough process to translate the desires and expectations of external customers and stakeholders into functional system-level requirements that are captured with sufficient rigor to allow development planning, resource allocation and system-level design, development, implementation and verification. These requirements are maintained in an integrated, relational database that provides traceability to governing Program requirements and also to verification methods and subsystem-level requirements.

Rogers, Eric↗
NASA NTRS1989

Pressure Distribution and Air Data System for the Aeroassist Flight Experiment

The Aeroassist Flight Experiment (AFE) is designed to provide critical flight data necessary for the design of future Aeroassist Space Transfer Vehicles (ASTV). This flight experiment will provide aerodynamic, aerothermodynamic, and environmental data for verification of experimental and computational flow field techniques. The Pressure Distribution and Air Data System (PD/ADS), one of the measurement systems incorporated into the AFE spacecraft, is designed to provide accurate pressure measurements on the windward surface of the vehicle. These measurements will be used to determine the pressure distribution and air data parameters (angle of attack, angle of sideslip, and free-stream dynamic pressure) encountered by the blunt-bodied vehicle over an altitude range of 76.2 km to 94.5 km. Design and development data are presented and include: measurement requirements, measurement heritage, theoretical studies to define the vehicle environment, flush-mounted orifice configuration, pressure transducer selection and performance evaluation data, and pressure tubing response analysis.

Gibson, Lorelei S.↗
NASA NTRS1976

NASA software specification and evaluation system design, part 1

The research to develop methods for reducing the effort expended in software and verification is reported. The development of a formal software requirements methodology, a formal specifications language, a programming language, a language preprocessor, and code analysis tools are discussed.

Source record↗