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 793 records · Page 44

Flight Servicing of Robotic Refueling Mission 3

The Robotic Refueling Mission 3 (RRM3) payload launched aboard a SpaceX rocket en route to the International Space Station on December 5th, 2018. The Goddard Space Flight Center designed payload carried approximately 50 liters of liquid methane onboard, with a mission to demonstrate long term storage and transfer of the cryogenic fluid in microgravity. Kennedy Space Center (KSC) was tasked to design, fabricate, test, and operate a system equipped to fill an RRM3 dewar with liquid methane prior to launch. Though KSC has a rich history of fueling rockets and payloads, no such operations had previously been accomplished using liquid methane. As such, all of the hardware and processes had to be developed from scratch. The completed ground system design, along with the verification and validation testing will be outlined in this paper. Several challenges that were met and overcome during procurement of the high purity methane are described. In addition, budget restrictions prohibited fueling operations from occurring in traditional processing facilities. The unique and creative solutions which were required to maintain payload cleanliness during cryogenic servicing are also detailed.

Cryogenics↗

cFS Test Framework (CTF)

NASA's Core Flight System (cFS) provides a generic flight software framework architecture for developing flight software. As the cFS framework has gained popularity over the years within the flight software community, supporting software tools have been developed to assist in the design, development, testing and verification of flight software. The cFS Test Framework (CTF) is a recently developed cFS tool with capabilities to develop and run automated test and verification scripts against flight software targets. The CTF tool parses and executes JSON-based test scripts containing test instructions, while logging and reporting the results. CTF utilizes a plugin-based architecture to allow developers to extend CTF with new test instructions, external interfaces, and custom functionality. To interface with flight software, CTF parses a set of CCSDS message definition files to create the necessary command and telemetry structures for use during the test run. Additionally, CTF also supports interfacing with multiple cFS instances, allowing a test script to verify requirements that involve multiple flight software targets. Lastly, CTF provides support for executing test scripts against FSW running on remote or embedded hardware. This allows CTF to execute the same test scripts across different target configurations throughout the development process. In this presentation, we will introduce the cFS Test Framework (CTF) architecture, discuss the history of cFS testing frameworks, and present the features and capabilities currently provided by CTF. Lastly, we will show a demo of the CTF tool being used to execute test scripts against flight software.

Aly I Shehata↗

CFS Test Framework

NASA's Core Flight System (cFS) provides a generic flight software framework architecture for developing flight software. As the cFS framework has gained popularity over the years within the flight software community, supporting software tools have been developed to assist in the design, development, testing and verification of flight software. The cFS Test Framework (CTF) is a recently developed cFS tool with capabilities to develop and run automated test and verification scripts against flight software targets. The CTF tool parses and executes JSON-based test scripts containing test instructions, while logging and reporting the results. CTF utilizes a plugin-based architecture to allow developers to extend CTF with new test instructions, external interfaces, and custom functionality. To interface with flight software, CTF parses a set of CCSDS message definition files to create the necessary command and telemetry structures for use during the test run. Additionally, CTF also supports interfacing with multiple cFS instances, allowing a test script to verify requirements that involve multiple flight software targets. Lastly, CTF provides support for executing test scripts against FSW running on remote or embedded hardware. This allows CTF to execute the same test scripts across different target configurations throughout the development process. In this presentation, we will introduce the cFS Test Framework (CTF) architecture, discuss the history of cFS testing frameworks, and present the features and capabilities currently provided by CTF. Lastly, we will show a demo of the CTF tool being used to execute test scripts against flight software.

cfs↗

ROMAN CGI Testbed WFSC Modeling and Validation

Optical diffraction and wavefront sensing and control (WFSC) models validated against the high-fidelity Roman Space Telescope Coronagraph Instrument (CGI) testbed play a key role in mask design selection and the verification of many requirements that cannot be accomplished until the observatory is in orbit. We have been steadily improving our model fidelity for the as-built CGI testbed system, demonstrating recently good agreement between measurements and model predictions while validating the Hybrid Lyot Coronagraph’s (HLC) performance using the in-orbit high order wavefront sensing and control (HOWFSC) operational scenario. We present modeling and testbed validation results that explain the reason many testbed WFSC iterations were needed for HLC in the past. A new, direct application of model-generated deformable mirror (DM) solutions has since been successfully demonstrated on the testbed with significant speed and performance improvement. The benefit of using such a solution opens up new model-based WFSC approaches for CGI. This can greatly reduce flight risk from potentially insufficient ground solution generation due to schedule or cost constraints or from unexpected post-delivery changes.

