interpenetration
Answers
-
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"?>
If it is only related to meshing issues, HM has the 'penetration check' panel (Ctrl+F >> penetration)
0 -
Thank you.
My problem is related to a penetration during a compression test. Where I can find this tutorial?0 -
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.
0 -
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"?>
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
0 -
That's how i create the contactsurf
Here the interfaces panel
I need no penetration during a compression test
0 -
0
-
What version o OptiStruct are you using?
Self-contact is available from OS 2017.something (maybe.2)
These are the tutorials from the Help.
0 -
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
0 -
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"?>
0 -
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.
0 -
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.
0
Altair Employee
