Internal Error Detected in Module

[sigurd.naess]

Hi!

I'm getting the following error when running my analysis:

My analysis is a duplication of a shell model non-linear analysis that ran just fine

Only changes are:

- Kinematic material model (plasitc material)

- 8 subcases cyclic the loads from 100% to 0%  and so on

My wish is to plot sigma1 vs epsilon1 to check for strain accumulation

Any thoughts on how to bypass this error?

Regards

I'm using Nastran 2022:

[sigurd.naess]

Hi!

I'm getting the following error when running my analysis:

My analysis is a duplication of a shell model non-linear analysis that ran just fine

Only changes are:

- Kinematic material model (plasitc material)

- 8 subcases cyclic the loads from 100% to 0%  and so on

My wish is to plot sigma1 vs epsilon1 to check for strain accumulation

Any thoughts on how to bypass this error?

Regards

I'm using Nastran 2022:

[salih_kapucu]

Hi @sigurd.naess 

Could you check the mates in the support, load and analysis section?

[salih_kapucu]

Hi @sigurd.naess 

Could you check the mates in the support, load and analysis section?

[vanderson.mapdata]

Hi @sigurd.naess 

Error S1117 could be generated from some causes in models:

Superelement, Contact or Mesh.

I see your model and you have some edge to surfacecontacts. Try generate continuous mesh instead of using contact. It could help you with this model.

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[vanderson.mapdata]

Hi @sigurd.naess 

Error S1117 could be generated from some causes in models:

Superelement, Contact or Mesh.

I see your model and you have some edge to surfacecontacts. Try generate continuous mesh instead of using contact. It could help you with this model.

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[sigurd.naess]

Hi @vanderson.mapdata @salih_kapucu 

Funny thing, I made a new analysis and repeated the same steps when setting up my model and it ran fine when using 8 subcases to cycle the load, but when adding more subcases the same error appeared. 

(My results for one node 😁)

@john.holtz are you aware of any limits to the number of subcases in a static non-linear analysis, that would explain the S1117 error? 

Thank you!

Regards

[sigurd.naess]

Hi @vanderson.mapdata @salih_kapucu 

Funny thing, I made a new analysis and repeated the same steps when setting up my model and it ran fine when using 8 subcases to cycle the load, but when adding more subcases the same error appeared. 

(My results for one node 😁)

@john.holtz are you aware of any limits to the number of subcases in a static non-linear analysis, that would explain the S1117 error? 

Thank you!

Regards

[John_Holtz]

Hi @sigurd.naess 

That is a neat graph!

I am not aware of any limit to the number of subcases in a nonlinear analysis, but I have probably only used 3 or  4 subcases maximum.

How much free space does the C: drive have before you run the analysis? I see from the output tab that the C: drive has 76 GB of free space. That is probably enough free space for a model that size, but I have seen some models (monster models) where 700+ GB of disk space gets used. It's possible the internal error is related to free space. The misleading thing is after the analysis fails, the temporary files are cleaned up, so it may look like the drive has a lot more free space than when the analysis is running.

The other possibility is there is something in the model that leads to the internal error. If you can post your model, I will run it here. (Zip the assembly and part files and attach them.)

John

[John_Holtz]

Hi @sigurd.naess 

That is a neat graph!

I am not aware of any limit to the number of subcases in a nonlinear analysis, but I have probably only used 3 or  4 subcases maximum.

How much free space does the C: drive have before you run the analysis? I see from the output tab that the C: drive has 76 GB of free space. That is probably enough free space for a model that size, but I have seen some models (monster models) where 700+ GB of disk space gets used. It's possible the internal error is related to free space. The misleading thing is after the analysis fails, the temporary files are cleaned up, so it may look like the drive has a lot more free space than when the analysis is running.

The other possibility is there is something in the model that leads to the internal error. If you can post your model, I will run it here. (Zip the assembly and part files and attach them.)

John