Poberezhskiy, Ilya↗

Design and Testing of an Approach to Automated In-Flight Safety Risk Management for sUAS Operations

An onboard risk management automation design is presented based on run-time assurance principles, as well as the concept for In-Time Aviation Safety Management Systems (IASMS) as described by the National Academies. The automation is designed to operate independently of the autopilot and perform real-time risk assessment spanning multiple classes of hazards, predict constraint violations, and track autopilot states. In the event of elevated risk conditions or predicted constraint violations, the automation will select from a set of available contingencies and trigger autopilot mode changes if necessary to mitigate risk exposure. The onboard automation also informs the remote operator/pilot of what the independent monitor is observing and any contingency decisions or actions that may arise during flight. Details of an implementation of this design and results of verification and validation activities, as required to meet stringent NASA software and system assurance standards, are also presented. This includes simulation and flight testing using small unmanned aircraft systems.

Ersin Ancel↗

Recent Activities of the Marshall Space Flight Center Natural Environments Branch Terrestrial & Planetary Environments Team

- The Natural Environments (NE) Branch is within the MSFC Engineering Directorate’s Spacecraft and Vehicle System (S&VS) Department - S&VS plans, performs and directs the technical Design, Analysis, Test, Evaluation, Verification, Integration, and Applied Research and Development of future Spacecraft and Launch Vehicle Systems - Current programs we support - Space Launch System, Human Landing System, Mars Ascent Vehicle, Orion, Gateway - NE maintains expertise in terrestrial, space, and planetary natural environments definition, characterization, and analysis - Responsibility to disseminate this expertise to Agency programs and projects in support of environment definition, requirements development, vehicle development, operations, and sustaining engineering through program’s life cycle - Branch has two teams; Terrestrial and Planetary Environments (T&PE) and Space Environments (SE) - T&PE has extensive expertise characterizing terrestrial surface and atmospheric (aloft) environments - Winds, temperature, humidity, pressure, lightning, density, precipitation, radiant energy, aerosols, sea state, sea surface temperature - Maintains climatological databases for engineering analyses

Ryan K. Decker↗

Out of Plane Stresses Using a Beam-Based Elastic Foundation Bonded Joint Model

Efficient, semi-analytical models of bonded joints are utilized for initial joint design and sizing due to their convenience and speed. Many of these models are based on beam and plate theories, which are most applicable when in-plane stresses/strains dominate. While this can be a sensible assumption for obtaining the deformations of the joint, out of plane (transverse) stresses are often of critical importance for failure in bonded joints composed of fiber reinforced composite materials. Since through-thickness strains are neglected in these semi-analytical theories, the present study shows a method to back-calculate the out of plane stresses based on stress balance equations, which use the in-plane stresses and displacements that have already been obtained. The method was implemented within the Joint Element Designer (JED) software, and verification and validation examples have been shown. As is typical for these types of models, corner stress singularities are not captured by the JED model, but the general trends of the stress and deformation fields agreed with a higher fidelity finite element model. As such, this method for obtaining out of plane stresses, when coupled with the JED code, is very useful for the complete stress analysis of bonded composite joints.

composites↗

NASA’s Developments in Cryogenic Fluid Management Technology

NASA has been pursuing the development and demonstration of enabling and enhancing technologies for Cryogenic Fluid Management (CFM) in collaboration with the US industry. NASA’s vision for current and future space exploration requires high-performance chemical and nuclear propulsion solutions that utilize cryogens. The Agency will use cryogenic fluids for Earth-to-orbit transportation, human missions to the Moon and Mars, planetary exploration, and in-situ resource utilization (ISRU) production. All these architectures will require state-of-the-art long-duration storage on the surface and in-space transfer for refueling. This paper focuses on key CFM technology developments completed or ongoing by the Cryogenic Fluid Management Portfolio Office within NASA’s Space Technology Mission Directorate. The CFM Portfolio Office, partnered with US aerospace industry, has invested in CFM technology ground and flight demonstrations, focused on maturing CFM hardware and operations for Artemis and Moon to Mars activities. These demonstrations additionally provide NASA with data to inform numerical modeling activities for verification and validation of design tools and approaches for future missions. This paper includes discussion on remaining high-priority open CFM technology gaps for Mar-forward architectures and initiatives for closure.

