''No RUN command found'' in Hyperworks CFD
Hi, I am the mechanical director of the formula student team of University Laval from Québec City Canada.
We are working on our aero kit this year and I have some issues while using Hyperworks.
I have this error while I try to run a cfd in HyperWorks CFD.
It's my first CFD with HyperWorks so I really have no idea how to fix the problem.
Could you please help me ?
Thank you
Best Answer
-
Loïc de Bluze said:
Thanks for your answer.
Here is the screenshot :
I try to change the problem directory but it still do the same thing.
I typically suggest to avoid 'special' characters in names (directories, problem names, etc) - like the é in the name of one of the directories. Personally I avoid spaces and dashes/hyphens - using underscore as the separator instead. For some reason the input file is not being saved into that directory when you hit 'Run' - thus it is not found and you get that error.
(Is that directory listing of the .../CFD 1/Resultat_2/ directory?)
1
Answers
-
This essentially is saying that the problem was indicated as REAR_WING_CFD3 - but it cannot locate the matching input file REAR_WING_CFD3.inp.
Can you post a screenshot of the launch panel from HWCFD - made wide enough to see the complete paths/directories? Also a screenshot from the 'File Explorer' showing the files/directories inside the directory indicated as 'Problem Directory'.
0 -
Hi,
luckily (or sadly) I have the same issue with another file.
I have attached the two screenshots. I know there are also Ansys files inside, but this should not be the problem.
Greetings
0 -
K.B. said:
Hi,
luckily (or sadly) I have the same issue with another file.
I have attached the two screenshots. I know there are also Ansys files inside, but this should not be the problem.
Greetings
This model appears to be entirely different from the previous. Do you get the similar error in the Log file - this time Error Opening File <2flap.inp> ?
Something is preventing HyperWorks CFD from writing the input file.
Things to try:
Don't use 'special' characters in any of the directory names - like the umlaut-u in this case (Maybe try this first)
Work in directories that don't have spaces in the names anywhere in the directory structureAny difference?
0 -
acupro_21778 said:
This essentially is saying that the problem was indicated as REAR_WING_CFD3 - but it cannot locate the matching input file REAR_WING_CFD3.inp.
Can you post a screenshot of the launch panel from HWCFD - made wide enough to see the complete paths/directories? Also a screenshot from the 'File Explorer' showing the files/directories inside the directory indicated as 'Problem Directory'.
Thanks for your answer.
Here is the screenshot :
I try to change the problem directory but it still do the same thing.
0 -
Loïc de Bluze said:
Thanks for your answer.
Here is the screenshot :
I try to change the problem directory but it still do the same thing.
I typically suggest to avoid 'special' characters in names (directories, problem names, etc) - like the é in the name of one of the directories. Personally I avoid spaces and dashes/hyphens - using underscore as the separator instead. For some reason the input file is not being saved into that directory when you hit 'Run' - thus it is not found and you get that error.
(Is that directory listing of the .../CFD 1/Resultat_2/ directory?)
1