Hypercrash seat simulation

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A

Hello,

 

I am currently carrying out a seat Crash Simulation. I have followed the seat-dummy Simulation process stated in hypercrash tutorials for the same.

When I try to  the run the Simulation, the engine is crashing every time. The seat geometry is very complex and hence meshed seat contains some intersections which I am unable to fix. I think this might be reason for engine Crash.

I am a novice in meshing such complex geometries and as well as Crash simulations.

Please do provide any help or suggestions regarding the same.

 

I have attached the starter out (0000.out) file for concerned Simulation.

 

Regards,

Sumedh V Joshi

 

 

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2017

    Hi Sumedh,

    Use the recommended contact parameters are as below for interface Type 7:

    Istf=4

    Igap=2

    Fscale_Gap=0.8

    INACTI=6

    Gap_min=

    Fric = 0.1

    Iform=2

     

    Can you perform a model checking in HyperCrash (Quality>Model Checker), so that all possible modelling errors will be listed out. The steps for model checking can be seen at https://www.youtube.com/watch?v=xi-1EvfVuyw In the out file shared there are no penetrations listed.

     

    If you still face the issue I recommend you to share the model file through secure dropbox link so that we can review the same.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2017

    Hello George,

     

    Thanks for the reply.

    I will work on your suggestions and get back to you!

     

    Regards,

    Sumedh V Joshi

  • Andy_20955
    Andy_20955 New Altair Community Member
    edited August 2017

    Hi,

    If you cannot remove the intersections in your mesh, then you could use /INTER/TYPE24 contact with Inacti=5 in areas where you have the intersections.  TYPE24 contact deals better with intersecting meshes than TYPE7.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2017

    Hi Andy,

     

    Thanks for the reply!.

    I'll try the same and get back to you.

     

    regards,

    Sumedh

     

  • Andy_20955
    Andy_20955 New Altair Community Member
    edited August 2017

    I downloaded your *.out file.  You also need to check these warnings,

    WARNING ID :          666
    ** WARNING IN SOLID ELEMENT DEFINITION
    DESCRIPTION :  
       CHANGED CONNECTIVITY OF 3D ELEMENT ID=5865175 TO AVOID NEGATIVE VOLUME
     BRICK GROUP     18149 VECTORIZATION CODE =  255

     

    and

    WARNING ID :          430
    ** WARNING IN 4-NODE SHELL ELEMENT(S)
    DESCRIPTION :  
      CONCERNING 406 SHELL ELEMENT
      SHELL ID=31 IS A 4-NODE DEGENERATED SHELL ELEMENT, USE A 3-NODE SHELL FOR BETTER RESULTS

     

    I suspect you have some elements with poor quality that could also cause a crash.

     

Categories