Warning Message ID 244 - Material law 25
Hello, I get this warning message for many elements in my model. I have used Law 25 to model a multi-layer composite and I get the error for different layers but I can not figure out why. Any suggestion on what to check?
MESSAGE ID : 244
** WARNING : MATERIAL LAW 25 - ELEMENT ID = 1585555 LAYER = 1
CANNOT PROJECT STRESS TENSOR ON CRITERIA
Thank you in advance!
Answers
-
I think it means that Radioss can not find a projection to the current plasticity surface in stress space
This usually happens when curvature of the plasticity surface is too high. Physically this is indication that plastic parameters may not be determined quite correctly. Say, yield stress in one of the directions is too small.
It may also be related to the relationship between your E1,E2 stiffnesses? Do you have failure defined also? What element formulation (ISHELL) are you using?
Try with Ishell=1 or 12 if you are using 24
If you can share the model we can take a look
0 -
Hello Paul,
Thanks for your answer. I am using the same value for E11 and E22 because I want to model multiple wovens layers stacked one over each other but without a matrix to bind them. I have not defined any failure. Since I have not defined /DEF/SHELL, ISHELL goes to the default value 1.
I cannot share the model.
Thank you.
0 -
Andrea_20669 said:
Hello Paul,
Thanks for your answer. I am using the same value for E11 and E22 because I want to model multiple wovens layers stacked one over each other but without a matrix to bind them. I have not defined any failure. Since I have not defined /DEF/SHELL, ISHELL goes to the default value 1.
I cannot share the model.
Thank you.
Ok, only other thing I can think of is possibly definition of the orientation (reference direction) but usually if that is an issue the warning is different, and more specifically about that (in case where orientation vector is normal to, or close to normal to the elements)
I recall getting the warning you see once several years ago, but I haven't seen it since and I can't remember what the fix was in that instance
0