High friends

We had a case concerning the application of f=1.2 in CAESARII

there are some answers, but non of them is addressing the load cycle N range , from Fig 302.3.5 in ASME B 31.3 (2004) , why is it so???

does it have any effect on f?( seems to have )

regards

shahram

1)Read this post: http://www.coade.com/ubbthreads/ubbthreads.php?ubb=showflat&Number=10405&page=1#Post10405

2) Send us the job if you can't figure it out.

Friends

I need to when we use Algebric or Scaler or any other method to combine the stresses ( load cases) .

Regards

Shahram

Richard

Thanks for your reply

I checked the mentioned case ,you had mentioned the code requirments as followings:

You just can't use f=1.2, there are some checks to be made. The Code allows "f" to go to 1.2 if:

(a) the material is ferrous - CAESAR II can't check this one, you have to
(b) the min tensile strength does not exceed 75 ksi, - CAESAR II can't check this one, you have to
(c) the temperature is less than 700 degF.

If you exceed any of these, "f" is limited to 1.0. CAESAR II can only enforce the temperature limit, so my guess is that your over this

But dose the load cycle has any effect here???

If you specified the number of cycles (either in the "f" field of the input or on the "Load Case Options" tab of the Load Case Editor), then CAESAR II uses the equation to determine "f".

In general, "Algebraic" should be used for all combinations except the "OCC" stress summation. There is help text available in the Load Case Editor for this option. See if this is sufficient.

Hi,

What is the rational behind this difference treatment.

Can I get some advice,

Thanks

Lawrence