Cryogenic Fluid Management↗

Enabling Computation on Sensitive Data in International Safeguards with Privacy-Preserving Encryption Techniques

Privacy-preserving machine learning is a field of study that explores how to protect and preserve the privacy of sensitive data while allowing the data to be used by machine learning algorithms. This field has had substantial industry investment due to heightened concerns about privacy in the technology industry, with a focus in two broad application areas: financial services and healthcare. Numerous privacy-preserving methods have also been proposed for international safeguards, but they have been difficult to enact because the data they require is con- sidered sensitive or proprietary by the nuclear facility operator. This work examines how current privacy-preserving approaches might be used to enable the International Atomic Energy Agency (IAEA) to use that data to contribute to a safeguards conclusion about a state while giving nuclear operators confidence that their sensitive data is adequately protected. This paper begins by exploring several broad categories of privacy-preserving techniques including homomorphic encryption, secure multiparty computation, secure enclaves, and zero-knowledge proofs. Then we discuss some of the security considerations related to using these methods, potential use cases, and a conceptual system design for applying privacy-preserving methods in international safeguards.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗

Experimental and Analytical Verification of ASME Section IiII Division 5 Creep-Fatigue Design Rules

The continuous advancement of structural materials and the growing demands for more reliable and economical structural components in high-temperature reactor applications have necessitated the development of comprehensive design methodologies and design rules. Mechanical degradation of structural components at elevated temperatures subjected to cyclic deformation is controlled by the creep-fatigue damage. Over the past few decades, diligent research efforts have been dedicated to refining the development of elevated temperature design rules in the American Society of Mechanical Engineers (ASME) Boiler and Pressure Vessel Code (BPVC), Section III, Division 5 and to develop conservative design rules that can effectively guard against the risk of creep-fatigue failure. In ASME Section III, Division 5, for a design to pass the creep-fatigue acceptance criteria, creep damage and fatigue damage are evaluated separately, and these damages must not violate the bi-linear creep-fatigue interaction diagram, i.e., the so-called D-diagram. The creep-fatigue damage evaluation procedure assumes that the effects of the actual cyclic loading sequence can be bounded by assuming that the individual loading cycles are uniformly distributed throughout the component design life. In this study, creep-fatigue experiments with variable amplitudes and loading sequencies were designed and performed on Alloy 617 at high temperatures. The results were analyzed to evaluate the loading history effect on creep-fatigue damage accumulation and to verify the assumptions for the creep-fatigue evaluation design rules.

36 - MATERIALS SCIENCE↗

6DOF Testing of the SLS Inertial Navigation Unit

The Navigation System on the NASA Space Launch System (SLS) Block 1 vehicle performs initial alignment of the Inertial Navigation System (INS) navigation frame through gyrocompass alignment (GCA). Because the navigation architecture for the SLS Block 1 vehicle is a purely inertial system, the accuracy of the achieved orbit relative to mission requirements is very sensitive to initial alignment accuracy. The assessment of this sensitivity and many others via simulation is a part of the SLS Model-Based Design and Model-Based Requirements approach. As a part of the aforementioned, 6DOF Monte Carlo simulation is used in large part to develop and demonstrate verification of program requirements. To facilitate this and the GN&C flight software design process, an SLS-Program-controlled Design Math Model (DMM) of the SLS INS was developed by the SLS Navigation Team. The SLS INS model implements all of the key functions of the hardware-namely, GCA, inertial navigation, and FDIR (Fault Detection, Isolation, and Recovery)-in support of SLS GN&C design requirements verification. Despite the strong sensitivity to initial alignment, GCA accuracy requirements were not verified by test due to program cost and schedule constraints. Instead, the system relies upon assessments performed using the SLS INS model. In order to verify SLS program requirements by analysis, the SLS INS model is verified and validated against flight hardware. In lieu of direct testing of GCA accuracy in support of requirement verification, the SLS Navigation Team proposed and conducted an engineering test to, among other things, validate the GCA performance and overall behavior of the SLS INS model through comparison with test data. This paper will detail dynamic hardware testing of the SLS INS, conducted by the SLS Navigation Team at Marshall Space Flight Center's 6DOF Table Facility, in support of GCA performance characterization and INS model validation. A 6-DOF motion platform was used to produce 6DOF pad twist and sway dynamics while a simulated SLS flight computer communicated with the INS. Tests conducted include an evaluation of GCA algorithm robustness to increasingly dynamic pad environments, an examination of GCA algorithm stability and accuracy over long durations, and a long-duration static test to gather enough data for Allan Variance analysis. Test setup, execution, and data analysis will be discussed, including analysis performed in support of SLS INS model validation.

