Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Standards Development”

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,675 records · Page 93
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

SpaceWire Protocol ID: What Does It Mean To You?

Spacewire is becoming a popular solution for satellite high-speed data buses because it is a simple standard that provides great flexibility for a wide range of system requirements. It is simple in packet format and protocol, allowing users to easily tailor their implementation for their specific application. Some of the attractive aspects of Spacewire that make it easy to implement also make it hard for future reuse. Protocol reuse is difficult because Spacewire does not have a defined mechanism to communicate with the higher layers of the protocol stack. This has forced users of Spacewire to define unique packet formats and define how these packets are to be processed. Each mission writes their own Interface Control Document (ICD) and tailors Spacewire for their specific requirements making reuse difficult. Part of the reason for this habit may be because engineers typically optimize designs for their own requirements in the absence of a standard. This is an inefficient use of project resources and costs more to develop missions. A new packet format for Spacewire has been defined as a solution for this problem. This new packet format is a compliment to the Spacewire standard that will support protocol development upon Spacewire. The new packet definition does not replace the current packet structure, i.e., does not make the standard obsolete, but merely extends the standard for those who want to develop protocols over Spacewire. The Spacewire packet is defined with the first part being the Destination Address, which may be one or more bytes. This is followed by the packet cargo, which is user defined. The cargo is truncated with an End-Of-Packet (EOP) marker. This packet structure offers low packet overhead and allows the user to define how the contents are to be formatted. It also provides for many different addressing schemes, which provide flexibility in the system. This packet flexibility is typically an attractive part of the Spacewire. The new extended packet format adds one new field to the packet that greatly enhances the capability of Spacewire. This new field called the Protocol Identifier (ID) is used to identify the packet contents and the associated processing for the packet. This feature along with the restriction in the packet format that uses the Protocol ID, allows a deterministic method of decoding packets that was not before possible. The first part of the packet is still the Destination Address, which still conforms to the original standard but with one restriction. The restriction is that the first byte seen at the destination by the user needs to be a logical address, independent of the addressing scheme used. The second field is defined as the Protocol ID, which is usually one byte in length. The packet cargo (user defined) follows the Protocol ID. After the packet cargo is the EOP, which defines the end of packet. The value of the Protocol ID is assigned by the Spacewire working group and the protocol description published for others to use. The development of Protocols for Spacewire is currently the area of greatest activity by the Spacewire working group. The first protocol definition by the working group has been completed and is now in the process of formal standardization. There are many other protocols in development for missions that have not yet received formal Protocol ID assignment, but even if the protocols are not formally assigned a value, this effort will provide synergism for future developments.

Rakow, Glenn↗
NASA NTRS2015

An Evaluation of Detect and Avoid (DAA) Displays for Unmanned Aircraft Systems: The Effect of Information Level and Display Location on Pilot Performance

A consortium of government, industry and academia is currently working to establish minimum operational performance standards for Detect and Avoid (DAA) and Control and Communications (C2) systems in order to enable broader integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS). One subset of these performance standards will need to address the DAA display requirements that support an acceptable level of pilot performance. From a pilot's perspective, the DAA task is the maintenance of self separation and collision avoidance from other aircraft, utilizing the available information and controls within the Ground Control Station (GCS), including the DAA display. The pilot-in-the-loop DAA task requires the pilot to carry out three major functions: 1) detect a potential threat, 2) determine an appropriate resolution maneuver, and 3) execute that resolution maneuver via the GCS control and navigation interface(s). The purpose of the present study was to examine two main questions with respect to DAA display considerations that could impact pilots' ability to maintain well clear from other aircraft. First, what is the effect of a minimum (or basic) information display compared to an advanced information display on pilot performance? Second, what is the effect of display location on UAS pilot performance? Two levels of information level (basic, advanced) were compared across two levels of display location (standalone, integrated), for a total of four displays. The authors propose an eight-stage pilot-DAA interaction timeline from which several pilot response time metrics can be extracted. These metrics were compared across the four display conditions. The results indicate that the advanced displays had faster overall response times compared to the basic displays, however, there were no significant differences between the standalone and integrated displays. Implications of the findings on understanding pilot performance on the DAA task, the development of DAA display performance standards, as well as the need for future research are discussed.

detect and avoid↗
NASA NTRS2016

