Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

MESSAGE ID : 11 ERROR IN ALE INTERFACE, need help!!

Altair Forum User

Hello there,

I got following message(from XX0001.out) while I am running a project in Radioss.

MESSAGE ID : 11

** ERROR IN ALE INTERFACE

NODE ID=101911 HAS 3 BOUNDARY CONDITIONS

And then I find that node 101911 and I am sure there's only one BC on this node, so why this message comes, and how can I solve it?

image.png.1b76612a08152ceb785320bca61e26ed.png

Thx in avance.

Find more posts tagged with

English

Radioss

Accepted answers

All comments

Altair Forum User

Hi,

Can you please the model file through the secure dropbox link?.

Also let us know which HyperWorks version are you using.

Altair Forum User

image.png.ef406ee6bfe588d0e8bf2916d32dadcc.png

I dont know how to upload my file through the secure dropbox, so I'll attach my Model here.

And by the way there are also some orther warnings like this and I want to know it as well.

image.png.d23cddc3572c535bf37161bf361cc67a.png

Thanks a lot George.

Unable to find an attachment - read this blog

Altair Forum User

Hi,

For the solid property Isolid=17 is not compatible for ALE. Update Isolid=24.

I recommend you to recreate the interface. Note that this interface is a kinematic condition and no other kinematic condition should be set on any node of the slave surface.

If you trying for a kinematic condition you can also try with Type 2 interface.

Altair Forum User

Hi George,

I've changed the solid property

image.png.95b88638cb5fc292453b731697680ce1.png

But it seem that ISOLID24 won't work in this condition. And I think before that I used Isolid=2 instead of 17, and when I use isolid=2 there's no error like this.

image.png.514e37c904c9f5a4c711cf486307b772.png

Altair Forum User

I've changed interface to type 2 and Isolid=0 as default, and then the analysis runs for very short time with some warnings.

And the problem is that after several seconds it will stop since a error message id167:

MESSAGE ID : 167

** STOP : NEGATIVE RHO=-0.4649246740324E-01 FOR 3D-ELEMENT ID=2146

And I fond this topic which has the same question with me but it seems that he has not solved it. So could anyone please help me with this problem?

Altair Forum User

Hi,

The NEGATIVE VOLUME error happens when solid elements are very deformed and their characteristic length goes to 0. For large strain formulation the time step of an element goes to 0 when the element is compressed. In RADIOSS Starter input file (Runname_0000.rad), use Ismstr =2 in the solid property and in RADIOSS Engine file (Runname_0001.rad) use the option/DT/BRICK/CST which will set the time step value tmin at which the solid elements will switch to small strain.This means that the solid elements using Ismstr =2 will use large strain formulation while their time step remains greater than tmin, and will then switch to small strain formulation.

Altair Forum User

image.png.d0dcd1a736d2e373bddc4d9cf5f3ee1e.png

image.png.59a9546449d863c45e81c491dfc26694.png

Like this?

But there's nothing changing.

Unable to find an attachment - read this blog

Altair Forum User

Hi,

This seems like the solid elements are deforming very badly. Please recheck the material parameters and also you can try with Ismstr=1.

If issue persist please share the model file.

Altair Forum User

Still nothing changes, and I'am sure the materail parameters are correcte because I used the same material for the type of Lagrange instead of ALE and it works well.

So here's my file and thx in advance.

Unable to find an attachment - read this blog

Altair Forum User

Hi,

Please try with the attached file.

Unable to find an attachment - read this blog

Altair Forum User

Hi,

I think it doesn't work either, the interface seems useless in this case, that master shell will traverse these slaver elements instead of impact.

image.png.f857ae56d358b6e4e865de7ebf3ca8f6.png

Is that because interface type2 is not compatible for ALE material, or maybe these are some other reasons?

Altair Forum User

Hi,

Please try running with a different contact type.

<?xml version="1.0" encoding="UTF-8"?>