Users Online

· Guests Online: 30

· Members Online: 0

· Total Members: 188
· Newest Member: meenachowdary055

Forum Threads

Newest Threads
No Threads created
Hottest Threads
No Threads created

Latest Articles

Contact Modeling in LS-DYNA

Contact Modeling in LS-DYNA

 

 

Contact treatment forms an integral part of many large-deformation problems. Accurate modeling of contact interfaces between bodies is crucial to the prediction capability of the finite element simulations. LS-DYNA offers a large number of contact types. Some types are for specific applications, and others are suitable for more general use. Many of the older contact types are rarely used but are still retained to enable older models to run as they did in the past. Users are faced with numerous choices in modeling contact. This document is designed to provide an overview of contact treatment in LS-DYNA and to serve as a guide for choosing appropriate contact types and parameters.

 

Contact output

There are numerous output files pertaining to contact which can be written by LS-DYNA. LSPOST can read these output files and plot the results.

The most common contact-related output file, RCFORC, is produced by including a *DATABASE_RCFORC command in the input deck. RCFORC is an ASCII file containing resultant contact forces for the slave and master sides of each contact interface. The forces are written in the global coordinate system. Note that RCFORC data is not written for single surface contacts as all the contact forces from such a contact come from the slave side (there is no master side) and thus the net contact forces are zero. To obtain RCFORC data when single surface contacts are used, one or more force transducers should be added via the *CONTACT_FORCE_TRANSDUCER_PENALTY command. A force transducer does not produce any contact forces and thus does not affect the results of the simulation. A force transducer simply measures contact forces produced by other contact interfaces defined in the model. One would typically assign a subset of the parts defined in a single surface contact to the slave side of a force transducer. No master side is defined. The RCFORC file would then report the resultant contact forces on that subset of parts. The ASCII output file NCFORC reports contact forces at each node. The command *DATABASE_NCFORC is required in the input deck to produce such a file. Further, one or more contact print flags must be set (see SPR and MPR on Card 1 of *CONTACT). Only those surfaces whose print flag is set to a value of 1 will have their nodal contact force output to the NCFORC file. By including a *DATABASE_SLEOUT command, contact interface energies are written to the ASCII ouput file SLEOUT. In cases where there are two or more contact interfaces in a model and the global statistics file (GLSTAT) indicates a problem with contact energy, such as a large negative value, the SLEOUT file is useful for isolating which contact interfaces are responsible. For general information on interpreting contact energies, see the LS-DYNA Theory Manual, Section 23.8.4. In some cases, it can be very useful to visualize contact surfaces and produce fringe plots of contact stress both in directions normal and tangential to the contact surface. To do this, a binary interface file must be written by (1) including a *DATABASE_BINARY_INTFOR command in the input deck, (2) setting one or more contact print flags as detailed above, and (3) including the option s=filename on the LS-DYNA execution line where filename is the intended name of the binary database. The database can be postprocessed using LS-POST.

 

 

 

 

 

 

 

Contact parameters

There are several contact-related parameters in LS-DYNA that can be used to modify or, in many cases, improve contact behavior.

The default settings for these parameters should be used as a starting point, but often non-default values are appropriate depending on the behavior of the contact. The following sections describe the most common contact parameters and make general recommendations regarding their use. Contact parameters may be set using the commands *CONTROL_CONTACT*CONTACT, and *PART_CONTACT. Certain parameters may be set using more than one command and so a command hierarchy must exist. Parameters set with *CONTROL_CONTACT redefine default settings for all contacts in the model. Contact parameters set in *CONTACT_ will override default settings for individual contacts. Contact parameters set in *PART_CONTACT supercede settings in *CONTACT for contact involving a specific part.

Thickness offsets, SLTHK (card 1, *CONTROL_CONTACT and Optional Card A in *CONTACT_option) AUTOMATIC (*CONTACT_option)

In crashworthiness analysis, sheet metal components are represented using shell elements with the nodal points at the mid-plane surface. Each shell has a thickness, ts, that by default is equal to the thickness of the sheet metal. When these components are included in the contact treatment, shell thickness offsets are used to project the mid-surface of the shell to create the surface for contact. The choice of the contact type determines whether shell thickness offsets are considered.

