lsdyna error 20252

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

Hi,

 

I got a error message listed below. What does it mean? Normally id should start from 1, but why solver told me id 0?

 

*** Error 20252 (STR+252)

     cross_section id 0 referenced but not defined

 

 

Many thanks.

Tagged:

Answers

  • tinh
    tinh Altair Community Member
    edited August 2013

    Hi,

    Go to Utility tab with LsDyna profile

    There is a tool 'Error Check' that can verify your model before test run

    It will guide you to debug some things

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2013

    Hi Tinh,

     

    Thank you for your suggestion.

     

    I have tried the 'error check' and I got a message 'no stress versus plastic strain is specified'. But I did define a LCSS id in mat24 pointing to a defined curve in plastic zone with the origin coordinate (0, yield strength). Why I still get this message?

     

     

     

     

  • tinh
    tinh Altair Community Member
    edited August 2013

    Hi,

    It's is a warning or an error message?

    It seems not to relate to runtime error 20252 as above.

    Clicking on the message will guide you to detail, it may be warning of other material

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2013

    Hi Tinh,

     

    It is an error message. When I click on the message, I was directed to material card image editor.

     

    It is better to attach a picture associating with this problem. But I can only attach a file smaller than 503bytes.

     

    PS. do you have any idea why I can not attach file freely as previously?

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited August 2013

    Hi Thomas,

     

     

    the material 'error' ins't a error. It is not clear handled at the 'old' error checker.

    Please use the new one, at Menu Tools->Model Checker->LS Dyna.

     

    It looks like a error inside of a *sectionbeam property. Maybe you have referenced to a cross section, which doesn't exists.

    It happens if you are creating a new *sectionbeam and don't edit the card. Check if there is a beamsec of 0 !?

     

    Regards,

    Mario

Categories