Future Standardization of Space Telecommunications Radio System with Core Flight System

NASA Glenn Research Center (GRC) is integrating the NASA Space Telecommunications Radio System (STRS) Standard with the Core Flight System (cFS), an avionics software operating environment. The STRS standard provides a common, consistent framework to develop, qualify, operate and maintain complex, reconfigurable and reprogrammable radio systems. The cFS is a flexible, open architecture that features a plugand- play software executive called the Core Flight Executive (cFE), a reusable library of software components for flight and space missions and an integrated tool suite. Together, STRS and cFS create a development environment that allows for STRS compliant applications to reference the STRS application programmer interfaces (APIs) that use the cFS infrastructure. These APIs are used to standardize the communication protocols on NASAs space SDRs. The cFS-STRS Operating Environment (OE) is a portable cFS library, which adds the ability to run STRS applications on existing cFS platforms. The purpose of this paper is to discuss the cFS-STRS OE prototype, preliminary experimental results performed using the Advanced Space Radio Platform (ASRP), the GRC S‑ band Ground Station and the SCaN (Space Communication and Navigation) Testbed currently flying onboard the International Space Station (ISS). Additionally, this paper presents a demonstration of the Consultative Committee for Space Data Systems (CCSDS) Spacecraft Onboard Interface Services (SOIS) using electronic data sheets (EDS) inside cFE. This configuration allows for the data sheets to specify binary formats for data exchange between STRS applications. The integration of STRS with cFS leverages mission-proven platform functions and mitigates barriers to integration with future missions. This reduces flight software development time and the costs of software-defined radio (SDR) platforms. Furthermore, the combined benefits of STRS standardization with the flexibility of cFS provide an effective, reliable and modular framework to minimize software development efforts for spaceflight missions.

space communications↗
NASA NTRS1993

Investigation for improving Global Positioning System (GPS) orbits using a discrete sequential estimator and stochastic models of selected physical processes

GEODYNII is a conventional batch least-squares differential corrector computer program with deterministic models of the physical environment. Conventional algorithms were used to process differenced phase and pseudorange data to determine eight-day Global Positioning system (GPS) orbits with several meter accuracy. However, random physical processes drive the errors whose magnitudes prevent improving the GPS orbit accuracy. To improve the orbit accuracy, these random processes should be modeled stochastically. The conventional batch least-squares algorithm cannot accommodate stochastic models, only a stochastic estimation algorithm is suitable, such as a sequential filter/smoother. Also, GEODYNII cannot currently model the correlation among data values. Differenced pseudorange, and especially differenced phase, are precise data types that can be used to improve the GPS orbit precision. To overcome these limitations and improve the accuracy of GPS orbits computed using GEODYNII, we proposed to develop a sequential stochastic filter/smoother processor by using GEODYNII as a type of trajectory preprocessor. Our proposed processor is now completed. It contains a correlated double difference range processing capability, first order Gauss Markov models for the solar radiation pressure scale coefficient and y-bias acceleration, and a random walk model for the tropospheric refraction correction. The development approach was to interface the standard GEODYNII output files (measurement partials and variationals) with software modules containing the stochastic estimator, the stochastic models, and a double differenced phase range processing routine. Thus, no modifications to the original GEODYNII software were required. A schematic of the development is shown. The observational data are edited in the preprocessor and the data are passed to GEODYNII as one of its standard data types. A reference orbit is determined using GEODYNII as a batch least-squares processor and the GEODYNII measurement partial (FTN90) and variational (FTN80, V-matrix) files are generated. These two files along with a control statement file and a satellite identification and mass file are passed to the filter/smoother to estimate time-varying parameter states at each epoch, improved satellite initial elements, and improved estimates of constant parameters.

Goad, Clyde C.↗
NASA NTRS1986

Evaluation of the usefulness of various simulation technology options for TERPS enhancement

Current approved terminal instrument procedures (TERPS) do not permit the full exploitation of the helicopter's unique flying characteristics. Enhanced TERPS need to be developed for a host of non-standard landing sites and navigation aids. Precision navigation systems such as microwave landing systems (MLS) and the Global Positioning System (GPS) open the possibility of curved paths, steep glide slopes, and decelerating helicopter approaches. This study evaluated the feasibility, benefits, and liabilities of using helicopter cockpit simulators in place of flight testing to develop enhanced TERPS criteria for non-standard flight profiles and navigation equipment. Near-term (2 to 5 year) requirements for conducting simulator studies to verify that they produce suitable data comparable to that obtained from previous flight tests are discussed. The long-term (5 to 10 year) research and development requirements to provide necessary modeling for continued simulator-based testing to develop enhanced TERPS criteria are also outlined.