Geohagan, Kevin↗

GTX Reference Vehicle Structural Verification Methods and Weight Summary

The design of a single-stage-to-orbit air breathing propulsion system requires the simultaneous development of a reference launch vehicle in order to achieve the optimal mission performance. Accordingly, for the GTX study a 300-lb payload reference vehicle was preliminary sized to a gross liftoff weight (GLOW) of 238,000 lb. A finite element model of the integrated vehicle/propulsion system was subjected to the trajectory environment and subsequently optimized for structural efficiency. This study involved the development of aerodynamic loads mapped to finite element models of the integrated system in order to assess vehicle margins of safety. Commercially available analysis codes were used in the process along with some internally developed spread-sheets and FORTRAN codes specific to the GTX geometry for mapping of thermal and pressure loads. A mass fraction of 0.20 for the integrated system dry weight has been the driver for a vehicle design consisting of state-of-the-art composite materials in order to meet the rigid weight requirements. This paper summarizes the methodology used for preliminary analyses and presents the current status of the weight optimization for the structural components of the integrated system.

Hunter, J. E.↗

GTX Reference Vehicle Structural Verification Methods and Weight Summary

The design of a single-stage-to-orbit air breathing propulsion system requires the simultaneous development of a reference launch vehicle in order to achieve the optimal mission performance. Accordingly, for the GTX study a 300-lb payload reference vehicle was preliminarily sized to a gross liftoff weight (GLOW) of 238,000 lb. A finite element model of the integrated vehicle/propulsion system was subjected to the trajectory environment and subsequently optimized for structural efficiency. This study involved the development of aerodynamic loads mapped to finite element models of the integrated system in order to assess vehicle margins of safety. Commercially available analysis codes were used in the process along with some internally developed spreadsheets and FORTRAN codes specific to the GTX geometry for mapping of thermal and pressure loads. A mass fraction of 0.20 for the integrated system dry weight has been the driver for a vehicle design consisting of state-of-the-art composite materials in order to meet the rigid weight requirements. This paper summarizes the methodology used for preliminary analyses and presents the current status of the weight optimization for the structural components of the integrated system.

Hunter, J. E.↗

Space Shuttle Crawler Transporter Vibration Analysis in Support of Rollout Fatigue Load Spectra Verification Program

The Crawler Transporter (CT), designed and built for the Apollo Program in the 1960's and surpassing its initial operational life, has become an integral part of the Space Shuttle Program (SSP). The CT transports the Space Shuttle Vehicle (SSV) stack, atop the Mobile Launch Platform (MLP), from the Vehicle Assembly Building (VAB) to the launch pad. This support structure provides hydraulic jacking, leveling and load equalization for the 12 million pound stack on its 3.5-5.0 mile rollout to the launch pad. Major elements of the SSV, consisting of the orbiter, solid rocket boosters (SRB) and external tank (ET) have required fatigue analyses as part of the mission life certification. Compared to rollout vibration, the SSV sees relatively high vibration loads during launch, ascent, descent and landing phases of the mission. Although preliminary measured SRB vibration levels during rollout were of low amplitude and frequency, the duration of the rollout phase is typically high, from 5-6 hours. As part of an expanded mission life assessment, additional certification effort was initiated to define fatigue load spectra for rollout. This study addresses the CT vibration analyses in support of the rollout fatigue study. Structural models developed for modal and vibration analyses were used to identify unique CT, CT/MLP and CT/MLP/SRB vibration characteristics for comparison to instrumented rollout tests. Whereas the main structural and vibration characteristics of the SSV are well defined, minimum analytical and vibration test data on the Crawler Transporter were available. Unique vibration characteristics of the CT are attributable to the drive mechanism, hydraulic jacking system, structural framing and the CT-to-MLP support pad restraints. Initial tests performed on the CT/MLP/SRB configuration showed reasonable correlation with predicted mode shapes and frequencies.

