Learning Forum

[Yonghwa Yi]

I am currently working on simulating usercreep using UPF.

 

After modifying usercreep file, ansys.exe was created through anscust.bat, but ansys mechanical apdl product launcher cannot read ansys.exe made by anscust.bat

 

In this case, how do I solve the problem?

 

[David Weed]

Hi,

Can you see if it makes a difference if you make the file name all lower case, i.e., "ansys.exe"?

[Yonghwa Yi]

If you change the file name to lowercase, UPF is not applied. the original MAPDL is just opened.

[David Weed]

I can reproduce the same error message in v221 when I make the custom executable file name all caps. If I change it back to lower case, then I can open an interactive MAPDL session without error. If MAPDL recognizes the custome exe then you should see this message in the output window:

Note - This ANSYS version was linked by Licensee

[David Weed]

As a sanity check to see if your modified subroutine is being used in the custom exe, you can insert a Fortran write statement into the subroutine code, e.g., write(*,*) 'my usercreep routine is working'. When you compile and run a sample problem, you should see the write statement print during the solve.

[Yonghwa Yi]

does this problem occur because I used intel open API? If so, I'm planning to purchase intel parallel studio .

[David Weed]

That might be the case because Intel oneAPI is not officially supported. For v221, these are the software items that are needed and supported: https://ansyshelp.ansys.com/account/secured?returnurl=/Views/Secured/corp/v221/en/installation/win_compilers.html

Microsoft Visual Studio Professional 2019 Version 16.0.22 (including the MS C++ compiler), Intel C++ and Intel Visual FORTRAN 2019 Update 5 (2019.5.281)