In LS-DYNA the non-automatic contact types:

  • *CONTACT_SURFACE_TO_SURFACE
  • *CONTACT_NODES_TO_SURFACE
  • *CONTACT_ONE_WAY_SURFACE_TO_SURFACE

use two different treatments depending on the parameter SHLTHK. This parameter can be specified globally on the *CONTROL_CONTACT card and locally for a given contact definition on optional card B of the *CONTACT input. If SHLTHK=0, an incremental search technique is used to determine the closest master segment and shell thickness offsets are not included. If SHLTHK=1, LS-DYNA considers the shell thickness offsets for deformable nodes but ignores the offsets for the nodes of rigid bodies. If SHLTHK=2, then LS-DYNA considers the thickness for both deformable and rigid nodes. For SHLTHK set to 1 or 2 a global bucket search is used to identify contact pairs. After contact is established, incremental searching is used to track the position of the slave nodes on the master surface. An advantage of global bucket searching is that the master and slave surfaces can be disjoint. This is impossible if incremental searching is used since incremental searching assumes that the contact surfaces are fully connected. In these contact types, it is important to orient the contact segment normals, based on the right-hand-rule, towards the contacting surface before the calculation begins. This is called oriented contact. An optional automatic orientation feature may be invoked using the parameter ORIEN on the *CONTROL_CONTACT card; however, for this option to work a gap must exist between opposing shell mid-plane surfaces. AUTOMATIC and single surface contact types always consider shell thickness offsets as shown in Figure 6.1. These contact types use both global bucket sorting and local incremental searching in determining the contact pairs. AUTOMATIC contacts are generally more robust than their nonautomatic counterparts since this contact type has no orientation requirement, i.e., contiguous segments do not obey the right-hand-rule. This is important in crash analysis since metal part can fold over and change the orientation. The contact search algorithm checks for penetration from either side of the shell mid-plane.

Shell Thickness Offset Recommendations

The AUTOMATIC contact types, which consider shell thickness offsets, are recommended for impact and crash analysis. If it is desired that shell thickness offsets of rigid components be disregarded, a non-automatic contact type may be used with the parameter SHLTHK set to 1 in either *CONTROL_CONTACT or on Optional Card B of *CONTACT. Additionally, it is important to ensure that the finite element mesh is constructed so that the shell mid-plane surfaces of the opposing parts are set apart by at least (ts+tm)/2 with meshes of similar density around sharp changes in curvature. If this condition is not satisfied, LS-DYNA will issue warning messages to indicate that penetrations were detected and that the penetrating nodes were moved to eliminate the penetrations. Sometimes the modification of the geometry can change the results. In version 960 of LS-DYNA, an option exists whereby penetrating nodes are not moved but rather the initial penetrations become the baseline from which additional penetration is measured. This option of tracking initial penetrations is invoked by setting the parameter IGNORE equal to 1 on Card 4 of *CONTROL_CONTACT or on optional card C of *CONTACT. We recommend that this option be used in most calculations. See Sections 6.4 and 6.5 for more on shell thickness offsets. In those sections, the term “contact thickness” refers to the magnitude of the shell thickness offsets.

Contact Sliding Friction, FS and FD (card 2, *CONTACT_option)

Contact sliding friction in LSDYNA is based on a Coulomb formulation and uses the equivalent of an elastic-plastic spring. Friction is invoked by giving non-zero values for the static and dynamic friction coefficients, FS and FD, respectively, in the *CONTACT or *PART_CONTACT input. For a detailed description of the frictional contact algorithm, please refer to Section 23.8.6 in the LS-DYNA Theory Manual.

Contact Sliding Friction Recommendations

figure 6_1

Figure 6.1 Automatic Contact Segment Based Projection

