07 KinematicConditions Radioss Intro V2019 MAR29-2019

ALTAIR RADIOSS V2019 – INTRO TO RADIOSS FOR IMPACT ANALYSIS
CH7 – KINEMATIC CONDITIONS

© 2019 Altair Engineering, Inc. Proprietary and Confidential. All rights reserved.
Altair Radioss, v2019
CHAPTER 7: KINEMATIC CONDITIONS
7. Kinematic Conditions
• Tied Contact /INTER/TYPE2
• Rigid Walls /RWALL
• Rigid Bodies /RBODY
• Boundary Conditions /BCS
• Imposed Displacement /IMPDISP
• icoor for cylindrical coordinate system
• /SKEW
• Imposed Velocity /IMPVEL
• Incompatible Kinematic Conditions
• Exercise 7: Three-Point Bending
2
TIED CONTACT /INTER/TYPE2

• Tied Contacts define an interface that kinematically connects slave nodes to a master
surface. It can be used to connect coarse and fine meshes, model spotwelds, rivets, etc.
Tied contact interface /INTER/TYPE2

(between solid spotweld and sheet metal)
3
TIED CONTACT /INTER/TYPE2

• A tied contact is defined by a group of slave nodes and a master surface
• The slave nodes are tied to the master surface within a defined search tolerance, dsearch
• Warnings are displayed in the starter output file (runname_0000.out) if a slave node cannot
find a master segment within the search tolerance
dsearch
4
TIED CONTACT /INTER/TYPE2: FORMULATIONS

Spotflag Formulation Usage Limitation / Advantage
1 Kinematic Optimized for spotwelds or rivets Mass is added to master surface
Kinematic option can lead to

5 Kinematic Default
incompatibilities
Formulations with plastic behavior and Kinematic contact until plastic

20, 21, 22 Kinematic
failure phase
No moments transmitted from

25 Penalty Only forces transmitted
slave to master
Automatic switch to penalty
Kinematic /
27 Similar to Spotflag =5 formulation for incompatible
Penalty
kinematic conditions.
Similar to Spotflag =1, Optimized for Automatic switch to penalty
Kinematic /
28 spotwelds or rivets formulation for incompatible
Penalty
kinematic conditions.
5
TIED CONTACT /INTER/TYPE2: PENALTY / KINEMATIC FORMULATIONS

• Slave nodes using the kinematic formulation are tied using kinematic equations and can
only be tied to 1 master segment.
• Slave nodes using the penalty formulation are tied using a spring and can be tied to
multiple master segments.
• Spotflag = 27, 28 use the kinematic formulation but automatically switch to penalty for
slave nodes tied to two master segments
6
TIED CONTACT /INTER/TYPE2: IGNORE OPTION
Ignore Action
0 No deletion of slave nodes (default)
Slave nodes with no master segment found during the Starter are deleted from the
1
interface
Slave nodes with no master segment found during the Starter are deleted from the
2,3
interface with different methods to define the maximum search distance
The flag Ignore is available to automatically remove all slave nodes which can not be projected
onto the master surface
7
TIED CONTACT /INTER/TYPE2: DELETION OPTION
Idel2 Action
0 Default, set to the value defined in /DEFAULT/INTER/TYPE2.
1 The kinematic condition is suppressed on slave node if the master element is deleted
1000 No deletion of slave nodes (default)
In case failure (rupture of the shell element) is defined on the master side of the interface, it is
necessary to update the interface in order to release kinematic condition between the slave
node and the deleted element.
Logic with defaults:
• If Idel2 = 0, then refer to /DEFAULT/INTER/TYPE2
• If Idel2 = 0 in /DEFAULT/INTER/TYPE2 (or /DEFAULT/INTER/TYPE2 doesn’t exist), then Idel2 = 1000
8
TIED CONTACT /INTER/TYPE2: CARD IMAGE
Slave nodes with no master Idel2 set to delete master shell

projection ignored elements if they rupture
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/INTER/TYPE2/2
SPOTWELD
# Slav_id Surf_id Ignore Spotflag Level Isearch Idel Dsearch
1014 1015 1 0 0 0 1 0
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
Default value for dsearch is the average

size of the master segments
Spotflag set to default
kinematic method
9
QUESTIONS & ANSWERS

Q: How is the default Type2 interface different than the ones described
in Chapter 6: Interface (Contact) Modeling?
A: The default Type2 interface is a kinematic condition, where the