Margasahayam, Ravi N.↗

Propfan test assessment testbed aircraft flutter model test report

The PropFan Test Assessment (PTA) program includes flight tests of a propfan power plant mounted on the left wind of a modified Gulfstream II testbed aircraft. A static balance boom is mounted on the right wing tip for lateral balance. Flutter analyses indicate that these installations reduce the wing flutter stabilizing speed and that torsional stiffening and the installation of a flutter stabilizing tip boom are required on the left wing for adequate flutter safety margins. Wind tunnel tests of a 1/9th scale high speed flutter model of the testbed aircraft were conducted. The test program included the design, fabrication, and testing of the flutter model and the correlation of the flutter test data with analysis results. Excellent correlations with the test data were achieved in posttest flutter analysis using actual model properties. It was concluded that the flutter analysis method used was capable of accurate flutter predictions for both the (symmetric) twin propfan configuration and the (unsymmetric) single propfan configuration. The flutter analysis also revealed that the differences between the tested model configurations and the current aircraft design caused the (scaled) model flutter speed to be significantly higher than that of the aircraft, at least for the single propfan configuration without a flutter boom. Verification of the aircraft final design should, therefore, be based on flutter predictions made with the test validated analysis methods.

Jenness, C. M. J.↗

A Verification Framework for Runtime Assurance of Autonomous UAS

Runtime Assurance (RTA) is a design-time architecture for safety-critical systems where an internal monitor acts upon detecting a violation of a property. The simplex architecture is an instance of RTA, where the action taken is to hand control of the overall system to a trusted controller when an untrusted one violates a safety property. Simplex RTA is emerging as a method for allowing AI/ML and other unverified software to be integrated into safety-critical applications like aircraft. To this end, the American Society for Testing and Materials (ASTM) and NASA have each published guidelines on the use of RTA in such systems. In the simplex RTA framework, a system has an advanced controller (AC) and a reversionary controller (RC). The system is allowed to operate with the AC until a runtime monitor detects that some property has been violated and then the RC takes over. Assuming that the sample rate of the monitor will detect improper functioning with enough time for the RC to correct the impending problem, and that the RC is trusted, the system will operate as intended. This use of the simplex RTA framework can allow for the integration of untrusted, but possibly more performant, controllers in a safe way. This paper presents a formalization of a simplex RTA framework in the Prototype Verification System (PVS) theorem prover using an embedding of differential dynamic logic (DDL) called Plaidypvs. A novel feature of this framework is that it can be instantiated at different levels of abstraction. This feature allows for the formal verification of a system with an untrusted black box component, such as an AI/ML controller. This paper does not address the many difficulties in deploying RTA in an industrial-level system. Instead, the focus is on the formal verification of the simplex RTA framework in the language of hybrid programs. Hybrid programs are programs that include both discrete and continuous dynamics and can be used to model complex cyber-physical systems. Plaidypvs is a tool that enables formalization of hybrid programs in the PVS theorem prover. Plaidypvs enables the verification of the general simplex RTA framework and then, by specializing some components of the hybrid program, verifying instances of the framework while treating the untrusted component as a black box. A selection of Unmanned Aircraft Systems (UAS) operations are shown as instances of the general RTA framework in PVS. This offers the benefit of design time verification of relevant safety properties to the system, and it also gives requirements on the sample rate of sensors that determine the time interval in which the ‘switch’ property of the RTA framework is checked.

PVS↗

Space station definitions, design, and development. Task 5: Multiple arm telerobot coordination and control: Manipulator design methodology

A proposed methodology applicable to the design of manipulator systems is described. The current design process is especially weak in the preliminary design phase, since there is no accepted measure to be used in trading off different options available for the various subsystems. The design process described uses Cartesian End-Effector Impedance as a measure of performance for the system. Having this measure of performance, it is shown how it may be used to determine the trade-offs necessary to the preliminary design phase. The design process involves three main parts: (1) determination of desired system performance in terms of End-Effector Impedance; (2) trade-off design options to achieve this desired performance; and (3) verification of system performance through laboratory testing. The design process is developed using numerous examples and experiments to demonstrate the feasability of this approach to manipulator design.

Stoughton, R. M.↗