When setting the frictional coefficients, physical values taken from a handbook such as Marks, provide a starting point. Note that to differentiate static and dynamic friction, FD should be less than FS and the decay coefficient DC must be nonzero. For numerically noisy problems such as crash, the static and dynamic coefficients are frequently set equal to avoid the creation of additional noise. The decay coefficient determines the manner in which the instantaneous net friction coefficient is ransitioned from FS to FD. The parameter, VC, provides a means to limit the frictional contact stress based on the strength of the material. The suggested value for VC is SIGY/sqrt(3) where SIGY is the minimum yield stress of the materials in contact. In LS-DYNA, version 960, the optional parameter FRCENG on card 4 of *CONTROL_CONTACT may be set to write the frictional contact energy to the binary interface database (*DATABASE_BINARY_INTFOR). Routinely, one automatic, single-surface contact with numerous dissimilar materials, are used in full vehicle simulations. In these cases, using a uniform value for FS and FD may be inappropriate. In such instances, it is recommended that the frictional parameters be specified part by part using the contact option in the part definition, *PART_CONTACT. It is helpful in understanding the sensitivity contact friction in a calculation by making two runs utilizing lower-bound and upper-bound friction coefficients.

6.3 Penalty Scale Factors, SFS and SFM (card 3, *CONTACT_option)

So-called penalty scale factors provide a means of increasing or decreasing the contact stiffness. SLSFAC in *CONTROL_CONTACT scales the stiffness of all penalty-based contacts, which have the parameter SOFT set equal to 0 or 2. SLSFAC is applied cumulatively with SFS, i.e., the actual scale factor is the product of SFS and SLSFAC, the slave penalty scale factor, or SFM, the master penalty scale factor, defined on card 3 of the *CONTACT input. SSF, when defined in *PART_CONTACT, is cumulative with the aforementioned penalty scale factors. For contacts with SOFT=1, the aforementioned penalty scale factors have no affect; rather SOFSCL on optional card A is used to scale the contact stiffness when SOFT=1. (SOFT is the first parameter specified on optional card A of *CONTACT.)

Penalty Scale Factors Recommendations

The default values (SFS=SFM=1.0; SLSFAC=0.1) generally work well for contact between similarly refined meshes of comparably stiff materials. For contacts involving dissimilar mesh sizes and dissimilar material constants, non-default values penalty scale factors may be necessary to avoid the breakdown of contact if SOFT=0. Generally, a better alternative than setting scale factors is to set SOFT=1 and leave all penalty scale factors at their default values.

Contact Thickness SST and MST (card 3, *CONTACT_option)

SST and MST on card 3 of *CONTACT allow users to directly specify the desired contact thickness. When the default value of SST=MST=0, is used, the contact thickness is equal to the element thickness specified in the *SECTION_SHELL card.

Contact Thickness Recommendations

Nonzero values of SST and MST are sometimes used to decrease the contact thickness and thus eliminate initial penetrations. This is a poor substitute for accurate mesh generation. When using nonzero values of SST and MST, it is highly recommended to use reasonable values. Specifying a very small thickness value, such as 0.1 mm, will result in contact breakdown owing to the fact that contact thickness goes into determining the maximum penetration allowed before the contact releases a penetrating node. Often, by increasing the contact thickness, breakdown of contact involving very thin materials can be averted. Based on experience, SST and MST should not be less than 0.6-0.7 millimeters. Since nonzero values of SST and MST are applied to all the parts defined in the contact, it may be more prudent to use the OPTT or SFT parameter in *PART_CONTACT to control the contact thickness for individual parts in cases where many parts of widely ranging thickness are included in a single contact.

Contact Thickness Scaling , SFST and SFMT, (card 3, *CONTACT_option)

As an alternative to directly specifying the contact thickness as described above, SFST and/or SFMT may be defined to serve as contact thickness scale factors. These factors are applied to the shell thickness specified in *SECTION_SHELL in order to obtain a contact thickness. The default values of SFST and SFMT are 1.0.

Contact Thickness Scaling Recommendations

The same concepts discussed in Contact Thickness Recommendations apply here. Care must be taken though not to assign contact thickness scale factors so small as to result in a contact thickness that is less than 0.6-0.7 mm.

Viscous Damping, VDC (Card 2, *CONTACT_option)