velocity of the node is kinematically tied to the master surface. The
other interfaces use a penalty method. (Type2 can be switched to
penalty method with Spotflag=25)
10
7. Kinematic Conditions • Incompatible Kinematic Conditions
• Tied Contact /INTER/TYPE2 • Exercise 7: Three-Point Bending
• /SKEW
11
RIGID WALLS /RWALL

• Rigid Walls allow for an easy way to define an interface between a rigid surface and nodes
of a deformable body
PLANE – Infinite
planar rigid wall
Slave nodes
CYL – Infinite
cylindrical rigid wall
12
RIGID WALLS /RWALL: FOUR TYPES

slave
1. Infinite plane nodes
2. Infinite cylinder of diameter Ф point M or Node N
3. Sphere of diameter Ф
M(N) M1 defines axis
Sphere
4. Parallelogram
point M1
slave
nodes
M(N) M1 defines n n = M M1 X M M2
point M or Node N
Infinite Plane Infinite Cylinder Parallelogram
13
RIGID WALLS /RWALL

• A Rigid Wall is defined by a Surface Type and a group of Slave Nodes
• The slave nodes to a rigid wall can be defined as a group of nodes and/or as nodes initially
at a distance less than the distance (Dsearch) from the rigid wall
• Each wall can be fixed (point M) or moving (node N)
• A Rigid Wall is a Kinematic Condition
• If a slave node penetrates the rigid wall surface a new velocity is computed
• From this velocity, the impulse and rigid wall force are determined
14
RIGID WALLS /RWALL: EXAMPLE CARD IMAGES

• Example of fixed infinite planar rigid wall:
/RWALL/PLANE/3
Floor
# N SLIDE gr_nod1 gr_nod2
0 633 0
# Distance Friction Diameter Ffac Ifq
0 0 0 0 0
# Xm Ym Zm
-1500 0 0
# Xm1 Ym1 Zm1
-1500 0 1
• Example of spherical rigid wall with mass and initial velocity:

/RWALL/SPHER/1
PUNCH
# N SLIDE gr_nod1 gr_nod2
4067 0 5 8
# Distance Friction Diameter Ffac Ifq
0 0 12.7 0 0
# Mass Vx_0 Vy_0 Vz_0
5.0 0 0 -678.2
15
RIGID WALLS /RWALL: LIMITATIONS & SOLUTION

• Some limitations with Rigid Walls
• Can only be fixed or have initial velocity – may want to move rigid object with an imposed displacement
function
• Can result in Incompatible Kinematic Condition – a result of nodes belonging to another kinematic
condition and the rigid wall
• Solution
Best practice is to use rigid body connected to a simple mesh representing the rigid object
• Easy to define more arbitrary shapes
• Can impose displacements, velocities according to function
• Removes issue with Incompatible Kinematic Conditions
16
• /SKEW
17
RIGID BODY /RBODY

• A Rigid Body constrains a set of nodes to move together with no relative motion and can
be used to simplify the modeling of non-deformable objects
Simulation switches all nodes to rigid body Rigid Body turned off just
during free flight for CPU efficiency before impact
18
RIGID BODY /RBODY

Input master node
• A Rigid Body is defined by a set of slave nodes and a location
master node
• Mass and inertia may be added to the initial master
node location
• By default the master node is moved to the center of
mass of all nodes
• Best practice is to create a master node that is not
attached to anything
• A Rigid Body is a kinematic condition
• No relative motion is allowed between the nodes
• A kinematic condition is applied on each slave node for all Calculated rigid body center of mass
directions
19
RIGID BODY /RBODY: SUMMARY OF ICOG ACTION

• The ICoG option chosen depends on application and desired behavior.
Master Node
ICoG COG Rigid Body Mass
Location
Computed using master Moved to computed Mass Entered +
1
and slave nodes COG Slave Node Mass
Computed based on Moved to computed Mass Entered +

2
slave nodes only COG Slave Node Mass
COG put at master node Mass Entered +

3 Not moved
coordinates Slave Node Mass
COG put at master node

4 Not moved Mass Entered
coordinates
20
RIGID BODY /RBODY: TYPICAL APPLICATIONS

• Rigid Body covering a part of a finite element model
• The center of gravity is computed by taking into account the slave node mass; the master
node is moved to the computed center of gravity, added mass and inertia are placed at the
center of gravity
ICoG = 2
21

• Rigid Body representing a non-modeled component
• The center of gravity is set at the master node coordinates; added mass and inertia are put
on center of gravity. The slave node mass and inertia are ignored. The master node is not
moved.
Powertrain mass and inertia

