External code stagger skipped
hi everyone,
I'm trying to use acusolve & optistruct for a TFSI simulation.
The TFSI in my case is: Acusolve (flow+thermal) for Fluid domain * OptiStruct thermal for Solid domain
I have made 2 completed models for OS and Acusolve and both of them can run separately.
However, when i tried to run the direct coupling b/w 2 solvers, the error happens.
At the 1st time step, the OS and AcuSolve seems connected.
But from the 2nd time step, it looks like OS was stopped and the log file showed as below:
This make the OS cannot complete the simulation and there is no result from OS, only from AcuSolve.
You can find all the models, files from my gg drive:
https://drive.google.com/drive/folders/1zuuRDFtnrT0MHQBp9D0BVFSqdbSpPuiJ?usp=sharing
Could you help debug this error?
Thanks in advance!
Answers
-
The 2-way transient coupling for AcuSolve and OptiStructs only supports the exchange of forces/displacements, for a deforming body due to pressure/force loads. The 2-way transient coupling exchange for thermal loading is not yet supported. On the thermal side, it would just be a single exchange of the thermal information, which is why only the first time step was reported, with the other exchanges being ignored. You would run the complete thermal on the AcuSolve side, then transfer that thermal information on the wetted surfaces to the OptiStruct model.
For my own understanding, is your desire just to do the thermal exchange, or are you also wanting to simulate the deformation due to the thermal transient?
0 -
acupro_21778 said:
The 2-way transient coupling for AcuSolve and OptiStructs only supports the exchange of forces/displacements, for a deforming body due to pressure/force loads. The 2-way transient coupling exchange for thermal loading is not yet supported. On the thermal side, it would just be a single exchange of the thermal information, which is why only the first time step was reported, with the other exchanges being ignored. You would run the complete thermal on the AcuSolve side, then transfer that thermal information on the wetted surfaces to the OptiStruct model.
For my own understanding, is your desire just to do the thermal exchange, or are you also wanting to simulate the deformation due to the thermal transient?
hi Acupro,
Thank you for your response.
Actually, i'm not so agree with you about the capabilites of OS-Acu FSI.
I have read in OS help session about the TFSI, OS-Acu can perform TFSI for 2-way transient.
To do this, the FSI card need to be defined with FSI DATA = 3 in the card.
(i have done this in my model)
We also have a tutorial about this transient TFSI in OS help.
However, the orginal tutorial/model files are not completed by the writer >> so i'm trying to debug & run it.
About your questions, i want to perform transient thermal exchange for 1st step, deformation will be the 2nd step.
Anyway, thank you very much for your kind help!
0 -
Junta_20361 said:
hi Acupro,
Thank you for your response.
Actually, i'm not so agree with you about the capabilites of OS-Acu FSI.
I have read in OS help session about the TFSI, OS-Acu can perform TFSI for 2-way transient.
To do this, the FSI card need to be defined with FSI DATA = 3 in the card.
(i have done this in my model)
We also have a tutorial about this transient TFSI in OS help.
However, the orginal tutorial/model files are not completed by the writer >> so i'm trying to debug & run it.
About your questions, i want to perform transient thermal exchange for 1st step, deformation will be the 2nd step.
Anyway, thank you very much for your kind help!
It does appear the transient with thermal exchange only should work - so long as you don't also want deformation. I've not much knowledge on the OptiStruct setup...
0 -
Junta,
May I ask which version of OptiStruct and AcuSolve you are running?
Also, I am attaching the completed set of models for OS-T: 1610 here.
Please see if this works for you on your end. Please try version 2019.0 if you have it available.
FYI - In one of the images of the tutorial, there is a typo wherein FSIDATA is set to 1 when it should have been 3 for thermal FSI. This will be fixed in the upcoming OptiStruct version help.
Regards,
Rajiv1 -
acupro_21778 said:
It does appear the transient with thermal exchange only should work - so long as you don't also want deformation. I've not much knowledge on the OptiStruct setup...
thanks acupro,
yes
currently TFSI between OS and AcuSolve only support for:1. steady state solution (CFD >> mapping result >> Structure)
2. transient solution but for thermal exchange only, no force/deformation supported.
0 -
Junta,
May I ask which version of OptiStruct and AcuSolve you are running?
Also, I am attaching the completed set of models for OS-T: 1610 here.
Please see if this works for you on your end. Please try version 2019.0 if you have it available.
FYI - In one of the images of the tutorial, there is a typo wherein FSIDATA is set to 1 when it should have been 3 for thermal FSI. This will be fixed in the upcoming OptiStruct version help.
Regards,
Rajivhi Rajiv,
Thank you very much for your support.
I'm using version 2020 for both OS and Acu.
I also tried with your files on version 2020 but the error still happens.
I will try with version 2019 and see if this works.
Anyway, many thanks for you!
0 -
Junta,
May I ask which version of OptiStruct and AcuSolve you are running?
Also, I am attaching the completed set of models for OS-T: 1610 here.
Please see if this works for you on your end. Please try version 2019.0 if you have it available.
FYI - In one of the images of the tutorial, there is a typo wherein FSIDATA is set to 1 when it should have been 3 for thermal FSI. This will be fixed in the upcoming OptiStruct version help.
Regards,
Rajivhi Rajiv,
Thank you for your support.
I have tried your model on version 2019 for both OS and AcuSolve.
This time, it shows another error as below:
Please note that these models can run on version 2020 but it skips the external code staggers.
Thank you!
0 -
Junta_20361 said:
hi Rajiv,
Thank you for your support.
I have tried your model on version 2019 for both OS and AcuSolve.
This time, it shows another error as below:
Please note that these models can run on version 2020 but it skips the external code staggers.
Thank you!
This appears to be working properly now in the 2021.1 release for both solvers.
0