HyperWorks Solvers

/INTER/TYPE10

/INTER/TYPE10

 Previous topic Next topic Expand/collapse all hidden text  

/INTER/TYPE10

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

Block Format Keyword

/INTER/TYPE10 - Interface Type 10 - Tied Contact with Void

Description

This interface is tied contact with void. It works similar to /INTER/TYPE7, but:

•Interface stiffness is constant.
•The time step remains constant throughout the contact.
•Force computation is incremental.
•Allows initial penetrations, if they are smaller than the gap.
•After impact, a slave node becomes tied to the master surface.
•A user enabled flag is defined, if rebound is allowed.

Format

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10)

/INTER/TYPE10/inter_ID/unit_ID

inter_title

grnd_IDs

surf_IDm

 

 

 

 

 

Idel

 

 

Stfac

 

 

Gap

Tstart

Tstop

 

 

ITIED

Inacti

VISS

 

 

Bumult
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)

 

grnd_IDs

Slave nodes group identifier

(Integer)

 

surf_IDm

Master 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 master side of 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 slave side of 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 master side of 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 slave side of 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.

Note: Idel =1 and -1 has a higher CPU cost when compared with Idel =2 and -2.

 

Stfac

Interface stiffness scale factor

Default = 0.2  (Real)

 

Gap

Gap for impact activation

(Real)

Tstart

Start time

(Real)

Tstop

Time for temporary deactivation

(Real)

ITIED

Tied option flag

(Integer)

= 0: slave node is tied during impact with possible rebound

= 1: slave node is tied after impact without possible rebound

 

Inacti

Deactivation of stiffness flag

(Integer)

= 0: no action

= 1: deactivation of stiffness on nodes

= 2: deactivation of stiffness on elements

= 3: change node coordinates to avoid initial penetrations

 

VISS

Critical damping coefficient on interface stiffness

Default set to 0.05  (Real)

 

Bumult

Sorting factor

Default set to 0.20  (Real)

 
hmtoggle_plus1Comments
1.In case of SPMD, each master segment defined by surf_IDm must be associated to an element (possibly to a void element).
2.Flag Idel = 1 has a CPU cost higher than Idel = 2.
3.There is no limitation value to the stiffness factor (but a value greater than 1.0 can reduce the initial time step).
4.The default gap is the minimum interface shell thickness.
5.One node can belong to the two surfaces at the same time.
6.Tied interface type 10 does not guarantee the momentum balance, if there is a leverage distance between master and slave (Gap > 0).

See Also:

Interface TYPE10 in User's Guide