defined along with master
node at specified CG
ICoG = 4
22

• Rigid body used to connect two or more parts
J 11 + J 22
J=0 J=
xx J=
yy J=
zz
3
A rigid body made of two slave

nodes requires using the spherical
inertia flag (Ispher =1)
Ispher = 1
Connections between Parts
23
/RBODY: EXAMPLE CARD IMAGE
Set to 1 if /RBODY only

connects 2 nodes
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/RBODY/815
RIGID BODY PRIMARY NODE 815
# RBID ISENS NSKEW ISPHER MASS Gnod_id IKREM ICOG Surf_id
81500 0 0 0 500000 39 0 0 0
# Jxx Jyy Jzz
0 0 0
# Jxy Jyz Jxz
0 0 0
#Ioptoff
0
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
Default is 1: Mass and inertia are added to

master node which is moved to CG computed
using the master and slave node coordinates
24
• /SKEW
25
BOUNDARY CONDITIONS /BCS

• Boundary Conditions define nodal translational and rotational degrees of freedom that are
fixed from moving
Fixed End Symmetric

(1-6) Symmetric Boundary
Boundary (246) (156)
26
BOUNDARY CONDITIONS /BCS

• There are six degrees of freedom at a node that can be constrained:
translation along X
translation along Y
translation along Z
101 110
rotation along X
rotation along Y
#---1----|----2----|----3----|----4----
rotation along Z
/BCS/1
boundary_condition
#trarot skew_id gr_node
• If skew_id is non-zero, then the boundary conditions 101 110 0 1004
are applied with respect to this local skew # BCS NODE GROUP
/GRNOD/NODE/1004
• A Boundary Condition is a kinematic condition in which group_of_nodes
the velocity on a node’s degree of freedom is set to zero 207
#---1----|----2----|----3----|----4----
27
LOCAL COORDINATE SYSTEMS /SKEW/FIX, /SKEW/MOV

• Skew (local coordinate system) is used to define local directions
• Two types of skews are available in Radioss:
Z’ Y’ Z’ Y’
N3
Z N1
Z O’
N2
X’ X’
O Y
Y
X
X
Fixed skew defined by Moving skew defined

coordinates of O’, Y’, and Z’ by 3 nodes N1, N2, and N3
X’ = Y’ x Z’ and
Y’ recomputed as Z’ x X’
28
• /SKEW
29
IMPOSED DISPLACEMENT & VELOCITY /IMPDISP, /IMPVEL

• Imposed Displacements or Velocities define nodal translational and/or rotational degrees of
freedom that are defined to move according to a function
A metal strip is passed through two rollers aiming at reducing its

thickness. Both rollers have an imposed angular velocity.
30
/IMPDISP, /IMPVEL – EXAMPLE CARD IMAGE

#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
/IMPVEL/1
V_Cylindre
# Ifunct DIR Iskew Isensor Gnod_id Iframe Icoor
1 XX 0 0 80 0
# Scale_x Scale_y Tstart Tstop
1 1 0 0
#---1----|----2----|----3----|----4----|----5----|----6----|----7----|----8----|----9----|---10----|
Can specify Cartesian or cylindrical

Rotation about X in this example
coordinates
• The imposed condition will follow the displacement (or velocity) versus time curve defined
by fct_IDT
• The direction is defined by Dir and can be X, Y, or Z in translation,
and XX, YY, or ZZ for rotation
• /IMPDISP and /IMPVEL are kinematic conditions
31
INCOMPATIBLE KINEMATIC CONDITIONS

• A kinematic condition results from using a feature that defines a kinematic (motion)
constraint on node
• These constraints are mutually exclusive for each degree of freedom, and there can be only
one constraint per DOF
• An Incompatible Kinematic Condition (IKC) means that a more than one kinematic condition
has been defined on a node.
• Example starter warning output
SUMMARY OF POSSIBLE INCOMPATIBLE KINEMATIC CONDITIONS :

-----------------------------------------------------
- POSSIBLE INCOMPATIBLE KINEMATIC CONDITIONS BETWEEN:

BOUNDARY CONDITION
RIGID WALL
- POSSIBLE INCOMPATIBLE KINEMATIC CONDITIONS BETWEEN

