Search NASA⌕ Search

SEARCH · Search NASA

Results for “FSW”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Investigation of Abnormal Grain Growth in a Friction Stir Welded and Spin-Formed Al-Li Alloy 2195 Crew Module

In order to improve manufacturing efficiency and reduce structural mass and costs in the production of launch vehicle structures, NASA is pursuing a wide-range of innovative, near-net shape manufacturing technologies. A technology that combines friction stir welding (FSW) and spin-forming has been applied to manufacture a single-piece crew module using Aluminum-Lithium (AL-Li) Alloy 2195. Plate size limitations for Al-Li alloy 2195 require that two plates be FSW together to produce a spin-forming blank of sufficient size to form the crew module. Subsequent forming of the FSW results in abnormal grain growth (AGG) within the weld region upon solution heat treatment (SHT), which detrimentally impacts strength, ductility, and fracture toughness. The current study seeks to identify microstructural factors that contribute to the development of AGG. Electron backscatter diffraction (EBSD) was used to correlate driving forces for AGG, such as stored energy, texture, and grain size distributions, with the propensity for AGG. Additionally, developmental annealing treatments prior to SHT are examined to reduce or eliminate the occurrence of AGG by promoting continuous, or uniform, grain growth

Tayon, Wesley A.↗
NASA NTRS2015

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗
NASA NTRS2016

The Core Flight System (cFS) Community: Providing Low Cost Solutions for Small Spacecraft

In February 2015 the NASA Goddard Space Flight Center (GSFC) completed the open source release of the entire Core Flight Software (cFS) suite. After the open source release a multi-NASA center Configuration Control Board (CCB) was established that has managed multiple cFS product releases. The cFS was developed and is being maintained in compliance with the NASA Class B software development process requirements and the open source release includes all Class B artifacts. The cFS is currently running on three operational science spacecraft and is being used on multiple spacecraft and instrument development efforts. While the cFS itself is a viable flight software (FSW) solution, we have discovered that the cFS community is a continuous source of innovation and growth that provides products and tools that serve the entire FSW lifecycle and future mission needs. This paper summarizes the current state of the cFS community, the key FSW technologies being pursued, the development/verification tools and opportunities for the small satellite community to become engaged. The cFS is a proven high quality and cost-effective solution for small satellites with constrained budgets.

System↗
NASA NTRS2016

Origins of Line Defects in Self-Reacting Friction Stir Welds and Their Impact on Weld Quality

Friction stir welding (FSWing) is a solid state joining technique which reduces the occurrence of typical defects formed in fusion welds, especially of highly alloyed metals. Although the process is robust for aluminum alloys, occasional reductions in the strength of FSWs have been observed. Shortly after the NASA-MSFC implemented a variation of FSW called self-reacting (SR), low strength properties were observed. At that time, this reduction in strength was attributed to a line defect. At that time, the limited data suggested that the line defect was related to the accumulation of native oxides that form on the weld lands and faying surfaces. Through a series of improved cleaning methods, tool redesign, and process parameter modifications, the reduction in the strength of the SR-FSWs was eliminated. As more data has been collected, the occasional reduction in the strength of SR-FSW still occurs. These occasional reductions indicate a need to reexamine the underlying causes. This study builds off a series of self reacting (SR)-FSWs that were made in 3 different thickness panels of AA2219 (0.95, 1.27 and 1.56 cm) at 2 different weld pitches. A bead on plate SR-FSW was also made in the 1.56 cm thick panel to understand the contribution of the former faying surfaces. Copper tracer studies were used to understand the flow lines associated with the weld tool used. The quality of the SR-FSWs was evaluated from tensile testing at room temperature. Reductions in the tensile strength were observed in some weldments, primarily at higher weld pitch or tool rotations. This study explores possible correlations between line defects and the reduction of strength in SR-FSWs. Results from this study will assist in a better understand of the mechanisms responsible for reduced tensile strength and provide methodology for minimizing their occurrence.

Schneider, Judy↗
NASA NTRS2016

