Cancel
Showing results for 
Search instead for 
Did you mean: 

Combine OP2 to avoid friction path dependency

Genius
Genius

I have a model with gap contacts including friction. The order in which I analyse my loadcases has an effect on the results, because of the stored contact state. If it were frictionless it wouldn't matter. I want a load order independent analysis, and have to have a single OP2 file for further post-processing.

 

My questions are:

  1. Is there a way to combine OP2 files into a single OP2 file? In this case I could run each loadcase as a single analysis (i.e. from the zero contact state) and then combine the results.
  2. Better yet, is there a setting to tell NX-NASTRAN not to store the friciton state from one loadcase to the next with CGAP elements in a linear analysis? I know you can do this for contact surfaces, I'm just not sure about with CGAP elements.

Thanks,

Kava

2 REPLIES

Re: Combine OP2 to avoid friction path dependency

Siemens Phenom Siemens Phenom
Siemens Phenom

There is no utility to combine op2 files.Why would you really need too? Femap can attach as many op2 files as you need and if you use the option to use the filename in the study title, it is easy to keep track of which results you are looking at.

 

If you have friction in gap elements, then it is not a linear contact analysis, period. If you are running solution 106, then the analysis and its subcases are a loading history. The only way to go back to the original state, is to create a subcase where zero load is applied, get a converged answer at zero, then begin again in the next subcase.

There is no reason to do this, you should run a separate analysis for each unique load case.

 

Are you actually trying to set up a preload type condition and then apply different load conditions to this same preload solution?

A more complete description of the intent might help us provide more helpful suggestions.

 

Regards,

 

Joe

Re: Combine OP2 to avoid friction path dependency

Genius
Genius
We use external postprocessing software which requires a single op2. My
workaround is using a contact surface, which has the option to start from
initial contact state for each load case.