error trapped

Hi,

Error trapped does not provide any information about the source of the problem, so it's hard to say. Can the input files be shared?

Hi

It's typical error and difficult to identify.

But you can cross check the model error us in HyperWorks / HyperMesh using Model checker tool.

it finds all the basic errors.

Still if you face the issue, please create ticket using Altair-one account

Regards

Harish

hi, thanks for advices, this is my file, can u check it for me ???

i'm using this model for crash simulation, but it's not working

hi, thanks for advices, this is my file, can u check it for me ???

i'm using this model for crash simulation, but it's not working

Hello! 

I've looked at your model, and I would like to make some comments.

1. When I run the model checker, it points to an error of Degenerated 4-node shells. This happens because the element type is not appropriate. If you right-click and isolate these degenerated 4-node shells, you will see that they are actually tria elements with quad config (SHELL4N). To solve this problem, you can select these degenerated elements and update their config to SHELL3N.

2. I don't have your run parameters (run time, animation frequency etc.), but running just the starter file, I found an issue with your property ID 4000197 related to the foam material. This property uses Isolid = 104, which does not exist. You can find more information about solid property here: /PROP/TYPE14 

3. I suggest checking the mesh quality, materials, etc. Quickly looking at the element quality check shows me 471 elements with questionable connectivity and a minimum normalized height of 0.0.

Generally, always check the model in HyperMesh using the Model Checker and the element quality. It will show you any inconsistencies in the model that may be corrected. 

Hope this helps you!

Hello! 

I've looked at your model, and I would like to make some comments.

1. When I run the model checker, it points to an error of Degenerated 4-node shells. This happens because the element type is not appropriate. If you right-click and isolate these degenerated 4-node shells, you will see that they are actually tria elements with quad config (SHELL4N). To solve this problem, you can select these degenerated elements and update their config to SHELL3N.

2. I don't have your run parameters (run time, animation frequency etc.), but running just the starter file, I found an issue with your property ID 4000197 related to the foam material. This property uses Isolid = 104, which does not exist. You can find more information about solid property here: /PROP/TYPE14 

3. I suggest checking the mesh quality, materials, etc. Quickly looking at the element quality check shows me 471 elements with questionable connectivity and a minimum normalized height of 0.0.

Generally, always check the model in HyperMesh using the Model Checker and the element quality. It will show you any inconsistencies in the model that may be corrected. 

Hope this helps you!

thanks for your suggestions

can u give me more detail about comment 1: what tool i can use for update their config to shell3N

thanks for your suggestions

can u give me more detail about comment 1: what tool i can use for update their config to shell3N

 

Sure!

If you are using HyperMesh in the new interface, you can go to Elements > Edit > Change element config > Select 2D - Tria3

Or you can search by using crtl+f and search for element config.

If you are using the HyperMesh in the legacy interface, you can go to the 2D Panel > Config Edit > New config = tria3.

After updating, I would suggest checking the model checker again to see if everything is ok.

Hope this helps!

Sure!

If you are using HyperMesh in the new interface, you can go to Elements > Edit > Change element config > Select 2D - Tria3

Or you can search by using crtl+f and search for element config.

If you are using the HyperMesh in the legacy interface, you can go to the 2D Panel > Config Edit > New config = tria3.

After updating, I would suggest checking the model checker again to see if everything is ok.

Hope this helps!

thanks you

i'm so appreciate, but my time step is very low, can u give me some ideals for this problem

have nice day !!!

Sure!

If you are using HyperMesh in the new interface, you can go to Elements > Edit > Change element config > Select 2D - Tria3

Or you can search by using crtl+f and search for element config.

If you are using the HyperMesh in the legacy interface, you can go to the 2D Panel > Config Edit > New config = tria3.

After updating, I would suggest checking the model checker again to see if everything is ok.

Hope this helps!

I try to fix min length, but the time step is still low, can u give me some advices, sorry to disturb you 

thanks and best regards

thanks you

i'm so appreciate, but my time step is very low, can u give me some ideals for this problem

have nice day !!!

You're welcome!

The critical time step is the time required for a shock wave to propagate across the smallest distance in an element. It is calculated by L/c, where L is the characteristic length of the element and c is the speed of sound in the material.

So as you can see, the issue can be:

1. Material definition: If the material density and Young Modulus are not well set (e.g. wrong unit system), the time step can be very low.

2. Mesh quality: The minimum element size will control your time step, so if your mesh quality is poor, your time step will be very low.

From what I saw in your model, you need to correct the mesh. There are 203 elements with a minimum length smaller than 0.05. You can also double-check the materials.

If, after correcting the mesh, you still need to improve the time step, one can use a time step control, like /DT/NODA. Using this control, one can define the target time step and a scale factor but always need to be careful about the amount of mass that will be added to the model. The starter out file (0000_out) will give you some information about the time step size, the estimation of mass added per time step, and so on.

You can gather more information on Time Step Control, Time Step, Nodal Time Step Control.

Altair will give a Radioss Training from June 26 to 29. If you would like to attend, here is the registration link: https://learn.altair.com/mod/facetoface/eventinfo.php?s=2972

Regards, 

Guilherme.

You're welcome!

The critical time step is the time required for a shock wave to propagate across the smallest distance in an element. It is calculated by L/c, where L is the characteristic length of the element and c is the speed of sound in the material.

So as you can see, the issue can be:

1. Material definition: If the material density and Young Modulus are not well set (e.g. wrong unit system), the time step can be very low.

2. Mesh quality: The minimum element size will control your time step, so if your mesh quality is poor, your time step will be very low.

From what I saw in your model, you need to correct the mesh. There are 203 elements with a minimum length smaller than 0.05. You can also double-check the materials.

If, after correcting the mesh, you still need to improve the time step, one can use a time step control, like /DT/NODA. Using this control, one can define the target time step and a scale factor but always need to be careful about the amount of mass that will be added to the model. The starter out file (0000_out) will give you some information about the time step size, the estimation of mass added per time step, and so on.

You can gather more information on Time Step Control, Time Step, Nodal Time Step Control.

Altair will give a Radioss Training from June 26 to 29. If you would like to attend, here is the registration link: https://learn.altair.com/mod/facetoface/eventinfo.php?s=2972

Regards, 

Guilherme.

this is my model, i try to solve problem about minimal height, but the time step is still  low, can you check for me, 

Thanks and best regards.

i will register your seminar