Modeling in the State Flow Environment to Support Launch Vehicle Verification Testing for Mission and Fault Management Algorithms in the NASA Space Launch System

Analysis methods and testing processes are essential activities in the engineering development and verification of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS). Central to mission success is reliable verification of the Mission and Fault Management (M&FM) algorithms for the SLS launch vehicle (LV) flight software. This is particularly difficult because M&FM algorithms integrate and operate LV subsystems, which consist of diverse forms of hardware and software themselves, with equally diverse integration from the engineering disciplines of LV subsystems. M&FM operation of SLS requires a changing mix of LV automation. During pre-launch the LV is primarily operated by the Kennedy Space Center (KSC) Ground Systems Development and Operations (GSDO) organization with some LV automation of time-critical functions, and much more autonomous LV operations during ascent that have crucial interactions with the Orion crew capsule, its astronauts, and with mission controllers at the Johnson Space Center. M&FM algorithms must perform all nominal mission commanding via the flight computer to control LV states from pre-launch through disposal and also address failure conditions by initiating autonomous or commanded aborts (crew capsule escape from the failing LV), redundancy management of failing subsystems and components, and safing actions to reduce or prevent threats to ground systems and crew. To address the criticality of the verification testing of these algorithms, the NASA M&FM team has utilized the State Flow environment6 (SFE) with its existing Vehicle Management End-to-End Testbed (VMET) platform which also hosts vendor-supplied physics-based LV subsystem models. The human-derived M&FM algorithms are designed and vetted in Integrated Development Teams composed of design and development disciplines such as Systems Engineering, Flight Software (FSW), Safety and Mission Assurance (S&MA) and major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GN&C), Thrust Vector Control (TVC), liquid engines, and the astronaut crew office. Since the algorithms are realized using model-based engineering (MBE) methods from a hybrid of the Unified Modeling Language (UML) and Systems Modeling Language (SysML), SFE methods are a natural fit to provide an in depth analysis of the interactive behavior of these algorithms with the SLS LV subsystem models. For this, the M&FM algorithms and the SLS LV subsystem models are modeled using constructs provided by Matlab which also enables modeling of the accompanying interfaces providing greater flexibility for integrated testing and analysis, which helps forecast expected behavior in forward VMET integrated testing activities. In VMET, the M&FM algorithms are prototyped and implemented using the same C++ programming language and similar state machine architectural concepts used by the FSW group. Due to the interactive complexity of the algorithms, VMET testing thus far has verified all the individual M&FM subsystem algorithms with select subsystem vendor models but is steadily progressing to assessing the interactive behavior of these algorithms with LV subsystems, as represented by subsystem models. The novel SFE applications has proven to be useful for quick look analysis into early integrated system behavior and assessment of the M&FM algorithms with the modeled LV subsystems. This early MBE analysis generates vital insight into the integrated system behaviors, algorithm sensitivities, design issues, and has aided in the debugging of the M&FM algorithms well before full testing can begin in more expensive, higher fidelity but more arduous environments such as VMET, FSW testing, and the Systems Integration Lab7 (SIL). SFE has exhibited both expected and unexpected behaviors in nominal and off nominal test cases prior to full VMET testing. In many findings, these behavioral characteristics were used to correct the M&FM algorithms, enable better test coverage, and develop more effective test cases for each of the LV subsystems. This has improved the fidelity of testing and planning for the next generation of M&FM algorithms as the SLS program evolves from non-crewed to crewed flight, impacting subsystem configurations and the M&FM algorithms that control them. SFE analysis has improved robustness and reliability of the M&FM algorithms by revealing implementation errors and documentation inconsistencies. It is also improving planning efficiency for future VMET testing of the M&FM algorithms hosted in the LV flight computers, further reducing risk for the SLS launch infrastructure, the SLS LV, and most importantly the crew.

Trevino, Luis↗
NASA NTRS2015

Rule-Based Flight Software Cost Estimation

