🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

interpenetration

User: "LucaC"
Altair Community Member
Updated by LucaC

Hi all, 
is there some way to disable interpenetration between elements of a component? 

Thank you all


p1.PNG.f23b67a0a4dda15f0fb8a010f5d3c22f.PNG

Find more posts tagged with

Sort by:
1 - 11 of 111
    User: "Adriano_Koga"
    Altair Employee
    Updated by Adriano_Koga

    if ?I understood correctly your question, you want to avoid elements to penetrate each other?

     

    If that's the case, you need to specify contacts between your parts. If it is in the same part, then, self-contact is needed:

    <?xml version="1.0" encoding="UTF-8"?>image.thumb.png.ee228206c26c6d89e54e8a83f4accf5a.png

     

    If it is only related to meshing issues, HM has the 'penetration check' panel (Ctrl+F >> penetration)

    User: "LucaC"
    Altair Community Member
    OP
    Updated by LucaC

    Thank you. 
    My problem is related to a penetration during a compression test. Where I can find this tutorial? 

    User: "Adriano_Koga"
    Altair Employee
    Updated by Adriano_Koga

    You need to launch the Help, going in the toolbar Help>>Altair Help Home

     

    Then navigate to OptiStruct Section.

    There will be then tutorials page.

     

    Or try typing the tutorial code or name into the Help search.

     

    I suggest you to look at Altair University and go through a couple non-linear analysis tutorials.

     

    User: "LucaC"
    Altair Community Member
    OP
    Updated by LucaC

    Thank you. I look for that tutorial, but I didn't find it, then i lok for other tutorial
     

    <?xml version="1.0" encoding="UTF-8"?>image.thumb.png.ad4f9af3b986216e2b7cb23f54eed42d.png

    When i run the simulation i get this advice. I created contactsurf with solid faces option. I select the so created contact both for SSID and MSID

     

    image.png.0d88a7bb48bb34360684fd97e0495123.png

    User: "LucaC"
    Altair Community Member
    OP
    Updated by LucaC

    That's how i create the contactsurf

    image.png.c0fafb82a5f0f07ebb89064990306b5f.png

     

    Here the interfaces panel 

    image.png.fbf5660ebae2fdb939f155158a26fa42.png

     

     

    I need no penetration during a compression test

    User: "LucaC"
    Altair Community Member
    OP
    Updated by LucaC

    If you need, here is the model 

    Unable to find an attachment - read this blog

    User: "Adriano_Koga"
    Altair Employee
    Updated by Adriano_Koga

    What version o OptiStruct are you using?

    Self-contact is available from OS 2017.something (maybe.2)

    These are the tutorials from the Help.

     

    Unable to find an attachment - read this blog

    User: "LucaC"
    Altair Community Member
    OP
    Updated by LucaC

    I'm using Hypermesh 2019.1

    Could you link me the hm model of OS-T_1540 ?
    I'm following the guide you linked me, but I can't find the Self contact  option. 
    It says 'For Slave (SSID), select Self contact.'
    Where it could be ?

    That's what I see

    image.png.1036533769b0784c449b254bf62f0d72.png
     

    User: "Adriano_Koga"
    Altair Employee
    Updated by Adriano_Koga

    the tutorial is based on HW2020, where self contact is already available inside HyperMesh environment.

    In 2019.1 it should be used like you did, or using it as slave only.

     

    i've made a few modifications in your model, but essentially it was fine.

    I've run OS2019.2.2

    <?xml version="1.0" encoding="UTF-8"?>SELF_CONTACT.gif

    Unable to find an attachment - read this blog

    User: "LucaC"
    Altair Community Member
    OP
    Updated by LucaC

    Thank you Adriano.
    I'm trying to run a different model using a set of loadcollector like yours. When I run the simulation, ig gives me that advice.

     

    *** ERROR # 4965 ***
     Maximum number of time increment cutbacks reached,
     analysis aborted.
     
     ANALYSIS COMPLETED.
      
     *** SOME ERRORS WERE REPORTED DURING THE RUN,
     *** PLEASE VERIFY RESULTS AS THEY MAY BE INVALID.
      
     
     *** PROGRAM STOPPED: FATAL ERROR(s) ENCOUNTERED.
      

    User: "Adriano_Koga"
    Altair Employee
    Updated by Adriano_Koga

    this error means convergency issue in your solution.

    It can be caused by some different causes.

     

    Try to run your model and include control card PARAM,NLMON,DISP.

    This will generate an additional H3D file showing what is happening at each increment, which might help you to identify where your issue is coming from.

    Additionally, there will be a more detailed .out file (name_nl.out) that gives you aditional information as well.