filippo1
Mechanical
- Oct 23, 2006
- 2
Hello,
I'm trying to use a custom script that would start when I push the "solve" button on mechanical. The idea is to create some kind of "model check" before running a analysis.
I have made a little test that doesn't really works but that explains my goal.
I have renamed the ANSY160.exe file under the ansys installation to ANSYS160_.exe
and i have create my own ASNYS160.exe that retreive the arguments give by Workbench, runs my custom script and then starts the ANSYS160_.exe (the original .exe) with the arguments retreived before. This almost works...
for small models(models that runs fast) when I click on solve it runs my script, launches the anlysis and I can get the results as usual. IT WORKS JUST FINE
The problem is that if I do the same with a bigger model, Workbench returns an unknown error and I can't get the results...
AND IT THIS CASE IT DOESN'T WORK
I know I'm cheating Workbench, but I gave a try...
If some of you have some you guys have an idea??? workaround???
Do you know if I can ask mechanical workbench to use a custom solver? and how?
do you know if i can add a snippet that starts an external script..(this would be a workaround, if i can't make it directly with the "solve" button.)
Anyway I hope my question is clear enough... and I hope it can inspire some of you...
Regards
Filippo
I'm trying to use a custom script that would start when I push the "solve" button on mechanical. The idea is to create some kind of "model check" before running a analysis.
I have made a little test that doesn't really works but that explains my goal.
I have renamed the ANSY160.exe file under the ansys installation to ANSYS160_.exe
and i have create my own ASNYS160.exe that retreive the arguments give by Workbench, runs my custom script and then starts the ANSYS160_.exe (the original .exe) with the arguments retreived before. This almost works...
for small models(models that runs fast) when I click on solve it runs my script, launches the anlysis and I can get the results as usual. IT WORKS JUST FINE
The problem is that if I do the same with a bigger model, Workbench returns an unknown error and I can't get the results...
AND IT THIS CASE IT DOESN'T WORKI know I'm cheating Workbench, but I gave a try...
If some of you have some you guys have an idea??? workaround???
Do you know if I can ask mechanical workbench to use a custom solver? and how?
do you know if i can add a snippet that starts an external script..(this would be a workaround, if i can't make it directly with the "solve" button.)
Anyway I hope my question is clear enough... and I hope it can inspire some of you...
Regards
Filippo