SEVERAL RIGID
32
EXAMPLE OF INCOMPATIBLE KINEMATIC CONDITION
#---1----|----2----|----3----|----4----|----5----|
/BCS/3
Spherical rigid wall center node
111 111 0 11
/GRNOD/NODE/11
grnodnode
4067
/IMPVEL/2
Imposed velocity in Z-direction
# Ifunct DIR Iskew Isensor Gnod_id Iframe
1 Z 0 11 0
0.0 -1.0 0.0
WARNING id : 312
** WARNING : INCOMPATIBLE KINEMATIC CONDITIONS IN MODEL
1 INCOMPATIBLE KINEMATIC CONDITIONS IN MODEL
SUMMARY OF POSSIBLE INCOMPATIBLE KINEMATIC CONDITIONS :

-----------------------------------------------------
- POSSIBLE INCOMPATIBLE KINEMATIC CONDITIONS BETWEEN:

BOUNDARY CONDITION
IMPOSED ACCELERATION, IMPOSED DEPLACEMENT, IMPOSED VELOCITY
33

• Radioss Starter does not check if the kinematic conditions are orthogonal or if they are
applied simultaneously. In these situations the warning can be ignored.
• Example
• Two rigid bodies with the same slave nodes but they are active at different times so there is no issue.
• Imposed movement defined at with start and end times.
34

• In the first case, a node is slave to a moving rigid wall and also has a fixed boundary
condition. If the wall is moving, it is impossible after impact to respect both conditions.
• In the second case, a node is defined as a slave for two parallel walls that are fixed, there
are no possible incompatible conditions, as the node cannot impact the two walls at the
same time.
35
QUESTIONS & ANSWERS

Q: Why is it important to remove true incompatible kinematic
conditions?
A: The behavior of the simulation may not be as expected. Depending

on which kinematic condition gets processed first, different behaviors
could result.
36
EXERCISE 7: THREE-POINT BENDING

File Name and Location
…\STUDENT-EXERCISE\
Ex_07_3PBENDING\BENDING_0000.rad
Objectives, see also HM and HC manual

• Simulate a 3-point bending event
• Review the output files for warnings or errors.
• Review the animation results in HyperView
Hints (1/7)
• UNITS: Length (mm), Time (s), Mass (ton), Force (N) and
Stress (MPa)
• Only one half of the model is modelled because it is
symmetric.
37

Hints (2/7)
• Create law 1 elastic material named Rigid Material
(ρ = 8e-09, E = 208000, ν = 0.29) and assign to
Impactor and Support parts
• Create a Piecewise Linear law 36 material named Shell
Material and assign for Inner, Outer, and FLAT parts
• RHO_I = 7.85e-9; E = 210000; ν = 0.29
• Create a function StressStrain curve with the following curve
points: {0,300}, {0.01,310}, {0.013,320}, {0.015,330},
{0.02,340}, {0.025,350}, {0.03,360}, {0.035,370},
{0.04,380}, {0.045,400}
• Add a new Strain Rate item and set Func_ID to StressStrain
• Create a law 28 Honeycomb orthotropic material named
Foam and assign to the HCFoam part
38

Hints (3/7)
• Create a law 28 Honeycomb orthotropic material
named Foam and assign to the HCFoam part
• RHO_I = 3e-10; E_11 = 200; E_22 = 200;
E_33 = 200; E_12 = 150; E_23 = 150; E_31 = 150
• Iflag1 = 1; Iflag2 = 1
• fun_ID11 = Honeycomb_Yfunc11;
fun_ID22 = Honeycomb_Yfunc22;
fun_ID31 = Honeycomb_Yfunc31
• Create a shell property Shell Property and
assign to the Inner, Outer, and FLAT parts
• Ishell = 24; Thick = 0.9119; Ithick = 1; Iplas = 1
• Duplicate Shell Property, rename it to Rigid
Shell and assign this property to Impactor and
Support.
39

Hints (4/7)
• Create a general solid type 14 property HCFoam and assign
to the part HCFoam.
• Isolid = 24
• Create a rigid body Impactor using all the nodes from the
part Impactor
• Create a rigid body Support using all the nodes from the
part Support
40

Hints (5/7)
• Create a BC BCI constraining the master node of the
Impactor rigid in all DOFs except Tz
• Create a BC BCS constraining the master node of the
Support rigid in all DOFs
• Create a BC Symmetry constraining all nodes on the Y-
XZ-plane
• Select nodes from Inner, Outer, and FLAT parts
• Constrain nodes in Ty, Rx, and Rz only
41

Hints (6/7)
• Create an ImposedVelocity for the
Impactor master node
• Direction = Z; funct_IDT = Imposed-Velocity
• ScaleX = 1; ScaleY = -1000
• ScaleX
• Define three Type 7 contacts between
• FLAT (slave) and Support (master)
• Outer (slave) and Impactor (master)
• for all elements in FLAT, Inner, and Outer
• with Igap = 2; Gapmin = 0.45; Inacti = 6; Fric = 0.1;
Iform = 2
42

