Discussion Closed This discussion was created more than 6 months ago and has been closed. To start a new discussion with a link back to this one, click here.

Prestressed frequency analysis is not supported in Beam interface

Please login with a confirmed email address before reporting spam

Hi,

when I analyze a shell-truss-beam coupling system by 5.5 version, a error always appearred as 'Prestressed frequency analysis is not supported in Beam interface'. but if I use 5.4 version to analyze this problem, the error will not appear. Do you have any ideas about this? Thanks very much for your help.

Lin


3 Replies Last Post Jul 10, 2020, 4:22 a.m. EDT
Henrik Sönnerlind COMSOL Employee

Please login with a confirmed email address before reporting spam

Posted: 4 years ago Jul 8, 2020, 7:10 a.m. EDT

It was never possible to take prestress effects into account in the Beam interface, but there was no warning message before.

-------------------
Henrik Sönnerlind
COMSOL
It was never possible to take prestress effects into account in the Beam interface, but there was no warning message before.

Please login with a confirmed email address before reporting spam

Posted: 4 years ago Jul 9, 2020, 4:05 a.m. EDT

Dear Henrik, thank you very much.

I want to get the natrual frequency of a coupling system. This system includes beam, truss and shell. Acturally, prestress effects the truss obviously, but not beam. So I am trying to run the study of frequency domain, prestressed for the whole system. Then, there is a error messsage ' Prestressed frequency analysis is not supported in Beam interface. ' Would you share any ideas for getting the frequency of the whole coupling system? Thank you very much for your help.

Lin

Dear Henrik, thank you very much. I want to get the natrual frequency of a coupling system. This system includes beam, truss and shell. Acturally, prestress effects the truss obviously, but not beam. So I am trying to run the study of frequency domain, prestressed for the whole system. Then, there is a error messsage ' Prestressed frequency analysis is not supported in Beam interface. ' Would you share any ideas for getting the frequency of the whole coupling system? Thank you very much for your help. Lin

Henrik Sönnerlind COMSOL Employee

Please login with a confirmed email address before reporting spam

Posted: 4 years ago Jul 10, 2020, 4:22 a.m. EDT
Updated: 4 years ago Jul 10, 2020, 5:17 a.m. EDT

Hi Lin,

The scenario which you outline here (where beams are present in a larger structure, but are not important from a prestress point of view) is of course meaningful.

There is no way to get past the error message in version, and it should not be possible, since we cannot guarantee that the results will be correct, even in your scenario.

In the future, the fact that beams are present in the model should generate a warning, not an error. One of our developers is looking into this. It is, however, not just a matter of changing the message. It must also be ensured that the stiffness matrices generated for the beams are not wrong.

If you send your model to support, it may be possible to find a workaround.

-------------------
Henrik Sönnerlind
COMSOL
Hi Lin, The scenario which you outline here (where beams are present in a larger structure, but are not important from a prestress point of view) is of course meaningful. There is no way to get past the error message in version, and it should not be possible, since we cannot guarantee that the results will be correct, even in your scenario. In the future, the fact that beams are present in the model should generate a warning, not an error. One of our developers is looking into this. It is, however, not just a matter of changing the message. It must also be ensured that the stiffness matrices generated for the beams are not wrong. If you send your model to support, it may be possible to find a workaround.

Note that while COMSOL employees may participate in the discussion forum, COMSOL® software users who are on-subscription should submit their questions via the Support Center for a more comprehensive response from the Technical Support team.