Phatak, A. V.↗
NASA NTRS2005

The Standard Deviation of Launch Vehicle Environments

Statistical analysis is used in the development of the launch vehicle environments of acoustics, vibrations, and shock. The standard deviation of these environments is critical to accurate statistical extrema. However, often very little data exists to define the standard deviation and it is better to use a typical standard deviation than one derived from a few measurements. This paper uses Space Shuttle and expendable launch vehicle flight data to define a typical standard deviation for acoustics and vibrations. The results suggest that 3dB is a conservative and reasonable standard deviation for the source environment and the payload environment.

Yunis, Isam↗
NASA NTRSDate not supplied

Activities of the NASA Urban Air Mobility Noise Working Group (UNWG)

The NASA-led Urban Air Mobility Noise Working Group was established in 2018 following an exploratory meeting of stakeholders from traditional and emerging aviation sectors across industry, government agencies, academia, and community groups. Its mission is to create and support a diverse community of acoustics experts to identify, discuss, and address noise issues associated with UAM vehicles and their operations. The UNWG is comprised of four subgroups including Tools and Technologies, Ground and Flight Testing, Human Response and Metrics, and Regulation and Policy. In 2020, NASA published the white paper entitled “Urban Air Mobility Noise: Current Practice, Gaps, and Recommendations,” that presents a set of high-level goals and makes recommendations to address gaps in the current practice. This presentation is about recent activities of each of the subgroups to address those recommendations, including work towards establishment of an aeroacoustic test database for model validation, development of a set of measurement guidelines to quantify vehicle acoustic emission, a remotely administered human response study for quantifying annoyance to UAM operations, and status on noise standard, regulation, policy, and community engagement developments.

Urban air mobility↗
DOE OSTI2020

Sampling and Analysis Plan for Investigation of Undeclared Nuclear Activities - 20104

The nuclear-centered energy policy in South Korea is moving towards a nuclear-free era. It also facilitates an action or progress on the denuclearization of the Korean peninsula. The Nuclear Safety and Security Commission (NSSC) launched a new R and D project which attempts to verify nuclear activities via analyzing environmental samples. Environmental samples possibly contain significant radiological information relevant to past undeclared activities. In order to precisely verify them, it is essential to provide 1) the concrete information of target facilities, 2) appropriate methodologies and procedures, and 3) well-suited instrumentation and equipment corresponding to sample signatures. It is also important to provide scientific reliability or validity in any process such as sample collection, handling, transportation and laboratory analysis. Therefore, the information of nuclear facilities (fuel fabrication plant, graphite moderated reactor, reprocessing plant) in North Korea are reviewed in order to determine parameters for appropriate sampling methods representing a facility's characteristics. Secondly, a sampling procedure for radioactive elements is being developed based on international and domestic standards such as ASTM (American Society for Testing and Materials), KS (Korean industrial Standards), and International Atomic Energy Agency (IAEA) manuals. The procedure contains some specific information including sampling process, sampling tools, amount of sample, sample identification, and other related information. Developing the qualified national guidelines is most important since sampling and analyzing results can be used as evidences of nuclear activities. The guideline developed through this work will clearly define various methodologies such as document verification, sampling procedures, collection methods, sample storage criteria, chain of custody, and transportation conditions. The final objective of this work is to establish the infrastructure and regulatory framework for assessment of nuclear activities, and provide a national guideline for sampling and analysis. This will bring confidence in the results and play a critical role in complete denuclearization progress in South Korea. (authors)

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗
NASA NTRS1979

Project CAD as of July 1978: CAD support project, situation in July 1978

The structure of Computer Aided Design (CAD) and the requirements for program developments in past and future are described. The actual standard and the future aims of CAD programs are presented. The developed programs in: (1) civil engineering; (2) mechanical engineering; (3) chemical engineering/shipbuilding; (4) electrical engineering; and (5) general programs are discussed.

Boesch, L.↗
NASA NTRS2016