This paper discusses the fundamental process for the computation of Flight Software (FSW) cost estimates. This process has been incorporated in a rule-based expert system [1] that can be used for Independent Cost Estimates (ICEs), Proposals, and for the validation of Cost Analysis Data Requirements (CADRe) submissions. A high-level directed graph (referred to here as a decision graph) illustrates the steps taken in the production of these estimated costs and serves as a basis of design for the expert system described in this paper. Detailed discussions are subsequently given elaborating upon the methodology, tools, charts, and caveats related to the various nodes of the graph. We present general principles for the estimation of FSW using SEER-SEM as an illustration of these principles when appropriate. Since Source Lines of Code (SLOC) is a major cost driver, a discussion of various SLOC data sources for the preparation of the estimates is given together with an explanation of how contractor SLOC estimates compare with the SLOC estimates used by JPL. Obtaining consistency in code counting will be presented as well as factors used in reconciling SLOC estimates from different code counters. When sufficient data is obtained, a mapping into the JPL Work Breakdown Structure (WBS) from the SEER-SEM output is illustrated. For across the board FSW estimates, as was done for the NASA Discovery Mission proposal estimates performed at JPL, a comparative high-level summary sheet for all missions with the SLOC, data description, brief mission description and the most relevant SEER-SEM parameter values is given to illustrate an encapsulation of the used and calculated data involved in the estimates. The rule-based expert system described provides the user with inputs useful or sufficient to run generic cost estimation programs. This system's incarnation is achieved via the C Language Integrated Production System (CLIPS) and will be addressed at the end of this paper.

computational intelligence↗
NASA NTRS2018

Using the cFS Command and Data Dictionary (CCDD) to Automate Software Development on Habulous

Final paper is attached. The NASA developed Core Flight System (cFS) is a reusable software architecture that has been used on multiple spaceflight missions. By using this framework, missions are able to reuse code from other missions, as well as leverage deployment onto similar computer architectures (i.e. not "reinvent the wheel" on each new mission). The success in the cFS concept can be seen in the large number of projects using cFS at FSW-2018. The Habulous project is an Earth-based testbed, used for hardware and software that may one day be used on a future space habitat unit, with many participating groups from various NASA centers and aerospace organizations around the country. The distributed nature of the various teams mean that defining (and following) an interface definition is critical on the project. Additionally, since various groups use various types of computer hardware (32/64-bit, big/little endian, Linux/VxWorks/Windows) many additional complications exist in interfacing all the various components into a final integrated system. cFS is used on the majority the flight software (FSW) in running in Habulous. But some subsystems have elected to not use cFS, and use a software bridge (called SBN_lib) to interact with the other cFS nodes in Habulous. In order to most efficiently develop the FSW, a central database is used to define and store each message sent by cFS. A Command and Data Dictionary (CDD) is something nearly universal on spacecraft, but as a team we worked to develop the CDD before the SW development was complete, and not treat it like "as built" documentation. To manage the CDD, the cFS Command and Data Dictionary (CCDD) tool was chosen (available from NASA as open source software). The CCDD tool has successfully been used to automate/autocode a large amount of software used on Habulous, as we are hoping to use it to define even more items in the future (time-triggered Ethernet (TTE) network maps, CPU scheduling). Additionally, Habulous has been exploring the use of cFS on wildly heterogeneous CPUs, and how to coordinate all those various machines using/extending the software bus – network (SBN) application in cFS, as well as TTE to coordinate message passing between various synchronized machines. The major topics to be covered in the presentation are: (1) Updating to the CCSDS_v2 extended headers (and using CPU# as subsystem ID). (2) Managing all the message identification numbers for each cFS message sent/received on any of the various CPUs. (3) Using the CCDD information to automatically generate the C-header files that define the structure for all software bus (SB) commands/telemetry messages. (4) Using the CCDD to automatically generate XML Telemetry and Command Exchange (XTCE) files, which streams display production/integration/testing in a web based display architecture (5) Extending/customizing SBN to pass messages among computers on multiple networks. (6) Using "Protobetter" inside SBN to manage different endian-ness/architectures. (7) Using SBN_lib to allow non-cFS node to communicate with cFS nodes. (8) Developing TTE network and schedule tables for all the various CPUs to use.

Hirsh, Robert L.↗
NASA NTRSDate not supplied

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↗
NASA NTRSDate not supplied

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↗
NASA NTRS1978

Work Capability and physiological effects predictive studies. 4: In He-O2 excursions to pressures of 400- 800- 1200- and 1600 feet of sea water

Experiments which exposed men in chambers, breathing helium with oxygen, to progressive increases of pressure equivalent to 400-800-1200-1600 feet of sea water (fsw) were conducted. Rates of compression and exposure to stable high pressure. Goals included: 1) determination of the specific character and time course of onset of physiological and performance decrements during the intentionally rapid compressions, and determination of rates of adaptation on reaching stable elevated pressure; 2) investigation of accelerated methods for decompression in deep saturation excursion diving; and 3) determination of competence in practical work performed in water at pressures equivalent to the extreme diving depths of 1200 and 1600 fsw.

