Step into, Step over and Step out are getting disabled whenever I run the sequence. Also Run Button is getting disabled after the execution breaks at break point.
Its very difficult to debug the code because of these isssues.
Is that anything to do with custom process model ? I use a third party process model. But in other PCs which are also using the same process model dont have these issues.
Does this happen with a simple sequence file? For example, if you create a new sequence file with only a Message Popup step, set a breakpoint, and then try to debug, does it work properly or do you have the debugging buttons grayed out in this case too?
This is most likely happening because your sequence has multiple threads and not all of the threads are being suspended when you hit the breakpoint. For example, if you have a LabVIEW VI executing in a different thread when the breakpoint is hit, you will not be able to debug unless the LabVIEW thread suspends. Here is a KnowledgeBase article describing this case: http://digital.ni.com/public.nsf/allkb/46D1E157756C37E686256CED0075E156?OpenDocument
It is possible that it is being caused by the process model, but I'd start by trying a very simple sequence file. If that works properly, we know it's something in your larger sequence file. If the simple file also does not allow debugging, we might look into the process model for the issue.
Let us know if you have any further questions!
it seems that was a great answer 😉
now it is emtpy.
Its now working after I made the externally suspended setting in Labview code which is being called in my sequences.