UAS-NAS Flight Test Series 3: Test Environment Report

The desire and ability to fly Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) is of increasing urgency. The application of unmanned aircraft to perform national security, defense, scientific, and emergency management are driving the critical need for less restrictive access by UAS to the NAS. UAS represent a new capability that will provide a variety of services in the government (public) and commercial (civil) aviation sectors. The growth of this potential industry has not yet been realized due to the lack of a common understanding of what is required to safely operate UAS in the NAS. NASA's UAS Integration in the NAS Project is conducting research in the areas of Separation Assurance/Sense and Avoid Interoperability (SSI), Human Systems Integration (HSI), and Communications (Comm), and Certification to support reducing the barriers of UAS access to the NAS. This research is broken into two research themes namely, UAS Integration and Test Infrastructure. UAS Integration focuses on airspace integration procedures and performance standards to enable UAS integration in the air transportation system, covering Detect and Avoid (DAA) performance standards, command and control performance standards, and human systems integration. The focus of Test Infrastructure is to enable development and validation of airspace integration procedures and performance standards, including integrated test and evaluation. In support of the integrated test and evaluation efforts, the Project will develop an adaptable, scalable, and schedulable relevant test environment capable of evaluating concepts and technologies for unmanned aircraft systems to safely operate in the NAS. To accomplish this task, the Project is conducting a series of human-in-the-loop (HITL) and flight test activities that integrate key concepts, technologies and/or procedures in a relevant air traffic environment. Each of the integrated events will build on the technical achievements, fidelity, and complexity of the previous tests and technical simulations, resulting in research findings that support the development of regulations governing the access of UAS into the NAS. The integrated events started with two initial flight test used to develop and test early integrations and components of the test environment. Test subjects and a relevant test environment were brought in for the integrated HITL (or IHITL) conducted in 2014. The IHITL collected data to evaluate the effectiveness of DAA Well Clear (DWC) algorithms and the acceptability of UAS concepts integrated into the NAS. The first integrated flight test (and the subject of this report) followed the IHITL by replacing the simulation components with live aircraft. The project finishes the integrated events with a final flight test to be conducted in 2016 that provides the researchers with an opportunity to collect DWC and Collision Avoidance (CA) interoperability data during flight encounters.

flight test↗
NASA NTRS2020

Leveraging ASTM Industry Standard F3269-17 for Providing Safe Operations of a Highly Autonomous Aircraft

This paper expands upon the ASTM industry standard F3269-17 to outline a run-time assurance (RTA) network architecture for use in ensuring safe flight operations of a highly autonomous aircraft. An RTA network architecture is proposed and critical features discussed to implement functions where automation is primarily responsible for the safety of the aircraft instead of a pilot. This shift in responsibility, made possible by the proposed architecture, is key to highly resilient automation and is a core enabler for future “pilotless” transportation concepts. The findings in this paper stem from the researcher’s experiences with ASTM in the generation of the standard and some seven years of RTA system development on various flight programs leveraging the RTA concepts outlined in the ASTM standard.

autonomous systems↗
NASA NTRS2000

JavaGenes and Condor: Cycle-Scavenging Genetic Algorithms

A genetic algorithm code, JavaGenes, was written in Java and used to evolve pharmaceutical drug molecules and digital circuits. JavaGenes was run under the Condor cycle-scavenging batch system managing 100-170 desktop SGI workstations. Genetic algorithms mimic biological evolution by evolving solutions to problems using crossover and mutation. While most genetic algorithms evolve strings or trees, JavaGenes evolves graphs representing (currently) molecules and circuits. Java was chosen as the implementation language because the genetic algorithm requires random splitting and recombining of graphs, a complex data structure manipulation with ample opportunities for memory leaks, loose pointers, out-of-bound indices, and other hard to find bugs. Java garbage-collection memory management, lack of pointer arithmetic, and array-bounds index checking prevents these bugs from occurring, substantially reducing development time. While a run-time performance penalty must be paid, the only unacceptable performance we encountered was using standard Java serialization to checkpoint and restart the code. This was fixed by a two-day implementation of custom checkpointing. JavaGenes is minimally integrated with Condor; in other words, JavaGenes must do its own checkpointing and I/O redirection. A prototype Java-aware version of Condor was developed using standard Java serialization for checkpointing. For the prototype to be useful, standard Java serialization must be significantly optimized. JavaGenes is approximately 8700 lines of code and a few thousand JavaGenes jobs have been run. Most jobs ran for a few days. Results include proof that genetic algorithms can evolve directed and undirected graphs, development of a novel crossover operator for graphs, a paper in the journal Nanotechnology, and another paper in preparation.