Hints (7/7)
• Create Interface time history
• Select the Delete Unused dialog box and review the
model to determine that all properties and materials
are assigned.
• Use the Engine File Assistant to define the engine
keywords as shown
• Export the file as 3PBENDING_0000.rad and run in
Radioss
• Review the P3BENDING_0000.out file
wrt warnings
• View the animation results in HyperView and
HyperGraph
43

Results
• Files
3PBENDING.h3d for
contour
3PBENDINGT01 for plot
• Contour
• von Mises (Max) Stress
Contour (MPa) – only
steel parts shown
• Plastic Strain (Max)
Contour – only steel
parts shown
• von Mises Stress (Mid)
Contour (MPa) – only
foam shown
• Plot
• Contact Force for
Impactor Interface
44
QUESTIONS & ANSWERS
45

07 KinematicConditions Radioss Intro V2019 MAR29-2019

Uploaded by

Copyright:

Available Formats

You might also like

07 KinematicConditions Radioss Intro V2019 MAR29-2019

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

07 KinematicConditions Radioss Intro V2019 MAR29-2019

Uploaded by

Copyright:

Available Formats

ALTAIR RADIOSS V2019 – INTRO TO RADIOSS FOR IMPACT ANALYSIS

CH7 – KINEMATIC CONDITIONS

CHAPTER 7: KINEMATIC CONDITIONS

TIED CONTACT /INTER/TYPE2

Tied contact interface /INTER/TYPE2

TIED CONTACT /INTER/TYPE2

TIED CONTACT /INTER/TYPE2: FORMULATIONS

1 Kinematic Optimized for spotwelds or rivets Mass is added to master surface

Kinematic option can lead to

Formulations with plastic behavior and Kinematic contact until plastic

No moments transmitted from

TIED CONTACT /INTER/TYPE2: PENALTY / KINEMATIC FORMULATIONS

TIED CONTACT /INTER/TYPE2: IGNORE OPTION

0 No deletion of slave nodes (default)

TIED CONTACT /INTER/TYPE2: DELETION OPTION

0 Default, set to the value defined in /DEFAULT/INTER/TYPE2.

1000 No deletion of slave nodes (default)

TIED CONTACT /INTER/TYPE2: CARD IMAGE

Slave nodes with no master Idel2 set to delete master shell

Default value for dsearch is the average

QUESTIONS & ANSWERS

A: The default Type2 interface is a kinematic condition, where the

CHAPTER 7: KINEMATIC CONDITIONS

7. Kinematic Conditions • Incompatible Kinematic Conditions

• Tied Contact /INTER/TYPE2 • Exercise 7: Three-Point Bending

• Rigid Walls /RWALL

• Rigid Bodies /RBODY

• Boundary Conditions /BCS

• Imposed Displacement /IMPDISP

• icoor for cylindrical coordinate system

• Imposed Velocity /IMPVEL

RIGID WALLS /RWALL

RIGID WALLS /RWALL: FOUR TYPES

2. Infinite cylinder of diameter Ф point M or Node N

Infinite Plane Infinite Cylinder Parallelogram

RIGID WALLS /RWALL

RIGID WALLS /RWALL: EXAMPLE CARD IMAGES

• Example of spherical rigid wall with mass and initial velocity:

RIGID WALLS /RWALL: LIMITATIONS & SOLUTION

CHAPTER 7: KINEMATIC CONDITIONS

7. Kinematic Conditions • Incompatible Kinematic Conditions

• Tied Contact /INTER/TYPE2 • Exercise 7: Three-Point Bending

• Rigid Walls /RWALL

• Rigid Bodies /RBODY

• Boundary Conditions /BCS

• Imposed Displacement /IMPDISP

• icoor for cylindrical coordinate system

• Imposed Velocity /IMPVEL

RIGID BODY /RBODY

RIGID BODY /RBODY

RIGID BODY /RBODY: SUMMARY OF ICOG ACTION

Computed based on Moved to computed Mass Entered +

COG put at master node Mass Entered +

COG put at master node

RIGID BODY /RBODY: TYPICAL APPLICATIONS

RIGID BODY /RBODY: TYPICAL APPLICATIONS

Powertrain mass and inertia

RIGID BODY /RBODY: TYPICAL APPLICATIONS