The viscous contact damping parameter, VDC, on card 2 of *CONTACT is zero by default. Originally, contact damping was implemented to damp out the oscillations that existed normal to the contact surfaces in sheet metal forming simulations. It has been found that contact damping is often beneficial in reducing high-frequency oscillation of contact forces in crash or impact simulations.

Viscous Damping Recommendations

In contacts involving soft materials such as foams and honeycombs, frequent instabilities exist due to contact oscillations. Using a value of VDC between 40-60 (corresponding to 40 to 60% of critical damping), it is found that the model stability improves; however, it may be necessary to reduce the scale factor for the time step size. Generally, a smaller value of 20 is recommended when metals, which have similar material constants, interact.

Contact Segment Extension, MAXPAR (Optional Card A, *CONTACT_option)

MAXPAR on Optional Card A of *CONTACT controls the enlargement of each contact segment that is needed to combat an inherent flaw in segment-based projection. This parameter is no longer used in the AUTOMATIC contact options, except for *AUTOMATIC_GENERAL, starting with version 950d of LS-DYNA. Figure 6.2 shows the contact surface that is projected from the shell mid-plane when using the segment-based projection scheme. It can be seen that at corners of convex surfaces, an open space or gap is present in the contact surface through which a slave node could freely enter without any contact detection. This can result in contact instability, negative contact energy, etc. due to a sudden, large penetration of a node that has entered through a gap. To combat this problem, the contact surface is automatically extended a slight distance parallel to the plane of the contact segment (as well as projected normally from the segment). This slight extention serves to close the gap in the contact surface. In versions starting with 950d, a cylindrical surface is created in the valley which is used as the contact surface with the forces acting normal to the surface.

Segment Extension Recommendations

The default value of MAXPAR (1.025) works well for most analyses, as most sheet metal components are not much greater than 3-4 mm. However, contact instabilities may develop when a part with a very large thickness (> 5-10mm) or having an angular surface is present in the contact definition. Such an instability may be corrected by reducing the contact thickness (discussed in earlier sections) or by increasing the segment enlargement parameter MAXPAR (to as high as, but no greater than, a value of 1.2). Refining the mesh to reduce sharp angles in the contact surface will also help. A certain cost penalty is paid for MAXPAR values greater than default.

Bucket-Sort Frequency, BSORT (Optional Card A, *CONTACT_), NSBCS, (Card 2, *CONTROL_CONTACT)

Bucket sorting refers to a very effective method of contact searching to identify potential master contact segments for any given slave node. This sorting is an expensive part of the contact algorithm so the number of bucket sorts should be kept to a minimum to reduce runtime. If thickness offsets are considered, then all contact types use the bucket sort approach to track the most probable contacting segments. BSORT specifies the number of time steps between bucket sorts. Depending on the contact type, the default bucket sort interval is between 10 and 100 cycles. Except for high speed impact, this interval is almost always adequate. The contact bucket searching frequency should increase, i.e., BSORT should be reduced, if nodes move from one disconnected surface to another in short time intervals or if the surface is folding onto itself. If two relatively smooth simply-connected surfaces are moving across each other without folds, the bucket sorting can be done at larger intervals. Note that if the surfaces are more than several segment widths away from each other, no information is stored related to future contact, and later bucket searching is required to pick up future contacts. Once a slave node is in contact, local searching tracks the motion, and bucket sorting for the nodes, which are in contact, is not necessary.

Bucket-Sort Frequency Recommendations

In certain contact scenarios where contacting parts are moving relative to each other in a rapid fashion, such as airbag deployment, more frequent (than default) bucket sorting intervals may improve the contact behavior. A tell-tale sign inadequate bucket sorting is the appearance of certain penetrating nodes inexplicably being bypassed in the contact treatment. In such cases, using the BSORT parameter

figure 6_2

a) MAXPAR = 1.0 b) MAXPAR = 1.2

Figure 6.2 Segment extension using MAXPAR. This option is now obsolete in the AUTOMATIC contact types.

in *CONTACT or NSBCS in *CONTROL_CONTACT, the user can decrease the cycle interval between bucket sorts. Rarely will a value of less than 10 be required.

6.9 Maximum Penetration, PENMAX (Optional card B, *CONTROL_CONTACT), XPENE (Card 2, *CONTROL_CONTACT)

