Jump to content
Sign in to follow this  
Tiago

Crash test using HyperCrash

Recommended Posts

Hello,

 

I am making a setup of a simple bumper structure colliding with a rigid wall on HyperCrash. I am using the Johnson-Cook model for the material.

 

The structure is made of a beam with 2 crash boxes attached with spot welds. In the beginning of the test the structure is already vibrating (Capture2) and seems that the boxes are colliding with the beam instead of being attached.

 

Can anyone help me to solve this vibration problem? can it be from the type of connection that I am using? Should I use other? see the print screens and tell me what you think. There are stress concentration close to the spot welds because they are completely rigid elements (Capture3)

 

Another big problem is that the material is not having the desirable behavior. It is aluminum and should bend on crash but is not bending, its fracturing (Capture4)

Capture1.PNG

Capture2.PNG

Capture3.PNG

Capture4.PNG

Share this post


Link to post
Share on other sites

The connectivity is ok and the rigid body too. I followed that tutorial and I am making a new simulation now but it takes 10 times more time than the old one to run. 

 

I am trying to use the exact same material and connections to see if the problem has another source. 

 

For that kind of steel and an element characteristic length of 5mm i am using an inicial timestep of 5 as they recommend. But in my calculations it should be closer to 1 if I am not mistaken.

 

It will take an hour to run. I let you know if its working. 

 

 

 

 

Share this post


Link to post
Share on other sites
Guest

Hi Tiago,

From the engine out file find what is causing for the time step drop.

It can be an element, a node or an interface.

•For an element, check the related material (especially its Young modulus and density in case of an elastic-plastic material; and its viscosity in case of a visco-elastic material). There must not be an error in the units system that this data is given in.

Check the size of the element, since elemental length is proportional to time step.

•For a node, check the characteristics of connected elements. If the node is on the master side or the slave side of an interface, this interface must be verified.

•For an interface, the gap of the interface must be verified if some failure happens on the master or the slave side of the interface.

 

Once this is cleared you can run the simulation without time step being dropped.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
You are posting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...