HyperWorks Solvers

/INTER/TYPE3

/INTER/TYPE3

Previous topic Next topic Expand/collapse all hidden text  

/INTER/TYPE3

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

Block Format Keyword

/INTER/TYPE3 - Interface Type 3

Description

This interface is used to simulate impacts between two surfaces (with oriented segments). This interface works properly if the two surfaces are simply convex. The main limitations are:

The segment normals must be oriented from one surface to the other
Only works with segments connected to solid or shell elements
The same node may not be put in the two impact surfaces

Format

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

/INTER/TYPE3/inter_ID/unit_ID

inter_title

surf_ID1

surf_ID2

 

 

 

 

 

Idel

 

 

Stfac

Fric

Gap

Tstart

Tstop

IBC

IRS

IRM

 

 

 

 

 

 

 

hmtoggle_plus1Flag Definition

Field

Contents

SI Unit Example

inter_ID

Interface identifier

(Integer, maximum 10 digits)

 

unit_ID

Optional unit identifier

(Integer, maximum 10 digits)

 

inter_title

Interface title

(Character, maximum 100 characters)

 

surf_ID1

First surface identifier

(Integer)

 

surf_ID2

Second surface identifier

(Integer)

 

Idel

Node and segment deletion flag

Default = 0  (Integer)

= 0: no deletion

= 1: when all the elements (4-node shells, 3-node shells, solids) associated to one segment are deleted, the segment is removed from the interface. It is also removed in case of explicit deletion using RADIOSS Engine keyword /DEL in the Engine file.

Additionally, non-connected nodes are removed from the interface.

= 2: when a 4-node shell, a 3-node shell or a solid element is deleted, the corresponding segment is removed from the interface. It is also removed in case of explicit deletion using RADIOSS Engine keyword /DEL in the Engine file.

Additionally, non-connected nodes are removed from the interface.

= -1: same as =1, except non-connected nodes are not removed from the slave side of the interface.

= -2: same as =2, except non-connected nodes are not removed from the slave side of the interface.

 

Stfac

Interface stiffness scale factor. Must be less than 1.0.

Default = 0.2  (Real)

Fric

Coulomb friction

(Real)

 

Gap

Gap for impact activation

(Real)

Tstart

Start time for contact impact computation

(Real)

Tstop

Time for temporary deactivation

(Real)

IBC

Deactivation flag of boundary conditions at impact

(Boolean)

 

IRS

Renumbering flag for segments of the first surface

(Integer)

= 0: if segment is connected to a solid element its normal is reversed if entering the solid element (the segment is renumbered)

= 1: normal is always reversed (segment 1234 is read 2143)

= 2: normal is never reversed (segments connected to a solid element are not renumbered)

 

IRM

Renumbering flag for segments of the second surface (same as IRS)

(Integer)

= 0: if segment is connected to a solid element its normal is reversed if entering the solid element (the segment is renumbered)

= 1: normal is always reversed (segment 1234 is read 2143)

= 2: normal is never reversed (segments connected to a solid element are not renumbered)

 

hmtoggle_plus1Flags for Deactivation of Boundary Conditions: IBC

(1)-1

(1)-2

(1)-3

(1)-4

(1)-5

(1)-6

(1)-7

(1)-8

 

 

 

 

 

IBCX

IBCY

IBCZ

 

Field

Contents

SI Unit Example

IBCX

=1 : Deactivation flag of X boundary condition at impact

(Boolean)

 

IBCY

= 1: Deactivation flag of Y boundary condition at impact

(Boolean)

 

IBCZ

= 1: Deactivation flag of Z boundary condition at impact

(Boolean)

 

hmtoggle_plus1Comments
1.The flag Idel =1 has a CPU cost higher than Idel =2.
2.If IBCX = 1, the boundary condition in X direction is deactivated. IBCY and IBCZ behave the same way respectively in Y and Z direction.
3.Boundary conditions are only deactivated on surf_ID1.

See Also:

Interface TYPE3 in User's Guide

Penalty Method in User's Guide

Interface TYPE3 in Theory Manual