To avoid instability in models, slave nodes that penetrate too far are eliminated from the contact algorithm; however, they remain in other calculations. This is done so that very high forces, which are proportional to large penetration values, are not applied to the penetrating nodes that might lead to instabilities. It’s also necessary for contacts that consider shell thickness offsets to prevent a sudden reversal in direction of contact force as a penetrating node passes through the shell midplane. In non-automatic types and SHLTHK=0, the default maximum penetration is set to 1e+20. In other words, no nodes are released at all. When SHLTHK=1 or 2, the XPENE parameter determines the nodal release criteria and is given as follows:

  • Max Distance (Solids) = XPENE (default=4.0) * (thickness of the solid element), SHLTHK=1
  • Max Distance (Solids) = 0.05 * (thickness of the solid element), SHLTHK=2
  • Max Distance (Shells) = XPENE (default=4.0) * (thickness of shell element), SHLTHK=1
  • Max Distance (Shells) = 0.05 * (minimum diagonal length), SHLTHK=2

In AUTOMATIC types and single surface, excluding AUTOMATIC_GENERAL, the maximum allowable penetration is a function of PENMAX that is set to a default value of 0.4 (40%). The maximum allowable penetration in these cases are shown below:

  • Max Distance = PENMAX * (thickness of the solid)
  • Max Distance = PENMAX * (slave thickness + master thickness)

For *AUTOMATIC_GENERAL only, the default value of PENMAX is set to 200 and provides an almost no nodal release criteria.

6.9.1 Maximum Penetration Recommendations

It is generally recommended that parameters affecting maximum penetration not be changed from the default values. If nodes penetrate too far and are released, the preferred solution is to increase the contact stiffness, change the penalty formulation (SOFT), or increase the contact thickness.

Modeling guidelines for full vehicle contact

Crash analysis involving a full vehicle incorporates contact interactions between all free surfaces. This is quite expensive since 20-30 percent of the total calculation CPU time is used by the contact treatment.

One of the challenging aspects of contact modeling in crash analysis is the handling of interactions between structural metallic parts and non-structural components typically made from foam and plastic. This is especially important when occupants are included in the model. Another challenge is handling contact at corners or edges of geometrically complex parts. Guidelines should be followed to achieve stability in contact as well as reasonable contact behavior. Some of the modeling practices based on experience are discussed below.

Global or local contact

Historically, many individual contact definitions were used for the treatment of contact. The development and implementation of a robust single surface type of contact has changed the way engineers model the contact today. From the standpoints of simplicity in preprocessing, numerical robustness, and computational efficiency, it is now usually advantageous to forsake the use of numerous contact definitions in favor of ONE single-surface-type contact that includes all parts which may interact during the crash event. We often casually refer to this single contact approach as a global contact approach.

This, however, does not mean that one should always avoid local contact definitions. Frequently, there exist certain areas of the vehicle that require special contact considerations where the global contact definition is observed to fail. In such instances the user is encouraged to define local contact interfaces with non-default parameters that would best suit the contact condition.

AUTOMATIC_SINGLE_SURFACE or AUTOMATIC_GENERAL

Though both contact algorithms belong to the single surface contact type, several key parameters distinguish these two contact types. Table 7.1 highlights the important differences.

Parameters AUTOMATIC_SINGLE_SURFACE AUTOMATIC_GENERAL
PENAX 0.4 100
BSORT frequency Every 100 cyles Every 10 cycles
SEARCH DEPTH 2 3
Shell Exterior Edge Treatment No Yes
Beam to Beam Contact No Yes

Table 7.1 Difference between *AUTOMATIC_SINGLE_SURFACE (13) and *AUTOMATIC_GENERAL (26)

Of the two single surface contact types listed in Table 7.1, *AUTOMATIC_GENERAL is computationally more expensive owing to its additional capabilities and its more frequent and thorough contact search.

