Dear Hamidreza,

I suggest you to see links and attached file in subject.

-Debugging with Breakpoints - Mathematica Stack Exchange

https://mathematica.stackexchange.com/questions/.../debugging-wit...

-ANSYS Icepak: Debugging Divergence - YouTube

https://www.youtube.com/watch?v=Z2TVtO5lIhM

-Information Management:MDM Workbench:Debugging in MDM - MDM ...

https://www.ibm.com/developerworks/community/.../topic?id...

-Contact problem convergence - debug tips - ANSYS: ANSYS Software ...

www.eng-tips.com/viewthread.cfm?qid=215994

Best regards

Dear Mohammad,

First of all thanks for your reply. However, My problem was about debugging Python scripts in Workbench using Visual studio. The links and attached file provided are not relevent to my question.

After searching a lot for finding a solution for this and asking from ANSYS support, I found that this opption was avaialanble until 2011 and after that ANSYS stop providing symbols required for debugging Workbench journals. However, I found a two cents solution which is a bit difficult and time consuming. We can use print function trough out the code and check that up to where the code was running properly. This is the best option possible.

The previous answer was valid until today, since I managed to debug Workbench using VS 2019 through "Run Script File..." command. I was able to see all the variables that I defined in my code in debugging mode.

Just wanted to give updates to whoever was following this question.

Thanks,

Thanks Hamidreza for sharing

So from your comment you could depug an ANSYS workbench command using the run script option? Correct!

I have developed an ANSYS restart script but i could not see the progress of the command through each iteration and I want to make sure that the script is working as it Should be

Dear Ahmed Elhattab ,

You need to put the following code on top of the wbjn file to be able to debug in VS.

Expect that your variables are in various sub folders which are very difficult to be find, however, they are there.

import System

from System import *

System.Diagnostics.Debugger.Break()

Hope this answer helps.