Lambertsen, C. J.↗
NASA NTRS1984

Body-freedom flutter of a 1/2-scale forward-swept-wing model, an experimental and analytical study

The aeroelastic phenomenon known as body-freedom flutter (BFF), a dynamic instability involving aircraft-pitch and wing-bending motions which, though rarely experienced on conventional vehicles, is characteristic of forward swept wing (FSW) aircraft was investigated. Testing was conducted in the Langley transonic dynamics tunnel on a flying, cable-mounted, 1/2-scale model of a FSW configuration with and without relaxed static stability (RSS). The BFF instability boundaries were found to occur at significantly lower airspeeds than those associated with aeroelastic wing divergence on the same model. For those cases with RSS, a canard-based stability augmentation system (SAS) was incorporated in the model. This SAS was designed using aerodynamic data measured during a preliminary tunnel test in which the model was attached to a force balance. Data from the subsequent flutter test indicated that BFF speed was not dependent on open-loop static margin but, rather, on the equivalent closed-loop dynamics provided by the SAS. Servo-aeroelastic stability analyses of the flying model were performed using a computer code known as SEAL and predicted the onset of BFF reasonably well.

Chipman, R.↗
NASA NTRS1984

Control of forward swept wing configurations dominated by flight-dynamic/aeroelastic interactions

An active control system concept for an aeroelastic wind-tunnel model of a statically unstable FSW configuration with wing-mounted stores is developed to provide acceptable longitudinal flying qualities while maintaining adequate flutter speed margin. On FSW configurations, the inherent aeroelastic wing divergence tendency causes strong flight-dynamic/aeroelastic interactions that in certain cases can produce a dynamic instability known as body-freedom flutter (BFF). The carriage of wing-mounted stores is shown to severely aggravate this problem. The control system developed combines a canard-based SAS with an Active Divergence/Flutter Suppression (ADFS) system which relies on wing-mounted sensors and a trailing-edge device (flaperon). Synergism between these two systems is exploited to obtain the flying qualities and flutter speed objectives.

Rimer, M.↗
NASA NTRS1985

Transonic test of a forward swept wing configuration exhibiting Body Freedom Flutter

The aeroelastic dynamic instability designated Body Freedom Flutter (BFF) involves aircraft pitch and wing bending motions characteristic of forward swept wing (FSW) aircraft. Attention is presently given to the results of tests conducted on a 1/2-scale cable-mounted FSW wind tunnel model, with and without relaxed static stability (RSS) control conditions. BFF instability boundaries were found to occur at significantly lower air speeds than those associated with aeroelastic wing divergence on the same model. Servoaeroelastic stability analyses have been conducted which proved capable of predicting the measured onset of BFF, in both the statically stable and RSS configurations tested.

Chipman, R.↗
NASA NTRS1985

X-29 initial flight test results