The *AUTOMATIC_SINGLE_SURFACE contact option is recommended for global contact. To treat special contact conditions where shell edge-to-edge or beam-to-beam contact is anticipated, the additional use of the *AUTOMATIC_GENERAL contact in localized regions is recommended. *AUTOMATIC_GENERAL contact should be used sparingly and only where conditions dictate its use. One advantage of the *AUTOMATIC_SINGLE_SURFACE contact starting with LS-DYNA version 950d is in its more rigorous treatment of interior sharp corners within the finite element mesh and in the handling of triangular contact segments; consequently, the *AUTOMATIC_SINGLE_SURFACE contact is usually superior for parts meshed from triangular and tetrahedron elements. In future version of LS-DYNA, the *AUTOMATIC_GENERAL option will also include these improvements.

Standard penalty-based or soft constraint stiffness method

When several parts of dissimilar mesh sizes and/or dissimilar material properties are included into one global slave set for *AUTOMATIC_SINGLE_SURFACE, the soft constraint stiffness method (SOFT =1) is recommended. The soft constraint method seeks to maximize contact stiffness while also maintaining stable contact behavior. The interacting nodal masses and the global time step are used in formulating the contact stiffness. The segment-based contact method, invoked by setting SOFT=2, calculates contact stiffness much like the soft constraint method but otherwise is quite different. Segment-based contact can often be quite effective where other methods fail at treating contact at sharp corners of parts.

In contrast to a soft constraint approach, the standard penalty-based contact stiffness (SOFT=0) is based on material elastic constants and element dimensions. In foam and plastic materials, the contact stiffness given by the two methods can differ by one or more orders of magnitude. The primary disadvantage of choosing the soft constraint method is its dependence on the global time step. Occasionally, the global time step must be scaled down using the TSSFAC parameter in *CONTROL_TIMESTEP to avoid numerical instabilities in the contact behavior. This results in an increased run time for the entire simulation. As an alternative to reducing the global time step the soft constraint scale factor, SOFSCL, in the *CONTACT definition can be reduced from the default value of 0.1 to 0.04-0.07.

If the standard penalty-based approach in used in a global contact definition, the soft constraint approach can be used locally to handle dissimilar materials in contact. The following are examples where contact behavior may benefit from use of the soft constraint method:

  • Airbag to Steering Wheel
  • Airbag to Occupant
  • Front Tire to SIL
  • Spare tire to neighboring components
  • Foam to structural components

Using a combination of both contact stiffness methods may promote good contact behavior without having to reduce the global time step.

Definition of slave set

There are several ways to define the slave set for the global contact definition. These include: all parts (this is the default), a set of included parts, a set of excluded parts, or a set of segments. The default, which includes all parts, can sometimes result in obvious instabilities at the beginning of a simulation unless great care is taken in setting up the model to avoid such things as initial penetrations and nonphysical intersections of parts. The option to ignore penetrations on the *CONTROL_ CONTACT keyword (set IGNORE equal to 1) is recommended if care is not taken to eliminate initial penetrations. Many models run perfectly with just one interface definition; others, however, will not run until changes are made to the input, usually by excluding parts or by modifying the finite element mesh to more accurately reflect the physical model. To reiterate, the following methods can be used for defining the global contact definition:

  • All parts (default)
  • Included parts by *SET_PART
  • Excluded parts by *SET_PART. Non-Excluded parts will be considered for contact
  • Segments by *SET_SEGMENT

In addition to the above slave sets, a three-dimensional box, defined using *DEFINE_BOX, may be used to restrict the contact to the parts or segments that lie within the box at the start of the calculation. This will reduce the extent of the contact definition leading to a reduction in contact-associated cpu time.

Friction

When using one global contact that includes several components of the vehicle, a uniform friction coefficient (possibly zero) may be acceptable for initial analyses. However, the use of *PART_CONTACT keyword to specify friction coefficients on a part-by-part basis is recommended when friction is expected to play a significant role. Friction coefficients specified in *PART_CONTACT will override friction coefficients specifed elsewhere if and only if FS in *CONTACT is set to -1.0. Please note that the dynamic friction coefficient FD will have no effect unless a nonzero decay coefficient DC is provided.

Contact