Globus, Al↗
NASA NTRS1989

Product specification documentation standard and Data Item Descriptions (DID). Volume of the information system life-cycle and documentation standards, volume 3

This is the third of five volumes on Information System Life-Cycle and Documentation Standards which present a well organized, easily used standard for providing technical information needed for developing information systems, components, and related processes. This volume states the Software Management and Assurance Program documentation standard for a product specification document and for data item descriptions. The framework can be applied to any NASA information system, software, hardware, operational procedures components, and related processes.

Callender, E. David↗
DOE OSTI2022

Renewable Portfolio Standard Assessment for Alaska's Railbelt

This memorandum for the Governor of Alaska evaluates the technical feasibility of reaching 80% renewable electricity by 2040 in the Railbelt corridor of Alaska, which represents 75% of Alaska's electric load. This analysis was developed to inform renewable energy portfolio standard (RPS) legislation.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
NASA NTRS2004

Space Network Devices Developed

The NASA Glenn Research Center through a contract with Spectrum Astro, Inc., has been developing space network hardware as an enabling technology using open systems interconnect (OSI) standards for space-based communications applications. The OSI standard is a well-recognized layered reference model that specifies how data should be sent node to node in a communications network. Because of this research and technology development, a space-qualifiable Ethernet-based network interface card (similar to the type found in a networked personal computer) and the associated four-port hub were designed and developed to flight specifications. During this research and development, there also have been many lessons learned for determining approaches for migrating existing spacecraft architectures to an OSI-network-based platform. Industry has recognized the benefits of targeting hardware developed around OSI standards such as Transmission Control Protocol/Internet Protocol (TCP/IP) or similar protocols for use in future generations of space communication systems. Some of these tangible benefits include overall reductions in mission schedule and cost and in system complexity. This development also brings us a step closer to the realization of a principal investigator on a terrestrial Internet site being able to interact with space platform assets in near real time. To develop this hardware, Spectrum Astro first conducted a technology analysis of alternatives study. For this analysis, they looked at the features of three protocol specifications: Ethernet (IEEE 802.3), Firewire (IEEE 1394), and Spacewire (IEEE 1355). A thorough analysis was performed on the basis of criteria such as current protocol performance and suitability for future space applications. Spectrum Astro also projected future influences such as cost, hardware and software availability, throughput performance, and integration procedures for current and transitive space architectures. After a thorough analysis, Ethernet was chosen because it was seen as the best longer term fit because of the prevalent commercial market; the current and projected availability of hardware, software, and development tools; and the ease of architecture integration.

Jones, Robert E.↗
NASA NTRS2015

Integrated Test and Evaluation Flight Test 3 Flight Test Plan

The desire and ability to fly Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) is of increasing urgency. The application of unmanned aircraft to perform national security, defense, scientific, and emergency management are driving the critical need for less restrictive access by UAS to the NAS. UAS represent a new capability that will provide a variety of services in the government (public) and commercial (civil) aviation sectors. The growth of this potential industry has not yet been realized due to the lack of a common understanding of what is required to safely operate UAS in the NAS. NASA's UAS Integration into the NAS Project is conducting research in the areas of Separation Assurance/Sense and Avoid Interoperability, Human Systems Integration (HSI), and Communication to support reducing the barriers of UAS access to the NAS. This research is broken into two research themes namely, UAS Integration and Test Infrastructure. UAS Integration focuses on airspace integration procedures and performance standards to enable UAS integration in the air transportation system, covering Sense and Avoid (SAA) performance standards, command and control performance standards, and human systems integration. The focus of Test Infrastructure is to enable development and validation of airspace integration procedures and performance standards, including the integrated test and evaluation. In support of the integrated test and evaluation efforts, the Project will develop an adaptable, scalable, and schedulable relevant test environment capable of evaluating concepts and technologies for unmanned aircraft systems to safely operate in the NAS. To accomplish this task, the Project will conduct a series of Human-in-the-Loop and Flight Test activities that integrate key concepts, technologies and/or procedures in a relevant air traffic environment. Each of the integrated events will build on the technical achievements, fidelity and complexity of the previous tests and technical simulations, resulting in research findings that support the development of regulations governing the access of UAS into the NAS.

