Error 760 and Quick tetra mesh

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

Hi,

 

I have attached the following hypermesh file. Could anyone of you tell me what the error is?

I am getting an error of 760 . Why does such an error arise.

 

Also I had a query in regards to the option quick tetra mesh. When I use this option it creates a new mesh component automatically. Now, I have 2 components one original and the other is the one with mesh. Both these components have mesh so which is used for placing Boundary conditions?

 

 

 

 

 

 

 

 

 

 

Unable to find an attachment - read this blog

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited November 2020

    Hi Kartik,

    There were 2D elements in the model which were assigned with assigned with solid property and some modelling errors. I deleted the added mass as it was not connected to any nodes. Please recreate the same where the mass should be attached to a node or group of nodes. Please check the model attached.

    Choose the component collector with tetra mesh for creating boundary conditions and loads.

    Unable to find an attachment - read this blog

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited September 2017

    Hi Kartik,

    There were 2D elements in the model which were assigned with assigned with solid property and some modelling errors. I deleted the added mass as it was not connected to any nodes. Please recreate the same where the mass should be attached to a node or group of nodes. Please check the model attached.

    Choose the component collector with tetra mesh for creating boundary conditions and loads.

    Now I am getting a new error after a little modification ERROR 760

    ** time step less or equal DTmin for solid element 20174. 

     

    What does the above error mean.

    Unable to find an attachment - read this blog

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited September 2017

    Hi Kartik,

    Do you  have /DT keyword in the engine file?. If so, please remove the same.
    The command /DT is specifying a minimum time step and if the elements timestep goes below that  the analysis will stop.  The timestep of one of your solid elements must be 
    going below mentioned timestep in /DT and this is why the analysis stops. 
    You don't need to specify a time step in your model.  RADIOSS will calculate the best timestep automatically.