How to set interface type 2 with no Warning ?

Wisawanart
Wisawanart Altair Community Member
edited October 2020 in Community Q&A

Hi

          I've been trying to set up the drop test tower simulation comprising of 8 components.

All of the components are SOLID, I have faced with the difficulty to connect those components appropriately

then,  I decided to use the interface type 2 as the connectors. As a result, during running RADIOSS, it showed up

the 10 warnings as below.

       1.   How to set this kind of interface with the suitable connection (Which parameter ?), just connect them instead of being the equivalent node.

       2.   I defined the BC as Solid symmetry and based fix, both of them cause the incompatible kinematic condition, how to solve?

 

WARNING ID: 194
** WARNING IN HIERARCHY REFERENCE
DESCRIPTION :
   -- NODE GROUP ID: 12
   -- BC_Gravity TITLE: PART
   REFERENCE TO UNEXISTING  ID=80
 .. BOUNDARY CONDITIONS
 .. INITIAL VELOCITIES
 .. DOMAIN DECOMPOSITION
 .. ELEMENT GROUPS
 .. INTERFACES
 .. INTERFACE BUFFER INITIALIZATION
WARNING ID :         1079
** WARNING : CHECK TIED INTERFACE
WARNING ID :         1157
** WARNING : TIED INTERFACE
WARNING ID :         1157
** WARNING : TIED INTERFACE
WARNING ID :         1157
** WARNING : TIED INTERFACE
 .. RIGID BODIES
 .. RETURNS TO DOMAIN DECOMPOSITION FOR OPTIMIZATION
 .. DOMAIN DECOMPOSITION
 .. ELEMENT GROUPS
 .. INTERFACES
 .. INTERFACE BUFFER INITIALIZATION
WARNING ID :         1079
** WARNING : CHECK TIED INTERFACE
WARNING ID :         1157
** WARNING : TIED INTERFACE
WARNING ID :         1157
** WARNING : TIED INTERFACE
WARNING ID :         1157
** WARNING : TIED INTERFACE
 .. RIGID BODIES
 .. ELEMENT BUFFER INITIALIZATION
WARNING ID :          312
** INCOMPATIBLE KINEMATIC CONDITIONS IN MODEL
DESCRIPTION :
    44 INCOMPATIBLE KINEMATIC CONDITIONS IN MODEL
 .. GEOMETRY PLOT FILE
 .. PARALLEL RESTART FILES GENERATION
     TERMINATION WITH WARNING
     ------------------
              0 ERROR(S)
             11 WARNING(S)
PLEASE CHECK LISTING FILE FOR FURTHER DETAILS

 

<?xml version="1.0" encoding="UTF-8"?>sss.jpg

<?xml version="1.0" encoding="UTF-8"?>dasd.PNG

<?xml version="1.0" encoding="UTF-8"?>sdsds.jpg

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited May 2018

    Hi,

     

    For tied contact use a slave node set and master surface instead of using surfaces and both master and slave and check if that helps. 

  • Wisawanart
    Wisawanart Altair Community Member
    edited May 2018

    Hi

    As the previous figure, I used slave node and master surface (Node to Surface) for all of the contact pairs.

     

    Best regards

     

  • gopal_rathore
    gopal_rathore Altair Community Member
    edited May 2018

    hi,

    You can run new model checker of hypercrash to identify the warning part. Also are you using IIgnore:1 in type 2 parameter, this will remove slave node not projecting on contact surface, this can also be displayed a warning

     

    If you have run the model and is it running fine ? I meant are you getting appropriate results with it

Categories