My company recently updated our CAESAR version to 5.10 and I`m still trying to get used to it. I`m working on a project right now where the load case combinations are quite complicated.

I have to create a case where all operating conditions plus occacional conditions (win1, win2, U1, F1, etc...) are present. After that I have to sustract this case to the original operation case to obtain the occasional condition alone, and after that, I have to make a case where I combine Sustained conditions and The occacional condition previously obtained.

The version we were working with before (4.5) could do this operations without any problems, but in 5.10 I have some troubles in the results. For example, for cases where occacional conditions are included, the stress summary seems to be fine, less than 100%, but when I check the results node by node, I see some element with percents of 999%, even when the code stress is less than allowable. What`s going on? I have some troubles with the restrain loads too. Does CAESAR II v5.10 does not let me to do this type of combinations or do I need to correct something in the configuration?

Best Regards

Hi Ramon.

I can't say I remember having problems like that since we updated to 5.1 a while ago, but have you checked you have downloaded the lastest build from coade?

Looks like you should show your model to your CAESAR II dealer or to COADE. If you want, send your file to techsupport@coade.com.

Was there a general solution to this problem? I'm having this same problem using version 5.20. It happens in my wind load cases. Calculated stresses are negative but small in magnitude and the report indicates 999% of the allowable. I am very out of practice at using Caesar so modelling mistakes are very possible.

Send the model in to TechSupport, that is the only way we can answer this. I've (personally) never seen this happen.

Previously suggested by Loren:

Check your combination method in the load case editor. If you are adding load cases then use scalar, if you are subtracting load cases then use algebraic.

Regards,

Loren A. Brown
Senior Engineer/Developer

Also check some elbow nodes (out of sequence)- BUT this may be UNRELATED.

Unless your model is secret, you can post it here. This way someone can take a look and can tell you more.

Regards,