Thickness To reduce the number of initial penetrations, the contact thickness can changed from the default element thickness by using the global SST and MST parameters in *CONTACT. The OPTT parameter in *PART_CONTACT can be used to override SST and MST on a part-by-part basis. The user is cautioned against setting the contact thickness to an extremely small value as this practice will often cause contact failure. In fact, for treating contact of very thin shells, e.g., less than 1 mm, it may be necessary to increase the contact thickness to prevent contact failure.

If a contact surface is comprised of tapered shell elements, then a uniform contact thickness should always be specified. The contact assumes that the segment thickness is constant, which can result in thickness discontinuities between adjacent segments. As a node moves between segments of differing thickness, the interface force will either suddenly drop or increase as a result of the discontinuous change in the penetration distance. This can result in negative contact interface energies.

 

 

 

 

 

Airbag contact

Simulation of airbag deployment and interaction of an airbag with other components may require special contact treatment.

Some of the challenges associated with airbag contact are as follows:

  • High Airbag Nodal Velocity (> 100 m/s)
  • Soft Tissue Properties ( E < 50 Mpa)
  • Small Tissue Thickness ( < 0.5 mm)
  • Frequent Initial Penetrations in Folded Bag
  • Treatment of Airbag Fabric Layers

To promote stability and accuracy in simulating airbag contact, the following contact types and contact parameters are recommended.

Airbag self-contact

When treating airbag self-contact (fabric-to-fabric contact), the use of *CONTACT_AIRBAG_SINGLE_SURFACE is highly recommended. This contact type is based on *CONTACT_AUTOMATIC_SINGLE_SURFACE but has significant modifications to account for the difficulties associated with deployment of a folded airbag.

SOFT=2 is generally recommended (SMP only) to better deal with the many initial penetrations present in a folded airbag and to invoke a segment-to-segment contact search which is often advantageous in dealing with the complex geometry of a folded or partially unfolded airbag. Airbag contact with SOFT=2 is expensive relative to other contact options so to improve cpu performance when using SOFT=2, an additional contact with SOFT=0 or 1 can be implemented as shown in Figure 8.1. By defining two separate contacts and employing contact birthtime and deathtime to switch from the SOFT=2 contact to the SOFT=1 contact when the bag has unfolded, a good combination of contact reliability and efficiency can be acheived.

If the airbag simulation is run using an MPP executable, note that SOFT=2 is not yet available and so SOFT=0 or 1 must be used. For a folded airbag, this will likely mean that a load curve defining the fabric contact thickness versus time will be necessary to transition from a very small thickness in the folded state to a larger thickness as the bag unfolds. This is done to prevent initial penetrations in the folded state and still have good contact behavior during the unfolding process. The contact thickness vs. time curve is identified by LCIDAB on Optional Card A of *CONTACT. As a possible alternative to a time-dependent contact thickness, the user may try invoking the option for tracking of initial penetrations by setting IGNORE=1 on Optional Card C. This latter option is new in version 960 and has not been thoroughly checked out for airbag applications.

Airbag-to-structure contact

During and after airbag deployment, the airbag fabric comes into contact with other parts of the model such as the steering wheel, occupant, instrument panel, door trim components and, in the case of side curtain 4 deployment, the seat. For these contact conditions, a two-way contact such as *CONTACT_AUTOMATIC_SURFACE_TO_SURFACE is generally recommended. In instances when the airbag nodes comprise the slave side in a one-way type contact such as *CONTACT_AUTOMATIC_NODES_TO_SURFACE, the structural nodes are not checked for penetration through the airbag segments. This may result in noticeable penetration of finely-meshed structural components into airbag segments. Single surface contacts such as *CONTACT_AUTOMATIC_SINGLE_SURFACE for airbag-to-structure interaction may be ill-advised as this would result in duplication of self-contact treatment for the fabric.

Difficulties in airbag-to-structure contact are largely associated with significant differences in material bulk moduli (up to 1000x) and very low thickness of the fabric. To avoid premature nodal release triggered by a small fabric thickness, it is recommended that the contact thickness of the fabric be set to a minimum value of 1.0 mm. Since a wide range of materials are involved, the use of SOFT=1 is highly recommended as it eliminates the need to fine-tune penalty scale factors. An example of the overall setup for airbag-related contact is shown in Figure 2.

