API 610 Output Results

Hey guys,

This is the first time I've gone through using the API 610 module in Caesar so I'm sorry if this is obvious.

Attached is an excerpt of the output. On page 1 the base Table 5 values and load comparisons make sense (ie, everything with ratio > 1.0 failed). On page 2, the Table values are modified with the 2.0 modifier. Some of the ratios here still exceed 1.0 but say pass (highlighted).

Does this make sense? I was under the impression that when using Annex F of API 610, the individual loads (seen on page 2) still can't exceed the 2.0 multiplier for Table 5.


Thanks

API-610 6.5.5. "Annex F gives methods of qualifying nozzle loads in excess of those in Table 5."

Right, and for this first part of the API 610 report (page 2) it's simply multiplying the Table 5 factors by the 2.0 modifier.

For example, the Suction Nozzle in Load Case 1 has an Fx of 1,729 lbs. On page 1, the allowable is 700 lbs, so the ratio is 2.51 and it fails. On page 2, the modified allowable is 1,400 lbs. The new ratio is 1.26 (still exceeds the modified allowable) but it says it passes.

The way I read F.1.2.a is each force/moment should be lower than this modified allowable. Then the next step is calculating F1-F5 later in the report for the combined loads.

What am I missing?

Okay, now I'm fairly certain something is wrong with my Casear.

The top table is simply the loads pulled from the synced file.

The middle table is the modified allowable with the 2.0 factor.

The bottom table is simply dividing the actual load from the model by the modified allowable. Any ratio > 1.0 should fail here because it exceeds the 2.0*Allowable. This table shows multiple instances where a ratio > 1.0 passes.

Additionally, it seems to have swapped FY with FZ and MY with MZ. I have no idea why this is occurring.

I agree, things are off here. I have attempted to recreate your input and find different results (see below).

What version of this processor are you running? I have indicted my version with the arrow below.

Regarding the Y and Z flip - I believe your shaft is in global X, this will also be the local X axis. The standard shows local Z as "up". This will make your global Y be local Z and global Z the local Y. (To me, this is one of the most valuable parts of the processor - keeping track of global and local references.)

Can you provide your complete .C2eDB file?

Hi Dave,

Thanks for the response. CAESAR II 2018 Ver: 10.00.00.7700

Attached is the DB file. The file manager would not allow a C2eDB file to be uploaded, so I changed the extension. If this doesn't work for you just let me know.

Thanks!

Apparently this was a bug addressed in a previous service pack update.

Once the update is installed everything seems good.

The Newsreel (the left hand window on the Main Menu) reports that latest Service Pack for the current version of C2. If this doesn't match the version/build shown in the lower right corner of the Main Menu, you're not running the latest software.

You should check this (newsreel) frequently.