Unmanned↗
NASA NTRS2015

UAS Integration in the NAS Project: Integrated Test and Evaluation (IT&E) Flight Test 3

The desire and ability to fly Unmanned Aircraft Systems (UAS) in the National Airspace System (NAS) is of increasing urgency. The application of unmanned aircraft to perform national security, defense, scientific, and emergency management are driving the critical need for less restrictive access by UAS to the NAS. UAS represent a new capability that will provide a variety of services in the government (public) and commercial (civil) aviation sectors. The growth of this potential industry has not yet been realized due to the lack of a common understanding of what is required to safely operate UAS in the NAS. NASA's UAS Integration into the NAS Project is conducting research in the areas of Separation Assurance/Sense and Avoid Interoperability, Human Systems Integration (HSI), and Communication to support reducing the barriers of UAS access to the NAS. This research is broken into two research themes namely, UAS Integration and Test Infrastructure. UAS Integration focuses on airspace integration procedures and performance standards to enable UAS integration in the air transportation system, covering Sense and Avoid (SAA) performance standards, command and control performance standards, and human systems integration. The focus of Test Infrastructure is to enable development and validation of airspace integration procedures and performance standards, including the integrated test and evaluation. In support of the integrated test and evaluation efforts, the Project will develop an adaptable, scalable, and schedulable relevant test environment capable of evaluating concepts and technologies for unmanned aircraft systems to safely operate in the NAS. To accomplish this task, the Project will conduct a series of Human-in-the-Loop and Flight Test activities that integrate key concepts, technologies and/or procedures in a relevant air traffic environment. Each of the integrated events will build on the technical achievements, fidelity and complexity of the previous tests and technical simulations, resulting in research findings that support the development of regulations governing the access of UAS into the NAS.

interoperability↗
NASA NTRS2024

X-57 Cruise Motor GVT Using Fixed-Base Correction Technique

The National Aeronautics and Space Administration (NASA) Armstrong Flight Research Center (AFRC) completed a modal survey of the X-57 Maxwell aircraft cruise motor system to help inform cruise motor redesign efforts. X-57 Maxwell was an electric propulsion demonstrator aircraft developed by NASA to inform airworthiness standards for electrified-aircraft. The cruise motor system modal survey was completed in spring of 2023 utilizing the fixed-base correction (FBC) ground vibration test (GVT) technique developed by ATA Engineering, to decouple the motor modes from the aircraft modes. Previously during the full aircraft GVT, a detailed modal assessment of the cruise motors was not performed. Owing to the X-57 project’s phase in the aircraft development cycle when the motor redesign effort occurred, the cruise motor GVT could only be performed with the cruise motor system installed on the aircraft, with most of its installation hardware (wiring, baffling, sensors, etc.) attached. An impact hammer was used to provide excitation input at various locations within the tight confines of the cruise motor installation. To better support motor redesign efforts, the FBC methodology was utilized to fix, separate and de-couple the cruise motor modes from aircraft modal response. During the GVT, this required additional impact tap tests on candidate fixed-boundary points for each degree of freedom (DOF) to be fixed. Additional triaxial accelerometers installed at the candidate points were used to compute frequency response functions (FRFs) in X, Y, and Z directions to enable those DOFs to be numerically fixed. Test data was acquired using Hottinger Brüel & Kjær’s LAN-XI data acquisition hardware and BK Connect software. FBC post-test processing was performed using the Structural Modification Using Frequency Response Functions (SMURF) technique with ATA Engineering’s Interface between MATLAB, Analysis, Test (IMAT) software. Utilizing the FBC technique relieved test engineers from having to instrument the entire aircraft to identify and separate aircraft response from cruise motor modes of interest. The FBC technique also permitted structural analysis engineers to omit secondary components from their finite element model (FEM) of the cruise motor system. This FBC modal survey was successful, and the first time NASA AFRC utilized the FBC method on an aircraft rather than a test fixture, and also using an impact hammer rather than multiple shakers allowing significant project schedule and cost savings

Modal Survey↗