figure 8_1

Figure 1 Airbag Self Contact Algorithm Switch

figure 8_2

Figure 2 Airbag Contact Definition

 

 

 

 

 

 

Edge-to-edge contact

Most contact types do not check for edge-to-edge penetrations as the search entails only nodal penetration through a segment. This may be adequate in many cases; however, in some unique shell contact conditions, the treatment of edge-to-edge contact becomes very important.

There are several ways to handle edge-to-edge contact; the merits/demerits of each one of these methods are discussed below.

*CONTACT_AUTOMATIC_GENERAL excluding Interior Edges

By default, *CONTACT_AUTOMATIC_GENERAL considers only exterior edges in its edge-to-edge treatment as indicated by Figure 1. An exterior edge is defined as belonging to only a single element or segment whereas interior edges are shared by two or more elements or segments. The entire length of each exterior edge, as opposed to only the nodes along the edge, is checked for contact. As with other penalty-based contact types, SOFT=1 can be activated to effectively treat contact of dissimilar materials.

*CONTACT_AUTOMATIC_GENERAL including Interior Edges

Edge-to-edge contact which includes consideration of interior edges may be invoked in one of two ways. One method takes advantage of the beam-to-beam contact capability of *CONTACT_AUTOMATIC_GENERAL. This labor-intensive approach involves creating null beam elements (*ELEMENT_BEAM*MAT_NULL) approximately 1 mm in diameter (elform=1, ts1=ts2=1,2mm, tt1=tt2=0 in *SECTION_BEAM) along every interior edge wished to be considered for edge-to-edge contact and including these null beams in a separate *AUTOMATIC_GENERAL contact. This is illustrated in Figure 2. The elastic constants in *MAT_NULL are used in determining the contact stiffness so reasonable values should be given. Null beams do not provide any structural stiffness.

A preferred alternative to the null beam approach, available in version 960, is to invoke the interior edge option by using *CONTACT_AUTOMATIC_GENERAL_INTERIOR. A certain cost penalty is associated with this option.

*CONTACT_SINGLE_EDGE

This contact type treats edge-to-edge contact but, unlike the other options above, it treats only edge-toedge contact. This contact type is defined via a part ID, part set ID, or a node set on the slave side. The master side is omitted.

figure 9_1

Figure 1 Interior and Exterior Shell Edges

figure 9_2

Figure 2 Null Beams to treat edge-to-edge treatment

 

 

 

 

 

Rigid body contact

Components for which deformation is negligible and stress is unimportant may be modeled as rigid bodies using *MAT_RIGID or *CONSTRAINED_NODAL_RIGID_BODY. The elastic constants defined in *MAT_RIGID are used for contact stiffness calculations. Thus the constants should be reasonable (properties of steel are often used).

Though there are several contact types in LS-DYNA which are applicable specifically to rigid bodies (RIGID appears in the contact name), these types are seldom used. Any of the penalty-based contacts applicable to deformable bodies may also be used with rigid bodies, and in fact, are generally preferred over the RIGID contact types. Rigid bodies and deformable materials may be included in the same penalty-based contact definition. Constraints and constraint-based contacts may not be used for rigid bodies.

Rigid bodies should have a reasonably fine mesh so as to capture the true geometry of the rigid part. An overly coarse mesh may result in contact instability. Another meshing guideline is that the node spacing on the contact surface of a rigid body should be no coarser than the mesh of any deformable part which comes into contact with the rigid body. This promotes proper distribution of contact forces. As there are no stress or strain calculations for a rigid body, mesh refinement of a rigid body has little effect on cpu requirements. In short, the user should not try to economize in the meshing of rigid bodies.

*CONTACT_ENTITY is an altogether different way of defining an analytic, rigid contact surface which interacts with nodes of deformable bodies. For more information

Comments

No Comments have been Posted.

Post Comment

Please Login to Post a Comment.

Ratings

Rating is available to Members only.

Please login or register to vote.

No Ratings have been Posted.
Render time: 0.71 seconds
10,800,039 unique visits