It is announced that the X-29 forward-swept-wing (FSW) aircraft has been built, with flight testing under way and proceeding smoothly. The X-29 is a single-seat, single-engine supersonic aircraft that blends an optimized FSW, a close-coupled near-coplar canard, an F-5A forward fuselage module employing two side-mounted engine inlets, and a new aft fuselage. An F404-GE-400 engine with afterburner provides about 16,000 lb of thrust. The X-29 was designed to be near neutrally stable in the supersonic region to minimize drag; it becomes highly unstable transonically and subsonically, which dictates the use of a computerized fly-by-wire flight control system capable of stabilizing the aircraft. The X-29 advanced technology demonstrator began flight testing on Dec. 14, 1984; by Sept. 26, 1985, its envelope had been expanded to 0.75 Mach, 350 knots estimated airspeed, and 30,000 feet altitude. The aircraft has flown with very few problems and aerodynamic, structural, and control system results have correlated well with predictions. Areas where prediction and performance are not so well correlated are noted.

Ishmael, S. D.↗
NASA NTRS1998

A Combined Experimental and Analytical Modeling Approach to Understanding Friction Stir Welding

In the Friction Stir Welding (FSW) process a rotating pin tool joins the sides of a seam by stirring them together. This solid state welding process avoids problems with melting and hot-shortness presented by some difficult-to weld high-performance light alloys. The details of the plastic flow during the process are not well understood and are currently a subject of research. Two candidate models of the FSW process, the Mixed Zone (MZ) and the Single Slip Surface (S3) model are presented and their predictions compared to experimental data.

Nunes, Arthur C., Jr.↗
NASA NTRS1998

Loading Considerations for Implementing Friction STIR Welding for Large Diameter Tank Fabrication

The main objectives of the research presented here are to determine the reaction loads associated with friction stir welding (FSW) and to determine the suitability of an existing welding fixture for implementing this welding process in the fabrication of large diameter tanks. Friction stir welding is a relatively new process which is being investigated as a method for joining aluminum alloys. The aluminum-lithium alloy, Al-Li 2195, which is being used to fabricate the super-light-weight shuttle external tank has proven difficult to join using fusion techniques. Therefore, FSW and its potential applicability to joining Al-Li 2195 are of particular interest to NASA.

Adams, Glynn↗
NASA NTRS1999

Assembly of a Full-Scale External Tank Barrel Section Using Friction Stir Welding

A full-scale pathfinder barrel section of the External Tank for the National Aeronautics and Space Administration (NASA) Space Transport System (Space Shuttle) has been assembled at Marshall Space Flight Center (MSFC) via a collaborative effort between NASA/MSFC and Lockheed Martin Michoud Space Systems. The barrel section is 27.5 feet in diameter and 15 feet in height. The barrel was assembled using Super-Light-Weight (SLWT), orthogrid, Al-Li 2195 panel sections and a single longeron panel. A vertical weld tool at MSFC was modified to accommodate FSW and used to assemble the barrel. These modifications included the addition of a FSW weld head and new controller hardware and software, the addition of a backing anvil and the replacement of the clamping system with individually actuated clamps. Weld process 4evelopment was initially conducted to optimize the process for the welds required for completing the assembly. The variable thickness welds in the longeron section were conducted via both two-sided welds and with the use of a retractable pin tool. The barrel assembly was completed in October 1998. Details of the vertical weld tool modifications and the assembly process are presented.

Jones, Chip↗
NASA NTRS2000

The Plastic Flow Field in the Vicinity of the Pin-Tool During Friction Stir Welding

The plastic flow field in the vicinity of the pin-tool during Friction Stir Welding (FSW) needs to be understood if a theoretical understanding of the process is to be attained. The structure of welds does not exhibit the flow field itself, but consists in a residue of displacements left by the plastic flow field. The residue requires analysis to extract from it the instantaneous flow field around the pin-tool. A simplified merry-go-round model makes sense of some tracer experiments reported in the literature. A quantitative comparison is made of the displacements of copper wire markers with displacements computed from a hypothetical plastic flow field. The hypothetical plastic flow field consists in a circular rotation field about a translating pin tool with angular velocity varying with radius from the pin centerline. A sharply localized rotational field comprising slip on a surface around the tool agreed better with observations than a distributed slip field occupying a substantial volume around the tool. Both the tracer and the wire displacements support the "rotating plug" model, originally invoked or thermal reasons, of the FSW process.

Bernstein, E. L.↗